Just trying this now but still does not seem to work.
I notice in the logs even though its a clean install of deconz and I have added /dev/ttyS0 in my config that its still mentioning /dev/ttyAMA0 each time its retrying?
Then probably it didn’t apply the change. Try to restart the add-on. Also you can check for possible ports in the hardware page under the supervisor page. Maybe you got another one than ttyS0
That did the trick except for the groups. After rebooting ha it all came back
I have this very strange behaviour… I run hass core in an esxi with usb passthrough to usb conbee2. It works very well!
But… if I reboot complete hassos I cannot start container (addon). I can only do that if I first physically unplug usb stick, place back and start addon. That always works…
But this is not desirable e.g. when I am away from home and need to reboot hassos remote (rarely though but…).
Any tips?
I got a chance to try the Stitchy zigbee modules out yesterday, and you guys were right, they just worked out of the box. A switch and a dimmer. Little report and photos on this thread.
Sorry, I really needs some tip on this. Today I had a power outage. All came up fine but deconz not. Can’t start it remote. Have to physically take out and in usb stick then it works immediately.
s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] done.
[services.d] starting services
[services.d] done.
starting version 237
[23:56:44] INFO: Waiting for device…
[23:59:45] FATAL: No device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2194613-if00 found!
[cmd] /run.sh exited 1
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal
After the update. deCONZ don’t work… What to try?
It was fine before the HA and deCONZ update for hassio RPi with Conbee II
deCONZ
Current version: 5.3.5
After the update what I’ve tried so far… few different firmware updates with Windows PC.
GCFFlasher V3_05 (c) dresden elektronik ingenieurtechnik gmbh
Path | Vendor | Product | Serial | Type
-----------------+--------+---------+------------+-------
\\.\COM3 | 0x1CF1 | 0x0030 | xxxxxxxxx | ConBee II
..\deCONZ\bin>GCFFlasher -d COM3 -t 60 -f ../firmware/deCONZ_ConBeeII_0x26580700.bin.GCF
GCFFlasher V3_05 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device COM3 (ConBee II)
deCONZ firmware version 264A0700
action: update firmware after 6822 ms
flashing 160930 bytes: |==============================|
verify: .
SUCCESS
\deCONZ\bin>GCFFlasher -d COM3 -t 60 -f ../firmware/deCONZ_ConBeeII_0x26580700.bin.GCF
GCFFlasher V3_05 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device COM3 (ConBee II)
deCONZ firmware version 26580700
action: update firmware after 6761 ms
flashing 160930 bytes: |==============================|
verify: .
SUCCESS
\deCONZ\bin>GCFFlasher -d COM3 -t 60 -f ../firmware/deCONZ_ConBeeII_0x26490700.bin.GCF
GCFFlasher V3_05 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device COM3 (ConBee II)
deCONZ firmware version 26580700
action: update firmware after 6823 ms
flashing 158985 bytes: |==============================|
verify: .
SUCCESS
22:59:59:531 wait reconnect 10 seconds
22:59:59:582 dev /dev/ttyAMA0
23:00:00:531 wait reconnect 9 seconds
23:00:01:531 wait reconnect 8 seconds
23:00:02:531 failed to reconnect to network try=8
23:00:02:531 wait reconnect 7 seconds
23:00:03:531 wait reconnect 6 seconds
23:00:04:531 wait reconnect 5 seconds
23:00:05:532 wait reconnect 4 seconds
23:00:06:531 wait reconnect 3 seconds
23:00:07:531 failed to reconnect to network try=9
23:00:07:531 wait reconnect 2 seconds
23:00:08:531 wait reconnect 1 seconds
23:00:08:580 dev /dev/ttyAMA0
23:00:08:580 COM: /dev/ttyAMA0 / serialno:
23:00:08:580 COM: --dev: /dev/ttyAMA0 (RaspBee)
23:00:08:659 device disconnected reason: 4, index: 0
23:00:09:531 wait reconnect 15 seconds
23:00:09:578 dev /dev/ttyAMA0
23:00:09:578 COM: /dev/ttyAMA0 / serialno:
23:00:09:578 COM: --dev: /dev/ttyAMA0 (RaspBee)
23:00:09:615 dev /dev/ttyAMA0
23:00:10:531 wait reconnect 14 seconds
23:00:11:531 wait reconnect 13 seconds
23:00:12:531 failed to reconnect to network try=10
23:00:12:531 wait reconnect 12 seconds
23:00:13:531 wait reconnect 11 seconds
23:00:14:531 wait reconnect 10 seconds
23:00:15:532 wait reconnect 9 seconds
23:00:16:531 wait reconnect 8 seconds
23:00:17:531 reconnect network failed, try later
23:00:17:531 wait reconnect 7 seconds
23:00:18:031 start reconnect to network
23:00:18:531 wait reconnect 6 seconds
23:00:19:531 wait reconnect 5 seconds
23:00:19:575 dev /dev/ttyAMA0
23:00:20:531 wait reconnect 4 seconds
23:00:21:531 wait reconnect 3 seconds
23:00:22:531 wait reconnect 2 seconds
23:00:23:282 failed to reconnect to network try=1
23:00:23:531 wait reconnect 1 seconds
23:00:23:576 dev /dev/ttyAMA0
23:00:23:576 COM: /dev/ttyAMA0 / serialno:
23:00:23:576 COM: --dev: /dev/ttyAMA0 (RaspBee)
23:00:23:622 device disconnected reason: 4, index: 0
23:00:24:530 wait reconnect 15 seconds
23:00:24:575 dev /dev/ttyAMA0
23:00:24:575 COM: /dev/ttyAMA0 / serialno:
23:00:24:575 COM: --dev: /dev/ttyAMA0 (RaspBee)
23:00:25:531 wait reconnect 14 seconds
23:00:26:530 wait reconnect 13 seconds
23:00:27:531 wait reconnect 12 seconds
23:00:28:531 failed to reconnect to network try=2
23:00:28:531 wait reconnect 11 seconds
23:00:29:531 wait reconnect 10 seconds
23:00:29:573 dev /dev/ttyAMA0
23:00:30:532 wait reconnect 9 seconds
23:00:31:531 wait reconnect 8 seconds
23:00:32:531 wait reconnect 7 seconds
23:00:33:530 failed to reconnect to network try=3
23:00:33:530 wait reconnect 6 seconds
23:00:34:530 wait reconnect 5 seconds
23:00:35:531 wait reconnect 4 seconds
23:00:36:531 wait reconnect 3 seconds
23:00:37:531 wait reconnect 2 seconds
23:00:38:531 failed to reconnect to network try=4
23:00:38:531 wait reconnect 1 seconds
23:00:38:576 dev /dev/ttyAMA0
23:00:38:576 COM: /dev/ttyAMA0 / serialno:
23:00:38:576 COM: --dev: /dev/ttyAMA0 (RaspBee)
23:00:38:598 device disconnected reason: 4, index: 0
23:00:39:531 wait reconnect 15 seconds
23:00:39:585 dev /dev/ttyAMA0
23:00:39:585 COM: /dev/ttyAMA0 / serialno:
23:00:39:585 COM: --dev: /dev/ttyAMA0 (RaspBee)
23:00:39:622 dev /dev/ttyAMA0
23:00:40:531 wait reconnect 14 seconds
23:00:41:531 wait reconnect 13 seconds
23:00:42:531 wait reconnect 12 seconds
23:00:43:531 failed to reconnect to network try=5
23:00:43:531 wait reconnect 11 seconds
23:00:44:531 wait reconnect 10 seconds
23:00:45:531 wait reconnect 9 seconds
23:00:46:531 wait reconnect 8 seconds
23:00:47:531 wait reconnect 7 seconds
23:00:48:531 failed to reconnect to network try=6
23:00:48:531 wait reconnect 6 seconds
23:00:49:531 wait reconnect 5 seconds
23:00:49:580 dev /dev/ttyAMA0
23:00:50:531 wait reconnect 4 seconds
23:00:51:531 wait reconnect 3 seconds
23:00:52:531 wait rec172.30.32.2 - - [16/Jun/2020:23:00:54 +0300] "GET /api/E463615D64/config?_=1592337172836 HTTP/1.1" 200 2854 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0"
172.30.32.2 - - [16/Jun/2020:23:00:59 +0300] "GET /api/E463615D64/config?_=1592337172837 HTTP/1.1" 200 2854 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0"
Thanks for this.
Between this particular issue and the unannounced dropping of support for eMMC on my TinkerBoard S I don’t think I’ll be updating HassOS 3.13 for a while yet.
Does anyone know how to access the underlying file system structure when using Deconz through HA addon? Im trying to follow some steps from this issue https://github.com/dresden-elektronik/deconz-rest-plugin/issues/1055 where it mentions to modify an xml file but i cannot work out how to actually access that file.
Has anyone firstly attempted to fix that issue above and has done so successfully or secondly ever been able to access the file system?
Thanks
Andrew
You need the ssh and web terminal add on from the community store. Then disable protection mode. Now ssh to HA and use docker commands: docker container list And docker -it exec addon_name /bin/bash
Be careful of what you do!
I’m new to deCONZ, I just got my ConBee II stick, and updated it to the latest fw.
I installed the deCONZ addon in HassIO, and I was surpised to see that I need to have the deCONZ GUI required to run in order for the Zigbee service to be online.
Anyway, my issue is that I am getting high CPU usage every time I connect to deCONZ via VNC, and the high CPU usage does not drop down once I disconnect from the session. I need to restart the addon for the usage to settle. Until I connect to VNC again.
Here are my deCONZ versions:
Here’s what processes are using CPU:
I’m not a too experienced Linux user, so I tried installing deCONZ for Windows to see how it works.
The behavior is pretty much the same. When deCONZ GUI is active and visible, the process will eat up 16-17% CPU, but once I minimize it, the usage drops below 1%. I don’t prefer however the Windows approach as I need to have the GUI always running in order for ConBee to work.
Is there a way to run deCONZ as a Windows service or without the GUI and only start GUI on-demand?
I’m running HassIO 0.111.2 on Ubuntu 19.04 VirtualBox VM, hosted on an Intel NUC running Windows. 10.
You will notice that your Conbee II is being recognized as a RaspBee. I suspect that the device “/dev/ttyAMA0” setting in the configuration is incorrect.
You can disable VNC in addon settings. You can also use the ZHA integration instead of the deCONZ one
I know, but I need VNC in order to see the connected devices. I have a couple of smoke sensors (Xiaomi and Heiman) which do not show up in Phoscon and I can’t manage them there.
I haven’t tried the ZHA integration though, I’ll give it a shot.
But is it woking ok with ConBee, compared to deCONZ?
Yes, Conbee II is supported
I don’t see anything else. After the update I needed to change it, cannot remember what it was before the update.
~ $ cd /dev
dev $ ls
fd mqueue ptmx random stderr stdout ttyAMA0 zero
full null pts shm stdin tty urandom
dev $
What does it say on the Supervisor - System - Hardware button? In my case, it is “/dev/ttyUSB0”.
So normally you could remove them from the core.device_registry file but if you are running homeassistant (formally hassio) you have no way to edit this file as you cannot bring homeassistant down and still edit the file.