[dc6jn]

Why don't you just make sure your fix the ttyUSB assignments?

Simply because this arbitrary assignment can change over time. If you attach more than one adapter to you board you will get into trouble with different device names over time.
If you want to be sure that this and only this very special adapter gets your preferred and configured device name than it's better to use a udev rule and fix it.
In my case after installation the 2 attached adapters changed their kernel name (ttyUSBX), and only pilight was configured to a fixed ttyUSB1. The other program was able to find the right device name because it is using a symbolic link created by udev. One might get after reboot the same address than before, but you can not be sure, and if you connect our device later all chances are lost.
So for me its the only logical solution to give device names depending on some unique features like the ftdi serial number, and its extremely simple. Just insert a line like
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="XXXXXX", SYMLINK+="nano0"
to you udev rules and aou are done.
On the other hand there is no need to check for a valid device name with you implemented table because milliseconds later you would get an serious error if you errorneous configured device does not exist (fopen would fail), time enough to check the config...

For me this is only an annoying check with less to no significance.
regards

[curlymo]

Can people try the pilight USB nano firmware on the Arduino Uno? The latest nightly code should work for both.

[tpm88]

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

[curlymo]

Install the latest nightly. It does have a hardcoded settings checker.

[tpm88]

Install the latest nightly. It does have a hardcoded settings checker.

Thanks. Now both device mappings (/dev/serial/by-id/... and udev link) are working.

[mkloeffer]

Hi curlymo,

I have one problem using a Nano with a 433 sender/receiver. Used the latest version to flash the nano. Now to my problem:
- Sending is working fine
- Receiving is not working for me

I used the same sender receiver combo on a raspi with GPIO and it worked before, do you have any ideas?

Thanks, Michael

[curlymo]

No, should work. Tried reflashing?

[mkloeffer]

Reflashing did not help, but I noticed that it works for some time and then stops... I figured out that the receiver part "hangs" in some situations, mostly after stopping and restarting... Any way to provide a log so you can look at it?

[curlymo]

Did you buy the nano from me?

[mkloeffer]

No, bought it on ebay