08-09-2015, 09:17 AM
Installed yesterday pilight stable 7.0 with a arduino nano clone using the latest pilight firmware for the nano from github. Works ootb - great!
But I hit the same problem like dc6jn - see two posts above.
I've got two serial USB devices connected (JeeLink and Nano) and can't be sure after reboot, which one will be /dev/ttyUSB0 and which one /dev/ttyUSB1.
I tried to address the correct nano in pilight hardware config clause using both
a) /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0 which is a symlink to /dev/ttyUSB1 created by the Debian Linux kernel
or
b) /dev/ttyUSB99 which is also a symlink to /dev/ttyUSB1 created by udevd using the following rule: SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", SYMLINK+="ttyUSB99"
But sadly - both approaches do not work. pilight won't start as long as I don't address the nano directly using /dev/ttyUSB1 (which could be the Jeelink after a reboot) :-(
Any chance to fix this?
Tobi
But I hit the same problem like dc6jn - see two posts above.
I've got two serial USB devices connected (JeeLink and Nano) and can't be sure after reboot, which one will be /dev/ttyUSB0 and which one /dev/ttyUSB1.
I tried to address the correct nano in pilight hardware config clause using both
a) /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0 which is a symlink to /dev/ttyUSB1 created by the Debian Linux kernel
or
b) /dev/ttyUSB99 which is also a symlink to /dev/ttyUSB1 created by udevd using the following rule: SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", SYMLINK+="ttyUSB99"
But sadly - both approaches do not work. pilight won't start as long as I don't address the nano directly using /dev/ttyUSB1 (which could be the Jeelink after a reboot) :-(
Any chance to fix this?
Tobi