Hello,
I have a setup running since almost one year and I didn’t had any significant issue. Suddenly, since a couple of days, I’m facing trouble with Alexa integration.
The communication with Alexa is extremely slow. When I say the command to control any light connected, it take so long time to switch on / off (> 10 seconds). Alexa then replies that the device is not connected, but then lights will anyway goes on and off.
If I control the lights by calling the API directly it works without any significant delay. It is the integration with Alexa that makes the communication extremely slow.
Any idea of what the issue can be?
I am running version 2.30.2 (recently updated) and ConBee III firmware 264D0900. I’m not completely sure if the issue happen just after updating the version, but for sure was quite good with a previous version.
Hello!
Since a few days my connection with deconz and Alexa ist very poor, too!
I thought it was a coincidence, but the connection to the devices is poor or even no longer exists.
It just comes: “Waiting for Philips Electronics” and then “server not responding” if i take a action.
Hi, I have exactly the same message when I try to access the devices through Alexa App. Also all devices connected appears as not connected on the App, but they are working properly on the Phoscon app.
Which version are you running?
Hi!
I have the latest software and firmware, but I’m back for testing purposes.
I also connected my Raspi 5 (with Proxmox and the same software) again for testing.
the same problem everywhere.
My IP-Plugs and the Zigbee-Temp-Sensors (over NodeRed->Alexa) are working great.
Same to me (Raspi/iobroker/blockly are working)
EDIT: all devices are working from new Phoscon App and Hue switches.
New Device search by Alexa does not help.
I have the same problem. I operate it at different locations with different accounts. All three have problems with Alexa and deCONZ. Sometimes the devices aren’t listed in the Alexa app and then reappear as if by magic. When you call up a device, it takes forever for it to appear or switch on.
I deactivated the devices provided by deconz in Alexa and entered the device metadata in OpenHAB. The devices are now recognized and respond immediately
I took a look at OpenHAB. It looks quite interesting, but unfortunately it’s not that easy to use. It recognized my Conbee hub and the devices, but what do I have to do next?
I would be very grateful if you could explain it to me,
preferably in German
I have exactly the same issue, but meanwhile for some weeks. I already have deleted all deconz lights from Alexa, deleted the Api key in the bridge and readded all devices.
This did help in the past for some days, but then it startet to get unresponsive again. I´m running Deconz 2.30.2 on a Proxmox VM.
Hi I’m not sure what is causing this, to my knowledge the REST-API endpoints which Alexa is using didn’t change (but will double check). Unfortunately I don’t have a Alexa anymore so can’t test it myself.
The REST API plug-in doesn’t have Alexa specific code the way it worked in the past was due the Hue API v1 aligned endpoints. But that soley depends if Alexa keeps using them (?) since Hue has also changed their API quite a lot in v2.
Could anybody please check if the problem also occurs with older deCONZ versions, e.g. stable version v2.29.5?
I followed the tip from another forum and switched to openHAB (cloud) with deconz. After that i connected it with Alexa. Plugs and temperature sensors, everything works fine
