Zemismart Wireless Wall Switch _TZ3000_tk3s5tyg Tuya TS0041 - Fast discharge + device announcements

[robertalexa]

Hi,

For the last 4 months I have been using 4 Zemismart Wireless Wall Switches 1 Gang available at
https://www.aliexpress.com/item/4001227549409.html

In these 4 months I have changed the batteries more than once per month for each of these devices. I have tried different brands including Duracell without noticing any difference in their longevity.

In this post I will be using only 1 of my devices as reference.

On top of that, despite the device "allegedly" reporting the battery state, the battery level never changes once the device is paired up. For example, new battery, pair the device, it usually says 90% battery, and it remains at 90 all the way until the battery dies.

Here is the device information from the database file.

{"id":7,"type":"EndDevice","ieeeAddr":"0x804b50fffe0b6a8f","nwkAddr":14083,"manufId":4098,"manufName":"_TZ3000_tk3s5tyg","powerSource":"Battery","modelId":"TS0041","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":0,"inClusterList":[0,1,6],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"modelId":"TS0041","manufacturerName":"_TZ3000_tk3s5tyg","powerSource":3,"zclVersion":3,"appVersion":65,"stackVersion":0,"hwVersion":1,"dateCode":""}},"genPowerCfg":{"attributes":{"batteryPercentageRemaining":180}}},"binds":[{"cluster":1,"type":"endpoint","deviceIeeeAddress":"0x00124b0021b953c1","endpointID":1}],"configuredReportings":[{"cluster":1,"attrId":33,"minRepIntval":3600,"maxRepIntval":62000,"repChange":0}],"meta":{}}},"appVersion":65,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{"configured":1},"lastSeen":1626691841882}

On top of this, I have noticed that the devices announce themselves approximately every hour and 1 or 2 minutes. Here is everything for this device for the last few hours (the device was not pressed so you won't see any actions).

Zigbee2MQTT:debug 2021-07-19 08:45:19: Device 'Rob's Nightstand Light Switch' announced itself,
Zigbee2MQTT:info  2021-07-19 08:45:19: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"Rob's Nightstand Light Switch","ieee_address":"0x804b50fffe0b6a8f"},"type":"device_announce"}',
Zigbee2MQTT:info  2021-07-19 08:45:19: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"Rob's Nightstand Light Switch"},"type":"device_announced"}',
Zigbee2MQTT:debug 2021-07-19 08:45:22: Received Zigbee message from 'Rob's Nightstand Light Switch', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0,
Zigbee2MQTT:debug 2021-07-19 09:47:05: Device 'Rob's Nightstand Light Switch' announced itself,
Zigbee2MQTT:info  2021-07-19 09:47:05: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"Rob's Nightstand Light Switch","ieee_address":"0x804b50fffe0b6a8f"},"type":"device_announce"}',
Zigbee2MQTT:info  2021-07-19 09:47:05: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"Rob's Nightstand Light Switch"},"type":"device_announced"}',
Zigbee2MQTT:debug 2021-07-19 09:47:09: Received Zigbee message from 'Rob's Nightstand Light Switch', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0,
Zigbee2MQTT:debug 2021-07-19 10:48:53: Device 'Rob's Nightstand Light Switch' announced itself,
Zigbee2MQTT:info  2021-07-19 10:48:53: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"Rob's Nightstand Light Switch","ieee_address":"0x804b50fffe0b6a8f"},"type":"device_announce"}',
Zigbee2MQTT:info  2021-07-19 10:48:53: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"Rob's Nightstand Light Switch"},"type":"device_announced"}',
Zigbee2MQTT:debug 2021-07-19 10:48:53: Device 'Rob's Nightstand Light Switch' announced itself,
Zigbee2MQTT:info  2021-07-19 10:48:53: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"Rob's Nightstand Light Switch","ieee_address":"0x804b50fffe0b6a8f"},"type":"device_announce"}',
Zigbee2MQTT:info  2021-07-19 10:48:53: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"Rob's Nightstand Light Switch"},"type":"device_announced"}',
Zigbee2MQTT:debug 2021-07-19 10:48:56: Received Zigbee message from 'Rob's Nightstand Light Switch', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0,
Zigbee2MQTT:debug 2021-07-19 11:50:37: Device 'Rob's Nightstand Light Switch' announced itself,
Zigbee2MQTT:info  2021-07-19 11:50:37: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"Rob's Nightstand Light Switch","ieee_address":"0x804b50fffe0b6a8f"},"type":"device_announce"}',
Zigbee2MQTT:info  2021-07-19 11:50:37: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"Rob's Nightstand Light Switch"},"type":"device_announced"}',
Zigbee2MQTT:debug 2021-07-19 11:50:41: Received Zigbee message from 'Rob's Nightstand Light Switch', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0,
Zigbee2MQTT:debug 2021-07-19 12:52:23: Device 'Rob's Nightstand Light Switch' announced itself,
Zigbee2MQTT:info  2021-07-19 12:52:23: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"Rob's Nightstand Light Switch","ieee_address":"0x804b50fffe0b6a8f"},"type":"device_announce"}',
Zigbee2MQTT:info  2021-07-19 12:52:23: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"Rob's Nightstand Light Switch"},"type":"device_announced"}',
Zigbee2MQTT:debug 2021-07-19 12:52:27: Received Zigbee message from 'Rob's Nightstand Light Switch', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0

