Device not responding

[lucaesse]

Hi, since I updated to v0.5.42 alexa says "device not responding". If i restart homebridge it works for a while then I got the same issue. Everything works fine in the home app, I tried to downgrade "Homebridge Alexa" but I got the same issue. I tried also disabling the skill and configuring every device from zero... The same! Can you help me please?

[NorthernMan54]

@WinfriedO Take a look at the comments to @Fsalvanha above, by tuning the keeplive down to 120 he was available to resolve the issue.

[WinfriedO]

@WinfriedO Take a look at the comments to @Fsalvanha above, by tuning the keeplive down to 120 he was available to resolve the issue.

currently running for 1.5 hours without loosing connection, am now away for some hours, will see if it still works when I come back. BTW got vulnerabilities after installing 0.5.50:

npm audit report

axios <=0.21.1 Severity: high Incorrect Comparison in axios - https://github.com/advisories/GHSA-cph5-m8f7-6c5x fix available via npm audit fix --force Will install homebridge-alexa@0.5.32, which is a breaking change node_modules/@oznu/hap-client/node_modules/axios @oznu/hap-client >=1.2.0 Depends on vulnerable versions of axios node_modules/@oznu/hap-client homebridge-alexa >=0.5.33 Depends on vulnerable versions of @oznu/hap-client node_modules/homebridge-alexa

3 high severity vulnerabilities

[WinfriedO]

24 hours. No Problem so far.

[lucaesse]

@WinfriedO Take a look at the comments to @Fsalvanha above, by tuning the keeplive down to 120 he was available to resolve the issue.

Hi @NorthernMan54, I tried to update to v0.5.50 with keeplive to 120 and it works! I've tested on the last 3 days!

[Fsalvanha]

@WinfriedO Take a look at the comments to @Fsalvanha above, by tuning the keeplive down to 120 he was available to resolve the issue.

Hi @NorthernMan54, I tried to update to v0.5.50 with keeplive to 120 and it works! I've tested on the last 3 days!

Same, here I have noticed some issues, but looks more my network than the plug in.

[Fsalvanha]

I think I said too soon. The issue is back. I have reduced the keep alive to 60 and no luck.

[NorthernMan54]

If it is not stable at 60, then you have something else going on and not triggered by this issue. If your network is not stable, then it can trigger this condition as well

[WinfriedO]

still running well for me

[diablolot]

I had the same problem with connection lost, actual v0.5.51 beta everthing okay. @NorthernMan54 Thanks!

Update: Has to change to keep alive to 60 to get it working.

[nixmeer]

I have had the timeout set to 300 for the past weeks. Most of the times, it worked properly, just in about 10 % of the cases, the blue and green lights of the echo dots and the missing response indicated Alexa having a problem to connect. It solved over time, so no restart was required. I have now set it to 60 to see, if there is any further improvement.

[nixmeer]

With timeout set to 60, Alexa could not connect to the devices.

it worked again about 5 minutes later when I asked Alexa to turn off another light

[NorthernMan54]

@nixmeer Is this resolved?

[nixmeer]

I'm sorry I didn't report back. It didn't work at the beginning but after installing the lasted 0.5.51, it just worked. My current settings are 1 min for Cloud Server Connection Keepalive and 60 for Refresh Interval

Best Jan

[NorthernMan54]

Awesome

[nixmeer]

Yes! Thanks a lot!

The only drawback is that Alexa likes my girlfriends voice better than mine... oftentimes she does not listen to me or misunderstands my request :D

[NorthernMan54]

Lol, I have the opposite issue

On Dec 8, 2021, at 7:09 PM, Jan Theiss @.***> wrote:

Yes! Thanks a lot!

The only drawback is that Alexa likes my girlfriends voice better than mine... oftentimes she does not listen to me or misunderstands my request

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/NorthernMan54/homebridge-alexa/issues/459#issuecomment-989329239, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEXEFGETUJUD2HMBPTM4M5TUP7XT7ANCNFSM5C63PPJA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[hAMMERlized]

@nixmeer Hey Jan,

I have the same Warning with both Philips Hue motion sensors. There is the Temperatur sensor and motion sensor ported into the alexa app, both named "Küche - BWM". I've renamed both sensors in the alexa app into "Küche - Temperatur" and "Küche - Bewegung.

I also did this with the other Hue Motion Sensor. But the warning still exist and while putting the refresh rate to 60, this warning keeps spamming my Homebridge protocol and log every minute with this. Pretty annoying if you are looking for another problem concerning a other plugin :/

So can you tell me if you were able to solve that "duplicate device" name warning and if yes how exactly did you do that? I would appreciate a "step by step" instruction for dummies like me 😄 .

Thanks in advance.

[nixmeer]

Hello @hAMMERlized No, I couldn’t resolve the issue yet.

[hAMMERlized]

So you are getting that warning every 60 seconds in your protocol and log? Is it worth getting that spam warnings concerning the "no device response" issue that we are talking about here?

I mean is it a benefit getting that warnings when at least the devices are working now with the latest beta and the 60 seconds interval?