Alexa sometimes responding 'Device isn't responding' despite executing action

Hey folks,

I just started using openHAB, version 3.3.0 / openHABian v1.7.4b on a Raspberry Pi 4 (2GB), and am having problem with the Alexa skill. I’m trying to get rid of my Hue bridge so I started connecting my lights using zigbee2mqtt with groups being handled by zigbee2mqtt. One such group is “Wohnzimmer_Licht”.

Most of the time commands using Alexa work fine but sometimes (~10%) the command is executed however after a few seconds Alexa seems to time out and responds with “$Device isn’t responding”. If I set the log level to debug I can see that there is a large delay between executing the action and PUSH_ACTIVITY. In this example I instructed Alexa to change the light level of “Wohnzimmer Licht” to 30% which happened immediately.

17:54:59.461 [DEBUG] [ocontrol.internal.WebSocketConnection] - Message received: {"command":"PUSH_VOLUME_CHANGE","payload":"<removed>","timeStamp":1667753699397}
17:54:59.468 [DEBUG] [ocontrol.internal.WebSocketConnection] - Message received: {"command":"PUSH_EQUALIZER_STATE_CHANGE","payload":"<removed>","timeStamp":1667753699400}
17:55:02.084 [DEBUG] [ntrol.internal.handler.AccountHandler] - check login amazonechocontrol:account:b4c3d5777b
17:55:02.160 [INFO ] [openhab.event.ItemCommandEvent       ] - Item 'Wohnzimmer_Licht_Brightness' received command 30
17:55:02.165 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'Wohnzimmer_Licht_Brightness' predicted to become 30
17:55:02.176 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'Wohnzimmer_Licht_Brightness' changed from 40.0 to 30
17:55:05.243 [DEBUG] [ntrol.internal.handler.AccountHandler] - updateSmartHomeState started with deviceFilterId=null
17:55:10.542 [DEBUG] [ocontrol.internal.WebSocketConnection] - Message received: {"command":"PUSH_ACTIVITY","payload":"<removed>","timeStamp":null}
17:55:10.548 [DEBUG] [amazonechocontrol.internal.Connection] - Make request to
17:55:10.818 [DEBUG] [amazonechocontrol.internal.Connection] - Call to succeeded
17:55:10.825 [DEBUG] [amazonechocontrol.internal.Connection] - Result of GET{"activities":[<removed>],"endDate":1667753701382,"startDate":1667753353455}

When this happens the Alexa Android app also displays “Device is unresponsive” but unlike in other forum topics I could find it resolves itself after a few seconds. That also happens with no discernible pattern when not giving commands. The state on my local webinterface and on MyOpenHAB updates immediately and there are no errors about losing connection to the openHAB Cloud.

I’d appreciate any help and tips on how to approach this problem as I seem to be the only one affected by this.

Unfortunately, you can’t use the Amazon Echo Control binding logs to troubleshoot the Alexa skill since these are using two different workflows. So the PUSH_ACTIVITY log lines you identified are unrelated.

1 Like