I update today more or less by accident my openhabianpi to openHAB 2.4. Thanks for your constant work on this project!!
After updating my MQTT configuration, I am now still facing problems with may homematic blinds. They are not visible for alexa anymore over the hue emulation.
I can control them over my sitemap but I get errors in the log:
Exception while formatting value '100' of item R_Rollaeden with format '%.2f %unit%': Conversion
I see a lot of this errors. I use homematic HM-LC-Ja1PBU-Fm and G-HM-LC-Bl1PBU-FM.
Both make the same error and also Alexa don’t find them any more. Also the slider in the sitemap shows a question mark.
I did that already! And my log is still full of errors and now I see http exceptions also…
Not sure how othen i rebooted now… My Alexa connection is stiil very unstable.
Update after one night:
The log is full of exceptions and errors. Devices and bridges going offline and online. Everything is very, very slow. It takes many seconds until a light reacts on a switch (If it reacts)
A bit frustrating. I will roll back to openHAB 2.3 now.
I can provide the 2.4 log files from over night, if anyone is interested.
I am happy because I managed a stable update to openHAB 2.4 by increasing the java heap size. Now its stable!
But the the error/warning in the log on each opening of a sitemap with roller shutters remains:
019-01-01 09:54:03.673 [WARN ] [ui.internal.items.ItemUIRegistryImpl] - Exception while formatting value '0' of item R_Rollaeden with format '%.2f %unit%': Conversion = 'u'
2019-01-01 09:54:03.681 [WARN ] [ui.internal.items.ItemUIRegistryImpl] - Exception while formatting value '0' of item alexa_rollos with format '%.2f %unit%': Conversion = 'u'
2019-01-01 09:54:03.688 [WARN ] [ui.internal.items.ItemUIRegistryImpl] - Exception while formatting value '0' of item alexa_slats with format '%.2f %unit%': Conversion = 'u'
And the sliders in the sitemap still show “Err” instead a value.
Now the log is clean and my sitemap looks like this:
Thanks @vzorglub. I thought about your hint and came to this idea.
There seams to be a change between openhab 2.3 and openhab 2.4 that this formating is needed.