Hi @gmanor77
That problem is because device has not been installed correctly.
Remove the device with the app and re-add the device with the search nearby option.
It has to be paired directly with this driver for it to set up correctly.
Hi @CiaoPapa
Addrd to this driver version
───────────────────────────────────────────────────
Name Zigbee Moisture Sensor Mc
Version 2023-01-06T15:44:03.092125865
───────────────────────────────────────────────────
- id: "_TYZB01_ttvdudvx-Sensor"
deviceLabel: TS0207 Water Sensor
manufacturer: _TYZB01_ttvdudvx
model: TS0207
deviceProfileName: moisture-battery
I have collected CLI logs for pairing a Sengled E1C-NB7 plug with the stock driver. Logs are here: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.. The device in question is d9cf7cd7-6734-41c2-99fd-9cce663cb9d4.
Interestingly, the plug worked correctly with the stock driver after pairing. Then, I pulled it out of the wall and moved it to its permanent place, and after plugging it back in, it has the problem again.
2023-06-14T00:59:08.150130448+00:00 INFO Zigbee Switch <ZigbeeDevice: d9cf7cd7-6734-41c2-99fd-9cce663cb9d4 [0x853A] (Sengled Outlet)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x853A, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0xFF, rssi: -50, body_length: 0x000A, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x25, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0302, ZclStatus: SUCCESS, DataType: Uint24, Divisor: 10000 > > > >
2023-06-14T00:59:08.160785826+00:00 TRACE Zigbee Switch Found ZigbeeMessageDispatcher handler in zigbee_switch
2023-06-14T00:59:08.162491515+00:00 INFO Zigbee Switch Executing ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: Divisor
2023-06-14T00:59:08.164624656+00:00 DEBUG Zigbee Switch Sengled Outlet device thread event handled
2023-06-14T00:59:08.207762285+00:00 TRACE Zigbee Switch Received event with handler zigbee
2023-06-14T00:59:08.208217057+00:00 INFO Zigbee Switch <ZigbeeDevice: d9cf7cd7-6734-41c2-99fd-9cce663cb9d4 [0x853A] (Sengled Outlet)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x853A, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0xFF, rssi: -49, body_length: 0x000A, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x26, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0301, ZclStatus: SUCCESS, DataType: Uint24, Multiplier: 1 > > > >
Hi @junrau
As I was saying you, this device uses only cluster 0702, SimpleMetering.
On setup it reads the divisor and multiplier on the device and the device responds with a divisor=10000 and a multiplier=1.
These values are stored in permanent memory and are used in default handlers to calculate both the InstantaneousDemand for power in w and the CurrentSummationDelivered for Energy in kWh. with the same divisor 10000.
These values stored in permanent memory are lost if you make a driver change, or were lost until now, if the procedure has not been changed without warning.
When you return to the stock driver, the initial configuration is not performed and the divisor and multiplier values will not be read again and therefore the default multiplier and divisor values = 1 will be used.
To fix this you have to uninstall the device and reinstall it from scratch.
In my driver if you put the preference:
- name: "simpleMeteringDivisor1"
title: "Custom Simple Metering Divider"
description: "If you device has Power & Energy measurement then this Custom Divisor is used for Total Energy Calculations. Some devices could use it for Power Instantaneous Demand calculations too, instead of the Active Power. SET TO DEFAULT VALUE= 0, TO USE DEFAULTS DIVISOR OF DRIVER."
required: false
preferenceType: number
definition:
minimum: 0
maximum: 1000000
default: 0
It will work perfectly even if you change the driver and come back to it later, since the custom dividers configuration will be used again.
If you have any problem with the stock driver you should tag to nayelyz or AlejandroPadilla so they can report to fix it
I also need help with this device,
It’s already added using your driver but when I check the accumumulative energy consumption seems incorrect (too high) since the fridge only consume 78w but the accumulative power already 171kwh within 48hours.
I use these settings, I put 1 because if I put 0 in the custom simple metering divisor and in custom electrical measure divisor it will not work
Any clue on the correct divisors parameter?
Thank you
Added to this driver version
───────────────────────────────────────────────────
Name Zigbee Multi Switch and Child Mc
Version 2023-06-15T11:53:42.142582547
───────────────────────────────────────────────────
- id: "TS0012/_TYZB01_2athzhfr"
deviceLabel: Two Switch
manufacturer: _TYZB01_2athzhfr
model: TS0012
deviceProfileName: two-switch
Thank you. Not sure why it is not detected yet. I’ll try to figure it out.
I’m having an issue with the Keen Vents. I figured I would remove them and then add them using these drivers. But only two of the vents show up with the drivers available. Fortunately, I only messed with four of my Keen Vents. I think the two vents that show up with these drivers available to use, are my oldest Keen vents.
The other two I tried will not show these drivers to install. Or any other drivers to choose from
Here is the info from one of my other Keen Vents. I’m hoping they are they same as the two I’m having issues with. I did not want to remove any other vents, since once they get added back, I have no access to the temperature or pressure. The two older vents, currently running these Edge drivers, show the correct info.
Metrics * Last Hop LQI: 205
- Last Hop RSSI: -53
- Received Messages From Device: 4154
- Received Messages From Device (Duplicates): 3
- Messages Transmitted to Device: 630
- Messages Transmitted to Device (Failures): 343
- Updated Time: 2023-06-15 6:36 PM EDT
Data * application: 13
- endpointId: 01
- firmwareFullVersion: 00000013
- firmwareImageType: 0
- firmwareManufacturerCode: 4443
- manufacturer: Keen Home Inc
- model: SV01-412-MP-1.1
- zigbeeNodeType: SLEEPY_END_DEVICE
Raw Description 01 0104 0003 00 0D 0000 0001 0003 0004 0005 0006 0008 0020 0402 0403 0B05 FC01 FC02 01 0019
Firmware * Current Version: 0x00000013
- Target Version: 0x00000013
- Last Updated: N/A
- Last Checked: 2021-10-05 7:59 AM EDT -
Hi @aaronwt
Added to this driver version
This driver is identical to the stock driver, to which I already added 4 more models to another user some time ago and I think they work
───────────────────────────────────────────────────
Name Zigbee Vent Mc
Version 2023-06-16T14:57:34.990565025
───────────────────────────────────────────────────
- id: "keen/SV01-412-MP-1.1"
deviceLabel: Keen SV01-412-MP-1.1 Vent
manufacturer: Keen Home Inc
model: SV01-412-MP-1.1
deviceProfileName: vent-profile-1
Having a Moes switch 1gang switch for a couple of lights in my garage. 2 questions:
- The Led light is working in the opposite order. It is on when the light is on, off when the light is off. Is there a way to revert this? Not sure if this helps.
- Is there a way to do multi-control association? I have two switches for a 2-way-control. The one at the entrance of the garage is an old 2-way switch. The new one is this one : https://www.aliexpress.com/item/1005002638421893.html and is linked to the kitchen. If I change the old one/dumb one with the one above/new one, how can I link the two switches in the app?
Update: Smartthings picked up Driver Zigbee Switch Mc, Version: 2023-06-12T18:00:59.680552366 but I cannot see what kind of data the switch has from the EDI 
Update #2: It is like this button. So I guess it is not considered from the driver Zigbee Switch Mc, right? I get Zigbee Thing Mc and Zigbee Switch when I try to select a driver in the app. I just installed ST Zigbee Button Mc and gonna wait another 12 hours to see if it populates.
Hi @nickolasemp
This setting is specific to some Tuya devices.
It would be necessary to modify the driver to differentiate devices and apply those settings to those devices. Sorry, I’m not going to do it for now.
The way you can do it is to buy a TUYA hub, between €15 or €20, pair it with tuya app and adjust it. Afterwards you return to smartthings and the settings are maintained
I don’t understand exactly what you want to do, but if what you want is to control the garage light from two different smart switches, the type you send in the link, and removing the dummy switches, it doesn’t seem physically possible to me.
You could try synchronizing them with routines or rules, but I don’t know if it will work well.
I don’t know if anyone has experience doing that with these types of switches
Simple 2-way to 200-way control is coming from Routine. No matter which switch or remote or sensor turned light on or off, other will do opposite.
200-way comes from 200 devices limit
Thanks!! That worked!! The two vents I was having issues with were able to load the driver now. And I was able to switch my other Keen vents to it as well.
1 Like
ok, I have the tuya hub lying somewhere around here, thank you for the hint 
If you look at the link I have shared, it shows how to do it, but in the app (look for Update #3). I suppose that it is a work-around in the app of Moes switches more like a real 2-way switch.
I don’t have any drivers that work with those buttons, wireless switches with battery.
What the Tuya app does is the same as what smartthings do with groups of lights or routines
Added to this driver version
───────────────────────────────────────────────────
Name Zigbee Multi Switch and Child Mc
Version 2023-06-18T20:23:00.544739853
───────────────────────────────────────────────────
- id: "TS011F/_TZ3000_in5s3wn1"
deviceLabel: TS011F Switch
manufacturer: _TZ3000_in5s3wn1
model: TS011F
deviceProfileName: five-outlet
1 Like