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

ConBee reported as RaspBee #157

Open
chmielowiec opened this issue Apr 6, 2021 · 3 comments
Open

ConBee reported as RaspBee #157

chmielowiec opened this issue Apr 6, 2021 · 3 comments

Comments

@chmielowiec
Copy link

Due to changes in commit db2861d in HA Beta my ConBee stick is reported as RaspBee device.

image

My env:

version core-2021.4.0b4
installation_type Home Assistant Container
dev false
hassio false
docker true
virtualenv false
python_version 3.8.7
os_name Linux
os_version 4.19.66-v7+
arch armv7l
timezone Europe/Warsaw
@chmielowiec
Copy link
Author

@systemcrash Related to #150, but it already worked fine before that fix.

@Adminiuga
Copy link
Collaborator

use /dev/serial/by-id for your ConBee device

@Xeevis
Copy link

Xeevis commented Dec 10, 2021

@Adminiuga

According to Phoscon docs
ConBee (USB) = ttyUSB0
ConBee II (USB) = ttyACM0
RaspBee/RaspBee II (GPIO) = ttyAMA0

In issue #150 OP states he has USB device in Synology NAS. Clearly he means ConBee II (Synology NAS doesn't even have GPIO pins). Proposed/applied change db2861d seems to just flag ConBee as GPIO Raspbee instead as ConBee. Original regex was in my opinion fine.

use /dev/serial/by-id for your ConBee device

I don't think that's even possible with Synology DSM ... and it's not necessary?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants