Sorry, I donβt understand what you mean by this.
Donβt you have the light bulbs connected to the physical switch?
The driver only interrogates the device when the switch is turned on or off from the app in order to emit the status that the device has after the On or Off command sent.
When On or Off is pressed on the physical device, the driver is completely passive until the device informs it of the command it has performed. At that moment driver processes the message and emit the on or off status that the device has sent.
If the message takes time to reach the driver, it may be the fault of your Zwave network, it may be saturated or there may be a device connection problem or hub memory overload
Sorry for the late reply, but yes, there are no physical lights connected to the switch. Iβm just using it as a way to control 4 separate lights through the software
Hi @Mariano_Colmenarejo
I manage to assign your βz-wave switch and child mcβ but the it just come out as single switch instead of 4 separate switch. The single switch only control the first output on the switch.
Can I know which part of the code did you modify base on z-wave switch folder in the github to make it work 75% ? I would like to create a custom driver for a few of my installations at my customer site.
The driver only creates as many child devices as the device has endpoints. Since the device only has 4 endpoints, it creates 1 main device and 3 secondary devices.
You can create a virtual device or a group of lights and a routine to turn on and another routine to turn off the 4 devices
Sorry, You need modify this table too, in the multi_metering_switch_configurations.lua file, in subdriver multi-metering-switch to add the product_ids 0x5103 to child profile type
@Mariano_Colmenarejo
Thanks for all the help and advice, working well now. had 4 child switches that can control each light individually, however, there is no Master switch to turn all ON/OFF. Hence I used routine to do an all ON/OFF, which is not a big issue.
Cheers !