search

NorthernMan54 / homebridge-alexa

Expose your homebridge controlled devices to Amazon Alexa.
https://www.homebridge.ca
442 stars 77 forks source link

Last plug-in response error #510

Closed mariomaz87 closed 2 years ago

mariomaz87 commented 2 years ago

Hi, Since a few days I have a problem with the plug-in. Alexa can’t communicate with the devices. If I check the web status, everything is green expect “Last plug-in response” which is red. If I restart HomeBridge, it works for a some time but after a few hours it’s back to no response. I’m using the latest version of the plug-in. Can I troubleshoot the issue in some way? Thanks!

NorthernMan54 commented 2 years ago

You can try tuning the Cloud Server Connection Keepalive parameter, default is 20 minutes, try 10 or 5, or worst case 1.

ckristo commented 2 years ago

Seems I have the same issue - "Last plug-in response" is red. I set the keepalive config parameter to 10 for now and will monitor the situation now.

WinfriedO commented 2 years ago

I had been using a beta version for some time that did not require a "keepalive" setting. Before that, there was once a version where this setting was part of the settings in the user interface and only a different value had to be entered. After the last update, the setting had to be added via the advanced settings, which I don't find so great now.

On my Raspberry Pi with Hoobs 4 I use the setting: "keepalive": 200

Where that 200 means 200 seconds. Values below 10 are probably interpreted as minutes. So maybe I could also use "keepalive": 3 or "keepalive": 4

ckristo commented 2 years ago

Changed to 10 minutes, no improvements - "Last plug-in response" still unchanged and red. @NorthernMan54: any idea what could cause this? In order to debug this more efficiently, what does "Last plug-in response" indicate? Is this communication from the plugin to the Alexa skill? Shall I try to debug my network setup (e.g. firewall that blocks communication)?

Here the last logs related to homebridge-alexa:

