-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alexa Tasmota Hue Bug (Server doesn't respond) #21747
Comments
This code hasn't changed in a while. Can you please share the logs when the problem happens? The problem you describe could simply be a network reachability problem unrelated to the numbering of relays. |
I don't think so, RSSI is 56% and its only faulty with this Relay#3. I'm pretty sure its a problem connected to shutter settings. As you can see in the logs, when switching Relay3 in alexa app, some strange interpretation of the incoming command in tasmota happens: 16:18:00.423 HTP: Hue POST args ({"on":false}) Why are there even shutter states/settings triggered. Doesn't make sense. Update: I redefined relay 3 as 6 (friendly name 7) and defined another unused GPIO as Relay 3 (hidden $friendly name 3) and now it works like a charm. So it is definitly a bug connected to shutter setting so80. |
It's not so easy to reproduce. Can you share logs when it works (after pairing if I understand well)? And the corresponding log when it does not work anymore? And please include the full log: the log above lacks the full URL with the Hue identifier |
Btw. " RSSI is 56%" is bad, especially when using UDP. UDP is send and forget. No check if successful. |
@jtauscher Are you going to provide the logs asked for? |
All under the assumption that we have a normal shutter relay1 is up and relay2 is down. no stepper motors, no servos and so on. There is an option to LOCK the shutter. this uses relay3 if defined. I did not get it why there is an INVERT. But let me check. I will update the documentation regarding the lock. This was introduced about a year ago and "highjack" the relay after up/down to lock it. This is made to prevent ALEXA from operating the shutter in some situations. In my case ALEXA conection is done through HomeAssistant not HUE |
Closing since no feedback. Feel free to ping when the logs needed and asked for are provided |
Hi guys,
I have latest Tasmota with Hue enabled. This Tasmota drives a shutter (Relay 1&2) and four other devices. Shutter of course doesnt work with Alexa App but all other devices work, except for device #3 "friendly name 3".
Alexa detects all 6 devices, or if I add $ to friendly names 1&2, shutter relays 1&2 are hidden. Problem is, if I toggle device 3 (Light) in Alexa app, Tasmota console tells me this:
device 4-6 output would be similar to:
I remember it worked fine after resetting everything but after a day or so Alexa app tells me that "server doesn't respond"
Is there a bug in numbering relay 1 to 6? Because 1 and 2 are somehow "one shutter unit" ?
selection of SetOptions:
SO15 1
SO32 40
SO33 5
SO34 200
SO35 0
SO36 1
SO37 0
SO38 6
SO39 0
SO40 0
SO41 60
SO42 90
SO43 10
SO44 25
SO45 40
SO57 1
SO80 1 (-> Shutter)
SO91 1
SO114 1 (detach switches -> sensors for HA)
SO128 1
The text was updated successfully, but these errors were encountered: