Open coast3r opened 3 years ago
Hi,
I'm not using docker for this myself. I've found this issue on usb pass through, but that does not seem to match your case since you mention it works from a commend line. Could it be that homebridge runs under a homebridge user with different rights?
Roy
Thanks for the reply. Docker is definitely the big variable for me. I'll look into this more when I have time and try to find more information. As far as I can tell, the docker local user has access to the serial port, and when I've run a command line inside my docker container (user is root; might not be the same as the user running the plugin) the serial port is available.
After more testing, this is still not working. I don't want to leave this open, since the problem likely lies with Docker. This issue will get another look, but it won't be for a while as I'm out of ideas.
The problem definitely lies inside Docker. Maybe the OS inside Docker. Not able to get it running right now. It does work when installed outside Docker. Today I tried running on the official Homebridge image, and I have a successful serial connection, I see power controls in HomeKit and a volume control in Homebridge. Want to make sure I'm not missing anything. Are there controls for input?
Homebridge runs on a raspberry pi under Docker. Using an FTDI serial adapter. Tested the serial connection to my receiver on the host system, and inside Docker from a command line. (Serial port is ttyUSB0). The plugin displays the following error in the homebridge log: [Receiver] Error when opening serialport: Error: Error: Permission denied, cannot open /dev/ttyUSB0
if there is elsewhere to look for clues, let me know.