[24/04/2022, 19:18:52] [Alexa] ERROR: ( homebridge-alexa) You have an issue with your installation, please review the README.
2022-04-24T17:18:52.951Z alexaLocal connect command/ckristo/#
2022-04-24T17:26:40.121Z hapNodeJSClient Starting Homebridge instance discovery
2022-04-24T17:26:40.154Z hapNodeJSClient HAP Device discovered Homebridge XXXX YYYY
2022-04-24T17:26:40.247Z hapNodeJSClient Homebridge instance discovered homebridge with 3 accessories
2022-04-24T17:26:40.459Z hapNodeJSClient HAP Device discovered Wemo Plug 113
2022-04-24T17:26:40.524Z hapNodeJSClient HAP Discover failed Socket -> http://XXX.XXX.X.167:59365 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T17:27:00.126Z hapNodeJSClient Ready
2022-04-24T17:27:00.129Z alexaActions alexaDiscovery
2022-04-24T17:27:00.139Z alexaActions Cookie Object:  280
2022-04-24T17:27:00.143Z alexaActions Cookie Object:  115
2022-04-24T17:27:00.148Z alexaActions alexaDiscovery - returned 2 devices
2022-04-24T17:38:52.958Z alexaLocal offline
2022-04-24T17:39:57.960Z alexaLocal reconnect
2022-04-24T17:39:58.242Z alexaLocal connect command/ckristo/#
2022-04-24T17:41:40.122Z hapNodeJSClient Starting Homebridge instance discovery
2022-04-24T17:41:40.152Z hapNodeJSClient HAP Device discovered Homebridge XXXX YYYY
2022-04-24T17:41:40.250Z hapNodeJSClient Homebridge instance discovered homebridge with 3 accessories
2022-04-24T17:41:40.297Z hapNodeJSClient HAP Device discovered Weather Station
2022-04-24T17:41:40.333Z hapNodeJSClient HAP Device discovered Wemo Plug 113
2022-04-24T17:41:40.423Z hapNodeJSClient HAP Discover failed Socket -> http://XXX.XXX.X.167:59365 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T17:41:40.476Z hapNodeJSClient HAP Discover failed Weather Station -> http://XXX.XXX.X.173:5001 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T17:42:00.127Z hapNodeJSClient Ready
2022-04-24T17:42:00.130Z alexaActions alexaDiscovery
2022-04-24T17:42:00.141Z alexaActions Cookie Object:  280
2022-04-24T17:42:00.144Z alexaActions Cookie Object:  115
2022-04-24T17:42:00.148Z alexaActions alexaDiscovery - returned 2 devices
2022-04-24T17:56:40.122Z hapNodeJSClient Starting Homebridge instance discovery
2022-04-24T17:56:40.152Z hapNodeJSClient HAP Device discovered Homebridge XXXX YYYY
2022-04-24T17:56:40.259Z hapNodeJSClient HAP Device discovered Wemo Plug 113
2022-04-24T17:56:40.274Z hapNodeJSClient HAP Device discovered Weather Station
2022-04-24T17:56:40.343Z hapNodeJSClient Homebridge instance discovered homebridge with 3 accessories
2022-04-24T17:56:40.376Z hapNodeJSClient HAP Discover failed Socket -> http://XXX.XXX.X.167:59365 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T17:56:40.519Z hapNodeJSClient HAP Discover failed Weather Station -> http://XXX.XXX.X.173:5001 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T17:57:00.128Z hapNodeJSClient Ready
2022-04-24T17:57:00.131Z alexaActions alexaDiscovery
2022-04-24T17:57:00.141Z alexaActions Cookie Object:  280
2022-04-24T17:57:00.145Z alexaActions Cookie Object:  115
2022-04-24T17:57:00.149Z alexaActions alexaDiscovery - returned 2 devices
2022-04-24T17:59:58.250Z alexaLocal offline
2022-04-24T18:01:03.255Z alexaLocal reconnect
2022-04-24T18:01:03.509Z alexaLocal connect command/ckristo/#
2022-04-24T18:11:40.123Z hapNodeJSClient Starting Homebridge instance discovery
2022-04-24T18:11:40.205Z hapNodeJSClient HAP Device discovered Homebridge XXXX YYYY
2022-04-24T18:11:40.237Z hapNodeJSClient HAP Device discovered Wemo Plug 113
2022-04-24T18:11:40.331Z hapNodeJSClient HAP Device discovered Weather Station
2022-04-24T18:11:40.361Z hapNodeJSClient HAP Discover failed Socket -> http://XXX.XXX.X.167:59365 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T18:11:40.382Z hapNodeJSClient Homebridge instance discovered homebridge with 3 accessories
2022-04-24T18:11:40.672Z hapNodeJSClient HAP Discover failed Weather Station -> http://XXX.XXX.X.173:5001 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T18:12:00.170Z hapNodeJSClient Ready
2022-04-24T18:12:00.174Z alexaActions alexaDiscovery
2022-04-24T18:12:00.184Z alexaActions Cookie Object:  280
2022-04-24T18:12:00.187Z alexaActions Cookie Object:  115
2022-04-24T18:12:00.191Z alexaActions alexaDiscovery - returned 2 devices
2022-04-24T18:21:03.519Z alexaLocal offline
2022-04-24T18:22:08.525Z alexaLocal reconnect
2022-04-24T18:22:08.778Z alexaLocal connect command/ckristo/#
2022-04-24T18:26:40.124Z hapNodeJSClient Starting Homebridge instance discovery
2022-04-24T18:26:40.154Z hapNodeJSClient HAP Device discovered Homebridge XXXX YYYY
2022-04-24T18:26:40.336Z hapNodeJSClient HAP Device discovered Weather Station
2022-04-24T18:26:40.365Z hapNodeJSClient HAP Device discovered Wemo Plug 113
2022-04-24T18:26:40.471Z hapNodeJSClient Homebridge instance discovered homebridge with 3 accessories
2022-04-24T18:26:40.532Z hapNodeJSClient HAP Discover failed Socket -> http://XXX.XXX.X.167:59365 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T18:26:40.551Z hapNodeJSClient HAP Discover failed Weather Station -> http://XXX.XXX.X.173:5001 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T18:27:00.128Z hapNodeJSClient Ready
2022-04-24T18:27:00.131Z alexaActions alexaDiscovery
2022-04-24T18:27:00.157Z alexaActions Cookie Object:  280
2022-04-24T18:27:00.163Z alexaActions Cookie Object:  115
2022-04-24T18:27:00.168Z alexaActions alexaDiscovery - returned 2 devices
2022-04-24T18:41:40.126Z hapNodeJSClient Starting Homebridge instance discovery
2022-04-24T18:41:40.156Z hapNodeJSClient HAP Device discovered Homebridge XXXX YYYY
2022-04-24T18:41:40.250Z hapNodeJSClient HAP Device discovered Wemo Plug 113
2022-04-24T18:41:40.289Z hapNodeJSClient Homebridge instance discovered homebridge with 3 accessories
2022-04-24T18:41:40.324Z hapNodeJSClient HAP Device discovered Weather Station
2022-04-24T18:41:40.343Z hapNodeJSClient HAP Discover failed Socket -> http://XXX.XXX.X.167:59365 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T18:41:40.504Z hapNodeJSClient HAP Discover failed Weather Station -> http://XXX.XXX.X.173:5001 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T18:42:00.132Z hapNodeJSClient Ready
2022-04-24T18:42:00.135Z alexaActions alexaDiscovery
2022-04-24T18:42:00.145Z alexaActions Cookie Object:  280
2022-04-24T18:42:00.149Z alexaActions Cookie Object:  115
2022-04-24T18:42:00.153Z alexaActions alexaDiscovery - returned 2 devices
2022-04-24T18:42:08.786Z alexaLocal offline
2022-04-24T18:43:13.791Z alexaLocal reconnect
2022-04-24T18:43:14.193Z alexaLocal connect command/ckristo/#
2022-04-24T18:56:40.126Z hapNodeJSClient Starting Homebridge instance discovery
2022-04-24T18:56:40.163Z hapNodeJSClient HAP Device discovered Homebridge XXXX YYYY
2022-04-24T18:56:40.251Z hapNodeJSClient HAP Device discovered Wemo Plug 113
2022-04-24T18:56:40.266Z hapNodeJSClient HAP Device discovered Weather Station
2022-04-24T18:56:40.418Z hapNodeJSClient Homebridge instance discovered homebridge with 3 accessories
2022-04-24T18:56:40.432Z hapNodeJSClient HAP Discover failed Socket -> http://XXX.XXX.X.167:59365 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T18:56:41.232Z hapNodeJSClient HAP Discover failed Weather Station -> http://XXX.XXX.X.173:5001 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T18:57:00.135Z hapNodeJSClient Ready
2022-04-24T18:57:00.138Z alexaActions alexaDiscovery
2022-04-24T18:57:00.150Z alexaActions Cookie Object:  280
2022-04-24T18:57:00.154Z alexaActions Cookie Object:  115
2022-04-24T18:57:00.158Z alexaActions alexaDiscovery - returned 2 devices
2022-04-24T19:03:14.206Z alexaLocal offline
2022-04-24T19:04:19.208Z alexaLocal reconnect
[24/04/2022, 21:04:19] [Alexa] ERROR: ( homebridge-alexa) You have an issue with your installation, please review the README.
2022-04-24T19:04:19.474Z alexaLocal connect command/ckristo/#
2022-04-24T19:11:40.132Z hapNodeJSClient Starting Homebridge instance discovery
2022-04-24T19:11:40.163Z hapNodeJSClient HAP Device discovered Homebridge XXXX YYYY
2022-04-24T19:11:40.223Z hapNodeJSClient HAP Device discovered Weather Station
2022-04-24T19:11:40.238Z hapNodeJSClient HAP Device discovered Wemo Plug 113
2022-04-24T19:11:40.325Z hapNodeJSClient Homebridge instance discovered homebridge with 3 accessories
2022-04-24T19:11:40.359Z hapNodeJSClient HAP Discover failed Socket -> http://XXX.XXX.X.167:59365 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T19:11:41.399Z hapNodeJSClient HAP Discover failed Weather Station -> http://XXX.XXX.X.173:5001 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T19:12:00.138Z hapNodeJSClient Ready
2022-04-24T19:12:00.141Z alexaActions alexaDiscovery
2022-04-24T19:12:00.151Z alexaActions Cookie Object:  280
2022-04-24T19:12:00.155Z alexaActions Cookie Object:  115
2022-04-24T19:12:00.159Z alexaActions alexaDiscovery - returned 2 devices
2022-04-24T19:24:19.483Z alexaLocal offline
2022-04-24T19:25:24.489Z alexaLocal reconnect
2022-04-24T19:25:24.743Z alexaLocal connect command/ckristo/#
2022-04-24T19:26:40.133Z hapNodeJSClient Starting Homebridge instance discovery
2022-04-24T19:26:40.877Z hapNodeJSClient HAP Device discovered Wemo Plug 113
2022-04-24T19:26:40.907Z hapNodeJSClient HAP Device discovered Weather Station
2022-04-24T19:26:40.962Z hapNodeJSClient HAP Device discovered Homebridge XXXX YYYY
2022-04-24T19:26:41.226Z hapNodeJSClient HAP Discover failed Socket -> http://XXX.XXX.X.167:59365 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T19:26:41.249Z hapNodeJSClient Homebridge instance discovered homebridge with 3 accessories
2022-04-24T19:26:41.506Z hapNodeJSClient HAP Discover failed Weather Station -> http://XXX.XXX.X.173:5001 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T19:27:00.139Z hapNodeJSClient Ready
2022-04-24T19:27:00.143Z alexaActions alexaDiscovery
2022-04-24T19:27:00.153Z alexaActions Cookie Object:  280
2022-04-24T19:27:00.157Z alexaActions Cookie Object:  115
2022-04-24T19:27:00.161Z alexaActions alexaDiscovery - returned 2 devices
2022-04-24T19:41:40.134Z hapNodeJSClient Starting Homebridge instance discovery
2022-04-24T19:41:40.168Z hapNodeJSClient HAP Device discovered Homebridge XXXX YYYY
2022-04-24T19:41:40.275Z hapNodeJSClient Homebridge instance discovered homebridge with 3 accessories
2022-04-24T19:41:40.286Z hapNodeJSClient HAP Device discovered Wemo Plug 113
2022-04-24T19:41:40.367Z hapNodeJSClient HAP Device discovered Weather Station
2022-04-24T19:41:40.396Z hapNodeJSClient HAP Discover failed Socket -> http://XXX.XXX.X.167:59365 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T19:41:41.214Z hapNodeJSClient HAP Discover failed Weather Station -> http://XXX.XXX.X.173:5001 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T19:42:00.164Z hapNodeJSClient Ready
2022-04-24T19:42:00.168Z alexaActions alexaDiscovery
2022-04-24T19:42:00.189Z alexaActions Cookie Object:  280
2022-04-24T19:42:00.193Z alexaActions Cookie Object:  115
2022-04-24T19:42:00.198Z alexaActions alexaDiscovery - returned 2 devices
2022-04-24T19:45:24.751Z alexaLocal offline
2022-04-24T19:46:29.753Z alexaLocal reconnect
2022-04-24T19:46:30.006Z alexaLocal connect command/ckristo/#
2022-04-24T19:56:40.134Z hapNodeJSClient Starting Homebridge instance discovery
2022-04-24T19:56:40.163Z hapNodeJSClient HAP Device discovered Homebridge XXXX YYYY
2022-04-24T19:56:40.260Z hapNodeJSClient HAP Device discovered Wemo Plug 113
2022-04-24T19:56:40.275Z hapNodeJSClient HAP Device discovered Weather Station
2022-04-24T19:56:40.338Z hapNodeJSClient Homebridge instance discovered homebridge with 3 accessories
2022-04-24T19:56:40.372Z hapNodeJSClient HAP Discover failed Socket -> http://XXX.XXX.X.167:59365 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T19:56:40.540Z hapNodeJSClient HAP Discover failed Weather Station -> http://XXX.XXX.X.173:5001 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T19:57:00.138Z hapNodeJSClient Ready
2022-04-24T19:57:00.142Z alexaActions alexaDiscovery
2022-04-24T19:57:00.163Z alexaActions Cookie Object:  280
2022-04-24T19:57:00.165Z alexaActions Cookie Object:  115
2022-04-24T19:57:00.168Z alexaActions alexaDiscovery - returned 2 devices
2022-04-24T20:06:30.015Z alexaLocal offline
2022-04-24T20:07:35.020Z alexaLocal reconnect
2022-04-24T20:07:35.291Z alexaLocal connect command/ckristo/#
2022-04-24T20:11:40.153Z hapNodeJSClient Starting Homebridge instance discovery
2022-04-24T20:11:40.312Z hapNodeJSClient HAP Device discovered Homebridge XXXX YYYY
2022-04-24T20:11:40.395Z hapNodeJSClient HAP Device discovered Wemo Plug 113
2022-04-24T20:11:40.731Z hapNodeJSClient HAP Discover failed Socket -> http://XXX.XXX.X.167:59365 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T20:11:41.098Z hapNodeJSClient Homebridge instance discovered homebridge with 3 accessories
2022-04-24T20:12:00.167Z hapNodeJSClient Ready
2022-04-24T20:12:00.171Z alexaActions alexaDiscovery
2022-04-24T20:12:00.182Z alexaActions Cookie Object:  280
2022-04-24T20:12:00.185Z alexaActions Cookie Object:  115
2022-04-24T20:12:00.189Z alexaActions alexaDiscovery - returned 2 devices
2022-04-24T20:26:40.154Z hapNodeJSClient Starting Homebridge instance discovery
2022-04-24T20:26:40.183Z hapNodeJSClient HAP Device discovered Homebridge XXXX YYYY
2022-04-24T20:26:40.277Z hapNodeJSClient HAP Device discovered Weather Station
2022-04-24T20:26:40.315Z hapNodeJSClient Homebridge instance discovered homebridge with 3 accessories
2022-04-24T20:26:40.401Z hapNodeJSClient HAP Discover failed Weather Station -> http://XXX.XXX.X.173:5001 invalid PIN or homebridge is not running in insecure mode with -I
2022-04-24T20:27:00.159Z hapNodeJSClient Ready
2022-04-24T20:27:00.162Z alexaActions alexaDiscovery
2022-04-24T20:27:00.172Z alexaActions Cookie Object:  280
2022-04-24T20:27:00.175Z alexaActions Cookie Object:  115
2022-04-24T20:27:00.180Z alexaActions alexaDiscovery - returned 2 devices
2022-04-24T20:27:35.300Z alexaLocal offline
2022-04-24T20:28:40.305Z alexaLocal reconnect
2022-04-24T20:28:40.549Z alexaLocal connect command/ckristo/#

