Raspberry Pi 5 + Raspbee = no devices found

[00lex]

Does the issue really belong here?

• I definitively want to report a bug within deCONZ or its REST-API

Is there already an existing issue for this?

• I have searched the existing issues and there is none for the bug at hand

Describe the bug

Hi! i was running deconz on my rpi4 with raspbee2 previously without issues.
Now i swapped the sd card and the module to the rpi5.

• in phoscon firmware is not connected.
• with "GCFFlasher_internal -l" I get "no devices found"

is deconz not ready for rpi5 or do I have a GPIO issue?

Steps to reproduce the behavior

• spent 6h on the internet without success.
• modul is ok. switching back, everything works.
• a clean install on a clean raspbian 12 results in the same.
• yes! original pi5 power adaptor
• checked both 5v pins and 3.3v. its ok
• here is a hint, but I don't know how to deal with it. serial port is enabled and bt disabled

Unlike previous Raspberry Pi models, where you could enable a serial console on GPIO14 and 15, enabling a serial console from raspi-config will enable a serial console on the new UART connector on /dev/ttyAMA0 on Raspberry Pi 5.

Expected behavior

getting help. I don't know what else to do

Screenshots

No response

Environment

• Host system: Raspberry Pi 5
• Running method: Raspbian 12 64
• Firmware version: latest
• deCONZ version: latest stable + latest beta
• Device: raspbee2
• Do you use an USB extension cable: no because raspbee2 + sd-card
• Is there any other USB or serial devices connected to the host system? no

deCONZ Logs

No response

Additional context

No response

[00lex]

got it!!!!!

add:
dtparam=uart0_console
to config.txt

close and please update the install instructions!

[Mimiix]

Great you figured it out :)

Thanks for sharing!

I'll close when Dresden updates the install guide.

[Mimiix]

To make a note: RPI5 is not listed as supported models on Phoscon docs as of now:

https://phoscon.de/en/raspbee2/install#raspbian

https://phoscon.de/en/raspbee/install#raspbian

It is being worked on :)

[manup]

Hi we received our first RPi5 today to make some tests and update the docs.
The (optional?) heat sink is a bit problematic as it sits right where RaspBee is located.

[ebaauw]

You probably want to use a GPIO riser. I've been using these for the RaspBee II on my Raspberry Pi 4B with heatsink case. Make sure to get one with medium to long pins; the RaspBee doesn't make good contact with the shorter variants.

The Pi 5 has a separate header for the serial port and no longer exposes it on GPIO 14 and 15, where the RaspBee expects it.
The documentation of the RP1 south bridge chip states that it supports up to 5 UARTs, that can be configured using alternate GPIO functions. I think adding the following line to /boot/config.txt should expose UART0 on GPIOs 14 and 15:

gpio=14,15=a4

See section 3.1 of the documentation and https://www.raspberrypi.com/documentation/computers/config_txt.html#gpio-control

[00lex]

Hi we received our first RPi5 today to make some tests and update the docs. The (optional?) heat sink is a bit problematic as it sits right where RaspBee is located.

Maybe but the rpi5 runs in my environmental 2 degree Celsius cooler. I'll leave the heat sink in its box for now.

Tomorrow I will test how the raspbee2 module behaves with the usb3 of the rpi5.

BTW. Found the Solution here: https://forums.raspberrypi.com/viewtopic.php?t=359132
maybe someone is interested in the discussion here

[00lex]

You probably want to use a GPIO riser. I've been using these for the RaspBee II on my Raspberry Pi 4B with heatsink case. Make sure to get one with medium to long pins; the RaspBee doesn't make good contact with the shorter variants.

or something like that :):

the reliability with usb3 without distance to the zigbee module is much much better. with the rpi4 I was able to disconnect the zigbee network with a lot of load on usb3. with the rpi5 without extension there are only rare dropouts. however. if you don't want to have stress, you continue to use extensions

btt:
this wasnt a bug. the solution is:
#7413 (comment)

case closed

[ebaauw]

Still cannot get my Pi 5 to recognise my old RaspBee (original model). @00lex what is your entire /boot/config.txt? And I assume you did the no serial console, but enable serial port from raspi-config?

I now have:

dtparam=uart0_console
dtparam=uart0=on

I edited the first line as per above suggestion, and I think raspi-config added the second line. The GPIOs are configured for the serial port:

$ pinctrl get 14-17
14: a4    pn | hi // PIN8/GPIO14 = TXD0
15: a4    pu | hi // PIN10/GPIO15 = RXD0
16: no    pd | -- // PIN36/GPIO16 = none
17: no    pd | -- // PIN11/GPIO17 = none

But the RaspBee isn't recognised by GCFFlasher_internal, nor by deCONZ.

[00lex]

just that:

enable_uart=1
dtparam=uart0_console

without:
dtparam=uart0=on
because:

enabling a serial console from raspi-config will enable a serial console on the new UART connector on /dev/ttyAMA0 on Raspberry Pi 5

Nothing else!

[ebaauw]

OK, Apparently I managed to brick one my old RaspBee devices. The other one is working with these settings, though.

[nsk]

Hi I tested your solution, no change for me I'm going to wire my rasbee2 in serial usb to see if I can flash a firmware directly to see if that solves anything, but no documentation on how to do it, will fumble around: pin 1 pin 6 and pin 8 for communication with the raspbee and Coolterm see if I can communicate with the raspbee ....

[krebsvo]

Where can I find the /boot directory (the file config.txt)?
I installed the last relay from the Git Hub page on the RI 5.