Not really related specific to Deconz (I guess), but more to Conbee stick together with Deconz.
I’ve been using the combination pi3 and Conbee for quite some time and once the zigbee network stabilized, I’ve rarely have had issue with nodes becoming unavailable, I’ve got around 50 nodes in total, half of them lights and half sensors.
A few weeks ago I made the move to a nuc and after that I’ve having constant minor issue that nodes are becoming unavailable, they are unavailable for a day or less and them coming back as available again.
I can think of three changes that I’ve made during the same period
On the pi I only used an extension cable for the Conbee, not for my Z-wave stick, now on the nuc I’m using extensions for both, so the actual sticks are fairly close to eachother (~5 cm)
The power from the nucs usbs are lower than from the pi and this is causing this behaviour.
I’ve gone from 5 to 25 Plejd units (it’s a scandinavian wall dimmer that creates a bluetooth mesh) and now this mesh is interfeering with the zigbee mesh.
Any ideas here? What should I try to improve this? Earlier the zigbee network was 99% reliable, now I would estimate it to 50%, which is quite frustrating.
Yeah, challenge is to try to do something about the BT interference since you don’t really have a control of the channel there. So I’m trying the channel change on Zigbee to see if it makes a difference. I’d rather not change the wifi, that I’ve coordinated between the neighbours to get as little interference as possible.
maybe a neighbour at the same time changed wifi channel or to a more powerful router …
Please note that routers with setting to USA have a much more powerful range/interference compared to EU settings (I personally put all my AP to USA Wifi and its much better for the signal, hope my brain will not fry though ).
If you have WiFI USA settings and live in a not so big environment you can put it to EU settings (even if you live in USA), that should help
I had the extension already on the pi, so no difference there. Now I’ve moved the sticks to approx 2 meters between them (Z-wave and ZigBee shouldn’t really interfere with eachother, but you never know), changed Deconz to channel 25 and got my 2.4 WiFi running on channel 1, can’t do much about Plejd since it’s BT.
Let’s see how this plays out, if this doesn’t help, I’ll put a powered USB hub between the nuc and Conbee stick.
The channel change seems to have solved my issues, but for anyone else that is thinking about doing this. Be prepared that all battery operated units have to be woken up before they will be online again and make sure that all powered units are connected otherwise those have to be removed and then added again.
I don’t know if this is the correct place to ask, but has anyone got deCONZ talking to the Hue iOS app (older one) or the one I use all the time iConnectHue
Running on a standalone Pi latest Rasbian, deCONZ v2.05.59 firmware version 262F0500.
Thanks. It is - I have looked on GitHub and it seems a couple of people are having similar issues with Hue App and Alexa as well (since the latest version), so hopefully a future fw update may fix it.
I finally got deCONZ working on my Synology. Took a very long time to figure out how to get the ConBee to show, but eventually, I found a guy saying to SSH and do this:
sudo insmod /lib/modules/usbserial.ko
sudo insmod /lib/modules/ftdi_sio.ko
Somehow, that worked.
So after that I tried to join some stuff in deCONZ. I have some Xiaomi things lying around so figured I would start by them.
I joined an Aqara window/door sensor which shows up fine in deCONZ, and the open/close sensor also shows in Home Assistant. However in deCONZ it appears that this sensor has a temperature sensor as well?:
Afterwards I tried joining a Xiaomi switch, but it does not seem to work in Home Assistant. It only shows up as a battery sensor, for how much battery is left on it:
).