EDIT: changed keepalive config setting to 5 and monitor if this changes anything...

NorthernMan54 commented 2 years ago

If your not successful with 5, then try 1 minute

And for your question what does "Last plug-in response" indicate? Is this communication from the plugin to the Alexa skill?

You are correct, this is the last communication from the plugin to the Alexa skill. It is set to go RED when an Alexa request isn't responded to.

ckristo commented 2 years ago

Thx for the prompt answer. Could this indicate some connectivity issue on my end? The strange thing: it seems Alexa could communicate with the plugin once successfully (shortly after I set up everything - I was able to see the device in the Alex app and control it via Alexa). Since then, no update - "Last plug-in response" is "Sat Apr 23 2022 08:33:59 GMT" - unchanged since more than a day now.

NorthernMan54 commented 2 years ago

It could be something local. The plugin needs to maintain a constant connection to the Homebridge.ca server in order to receive Alexa messages. If you have a network setup that blocks the outbound connection from the plugin to the homebridge.ca server, it would have this issue.

ckristo commented 2 years ago

I see, I will try to check what is going on at network level (via tcpdump) tomorrow.

EDIT: The plugin communicates with www.homebridge.ca (54.198.155.191, 34.194.207.130)? EDIT2: which port?

NorthernMan54 commented 2 years ago

The IP address is alexa.homebridge.ca on port 1883 ( MQTT )

Another connection option is the current beta release, which uses websockets instead of mqtt.

ckristo commented 2 years ago

Plugin communication with alexa.homebridge.ca seems to work fine for me now, I guess changing the Keepalive setting to 10 finally made the difference. In the network trace I see communication happening to alexa.homebridge.ca via MQTT.

earldgrayjr commented 2 years ago

I am having the same issue. It worked originally but now Alexa responds with having difficulty finding null. The website shows a bad last response and "Last plugin response | Sun May 01 2022 22:34:51 GMT" I don't think anything changed on my end other than setting up rooms on hoobs. I did try unlinking and re-linking the skill. No joy there. Not as smart or experienced as others here. Would really appreciate the help. Got these error messages: 5/2/2022, 10:56:21 AMWARNINGplugin site unavailable 5/2/2022, 10:57:21 AMAlexa BridgeAlexaERROR: ( homebridge-alexa) You have an issue with your installation, please review the README.

NorthernMan54 commented 2 years ago

@earldgrayjr - 5/2/2022, 10:57:21 AMAlexa BridgeAlexaERROR: ( homebridge-alexa) You have an issue with your installation, please review the README. means that no Homebridge devices were found during discovery, can you enable debug mode in the config and share the log .

