You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using a JRuby profile to convert between Mired and Kelvin which is attached to each color temperature channel. The profile looks as follows:
profile(:mired_to_kelvin) do |event, callback:, command:, state:|
case event
when :command_from_item
callback.handle_command(command | "mired" | "K")
when :state_from_handler
mired = state.to_f | "K" | "mired"
callback.send_update(mired.to_f)
else
true
end
false
end
In Homekit my lights look like this:
With OH 4.3 I have issues with the color temperature items. They look like that in the homekit app:
I tried all different configurations from the documentation. But none works with OH 4.3. I have the impression that the example
// Dimmer item, with allowed range given in Kelvin
Dimmer light_temp { homekit="Lighting.ColorTemperature"[ minValue="2700 K", maxValue="5000 K" ]}
does not even work with OH 4.2.
I tried it with OH 4.3.1 and 4.3.2.
The text was updated successfully, but these errors were encountered:
Hi,
this issue is related to a longer discussion on the OH forum: [openHAB 4.3 Milestone discussion](https://community.openhab.org/t/openhab-4-3-milestone-discussion/158139/114?u=jabra_the_hut)
Expected Behavior
When using OH 4.2.1 all my color temperature items behave perfectly normal both on OH UI and on Homekit side. Example item:
I am using a JRuby profile to convert between Mired and Kelvin which is attached to each color temperature channel. The profile looks as follows:
In Homekit my lights look like this:
With OH 4.3 I have issues with the color temperature items. They look like that in the homekit app:
I tried all different configurations from the documentation. But none works with OH 4.3. I have the impression that the example
does not even work with OH 4.2.
I tried it with OH 4.3.1 and 4.3.2.
The text was updated successfully, but these errors were encountered: