Raspbee II issues

Hello all,

I decided to get a new Raspberry 4 and a new Raspbee II to finally switch to supported supervised installation on Home Assistant OS. So I’ve got a fresh installation but I cannot use the Raspbee II.

All is updated to current versions:

  • Home Assistant OS 5.10
  • core-2021.1.4
  • deCONZ 6.6.2

I have a backup restored that seems to be doing well.

The following is listed under “Hardware”:

serial:
  - /dev/ttyAMA0
  - /dev/ttyS0
gpio:
  - gpiochip0
  - gpiochip504
usb:
  - /dev/bus/usb/001/001
  - /dev/bus/usb/001/002
  - /dev/bus/usb/002/001

(removed audio, input & disk, as it should not be related)

And I already tested both, /dev/ttyAMA0 & /dev/ttyS0 in the deCONZ addon configuraiton.
Most likely it should be like the current setup:

device: /dev/ttyAMA0

I’ve already tried to install Raspian and installed deCONZ via apt. This is working fine, so the hardware should be ok.

This is added to the config.txt:

enable_uart=1
dtoverlay=pi3-miniuart-bta

Ok, when I start the deCONZ addon the following is shown in the log:

[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] firmware.sh: executing... 
[21:35:28] INFO: GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyAMA0     | 0x0000 | 0x0000  |            | RaspBee 
[cont-init.d] firmware.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] novnc.sh: executing... 
[cont-init.d] novnc.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[21:35:29] INFO: Running the OSRAM LEdvance OTA updater...
[21:35:29] INFO: Running the deCONZ OTA updater...
[21:35:29] INFO: Starting udevd...
[21:35:29] INFO: Websockify waiting for VNC to start
[21:35:29] INFO: Running the IKEA OTA updater...
[21:35:29] INFO: Starting VNC server (local/yes)...
[21:35:30] INFO: Starting websockify...
[21:35:32] INFO: deCONZ waiting for VNC to start
[21:35:34] INFO: Starting the deCONZ gateway...
QCoreApplication::arguments: Please instantiate the QApplication object first
WebSocket server settings:
  - Listen on 127.0.0.1:5901
  - Flash security policy server
  - Web server. Web root: /usr/share/novnc
  - No SSL/TLS support (no cert file)
  - proxying from 127.0.0.1:5901 to 127.0.0.1:5900
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[21:35:41] INFO: Starting Nginx...
2021/01/19 21:35:42 [notice] 328#328: using the "epoll" event method
2021/01/19 21:35:42 [notice] 328#328: nginx/1.14.2
2021/01/19 21:35:42 [notice] 328#328: OS: Linux 5.4.79-v7l
2021/01/19 21:35:42 [notice] 328#328: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2021/01/19 21:35:42 [notice] 328#328: start worker processes
2021/01/19 21:35:42 [notice] 328#328: start worker process 1585
[21:35:52] INFO: Successfully send discovery information to Home Assistant.
21:35:41:808 HTTP Server listen on address 0.0.0.0, port: 40850, root: /usr/share/deCONZ/webapp/
21:35:42:231 CTRL. 3.27.221:35:42:348 dev /dev/ttyAMA0
21:35:42:348 COM: /dev/ttyAMA0 / serialno: , RaspBee
21:35:42:348 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt
21:35:42:495 parent process s6-supervise
21:35:42:496 gw run mode: docker/hassio
21:35:42:496 GW sd-card image version file does not exist: /data/.local/share/dresden-elektronik/deCONZ/gw-version
21:35:42:496 sd-card cid: 1b534d474231515430ffffffff014500
21:35:42:498 DB sqlite version 3.27.2
21:35:42:500 DB PRAGMA page_count: 33
21:35:42:500 DB PRAGMA page_size: 4096
21:35:42:500 DB PRAGMA freelist_count: 0
21:35:42:500 DB file size 135168 bytes, free pages 0
21:35:42:501 DB PRAGMA user_version: 7
21:35:42:501 DB cleanup
21:35:42:502 DB create temporary views
21:35:42:508 started websocket server at port 8081
21:35:42:511 [INFO] - Found file containing button maps. Parsing data...
21:35:42:514 [WARNING] - Button map 'sunricherCCTMap' in JSON file has no assigned ModelIDs. Skip loading button map...
21:35:42:522 [INFO] - Button maps loaded.
21:35:42:524 dlg action: Read binding table
21:35:42:525 found node plugin: libde_rest_plugin.so - REST API Plugin
21:35:42:528 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
21:35:49:416 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
21:35:49:471 dev /dev/ttyAMA0
21:35:49:471 COM: /dev/ttyAMA0 / serialno: , RaspBee
21:35:49:804 dev /dev/ttyAMA0
21:35:50:075 Announced to internet https://phoscon.de/discover
21:35:50:076 discovery server date: Tue, 19 Jan 2021 20:35:50 GMT
21:35:50:077 	 local time seems to be ok
21:35:50:078 discovery found version 2.04.35 for update channel stable
21:35:50:534 dev /dev/ttyAMA0
21:35:50:535 COM: /dev/ttyAMA0 / serialno: , RaspBee
21:35:50:571 device disconnected reason: 4, index: 0
21:35:50:925 New websocket 172.30.32.1:60472 (state: 3) 
21:35:51:423 wait reconnect 15 seconds
21:35:51:487 dev /dev/ttyAMA0
21:35:51:487 COM: /dev/ttyAMA0 / serialno: , RaspBee
21:35:52:372 wait reconnect 14 seconds
21:35:53:368 wait reconnect 13 seconds
21:35:54:368 wait reconnect 12 seconds
21:35:55:367 wait reconnect 11 seconds
21:35:56:368 wait reconnect 10 seconds
21:35:57:367 wait reconnect 9 seconds
21:35:58:368 wait reconnect 8 seconds
21:35:59:368 wait reconnect 7 seconds
21:35:59:419 dev /dev/ttyAMA0
21:36:00:368 wait reconnect 6 seconds
21:36:01:368 wait reconnect 5 seconds
21:36:02:368 wait reconnect 4 seconds
21:36:03:368 wait reconnect 3 seconds
21:36:04:367 wait reconnect 2 seconds
21:36:05:367 wait reconnect 1 seconds

