Actually I do not have any problem however, something really strange has happened when I moved hassio from lab to prod that is, from a R-Pi2B to a R-Pi3B+.
I am making use of a RFXCom RFXtrx433E device. I followed the installation steps and so I configured hassio by searching for the device on the /dev folder. There I found it and so I configured it under configuration.yaml as follows:
rfxtrx:
device: /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A11D28G3-if00-port0
Nothing strange so far that is, the whole path was found as described.
The strange thing came when I moved the whole configuration as-is to the R-Pi3 as it was on the R-Pi2. What I found is that there is no trace of /dev/serial path but it still works. Here you go the content of the /dev folder on the R-Pi3:
core-ssh:/dev# ls -la
total 423
drwxr-xr-x 5 root root 340 Sep 26 07:31 .
drwxr-xr-x 1 root root 4096 Sep 26 07:31 ..
lrwxrwxrwx 1 root root 13 Sep 26 07:31 fd -> /proc/self/fd
crw-rw-rw- 1 root root 1, 7 Sep 26 07:31 full
-rwxr-xr-x 1 root root 428228 Aug 27 19:33 init
drwxrwxrwt 2 root root 40 Sep 26 07:31 mqueue
crw-rw-rw- 1 root root 1, 3 Sep 26 07:31 null
lrwxrwxrwx 1 root root 8 Sep 26 07:31 ptmx -> pts/ptmx
drwxr-xr-x 2 root root 0 Sep 26 07:31 pts
crw-rw-rw- 1 root root 1, 8 Sep 26 07:31 random
drwxrwxrwt 2 root root 40 Sep 26 07:31 shm
lrwxrwxrwx 1 root root 15 Sep 26 07:31 stderr -> /proc/self/fd/2
lrwxrwxrwx 1 root root 15 Sep 26 07:31 stdin -> /proc/self/fd/0
lrwxrwxrwx 1 root root 15 Sep 26 07:31 stdout -> /proc/self/fd/1
crw-rw-rw- 1 root root 5, 0 Sep 26 07:31 tty
crw-rw-rw- 1 root root 1, 9 Sep 26 07:31 urandom
crw-rw-rw- 1 root root 1, 5 Sep 26 07:31 zero
And this is the rfxcom section on the configuration.yaml file on the R-Pi3:
rfxtrx:
device: /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A11D28G3-if00-port0
So how could it be that it works?