FW 2.5.1.140 broke Zemismart Zigbee Blind Driver

Get Help Apps
1

Firmware update from 2.5.0.159 to 2.5.1.140 broke all my blinds. Logs were reporting “not a Tuya device”. A rollback to 2.5.0.159 fixed the issue.

[RELEASE] Zemismart Zigbee Blind Driver

3

We will need some more details on what your device is :

Also, make sure you are using the latest version of the community driver :

The latest version is 3.6.1 :

image
image484×160 11.3 KB

In the driver code, there is a debug message "Not a Tuya Message"
Posting the complete debug log will help to identify the issue.

4

I have multiple roller shades using this driver, and haven't seen this. Even during 2.5.1 Beta testing my devices were fine.

Model numbers and exact logs probably would be helpful here.

5

Thank you for your quick response.

Driver 3.6.1.

Attached is a log snippet from one of the blinds:

**dev:199**2026-07-31 08:07:39.932

debug

Beach Kitchen Shade parse: Not a Tuya Message descMap=[raw:catchall: 0000 0002 00 00 0040 00 48DF 00 00 0000 00 00 9A0000, profileId:0000, clusterId:0002, clusterInt:2, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:48DF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[9A, 00, 00]]

**dev:199**2026-07-31 08:07:33.807

debug

Beach Kitchen Shade Tuya MCU Version Respinse : [3B, 68, 40]

**dev:199**2026-07-31 08:07:13.726

debug

Beach Kitchen Shade parse: ACK command=24

**dev:199**2026-07-31 08:07:13.602

debug

Beach Kitchen Shade sending time data : [he cmd 0x48DF 0x01 0xEF00 0x24 {00086A6BCB116A6C57B1}, delay 2000]

**dev:199**2026-07-31 08:07:13.600

debug

Beach Kitchen Shade time synchronization request

**dev:199**2026-07-31 08:07:10.021

debug

Beach Kitchen Shade parse (12): fault code (DP 12) value = 0

**dev:199**2026-07-31 08:07:10.018

debug

Beach Kitchen Shade parse: descMap=[raw:catchall: 0104 EF00 01 01 0040 00 48DF 01 00 0000 02 01 00010C05000100, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:48DF, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 01, 0C, 05, 00, 01, 00]]

**dev:199**2026-07-31 08:07:09.891

debug

Beach Kitchen Shade parse: Not a Tuya Message descMap=[raw:48DF01000012DFFF42052013FF3111, dni:48DF, endpoint:01, cluster:0000, size:12, attrId:FFDF, encoding:42, command:0A, value: ÿ1, clusterInt:0, attrInt:65503]

**dev:199**2026-07-31 08:07:08.552

debug

Beach Kitchen Shade Tuya check-in message (attribute 0001 reported: 48)

**dev:199**2026-07-31 08:07:03.300

debug

Beach Kitchen Shade ZDO cluster 0013 device announcement Device network ID: 48DF, Capability Information: 80

7

Thanks for the quick reply. Driver 3.6.1. A log snippet:

**dev:199**2026-07-31 08:07:39.932

debug

Beach Kitchen Shade parse: Not a Tuya Message descMap=[raw:catchall: 0000 0002 00 00 0040 00 48DF 00 00 0000 00 00 9A0000, profileId:0000, clusterId:0002, clusterInt:2, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:48DF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[9A, 00, 00]]

**dev:199**2026-07-31 08:07:33.807

debug

Beach Kitchen Shade Tuya MCU Version Respinse : [3B, 68, 40]

**dev:199**2026-07-31 08:07:13.726

debug

Beach Kitchen Shade parse: ACK command=24

**dev:199**2026-07-31 08:07:13.602

debug

Beach Kitchen Shade sending time data : [he cmd 0x48DF 0x01 0xEF00 0x24 {00086A6BCB116A6C57B1}, delay 2000]

**dev:199**2026-07-31 08:07:13.600

debug

Beach Kitchen Shade time synchronization request

**dev:199**2026-07-31 08:07:10.021

debug

Beach Kitchen Shade parse (12): fault code (DP 12) value = 0

**dev:199**2026-07-31 08:07:10.018

debug

Beach Kitchen Shade parse: descMap=[raw:catchall: 0104 EF00 01 01 0040 00 48DF 01 00 0000 02 01 00010C05000100, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:48DF, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 01, 0C, 05, 00, 01, 00]]

**dev:199**2026-07-31 08:07:09.891

debug

Beach Kitchen Shade parse: Not a Tuya Message descMap=[raw:48DF01000012DFFF42052013FF3111, dni:48DF, endpoint:01, cluster:0000, size:12, attrId:FFDF, encoding:42, command:0A, value: ÿ1, clusterInt:0, attrInt:65503]

**dev:199**2026-07-31 08:07:08.552

debug

Beach Kitchen Shade Tuya check-in message (attribute 0001 reported: 48)

**dev:199**2026-07-31 08:07:03.300

debug

Beach Kitchen Shade ZDO cluster 0013 device announcement Device network ID: 48DF, Capability Information: 80

8

Thank you for the logs. They look normal, the “Not a Tuya Message” entries are debug messages for keep-alive packets and do not indicate an error.

Were these logs produced on the old Hubitat platform version or on the latest version?

Please also clarify exactly what is not working. If the Open, Close, or Stop commands are not working, enable debug logging and post the complete logs captured while trying each command.

We still need the exact device model and manufacturer. Please follow the “How to identify a Zigbee device” instructions linked in my previous post and share the complete device information.