I don’t know if this is normal, but this part (including the “wait reconnect x seconds”) is repeated then once in a while:

21:53:37:429 dev /dev/ttyAMA0
21:53:37:430 COM: /dev/ttyAMA0 / serialno: , RaspBee
21:53:38:368 failed to reconnect to network try=1

So, when I try to access deCONZ from the addon, I choose to start “Phoscon” which leads to the initial light search which does not find my test bulb and when I skip that, I find myself on a page claiming that the network cannot be connected/accessed. At least this was the state yesterday, today I configured the integration and the gateway cannot even selected anymore in deCONZ addon…

So, before I do another fresh install or start trying to do a supervised installation on Debian 32bit… does anbody have any information on this setup? Does it work at all with the “Raspbee II”… ? I’m kinda stuck here and do not find any helpful information on how to proceed.

Thanks in advance!
Christian

This should go in your config.txt file

Have you got an extension cable between the pi and conbee?

Hello Riccardo,

thanks for the info. I’ve set this, but unfortunately did not change anything.

I even deleted the deCONZ integration and the AddOn. After new installation of the AddOn I do not even see the Gateway:

:confused:

Hello samnewman86,

it’s a Raspbee II, not a Conbee. There is no way to add an extension cable in between.

Hi Christian, you need to run a phoscon server. This can be on the very same Pi as your HA, however, the HA people will discourage you from doing this.
The docker image is here: https://github.com/deconz-community/deconz-docker
A convenient way to add docker images directly from the HA interface is to use portainer. There is no official portainer add-on any more, but you can use this: https://blog.mikejmcguire.com/2021/02/17/portainer-ce-2-1-add-on-for-home-assistant/

You’ll have to grant access to /dev/ttyAMA0 as well as open the ports up.

Hi there,
did you finally solve the problem?

I can see there is a typo in your line:

dtoverlay=pi3-miniuart-bt(a) # final “a” to be deleted

but anyway, I am in a similar situation, I am migrating from Raspbian to Debian 11 and I can’t find the
correct configuration for my RaspBee (I) because the original configuration from Dresden Electronic are only for Raspbian and I cannot find the way to show the /dev/ttyAMA0 or the other /dev/ttyS0 or S1 to work. Any help appreciated.
Regards,
Michele