Addon wont start because /dev/ttyZ2M is read only about hassio-zigbee2mqtt HOT 7 CLOSED

Thanks for the report. This indeed also fixed my issue.

from hassio-zigbee2mqtt.

@KennieNL I will try to make a fix in 1.17.1-2 by updating the default to your suggestion for Socat.

from hassio-zigbee2mqtt.

The /share/zigbee2mqtt/ directory is used for data, logging and configuration. It might make sense to expose the serial device from /tmp/ttyZ2M instead?

from hassio-zigbee2mqtt.

Might be better to expose in /tmp/ yeah. But since it was late I didn't want to run into any other pemission issues.

I'll leave that for the devs to decide :)

from hassio-zigbee2mqtt.

So it seems like this helps for those using socat, but for people who use the device directly (or passed through to the VM) we're out of luck until the supervisor change gets reverted right?

My instance is failing to open /dev/ttyUSB0 with an "Operation not permitted" error which I assume is due to the same supervisor change.

from hassio-zigbee2mqtt.

My instance is failing to open /dev/ttyUSB0 with an "Operation not permitted" error which I assume is due to the same supervisor change.

I have this problem too. The supervisor identifies devices by the major device number in /dev. But on my hardware, these numbers are different from those built into the supervisor. For example, my /dev/ttyAML2 has a major of 243 and falls into the audio devices, but in the supervisor's major 244 is searched for ttyAML devices.

from hassio-zigbee2mqtt.

I'm not sure if this issue is the correct place to report the problems with usb as those are related to the supervisor update. changes in the add-on won't be able to fix.

from hassio-zigbee2mqtt.