-
Notifications
You must be signed in to change notification settings - Fork 582
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
Zigbee2MQTT:error Error while opening serialport #221
Comments
Please see This project is dormant. I'm not saying your problem will necessarily be solved by switching to SensorsIot/IOTstack but zigbee2mqtt has had more recent work done on that repo. A word to the wise, however. The new repo is in the middle of switching to a new menu structure and there are a lot of problems being reported. To minimise the risk of confusing a zigbee2mqtt issue with an artefact of the new menu, I'd recommend
then I'd nose around There was also at least one issue in the new repo on this so maybe search the issues for zigbee2mqtt. Hope this helps. |
1 similar comment
Please see This project is dormant. I'm not saying your problem will necessarily be solved by switching to SensorsIot/IOTstack but zigbee2mqtt has had more recent work done on that repo. A word to the wise, however. The new repo is in the middle of switching to a new menu structure and there are a lot of problems being reported. To minimise the risk of confusing a zigbee2mqtt issue with an artefact of the new menu, I'd recommend
then I'd nose around There was also at least one issue in the new repo on this so maybe search the issues for zigbee2mqtt. Hope this helps. |
See if Issue 167 helps. |
fixed spelling mistake Zigbee2MQTT
Hello,
Not sure if this is an issue from IoTStack or zigbee2mqtt, but here it goes:
I'm trying to use a CC2652RB development stick - but the zigbee2mqtt keeps restarting every minute or so. It isn't able to access the stick, which is recognized by the OS as /dev/ttyUSB0. (BTW, modemmanager isn't installed on this system)
Initially, I changed the the /home/pi/IOTstack/volumes/zigbee2mqtt/data/configuration.yaml to:
But this didn't work, so after further reading and troubleshooting I understood that, when on a stack, the docker container isn't able to access directly the /dev/ttyUSB0 so a special procedure is required to make it available to it. So I followed the procedure described in zigbee2mqtt.io.
After this, I had a new link to the original device, that would be supposed to be accessible to the zigbee2mqtt docker container, called /dev/cc2652:
After some restarts and reboots, the log shown exactly the same error: not possible to read the stick.
I troubleshooted the procedure scripts that supposedly will make the new device available to the docker container and realized there is something that isn't right:
The script is:
And it fails because firstly, it starts by getting the zigbee2mqtt docker container identifier:
docker ps -a --no-trunc | grep koenkk/zigbee2mqtt | head -1 | awk '{print $1}'
Then, the script is supposed to add the permissions to that container:
echo "c $dmajor:$dminor rwm" > /sys/fs/cgroup/devices/docker/$CID/devices.allow
But, the contained ID found previously never exists in /sys/fs/cgroup/devices/docker/, so the permissions aren't added.
So, is it expected that the CID of a docker container, obtained by the
docker ps -a --no-trunc
command isn't available in the/sys/fs/cgroup/devices/docker/
directory?How to make this work?
Cheers,
Joaoabs
The text was updated successfully, but these errors were encountered: