Trying to connect ZemiSmart blinds - "No supported clusters found"

arp · October 10, 2021, 4:36pm

Platform information:
- Hardware: Helios 4 SoC. CPU: Marvell Armada 380/385 (armv7l), RAM: 2GB, Storage: 7G free on main drive (which is the only one OpenHAB should be using)
- OS: Armbian Buster. uname -a: Linux helios4.local 5.10.60-mvebu #21.08.1 SMP Wed Aug 25 18:44:04 UTC 2021 armv7l GNU/Linux
- Java Runtime Environment:

openjdk 11.0.12 2021-07-20
OpenJDK Runtime Environment (build 11.0.12+7-post-Debian-2deb10u1)
OpenJDK Server VM (build 11.0.12+7-post-Debian-2deb10u1, mixed mode)

openHAB version: 3.1.0-1
Issue of the topic: please be detailed explaining your issue

I’m trying to connect ZemiSmart blinds via Zigbee, using a HUSBZB-1 (Ember) coordinator. Trying to do so gives me this result:

I’ve confirmed that my coordinator setup works with a Samsung motion sensor, and that the blinds work with their included remote. It looks like it is supported by Zigbee2MQTT (see also blakadder’s compat page), but I’d rather connect it directly to OpenHAB than buy additional hardware. What are my next steps from here?

Please post configurations (if applicable):
- Items configuration related to the issue
  - Zigbee coordinator: Ember coordinator, software flow control, 57600baud, normal ncp config & transmit power, 1 day child timeout, small network size
If logs where generated please post these here using code fences:

after increasing logging per the instructions,
dump from tail -f /var/log/openhab/openhab.log when trying to connect it:

