What I want to do is to combine these two components and have them show as 1 light. Of which the turn_on, turn_off and toggle switches the switch, but any other setting (brightness, color, white_value) should modify the mqtt light.
Iâve been looking into how to configure this, and Iâm not sure I can do this with the âMQTT Template Lightâ or âTemplate Lightâ or that I need to start working with automations or scripts.
Is there anyone who has a similar set-up or some tips on how to get started with something like this? Thanks
EDIT:
Iâm going to try to combine at least the switch with the brightness of the milights. The color / white_temperature etc I will arrange via scenes / seperate identities. Iâll keep this thread updated with my findings/struggles.
I would recommend changing the value_template because you are using the state of a platform that maybe takes extra time to load, the Template Light may get an unknown state during startup.
Iâve done that now, warnings/errors due to that in the log are gone as-well. thanks for the tip.
So now I have my z-wave switches and milight lights combined via template lights, everything seems to work. (well: on,off, and brightness atleast)
Is there a way I can also send a switch.turn_on command to the switches when changing the brightness when the light is initially off? Also Iâd like to not send light.turn_on commands to my lights when changing the brightness, because when Iâm doing this to fast, the milights think they should go into pairing mode since they received the on command 3 times within a few seconds.
Iâm not sure if the âswitch.turn_onâ can pass brightness, but itâs maybe worth a try? So when brightness changes it should do âswitch.turn_onâ with a data_template containing âbrightnessâ.
Scratch that.
Maybe you can have multiple entities in your set_level, like this: