Hi!
I ran in to the problem that the conbee II usb-dongle was reported as “Product - RaspBee” as shown in your attached image, but the firmware wasn’t, I think it stated “not connected”.
I then made a identical hass.io docker install on a sd card and everything worked.
Found these two:
https://github.com/dresden-elektronik/deconz-rest-plugin/issues/1803
https://www.raspberrypi.org/forums/viewtopic.php?t=245931
…and tried the ssd in usb2.0 port instead and everything was ok. Of course usb3.0 is better than usb2.0 but as long as I don’t have to run Hass of sd cards I’m happy.
I did zero debugging.
Hi all! I have recently experienced issues with my ConBee2 setup.
My hardware is:
HP proviant ML350G6 server, running Ubuntu.
deCONZ 2.05.72, running in docker container, using marthoc/deconz image, and host network.
Home Assistant version 0.104.3, running in docker container on same host, but with unique IP-address on my LAN.
ConBee2 connected to USB 2.0 port, with extension cable. Firmware 264A0700.
Had it running in deCONZ, and all working well.
Changed over to using the ZHA-integration in home-assistant, but found it a bit difficult to set up (above my Zigbee-knowlegde), so decided to go back to deCONZ.
Did a reset on my phoscon gateway, and started setting up lights, sensors, switches, groups and scenes in the Phoscon App.
But now my container logs are throwing following error every time I turn on a light, call a scene or whatever. Seems to also repeat every 4 minutes.
10:47:30:959 Remove websocket <homeassistant-IP>:42974 after error Unknown error
10:47:46:171 New websocket <homeassistant-IP>:43498 (state: 3)
This makes all entities unavailable for a while, seems like the ConBee is rebooting.
Tried another reset of gateway, but still the same error.
Can someone help guide me to what this is, and what I might do to fix it?
Espen
Hi,
Am I doing something wrong? Updated from 0.103.6 to 0.105.2 and all my groups got duplicated. I was hoping to skip a couple of versions in order to avoid this problem.
Hi, iam using the conbee 2 with various zigbee lights from hue, osram and tink. When i apply scenes from HA, 2 out of 10 times one or two lights wont get the state right. Sometimes they dont turn on, or they dont get the color right. My Zigbee Mesh seems to be fine like you can see in the posted screenshot. I tried to change the Zigbee channel, but without sucess. Is there something else i can do, then apply the scene twice?
No matter which Zigbee solution you use - if you send a awful lot of messages to many devices at the same time, the Zigbee network can get flooded or the devices cannot follow all the communication.
If you create groups in Home Assistant of lights and you turn the group on or off then Home Assistant will send turn on/off message to each individual lamp in the group.
If you create groups in Phoscon then you create Zigbee groups. They are represented as a single light in Home Assistant. More important on the Zigbee network you only have one single turn on or turn off message that all the members of the Zigbee group react on. And only one message need to be relayed from device to device. It is much more reliable to use the Phoscon groups.
It would be the exact same for people using ZHA which just recently got enhanced to create groups.
It gets even worse if you try to increase and decrease intensity in small steps. Then the flooding gets massive. Naturally the number of members is important. A group of two probably does not make a big difference. But I have groups of 7 in my living room and I have groups representing most of the house and for sure that work very poorly if I use Home Assistant groups.
You can create a Phoscon/deconz group. And in Home assistant where this is a light you can put this light in a groups of non-Zigbee lights and switches if you have some mixed technology groups.
3 Likes
Thank you for your constructive answer!
So I guess iam out of luck when it comes to scenes where different lights get different colors and brightness…
I had the same behavior until 8 weeks ago and solved it by plugging a 3m usb-enhencement cable between the raspberry and the stick. In addition I plugged an old powerd usb 2.0 hub beween. No issues since that.
I have 38 bulbs from different providors (hue, tint, innr), switches and 7 motion sensors in my house. All groups are created in deConz. But screnes have been moved exept 3 basic scenes per room (dark, medium, bright) into HA.
Iam running HA in docker on a nuc. The nuc only has USB 3.0 ports. I already use a 3m USB extender. I will See if I can get a cheap USB 2 hub.
This is really weird. There must be a method to measure the data that gets lost so we can see what goes wrong where. I dont know how to use vnc tiger well.
thats my picture:
But everything works fine.
Sometimes it is amazing, that two bulbs relatively close together have only a red or no connection and two others, far away, have a green connection
But: the result is key
Wow,
The weird thing is that the connection between all of my bulbs seems fine.
Now i got the ingress error and nothing is working anymore after i tried to change the usb port, lol.
i can enter the deconz page in HA but no lights get detected, cant change zigbee channel, firmware update says not connected. I tried to clear cache and cookies of the browser, unistalled the deconz addon and resetted the getway, restarted home assistant multiple times. nothing.
this thing wants to kill me
These are the error codes i get from HA
20-02-09 17:54:37 WARNING (MainThread) [hassio.api.ingress] Ingress for -BQb8Gtl_lbYrQ5o9cAhUqK6ZRYI-hq5ZbJv2rswpO0 not available
20-02-09 17:55:17 ERROR (MainThread) [hassio.api.ingress] Ingress error: None
20-02-09 17:56:33 ERROR (MainThread) [asyncio] Unclosed connection
client_connection: Connection<ConnectionKey(host='172.30.33.3', port=8099, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None)>
20-02-09 17:56:33 ERROR (MainThread) [asyncio] Unclosed connection
client_connection: Connection<ConnectionKey(host='172.30.33.3', port=8099, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None)>
Ok, since no one commented my last post, I went a did what Robban said here:
Didn’t work. All my groups are not available in the interface and the configurator never opened, so I have no idea if the groups are duplicated or not. Since I am on a virtual machine I reverted it back to 0.103.6. Removing the integration, upgrading and adding the integration again didn’t work too.
Does anyone have any idea what can I do now?
Thanks for your help.
Hi
The problem with USB 3 is unique to the Raspberry Pi 4 where there is some strange issue with SSDs on USB3 in combination with USB serial devices. And what seems to help is to move the SSD to a USB2 port which makes it slower but cures the problem. On your NUC it has no significance that the ports are USB3
The USB hub is also a Raspberry Pi thing.
The extention USB cable can help on all computers. It is a matter of moving the Conbee away from noise (electrical radio noise) item like the computer itself. If you move the Conbee away from the NUC but place it next to another device that makes noise then it does not helpor can get worse. The idea is to move the Conbee stick a bit away from anything electrical so the radio reception is less disturbed.
And you can also maybe place it a bit high so it is higher than most furniture. That can also increase the range.
With respect to scenes.
It all comes to the size of the group
I also use scenes with 7 or 8 lights and it seems to work most of the time. I try to think about how much I change at a time.
The good thing in Phoscon/deconz is that you can create as many groups as you want and the same light can be in multiple groups. So you can create subgroups for lights that you set to the same settings.
Let us say you have a living room with 10 lights. 7 of them should be set to 50% and 3 of them to 80 %. Then create two groups of the 7 and 3 and in your Home Assistant scene you now only need to set two lights groups. And in the zigbee network it becomes only two commands sent.
I have scenes where I do not use a group with 12 lights that turn on when it gets dark. And it mostly works. But I notice that sometimes a light is missed when I come home. It is not critical in this instance because all I want is the house to appear busy.
What you really want to avoid is combinations of intensity, colour and using stepwise transitions. There are many examples people make with scripts that makes transitions sending many small steps. Then you end up sending 10 messages for 10 lights to turn on. Then 10 messages to change colour. And the next seconds 100s of messages stepping up intensity. That does not work well. Zigbee is not a fast communication channel. It has a very limited bandwidth
2 Likes
Thank you these are really good advices you made! but first i have to get the conbee running again. like you see in my post above something serious broke and iam trying for hours to get this right again…
Very interesting aspects to think about even I have scenes with 8 to 10 devices in the living room.
Thanks a lot.
Does anyone know why the Aqara vibration sensor has (as a binary sensor) the device_class motion instead of vibration?
Hi guys,
I am using deconz for some time, have multiple Ikea bulbs (1 group) paired and no issues with managing through home assistant.
I just purchased Xiaomi Aqara/Opple Zigbee Smart Switch (6 buttons model) and trying to pair it with Conbee2 gateway. From the deconz menu I go to the menu - devices - switches and click “Add New Switch”. It starts scanning, at this point I reset my switch and it flashes twice as it should when it is paired. Few minutes later decons gives me - no switches found. I retried multiple times but no luck.
What is interesting here - the switch starts working somehow (4 out of 6 buttons): 1st button - turn on my IKEA bulbs, 2nd - turn off, 3d and 4th - brightness up/down. So it assigned some actions/automations to the buttons but I cannot find it anywhere (not in Deconz devices and not in HA Devices/entities), unless I look in the wrong place.
Also tried listening fro deconz_events from HA developer tools, but pressing the buttons on the switch doesn’t give anything.
Anyone has any experience with Xiaomi Aqara Opple switches?
Or it might be purely because this Xiaomi switch is not in the list of supported devices
Update: If anyone interested - found this thread on github, they say Xiaomi Opple initial support will be included in the next release.
Are you using the in-built automation editor? Maybe you should give Appdaemon a try. I have two of these cubes and none of your mentioned issues. Good luck https://www.triumvirat.org/2019/09/18/homeassistant-magiccube/
I completely reinstalled the Ubuntu server and installed home assistant in docker. Even on vanilla HA I get the ingress Error. I always get
Cannot connect to host 172.30.33.0:8099 ssl:None [connection refused]