Sure i’m currently on vacation and i’ll update It when i’ll be back.
T’hank you!
No rush; meanwhile I’ve cloned your repo and tested these two instances locally based on the VI triac for the satellite and rollers and shutters for the single shutter 
Hi Oreste,
I’ve finally decided to leave eedomus. So, I’m setting up all my Vitrum switches on Homey.
But some aren’t recognized like a BS IV. Please, could you add the following version :
Manufacturer : 266
Product Type : 8704
Product ID : 37888
Thank you
Thierry
I’m traveling those two weeks so unfortunately i cannot add those soon.
Anyway if you could provide a full list with:
Device Type:
Manufacturer:
Product Type:
Product ID:
I would add those as soon as i come back.
write me a private message
thanks
No rush
Have a great vacation
Thierry
Hi Oreste
I Have an other one 
Device Type: BS I
Manufacturer: 266
Product Type: 29025
Product ID: 4194
And the first one (in my first mail)
Device Type: BS IV
Manufacturer: 266
Product Type: 8704
Product ID: 37888
Have a great holidays
Thanks
Thierry
I updated the app with your IDS (Vitrum OnOff BS I and BS IV) and it should be deployed within 24h.
Thank you for your patience
Oreste
Thank you so much, it’s really very nice
Have a good evening or a good day
I’m having trouble pairing a Vitrum Design Cloud switch (the specific model doesn’t matter) with a Fibaro Wall Plug (for exemple)
I’m coming from an eedomus system and never encountered this kind of error; pairing used to work without any issues.
I therefore conclude that the problem lies with the Homey Pro.
Whenever I try to pair the switch with the Wall Plug, I always get the same error: " Command class SWITCH_MULTILEVEL not found on destination xxx »
I’ve tried various settings regarding the switch type, as well as exclusion and inclusion, but nothing works.
Has anyone else experienced this problem, and—more importantly—did you find a solution?
Thanks in advance.
Thanks for this express reply.
Type ID is : 28993
Type prodcut : 4162
Maybe there will be others
I have this one too, sorry
Type ID is : 29025
Type prodcut : 4194
Yes, you’re right, but I want to associate these two elements so they work without a box. And with no latency.
And I have the same issue with Fibaro FGS-214 & FGS-224
You need to perform Z-wave associations. Have a look at HW manuals, this is not managed within the app but is an underlying Z-wave feature.
Oreste
Thank you for your message but I don’t have the skills or knowledge to understand. If Homey can’t do it, then I can’t do it. lol
Thank you very much.
Thierry
it’s somethibg you can do on homey but on additional options on device.
Setting up direct Z-Wave association is essentially like giving two switches a private radio channel so they can talk directly to each other—meaning if your smart hub ever goes offline, the switches will still control each other instantly.
The step-by-step process below outlines how to explain the setup, using two hypothetical switches (Switch A and Switch B).
1. Grab the Node IDs
Every Z-Wave device added to your hub gets assigned a unique number called a Node ID (e.g., Node 12, Node 25).
-
Go to your hub’s device list or Z-Wave controller panel (Home Assistant, Hubitat, Z-Wave JS UI, etc.).
-
Find the two switches and write down their Node IDs:
-
Switch A (Trigger/Primary): e.g., Node 12
-
Switch B (Target/Secondary): e.g., Node 25
-
2. Check Prerequisites (The Security Match)
Z-Wave switches can only talk directly if they share the exact same security level (e.g., both paired as S2 Authenticated or both as Unauthenticated). If one switch is secured and the other isn’t, the receiving switch will ignore the direct signal.
3. Set Up Switch A $\rightarrow$ Switch B (One-Way)
To make Switch A control Switch B:
-
Open the device settings for Switch A in your Z-Wave controller.
-
Look for Groups or Associations.
-
Select the target Association Group:
-
Note: Avoid Group 1 (that’s reserved for the “Lifeline” back to your hub).
-
Choose Group 2 (Basic Set) for simple On/Off toggles, or Group 3 (Multilevel Set) if these are dimmers.
-
-
Set the Target Node ID to 25 (Switch B) and save.
How to verify: Tap Switch A. Switch B should turn on/off almost instantaneously, even if you unplug your hub’s network cable.
4. Set Up Switch B $\rightarrow$ Switch A (Two-Way / Virtual 3-Way)
If you want a true 3-way setup where tapping either switch updates the other, complete the loop in reverse:
-
Open the device settings for Switch B.
-
Add an association on Group 2/3 and set the Target Node ID to 12 (Switch A).
-
Prevent Feedback Loops: Check your switch brand’s parameter guide (like Inovelli or Zooz). Many switches require you to toggle a specific configuration parameter (e.g., “Association Behavior” or “Smart Bulb Mode”) so the switches don’t trigger each other endlessly in an infinite signal loop.
In Homey that would be Homey Developer Tools
Hello Alexus
No only le V3 version V4.03
Hello Oreste
Sorry, my English come from Google Translate
So, I think my explanation wasn’t very clear.
Currently, I have no trouble directly associating a push-button with a light (e.g., a Fibaro FGD-213) using the Z-Wave protocol and Homey.
It works perfectly. However, I’m running into an issue that I believe stems from Homey (since I had no problems with my previous hub using the same devices): when I try to associate a button on a Vitrum switch with either a Fibaro Wall Plug, an FGS-214, or an FGS-224, Homey returns the error: “Command class SWITCH_MULTILEVEL not found on destination xxx.”
Just to clarify, neither of the two devices is included in secure mode
Thanks for everything.