Unrender commented 2 years ago

Hi. I have Last plugin response error since Sat Jun 11 2022 07:11:49 GMT. Yesterday, I make a subscription but the error still here. I've tried to turn the Cloud Server Connection Keepalive to 1 but nothing happened.

In the Homebridge status, I have this : [2022-6-19 14:36:40] [Homebridge UI] [homebridge-alexa] Failed to check registry.npmjs.org for updates: "timeout of 10000ms exceeded"

NorthernMan54 commented 2 years ago

That message is not from the Alexa plugin but the homebridge UI.

Is your account dashboard all green?

On Jun 19, 2022, at 8:39 AM, Unrender @.***> wrote:

 Hi. I have Last plugin response error since Sat Jun 11 2022 07:11:49 GMT. Yesterday, I make a subscription but the error still here. I've tried to turn the Cloud Server Connection Keepalive to 1 but nothing happened.

In the Homebridge status, I have this : [2022-6-19 14:36:40] [Homebridge UI] [homebridge-alexa] Failed to check registry.npmjs.org for updates: "timeout of 10000ms exceeded"

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

Unrender commented 2 years ago

No, the Last Plugin response is red.

Capture d’écran 2022-06-19 à 18 54 20
NorthernMan54 commented 2 years ago

Okay, for some reason the plugin is not connecting to the cloud server ( the red circle ). This type of issue should have something in the plugin logs. It could also be the cloud server DDOS protection, which is tripped if the plugin/homebridge restarts too many times in a row. To resolve, shutdown your RPI for a few minutes, and it should reconnect.

