It has only detected 2 devices connected to the driver.
They do not respond to any attribute reading, they only send messages when they are physically activated or deactivated or when they report their status.
Does it only happen to you with these devices?
The other zigbee devices work well for you?
@Mariano_Colmenarejo I have several other devices that are not currently connected.
But they also react exactly like that.
They respond and update the app just by physically pressing the switch. Every other click in the application shows a communication error.
They function from the application only in the first 3-5 minutes after pairing and immediately after that they stop responding to the application
All the other devices I have at home work as usual without problems.
(also 2 gang acts like this)
Well, take one of those that you have disconnected and pair it near the hub and leave it there, to see what it does.
I think you have a problem with your Maya Zigbee.
If when they are paired they work and then they stop working and if you have devices that you remove and put the network is destroyed and it has to be rebuilt
Hi Mariano
The driver only adds Zigbee device which has range extender and does not add wave plug. Please find groovy code at below link which might help in modifying the driver
Thank you in advance.
Hi @lalooprasad
From what I read in the link to the post that you send me, it is a zigbee plug and a zwave repeater, not a zigbe repeater and a zwave plug
If you already have the zigbee plug working:
My bad. It only pairs to zwave repeater. It doesn’t pair to Zigbee plug when I start the pairing.
Hi Mariano,
Could you please add CT-100 ZWave thermostat with following details pulled from IDE?
Thank you in advance.
Hi @lalooprasad
I haven’t searched much, but it seems to me that this device is on the stock Z-Wave Thermostat driver
- id: "0098/6401/0107"
deviceLabel: 2Gig CT100 Programmable Thermostat
manufacturerId: 0x0098
productType: 0x6401
productId: 0x0107
deviceProfileName: base-thermostat
- id: "0098/6501/000C"
deviceLabel: Iris Thermostat
manufacturerId: 0x0098
productType: 0x6501
productId: 0x000C
deviceProfileName: base-thermostat
- id: "0098/6501/000B"
deviceLabel: Iris Thermostat
manufacturerId: 0x0098
productType: 0x6501
productId: 0x000B
deviceProfileName: base-thermostat
Could you please add Zemismart Zigbee 3gang switch?
Blockquote
──────────────────────────────────────────────────────────────────────────────
──────────────────────────────────────────────────────────────────────────────
1 b18cdef6-1d11-4a7c-a0f4-7efa554ef45b Xiaomi/Aqara Switch and Button v1.8
2 540ae948-6fcc-4137-809c-875c3e186071 Zigbee Multi Switch and Child Mc
3 f2e891c6-00cc-446c-9192-8ebda63d9898 Zigbee Switch
──────────────────────────────────────────────────────────────────────────────
? Select a driver. 3
2022-12-02T01:45:52.574877909+00:00 DEBUG Zigbee Switch driver device thread event handled
2022-12-02T01:46:22.574837257+00:00 DEBUG Zigbee Switch driver device thread event handled
2022-12-02T01:46:52.576976605+00:00 DEBUG Zigbee Switch driver device thread event handled
2022-12-02T01:47:22.585031285+00:00 DEBUG Zigbee Switch driver device thread event handled
2022-12-02T01:47:49.945159835+00:00 TRACE Zigbee Switch Received event with handler zigbee
2022-12-02T01:47:49.954849835+00:00 INFO Zigbee Switch <ZigbeeDevice: 40abb638-c758-4526-b486-f1fdefaf03f7 [0xEC40] (Canopy Lights)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xEC40, src_endpoint: 0x03, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -56, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x22, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-12-02T01:47:50.030159168+00:00 TRACE Zigbee Switch Found ZigbeeMessageDispatcher handler in zigbee_switch
2022-12-02T01:47:50.044836168+00:00 INFO Zigbee Switch Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-12-02T01:47:50.051892168+00:00 INFO Zigbee Switch <ZigbeeDevice: 40abb638-c758-4526-b486-f1fdefaf03f7 [0xEC40] (Canopy Lights)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-12-02T01:47:50.074754835+00:00 DEBUG Zigbee Switch Canopy Lights device thread event handled
2022-12-02T01:47:52.581607168+00:00 DEBUG Zigbee Switch driver device thread event handled
2022-12-02T01:48:22.582643505+00:00 DEBUG Zigbee Switch driver device thread event handled
2022-12-02T01:48:52.593062842+00:00 DEBUG Zigbee Switch driver device thread event handled
2022-12-02T01:49:22.592525512+00:00 DEBUG Zigbee Switch driver device thread event handled
2022-12-02T01:49:52.592492849+00:00 DEBUG Zigbee Switch driver device thread event handled
2022-12-02T01:49:54.800904183+00:00 TRACE Zigbee Switch Received event with handler zigbee
2022-12-02T01:49:54.809783850+00:00 INFO Zigbee Switch <ZigbeeDevice: 40abb638-c758-4526-b486-f1fdefaf03f7 [0xEC40] (Canopy Lights)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xEC40, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD6, rssi: -56, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x24, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-12-02T01:49:54.834388183+00:00 TRACE Zigbee Switch Found ZigbeeMessageDispatcher handler in zigbee_switch
2022-12-02T01:49:54.839870850+00:00 INFO Zigbee Switch Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-12-02T01:49:54.846427183+00:00 INFO Zigbee Switch <ZigbeeDevice: 40abb638-c758-4526-b486-f1fdefaf03f7 [0xEC40] (Canopy Lights)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-12-02T01:49:54.883358516+00:00 DEBUG Zigbee Switch Canopy Lights device thread event handled
2022-12-02T01:50:22.597456186+00:00 DEBUG Zigbee Switch driver device thread event handled
2022-12-02T01:50:25.276552520+00:00 TRACE Zigbee Switch Received event with handler device_lifecycle
2022-12-02T01:50:25.294605853+00:00 TRACE Zigbee Switch Zigbee Device: 1864912e-b24e-4dfe-89d1-6185605587d9
Manufacturer: _TZ3000_snq47izk Model: TS0013
[1]: Basic, Identify, Groups, Scenes, OnOff, 0xE000, 0xE001 [2]: Identify, Groups, Scenes, OnOff, 0xE000, 0xE001 [3]: Identify, Groups, Scenes, OnOff, 0xE000, 0xE001 [242]:
2022-12-02T01:50:25.327541520+00:00 INFO Zigbee Switch <ZigbeeDevice: 1864912e-b24e-4dfe-89d1-6185605587d9 [0x456B] (Zigbee Switch)> received lifecycle event: added
2022-12-02T01:50:25.341653853+00:00 TRACE Zigbee Switch Received event with handler device_lifecycle
2022-12-02T01:50:25.347116853+00:00 INFO Zigbee Switch <ZigbeeDevice: 1864912e-b24e-4dfe-89d1-6185605587d9 [0x456B] (Zigbee Switch)> received lifecycle event: doConfigure
2022-12-02T01:50:25.358058186+00:00 TRACE Zigbee Switch <ZigbeeDevice: 1864912e-b24e-4dfe-89d1-6185605587d9 [0x456B] (Zigbee Switch)> received unhandled lifecycle event: added
2022-12-02T01:50:25.363204520+00:00 DEBUG Zigbee Switch Zigbee Switch device thread event handled
2022-12-02T01:50:25.377113853+00:00 TRACE Zigbee Switch Found DeviceLifecycleDispatcher handler in zigbee_switch
2022-12-02T01:50:25.382792853+00:00 DEBUG Zigbee Switch Zigbee Switch device thread event handled
2022-12-02T01:50:25.397864853+00:00 TRACE Zigbee Switch Found DeviceLifecycleDispatcher handler in zigbee_switch
2022-12-02T01:50:25.404862520+00:00 INFO Zigbee Switch <ZigbeeDevice: 1864912e-b24e-4dfe-89d1-6185605587d9 [0x456B] (Zigbee Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x456B, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-02T01:50:25.438549520+00:00 INFO Zigbee Switch <ZigbeeDevice: 1864912e-b24e-4dfe-89d1-6185605587d9 [0x456B] (Zigbee Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x456B, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-02T01:50:25.481416187+00:00 INFO Zigbee Switch <ZigbeeDevice: 1864912e-b24e-4dfe-89d1-6185605587d9 [0x456B] (Zigbee Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x456B, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-02T01:50:25.520990520+00:00 INFO Zigbee Switch <ZigbeeDevice: 1864912e-b24e-4dfe-89d1-6185605587d9 [0x456B] (Zigbee Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x456B, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: E0798DFFFEDE210B, src_endpoint: 0x01, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D970002048BB2, dest_endpoint: 0x01 > > >
2022-12-02T01:50:25.542439187+00:00 INFO Zigbee Switch <ZigbeeDevice: 1864912e-b24e-4dfe-89d1-6185605587d9 [0x456B] (Zigbee Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x456B, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-12-02T01:50:25.573126187+00:00 INFO Zigbee Switch <ZigbeeDevice: 1864912e-b24e-4dfe-89d1-6185605587d9 [0x456B] (Zigbee Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x456B, dest_endpoint: 0x02, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: E0798DFFFEDE210B, src_endpoint: 0x02, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D970002048BB2, dest_endpoint: 0x01 > > >
2022-12-02T01:50:25.586895187+00:00 INFO Zigbee Switch <ZigbeeDevice: 1864912e-b24e-4dfe-89d1-6185605587d9 [0x456B] (Zigbee Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x456B, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-12-02T01:50:25.611873187+00:00 INFO Zigbee Switch <ZigbeeDevice: 1864912e-b24e-4dfe-89d1-6185605587d9 [0x456B] (Zigbee Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x456B, dest_endpoint: 0x03, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: E0798DFFFEDE210B, src_endpoint: 0x03, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D970002048BB2, dest_endpoint: 0x01 > > >
2022-12-02T01:50:25.640869853+00:00 INFO Zigbee Switch <ZigbeeDevice: 1864912e-b24e-4dfe-89d1-6185605587d9 [0x456B] (Zigbee Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x456B, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-12-02T01:50:25.652500520+00:00 DEBUG Zigbee Switch Zigbee Switch device thread event handled
Blockquote
Is it possible to include signal metrics also in
Zigbee Range Extender Mc driver ?
Seems straight forward for me… Works fine and display in Zigbee Thing Mc driver
Sorry, until Monday or Tuesday I will not be able to modify or add anything
Hello. Is it possible to update the drivers for the following?
Manufacturer: _TZ3000_Itt60asa
Model: TS0004
App Version: 0x20 ZCL Version: 0x03
Network ID: 0x8A46
Zigbee EUI: A4C138A736258B8B
Device ID: 689f0299-d977-4c80-9e05- d63dad68bb8f
Server Cluster:
Ep: 04={0004,0005,0006}
Ep: 02 (0004,0005,0006}
Ep: 03={0004,0005,0006}
Ep: 01={ 0003,0004,0005,0006,0702,0B04,E00C E001,0000}
Client Clusters:
Ep: 01={0019,000A }
Ep: F2={0021}
It is recognized as TS0004 but fails to get any information and goes offline after a few minutes.
Thank you very much.
Yiannis
Hi @Mariano_Colmenarejo, just received a new flush mount dimmer module and it has the following details.
It does connect using your “Zigbee Light Multifunctional” Edge driver but it is not responding as expected. Help would be great.
Details from the thing MC driver are:
Any suggestions?
Thanks,
Erwin
hi friend, could you add finger for this contact sensor & ikea bulb?
manufacturer: TUYATEC-rkqiqvcs
model: RH3001
Raw description : 01 0104 0402 00 04 0000 0001 0003 0500 01 0003
manufacturer: IKEA of Sweden
model: TRADFRI bulb E26 WS clear 950lm
Raw description : 01 C05E 0220 02 09 0000 0003 0004 0005 0006 0008 0300 0B05 1000 04 0005 0019 0020 1000
I have a a tuya ZigBee mmwave presence sensor I’d like to get working. Let me know if any other info is needed to get driver’s for it. Thanks!
@X0mbie
I don’t have any driver for this device.
Use the EF00 cluster, I don’t know how to handle it
Hopefully someone else will figure it out. I do appreciate you responding and all that you’ve done for the community. Thank you.
I need the fingerprint device model too
until Monday or Tuesday I will not be able to modify or add anything
