Unable to access serial ports

[ldrrp]

I am having no luck under docker

• Platform information:
  • Hardware: amd64 docker image
  • OS: Debian 10
  • Java Runtime Environment: Whatever docker snapshot has
  • openHAB version: 2.5.0
• Issue of the topic:

Unable to detect nortek dongle for either communication protocol. "Offline - Communication Error"

The dropdown under the controller/coordinator does not show any serial dropdown like i see on videos. Im guessing something is missing. I have read over and over all the docs with no luck. Here is what i tried

• Added openhab to groups on host: openhab tty dialout audio bluetooth
• Confirmed serial device is using proper driver "cp210x" with "dmesg | grep tty" [ 5.148772] usb 1-1.1.3: cp210x converter now attached to ttyUSB0 [ 5.160085] usb 1-1.1.3: cp210x converter now attached to ttyUSB1
• Added EXTRA_JAVA_OPTS=-Dgnu.io.rxtx.SerialPorts=/dev/ttyUSB0:/dev/ttyUSB1
• Docker device passed: --device=/dev/ttyUSB0 and --device=/dev/ttyUSB0
• Alternatively tried passing devices as volume path as well seperately
• Added zigbee as Port=/dev/ttyUSB1, flow control=software, baud=57600
• Checked to see if docker can see the file using "docker exec -it openhab ls -lisa /dev/ttyUSB* 11817 0 crw-rw-rw- 1 root dialout 188, 0 Dec 30 13:00 /dev/ttyUSB0 16696 0 crw-rw-rw- 1 root dialout 188, 1 Dec 30 13:00 /dev/ttyUSB1
• Checked docker uid and gid, both are 1000 (openhab)
• Changed udev rules to 666 for ttyUSB[0-9]
• Started home assistant docker image and zwave/zigbee both work and shows up with --device

Logs:

==> /srv/dev-disk-by-id-md-name-omv-Raid-part1/openhab/userdata/logs/events.log <==
2019-12-30 09:15:48.851 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:d407648b' changed from UNINITIALIZED to INITIALIZING
2019-12-30 09:15:48.858 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:d407648b' has been updated.
2019-12-30 09:15:48.860 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:d407648b' has been updated.
2019-12-30 09:15:48.861 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:d407648b' has been updated.
2019-12-30 09:15:48.864 [me.event.ThingUpdatedEvent] - Thing 'zigbee:coordinator_ember:d407648b' has been updated.
2019-12-30 09:15:48.865 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:d407648b' changed from INITIALIZING to UNKNOWN
2019-12-30 09:15:48.865 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:coordinator_ember:d407648b changed to UNKNOWN.

==> /srv/dev-disk-by-id-md-name-omv-Raid-part1/openhab/userdata/logs/openhab.log <==
2019-12-30 09:15:49.864 [ERROR] [zigbee.dongle.ember.ZigBeeDongleEzsp] - Unable to open Ember serial port

==> /srv/dev-disk-by-id-md-name-omv-Raid-part1/openhab/userdata/logs/events.log <==
2019-12-30 09:15:49.865 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:d407648b' changed from UNKNOWN to OFFLINE: Failed to open communications port
2019-12-30 09:15:49.866 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:d407648b' changed from OFFLINE: Failed to open communications port to OFFLINE (COMMUNICATION_ERROR)

==> /srv/dev-disk-by-id-md-name-omv-Raid-part1/openhab/userdata/logs/openhab.log <==
2019-12-30 09:15:50.867 [ERROR] [zigbee.dongle.ember.ZigBeeDongleEzsp] - Unable to open Ember serial port

==> /srv/dev-disk-by-id-md-name-omv-Raid-part1/openhab/userdata/logs/events.log <==
2019-12-30 09:15:50.868 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:d407648b' changed from OFFLINE (COMMUNICATION_ERROR) to OFFLINE: Failed to open communications port
2019-12-30 09:15:50.869 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:d407648b' changed from OFFLINE: Failed to open communications port to OFFLINE (COMMUNICATION_ERROR)

==> /srv/dev-disk-by-id-md-name-omv-Raid-part1/openhab/userdata/logs/openhab.log <==
2019-12-30 09:15:55.869 [ERROR] [zigbee.dongle.ember.ZigBeeDongleEzsp] - Unable to open Ember serial port

==> /srv/dev-disk-by-id-md-name-omv-Raid-part1/openhab/userdata/logs/events.log <==
2019-12-30 09:15:55.870 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:d407648b' changed from OFFLINE (COMMUNICATION_ERROR) to OFFLINE: Failed to open communications port
2019-12-30 09:15:55.871 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:d407648b' changed from OFFLINE: Failed to open communications port to OFFLINE (COMMUNICATION_ERROR)

[ldrrp]

https://www.bountysource.com/issues/86212593-unable-to-access-serial-ports

[ldrrp]

Troubleshooting here https://community.openhab.org/t/docker-snapshot-not-reading-my-serial-ports/88974/5

[wborn]

What's the exact command you use for creating the container? Does the issue also occur when you use one of the other distributions such as APT or the .tar.gz?

[mindstorms6]

I'm not sure if it's related - I recently had some issues with Openhab via Docker where Openhab couldn't hit /dev/ttyACM0 - but for reasons that weren't clear to me.

After some explore around the forum, there's rumor that the openhab user must also be a member of the group tty in addition to dialout

As a hack - did the following in my Dockerfile (which uses of course FROM openhab:2.5.0)

RUN sed -i '2iadduser openhab tty' start.sh

This adds the command adduser openhab tty to the start.sh file (inherited from this repo) at line 2

This has seemingly worked for me (inspiration from the current entrypoint.sh file)

I would have expected to see "permission denied" somewhere - but no such entry was in my logs.

If this same "hack" works for you, I'll submit a PR to the repo proper.

It was all working before, so I'm not sure if this is actually a root cause or just random luck.

Let me know!

[ldrrp]

Sorry for late reply. I kind of gave up on openhab and moved to home assistant in docker because it picks up the tty devices.

My setup, Open Media Vault 4.x latest, openhab docker latest. I tried with multiple dongles.

@mindstorms6 You can see from the forum the issues we faced. i did try multiple ways of giving group access. Even down to setting the host os to make the tty devices 777 permission on boot. I was even able to hit it from inside openhab docker image but openhab was not able to see it.

@wborn I no longer have openhab setup but the gui in omv was used to make it, with everything being able to be set from it including custom parameters.

Everything is the same for home assistant and it works so i wont be going any further with troubleshooting this for openhab as i need to get my home back up after switching from smartthings

[wborn]

I no longer have openhab setup but the gui in omv was used to make it

Most likely the issue is that the serial libraries cannot not be properly loaded on OpenMediaVault because it doesn't allow the serial libraries in the temp dir to be set as executable since it mounts filesystems using the noexec flag.

There's also a YouTube video about how to remove the noexec flag to fix similar issues when using Plex/OpenVPN with Docker on OMV.

See also:

• https://github.com/openhab/openhab-docker/issues/286
• https://github.com/openhab/openhab-docker/issues/287

[ldrrp]

@wborn you should claim the bounty https://www.bountysource.com/issues/86212593-unable-to-access-serial-ports