This blueprint is designed to simplify configuration of all Inovelli Blue devices (mmWave, Fan, On/Off, Dimmer/2-1 switches and canopy).
All configuration type settings are supported for each device and the automation will adjust to unique settings for device types if grouping them all together. Here are a few key points of the blueprint:
Zigbee2MQTT is required
Target one or many devices, areas, and/or labels
This allows you to target an entire room(s) or send certain configs to specific devices with labels
All setting values are set to defaults and disabled in automation, allowing you to only enable and push setting you care about. Automation will filter any devices using labels/areas to only be Inovelli devices using MQTT integration.
To push a setting it first needs to be enabled in the blueprint and it will send the value to all targeted devices (if device supports the setting otherwise it’s skipped)
Settings that are for the state of switch or effects are not supported in this
Triggers are optional so it can be run manually as needed or trigger how ever you would like
Upon completion a persistent notification will be sent letting you know the bulk configuration settings have been completed
Notification has a custom field for setting the title and the body of the message will include all the devices that were targeted
This is a great blueprint! It makes managing these switches much easier.
Is it possible to get a setting for “FanTimerMode”? It looks like this is parameter 121. This is the documentation for the VZM35-SN, but it seems to be supported in at least the VZM30-SN, VZM32-SN, and VZM35-SN, and not the VZM31-SN (I don’t have a VZM36 to validate if it exists there or not).
Thanks for the input! It has recently saved me from a bad coordinator and repairing was not as daunting since I had this to push settings after switches went back to factory settings!
I think I somehow missed that as it’s not something I personally use. I tested it on the VZM35-SN and it is now added and working as of version 1.1. The setting is under the advanced features dropdown and sorted by point number.
You should see your current version number under the title at the top of the blueprint.
To update your blueprint:
Go to: Settings → Automations & Scenes → Blueprints
Find this blueprint in the list and click the 3 dots to the far right.
Hit re-import blueprint in the sub menu.
It should update all your existing automations that are counted as “In Use” (number next to the 3 dots) to version 1.1 automatically. You don’t need to rebuild them to see the new setting added and it will be disabled by default leaving existing automations unchanged.
@gbosky any chance you could update this to make the mqtt topic adjustable? I don’t use the default “zigbee2mqtt” which is causing this to not work. I could change the code myself, but would have to do so every time it’s updated, and I don’t want to do that if I can avoid it!
I added this to v1.2 which is available now if you update your blueprint. A new mqtt topic field is added at the top of initial inputs so you should see it right away without digging through the dropdowns.
Default value is still zigbee2mqtt and it worked for me. It also stopped working if I changed it to anything else, so I am assuming it works for other topics after those tests but let me know if you run into issues.
