Thanks for the heads up. I received my ConBee II stick this weekend and started setting up my ZigBee devices (Ikea and Aqara) using the faulty docker image. Most things seemed to work. Only thing I could not get to work was the VNC setup. After downgrading to the previous image VNC started to work.
Unfortunately after the downgrade my ConBee/Phoscon lost the connection to all of my ZigBee devices. They where still visible in Phoscon and Home Assistant, I just could not send any commands, sensors went silent. Had to actually re-pair all of them.
Is it known if the downgrade could damage the pairing of devices? Or did Conbee/Phoscon loose the connection independently of the downgrade of the docker image?
I added some Xiaomi Door/Window Sensors - After a while one of the 3 sensors did not respond anymore.
Removed the sensor and added again - the sensor started working.
Then a while later, the second sensor as well started doing the same - same process of removing and adding again was followed.
So far the 3rd sensor kept responding.
This morning everything was still responding…
Strange…
Does anybody have knowledge of the Xiaomi Door Window Sensors sometimes doing this?
I am running the latest version of Docker Marthoc/Deconz 02.05.69
@DieterClaeys same here .I got some Xiaomi motion sensors which stop responding and after readding them they work again . Sometimes I’ve the feeling it’s not really stable with devices which don’t send ping or whatever in a certain time.its like deconz forgets them
Same here, xiaomi doesn’t work reliable… What do you use as routers? I only have Osram plugs, now bought Ikea plugs to test… but not yet paired them, will do it by the end of week
I have lots of aqara door sensors and pir sensors and have no problems at all. I do have multiple devices that act as routers though including some cc2531 usb flashed as routers.
I’ve recently installed the deCONZ addon v 3.6 and connected a Conbee ii stick, but I’m finding it very slow to respond to hassio compared to my previous hue controllor? Sometimes senors stop reponding altogther and the only way to get them working is to restart DeCONZ
I have the stick connected to my rpi3 which is wired into my networt vai ethernet. Is there a chance that wifi or z-wave can interfere with the conbee? I also have a z-wave usb stick connected into my pi, although I did try disconecting this to see if it made any difference and it didn’t.
Its all setup in exactly the same place as my previous hue controller. I’ve also been trying some aqaua motion senors and a wireless switch all of which don;t seem to repond very quickly and sometimes intermitantly to both motion and presses.
At the momemt it doesn’t appear reliable enough to use so I’m almost at the point of giving up and sending all this back for a refund. But if anyone has suggestions as to how I might be able to improve performace that would be great.
My ConBee 2 setup is only up for a week, but so far it has been reasonably stable. I do have three Ikea bulbs wich should act as repeaters. The passive nodes, two aqara door sensors and three Ikea motion sensors, seem to have a stable conneciton.
I did once loose all devices. But that could have been a problem with the deconz docker which was described in this thread.
Is there a way to check connection quality for each device in deconz?
Ok, asking my question here since my seperate thread didn’t get any reply so far. I have HA running in a container (not hass.io) and also the deconz container from hub.docker.com. In the past I used just the standard ports, due to other apps I want to run on the same machine I changed the ports. After that I had to add
deconz:
host: 192.168.0.xxx
port: 1234
in the configuration.yaml. After that I was able to add the integration again. But now everything shows up as not available. Any idea?
