Try this version, assign the endpoint 2 to “main” component for this device
I think this device has device.fingerprinted_endpoint_id = 0x01 then default handlers assign endpoint 1 to “main” component
Please, could you send me the log of new driver version installation
───────────────────────────────────────────────────
Name Zigbee Switch Mc
Version 2022-11-21T23:11:29.726700394
───────────────────────────────────────────────────
Thanks for making the change so quickly.
Here is the complete log for paring the device with the updated driver. I noticed there is an error at the end. After pairing the switch seem to be operational, but the log also show the same error. See second part of log. Also, when i open the device card on smartthings app. I get the error “Couldn’t get device status”
Thanks
------ Device pairing log —
2022-11-21T23:31:05.420019885+00:00 WARN Zigbee Switch Mc Unexpected filesystem lookup for capability legendabsolute60149.driverVersion1
2022-11-21T23:31:05.450329135+00:00 TRACE Zigbee Switch Mc Setup driver Zigbee_Switch with lifecycle handlers:
DeviceLifecycleDispatcher: Zigbee_Switch
default_handlers:
init:
removed:
doConfigure:
infoChanged:
driverSwitched:
child_dispatchers:
2022-11-21T23:31:05.454395344+00:00 TRACE Zigbee Switch Mc Setup driver Zigbee_Switch with Capability handlers:
CapabilityCommandDispatcher: Zigbee_Switch
default_handlers:
legendabsolute60149.energyReset1:
setEnergyReset
switch:
off
on
legendabsolute60149.randomOnOff2:
setRandomOnOff
legendabsolute60149.getGroups:
setGetGroups
energyMeter:
resetEnergyMeter
refresh:
refresh
child_dispatchers:
2022-11-21T23:31:05.458329219+00:00 TRACE Zigbee Switch Mc Setup driver Zigbee_Switch with Zigbee handlers:
ZigbeeMessageDispatcher: Zigbee_Switch
default_handlers:
attr:
ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
global:
ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
cluster:
ZclClusterCommandHandler: cluster: Groups, command: GetGroupMembership
zdo:
child_dispatchers:
2022-11-21T23:31:05.480494927+00:00 TRACE Zigbee Switch Mc Zigbee Device: c9ddf88d-d9f0-4683-9377-fcf086c512f4
Manufacturer: Quirky Model: Smart Switch
[1]: Basic, Identify, 0xFC20 [2]: Basic, Identify, OnOff, Scenes, Groups
2022-11-21T23:31:05.484992344+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
2022-11-21T23:31:05.517897219+00:00 TRACE Zigbee Switch Mc Received event with handler _resync
2022-11-21T23:31:05.521054677+00:00 TRACE Zigbee Switch Mc Received event with handler environment_info
2022-11-21T23:31:05.528554635+00:00 TRACE Zigbee Switch Mc Found DeviceLifecycleDispatcher handler in Zigbee_Switch
2022-11-21T23:31:05.532230927+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> emitting event: {“attribute_id”:“randomOnOff”,“capability_id”:“legendabsolute60149.randomOnOff2”,“component_id”:“main”,“state”:{“value”:“Inactive”}}
2022-11-21T23:31:05.543638760+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> emitting event: {“attribute_id”:“randomNext”,“capability_id”:“legendabsolute60149.randomNextStep2”,“component_id”:“main”,“state”:{“value”:“Inactive”}}
2022-11-21T23:31:05.559181719+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> emitting event: {“attribute_id”:“energyReset”,“capability_id”:“legendabsolute60149.energyReset1”,“component_id”:“main”,“state”:{“value”:“Last: 0.000 kWh (11/21/2022)”}}
2022-11-21T23:31:05.569857094+00:00 DEBUG Zigbee Switch Mc Smart Switch device thread event handled
2022-11-21T23:31:05.573310427+00:00 TRACE Zigbee Switch Mc Received event with handler environment_info
2022-11-21T23:31:05.576860594+00:00 DEBUG Zigbee Switch Mc Z-Wave hub node ID environment changed.
2022-11-21T23:31:05.584749844+00:00 TRACE Zigbee Switch Mc Received event with handler device_lifecycle
2022-11-21T23:31:05.588147469+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received lifecycle event: added
2022-11-21T23:31:05.592697135+00:00 TRACE Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received unhandled lifecycle event: added
2022-11-21T23:31:05.595890635+00:00 DEBUG Zigbee Switch Mc Smart Switch device thread event handled
2022-11-21T23:31:05.599388427+00:00 TRACE Zigbee Switch Mc Received event with handler device_lifecycle
2022-11-21T23:31:05.602898052+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received lifecycle event: doConfigure
2022-11-21T23:31:05.608313969+00:00 TRACE Zigbee Switch Mc Found DeviceLifecycleDispatcher handler in Zigbee_Switch
2022-11-21T23:31:05.614523677+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xC40B, dest_endpoint: 0x02, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 7C25E4000010A97E, src_endpoint: 0x02, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 24FD5B0000032AF9, dest_endpoint: 0x01 > > >
2022-11-21T23:31:05.625060594+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xC40B, 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-11-21T23:31:05.640570469+00:00 DEBUG Zigbee Switch Mc Smart Switch device thread event handled
2022-11-21T23:31:05.649745260+00:00 DEBUG Zigbee Switch Mc Smart Switch device thread event handled
2022-11-21T23:31:05.790251927+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-11-21T23:31:05.795989219+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC40B, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xFF, rssi: -56, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x7B >, < BindRequestResponse || status: 0x00 > > >
2022-11-21T23:31:05.805000469+00:00 DEBUG Zigbee Switch Mc Smart Switch device thread event handled
2022-11-21T23:31:05.967424677+00:00 TRACE Zigbee Switch Mc Received event with handler device_lifecycle
2022-11-21T23:31:05.975079344+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received lifecycle event: infoChanged
2022-11-21T23:31:05.980411094+00:00 TRACE Zigbee Switch Mc Found DeviceLifecycleDispatcher handler in Zigbee_Switch
2022-11-21T23:31:05.985120094+00:00 PRINT Zigbee Switch Mc << do_Prefrences >>
2022-11-21T23:31:05.988575094+00:00 PRINT Zigbee Switch Mc << Preference changed name: signalMetricsVisibles old value: nil new value: No
2022-11-21T23:31:06.017580927+00:00 PRINT Zigbee Switch Mc << Preference changed name: changeProfile old value: nil new value: Switch
2022-11-21T23:31:06.024992052+00:00 PRINT Zigbee Switch Mc << Preference changed name: randomMin old value: nil new value: 1.0
2022-11-21T23:31:06.028350677+00:00 PRINT Zigbee Switch Mc << Preference changed name: logDebugPrint old value: nil new value: false
2022-11-21T23:31:06.031868594+00:00 PRINT Zigbee Switch Mc << Preference changed name: groupAdd old value: nil new value: 0.0
2022-11-21T23:31:06.036160344+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xC40B, dest_endpoint: 0x02, profile: 0x0104, cluster: Groups >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x02 >, < GetGroupMembership || group_list_length: 0x00 > > >
2022-11-21T23:31:06.050963177+00:00 PRINT Zigbee Switch Mc << Preference changed name: powerTimer old value: nil new value: 5.0
2022-11-21T23:31:06.054172760+00:00 PRINT Zigbee Switch Mc << Preference changed name: version old value: nil new value:
2022-11-21T23:31:06.059288802+00:00 PRINT Zigbee Switch Mc << Preference changed name: localTimeOffset old value: nil new value: 0
2022-11-21T23:31:06.065340635+00:00 PRINT Zigbee Switch Mc << Preference changed name: loadPower old value: nil new value: 0
2022-11-21T23:31:06.076643135+00:00 PRINT Zigbee Switch Mc << Preference changed name: randomMax old value: nil new value: 10.0
2022-11-21T23:31:06.079952344+00:00 PRINT Zigbee Switch Mc << Preference changed name: offTime old value: nil new value: 10
2022-11-21T23:31:06.083550510+00:00 PRINT Zigbee Switch Mc << Preference changed name: onTime old value: nil new value: 10
2022-11-21T23:31:06.087223594+00:00 PRINT Zigbee Switch Mc << Preference changed name: restoreState old value: nil new value: 255
2022-11-21T23:31:06.090463510+00:00 PRINT Zigbee Switch Mc <<< Write restore state >>>
2022-11-21T23:31:06.095035760+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xC40B, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x4003, DataType: Enum8, data: 0xFF > > > >
2022-11-21T23:31:06.107080427+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xC40B, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x8002, DataType: Enum8, data: 0x02 > > > >
2022-11-21T23:31:06.118682344+00:00 PRINT Zigbee Switch Mc << Preference changed name: groupRemove old value: nil new value: 1.0
2022-11-21T23:31:06.122149052+00:00 PRINT Zigbee Switch Mc Remove Groups >>>>>>>>>>>>>>>>>
2022-11-21T23:31:06.135979635+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xC40B, dest_endpoint: 0x02, profile: 0x0104, cluster: Groups >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x03 >, < RemoveGroup || group_id: 0x0001 > > >
2022-11-21T23:31:06.144594427+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xC40B, dest_endpoint: 0x02, profile: 0x0104, cluster: Groups >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x02 >, < GetGroupMembership || group_list_length: 0x00 > > >
2022-11-21T23:31:06.151684010+00:00 PRINT Zigbee Switch Mc Device ID <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)>
2022-11-21T23:31:06.154832219+00:00 PRINT Zigbee Switch Mc Manufacturer >>> Quirky Manufacturer_Len >>> 6
2022-11-21T23:31:06.167567385+00:00 PRINT Zigbee Switch Mc Model >>> Smart Switch Model_len >>> 12
2022-11-21T23:31:06.170590219+00:00 PRINT Zigbee Switch Mc <<<<< Firmware Version >>>>>
2022-11-21T23:31:06.173866802+00:00 PRINT Zigbee Switch Mc Memory >>>>>>> 1144.3369140625 Kbytes
2022-11-21T23:31:06.177252094+00:00 DEBUG Zigbee Switch Mc Smart Switch device thread event handled
2022-11-21T23:31:06.189320094+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-11-21T23:31:06.195984844+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC40B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -56, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x7D, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || ZclStatus: SUCCESS > > >
2022-11-21T23:31:06.237470344+00:00 DEBUG Zigbee Switch Mc Smart Switch device thread event handled
2022-11-21T23:31:06.243952552+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-11-21T23:31:06.248836635+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC40B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Groups >, lqi: 0xFF, rssi: -58, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x7E, ZCLCommandId: 0x02 >, < GetGroupMembershipResponse || capacity: 0x08, group_list_length: 0x00 > > >
2022-11-21T23:31:06.266028010+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-11-21T23:31:06.307525135+00:00 INFO Zigbee Switch Mc Executing ZclClusterCommandHandler: cluster: Groups, command: GetGroupMembership
2022-11-21T23:31:06.311587177+00:00 PRINT Zigbee Switch Mc group_list >>>>>> {}
2022-11-21T23:31:06.315005177+00:00 PRINT Zigbee Switch Mc All Deleted
2022-11-21T23:31:06.326684677+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> emitting event: {“attribute_id”:“getGroups”,“capability_id”:“legendabsolute60149.getGroups”,“component_id”:“main”,“state”:{“value”:“All Deleted”}}
2022-11-21T23:31:06.337769969+00:00 DEBUG Zigbee Switch Mc Smart Switch device thread event handled
2022-11-21T23:31:06.346041344+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-11-21T23:31:06.353857969+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC40B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -57, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x7F, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, AttributeId: 0x4003 > > > >
2022-11-21T23:31:06.363515469+00:00 DEBUG Zigbee Switch Mc Smart Switch device thread event handled
2022-11-21T23:31:06.366981969+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-11-21T23:31:06.372189802+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC40B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -57, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x00, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, AttributeId: 0x8002 > > > >
2022-11-21T23:31:06.381670219+00:00 DEBUG Zigbee Switch Mc Smart Switch device thread event handled
2022-11-21T23:31:06.385008760+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-11-21T23:31:06.391869594+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC40B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Groups >, lqi: 0xFF, rssi: -56, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x01, ZCLCommandId: 0x03 >, < RemoveGroupResponse || status: 0x8B, group_id: 0x0001 > > >
2022-11-21T23:31:06.431956510+00:00 DEBUG Zigbee Switch Mc Smart Switch device thread event handled
2022-11-21T23:31:06.499419052+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-11-21T23:31:06.504121844+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC40B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Groups >, lqi: 0xFF, rssi: -58, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x02, ZCLCommandId: 0x02 >, < GetGroupMembershipResponse || capacity: 0x08, group_list_length: 0x00 > > >
2022-11-21T23:31:06.512806052+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-11-21T23:31:06.515952302+00:00 INFO Zigbee Switch Mc Executing ZclClusterCommandHandler: cluster: Groups, command: GetGroupMembership
2022-11-21T23:31:06.519454344+00:00 PRINT Zigbee Switch Mc group_list >>>>>> {}
2022-11-21T23:31:06.523080510+00:00 PRINT Zigbee Switch Mc All Deleted
2022-11-21T23:31:06.526627510+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> emitting event: {“attribute_id”:“getGroups”,“capability_id”:“legendabsolute60149.getGroups”,“component_id”:“main”,“state”:{“value”:“All Deleted”}}
2022-11-21T23:31:06.536710260+00:00 DEBUG Zigbee Switch Mc Smart Switch device thread event handled
2022-11-21T23:31:07.016055761+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-11-21T23:31:07.060766344+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC40B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -57, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x01, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-11-21T23:31:07.112678052+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-11-21T23:31:07.164250302+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-11-21T23:31:07.183644552+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart 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/21 Time: 23:31
DNI: 0xC40B LQI: 255 RSSI: -57dbm
”},“visibility”:{“displayed”:false}}
2022-11-21T23:31:07.225862177+00:00 PRINT Zigbee Switch Mc <<<<< device.fingerprinted_endpoint_id >>>>>> 1
2022-11-21T23:31:07.231286969+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-11-21T23:31:07.250327386+00:00 PRINT Zigbee Switch Mc <<<<< device.fingerprinted_endpoint_id >>>>>> 1
2022-11-21T23:31:07.254280094+00:00 ERROR Zigbee Switch Mc Smart Switch thread encountered error: [string “st/dispatcher.lua”]:233: Error encountered while processing event for <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)>:
arg1: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC40B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -57, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x01, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
[string “st/device.lua”]:121: attempt to index a nil value (local ‘component’)
2022-11-21T23:31:35.476225268+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
-------- Device control from smartthings app log ------
2022-11-21T23:36:50.185371707+00:00 TRACE Zigbee Switch Mc Received event with handler capability
2022-11-21T23:36:50.190797207+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“off”,“component”:“main”,“positional_args”:{}}
2022-11-21T23:36:50.194080749+00:00 TRACE Zigbee Switch Mc Found CapabilityCommandDispatcher handler in Zigbee_Switch
2022-11-21T23:36:50.197387791+00:00 PRINT Zigbee Switch Mc <<<<< device.fingerprinted_endpoint_id >>>>>> 1
2022-11-21T23:36:50.217492749+00:00 DEBUG Zigbee Switch Mc Smart Switch device thread event handled
2022-11-21T23:36:50.299888874+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-11-21T23:36:50.304757124+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC40B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -59, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x04, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-11-21T23:36:50.315441541+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-11-21T23:36:50.318784791+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-11-21T23:36:50.329540874+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart 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/21 Time: 23:36
DNI: 0xC40B LQI: 255 RSSI: -59dbm
”},“visibility”:{“displayed”:false}}
2022-11-21T23:36:50.352272791+00:00 PRINT Zigbee Switch Mc <<<<< device.fingerprinted_endpoint_id >>>>>> 1
2022-11-21T23:36:50.356240374+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-11-21T23:36:50.369163624+00:00 PRINT Zigbee Switch Mc <<<<< device.fingerprinted_endpoint_id >>>>>> 1
2022-11-21T23:36:50.374254749+00:00 ERROR Zigbee Switch Mc Smart Switch thread encountered error: [string “st/dispatcher.lua”]:233: Error encountered while processing event for <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)>:
arg1: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC40B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -59, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x04, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
[string “st/device.lua”]:121: attempt to index a nil value (local ‘component’)
2022-11-21T23:36:50.379273624+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-11-21T23:36:50.384215291+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC40B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -60, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x07, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: SUCCESS > > >
2022-11-21T23:36:50.393883374+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-11-21T23:36:50.397451166+00:00 INFO Zigbee Switch Mc Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-11-21T23:36:50.401560707+00:00 PRINT Zigbee Switch Mc <<<<< device.fingerprinted_endpoint_id >>>>>> 1
2022-11-21T23:36:50.405072541+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: c9ddf88d-d9f0-4683-9377-fcf086c512f4 [0xC40B] (Smart Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-11-21T23:36:50.414459791+00:00 DEBUG Zigbee Switch Mc Smart Switch device thread event handled
The error is due to endpoint 1 not can be assigned to a component. The profile only has main component.
This shouldn’t affect the device function, but it looks ugly.
It works well to on-off?
The update message does not affect the operation, it appears on many devices with the latest version of the app.
Tomorrow I will try to solve the endpoint 1 error
Other then the status error message on the app, On-off operation is working well so far. I’ll run some more tests and monitor if the device goes offline.
Here is some additional info i found that might be more meaningful for you as i don’t completely under zigbee protocol.
I have another zigbee switch that is using groovy that I need to migrate over to edge. May have to ask your help again when i get time to get the device info.
Thanks again.
Hi @witchrobin
I modify the driver to assign a new profile to avoid error in log
Try this version
───────────────────────────────────────────────────
Name Zigbee Switch Mc
Version 2022-11-22T17:17:32.914130426
───────────────────────────────────────────────────
Updated the driver and I don’t see the error in log anymore when turning on/off from app. Since this switch does not support power meter, can those related fields in the app be hiddened?
Thanks
It is a virtual power and energy meter, which all profiles have.
To activate it, the value in Watts of the connected load is entered and the driver calculates the consumption virtually
That’s pretty cool. I didn’t know there is an option for virtual calcuation based on the input of the load.
I am also using your Switch Power Mc for an outlet that does have power meter. The power meter value is showing up correctly, but the energy consumption field is empty. It’s only been a day since i used the power Mc driver. Does it take some time for driver to gather the data before showing energy consumption?
There are devices that only support power and do not support energy.
By default I place them in power and energy profile for the clusters that have 0702 and 0B04 or just one of the two.
To see what attributes it supports, you would have to see the pairing logs, which is when the device is configured and answers with what it supports and what it does not support.
@Mariano_Colmenarejo
, As of note to the above posts, I’m using your Zigbee Power MC on 4 Smartthings outlets. I am near certain that these did previously reported energy but now when opening the tile I get a message “couldnt get device status” with the exclamation point on energy consumption
Hi @troy_owens
In this driver I haven’t touched anything since November 9th and for power and energy it only uses the defualt handlers.
I don’t know why this can happen now.
Zigbee Switch Power Mc
2022-11-09T12:41:31.940402857
If it is not solved and you want to send a log turning on and off to see the power and energy messages, I will take a look
Thanks Mariano. temporarily changed the driver back to stock. Been having a lot “Smartthings has stopped responding” (Android) messages lately and on a hunch I changed the driver…messages stopped. When I get a chance, I’ll reinstall your driver on my plugs and get some logs for you.
Added devices to this driver version
───────────────────────────────────────────────────
Name Zigbee Switch Power Mc
Version 2022-11-27T16:25:04.092419894
───────────────────────────────────────────────────
- id: "TS011F/_TZ3000_hdopuwv6"
deviceLabel: Aubess TS011F Plug
manufacturer: _TZ3000_hdopuwv6
model: TS011F
deviceProfileName: switch-power-energy-plug
- id: "SmartPlugHeiman"
deviceLabel: Heiman SmartPlug
manufacturer: Heiman
model: SmartPlug
deviceProfileName: switch-power-energy-plug
Thanks!
Just tried it, seems to work OK. I have to check the power as with previous drivers the power reading was off. Incidentally, is there a way to reset the power consumption figure?
Hi @mickfff
With routines has a command to reset energy.
The default libraries, in zigbee Save the last value and reset to zero de value emitted.
Then the Next readings subtracts the saved value from the accumulated reading received
Thanks to @LG0000 Collaboration, added Interfree devices to this driver version
───────────────────────────────────────────────────
Name Zigbee Multi Switch and Child Mc
Version 2022-11-28T11:37:14.62438017
───────────────────────────────────────────────────
Updated Github with driver code version 4, with two dimmers profile and code to create dimmer child devices.
@LG0000 This driver version is not compatible with version 3.5, due to child devices created are new metadata values. The driver Id created is different
very nice！！！
2-Dim is running well. I will continue to test and let you know if there are any problems.
One problem is that the icon of the switch will be displayed after adding, instead of light. I can manually modify the icon normally.
Can 1-dim use Zigbee Multi Switch and Child Mc?
Which profiles? child-switch-level？
I don’t know if it would work on this driver.
The correct thing would be to put it in zigbee light multifunction Mc, I have put it here.
You can also use zigbee switch stock