cec_scan with pulse-eight and /dev/ttyACM0

[xeor]

Describe the issue you are experiencing

When using the cec_scan addon on an intel nuc with HAOS installed and a pulse-eight hdmi-cec adapter. I am getting this error:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[18:45:31] INFO: Starting CEC client scan...
opening a connection to the CEC adapter...
ERROR:   [            3515]	error opening serial port '/dev/ttyACM0': Operation not permitted
ERROR:   [            3515]	could not open a connection (try 1)
ERROR:   [            6350]	error opening serial port '/dev/ttyACM0': Operation not permitted
ERROR:   [            6350]	could not open a connection (try 2)
ERROR:   [            8240]	error opening serial port '/dev/ttyACM0': Operation not permitted
ERROR:   [            8240]	could not open a connection (try 3)
ERROR:   [            9499]	error opening serial port '/dev/ttyACM0': Operation not permitted
ERROR:   [            9499]	could not open a connection (try 4)
unable to open the device on port /dev/ttyACM0
ERROR:   [           10504]	could not start CEC communications
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.

I tried to start the container manually on haos with --device, like

docker run -it --device /dev/ttyACM0 --entrypoint /bin/sh homeassistant/amd64-addon-cec_scan -l
036e25bd6d10:/# echo scan | cec-client -s -d 1
opening a connection to the CEC adapter...
requesting CEC bus information ...
CEC bus information
===================
device #0: TV
address:       0.0.0.0
active source: no
vendor:        Samsung
osd string:    TV
....

works like a charm.

If I inspect the container cec_scan starts, it mounts /dev as a bind-mount.. I tried

docker run -it -v /dev:/dev --entrypoint /bin/sh homeassistant/amd64-addon-cec_scan -l
2b3169bbd099:/# echo scan | cec-client -s -d 1
opening a connection to the CEC adapter...
ERROR:   [            3513]     error opening serial port '/dev/ttyACM0': Operation not permitted
ERROR:   [            3513]     could not open a connection (try 1)
ERROR:   [            6347]     error opening serial port '/dev/ttyACM0': Operation not permitted
ERROR:   [            6347]     could not open a connection (try 2)
ERROR:   [            8237]     error opening serial port '/dev/ttyACM0': Operation not permitted
ERROR:   [            8237]     could not open a connection (try 3)
ERROR:   [            9497]     error opening serial port '/dev/ttyACM0': Operation not permitted
ERROR:   [            9497]     could not open a connection (try 4)
unable to open the device on port /dev/ttyACM0
ERROR:   [           10502]     could not start CEC communications
2b3169bbd099:/# ls -l /dev/ttyACM0 
crw-rw----    1 root     audio     166,   0 Aug  2 16:29 /dev/ttyACM0

An alternative would be to use use --privileged. That would work without using --device and using bind-mount like now.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

CEC Scanner

What is the version of the add-on?

3.0

Steps to reproduce the issue

See description

System Health information

There are currently no repairs available

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

No response

Additional information

No response

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[xeor]

This is still a problem.. New install, newest versions, new pc.

Is this plugin working for anyone?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.