I am not sure if this means:

• the device falls off the network (but I have nothing in the logs to make me think of that. The devices are close to other powered devices in the mesh, and there are other zigbee devices connected to the same nodes that do not disconnect)
• fall into deep sleep (idk if devices announce themselves again when they come back?)
• or they are just crappy devices?

Regarding the deep sleep, there are many occasions where i press the switch and nothing happens for the first action (single, double, hold) but then it does work if i repeat the action (this is really annoying me) - because this happens sporadically (basically when i go to bed) I have not found the chance to investigate the logs. So I am not sure if the device is sleeping or what, this is just a guess.

I was hoping that maybe some of you have this device and can share their story, or if anyone else can spot an issue here, or can come with some recommendations.

TLDR:

• device announces itself every hour
• battery drains super fast for a device that gets barely used - roughly dies every 2 weeks
• sometimes first action doesn't do anything but works on second try

Many thanks,
Rob

Debug info

Zigbee2MQTT version: 1.20.0-1
Adapter hardware: Electrolama zig-a-zig-ah!

[MattWestb]

The device announce and that the firs key press not working is the same problem.
Its one Zigbee 3 device and its checking in to its parent between its being in sleep mode.
If its to long between the checkins its its must doing handshake with its parent for going back in to thee network.

It can also being that the pull control cluster in the parent is not being OK configured or the host system is setting it up wrongly (or the device is making it bad it self).
I was testing the problem that IKEA controllers super draining batteries and is setting the checkin interval longer then the device is requesting from its parent (child time out request then pairing) was the device doing device announce then every pull of its parent = very bad for battery and system performance.

One more thing tuya have one old version of the device with TYZS5 that is having one MG13 with 512 kb flash and 64 kb ram that is enough (the dark module with pads on 2 sides) but dont have enough pins for the 4 button model.
The newer variant is with MG21 (white with pads on 3 sides) that is having more then the double hardware performance and IO pads that is one of the best on the market but both is being bad mounted and the antenna is very disturbed of metal on the PCB so the layout is pity bad from the radio part.

Sniffing the Zigbe traffic is the only way to see wot is going wrong between the device and its parent.

[robertalexa]

@MattWestb Hi Matt and thank you for your reply.

In my case:

I don't think the problem is with the parent. The reason for my assumption is that i have 4 switches that suffer from this problem. 2 of them are connected to the device in the screenshot, 1 is connected to a different type of plug and the last 1 is connected directly to coordinator.

I also don't think it is a problem with range or signal. All 4 devices are within 1 metre from their parent. Also i would most likely see variation in the timestamp when the devices announce themselves, rather than 1h and 1 or 2 minutes every time.

So the other option from your suggestions is regarding the polling of devices. But as mentioned above, the devices are connected to different parents, including coordinator. So idk where to go at this point.

@Koenkk do you have any thoughts please?

Rob

[Koenkk]

@robertalexa device announcement are usually send when the device boots (e.g. after power loss of a AC powered bulb or if a device crashes due to some issue in the firmware). Do you maybe have the original gateway, if yes does the same issue happen here?

[robertalexa]

@Koenkk Thanks for your prompt reply!

Unfortunately i don't have a tuya gateway, but i am tempted to buy one purely on this basis of sniffing and testing.

As to your statement, i was imagining the same to be true, but this happens with brand new batteries too. And it is super weird how it happens every hour and 1 minute or 2.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[robertalexa]

@Koenkk a lot of time has passed since this, but I have finally found some time to purchase a tuya gateway and sniff the traffic between this switch and it. I have left it running for a few hours and did NOT see the same behaviour. The device does not re announce itself, nor does the blue light flash (as it does when announcing on z2m).

Would you be kind to have a look and see if you notice anything that is handled differently than in z2m? Currently I have 4 of these switches in use with z2m. The full description of the issue is in the first comment.

Thanks in advance

Notes:

• i had to zip the file because github doesn't like pcapng files
• the sniff should show the device first pairing, while doing that i have also added the required key to decrypt
• there is only communication from 2 devices: gateway and switch
• the command for single/double/hold shows as unknown in wireshark.

Tuya Gateway Sniff

switch-wireshark.zip

[robertalexa]

To further add to this.
Using the tuya gateway, i can check for device connection quality:

• after the switch has been used the results comes with excellent
• after a while (in my testing a bit over an hour) the device can't be reached. Note: tuya says make sure to wake up battery devices before doing this. But i didn't just to confirm the device is actually sleeping

Knowing the device is sleeping, i press the button and the tuya automation triggers first time, unlike z2m. In z2m the device will most likely need to re-announce, re-connect, and on second attempt it will work fine. That is for another while when it goes to sleep. Though every hourish the device re-announces, and if you press the button for the first time (coincidentaly) after that time, it will work first try

[Koenkk]

@robertalexa could you try with the following definition (I modified the configure to match the commands send by the tuya gateway)

{
        zigbeeModel: ['TS0041'],
        fingerprint: [{manufacturerName: '_TZ3000_tk3s5tyg'}],
        model: 'TS0041',
        vendor: 'TuYa',
        description: 'Wireless switch with 1 button',
        whiteLabel: [{vendor: 'Smart9', model: 'S9TSZGB'}, {vendor: 'Lonsonho', model: 'TS0041'}, {vendor: 'Benexmart', model: 'ZM-sui1'}],
        exposes: [e.battery(), e.action(['single', 'double', 'hold'])],
        fromZigbee: [fz.tuya_on_off_action, fz.battery],
        toZigbee: [],
        configure: async (device, coordinatorEndpoint, logger) => {
            const endpoint = device.getEndpoint(1);
            await endpoint.read('genBasic', [0x0004, 0x000, 0x0001, 0x0005, 0x0007, 0xfffe]);
            await endpoint.write('genBasic', {0xffde: {value: 0x13, type: 0x20}});
            await reporting.bind(endpoint, coordinatorEndpoint, ['genPowerCfg']);
            try {
                await reporting.batteryPercentageRemaining(endpoint);
            } catch (error) {/* Fails for some: https://github.com/Koenkk/zigbee2mqtt/issues/6313 */}
        },
    }

[robertalexa]

@Koenkk Thanks a lot for your prompt reply.

Could you please clarify sth for me? Once adding this in (via portainer on HA addon and restarting via portainer for the changes to persist), is it necessary to press the reconfigure button for each device (since this is in configure)?

[robertalexa]

Ive done it anyway.

One thing to note is that configuration fails (but it failed before anyway) - but maybe only the first attempt failed?

Info Configuring 'Rob's Nightstand Light Switch'
Error Failed to configure 'Rob's Nightstand Light Switch', attempt 1 (Error: Read 0x804b50fffe0b6a8f/1 genBasic([4,0,1,5,7,65534], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 14083 - 1 - 41 - 0 - 1 after 10000ms) at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35) at listOnTimeout (internal/timers.js:557:17) at processTimers (internal/timers.js:500:7))
Info MQTT publish: topic 'zigbee2mqtt/bridge/response/device/configure', payload '{"data":{"id":"Rob's Nightstand Light Switch"},"error":"Failed to configure (Read 0x804b50fffe0b6a8f/1 genBasic([4,0,1,5,7,65534], {\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":true,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null,\"writeUndiv\":false}) failed (Timeout - 14083 - 1 - 41 - 0 - 1 after 10000ms))","status":"error","transaction":"7ap2o-3"}'
Info MQTT publish: topic 'zigbee2mqtt/Rob's Nightstand Light Switch', payload '{"action":"single","battery":100,"last_seen":1642524978616,"linkquality":102,"voltage":3000}'
Info MQTT publish: topic 'zigbee2mqtt/Rob's Nightstand Light Switch', payload '{"action":"","battery":100,"last_seen":1642524978616,"linkquality":102,"voltage":3000}'
Info MQTT publish: topic 'zigbee2mqtt/Rob's Nightstand Light Switch/action', payload 'single'
Info MQTT publish: topic 'zigbee2mqtt/Rob's Nightstand Light Switch', payload '{"action":null,"battery":100,"last_seen":1642524978748,"linkquality":102,"voltage":3000}'
Info MQTT publish: topic 'zigbee2mqtt/Rob's Nightstand Light Switch', payload '{"action":null,"battery":100,"last_seen":1642524978791,"linkquality":102,"voltage":3000}'

Throughout the use of these devices over the last year or so I have never seen a battery change more than the initial value.

The battery is reported with the tuya gateway, but i have yet to see a decrease, only set this up a few days back with a brand new battery. So i will keep an eye on this one and come back with further findings. I wonder is this is also sth that is broken?

[Koenkk]

@robertalexa have you tried to force remove and repair the device?

[robertalexa]

@Koenkk Just for peach of mind i did that now with all 4 devices. This emulates a fresh/cold start. Device paired and configured successfully. (they were configured before anyway, but the battery percent never changed, not even when the batteries died).

I will continue normal use and report once I have more. It should only take me a few nights to notice if the light is randomly flashing (meaning it was re-announced) or not. If they don't then that might be a very good sign, and hopefully that increased the battery life span.

Thanks for your help, will comment here with findings.