This topic can be used to discuss problems/experiences/questions on the openHAB 4.3 release as announced in this topic .

[image] Lolodomo: og:set DEBUG org.openhab.ui.basic.internal.render.ColortemppickerRenderer 2025-03-14 09:41:10.609 [DEBUG] [ernal.render.ColortemppickerRenderer] - Can't get RGB for 15 Kelvin, bypassing color gradient! 2025-03-14 09:41:10.614 [DEBUG] [ernal.render.ColortemppickerRenderer] -…

Apparently, you have inconsistent values and inconsistent min/max for a color temperature in Kelvin. What is expected is a value in range 1000-10000. 1 K or 15 K is not a proper value. Maybe a bug in the deconz binding or in your config?

[image] milo: item config Number:Temperature ColorTemperature_GF_Corridor_ExtendedLight1 "ColorTemperature_GF_Corridor_ExtendedLight1" (Group_GF_Corridor_Light, Group_GF_Corridor_ColorTemperatureLight) ["Control", "ColorTemperature"] {channel="deconz:extended…

[image] milo: This is my config what is wrong? Something wrong in your item definition .. looks like " or [ ] characters munged up.. Number:Temperature .. {channel="deconz:extendedcolorlight:smarthome:Corridorextendedcolorlight1:color_temperature", stateDescription=" "[ pattern="%.0f %unit…

You could add it to the addon.cfg in your config/services folder?

hi all ,i tried to update my openhabian setup (running on a Rpi4 2gb) to the 4.3 openhab 64bit.I took a backup of my configuration,installed openhabian 64bit to my sd card and restored my config.At first all went well without errors but i had high memory consumption over 89 to 95% and system hangs a…

solved by using stateDescription=" "[ pattern="%.0f %unit%" , min=2000, max=6500], unit="K"

[image] mstormi: Only if you believe this is a general software issue and was introduced with 4.3 vs. 4.2 (that is, it didn’t exist in version versions before 4.3). Isn’t this thread also used to discuss changes throughout the 4.3.x release cycle? i.e. 4.3.2 → 4.3.3 ? As per openHAB 4.3 has …

Okay, too. But as per definition there should not be any changes as the X in 4.3.X mean it is just a patch release, i.e. no or at least no functional changes.

update from 4.3.2-release auf 4.3.3.-relase on a raspberry Pi 4 (4GB) with current openHABian. Relatively smoothly, but still got these ERRORs. Were gone, after I just “saved” the corresponding rule BalboaEltakoCount. I ran into similar/same issues with 4.3 (see openHAB 4.3 Release Discussion - #3…

openHAB Community

openHAB 4.3 Release Discussion

Setup, Configuration and Use News & Important Changes