@zanix Love the blueprint. Is it possible to modify it to work with the blue series fan switch? The fan switch entity does not show up as a selectable option. Probably because it is a fan and not a light. For example my fan entity is:
fan.0x048727fffe1b2ba0
and my 2-1 (which does show up is):
light.0x60a423fffe30a49c
I made the blueprint set to only show light entities. So that explains why it doesn’t show up.
It also filters based on the model name “Inovelli 2-in-1 switch + dimmer (VZM31-SN)” so it doesn’t try to send the commands to other devices if you pick an area for the target.
I can edit the blueprint to show fan entities and add the model name of the fan switch to the filter. If the Z2M commands are the same as the 2-in-1 it should work just fine.
Can you put this in Developer tools > Template and send back what the model string is?
{{ device_attr("fan.0x048727fffe1b2ba0", "model") }}
Inovelli Fan Controller (VZM35-SN)
I got the blueprint updated in another branch on my GitHub
It works for the light switch but since I don’t have the fan switch can you let me know if it works?
EDIT: I merged this into the main branch
Works great, thanks! I am able to mix lights and fans to call the same notification at the same time.
Awesome! I’ll push the update to the main branch.
Now I just need to order a couple fan switches so I can use the update myself!
I was not having luck with my new fan switch and discovered that it is showing up as model “Fan controller (VZM35-SN)” without the Inovelli. Adding a line to models around 201 resolved my issue. Not sure why mine is showing up differently. Currently running Z2M 1.33.1-dev
Interesting, if the models values were stripped down to just the model number the filter should work the same. Can you test that for me?
models:
- VZM31-SN
- VZM35-SN
This means you are using the contributed convertor instead of the external convertor and the maintainer of z2m requested the name of the device be changed, removing the Inovelli portion from the name.
Looks great! Is there something like this to control LED notifications for the Z-Wave Red 800 LR switches?
Can you say more about the external converter? I run Z2M in its own docker and the latest tag didn’t have the VZM35-SN yet so I had to use the dev tag. I actually just got around to converting from ZHA to Z2M so it is very new to me but I love the flexibility of MQTT. I run HAOS in its own proxmox VM and then dockers for node-red, mqtt, z2m, etc.
Thanks
This works!
Nice! Thanks for testing. I’ll update the blueprint soon.
There was a PR to add the VZM35 to z2m default converters. The z2m repo maintainer renamed the device in the PR. So, since you were using the dev z2m, you were getting the new name and that was making the blueprint have issues. Looks like having the model numbers in the blueprint catches the devices no matter which converter / version you are using.
Update inovelli.ts · Koenkk/zigbee-herdsman-converters@f79948a (github.com)
I pushed an update, then another later on to fix the first update.
Update model filter to only model numbers
Model ID fix
I just started playing with this. In general it seems to be working, but seems to mess up the LEDs when the switch is used locally. If an automation sets the LEDs and then I turn the switch on or off locally, the LEDs immediately go back to what the automation set instead of representing the on/off state of the switch.
I am using an interval of “indefinitely” which seems to me to be appropriate. I would only expect the behavior I am seeing with an interval of “forever”. Is there some other parameter that I am missing?
Also, Is there a way to query the current LED state of a switch?
TIA
This is how effects work. The effect stays until it times out or it is cleared (or never if you pick “Indefinitely”). To remove the effect, you need to send “Clear” as the effect, or just leave “effect” blank in my script as that sends clear.
Ah. I assumed “clear” was translucent, or something.
Thanks.