I’m on openHAB 4.3.5 and I have quite a lot of items with Amazon Alexa Meta data. All these items appear in the Alexa app. But quite a short while ago all these items show a red dot with “Gerät reagiert nicht” (~= no device reaction) in the devices list. Although, when I for example switch on a light it works. But a few seconds later the device status is set to off in the Alexa app though the device itself is still turned on. To switch off the device in the Alexa app I have to turn it on and then turn it off. Voice commands via Echo devices work as expected but the device state is broken.
I recently worked over my reverse proxy settings and secured everything as good as possible. So I guess I have a problem with rights or ports. I searched a lot but could not find any helpful information which could lead me on the right track.
Can someone point out the basic communication between Alexa and openHAB (local, remote) and what ports have to be open?
Have a look into your reverse proxy log files.
If device can be turned on/off then the right port is used and it in general works.
Port that’s used is 443 as https/SSL is used.
Access might be done from different AWS servers.
As long as the access is not already blocked by a firewall ( also that can have a log file ) you should see granted/denied access in the reverse proxy log fle.
Looks like there is no problem with the reverse proxy. I changed the log level to “debug” for the openHAB cloud binding.
To give an example:
I have two light bulbs, both controlled by zigbee2mqtt, both connected to openHAB via mqtt. Both can be controlled by openHAB (UI and app), both show item changes when controlled by zigbee2mqtt or Alexa app.
The first light bulb looks normal in the Alexa app. Item changes (on/off, brightness, color temp) work as expected. External changes are reflected in the Alexa app.
The second light bulb shows “Gerät reagiert nicht” in the Alexa app but I can switch on the light with the Alexa app or change brightnes. A few seconds later the Alexa app shows “off” again though the light is still “on”. I can turn off the light with Alexa by turning it “on” and “off” while the app still shows “on”. External changes to the bulb are not reflected in Alexa.
I checked the settings of the bulbs in openHAB and did not find any differences in the config. The log file with log level “debug” for openHAB cloud shows the same requests for both bulbs and no errors. So the Alexa skill “openHAB” seems to work as expected in terms of controlling devices but not in terms of showing item states. And it is not only limited to zigbee devices. Some of my homematic devices (rollershutters) have the same problem.
I am thinking about removing all items from the alexa app and discover them again. But I fear that the still working items might be affected too after rediscover.
My bulbs are organized in groups with their corresponding items (power, brightness, color_temp) and a color item if it is a color bulb. Some of the bulb groups had “NULL” as color value because the color had never been changed due to the fact that only the color_temp is used.
After changing the color of the item, removing it from Alexa and rediscover the group is working again. Several other items in the Alexa devices list recovered from the state “not reacting” too.
Looks like “NULL” has an impact on how items are detected.
