Enocean RS485 Error / openhab Restarts

1

Hey guys. Now its getting weird for me and I need some help.
I am running an Raspberry Pi 4 with 2 USB-Connections:

1: to my eltako FGW14-USB
1: deconz dresden-elektronik USB
Raspberry Pi 4 on openhabian 3.3.0

The pi is connected via LAN and no here is the werid thing:

When the pi comes up. The used USB Path /dev/ttyUSB0 changes to USB1 or from USB1 to USB0.

The Gateway-Thing comes online. Everything works like a charm.
When I us some Rollershutter actors (ELTAKO FSB14) the rollershuter works. But after a couple of minutes the Gateway becomes Offline.

Either I only have to change the USB Port again to USB0

image
image771×761 15 KB

or the whole openhab service restarts.

I am pretty sure there must be a bug somewhere, or I did missconfigure something.
But I am able to move all shutters, and all lights.

Maybe i did forget anything important. But whenever you guys need more information, pls let me know.

Thank you very much

2

When you have more than one USB serial device, it’s basically a trick of the timing which one of two ends up on ttyUSB0 and ttyUSB1. They could theoretically swap each and every time the system reboots.

There are a number of posts here and online about how to create a static location. Here’s one: linux - How to bind USB device under a static name? - Unix & Linux Stack Exchange

3

I will bind the ports to static paths. But for me this doesn’t explain, why the gateway goes offline, or even more… The whole openhab service crashs.
Any ideas? Or better any hints of logs where I could find out what’s the problem?

4

I don’t have any advice for the rest. I don’t use any of these technologies. I’d look in the openhab.log and syslog around the time that OH crashes but I’ve nothing more specific than that.

5

As @rlkoshak mentioned have a look into the openhab.log. I would expect to see message about openhab related crashes in that logfile.
The systemlog should show logs about problems on system level.

I also would check the output of sudo dmesg and sudo journalctl

6

Good Morning everyone.
I installed the binding yesterday and since i did this the service didnt crashed anymore.
I even were able to use the rollershutters and the system stayed online. :smile:

I will watch this today and use my shutters whenever i can. Hopefully this “easy” solution fix all my worries. :smiley:
Have a good day everyone!

Marcel

7

Hello everyone.
Now after testing a bit i can say: it works much better than before, but is still not 100% solved.

image
image1772×124 28.7 KB

The path to usb now is /dev/ttyUSBEnocean which works quite well.
When using a Rollersthutter the Gateway-Thing still goes offline for a moment.
(See attached Screenshot)

8

And without doing anything suddenly this happens:

Nov 29 12:55:57 openhabian karaf[31279]: Write action failed! Eingabe-/AusgabefehlerWrite action failed! Eingabe-/AusgabefehlerWrite action failed! Eingabe>
Nov 29 12:55:57 openhabian karaf[31279]: # A fatal error has been detected by the Java Runtime Environment:
Nov 29 12:55:57 openhabian karaf[31279]: #
Nov 29 12:55:57 openhabian karaf[31279]: # SIGSEGV (0xb) at pc=0xb6d7bdec, pid=31279, tid=14700
Nov 29 12:55:57 openhabian karaf[31279]: #
Nov 29 12:55:57 openhabian karaf[31279]: # JRE version: OpenJDK Runtime Environment (11.0.16+8) (build 11.0.16+8-post-Raspbian-1deb11u1)
Nov 29 12:55:57 openhabian karaf[31279]: # Java VM: OpenJDK Server VM (11.0.16+8-post-Raspbian-1deb11u1, mixed mode, g1 gc, linux-)
Nov 29 12:55:57 openhabian karaf[31279]: # Problematic frame:
Nov 29 12:55:57 openhabian karaf[31279]: # C [libpthread.so.0+0xadec] __pthread_mutex_unlock_usercnt+0x4
Nov 29 12:55:57 openhabian karaf[31279]: #
Nov 29 12:55:57 openhabian karaf[31279]: # No core dump will be written. Core dumps have been disabled. To enable core dumping, try “ulimit -c unlimited” b>
Nov 29 12:55:57 openhabian karaf[31279]: #
Nov 29 12:55:57 openhabian karaf[31279]: # An error report file with more information is saved as:
Nov 29 12:55:57 openhabian karaf[31279]: # /var/lib/openhab/hs_err_pid31279.log
Nov 29 12:55:57 openhabian karaf[31279]: #
Nov 29 12:55:57 openhabian karaf[31279]: # If you would like to submit a bug report, please visit:
Nov 29 12:55:57 openhabian karaf[31279]: # Unknown
Nov 29 12:55:57 openhabian karaf[31279]: #
Nov 29 12:55:57 openhabian systemd[1]: openhab.service: Main process exited, code=killed, status=6/ABRT
Nov 29 12:55:57 openhabian systemd[1]: openhab.service: Failed with result ‘signal’.
Nov 29 12:55:57 openhabian systemd[1]: openhab.service: Consumed 4h 22min 2.041s CPU time.
Nov 29 12:56:02 openhabian systemd[1]: openhab.service: Scheduled restart job, restart counter is at 2.
Nov 29 12:56:02 openhabian systemd[1]: Stopped openHAB - empowering the smart home.
Nov 29 12:56:02 openhabian systemd[1]: openhab.service: Consumed 4h 22min 2.041s CPU time.
Nov 29 12:56:02 openhabian systemd[1]: Started openHAB - empowering the smart home.
~

9

hmm sadly nobody can help?

10

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.