Unrender commented 2 years ago

Okay. I've shutdown my RPI few minutes but the red circle is always here. Have you an other idea for me ? Thanks :)

NorthernMan54 commented 2 years ago

Anything in the plugin logs, it should be pretty verbose about a connection issue.

On Jun 20, 2022, at 12:19 PM, Unrender @.***> wrote:

 Okay. I've shutdown my RPI few minutes but the red circle is always here. Have you an other idea for me ? Thanks :)

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

Unrender commented 2 years ago

Ok no problem. Could you just tell me where I can find the files you need ?

NorthernMan54 commented 2 years ago

Where the logs are depends on your setup, typically they are in /var/log/syslog

Unrender commented 2 years ago

Ok. I'm going to check that.

Unrender commented 2 years ago

syslog.zip

Here is the file.

NorthernMan54 commented 2 years ago

Tks

I’m not in a location where I can open this for a few hours

Unrender commented 2 years ago

Oh yes no problem. It's already nice to help me.

NorthernMan54 commented 2 years ago

Looking at that log, and it doesn't have the Homebridge log in it, but says that the homebridge log is here

Jun 20 15:47:41 raspberrypi hb-service.js[793]: #033[37m[2022-6-20 15:47:41]#033[0m #033[36m[HB Supervisor]#033[0m Logging to /var/lib/homebridge/homebridge.log
NorthernMan54 commented 2 years ago

