openHAB 3.4 Release discussion

[Matthias_Kaufmann (Matthias)]

Another issue I found is using icons.
I have a group icon using a custom png icon:

Group     gSonosBad                   "Sonos"             <sonos>          (gBadezimmer)    ["Speaker"]

This is shown successfully in the items editor in the main UI:

But in the model the icon is not shown:

I have also other items with custom png icons that show the icon successfully in the model as well.

[Spaceman_Spiff (Sebastian)]

@Cplant

After having upgraded to 3.4, everything above Start Level 70 (80 - Things Initialized and 100 - Startup complete) are not working for me anymore (rules just not getting fired).

Can you confirm that your system reaches Start Level 100?
If there are broken/uninitialized things it’s possible that it’s still stuck on 70.
You can check the status e.g. with the RestAPI

[dikay1969 (Dierk Kaczmarczyk)]

Sorry that I’m so late in contacting you about the Shellys, but I was sick.

https://community.openhab.org/t/openhab-3-4-milestone-discussion/138093/161?u=dikay1969

The Shellys work perfectly with OpenHab 3.4 and the items are updated cyclically and permanently.

In the 3.4 Milestone 6, “ECMA Script 2021 Edition 11” no longer worked for me at the same time, maybe that also had an effect on the Shellys. The developers will know. I didn’t try the RC1 again after that.

[og-openhab (Torsten)]

Hi,

I just upgraded my docker to OH 3.4.
I see issues with the addon “Bose SoundTouch Binding”.
There are no spontaneous events present in events.log.
Does anyone face same issues?

Thanks!

[Cplant]

@rossko57

This might be an indication that it is working as designed … version updates can break existing Things, where the binding has added/removed channels for example. Check logs carefully.

@Spaceman_Spiff

Can you confirm that your system reaches Start Level 100?
If there are broken/uninitialized things it’s possible that it’s still stuck on 70.

You were both correct: After going to 3.4, Gardena did not connect anymore (Error 403 Forbidden, {"Message":"User is not authorized to access this resource with an explicit deny"}), leading to uninitialized systems and this never reaching Start Level 100.

Interestingly I had to delete the entire application under https://developer.husqvarnagroup.cloud for the connection to the Gardena Smart System Account to work again.

[jheiler (Jürgen Heiler)]

With respect to the new default units:
dust and gas is measured in kg/m³? Is this serious, how can I fix my configuration again?

Kind regards

[tknaller]

I am still in 3.3 stable and have the same issue - thank you the fix

[ccutrer (Cody Cutrer)]

You need to include the unit you want in the item’s state description. If you’re using .items files, you do it like this:

Number:Dimensionless Bedroom_PM25 “Bedroom PM 2.5 [%d ppb]

If you use MainUI, it’s under the item’s metadata:

[MikeH]

All my Hue lights are showing “Error:Bridge” . How do you change to https and how do you clean the cache. Thanks for any help.

[jheiler (Jürgen Heiler)]

Thank you for your advise. But these figures are not dimensionless but density. Your purpose leads to an error.

[rossko57]

@jheiler

Your purpose leads to an error.

That’s why he said “like”, it is an example not a tailored solution just for you.
Bear in mind the units that you do want are still a secret from us.

If you are using sitemap files and have specified [state presentation] in the labels there, you will need to fix those (or remove to use Item unit instead)

[Spaceman_Spiff (Sebastian)]

From his screenshot I’m assuming he wants ug/m³.

I am still convinced the whole unit of measurements concept is/was something that we call “bear service” in Germany.

[jheiler (Jürgen Heiler)]

If pm2.5 for example is
10 Mikrogramm pro Kubikmeter [µg/m³]
with this method is shown
= 1,0×10-8 Kilogramm pro Kubikmeter [kg/m³]
or
0,000 000 01 Kilogramm pro Kubikmeter [kg/m³]
This does not make sense.

Another way (I do not know how) could be to set up a transformation rule for any affected item.
This would be annoying.

Kind regards

[ccutrer (Cody Cutrer)]

I think we need more information. What binding/channel are you using? What’s the full item definition? Your latest comment sounds to me like your binding is sending just a DecimalType, and you’re using a Number:Density without a state description to define the unit. With 3.4.0 OpenHAB will now assume a default unit for every dimensioned item. But if your binding isn’t sending dimensioned (QuantityType) data, you might as well just use a plain Number item. Then you can be sure that no conversions will take place. If you want conversions to take place, you’ll need to work with the binding’s author (or the config, if say it’s coming from MQTT) to make sure it’s coming in with the proper units so that conversions will make sense.

[milo (M)]

Maxi ask this stupid question?? How to find out in which state openhab is? @rossko57

[rossko57]

“Raw” state of an Item? Quick reliable way is to inspect your events.log for a state change.

[binderth (Thomas Binder)]

@jheiler

Another way (I do not know how) could be to set up a transformation rule for any affected item.
This would be annoying.

no, that’s not needed.

First of all: what kind of unit information do you get from the binding?
=> the channel particulateMatter2dot5? delivers Number:Density and “Current or forecasted density of particles less than 2.5 µm in diameter.” - which shold be around 5 µg/m³. The binding will update the item with let’s say 2.07 µg/m³ bear in mind, the binding will tell the unit µg/m³ in this case.
Second of all: what initial unit configuration does the binding have? I don’t have the openweathermap binding installed, but I reckon it should come preconfigured with µg/m³ as the unit for the particulateMatter2dot5 channel.
So: either your update messed up something or it came without any UoM in the first place. Then your previous OH-installation would just display a Numer 2.07. But now: that OH3.4 does have some standard UoMs (I reckon kg/m³ for Number:Density?) your OH displays that.

What to do: change your metadata to µg/m³ and you should be fine and the conversion should be made automagically.

[rossko57]

@binderth

What to do: change your metadata to µg/m³ and you should be fine and the conversion should be made automagically.

But note that if using sitemap based GUI, the sitemap can override Item default and make another conversion, for display only.

[milo (M)]

I mean when the start level changed from openhab from 70 to 80 and so on is there a variable?

[binderth (Thomas Binder)]

@rossko57

But note that if using sitemap based GUI, the sitemap can override Item default and make another conversion, for display only.

oh. that’s right. on sitemap there should be also the µg/m³ “conversion”.
Remember: UoM is magic! You could put in Mt/m³ and still geht µg/m³ as displayed.
Also Remember: the metadata on the item is responsible for persistence. If you like OH-graphs, be sure to change that to a UoM of your liking beforehand - a change afterwards doesn’t affect persisted values - so you could have incorrect graphs if changing in the middle of the day.