Received my Inovelli blue fan switch and canopy module. Purchased these as a set with the intent of controlling both fan and lights. I have a single-pole switch for power. Wiring seems straight forward. However, I have questions re: pairing/programming for my specific application. I have zigbee2MQTT up and running, but am very (very) new to HomeAssistant (HA). My thought is to set my fan/light up manually, and perhaps pair it with HA later. I think I understand the basic programming process, but would like some guidance re: manually programming the switch for my application. The accompanying instruction booklet seems to guide me to âinov.li/vzm31snmanualsetupâ, but that link is not working for me.
Can someone point me to, or walk me through proper configuration for both light and fan control?
OK. Switch and Canopy module installed. Power on. Switch flashing blue (pairing mode). Iâm a little lost from this point forward. To new to this technology. Need some step-wise help. Do I somehow need to pair the switch and the module?
As a first step, youâll need to pair both your switch and the canopy to your hub. Once they are both paired there, then you will use binding to bind the switch to the canopy.
Here is Inovelliâs document on binding the switch to the canopy. You may need to post back here with questions but at least that will get you going. Since things change in HA fairly rapidly, the document may not be up to date.
Plenty of people here using Z2M, so post back with questions.
Thanks Bry,
Step #1 says go to âgroupsâ. Donât see that anywhere. I think something is wrong with my Home Assistant instance. Crap. Two-steps backwards. Is there no way to âbindâ the switch and module manually?
If by manually you mean without using the hub, I am not aware of any way to do that.
Someone with Z2M canopy binding experience should be able to post here and give you a hand.
Thanks,
The issue is Iâm not seeing the opening Z2M page indicated in the Inovelli article. There is an (Z2M) option in my HA side bar, but is does not produce the Z2M page. It simply produces two additional versions of the side bar. Frustrating. I canât get past step one, cause I canât get the Z2M page to display. Any HA/Z2M users out there have a suggestion?
Can you upload some screenshots? Itâs hard for us to understand whatâs going on otherwise. It sounds like you actually have a problem with either Home Assistant or Z2M itself and we need to understand that before we can help.
Thanks Rohan,
I believe you are correct. Problems with my HA or Z2M install need to be addressed first.
HA-Overview (below) shows my main HA page
I can access Portainer by clicking on the âPortainerâ item in the side bar. Portainer shows four expected containers running
Part 2
The âzigbee2MQTTâ item in the side bar was generated in similar fashion (to Portainer). However, when I click on zigbee2MQTT â I get the followingâŚ
I was able earlier in the evening to display zigbee2MQTT page by directly typing IP Address:Port. However, most recently, I am unable to connect in this manner. I can no longer reach zigbee2MQTT directly. I can SSH into my server.
I believe I have made a ânoobâ mistake. I seem to have lost communication with my dongle/router. Be advised, Iâm not above starting over with a fresh version of software. Sometimes that is easier than digging around in all the dusty corners. Anyway, appreciate any insight you may offer.
Iâm guessing that youâre running Home Assistant OS and then have installed ZIgbee2MQTT as an Add-on? Based on the fact that youâre also running Portainer, I wonder if youâve made some changes to the configuration of Z2M container that has broken the default add-on configuration.
Unfortunately, I canât provide much help here since I donât run Home Assistant OS or the addons, I directly run everything in docker. I think your best bet is probably on the Z2M discord or Home Assistant discord / forum to see if someone can help you get Z2M working again properly.
Once you have that in place, we should be able to help you configure the binding here.
OK Boyz, I believe I am back on-line.
Thank you Bry for reference to document ( [Setting Up Your Blue Series Fan/Light Canopy Module With an Inovelli BlueâŚ]).
Somewhere I (think I) read that prior to pairing switch and canopy assure the fan speed is selected as âhighâ. Did not do this prior to wiring. Do I need to back up a step (or two) and confirm my fan speed?
No. Just turn the switch up so the canopy is on high. Then cycle through the fan speeds with the chain. Wait for it to turn off, then the first pull will be high.
So, just to be clearâŚ
Proceed with pairing/setup,
Once setup, turn the fan on and adjust to high using the pull chain,
Operate fan using switch.
Have proceeded with (Inovelli) instructions. Established a group. Pairing (of VZM31) seems OK. Computer (and dongle) in basement, switch on second floor. Zigbee2mqtt showing model unknown/unsupported? Have a flashing exclamation point (indicating interview failure). Instructions say to select from drop down menu and specify endpoint 1. I assume this to mean the drop down menu showing current paired devices. However, I donât seem able to view VZM31 options (as illustrated in the instructions).
Oops. VZM31 (switch) did not show up on my âOverviewâ page. Any help?
UpdateâŚ
Removed VZM31 from HA. Repeated attempts to pair fail. I do have four (Third Reality) smart plugs dispersed near the VZM31 switch (all paired). I turn âonâ âPermit Joinâ (countdown commences). Put VZM31 into pairing mode (confirm by blue flashing led). However, no joy. Am I missing a step?
Update 2âŚ
Restarted HA and Z2M. Factory reset VZM31. No pairing.
Update 3 (29 Jun)âŚ
Not much left to investigate/troubleshoot. Maybe it is proximity. Moved Dell Wyse (containing HA, Mosquitto, Z2M, Docker, and Portainer) to bedroom (next to switch). Factory reset switch, put in paring mode⌠And VOILA! I see switch and canopy module on my list. Well, learned a few things. Perhaps installation of the second one will go more smoothly. Moving on to configuration steps.
As my devices are now paired I will close this string and mark it a solved. Iâll likely open another string regarding configuration.