I also looking for a similar device, Is it that device?
Yes, you are right, this is exact that device.
1 Like
dev:4472020-10-24 14:33:11.152 infoCOPY AND PASTE THIS ROW TO THE DEVELOPER: fingerprint model:"FNB56-ZSW03LX2.0", manufacturer:"FeiBit", profileId:"C05E", endpointId:"01", inClusters:"0000,0004,0003,0006,0005,1000,0008", outClusters:"0019", application:"
I'm having problems with this device. It is a switch with 3 physical buttons.
He's not pairing properly.
It’s losing the connection all the time, although on the hub it shows the device, the device keeps flashing as if it hadn't paired yet.
Every time I put it on to discovery a new device, it appears even though it's already on the network, and none of them does stabilize the connection.
Important Update
A new version (v1.0.0.1025) of all my Generic Zigbee drivers have been released.
This update is important to move over to since it contains patches for platform-related issues that may affect some users without them knowing. It also contains minor patches for reported issues.
To keep up to date with new releases, sign up here.
6 Likes
Hi Markus
Just to be sure..:
Do you have to do anything after you update the driver..?
Initialize, Refresh ect..?
Or do you simply update the code, and sit back and enjoy the new driver..? 
Unless it's a wall switch device no need to do anything, but good you mentioned it. For wall switch devices I'd recommend Initialize. Just sit back and enjoy the new drivers 
4 Likes
Thanks.. Enjoying your new drivers already.. 
BTW - i found a "PLEASE REPORT TO DEV" line in the log for a LLKZMK11LM dual relay using your "Zigbee - Generic Switch (with Presence)" driver ver. 1.0.0.1025:
dev:1132020-10-25 11:32:17.064 infoUnhandled Event IGNORE THIS - description:read attr - raw: 09530100009001FF4244032828052118000727000000000000000008212312092104186410006510006E20006F200094200395399A99E93D9639C3CB12459739F029243C983920F1B13D9B210000, dni: 0953, endpoint: 01, cluster: 0000, size: 90, attrId: FF01, encoding: 42, command: 0A, value: 44032828052118000727000000000000000008212312092104186410006510006E20006F200094200395399A99E93D9639C3CB12459739F029243C983920F1B13D9B210000 | msgMap:[raw:09530100009001FF4244032828052118000727000000000000000008212312092104186410006510006E20006F200094200395399A99E93D9639C3CB12459739F029243C983920F1B13D9B210000, dni:0953, endpoint:01, cluster:0000, size:90, attrId:FF01, encoding:41, command:0A, value:[raw:[deviceTemperature:28, RSSI_dB:0018, unknown2:0000000000000000, unknown3:1223, unknown4:1804, openClose:00, switch2:00, unknown10:00, unknown11:00, unknown9420:03, consumption:3C2429F0, voltage:4512CBC3, power:3DB1F120, unknown9:0000], deviceTemperature:40, RSSI_dB:24, unknown2:0, unknown3:4643, unknown4:6148, openClose:false, switch2:false, unknown10:0, unknown11:0, unknown9420:3, consumption:0.010019764, voltage:2348.735, power:0.08688569, unknown9:0], clusterInt:0, attrInt:65281]
dev:1132020-10-25 11:32:17.046 warnPLEASE REPORT TO DEV - The Xiaomi Struct used an unrecognized tag: 0x94 (type: 0x20) (struct: 44032828052118000727000000000000000008212312092104186410006510006E20006F200094200395399A99E93D9639C3CB12459739F029243C983920F1B13D9B210000)
dev:1132020-10-25 11:31:51.029 infoUnhandled Event IGNORE THIS - description:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000 | msgMap:[raw:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000, profileId:0104, clusterId:000A, clusterInt:10, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0953, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00]]
dev:1132020-10-25 11:31:09.039 infoUnhandled Event IGNORE THIS - description:read attr - raw: 095301000C0E55003960E8363E, dni: 0953, endpoint: 01, cluster: 000C, size: 0E, attrId: 0055, encoding: 39, command: 0A, value: 60E8363E | msgMap:[raw:095301000C0E55003960E8363E, dni:0953, endpoint:01, cluster:000C, size:0E, attrId:0055, encoding:39, command:0A, value:3E36E860, clusterInt:12, attrInt:85, valueParsed:0.17862082]
dev:1132020-10-25 11:31:07.335 infoOn/Off Button press - description:read attr - raw: 09530100060800001000, dni: 0953, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00 | parseMap:[raw:09530100060800001000, dni:0953, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0, valueParsed:false]
dev:1132020-10-25 11:31:07.194 infoOn/Off Button press - description:read attr - raw: 0953020006160000100000F0233E000007, dni: 0953, endpoint: 02, cluster: 0006, size: 16, attrId: 0000, encoding: 10, command: 0A, value: 0000F0233E000007 | parseMap:[raw:0953020006160000100000F0233E000007, dni:0953, endpoint:02, cluster:0006, size:16, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0, additionalAttrs:[[value:0700003E, encoding:23, attrId:F000, consumedBytes:7, attrInt:61440]], valueParsed:false]
dev:1132020-10-25 11:31:07.175 infoON/OFF CATCHALL CLUSTER EVENT - description:catchall: 0104 0006 02 01 0040 00 0953 00 00 0000 0B 01 0000 | parseMap:[raw:catchall: 0104 0006 02 01 0040 00 0953 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:0953, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]
Hope it is useful..
Congratulations, I already did the update. I would like to thank you for all your efforts in helping the community.
Then please see if you can take a look at that Gledopto controller.
I would like to ask a question, is it possible to add in the driver some function to save the last state of the device? in case there is a power failure and when it comes back the device establishes the last saved state
FYI
Did Marcus ever get back to you on a zigbee driver for this?
Nothing, haven't had a chance to try anything other than load all the drivers I could find for sirens, temps, humidity etc. etc.
Hopefully something comes up on the other thread.
Any luck already with connecting the MOES Thermostat?
Still no luck. I have ordered tuya hub to upgrade firmware there. Gonna try again after that.
1 Like
The missing device, a working EU zigbee thermostat that works on Hubitat where the repeater function is working well for Xiaomi & Aqara devices...
I need 6 of them...
Hello I have bought a tuya trv, I put driver
Tuya Zigbee Valve (works with Tuya Zigbee Valves and probably any other Zigbee Valve devices using standard clusters)
But didn't work.
Didn't open.. Close... Can't do anything.
I have this device.
€ 24,51 34%OFF | Termostato termostático programable para radiador, controlador de temperatura compatible con Alexa, Tuya Smart ZigBee
1 Like
I received and installed tuya hub, that moes thermostats work well with tuya hub, but still can't be controlled from hubitat. I have tried every thermostat driver in HE, no reaction to on/off buttons and no info about currently temperature.
But at the same time it works fine as a router. Several devices as aqara motion sensors or ikea bulbs connected through this thermostat.
I'm talking about this device: https://a.aliexpress.com/_mLlYpyZ
1 Like
Have you tried zen thermostat driver?
Or this
For me it would be ideal, 6 thermostats connected to my Hubitat that work as repeaters for my Aqara sensors in the house.
It is a pity that Hubitat does not support such devices because it is not 100% zigbee while other hubs or drivers do work. There are many popular devices (Ikea, Aqara, Moes ...) that do not work on Hubitat, I am very happy with my Hub, but if there is ever an alternative that can offer this ....
