The operating code for the quibino devices in the stock driver and in my driver are the same, I have only added the option to create a device to configure the parameters and associations.
This device is certified by sartthings and in the driver that has migrated from DTH it has only implemented that it can have a temperature probe connected, not an open/close sensor.
I donβt know why quibino and samrtthings have certified it this way and then in the device profile they have a preference for a switch input.
Maybe I could implement the contactSensor capability in an optional profile, but I donβt know if I could make a child device.
In any case, to try to do it I would need you to create the configurator device and send me all the fingerprint, endpoint and command class information of the device and you would have to help me debug it by sending everything with the CLI. I donβt have the device and I canβt do it
Hi and many thanks for the commitment. I would gladly help you. But right now is not a great time personally. Going to do some surgery next week. Maybe I can get back to you later this fall?
Youβre genius.
Unfortunately Iβm not. I do still have the issue that I canβt find how to configure to control the two switches individually.
And, I canβt find the network ID of the switch.
Sorry, I donβt understand what your real problem is.
If you press main, the main and switch1 physical turn on and if you press switch1, do they both turn on too?
The βmainβ component of the app controls physical switch 1 and app switch 1 controls physical switch 2. Smartthing stuff! There is no switch2 component in the app.
Iβve been checking the driver.
I added it about two weeks ago, with the dual-metering-switch profile, just like other dual-switch MCO devices.
The assignment of endpoints and components may not have been configured correctly.
I would recommend that you exclude it and or add it back to the driver to see if it is configured correctly.
If the main switch and switch1 still do not work independently, you would have to send me the logs with the CLI to see what the device is sending to the driver
I see that this device does not support power and energy.
I have looked for the documentation for the device on the manufacturerβs website, but I donβt know exactly what commercial model it is, since the manufacturer does not publish the fingerprints nor can I find them in the zwave alliance.
If you can provide me with the documentation or a link to it.
This is a tutorial to capture the message logs when you press on and off on each switch in the app.