-
Notifications
You must be signed in to change notification settings - Fork 29
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
Still RaspBee II issue - /dev/ttyAMA0 permissions #269
Comments
The fact that /dev/ttyAMA0 has a group owner of tty typically means that there is a getty running on that port, and you need to disable that. |
Conbee is USB and is not on /dev/ttyAMA0 ? Did you look here WebThingsIO/serial-prober-node#11 |
Sorry - my mistake. It's a Raspbee II... |
@mchisari can you edit title and first message ? |
mrstegeman
changed the title
Still Conbee II issue - /dev/ttyACM0 permissions
Still RaspBee II issue - /dev/ttyACM0 permissions
Dec 15, 2020
mrstegeman
changed the title
Still RaspBee II issue - /dev/ttyACM0 permissions
Still RaspBee II issue - /dev/ttyAMA0 permissions
Dec 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I have a RaspBee II with firmware 26610700 I'd like to use with WebThings.
I've just downloaded and installed a fresh gateway, version 1.0.0, and installed it on a Raspberry Pi 3B.
I've done everything as described: added "dtoverlay=pi3-miniuart-bt" in config.txt and removed "console=tty1" from cmdline.txt; then enabled plugin with "allowAMASerial". However, it didn't suffice; the adapter was still unrecognized. I noticed messages like this in run-app.log:
ERROR : zigbee-adapter: [Error: Error: Permission denied, cannot open /dev/ttyAMA0]
so I did ls -la /dev/tty* and got:
As you can see, differently from ttyS0, ttyAMA0' group was tty (which is not among those of pi user which runs gateway); I've tried to fix permissions and give ownership to pi; nothing didn't help as the new permissions were reverted immediately.
After googling a bit, I've come to the right solution: issuing "sudo systemctl mask serial-getty@ttyAMA0" and rebooting made it.
Apparently, a login console was spawned at ttyAMA0, which is connected to the RaspBee; I guess the latter kept sending characters to login prompt, making it restart and reverting permissions (not that it would work that way anyway...).
For reference, here is the failing log:
And this the working one:
I don't know if "invalid packet" hurts, however I see it only happened once.
The text was updated successfully, but these errors were encountered: