I bought this 3 gang switch.
Smartthings discovered it as “Zigbee Switch Power” so I can’t control the switches separately.
This type also isn’t an edge driver so when pressing the 3-dot menu I can’t change the “driver”.
───────────────────────────────────────────────────
Name Zigbee Multi Switch and Child Mc
Version 2023-05-29T16:20:58.802129236
───────────────────────────────────────────────────
- id: "TS0003/_TZ3000_hbic3ka3"
deviceLabel: TS0003 Switch
manufacturer: _TZ3000_hbic3ka3
model: TS0003
deviceProfileName: three-switch
Install this new version of the driver in your hub from my shared channel.
If you already have another previous version of the driver installed and you have devices paired with other devices, then let it update automatically in a maximum of 12 hours.
Uninstall the device with the App
Add a new device in the app with the option search nearby.
When paired it will appear in the same room where you have the Hub
divisors and multipliers get reading these attributes during installation.
If the device does not reply then the driver uses the default 1 or a custom value if the driver knows it.
@Mariano_Colmenarejo, the team mentioned they’re not sure that the sub_drivers part could cause the issue, so, to have a better reference, we need your help to share the code you used to create the version that caused the issue, please. You can send the zip file to build@smartthings.com
After that, you can update the driver and we’ll try to replicate the issue.
My switch stopped working with the latest update (28th May). Works with built in driver but yours has better functionality. It’s reporting a network error when I try and switch it.
In your post on January 8, you were concerned that maybe setting both values did not work. This is what I am seeing, only setting the energy value to 10000 is affecting the power and energy values, and setting power value to 10 (or anything else) doesn’t appear to have any effect.
What is strange is that I only see this on one of four Sengled E1C-NB7 plugs. Three work correctly with the stock ST Edge driver. These three also were installed prior to Edge, with stock local Groovy drivers that transitioned to Edge drivers. The plug with the problem was installed only with an Edge driver.
I’ve switched between your latest Zigbee Switch Power MC and the corresponding Test-driver, back and fort, and emptied the app buffer in between the switching.
Wheras both drivers enables device on/off control using the app and in addtion displays W, Wh and signal metrics and soforth, no temperature field is present in the app. Using the CLI I’m not able to see if the temperature capability/configuration/presentation aspects are built into either of the 2 drivers?
(I’ve not yet had the opportunity to reset the device, but will do soon)
In the post to which you refer from January 8, there is almost everything that can be said about this problem, But I’m going to try to clarify it one last time
It all depends on the clusters that the device uses, if it use only 0702, as DTH code, the driver with the default handlers would not work well, since it can only use a divisor for the cluster SimpleMetering ID 0x0702 (constants.SIMPLE_METERING_DIVISOR_KEY), which in my driver is assigned a value of 10 as in the DTH and in the stock driver no custom value is assigned and then the value that it reads (SimpleMetering.attributes.Divisor) from the device must be assigned.
But if driver apply the same divisor for the calculation of power and energy then this does not work fine if device need 10 for power and 10000 for energy as DTH
In the DTH fingerprints the Sengled E1C-NB7 has clusters 0702 and 0B04:
In the January post, the Sengled E1C-NB7 clusters only have cluster 0702 and do not have cluster 0B04, which the default libraries use to calculate power with the ActivePower attribute. and the divisor key (constants.ELECTRICAL_MEASUREMENT_DIVISOR_KEY)
The fact that some devices for you and another user @NickA work well and others poorly makes me think that could have E1C-NB7 devices with clusters 0702 and 0B04 and others only with 0702.
Could you please send with zigbee Thing Mc the fingerprints of the plug that works well and the one that works badly?
And it would be important to see CLI logs of what we are talking about, I will be happy to try to solve it, but if you do not send them, this is useless and it is a waste of time and going over and over the same thing.
