Fingerprint issues, maybe. That happened to me when joining devices that were not being handled by any driver nor dth.
@erickv
I have tried with ewelink, moes, lidl, samotech and they all report the same message
Wait a moment, i have not published yet
1 Like
@BaRaD5,
I published as switch without power meter.
If works for you then I will modify the switch power driver
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Switch for Test │
│ Version │ 2022-01-15T18:39:50.798733 │
└─────────────┴──────────────────────────────────────┘
- id: "TYZB01_b1ngbmlm/Plug"
deviceLabel: TYZB01 Plug
manufacturer: _TYZB01_b1ngbmlm
model: TS0112
deviceProfileName: single-switch-plug
1 Like
I have seen in the zigbee 3.0 specification that the attribute 0x4003 is optional.
I don’t know how the Tuya platform will do it
Is there any way to identify that the device just did a power On?
I have only seen that it emits a message from the Basic cluster with the generic body data
2022-01-15T20:27:27.948497204+00:00 TRACE Zigbee Switch v5.6 Received event with handler zigbee
2022-01-15T20:27:27.967910871+00:00 INFO Zigbee Switch v5.6 <ZigbeeDevice: 782297fd-21de-4fbd-b2b2-884bc9878a04 [0xFC69] (Lidl Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x02, < AddressHeader || src_addr: 0xFC69, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: Basic >, lqi: 0x70, rssi: -72, body_length: 0x000B, < ZDOMessageBody || < ZDOHeader || seqno: 0x81 >, GenericBody: 80 B6 04 02 00 97 6D 28 00 00 > >
@Mariano_Colmenarejo - Good day. I just went on …41.x firmware beta. All my power numbers are now crazy high (1000x). Do you have plans to adjust the math for these drivers?
Update: If I remove some of the devices (sengled power outlet) and re add things seem to report power right…. Others not (centralize power outlet).
Hi Mariano.
You can add the switch 3 plug to the zigbee-multi-switch-Zemismart driver, this was not added yet.
The fingerprints is:
id: “3A Smart / LXN3S2”
deviceLabel: 3A Smart 3 Switch
manufacturer: 3A Smart Home DE
model: LXN-3S27LX1.0
deviceProfileName: three-switch
Thank you.
Added to thid driver version
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Multi Switch Zemismart Mc │
│ Version │ 2022-01-16T15:30:24.100704 │
└─────────────┴──────────────────────────────────────┘
- id: "3A Smart/LXN-3S27LX1.0"
deviceLabel: 3A Smart 2 Switch
manufacturer: 3A Smart Home DE
model: LXN-3S27LX1.0
deviceProfileName: three-switch
Hi Mariano.
I have a problem with the Innr plug. With your driver
Zigbee Switch Power Mc the power meter is multiplied by 1000 (this after updating the hub to version 41).
Can you also insert a system to reset the counters?
My friend, this driver was perfect, thanks again for the help!
1 Like
As the libraries have changed, it is possible that they have fixed some and damaged others.
you can try to reinstall the device so that it is configured again with the values of the divisor and multiplier that the device returns. Let’s see if it fixes.
There is also a new stock driver in the Beta channel smartthings zigbee light switch that has many devices, I don’t know if yours will be
Hello,
As the libraries have changed, it is possible that they have fixed some and damaged others.
I have not any power meter device to test.
I will see when see wath changes they have done on libraries
Hi Mariano,
I know that is not recommended to pair hue bulbs because the network can be messed up. But I just got 2 for buying echo devices, so I don’t think is worthy to buy the hue bridge.
Could an edge driver be developed?
Added to this version of driver
Tell me if works, please
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Light Multifunction Mc │
│ Version │ 2022-01-16T21:28:21.774767 │
└─────────────┴──────────────────────────────────────┘
- id: "Signify/LWA017"
deviceLabel: Bulb LWA017
manufacturer: Signify Netherlands B.V.
model: LWA017
deviceProfileName: switch-level
That was fast!!
It pairs correctly and the dimmer level works good as well. However, for the progressive ON/OFF, the dimmer level is increased/decreased 1% each 3 or 4 seconds, so it would take several minutes to finish.
On top of that, when progressive OFF is not selected, the light is progressively off anyway.
Thanks!
For the progressive on and off, check the time settings for on and off and what you have to do if you press the switch during the progressive on or off, it is a bit messy to coordinate at first
@Mariano_Colmenarejo Hi my friend, how are you? With the last change the vibration sensor looks great, it’s working very well, @Glauber_GD was also successful in the tests. Thanks a lot for the help. 
1 Like
I see. I don’t really need this functionality, but in case this is useful for anyone:
- Progressive ON active: the light switch on to the last dimmer value and inmediatly goes to the 1% value and start increasing according to configuration
This function was intended to replace the gentle wake up smart app.
but can also be used for other things
I have been using it daily in a lamp to turn on progressively at sunset, from 40% to 80% in 15 minutes and it always does it perfectly.
I don’t know what values you use to see what can happen in your lamp.
the first thing the driver does when on is pressed or receives an on command and progressive on is activated is to set the initial level to the initial value in preferences
1 Like
@Paul_Oliver
I’ve moved this answer to this thread.
Hello @Paul_Oliver, thanks to the log sent I can try to do something.
I have seen this driver receive the normal messages of false = off and true = on and others duplicate messages false = 0 and true = 1 , which are mixed with the normal ones.
This causes changes of state that are sometimes contradictory since duplicate messages arrive followed by or mixed with different values, which produce the emission of events that do not correspond to the real state of the device.
Without knowing why this happens, I have made some corrections in the driver to see what result they give.
With others switches only receive false =off and true = on messages.
With the modification they also work well to see what happens.
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Switch Mc │
│ Version │ 2022-01-17T11:31:07.881443 │
└─────────────┴──────────────────────────────────────┘
1 Like