Igel thin client openhab2 -> controller offline

I’m running openhab2 on a mini pc zotac for the moment, and everything is working.
But I’d like to run it on a Igel thin client in the future, as the zotac is getting hot from time to time so that the fan is running which is annoying ;).

So I installed debain on my igel and everything seemed to work, but when I added my usb controller Aeotec Z-Stick and configured the port /dev/ttyS0, I got a message that the controller is offline. I tried with other ports, ttyyACM0 and other, but then I only get this error OFFLINE - COMMUNICATION_ERROR.
So ttyS0 must be the right one as I get no error at least, just controller offline.

I tried many things:

EXTRA_JAVA_OPTS="-Dgnu.io.rxtx.SerialPorts=/dev/ttyUSB0:/dev/ttyS0:/dev/ttyS2:/dev/ttyACM0:/dev/ttyAMA0"

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install liblockdev1-dev

added the openhab user to both tty and dial out group…
no luck.

Anyone here who is runing openhab2 on an igel?

That’s the one I have, but I tried as well on an other Igel, same result.
IGEL UD3-430LX v4 M300C Thin-Client VIA U3400 800MHz

I think first you have to identify the correct port. Start your Igel, login, add your Aeotec Z-Stick to a USB port, after that, take a look at

dmesg 

output, you should find information about the new hardware (each time the stick is conncted to the port)

After that, if the port name is other than ttyUSB0, ttyS0, ttyS2, ttyACM0 or ttyAMA0, you have to add this name to the list (EXTRA_JAVA_OPTS).

By the way:

  • ttyS0 -> first onboard serial interface
  • ttyS2 -> third onboard serial interface
  • ttyAMA0 -> first serial interface for Raspberry
  • ttyACM0 -> first serial interface of a USB interface of type AbstractControlModel
  • ttyUSB0 -> first serial interface of a USB interface (generic type)

The names of USB sticks can differ dependent on to which port they are connected

1 Like

dmesg

115.080046] usb 4-1: new full-speed USB device number 2 using uhci_hcd
[ 115.248095] usb 4-1: New USB device found, idVendor=10c4, idProduct=ea60
[ 115.248107] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 115.248116] usb 4-1: Product: CP2102 USB to UART Bridge Controller
[ 115.248123] usb 4-1: Manufacturer: Silicon Labs
[ 115.248129] usb 4-1: SerialNumber: 0001
[ 115.271165] usbcore: registered new interface driver usbserial
[ 115.271670] usbcore: registered new interface driver usbserial_generic
[ 115.272954] usbserial: USB Serial support registered for generic
[ 115.278435] usbcore: registered new interface driver cp210x
[ 115.278690] usbserial: USB Serial support registered for cp210x
[ 115.279309] cp210x 4-1:1.0: cp210x converter detected
[ 115.388055] usb 4-1: reset full-speed USB device number 2 using uhci_hcd
[ 115.539644] usb 4-1: cp210x converter now attached to ttyUSB0
[ 118.296120] usb 4-1: usbfs: interface 0 claimed by cp210x while ‘brltty’ sets config #1
[ 118.298387] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[ 118.298423] cp210x 4-1:1.0: device disconnected

I’m not an expert with Linux, so does it mean it0s port ttyUSB0 and my stick is disconnecting it self?
I have 2 Aeotec Z-Sticks, a black (old) and a white one. I treid both with the same result.
The sticks are working, as on my mini pc the white one works without problems…

lsub gives me this with the stick plugged in:
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Without this line isn’t there:
Bus 004 Device 002: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light

I got the solution by looking at dmesg again. I removed brltty.

sudo apt-get remove --purge brltty

Now it’s working :slight_smile:

Btw the controller is on ttyUSB0

Thx, dmesg helped to find the solution :slight_smile:

Yes, obviously brltty grabbed the stick :slight_smile:
I guess you could use brltty anyway but then have to blacklist the Aeotec stick.
But if there is no need for a Braille display… :wink:

1 Like