- Hardware: Raspi 3b+
- OS: Linux openhab 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux
- Java Runtime Environment: java-common 0.58
*Environment: openHAB 2.4.0.RC1 Milestone Build
*openHAB binding: onewire:digitalio2 by Jan N. Klug
*Oweserver: 3.1p5-1 (stretch standard apt installed)
One Onewire bus with multiple DS18B20 temp sensors, DS2438 humidity sensors, DS2413 gpio relais controller
The Onewire setup was working well unit I attached the DS2413 gpio relais controller.
DS2413 is correctly detected in the Paper UI Inbox.
The openHAB thing type is “digitalio2” and it has two channels. The channel are configured to OUTPUT channels, because I’d like to switch an attached relais card.
The problem starts when I use e.g. the Paper UI control dashboard to toggle that DS2413 channel status e.g. from OFF to ON I cause a reproducible “crash” the the whole onewire binding.
The effect is exactly the following:
I set the onewire-binding log level to TRACE
I see a lot of sensor communication logging flying though the log tail.
I watch the log tail while toggling the DS2413 channel status
The DS2413 toggle is seen in the log but not executed
the logging is completely stopped and the whole onewire communication is halted
INFO_A: for information, at the same time I verify the correct working of the owserver by sending a
“owwrite 3A.812B00000000/PIO.A 1”
That is still working fine and the relais-A is activated.
INFO_B: tested with two DS2413 boards. Both show the same crashing behavior.
INFO_C: the “crash” situation is recovering by restarting the openhab2 service.
Is anybody successfully using this Dallas Onewire chip with openHAB? Any hint is very much welcome.