2021-10-09 20:47:03.187 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH took EZSP frame to receive queue. Queue length 0
2021-10-09 20:47:03.189 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH added EZSP frame to receive queue. Queue length 0
2021-10-09 20:47:03.190 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameAck [ackNum=7, notRdy=false]
2021-10-09 20:47:04.179 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: TX EZSP queue size: 1
2021-10-09 20:47:04.181 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameData [frmNum=7, ackNum=7, reTx=false, data=14 00 18]
2021-10-09 20:47:04.187 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=7, ackNum=0, reTx=false, data=14 80 18 02]
2021-10-09 20:47:04.189 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: Frame acked and removed AshFrameData [frmNum=7, ackNum=7, reTx=false, data=14 00 18]
2021-10-09 20:47:04.190 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH took EZSP frame to receive queue. Queue length 0
2021-10-09 20:47:04.191 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH added EZSP frame to receive queue. Queue length 0
2021-10-09 20:47:04.193 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameAck [ackNum=0, notRdy=false]
2021-10-09 20:48:48.491 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B4E3F9FFFE0C5045: Handler dispose.
2021-10-09 20:48:48.493 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker removed for thingUID=zigbee:device:c6b9e12b5d:b4e3f9fffe0c5045
2021-10-09 20:48:53.969 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B4E3F9FFFE0C5045: Initializing ZigBee thing handler zigbee:device:c6b9e12b5d:b4e3f9fffe0c5045
2021-10-09 20:48:53.973 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B4E3F9FFFE0C5045: Coordinator status changed to ONLINE.
2021-10-09 20:48:53.975 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B4E3F9FFFE0C5045: Coordinator is ONLINE. Starting device initialisation.
2021-10-09 20:48:53.981 [DEBUG] [pp.discovery.ZigBeeNetworkDiscoverer] - B4E3F9FFFE0C5045: NWK Discovery starting node rediscovery
2021-10-09 20:48:53.984 [DEBUG] [pp.discovery.ZigBeeNetworkDiscoverer] - B4E3F9FFFE0C5045: NWK Discovery: Rediscovery using unicast to E2B0
2021-10-09 20:48:53.988 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - B4E3F9FFFE0C5045: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=B4E3F9FFFE0C5045 queueTime=0, state=WAITING, sendCnt=0, command=NetworkAddressRequest [0000/0 -> E2B0/0, cluster=0000, TID=--, ieeeAddr=B4E3F9FFFE0C5045, requestType=0, startIndex=0]]
2021-10-09 20:48:53.990 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction Manager: Send Next transaction. outstandingTransactions=0, outstandingQueues=1, sleepy=0/3
2021-10-09 20:48:53.991 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B4E3F9FFFE0C5045: Start initialising ZigBee Thing handler
2021-10-09 20:48:53.993 [DEBUG] [scovery.ZigBeeNodePropertyDiscoverer] - B4E3F9FFFE0C5045: ZigBee node property discovery start
2021-10-09 20:48:53.993 [DEBUG] [transaction.ZigBeeTransactionManager] - E2B0/0: Sending ZigBeeTransaction [ieeeAddress=B4E3F9FFFE0C5045 queueTime=6, state=WAITING, sendCnt=0, command=NetworkAddressRequest [0000/0 -> E2B0/0, cluster=0000, TID=3A, ieeeAddr=B4E3F9FFFE0C5045, requestType=0, startIndex=0]]
2021-10-09 20:48:53.996 [DEBUG] [scovery.ZigBeeNodePropertyDiscoverer] - B4E3F9FFFE0C5045: ZigBee node property discovery using basic cluster on endpoint E2B0/1
2021-10-09 20:48:54.000 [DEBUG] [transaction.ZigBeeTransactionManager] - transactionListenerAdded: 1 outstanding
2021-10-09 20:48:54.001 [DEBUG] [scovery.ZigBeeNodePropertyDiscoverer] - B4E3F9FFFE0C5045: ZigBee node property discovery using OTA cluster on endpoint E2B0/1
2021-10-09 20:48:54.003 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: NetworkAddressRequest [0000/0 -> E2B0/0, cluster=0000, TID=3A, ieeeAddr=B4E3F9FFFE0C5045, requestType=0, startIndex=0]
2021-10-09 20:48:54.005 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0000/0, destinationAddress=E2B0/0, profile=0000, cluster=0000, addressMode=DEVICE, radius=8, apsSecurity=false, ackRequest=true, apsCounter=63, rssi=--, lqi=--, payload=3A 45 50 0C FE FF F9 E3 B4 00 00]
2021-10-09 20:48:54.008 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - B4E3F9FFFE0C5045: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=B4E3F9FFFE0C5045 queueTime=0, state=WAITING, sendCnt=0, command=ReadAttributesCommand [Ota Upgrade: 0000/0 -> E2B0/1, cluster=0019, TID=--, identifiers=[2]]]
2021-10-09 20:48:54.010 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction Manager: Send Next transaction. outstandingTransactions=1, outstandingQueues=1, sleepy=0/3
2021-10-09 20:48:54.021 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX EZSP: EzspSendUnicastResponse [networkId=0, status=EMBER_SUCCESS, sequence=80]
2021-10-09 20:48:54.043 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction Manager: Send Next transaction. outstandingTransactions=1, outstandingQueues=1, sleepy=0/3
2021-10-09 20:48:54.043 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX EZSP: EzspIncomingRouteRecordHandler [networkId=0, source=E2B0, sourceEui=B4E3F9FFFE0C5045, lastHopLqi=255, lastHopRssi=-51, relayList=]
2021-10-09 20:48:54.045 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX EZSP: EzspIncomingRouteRecordHandler [networkId=0, source=E2B0, sourceEui=B4E3F9FFFE0C5045, lastHopLqi=255, lastHopRssi=-51, relayList=]
2021-10-09 20:48:54.095 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX EZSP: EzspIncomingMessageHandler [networkId=0, type=EMBER_INCOMING_UNICAST, apsFrame=EmberApsFrame [profileId=0000, clusterId=8000, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY, EMBER_APS_OPTION_RETRY], groupId=0, sequence=63], lastHopLqi=255, lastHopRssi=-51, sender=E2B0, bindingIndex=255, addressIndex=255, messageContents=3A 00 45 50 0C FE FF F9 E3 B4 B0 E2]
2021-10-09 20:48:54.098 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=E2B0/0, destinationAddress=0000/0, profile=0000, cluster=8000, addressMode=DEVICE, radius=0, apsSecurity=false, ackRequest=false, apsCounter=63, rssi=-51, lqi=FF, payload=3A 00 45 50 0C FE FF F9 E3 B4 B0 E2]
2021-10-09 20:48:54.100 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - B4E3F9FFFE0C5045: Node update. NWK Address=E2B0
2021-10-09 20:48:54.102 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - B4E3F9FFFE0C5045: Node E2B0 is not updated
2021-10-09 20:48:54.104 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: NetworkAddressResponse [E2B0/0 -> 0000/0, cluster=8000, TID=3A, status=SUCCESS, ieeeAddrRemoteDev=B4E3F9FFFE0C5045, nwkAddrRemoteDev=E2B0, startIndex=null, nwkAddrAssocDevList=[]]
2021-10-09 20:48:54.106 [DEBUG] [transaction.ZigBeeTransactionManager] - notifyTransactionCommand: NetworkAddressResponse [E2B0/0 -> 0000/0, cluster=8000, TID=3A, status=SUCCESS, ieeeAddrRemoteDev=B4E3F9FFFE0C5045, nwkAddrRemoteDev=E2B0, startIndex=null, nwkAddrAssocDevList=[]] 
2021-10-09 20:48:54.109 [DEBUG] [pp.discovery.ZigBeeNetworkDiscoverer] - B4E3F9FFFE0C5045: NWK Discovery NetworkAddressRequest returned from NetworkAddressResponse [E2B0/0 -> 0000/0, cluster=8000, TID=3A, status=SUCCESS, ieeeAddrRemoteDev=B4E3F9FFFE0C5045, nwkAddrRemoteDev=E2B0, startIndex=null, nwkAddrAssocDevList=[]]
2021-10-09 20:48:54.109 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction complete: ZigBeeTransaction [ieeeAddress=B4E3F9FFFE0C5045 queueTime=122, state=COMPLETE, sendCnt=1, command=NetworkAddressRequest [0000/0 -> E2B0/0, cluster=0000, TID=3A, ieeeAddr=B4E3F9FFFE0C5045, requestType=0, startIndex=0]]
2021-10-09 20:48:54.111 [DEBUG] [pp.discovery.ZigBeeNetworkDiscoverer] - B4E3F9FFFE0C5045: NWK Discovery: Rediscovery found network address to E2B0
2021-10-09 20:48:54.111 [DEBUG] [transaction.ZigBeeTransactionManager] - transactionListenerRemoved: 0 outstanding
2021-10-09 20:48:54.113 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - B4E3F9FFFE0C5045: transactionComplete, state=COMPLETE, outstanding=0
2021-10-09 20:48:54.114 [DEBUG] [pp.discovery.ZigBeeNetworkDiscoverer] - B4E3F9FFFE0C5045: NWK Discovery add node E2B0
2021-10-09 20:48:54.114 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction Manager: Send Next transaction. outstandingTransactions=0, outstandingQueues=1, sleepy=0/3
2021-10-09 20:48:54.116 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - B4E3F9FFFE0C5045: Updating node NWK=E2B0
2021-10-09 20:48:54.116 [DEBUG] [transaction.ZigBeeTransactionManager] - E2B0/1: Sending ZigBeeTransaction [ieeeAddress=B4E3F9FFFE0C5045 queueTime=109, state=WAITING, sendCnt=0, command=ReadAttributesCommand [Ota Upgrade: 0000/0 -> E2B0/1, cluster=0019, TID=3B, identifiers=[2]]]
2021-10-09 20:48:54.118 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX EZSP: EzspMessageSentHandler [networkId=0, type=EMBER_OUTGOING_DIRECT, indexOrDestination=E2B0, apsFrame=EmberApsFrame [profileId=0000, clusterId=0000, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY, EMBER_APS_OPTION_ENABLE_ADDRESS_DISCOVERY, EMBER_APS_OPTION_RETRY], groupId=0, sequence=80], messageTag=3A, status=EMBER_SUCCESS, messageContents=]
2021-10-09 20:48:54.119 [DEBUG] [transaction.ZigBeeTransactionManager] - transactionListenerAdded: 1 outstanding
2021-10-09 20:48:54.120 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX STA: msgTag=3A state=RX_ACK
2021-10-09 20:48:54.121 [DEBUG] [transaction.ZigBeeTransactionManager] - notifyTransactionProgress: TID=3A, state=RX_ACK, outstanding=1
2021-10-09 20:48:54.121 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - B4E3F9FFFE0C5045: Node update. NWK Address=E2B0
2021-10-09 20:48:54.123 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: ReadAttributesCommand [Ota Upgrade: 0000/0 -> E2B0/1, cluster=0019, TID=3B, identifiers=[2]]
2021-10-09 20:48:54.125 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=false, direction=SERVER_TO_CLIENT, disableDefaultResponse=false, manufacturerCode=0, sequenceNumber=59, commandId=0]
2021-10-09 20:48:54.126 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - B4E3F9FFFE0C5045: Node E2B0 is not updated
2021-10-09 20:48:54.127 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0000/1, destinationAddress=E2B0/1, profile=0104, cluster=0019, addressMode=DEVICE, radius=8, apsSecurity=false, ackRequest=true, apsCounter=64, rssi=--, lqi=--, payload=08 3B 00 02 00]
2021-10-09 20:48:54.139 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX EZSP: EzspSendUnicastResponse [networkId=0, status=EMBER_SUCCESS, sequence=81]
2021-10-09 20:48:54.161 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX EZSP: EzspIncomingRouteRecordHandler [networkId=0, source=E2B0, sourceEui=B4E3F9FFFE0C5045, lastHopLqi=255, lastHopRssi=-51, relayList=]
2021-10-09 20:48:54.163 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX EZSP: EzspIncomingRouteRecordHandler [networkId=0, source=E2B0, sourceEui=B4E3F9FFFE0C5045, lastHopLqi=255, lastHopRssi=-51, relayList=]
2021-10-09 20:48:54.212 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX EZSP: EzspIncomingMessageHandler [networkId=0, type=EMBER_INCOMING_UNICAST, apsFrame=EmberApsFrame [profileId=0104, clusterId=0019, sourceEndpoint=1, destinationEndpoint=1, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=64], lastHopLqi=255, lastHopRssi=-51, sender=E2B0, bindingIndex=255, addressIndex=255, messageContents=10 3B 01 02 00 86]
2021-10-09 20:48:54.214 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=E2B0/1, destinationAddress=0000/1, profile=0104, cluster=0019, addressMode=DEVICE, radius=0, apsSecurity=false, ackRequest=false, apsCounter=64, rssi=-51, lqi=FF, payload=10 3B 01 02 00 86]
2021-10-09 20:48:54.216 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - B4E3F9FFFE0C5045: Node update. NWK Address=E2B0
2021-10-09 20:48:54.218 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - B4E3F9FFFE0C5045: Node E2B0 is not updated
2021-10-09 20:48:54.220 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=false, direction=CLIENT_TO_SERVER, disableDefaultResponse=true, manufacturerCode=0, sequenceNumber=59, commandId=1]
2021-10-09 20:48:54.222 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReadAttributesResponse [Ota Upgrade: E2B0/1 -> 0000/1, cluster=0019, TID=3B, records=[ReadAttributeStatusRecord [status=UNSUPPORTED_ATTRIBUTE, attributeIdentifier=2]]]
2021-10-09 20:48:54.224 [DEBUG] [transaction.ZigBeeTransactionManager] - notifyTransactionCommand: ReadAttributesResponse [Ota Upgrade: E2B0/1 -> 0000/1, cluster=0019, TID=3B, records=[ReadAttributeStatusRecord [status=UNSUPPORTED_ATTRIBUTE, attributeIdentifier=2]]] 
2021-10-09 20:48:54.226 [DEBUG] [.zsmartsystems.zigbee.zcl.retsulClcZ] - E2B0/1: Error reading client attribute 2 in cluster 25 - UNSUPPORTED_ATTRIBUTE
2021-10-09 20:48:54.228 [DEBUG] [scovery.ZigBeeNodePropertyDiscoverer] - B4E3F9FFFE0C5045: Could not get OTA firmware version from device
2021-10-09 20:48:54.228 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction complete: ZigBeeTransaction [ieeeAddress=B4E3F9FFFE0C5045 queueTime=220, state=COMPLETE, sendCnt=1, command=ReadAttributesCommand [Ota Upgrade: 0000/0 -> E2B0/1, cluster=0019, TID=3B, identifiers=[2]]]
2021-10-09 20:48:54.229 [DEBUG] [transaction.ZigBeeTransactionManager] - transactionListenerRemoved: 0 outstanding
2021-10-09 20:48:54.230 [DEBUG] [scovery.ZigBeeNodePropertyDiscoverer] - B4E3F9FFFE0C5045: ZigBee node property discovery complete: {zigbee_logicaltype=ROUTER, zigbee_powerlevel=FULL, zigbee_manufacturercode=0x1002, modelId=TS0601, zigbee_networkaddress=58032, zigbee_powersource=MAINS, zigbee_stkversion=0, zigbee_datecode=, zigbee_zclversion=3, vendor=_TZE200_xaabybja, zigbee_powermode=RECEIVER_ON_IDLE, zigbee_powersources=[MAINS], hardwareVersion=1, zigbee_applicationVersion=82, zigbee_device_initialised=true}
2021-10-09 20:48:54.231 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - B4E3F9FFFE0C5045: transactionComplete, state=COMPLETE, outstanding=0
2021-10-09 20:48:54.233 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction Manager: Send Next transaction. outstandingTransactions=0, outstandingQueues=0, sleepy=0/3
2021-10-09 20:48:54.236 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX EZSP: EzspMessageSentHandler [networkId=0, type=EMBER_OUTGOING_DIRECT, indexOrDestination=E2B0, apsFrame=EmberApsFrame [profileId=0104, clusterId=0019, sourceEndpoint=1, destinationEndpoint=1, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY, EMBER_APS_OPTION_ENABLE_ADDRESS_DISCOVERY, EMBER_APS_OPTION_RETRY], groupId=0, sequence=81], messageTag=3B, status=EMBER_SUCCESS, messageContents=]
2021-10-09 20:48:54.238 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX STA: msgTag=3B state=RX_ACK
2021-10-09 20:48:54.238 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B4E3F9FFFE0C5045: Checking endpoint 1 channels
2021-10-09 20:48:54.240 [DEBUG] [transaction.ZigBeeTransactionManager] - notifyTransactionProgress: TID=3B, state=RX_ACK, outstanding=0
2021-10-09 20:48:54.247 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B4E3F9FFFE0C5045: Dynamically created 0 channels
2021-10-09 20:48:54.250 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B4E3F9FFFE0C5045: Device initialization will be skipped as the device is already initialized
2021-10-09 20:48:54.253 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - B4E3F9FFFE0C5045: Channel initialisation complete
2021-10-09 20:48:54.255 [WARN ] [ng.zigbee.handler.ZigBeeThingHandler] - B4E3F9FFFE0C5045: No supported clusters found

chris · October 10, 2021, 6:50pm

This device uses a non-standard cluster. I have one here and will look to try and implement this in the next few weeks.

Richard_Laveau · October 28, 2021, 1:29pm

Hi,

I’m having exactly the same problem with a MOES ZigBee device (Wall switch ZTS-US).
Any progress?

New to openHab. Running fine on a PI 2 and openHabian.
I’m in the smart products selection phase.

X10 (CM11a) Binding is working with all my existing X10 devices.
Z-Wave Binding: One (1) Stelpro Smart KI thermostat. Working.
ZigBee Binding: first device does NOT work! Exactly as described by arp (this post).

First post. Hope I will be able to help someone at some point.

chris · October 28, 2021, 7:15pm

As above, the device has a non-standard cluster. I now have a Tuya hub (Arrived yesterday) so am looking at the commands sent to the blinds to decode this and will try and implement something in the next week or two.

The binding is generally designed to support Zigbee devices. Most of these cheap chinese devices are not Zigbee compliant and that is the case here. The device does not use the standard window blinds commands as defined by the standards - they use some other commands that are not documented anywhere. This means we need to reverse engineer how they work, and write special code to make them work.

If you stick to standard devices, then you are likely to be more successful - of course there may still be features not implemented, but it is normally a lot easier to implement things when I can simply read the documentation and implement the necessary functionality.

Richard_Laveau · October 29, 2021, 12:04pm

You are confirming my suspicion that this device could be a cheap knockoff with a poor implementation; on purpose or not.

Thanks.

arp · October 29, 2021, 3:55pm

It sucks that these companies aren’t building on the existing standard. I’m relatively new to OpenHAB and Zigbee, but am a Java developer - is there anything I can do to help this along, or anywhere you’d point me to start reading to be more helpful on these in the future?

chris · October 29, 2021, 6:22pm

This is only partly true. They are designed for a closed system - ie to work with their own hub, and within this scope I understand they work well. They aren’t designed to be sold and included into other systems, although plenty of people do that, and therefore they aren’t fully compliant with the standards.

These blinds devices aren’t exactly cheap though - although it’s relative as compliant zigbee blinds are even more expensive, but these Chinese ones still cost around USD80 I think - so not exactly “cheap”. They also aren’t really “knock offs” - they are generally reasonable quality, and designed to do a job, and work within a system, and they do that well. However try to use them outside of their native environment is the problem…

I agree - it’s a real pain, but I can also understand why.

Last year I went through the process of certifying a device and it cost a lot of money, and took a lot of time. We had a device working well in the field for a few months with a couple of thousand users, but to get it certified we had to add a load of functionality that the system will never use and put it through a week or so of testing at an expensive test facility. The system was a smart meter system and to get the security certificates to connect to the meters we needed the certification, but it’s expensive and for closed systems, it doesn’t necessarily add value.

It will take some time, but I’m working on it and it’s not something you can probably help with. I’ve just received the Tuya hub and have sniffed the communications with this device so now know how to control it. The problem is that the binding needs some reasonably heavy refactoring to support custom code - it was written with standards in mind so that it could support any standards compliant device without having to add definitions or code like was required at the time the ZWave binding was written.

I have now done a lot of this refactoring, and once complete it should make it easier to add non-standard devices - at least to cover the application layer. If they don’t adhere to the lower level standards which are handled by the coordinator then that’s much more difficult (ie probably impossible) to resolve.

PeteW · April 14, 2022, 7:04am

Hi @chris Just wondering how you are getting on with updateing the binding to support Zemismart blinds? I really like these blind motors, they are very well made imo and there are not many things are the market like them. Would be happy to do some testing if that is any help to you?

I’m currently on OH openHAB 3.2.0 Release Build but can head over to a dev build if that’s needed?

Thanks for all your efforts on the Zigbee binding!

Konstantin_Panchenko · November 15, 2022, 8:28am

Hi @chris Also wonder is there news of supporting this? I’m currently on 3.3 Release Build and have the same error for this device “_TZE200_hsgrhjpf”, also blinds motor. Can we do anything to help you integrate this in to binding?

Thanks,
K.

LORDUDE · September 6, 2023, 2:37am

Hi @chris i recently bought a ZigBee Garage Door Opener and i’m seeing similar error message:

HANDLER_INITIALIZING_ERROR
No supported clusters found

OpenHab → 4.0.2
OS → Ubuntu Server 22.04
Java → openjdk 17.0.8 2023-07-18 LTS
ZigBee/Zwave → GoControl CECOMINOD016164 HUSBZB-1 USB Hub

Is there a way to tell if this device is supported?

This is the device → XFTOPSE Tuya Smart Life ZigBee/WiFi Garage Door Opener Controller App Remote Control Supports Alexa Google Home Zigbee2MQTT Gateway Needed 1pcs (ZigBee American Standard Plug) - Amazon.com