OneWire binding stops working

[peloy (Eloy)]

Hello, brand new user here!

Trying to get a stable OneWire integration, which has been stable for more than a decade on the home automation software I am migrating from (MisterHouse).

The binding works fine for a few hours and then it just stops working… I have OneWire logging at the TRACE level, I see a continuous stream of log messages, until they stop. Then the binding stops working (no more reads from the OneWire devices).

[...]
2026-03-12 14:22:46.389 [TRACE] [ternal.handler.OwserverBridgeHandler] - onewire:basic:a8fc3d7c65:28_154BA2020000 initialized, refreshing
2026-03-12 14:22:46.389 [TRACE] [ternal.handler.OwserverBridgeHandler] - refresh: getting handler for onewire:basic:a8fc3d7c65:28_B844A2020000 (1 to go)
2026-03-12 14:22:46.389 [TRACE] [ternal.handler.OwserverBridgeHandler] - onewire:basic:a8fc3d7c65:28_B844A2020000 initialized, refreshing
2026-03-12 14:22:46.389 [TRACE] [internal.owserver.OwserverConnection] - owServerConnection already open, skipping input buffer
2026-03-12 14:22:46.389 [TRACE] [internal.owserver.OwserverConnection] - wrote: messageType READ, size 53, controlFlags 0x00000104, payload ‘uncached/99.000000000002/dia’
2026-03-12 14:22:46.483 [TRACE] [internal.owserver.OwserverConnection] - read: return code 12, size 36, controlFlags 0x00000104, payload ’ 0’
2026-03-12 14:22:46.483 [TRACE] [ternal.handler.OwserverBridgeHandler] - updated onewire:owserver:a8fc3d7c65:garage_centurion_dia to 0
2026-03-12 14:35:23.040 [WARN ] [l.internal.handler.UpnpServerHandler] - Cannot serve media from server myth: MythTV AV Media Server, no renderer selected

Something similar happens with the IKEA TRÅDFRI binding… it works for a while and then it just stops. It’s not the focus of this post but I mention it in case it’s related/relevant.

Any suggestions on what component’s logging to increase to try to find a clue about what is causing this?

Thanks in advance for any pointers.

==================================

Platform information:

• • Hardware: x86/4 GBytes RAM/plenty available storage
  • OS: Ubuntu 24.04
  • Java Runtime Environment: OpenJDK Runtime Environment (build 21.0.10+7-Debian-1deb13u1)
  • openHAB version: 5.1.3 running on Docker

• Configuration:

  Thing onewire:owserver:a8fc3d7c65 “OW Server” [network-address=“10.123.1.1”, port=4304] {
Channels:
Type owfs-number : crawlspace_centurion_temperature “Crawlspace Centurion Temperature” [path=“99.000000000003/temperature”]
Type owfs-number : backporch_centurion_temperature “Back Porch Centurion Temperature” [path=“99.000000000004/temperature”]
Type owfs-number : garage_centurion_dia “Garage Centurion Door Sensor” [path=“uncached/99.000000000002/dia”, refresh=30]
}

  Number Garage_Door_Status “Garage Door Status” (Garage) [Position, Status]

• Related rules:

  configuration: {}
  triggers:
  
  id: “1”
  configuration:
  itemName: Garage_Door_Status
  type: core.ItemStateChangeTrigger
  conditions: 
  
  actions:
  
  inputs: {}
  id: “2”
  configuration:
  type: application/vnd.openhab.dsl.rule
  script: >
  // If sensor is 1 (Open), turn LED ON. If 0 (Closed), turn LED OFF.
  
  if (Garage_Door_Status.state == 1) {
    Garage_Hallway_Keypad_Button_A.sendCommand(ON)
    logInfo("InsteonSync", "Garage door state changed to 1. Keypad LED updated.")
  } else {
    Garage_Hallway_Keypad_Button_A.sendCommand(OFF)
    logInfo("InsteonSync", "Garage door state changed to 0. Keypad LED updated.")
  }
  
  type: script.ScriptAction
  

Nothing out of the ordinary in Docker logs.

[peloy (Eloy)]

This issue has been solved. The solution was to uninstall the AndroidTV binding, which for some reason (a bug, most likely), was exhausting the thing handler thread pool and preventing from running scheduled tasks from other bindings (in my case, the OneWire binding).

See the following post for details:

AndroidTV binding toxic to my system

Hello. Short version: I am a new openHAB user, coming from more than a decade on MisterHouse. I set up openHAB a couple of weeks ago with the goal of bringing my devices and automations from MisterHouse to openHAB. One device class I use is 1-Wire. It had been 100% stable for years on MisterHouse and after setting it up on openHAB, it would work perfectly for a short period of time (from minutes to hours) and then completely stop working. There would be absolutely nothing in the logs, even at t…

I do NOT need the AndroidTV binding; I had it installed because openHAB auto-discovered my AndroidTV devices and suggested that I install the respective binding, which I did to “play with it later”.

Eloy.-