Conbee II and Deconz

stain3565 · July 21, 2020, 5:56pm

As I have now a Xiaomi Light sensor to set up, and am always looking at expanding smart devices, I bought a Conbee II.

I have looked at all instructions on setting up in home assistant and went the Add On route.

My hassio is on a Raspberry Pi 4. I connected the Conbee II (currently directly into the Pi as, temporarily, I have not got a USB extender - arriving tomorrow and, although I know this is not ideal re interference, I don’t think its is causing my current issue).

The Deconz addon installed and once I had altered the config, it started. Current config is below:

device: >- /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_xxxxxxxx-if00 vnc_password: ''

The Web UI results in Bad Gateway 502.

In Supervisor System, I have the following:

20-07-21 17:26:59 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.xx.xx.xx:8099 ssl:None [Connection refused]

I am still a NOOB so look forward to some help.

mirekmal · July 22, 2020, 7:36am

Go to Supervisor->System->Hardware and check what is exact name of your Conbee stick. it should look like:

then copy the full name of stick into config. There should no ‘xxxxx’ there:

device: >-
  /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE1963248-if00

Also try to restart HA. I found that sometimes Deconz plugin does not always start properly, even if UI shows it it is working… then usually I get this Bad Gateway error.

stain3565 · July 22, 2020, 10:33am

Sorry should have stated that the xxxxx was just my replacement of info that could identify the full address of my conbee stick. I am using the full name from System hardware.

Joerg · July 22, 2020, 10:47am

Silly question, but the Deconz software is installed and started on your PI?

Burningstone · July 22, 2020, 11:51am

He ibstalled the add-on so this is covered already.

Burningstone · July 22, 2020, 11:54am

do you see something in the logs of the add-on?

I wouldn’t be too sure about this, mine didn’t work at all directly attached to a Pi 4.

Did you try to reinstall the add-on?

Joerg · July 22, 2020, 1:05pm

Ok, interesting, incl. Phoscon?

stain3565 · July 22, 2020, 6:57pm

You were right. Once I had the USB extender, Phoscon worked fine. Mind you, my first idea to add the xiaomi light sensor has fallen apart as now I am seeing that it is not actually supported by Deconz! Not sure how I made that mistake. I was sure I had seen this on the official list or seen Conbee suggested as able to integrate it. Never mind. At least Conbee is now up and working for future Zigbee Integrations.

Burningstone · July 22, 2020, 7:26pm

Yes, including Phoscon

Burningstone · July 22, 2020, 7:30pm

I have Xiaomi light sensors sucessfully integrated into DeCONZ. They are not supported by Phoscon but you can pair them to DeCONZ.

I can’t remember how I added them. Try to search for new sensors in Phoscon, then press and hold the button to pair the device. If you have VNC access to DeCONZ, you should see the device, in HA there should be a new sensor showibg the lux value. You may need to repeat the procedure a few times until it pairs.

stain3565 · July 22, 2020, 8:26pm

I am getting Ready when trying to pair but nothing happens when I click it. That is when I went back to check the supported list.

stain3565 · July 24, 2020, 12:07pm

My installatipn is on a Raspberry Pi 4 with Hassio so I am not working on a Raspbian GUIVsystem.

Although it appears, from comments online, that VNC gives a better Deconz interface, I am not sure whether VNC can be installed on Hassio and whether that would even allow a GUI interface with Deconz. Is it feasible, and if so, how to install when Apt-get does not appear to be an option on hassio?

Burningstone · July 24, 2020, 1:03pm

The add-on already includes VNC access. You need to access it from a remote computer with a VNC client (e.g. I use Remmina in linux).

Where fid you click what? In the Phoscon UI?

stain3565 · July 24, 2020, 1:24pm

This was in the phoscon ui. Things have changed since then and have got worse.

Today, it did now appear that the ‘daylight sensor’ had been added successfully. So I thought I had moved on. However, I then started getting issues with most of the Configuration pages in Home assistant failing to load, including entities etc. I think I had seen Phoscon identify the sensor in Notifications and had enabled it fir use. Seemed sensible but this obviously meant the sensor was now in Home assistant and was most likely causing page failures.

Logs suggested Deconz issues so I went for the nuclear option and uninstalked/reinstalled Deconz with the correct device id, as before.

This did solve the page loading issue but now Decinz does not start, even though clicking Start does enable Web Ui buttons etc.

The logs state otherwise and the Web Ui does not in fact open anything now. I have attached a screen showing that Start has been pressed (all other options enabled so looks ok) and also a screenprint created after this when I attempted to open Deconz. A log entry is below:

Config entry for deconz not ready yet. Retrying in 5 seconds

13:55:20 – config_entries.py (WARNING) - message first occurred at 13:46:58 and shows up 10 times

I get thrown back to the Deconz Start screen to try again. Same result every time.