Finding USB port name for serial gateway running homeassistant on an Intel Nuc

[chorob]

Hello,

I recently switched from a raspi to an intel nuc. My serial gateway worked well with the raspi. I am struggling to figure out the config parameters for my nuc. After a lot of google searching, I can't find it but am probably missing something easy.

Below is the default. I cannot find the right terminal command for the nuc to show the connected devices. Any ideas? Thanks!

device: '/dev/ttyUSB0'

[mfalkvidd]

@chorob the following commands can be useful:

lsusb
ls /dev/

Disconnect the serial gateway and run the commands. Then connect the serial gateway and run the commands again. Compare the output. The difference should be the serial gateway.

You can also run

dmesg

after connecting the serial gateway. The last few lines should show a message about what name the gateway got.

[chorob]

@mfalkvidd Thanks for the tips. Still trying to figure it out.

This was the output of your first suggestion:

Unplugged

➜ ~ lsusb
Bus 001 Device 003: ID 8087:0a2a
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 05e3:0610
Bus 002 Device 001: ID 1d6b:0003

Plugged in
➜ ~ lsusb
Bus 001 Device 003: ID 8087:0a2a
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 05e3:0610
Bus 001 Device 006: ID 1a86:7523
Bus 002 Device 001: ID 1d6b:0003

Output of our last suggestion.

[631437.779324] usb 1-3: new full-speed USB device number 6 using xhci_hcd

I have tried different combinations using device 6 and it still is not validating my config file. Any ideas?

Tried
device: '/dev/ttyUSB6'
device: '/dev/ttyACM6'
device: '/dev/tty1a86:7523'

Thanks!

[mfalkvidd]

@chorob try ls /dev/ as well

[chorob]

@mfalkvidd

unplugged

core fd full init kmsg mqueue null ptmx pts random shm stderr stdin stdout tty urandom zero

plugged in
core fd full init kmsg mqueue null ptmx pts random shm stderr stdin stdout tty urandom zero

Thanks!

[mfalkvidd]

@chorob strange. This is my output before plugging in:

ls /dev
autofs           full       loop3             mqueue              ram12  random     tty0   tty2   tty30  tty41  tty52  tty63                vcio    vcsa3
block            fuse       loop4             net                 ram13  raw        tty1   tty20  tty31  tty42  tty53  tty7                 vc-mem  vcsa4
btrfs-control    gpiochip0  loop5             network_latency     ram14  rfkill     tty10  tty21  tty32  tty43  tty54  tty8                 vcs     vcsa5
bus              gpiomem    loop6             network_throughput  ram15  serial0    tty11  tty22  tty33  tty44  tty55  tty9                 vcs1    vcsa6
cachefiles       hwrng      loop7             null                ram2   shm        tty12  tty23  tty34  tty45  tty56  ttyAMA0              vcs2    vhci
char             initctl    loop-control      ppp                 ram3   snd        tty13  tty24  tty35  tty46  tty57  ttyMySensorsGateway  vcs3    watchdog
console          input      mapper            ptmx                ram4   spidev0.0  tty14  tty25  tty36  tty47  tty58  ttyprintk            vcs4    watchdog0
cpu_dma_latency  kmsg       mem               pts                 ram5   spidev0.1  tty15  tty26  tty37  tty48  tty59  ttyUSB20             vcs5    zero
cuse             log        memory_bandwidth  ram0                ram6   stderr     tty16  tty27  tty38  tty49  tty6   uhid                 vcs6
disk             loop0      mmcblk0           ram1                ram7   stdin      tty17  tty28  tty39  tty5   tty60  uinput               vcsa
fb0              loop1      mmcblk0p1         ram10               ram8   stdout     tty18  tty29  tty4   tty50  tty61  urandom              vcsa1
fd               loop2      mmcblk0p2         ram11               ram9   tty        tty19  tty3   tty40  tty51  tty62  vchiq                vcsa2

and after:

ls /dev
autofs           full       loop3             mqueue              ram12  random     tty    tty19  tty3   tty40  tty51  tty62                urandom  vcsa1
block            fuse       loop4             net                 ram13  raw        tty0   tty2   tty30  tty41  tty52  tty63                vchiq    vcsa2
btrfs-control    gpiochip0  loop5             network_latency     ram14  rfkill     tty1   tty20  tty31  tty42  tty53  tty7                 vcio     vcsa3
bus              gpiomem    loop6             network_throughput  ram15  serial     tty10  tty21  tty32  tty43  tty54  tty8                 vc-mem   vcsa4
cachefiles       hwrng      loop7             null                ram2   serial0    tty11  tty22  tty33  tty44  tty55  tty9                 vcs      vcsa5
char             initctl    loop-control      ppp                 ram3   shm        tty12  tty23  tty34  tty45  tty56  ttyAMA0              vcs1     vcsa6
console          input      mapper            ptmx                ram4   snd        tty13  tty24  tty35  tty46  tty57  ttyMySensorsGateway  vcs2     vhci
cpu_dma_latency  kmsg       mem               pts                 ram5   spidev0.0  tty14  tty25  tty36  tty47  tty58  ttyprintk            vcs3     watchdog
cuse             log        memory_bandwidth  ram0                ram6   spidev0.1  tty15  tty26  tty37  tty48  tty59  ttyUSB0              vcs4     watchdog0
disk             loop0      mmcblk0           ram1                ram7   stderr     tty16  tty27  tty38  tty49  tty6   ttyUSB20             vcs5     zero
fb0              loop1      mmcblk0p1         ram10               ram8   stdin      tty17  tty28  tty39  tty5   tty60  uhid                 vcs6
fd               loop2      mmcblk0p2         ram11               ram9   stdout     tty18  tty29  tty4   tty50  tty61  uinput               vcsa

the difference being serial.

So it seems your device does not create any serial port. Strange.

[mfalkvidd]

@chorob see if the suggestion in https://unix.stackexchange.com/questions/189896/testing-qinheng-electronics-hl-340-usb-serial-adapter works on your Nuc. (sudo modprobe ch341)

[chorob]

@mfalkvidd

sudo modprobe ch341
modprobe: FATAL: Module ch341 not found in directory /lib/modules/4.8.17-yocto-standard

Must be a package I need to install? I just used the standard hass.io image for the NUC.

Thanks for your help on this!

[mfalkvidd]

@chorob what linux distro is the hass image based on?

Modules are installed differently depending on which linux distro, and I have no experience with Hass so I don't know.

Maybe it is easier to switch Arduino to one with a ftdi232 chip.

[chorob]

@mfalkvidd the image is based on resin.io. I will do some more digging but your advice might be the best option. I really appreciate your help on this. I will report back what I find. Thanks!