Hmmm… haven’t been changing a lot on my config lately but all of a sudden some sensors are starting to die. Out of nothing they are not reachable. If I remove them and readd, they’re working fine again. Anyone else have these same problems?
I have nearly the whole range of Aqara, a lot Hue motion sensors and some Ikea stuff. 100% are reachable. Have you checked if they are reachable in Phoscon or used the Deconz gui?
In phoscon they we’re unreachable too. Don’t know what happened but three range extenders we’re unreachable as well. Two of them I just did a powercycle and they started working again. One refused to work, after a powercycle it gave the impression it worked but after rebooting deconz docker image it didn’t. So after a while I decided I’d remove it and readd, after that, the sensors started working again too.
Hey @Jeff1
Thx for the details, that’s exactly what I need to support the device. Will be supported soon;)
@MadMonkey your .1 release solved it for me. If I now hit the test button it shows all info! Great work.
Hey @MadMonkey thanks for the support. If you need additional info. I am happy to help you.
@Martijn_Hoogenbosch I use the Deconz gui to check the network quality of my routers. Here I can see how many connections each routers has. Most routers have like 9 green lines to other routers, so their are a lot of back up routes and they work stable. If they are no so many lines or yellow or red lines then I add an additional router. My personal experience with around 30 Xiaomi routers is that a lot of sensors via Deconz connect to a IKEA reapeter or IKEA powerplugs. In my setup even Hue motions sensors connect to Ikea routers instead of a Hue powerplug. Only don’t know how to use GUI in Docker. I have a PI4 with deconz locally installed so I have Deconz and Phoscon together. I use Docker only for Home Assistant to run in Homey unsupported devices,for example IR (Broadlink mini 4)
Yes I know. If you add the container with macvlan driver it get’s it own IP address, so I can VNC to the container without problems. I already have a couple of routers, but if they start failing one after another then that’s a problem. Don’t know why or what happend, it now works great again. Did not add the repeaters to Homey so I didn’t see it. Now I have. And Yes, maybe i should add some additional repeaters. The thing is I don’t want to ‘see’ them, very much want to hide them out of sight, and don’t have that much room.
I just installed ConBee2 on Raspberry Pi using deCONZ image. The discovery doesn’t work at all. Getting ‘Error:Unable to find a deCONZ gateway’. I can connect ok to Phoscon App via web interface and was able to add some sensors that work ok. I also tried the manual configuration but stuck with getting an API. I was following the instructions on dresden-elektronik github and when using Postman with GET https://dresden-light.appspot.com/discover returns only this - . Any one could help, please?
I finally got a new Synology that can run Docker. I have installed the DeConz container (marthoc/deconz:latest) , but need some help getting it running.
Unfortunately I can’t find a tutorial to setup the DeConz container. Read thru this tread, but I can’t figure it out. Sorry…
(for instance, do I need to do this:
SSH to the nas and run 2 commands to load the drivers for the Conbee:
sudo insmod /lib/modules/usbserial.ko
sudo insmod /lib/modules/ftdi_sio.ko)
Could some kind soul please describe the next steps and best setting to get it up and running, to find my DeConz 2 stick and being seen in the Homey DeConz App?
Perhaps not relevant, but I host some websites on my Synology and have ‘Web Station’ running. Port 80 is not available.
Thanks!
How far did you get following the instructions on https://hub.docker.com/r/marthoc/deconz?
1 Like
Robert to the rescue 
I was not sure if I needed to do the steps listed under Pre-requisite, but it was simply a matter of running the container in Docker… I now understand that I have to do this 
In that case I will also need to change the ports from 80/443 to other values; I need 80 for Web Station. Or, will this work?
No, if they are already in use by another process you can’t reuse them. Alternatively, you can use a different network driver (search for macvlan on the forum) which would give the container its own IP-address, which would allow you to keep using 80/443. That will (probably) also work better with discovery.
Will do so Robert. Thanks!
If I run
sudo usermod -a -G dialout $USER
Do I replace USER with a Synology user name?
No, just leave as-is.
Gives an error.
Tried with USERS too (with an S):
I guess it all is a bit more complicated than anticipated…
Perhaps that instruction doesn’t apply to Synology, I can’t remember.
I will just carry on with the rest of the steps.
Thanks for pointing me in the right direction (again) !
I had the same problem. Plug the ConBee II USB stick into a different port.
Also type the command line {“devicetype”: “homey”} by hand, not copy/past!
With this I got the ConBee II Stick working, but not via the GUI interface of the Raspberry but via web browser on my MacBook.
Because I can’t access the GUI on the Raspberry, I can’t do any maintenance or control it with the deCONZ software. And the guys here in this post don’t seem to use Raspberry. Dresden Elektronik is not helpful either.
All in all I am not satisfied with the stick.
1 Like
Thanks @DirkG
Fed up for now. I will try again later this weekend!
