Creating a timer to restart the plugin every 3 hours has pretty much solved my problem. Very rarely do I get the dreaded double bong sound when trying to voice-control a light.
Is it possible to create a timer to restart the Indgo server?
Creating a timer to restart the plugin every 3 hours has pretty much solved my problem. Very rarely do I get the dreaded double bong sound when trying to voice-control a light.
khall51 wrote:I am having similar issues, usually a couple of times per week. Everything will work fine and then I get "xxx device is not responding". It does it to all devices I have connected. When I open indigo after the problem happens, I always find that discovery is turned off even thought I have it set to stay on continuously. The only fix is to reload the plug in and then ask alexa to rediscover devices. Event log shows no sign of what is triggering the issue.
I have a basic wifi network, 1 bridge set up with 18 devices, 2 echos in the house. Problem started when we went to version 3. V2 was very reliable so I am not sure what changed.
Here is the error code from the log when my request fails.
Alexa-Hue Bridge Error Unable to process Alexa request on 'Alexa' : Alexa key 34898745 is not a valid hash key for 'Breakfast Lights'
The log entries for the other devices I try are all the same as this one but with a different key number.
My skill level is very basic and I don't know how to code or program but I can follow directions pretty well. Any recommendations for trouble shooting?
Thanks.
Ken
... Now the next important part, use the Alexa Desktop (not iOS App) to forget all devices and then do a discovery which is best done by asking Alexa to 'Discover Devices'. ...
khall51 wrote:Yes sir, I did the migration. I did the forget all devices using my android phone. I don't have a desktop. Was android okay?
Users browsing this forum: No registered users and 3 guests