(EDGE Driver-Mc): Zigbee Drivers for Motion, Open/Close, Moisture, Smoke-Co Sensors and others Devices

I understand!!

Now that you have the CLI working try doing this:

  • I have compiled and published a new version, it has no changes, but you are going to install it with the CLI so that all the devices are reconfigured.
  • Prepare a window with the CLI to capture the driver installation log
  • Open another window with the CLI to install the new version
  • In this window, Type smartthings edge:drivers:install and press enter
  • Follow the steps to choose the number corresponding to the Hub, then to the channel where the driver is installed and finally the driver you want to install.
  • Open the log window and after about 10 seconds or more you will see the installation and configuration process of all the devices with the driver.
  • Capture the log of at least 30 sec and send it to me in case I can see any errors
  • I don’t know if this will make them work again or not.
───────────────────────────────────────────────────
 Name         Zigbee Multi Switch and Child Mc
 Version      2022-11-26T16:55:20.155189529
───────────────────────────────────────────────────

tank you for your help!!
try to do it still didnt work.
also turn off wifi and open the electrical box still noting ):
thts the log

? Select a driver. 24
connecting… connected
2022-11-26T17:25:54.881369693+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler driver_lifecycle
2022-11-26T17:26:06.056694361+00:00 TRACE Zigbee Multi Switch and Child Mc Setup driver Zigbee_Multi_Switch with lifecycle handlers:
DeviceLifecycleDispatcher: Zigbee_Multi_Switch
default_handlers:
removed:
infoChanged:
driverSwitched:
init:
doConfigure:
added:
child_dispatchers:

2022-11-26T17:26:06.104748361+00:00 TRACE Zigbee Multi Switch and Child Mc Setup driver Zigbee_Multi_Switch with Capability handlers:
CapabilityCommandDispatcher: Zigbee_Multi_Switch
default_handlers:
refresh:
refresh
energyMeter:
resetEnergyMeter
switchLevel:
setLevel
switch:
off
on
legendabsolute60149.switchAllOnOff1:
setSwitchAllOnOff
child_dispatchers:

2022-11-26T17:26:06.112957028+00:00 TRACE Zigbee Multi Switch and Child Mc Setup driver Zigbee_Multi_Switch with Zigbee handlers:
ZigbeeMessageDispatcher: Zigbee_Multi_Switch
default_handlers:
attr:
ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ACPowerMultiplier
ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ACPowerDivisor
ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ActivePower
ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: InstantaneousDemand
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: Multiplier
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: Divisor
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: CurrentSummationDelivered
ZclClusterAttributeValueHandler: cluster: Level, attribute: CurrentLevel
global:
ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
cluster:
zdo:
child_dispatchers:

2022-11-26T17:26:06.201382361+00:00 TRACE Zigbee Multi Switch and Child Mc Zigbee Device: f70a5200-5516-40bc-ab5a-39ed5c6bc8a6
Manufacturer: _TYZB01_gzhgaaqi Model: TS0003
[1]: Basic, Groups, Identify, OnOff, Scenes, TouchlinkCommissioning, Level [2]: Basic, Groups, Identify, OnOff, Scenes, TouchlinkCommissioning, Level [3]: Basic, Groups, Identify, OnOff, Scenes, TouchlinkCommissioning, Level
2022-11-26T17:26:06.238418361+00:00 TRACE Zigbee Multi Switch and Child Mc Zigbee Device: fe92f059-db6f-427a-8ff8-c8de85bb1f1e
Manufacturer: _TYZB01_gzhgaaqi Model: TS0003
[1]: Basic, Groups, Identify, OnOff, Scenes, TouchlinkCommissioning, Level [2]: Basic, Groups, Identify, OnOff, Scenes, TouchlinkCommissioning, Level [3]: Basic, Groups, Identify, OnOff, Scenes, TouchlinkCommissioning, Level
2022-11-26T17:26:06.246342028+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler _resync
2022-11-26T17:26:06.252200028+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler environment_info
2022-11-26T17:26:06.302651361+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-11-26T17:26:06.307849361+00:00 PRINT Zigbee Multi Switch and Child Mc device_network_id >>> 86F6
2022-11-26T17:26:06.313291028+00:00 PRINT Zigbee Multi Switch and Child Mc label >>> TS0003 Switch
2022-11-26T17:26:06.319000361+00:00 PRINT Zigbee Multi Switch and Child Mc parent_device_id >>> 4d626778-721c-4f13-a27d-1f908e8880bf
2022-11-26T17:26:06.324321028+00:00 PRINT Zigbee Multi Switch and Child Mc manufacturer >>>
2022-11-26T17:26:06.329341361+00:00 PRINT Zigbee Multi Switch and Child Mc model >>>
2022-11-26T17:26:06.335151361+00:00 PRINT Zigbee Multi Switch and Child Mc vendor_provided_label >>>
2022-11-26T17:26:06.340807361+00:00 PRINT Zigbee Multi Switch and Child Mc Parent_devices[f70a5200-5516-40bc-ab5a-39ed5c6bc8a6]>>>>>> <ZigbeeDevice: f70a5200-5516-40bc-ab5a-39ed5c6bc8a6 [0x86F6] (TS0003 Switch)>
2022-11-26T17:26:06.346056028+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> changeProfileThreeSw Preference value: Single
2022-11-26T17:26:06.358967361+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> version Preference value:
2022-11-26T17:26:06.366279028+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch2Child Preference value: No
2022-11-26T17:26:06.371454361+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> signalMetricsVisibles Preference value: No
2022-11-26T17:26:06.377504028+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch1Child Preference value: No
2022-11-26T17:26:06.382804028+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch3Child Preference value: No
2022-11-26T17:26:06.387924695+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> restoreState Preference value: 255
2022-11-26T17:26:06.393232695+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Read Basic clusters attributes >>>
2022-11-26T17:26:06.400215361+00:00 PRINT Zigbee Multi Switch and Child Mc <<<< attr_id >>>> {4, 0, 1, 5, 7, 65534}
2022-11-26T17:26:06.419425361+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: f70a5200-5516-40bc-ab5a-39ed5c6bc8a6 [0x86F6] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x86F6, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0004, AttributeId: 0x0000, AttributeId: 0x0001, AttributeId: 0x0005, AttributeId: 0x0007, AttributeId: 0xFFFE > > >
2022-11-26T17:26:06.447926695+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T17:26:06.454568695+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-11-26T17:26:06.460096028+00:00 PRINT Zigbee Multi Switch and Child Mc device_network_id >>> 6F80
2022-11-26T17:26:06.465896028+00:00 PRINT Zigbee Multi Switch and Child Mc label >>> TS0003 Switch
2022-11-26T17:26:06.471251695+00:00 PRINT Zigbee Multi Switch and Child Mc parent_device_id >>> 4d626778-721c-4f13-a27d-1f908e8880bf
2022-11-26T17:26:06.483652028+00:00 PRINT Zigbee Multi Switch and Child Mc manufacturer >>>
2022-11-26T17:26:06.491771028+00:00 PRINT Zigbee Multi Switch and Child Mc model >>>
2022-11-26T17:26:06.497103361+00:00 PRINT Zigbee Multi Switch and Child Mc vendor_provided_label >>>
2022-11-26T17:26:06.502575361+00:00 PRINT Zigbee Multi Switch and Child Mc Parent_devices[fe92f059-db6f-427a-8ff8-c8de85bb1f1e]>>>>>> <ZigbeeDevice: fe92f059-db6f-427a-8ff8-c8de85bb1f1e [0x6F80] (TS0003 Switch)>
2022-11-26T17:26:06.508637361+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> changeProfileThreeSw Preference value: Single
2022-11-26T17:26:06.521370695+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> version Preference value:
2022-11-26T17:26:06.528710361+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch2Child Preference value: No
2022-11-26T17:26:06.543109028+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> signalMetricsVisibles Preference value: No
2022-11-26T17:26:06.550262028+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch1Child Preference value: No
2022-11-26T17:26:06.556779028+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch3Child Preference value: No
2022-11-26T17:26:06.562344028+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> restoreState Preference value: 255
2022-11-26T17:26:06.567559695+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Read Basic clusters attributes >>>
2022-11-26T17:26:06.573012028+00:00 PRINT Zigbee Multi Switch and Child Mc <<<< attr_id >>>> {4, 0, 1, 5, 7, 65534}
2022-11-26T17:26:06.580355362+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fe92f059-db6f-427a-8ff8-c8de85bb1f1e [0x6F80] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6F80, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0004, AttributeId: 0x0000, AttributeId: 0x0001, AttributeId: 0x0005, AttributeId: 0x0007, AttributeId: 0xFFFE > > >
2022-11-26T17:26:06.625009695+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T17:26:06.630760028+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler environment_info
2022-11-26T17:26:06.643808695+00:00 DEBUG Zigbee Multi Switch and Child Mc Z-Wave hub node ID environment changed.
2022-11-26T17:26:35.812603698+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-11-26T17:26:35.913883365+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: f70a5200-5516-40bc-ab5a-39ed5c6bc8a6 [0x86F6] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x86F6, src_endpoint: 0x03, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -59, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x0A, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-11-26T17:26:35.971193032+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-11-26T17:26:35.985018032+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-11-26T17:26:35.991172698+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-11-26T17:26:36.001219032+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: f70a5200-5516-40bc-ab5a-39ed5c6bc8a6 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2022/11/26 Time: 17:26
DNI: 0x86F6 LQI: 136 RSSI: -59dbm
”},“visibility”:{“displayed”:false}}
2022-11-26T17:26:36.043962365+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 3 value = false
2022-11-26T17:26:36.052017032+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: f70a5200-5516-40bc-ab5a-39ed5c6bc8a6 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch3”,“state”:{“value”:“off”}}
2022-11-26T17:26:36.089436365+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T17:26:36.095233032+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-11-26T17:26:36.105461365+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: f70a5200-5516-40bc-ab5a-39ed5c6bc8a6 [0x86F6] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x86F6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x90, rssi: -57, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x09, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-11-26T17:26:36.144827365+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T17:26:36.152654698+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-11-26T17:26:36.157880365+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-11-26T17:26:36.163909365+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-11-26T17:26:36.170939698+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: f70a5200-5516-40bc-ab5a-39ed5c6bc8a6 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2022/11/26 Time: 17:26
DNI: 0x86F6 LQI: 144 RSSI: -57dbm
”},“visibility”:{“displayed”:false}}
2022-11-26T17:26:36.189426698+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 2 value = false
2022-11-26T17:26:36.197515032+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: f70a5200-5516-40bc-ab5a-39ed5c6bc8a6 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-11-26T17:26:36.224561698+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T17:26:36.235460032+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T17:26:38.097557699+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-11-26T17:26:38.104380699+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: f70a5200-5516-40bc-ab5a-39ed5c6bc8a6 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:"S1:On "}}
2022-11-26T17:26:38.123732365+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T17:26:38.246734032+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-11-26T17:26:38.293522365+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: f70a5200-5516-40bc-ab5a-39ed5c6bc8a6 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:"S1:On "}}
2022-11-26T17:26:38.391005699+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled

@raz6498635

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

21 posts were split to a new topic: [Edge drivers] Issue opening the device’s Detail View

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:

  • Install Zwave Thing Mc
  • Put the zwave repeater in pairing mode as the post you sent says and in the app add a device with search nearby.
  • This should be enough for it to pair with the Z-wave Thing Mc and work

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
1 Like

Hi @Mariano_Colmenarejo

Could you please add Zemismart Zigbee 3gang switch?

Blockquote

──────────────────────────────────────────────────────────────────────────────

Driver Id Name

──────────────────────────────────────────────────────────────────────────────
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

Do we know if yagusmart 3 gang wall switch working?

Or can we add it?

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