openHAB 3.4 Release discussion

Yes, I am also experiencing this. My logs are flooded right now and it seems to even impact performance on my raspberry pi.

Sliders and Setpoints in basic UI are currently broken in 3.4.0, when used with a Number type with dimension (e.g. Number:Temperature) and no explicit unit is set in the pattern.

As a workaround you have to define a pattern for each affected item, which contains the unit you want to use (e.g. %.1f °C).

I just upgraded OH 3.3 to 3.4. My Karaf window under Win11 shows that OH version is 3.4 (see attached screen copy)

but Help&About in MainUI shows 3.2.

I had this same issue when upgrading 3.2 to 3.3 so what I’m missing.

Thanks for the feedback. Happy to see that this issue is known. I should have checked this before…

Due to this problem, I downgraded back to OH3.3.
Will check on a separate instance if there are possible solution available.

Which one?

Problems with the “Bose Soundtouch Binding”.
It does not receive events from the devices in OH3.4.
Also the control from OH is not working as in OH3.3, e.g. selection of presets.

Is it solved if you clear the cache of your WEB browser ?

Work in progress to fix the Bose Soundtouch binding:

1 Like

Could you grab the jar from the github [issue ([bosesoundtouch] Things don't receive state updates and configurations from the speakers anymore · Issue #14059 · openhab/openhab-addons · GitHub) and test the latest version and report back with your findings and debug log? Thanks!

No, I tried both FF and MS Edge with cleared caches and Help&about still shows 3.2.0.

Strange question but are you sure to point your browser to the right server?
How did you run your upgrade?

After some experiments I think it might have something to do with triggering hue from rules.
Or maybe my rules are written badly, resulting in huge performance issues. But since everything was faster with 3.3.0 it might as well be something different.

Any ideas on how to debug this?

I have only one openHAB server in my home network so the browser must point to the correct server. I made the OH3.4 installation according to the manual installation section in Download openHAB | openHAB.

I am also having the same problem. Seems to be all my Chromecast enabled devices (I have many) including several minis, a Nest Hub, a Nest Hub Max, a bunch of chromecast enabled Vizio smart TVs, an original Google Home, and even a couple of remaining actual Chromecasts. My logs are getting pounded with the Offline/Online ping pong action. Hopefully this is something that is an easy fix.

Here’s what my logs are filled with:

2022-12-27 23:36:53.427 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:88bad034dd40307e13ba8b775ececedb' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): No route to host (Host unreachable)
2022-12-27 23:36:54.978 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:5f704f7973428c949f6287a88e10c6a2' changed from OFFLINE (COMMUNICATION_ERROR): No route to host (Host unreachable) to ONLINE
2022-12-27 23:36:56.819 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:062abc50874a948a0bb0df136bcc677f' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): No route to host (Host unreachable)
2022-12-27 23:36:58.162 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:6a68b880438f43b57ba24d410cb62142' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): No route to host (Host unreachable)
2022-12-27 23:36:58.213 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:88bad034dd40307e13ba8b775ececedb' changed from OFFLINE (COMMUNICATION_ERROR): No route to host (Host unreachable) to ONLINE
2022-12-27 23:37:01.466 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:6a68b880438f43b57ba24d410cb62142' changed from OFFLINE (COMMUNICATION_ERROR): No route to host (Host unreachable) to ONLINE
2022-12-27 23:37:01.554 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:6a68b880438f43b57ba24d410cb62142' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): No route to host (Host unreachable)
2022-12-27 23:37:03.222 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:062abc50874a948a0bb0df136bcc677f' changed from OFFLINE (COMMUNICATION_ERROR): No route to host (Host unreachable) to ONLINE
2022-12-27 23:37:04.882 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:5f704f7973428c949f6287a88e10c6a2' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): No route to host (Host unreachable)
2022-12-27 23:37:05.045 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:5f704f7973428c949f6287a88e10c6a2' changed from OFFLINE (COMMUNICATION_ERROR): No route to host (Host unreachable) to ONLINE
2022-12-27 23:37:06.481 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:88bad034dd40307e13ba8b775ececedb' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): No route to host (Host unreachable)
2022-12-27 23:37:08.313 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:88bad034dd40307e13ba8b775ececedb' changed from OFFLINE (COMMUNICATION_ERROR): No route to host (Host unreachable) to ONLINE
2022-12-27 23:37:09.874 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:062abc50874a948a0bb0df136bcc677f' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): No route to host (Host unreachable)

@Mick_Smothers @Lolodomo @higgers @JimT

I finally became so annoyed with the flickering chromecast things (during development I need to look at the logs so often that something like this is extremely distracting :grimacing:) that I picked up the issue.

There doesn’t seem to be a codeowner around for that binding, so I did at least one simple thing. Even though the binding has a surprisingly good amount of logging implemented, nothing comes up in my cases (or lets say hardly ever) that would hint me why it goes offline. So I went through the code and detected a few white logging spots. I added a number of traces to every location in the code where the binding tells the core to put the thing OFFLINE, built a new jar file based on 3.4, deployed it to my production system and hope to see that something is coming up.

I guess you know what is coming now in a strange world like this: ever since I deployed the new bundle version, there is complete silence (remember, there is no change except more logs on the trace level) … :stuck_out_tongue_closed_eyes:

Anyways, if anyone wants me to join on testing this and is able to deploy an addon manually, please PM me and I will provide you with a snapshot build of that bundle.

4 Likes

Do you mean that after you added the logging the things do not go offline any more?

Yes :smiley:

Ah, the joys of software development!

Does this point to something other than the binding being the issue? Did you reboot your OH server or restart the OH service? Could something else you did have resolved the issue?

@stefan.hoehn is it in a github branch? I can build the jar and also help debug it.
I’m still seeing this issue on my system.