I’m using a tuya lamp, which is configured as alexa device. In openhab im using this as a thing connected over the amazonechocontrol binding. An i created a item (type switch) with a link to this thing.
This is not working correctly. When i turn the light on in Main UI, the light turns on. But the state goes back to “off”. And after that, i cannot turn the light of.
event.log
[INFO ] [openhab.event.ItemCommandEvent ] - Item 'lichtNoahDecke' received command ON
2024-10-24 20:15:43.663 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'lichtNoahDecke' predicted to become OFF
When i use the alexa app, everything is working. I have connected another thing (“amazon smart plug”). Here everything ist working fine (in openHab).
I can’t answer why, but it looks like autoupdate is predicting the wrong new state of the Item based on the command. Turn autoupdate off for that Item. I beleive the amazoncontrol binding will update the Item anyway so autoupdate isn’t needed.
Navigate to Items → lichtNoahDecke → Add Metadata → Autoupdate and toggle it off.
OK, well that is showing the light is ON. An OFF toggle appears as gray with the circle on the left. So you’ve turned ON the light and the UI is showing that the light is ON. I don’t understand the problem now.
I’ve turned the debug log on. Now there appears the following log message:
2024-10-25 15:05:49.909 [DEBUG] [mazonechocontrol.internal.Connection] - Requested {"stateRequests":[{"entityId":"AAA_SonarCloudService_ead20187-0b20-4a5f-80d8-xxx","entityType":"APPLIANCE"},{"entityId":"AAA_SonarCloudService_00PgPmsFEqXWRcScVLNBUz6qevXvV_yyy","entityType":"APPLIANCE"}]} and received {"deviceStates":[{"entity":{"entityId":"AAA_SonarCloudService_00PgPmsFEqXWRcScVLNBUz6qevXvV_zzz","entityType":""},"capabilityStates":["{\"namespace\":\"Alexa.PowerController\",\"name\":\"powerState\",\"value\":\"OFF\",\"timeOfSample\":\"2024-10-22T15:53:46Z\",\"uncertaintyInMilliseconds\":0,\"deepQuery\":false,\"timeOfStateChange\":\"2024-10-22T15:53:46Z\"}"],"error":null}],"errors":[{"entity":{"entityId":"AAA_SonarCloudService_ead20187-0b20-4a5f-80d8-yyy","entityType":""},"code":"ENDPOINT_UNREACHABLE","message":null,"data":null}]}
And i forget to mention, that the status of the thing ist “UNKNOWN”.
If the status of the Thing is UNKNOWN then you need to focus on that. If the Thing isn’t healthy there isn’t anything else you can do from the Items nor UI widgets to make it work.
That error message says “ENDPOINT_UNREACHABLE”. Given this is comming from the Connection class I’m going to assume that the prooblem is your OH cannot reach the Amazon servers for some reason.
so your lamp is connected to the tuya-cloud and then to the Amazon-cloud? (really cloudy? or do you use the tuya binding?)
Amazon is a little obscure cause they keep on changing stuff which breaks working solutions without any notice.
I would delete the lamp in the Alexa app and check if you can rediscover it.
I configured my lamp in the app “tuya smart” and there i connected it to alexa. After that it was listed in the alexa app. In openHab i connected it with the “alexa binding”.
Personally I would avoid those double-cloud connections: This doubles the risk of failures and the delays too.
As an alternative there is a tuya-binding which enables local control of your tuya devices.
Unless and until the Thing is ONLINE this lamp is never going to work correctly.