OH going to 100% (or greater) and not responding

The 1.x binding is still compatible with OH 2.5.7 and I believe you can run both the 1.x and 2.x versions at the same time. So you don’t have to switch everything over all at once to upgrade. You don’t even need to switch them over at all and can continue to run 1.x. However, the 1.x binding will not be compatible with OH 3 so it would be a good idea to move over at some point. But you can go a little at a time.

The first part of Marketplace MQTT Event Bus might be useful to read.

At a very high level:

  • the stuff that goes in mqtt.cfg now goes in an MQTT Broker Thing. Manually create the MQTT Broker Thing by clicking the + icon in the Things page or Inbox page and navigate to MQTT and MQTT Broker. Fill in the connection stuff.

  • Manually create a Generic MQTT Thing and create a Switch Channel and put the cmnd topic in the command topic filed and the stat topic into the state topic field. You are not using any transformations so there is nothing else to fill in.

  • Link the Channel to a Switch Item

For the Tasmota stuff, you could also enable Home Assistant MQTT on the device in which case openHAB will automatically discover the devices and create the Things for you. Then all you need do is accept them from the inbox.

Something must have changed, an OS update, lost power resulting in file corruption, SD card wearing out, etc. Wolfgang_S is definitely right about the Amazon Control Binding. Amazon changed something on their end that broke our binding.

Between OH 2.3 and OH 3 there are several bindings that require the deletion and rediscovery of Things. I wouldn’t copy over Things and instead recreate them.

3 Likes