Actually my led strip don’t have warm and cold white so i can’t test, but i guess you should use a dimmer instead of a switch.
For the stateTopic you should also use the transformationPattern
okay, finally I have an idea why you did not get this message: I think it requires the command SetOption4 1 in the Tasmota Webconsole.
Apparently I routinely issue this command on any new Tasmota device, although I don’t remember it
Form Tasmota documentation:
SetOption4:
Return MQTT response as
0 = RESULT topic (default)
1 = %COMMAND% topic
This allows to use individual state topics for all openHAB channels and makes the chained state transformation with the Regex unnecessary. Sorry I didn’t remember this until now. It answers your original question of “why does the item linked to the HSBCOLOR channel not change”.
The solution of chaining state transformations has the advantage of not having to set this non-default setting on every Tasmota device (and then forgetting about it), so it’s probably a better solution overall.
Thank you so much! This was missing on the sites I looked at.
I’ll keep it that way with reggex
I’m currently setting Alexa up.
I created a group (g_Schreibtisch) for Brightness, Color HSB and Power.
This works fine. Everything can be controlled as one item (added Alexa Metadata).
Since I don’t think RGB + W works with Alexa, I tried splitting it up:
one more group, g_SchreibtischWeiss which includes the White Element and also the Dimmer.
But there I can’t setup the deployed items in the Meta Data
In case of a Color Light i would stick to to the default SetOption4 0
because if your light is off and you change any channel, color, dimmer or white, the light will be swiched on and also the power state changes but it’s only published in