vectronic / homebridge-shinobi

A Homebridge plugin integrating Shinobi for motion detector cameras

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

ECONNREFUSED

Archerious opened this issue · comments

What's odd is my shinobi is using port 8080, and I set to http://10.1.1.44:8080 in the shinobi api plugin settings, and confirmed it shows that in config, but yet it seems when the iOS device is requesting the feed in homekit it's doing it over port 80 which is causing ECONNREFUSED.

Any suggestions?

[5/15/2021, 12:51:30 AM] [Shinobi] handleSnapshotRequest() error: request to http://10.1.1.44/:8080undefined failed, reason: connect ECONNREFUSED 10.1.1.44:80
[5/15/2021, 12:51:31 AM] [Shinobi] handleSnapshotRequest() error: request to http://10.1.1.44/:8080undefined failed, reason: connect ECONNREFUSED 10.1.1.44:80
[5/15/2021, 12:52:21 AM] [Shinobi] handleSnapshotRequest() error: request to http://10.1.1.44/:8080undefined failed, reason: connect ECONNREFUSED 10.1.1.44:80
[5/15/2021, 12:52:21 AM] [Shinobi] handleSnapshotRequest() error: request to http://10.1.1.44/:8080undefined failed, reason: connect ECONNREFUSED 10.1.1.44:80
[5/15/2021, 12:53:21 AM] [Shinobi] handleSnapshotRequest() error: request to http://10.1.1.44/:8080undefined failed, reason: connect ECONNREFUSED 10.1.1.44:80
[5/15/2021, 12:53:21 AM] [Shinobi] handleSnapshotRequest() error: request to http://10.1.1.44/:8080undefined failed, reason: connect ECONNREFUSED 10.1.1.44:80
[5/15/2021, 12:54:31 AM] [Shinobi] handleSnapshotRequest() error: request to http://10.1.1.44/:8080undefined failed, reason: connect ECONNREFUSED 10.1.1.44:80
[5/15/2021, 12:54:31 AM] [Shinobi] handleSnapshotRequest() error: request to http://10.1.1.44/:8080undefined failed, reason: connect ECONNREFUSED 10.1.1.44:80
        {
            "monitors": [
                {
                    "monitor_id": "is1NKBvgHZ"
                },
                {
                    "monitor_id": "DJwCaFW0Rd"
                }
            ],
            "shinobi_api": "http://10.1.1.44:8080",
            "api_key": "CENSORED",
            "group_key": "CENSEORED",
            "web_hook_port": 8080,
            "platform": "Shinobi"
        }
    ]
}

The log message mentioning http://10.1.1.44/:8080undefined looks strange as this is an invalid URL.

Is Shinobi listening on the same IP as this homebridge plugin?

If so, it is possible that you have setup Shinobi to listen on http://10.1.1.44:8080 via the "shinobi_api" property AND you have setup this plugin to listen on http://10.1.1.44:8080 as well via the web_hook_port property?

In this case the plugin might be calling itself, instead of Shinobi....

Closing due to no response.