Closed schweppy closed 2 years ago
Did you see this issue and the workaround 'keep alive' setting that is available with the current beta release ?
https://github.com/NorthernMan54/homebridge-alexa/issues/479
Sorry I didn’t! Will play with those settings and report back! Many thanks
updated to 0.5.55, looks better
@NorthernMan54 I experience something quite similar now with 0.5.55. After a recent reboot there is one device where I get "Device is unresponsive". It's a Philips Hue Light configured in fhem. Switching on/off and dimming via Siri and homebridge works fine, though. Any thoughts?
Log entry when trying to switch on via Alexa:
[2022-1-11 11:20:33] [Alexa] PowerController TurnOn 52:54:00:77:82:E9 { characteristics: [ { aid: 207, iid: 10, status: -70410 } ] } null
Log entry when trying to switch on via Siri:
2022-1-11 11:21:12] [FHEM] HUEDevice6: executing set cmd for On with value true [2022-1-11 11:21:12] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=set%20HUEDevice6%20on&XHR=1 2022-01-11 11:21:14 caching: HUEDevice6-onoff: 1
@aski71 have you tried asking Alexa to discover devices again?
Yes. Alexa does not find any new devices.
But does it now work?
Ok. You got me. 😂 As it did not find anything and it did not look any different in the Alexa App UI, that was the one thing I didn't try. Yes. It works again.
Asking Alexa to discover devices again refreshes the device cache on the Alexa side and fixes a broken device mapping like this.
Hello
I regularly have issues surrounding the following found in the troubleshooting wiki - “After restarting homebridge Alexa can't find devices and needs to discover them again. Or you have duplicate devices in Alexa”
Usually I have to either restart homebridge or rediscover devices in Alexa app several times as all devices show as unavailable.
As per the wiki, I have a port number set for homebridge. Is there anything else I can try so that I don’t get a regularly annoyed wife 😂??
Many thanks