JowiHue and Aqara Wireless Mini Switch not being added

[ØysteinHJ]

It's been a couple months since I installed my Conbee II. It all installed fine for me on Windows 10. I don't remember exactly how I did it but I'm sure I followed the instructions in the PDF.

Jim

Didn't know about the PDF, to be honest. I'll be sure to check it next time. 🙂

[w.vuyk]

I think I might know what is happening here. I am seeing the same here on my Conbee. If the conbee is connected for some time, the plugin still functions. But a search for the conbee does not come back with results on a UPNP scan, nor from the Dresden test on https://phoscon.de/discover (which is used by the plugin when UPNP does not come with an answer). You can test this effect yourself by using this link in a browser. If the conbee is in for two or three days, you will not find it anymore in the result list.

When the bridge device is missing (when deleted...) the plugin does not know the IP address anymore and will do a search during initialization. But the conbee probably is then not to be found anymore.

To solve this, choose to reboot the device in deCONZ (in the edit list) and close deCONZ after that. Then take out the Conbee USB stick for at least 10 seconds and put it back. Start deConz and connect to the USB stick. Using the above link, will show you the device again. A new search in JowiHue will now find the device as well.

Startup of both deCONZ and HS4 on a machine is best done with starting deCONZ first, and delay the startup for HS4 for the time that deCONZ needs to start. In my case this is 20 seconds. I have heard users using some startup delayer for this. I am using the task planner of Windows 10 for this, with giving a delay time for each program at login.

Wim

[fresnoboy]

I think I might know what is happening here. I am seeing the same here on my Conbee. If the conbee is connected for some time, the plugin still functions. But a search for the conbee does not come back with results on a UPNP scan, nor from the Dresden test on https://phoscon.de/discover (which is used by the plugin when UPNP does not come with an answer). You can test this effect yourself by using this link in a browser. If the conbee is in for two or three days, you will not find it anymore in the result list.

When the bridge device is missing (when deleted...) the plugin does not know the IP address anymore and will do a search during initialization. But the conbee probably is then not to be found anymore.

To solve this, choose to reboot the device in deCONZ (in the edit list) and close deCONZ after that. Then take out the Conbee USB stick for at least 10 seconds and put it back. Start deConz and connect to the USB stick. Using the above link, will show you the device again. A new search in JowiHue will now find the device as well.

Startup of both deCONZ and HS4 on a machine is best done with starting deCONZ first, and delay the startup for HS4 for the time that deCONZ needs to start. In my case this is 20 seconds. I have heard users using some startup delayer for this. I am using the task planner of Windows 10 for this, with giving a delay time for each program at login.

Wim

Ah, this may explain odd behavior on deconz starts. My Conbee is hung off a raspberry Pi and connected via virtual USB here. This is because I run HS3 and deconz on a windows server instance as a guest on a vmware ESXi host. I wanted to get rid of USB passthrough because I can't migrate HS3 to another server when I am doing maintenance work. By hanging it off an Rpi and accessing it over the network, I don't have issues with local USB devices.

But this means the conbee never truly initializes when the HS 3 system reboots as it's connected to the USB bus of the rpi.

Why is this behavior occurring? A conbee firmware bug?

[TC1]

Startup of both deCONZ and HS4 on a machine is best done with starting deCONZ first, and delay the startup for HS4 for the time that deCONZ needs to start. In my case this is 20 seconds. I have heard users using some startup delayer for this. I am using the task planner of Windows 10 for this, with giving a delay time for each program at login.

Wim

I don't disagree with the startup sequence, but you need to add a caution, if the user starts up deConz and HS on the same PC, and deConz starts first, it will grab the http port 80 first and cause a conflict with HS. deConz needs startup parameters to alter the listening ports or it has to start after HS so it automatically picks alternative ports.

[w.vuyk]

Why is this behavior occurring? A conbee firmware bug?

My feeling agrees to that thinking. I know Dresden Electronics is aware of some issues with the Conbee 2

I don't disagree with the startup sequence, but you need to add a caution, if the user starts up deConz and HS on the same PC, and deConz starts first, it will grab the http port 80 first and cause a conflict with HS. deConz needs startup parameters to alter the listening ports or it has to start after HS so it automatically picks alternative ports.

Agreed, was mentioned in post #15