Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RaspBee not recognized on RPi3 Bullseye #7515

Closed
2 tasks done
brown78 opened this issue Jan 5, 2024 · 1 comment
Closed
2 tasks done

RaspBee not recognized on RPi3 Bullseye #7515

brown78 opened this issue Jan 5, 2024 · 1 comment

Comments

@brown78
Copy link

brown78 commented Jan 5, 2024

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

I have a Raspberry 3 with RaspBee on it. With an SD-Card flashed with Stretch all works pretty well. I set up a second SD-Card with Bullseye and installed deCONZ-latest-beta.deb - with the latest stable the deCONZ-gui didn't work.
The GUI now works but can't connect to the RaspBee. In the /boot/config.txt I added "dtoverlay=miniuart-bt" and Bluetooth is off after a reboot. Still the RaspBee is not found. The command "GCFFlasher_internal l" showed that no device was found. Is there something more I can try to make it work?

Steps to reproduce the behavior

Boot Raspberry
deCONZ-GUI is starting
No connection to RaspBee is established

Expected behavior

Connecting to RaspBee

Screenshots

No response

Environment

  • Host system: (Raspberry Pi 3B)
  • Running method: (Raspbian Bullseye)
  • Firmware version: (26350500)
  • deCONZ version (not Home assistant Addon version!): (2.05.67)
  • Device: (RaspBee I)
  • Do you use an USB extension cable: (no)
  • Is there any other USB or serial devices connected to the ho system? If so: Which? 433MHz Dongle, HMMOD on USBtoI2C

deCONZ Logs

No response

Additional context

No response

@Mimiix
Copy link
Collaborator

Mimiix commented Jan 5, 2024

Hi,

As this is not a bug report as described in #5113 i am closing this issue.

Please open a forum post for help.

Closing.

@Mimiix Mimiix closed this as not planned Won't fix, can't repro, duplicate, stale Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants