Thank you for the feedback, I have fixed the typo, and the outClusters are now corrected in the dev branch (timestamp 2022/06/06 9:47 AM ). '000A' is Zigbee time cluster, but omitting it in the fingerprint does not have any effects in my opinion.
It seems like you have some strange one-direction only communication.. The Zemismart switch accepts the commands, but the reporting back to HE hub is lost somewhere.. If you check http://192.168.0.66/hub/zigbee/getChildAndRouteInfo (replace the IP address with your local IP), do you see the switch in the 'Route Table Entry' communicating to HE via another repeating device?
When you have the chance, you may try switching off the HE hub for a couple of minutes and then powering it back again - this worked in @ADDs case.
Do you see any debug logs? What I am looking for is logs that contain "Parsed: [raw: ......." like this:
Debug Logs
dev:24792022-06-07 07:32:14.535 debugTS0011 _TZ3000_txpirhfq Parent switch on
dev:24792022-06-07 07:32:14.531 debugTS0011 _TZ3000_txpirhfq Parsed: [raw:739D0100060800001001, dni:739D, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0]
dev:24792022-06-07 07:31:53.149 debugTS0011 _TZ3000_txpirhfq Parent switch off
dev:24792022-06-07 07:31:53.140 debugTS0011 _TZ3000_txpirhfq Parsed: [raw:739D0100060800001000, dni:739D, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]