Also I looked at some of the other messages in that log and noticed that pihole was mentioned, are you running pihole and is it possibly blocking access to the cloud backend ?

Unrender commented 2 years ago

So, here is the homebridge log. homebridge.log

Yes I'm running pihole. But it has been running for about 2 years and before June 11, it worked perfectly. Not sure I understand that " is it possibly blocking access to the cloud backend "... My english is not very good.

I've tried to disable pihole for a while but the red circle remains.

NorthernMan54 commented 2 years ago

Looking at the log, I see this repeated

2022-06-21T08:46:25.270Z hapNodeJSClient Homebridge instance discovered homebridge with 18 accessories 2022-06-21T08:46:43.086Z alexaLocal reconnect [2022-6-21 10:46:43] [Alexa] ERROR: ( homebridge-alexa) You have an issue with your installation, please review the README.

which indicates a connectivity issue between the plugin and the cloud servers

can you share your external IP address so I can check if the DDOS is tripping against your IP

Unrender commented 2 years ago

Of course. unrender.ddns.net

NorthernMan54 commented 2 years ago

Well its not the DDOS service, as your IP address is not in the log files.

I'm kinda stumped as something is blocking the plugin from connecting to the servers.

I presume that you have already tried restarting homebridge, and it made no difference?

And you disabled pihole, so it isn't blocking anything

And another option, is to install the current beta ( If you look at previous releases in the UI it is listed ) as it uses a different network transport which may work around the issue.

Unrender commented 2 years ago

Yes, restarting homebridge, restarting the RPI, and no difference. I've tried to install the beta but I've this error : Http failure response for http://192.168.x.x:8581/api/plugins/lookup/homebridge/versions: 404 Not Found

So I'm looking to resolve that and I come back here...

WinfriedO commented 2 years ago

Seems that we now need to pay 2$ per month for the Cloud Get Error: Hombridge Alexa Account is not active:api 143

Unrender commented 2 years ago

Seems that we now need to pay 2$ per month for the Cloud Get Error: Hombridge Alexa Account is not active:api 143

Yes, indeed.

NorthernMan54 commented 2 years ago

@Unrender If you look at the PiHole Dashboard does it show any of the homebridge.ca domains ? The plugin uses alexa.homebridge.ca.

In regards to this error

Http failure response for http://192.168.x.x:8581/api/plugins/lookup/homebridge/versions: 404 Not Found

I'm not really familiar with the homebridge UI, so can't comment.

Unrender commented 2 years ago

@Unrender If you look at the PiHole Dashboard does it show any of the homebridge.ca domains ? The plugin uses alexa.homebridge.ca.

In regards to this error

Http failure response for http://192.168.x.x:8581/api/plugins/lookup/homebridge/versions: 404 Not Found

I'm not really familiar with the homebridge UI, so can't comment.

No, I have already check that. But I have a problem with the DNS. If I connect to the Pi using SSH, and then I ping an IP on internet, it's okay. But if I ping www.google.fr for example, I can't. There is an error with DNS. For the moment, I can't solve it. I'll try to uninstall PiHole.

NorthernMan54 commented 2 years ago

@Unrender As your continuing to have issues, we have refunded your first subscription payment.

Unrender commented 2 years ago

@NorthernMan54 Oh you shouldn't. I can't find where the problem is coming from. I formatted my SD card and am trying to reinstall everything. As soon as it's good, I will resume the subscription. Thanks again !

Unrender commented 2 years ago

@NorthernMan54 With a brand new installation, everything is finally back to normal and everything works as before. The only annoying point is that I really don't know why I had this problem. But hey, it's settled. Thanks again for your help and sorry for the inconvenience!!!

NorthernMan54 commented 2 years ago

Glad to hear you have this sorted.