Once more I got the /dev/ttyUSB0 writing permission failure, though my linux box was up all nite. Is it the restarting of the zigbee2mqqt docker container at the origin of that failure?
fl@Satellite-Z930:~$ test -w /dev/ttyUSB0 && echo success || echo failure
failure
failure
failure: command not found
fl@Satellite-Z930:~$ sudo chown fl /dev/ttyUSB0
[sudo] password for fl:
fl@Satellite-Z930:~$ test -w /dev/ttyUSB0 && echo success || echo failure
success
I need to get the effect of sudo chown fl /dev/ttyUSB0 permanent .How do I achieve that?
Is there some new error log?
fl@Satellite-Z930:~$ docker compose restart zigbee2mqtt
fl@Satellite-Z930:~$ sudo docker compose logs --tail 100 zigbee2mqtt
fl@Satellite-Z930:~$
Yes! The FATAL error is back. How come this has to be fixed everytime there is the /dev/ttyUSB0 writing permission failure?
*** to be done: ***
A. fix fatal error, and new run, see results, if ok go to zigbee2mqqt UI and try pairing
B. If not:
verify /dev/ttyUSB0 writing permission failure
and go back to A