Skip to content

Failed to sync time manuSpecificTuya.mcuSyncTime #28486

@u15jtau

Description

@u15jtau

What happened?

I'm experiencing frequent time sync issues in Zigbee2MQTT when using the SLZB-MR4 (EFR32MG26) adapter with firmware version 20240602. These messages appear in the Zigbee2MQTT log continuously to the point I'm getting multiple per second.

Environment
Zigbee2MQTT version: 2.6.1
Node.js version: 18.20.8
npm version: 10.8.2
OS: Ubuntu 24.04.3 LTS (noble)
Running in: Proxmox VM (Ubuntu guest)
MQTT broker: [insert broker name/version]
Zigbee adapter: SLZB-MR4
Chipset: EFR32MG26
Adapter firmware: 20240602
Adapter type (Z2M config): ember

Coordinator Info
Coordinator type: ember
Firmware version: 20240602
Network state: Running
Zigbee2MQTT DB: Clean/fresh install (no previous devices or database)
Adapter connected via ethernet.

Zigbee Network
Total devices: 59
Repeater devices: 50+
Signal strength (LQI): Most devices have LQI ≥ 120
Network health: Stable, no routing issues, no pairing loss
Given the high repeater count and strong LQI across the network, this appears not to be caused by network instability or interference.

Problem Behavior
Time sync errors appear in logs every few minutes
No device dropouts or visible loss of communication
No pairing loss
Issue started immediately on clean install
Survives reboots, adapter reconnects, and restarts

zhc:tuya: Failed to sync time with '0xa4c138ad92360951' (Error: ZCL command 0xa4c138ad92360951/1 manuSpecificTuya.mcuSyncTime({"payloadSize":8,"payload":[48,75,178,196,48,76,63,100]}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Delivery failed for '36257'.))

What I’ve Tried
Clean install of Ubuntu 24.04.3 LTS
Clean install of Zigbee2MQTT 2.6.1
Flashed latest firmware (20240602) to SLZB-MR4
Downgraded Node.js from v22 to v18 LTS
Reinstalled dependencies via npm ci
Enabled debug logging
Restarted Zigbee2MQTT and VM

Let me know what else you need and I'd be happy to provide the relevant information.

The main device I have is https://www.zigbee2mqtt.io/devices/ZMS-206US-4.html#zemismart-zms-206us-4

What did you expect to happen?

I expect that the message is not shown and the time is synced.

How to reproduce it (minimal and precise)

This started from the moment I added the first device.

Zigbee2MQTT version

2.6.1

Adapter firmware version

20240602

Adapter

SLZB-MR4

Setup

Intel NUC with proxmox on an unbuntu server.

Device database.db entry

{"id":16,"type":"Router","ieeeAddr":"0xa4c138e18df4b70e","nwkAddr":32042,"manufId":4417,"manufName":"_TZE204_wwaeqnrf","powerSource":"Mains (single phase)","modelId":"TS0601","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[4,5,61184,0],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"65503":"K0iK0iK0iK0iK0i�K0i�K0i�K0i","65506":56,"65508":0,"65534":0,"modelId":"TS0601","manufacturerName":"_TZE204_wwaeqnrf","powerSource":1,"zclVersion":3,"dateCode":"","appVersion":74}}},"binds":[],"configuredReportings":[],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":74,"dateCode":"","zclVersion":3,"interviewCompleted":true,"interviewState":"SUCCESSFUL","meta":{"configured":332242049},"lastSeen":1756951491547}

Debug log

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    problemSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions