search

bwssytems / ha-bridge

Home automation bridge that emulates a Philips Hue light system and can control other systems such as a Vera, Harmony Hub, Nest, MiLight bulbs or any other system that has an http/https/tcp/udp interface. This is a compact impl to run on small format computers. This is impl started from this project https://github.com/armzilla/amazon-echo-ha-bridge.
Apache License 2.0
1.45k stars 198 forks source link

Device not responding #1278

Open smartypantsuk opened 3 years ago

smartypantsuk commented 3 years ago

Simply, I have two devices that Alexa complains aren't responding when I tried to turn them on. The devices turn on anyway, but always get the complaint. Turning off works fine.

I followed the advice in the same issue here #1213, which included turning on or off a couple of options such as do not update device state etc, but none have worked. I restarted the bridge after changes.

I have tried: Removing ALL devices from Alexa app, wait 1 hour. Change numbering seed from 100 to 200 in HA-Bridge, Save Press the re-number button in HA-Bridge Save Turn on ALL Alexa devices, then wait 1 hour. Scan for new devices in Alexa App, Finds all devices no problem.

Same two devices still complain about not responding.

Any ideas?

Thanks

audiofreak9 commented 3 years ago

What are these two devices? Do they have a longer type script to run or the like that would delay the HTTP success message from HA-Bridge?

smartypantsuk commented 3 years ago

Ones a fibaro socket outlet and ones a fibaro switch/relay. I've had them working without issue before. I have a feeling this is to do with the unique ID or similar, or perhaps not.

This is the simple script which works in other identical devices.

http://x.x.x.x/JSON?request=controldevicebyvalue&ref=1514&value=255

audiofreak9 commented 3 years ago

Try replacing the ON or OFF with something else and see if the device(s) still do not respond...

smartypantsuk commented 3 years ago

Ok, I have this working and the fix is strange but simple, at least for me.

I tried removing the problem devices from the alexa app, changing the unique IDs manually in the bridge database then re-scanning for devices.

But this didn't fix anything and Alexa still complained when trying to turn them on.

The fix was to go into the Alexa app and manually turn the problem devices on and off. After I did this the devices respond properly via voice command.

Bizarre.

@bwssytems ?

DukyNuky commented 3 years ago

hi,

i have the same problem... and the same "fix".. turning on/off in app will fix it.. all devices are fhem devices controlled through url.

RobotNot commented 1 year ago

In my case, turning on/off in the Alexa app is just a temporary fix for Alexa seeing the device as online again. But the problem recurs once the On command is given again. This only happens for longer command sequences that take 5 seconds or more before the HTTP success message is received by HA-Bridge. It's a timeout issue. I've provided more details over in #1213.