Mariano-Github / Edge-Drivers-Beta

Edge Driver Beta Modified for Created
Apache License 2.0
122 stars 121 forks source link

zigbee-contact-mc-v3 attempt to perform arithmetic on a nil value (field 'maxTime') #61

Closed vvicked closed 1 year ago

vvicked commented 1 year ago

Hi, first of all, thank you for the effort you put into these drivers!

I am trying to add my Sercomm Open/Closed Sensor (Quirky Tripper) to smartthings but after adding it, the device is unresponsive. When looking at the driver logs, I can see a the follow error which I assume is causing my problem.

2023-03-14T12:27:39.226275629+00:00 PRINT Zigbee Contact Mc subdriver do_configure 2023-03-14T12:27:39.227414296+00:00 ERROR Zigbee Contact Mc Sercomm Open/Closed Sensor thread encountered error: [string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)>: arg1: doConfigure arg2: table: 0x1c5d330 [string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)>: arg1: doConfigure arg2: table: 0x1c5d330 [string "temperature/init.lua"]:39: attempt to perform arithmetic on a nil value (field 'maxTime') 2023-03-14T12:27:39.242849962+00:00 DEBUG Zigbee Contact Mc Sercomm Open/Closed Sensor device thread event handled'

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

Driver Id Name

──────────────────────────────────────────────────────────────────────────── 1 cdb5df02-8915-474d-941c-3bc6acd46032 LAN Device Monitor 2 c411db9e-a042-459a-a145-f005c65412ee ST Zigbee Button Mc
3 0fd9a9a4-8863-4a83-97a7-5a288ff0f5a6 Virtual Devices V2 4 0ec75098-cf62-47c5-a23c-5bf7fb1f2dd6 Z-Wave Bulb Mc 5 7ca45ba9-7cfe-4547-b752-fe41a0efb848 Z-Wave Device Config Mc ──────────────────────────────────────────────────────────────────────────── 6 e7947a05-947d-4bb5-92c4-2aafaff6d69c Z-Wave Fan 7 d58d8432-ea22-4d38-8300-2bd75fdf1358 Z-Wave Sensor 8 ea748a00-7990-4c87-8275-e15d45d9b40c Z-Wave Siren Mc 9 2cbf55e3-dbc2-48a2-8be5-4c3ce756b692 Z-Wave Switch 10 17c05c19-f008-42e2-aa12-f12f1aae5612 Z-Wave Switch and Child Mc ──────────────────────────────────────────────────────────────────────────── 11 5197249e-95aa-4a27-a08f-2232d193e13b Z-Wave Thing Mc 12 3fb97b6c-f481-441b-a14e-f270d738764e Zigbee Button 13 408981c2-91d4-4dfc-bbfb-84ca0205d993 Zigbee Contact 14 b1504ded-efa4-4ef0-acd5-ae24e7a92e6e Zigbee Contact Mc 15 bb1b3fd4-dcba-4d55-8d85-58ed7f1979fb Zigbee Light Multifunction Mc ──────────────────────────────────────────────────────────────────────────── 16 12e71b3b-184d-4b78-a0e4-679c02ca43dd Zigbee Moisture Sensor Mc 17 1eef4c45-5c94-4442-a771-0edfe41c8f4a Zigbee Multi Sensor Mc 18 e9bfd289-1d51-499e-8c64-d564d1868ad2 Zigbee Multi Switch and Child Mc 19 f2e891c6-00cc-446c-9192-8ebda63d9898 Zigbee Switch 20 bc53adfe-d18f-4ea4-9610-6aade6696b7a Zigbee Switch Mc ──────────────────────────────────────────────────────────────────────────── 21 7fee6e41-26cc-49ef-b1f4-b30a43e02fe6 Zigbee Switch Power Mc 22 d692640b-402a-4d91-9151-d643ad4771f0 Zigbee Thing Mc 23 f82dec82-e5fa-487f-8f0f-22c3e4a8bd89 Zigbee Water Leak Sensor ──────────────────────────────────────────────────────────────────────────── ? Select a driver. 14 connecting... connected 2023-03-14T12:01:09.833128495+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:01:39.834241509+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:02:09.852803017+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:02:39.843141031+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:03:10.023282712+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:03:39.853909060+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:04:09.854718074+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:04:39.907220755+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:05:09.868278769+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:05:39.864763450+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:06:09.915834287+00:00 INFO Zigbee Contact Mc Doing health check read for [EA63]:0500:0002 2023-03-14T12:06:09.927651859+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: b2243242-efbb-4d2d-8582-25d0fe847949 [0xEA63] (Fridge Door Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xEA63, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > > 2023-03-14T12:06:09.932937834+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:06:39.884770636+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:07:09.893165317+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:07:39.894797331+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:08:09.905132679+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:08:39.915103359+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:09:09.924741374+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:09:39.914732388+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:10:09.925337534+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:10:39.925054538+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:11:09.949339875+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:11:39.952383878+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:12:09.954747215+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:12:39.961497552+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:13:09.973365889+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:13:39.995422226+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:14:10.008721983+00:00 INFO Zigbee Contact Mc Doing health check read for [EA63]:0500:0002 2023-03-14T12:14:10.010562880+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: b2243242-efbb-4d2d-8582-25d0fe847949 [0xEA63] (Fridge Door Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xEA63, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > > 2023-03-14T12:14:10.034707522+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:14:40.002211778+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:15:09.994763459+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:15:40.009293473+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:16:10.084268487+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:16:40.025633168+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:17:10.024734182+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:17:40.064896863+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:18:10.044759865+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:18:40.224761552+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:19:10.154781889+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:19:40.195426226+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:20:01.717301895+00:00 TRACE Zigbee Contact Mc Received event with handler device_lifecycle 2023-03-14T12:20:01.718504895+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: b2243242-efbb-4d2d-8582-25d0fe847949 [0xEA63] (Fridge Door Sensor)> received lifecycle event: removed 2023-03-14T12:20:01.720317895+00:00 TRACE Zigbee Contact Mc Received event with handler driver_lifecycle 2023-03-14T12:20:01.721511895+00:00 TRACE Zigbee Contact Mc <ZigbeeDevice: b2243242-efbb-4d2d-8582-25d0fe847949 [0xEA63] (Fridge Door Sensor)> received unhandled lifecycle event: removed 2023-03-14T12:20:01.722882229+00:00 DEBUG Zigbee Contact Mc Fridge Door Sensor device thread event handled 2023-03-14T12:20:01.754755562+00:00 DEBUG Zigbee Contact Mc Fridge Door Sensor device thread event handled 2023-03-14T12:27:38.945631962+00:00 TRACE Zigbee Contact Mc Setup driver zigbee_contact with lifecycle handlers: DeviceLifecycleDispatcher: zigbee_contact default_handlers: doConfigure: infoChanged: driverSwitched: init: child_dispatchers: DeviceLifecycleDispatcher: zigbee_contact -> Cell battery 2.1v default_handlers: init: child_dispatchers: DeviceLifecycleDispatcher: zigbee_contact -> Battery Voltage default_handlers: child_dispatchers: DeviceLifecycleDispatcher: zigbee_contact -> Temp-Sensor default_handlers: doConfigure: child_dispatchers: DeviceLifecycleDispatcher: zigbee_contact -> Multiporpuse default_handlers: added: child_dispatchers: DeviceLifecycleDispatcher: zigbee_contact -> Multiporpuse -> SmartThings multi sensor default_handlers: child_dispatchers:

2023-03-14T12:27:38.947147295+00:00 TRACE Zigbee Contact Mc Setup driver zigbee_contact with Capability handlers: CapabilityCommandDispatcher: zigbee_contact default_handlers: refresh: refresh child_dispatchers: CapabilityCommandDispatcher: zigbee_contact -> Cell battery 2.1v default_handlers: child_dispatchers: CapabilityCommandDispatcher: zigbee_contact -> Battery Voltage default_handlers: child_dispatchers: CapabilityCommandDispatcher: zigbee_contact -> Temp-Sensor default_handlers: child_dispatchers: CapabilityCommandDispatcher: zigbee_contact -> Multiporpuse default_handlers: child_dispatchers: CapabilityCommandDispatcher: zigbee_contact -> Multiporpuse -> SmartThings multi sensor default_handlers: child_dispatchers:

2023-03-14T12:27:38.948559962+00:00 TRACE Zigbee Contact Mc Setup driver zigbee_contact with Zigbee handlers: ZigbeeMessageDispatcher: zigbee_contact default_handlers: attr: ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus global: cluster: ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse zdo: child_dispatchers: ZigbeeMessageDispatcher: zigbee_contact -> Cell battery 2.1v default_handlers: attr: global: cluster: zdo: child_dispatchers: ZigbeeMessageDispatcher: zigbee_contact -> Battery Voltage default_handlers: attr: ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage global: cluster: zdo: child_dispatchers: ZigbeeMessageDispatcher: zigbee_contact -> Temp-Sensor default_handlers: attr: ZclClusterAttributeValueHandler: cluster: TemperatureMeasurement, attribute: MeasuredValue global: cluster: zdo: child_dispatchers: ZigbeeMessageDispatcher: zigbee_contact -> Multiporpuse default_handlers: attr: ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0014 ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0010 ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0012 ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0013 ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus global: cluster: ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse zdo: child_dispatchers: ZigbeeMessageDispatcher: zigbee_contact -> Multiporpuse -> SmartThings multi sensor default_handlers: attr: ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0010 ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0014 ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0012 ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0013 global: cluster: zdo: child_dispatchers:

2023-03-14T12:27:39.105805295+00:00 TRACE Zigbee Contact Mc Zigbee Device: 90412f4f-5b61-473b-b572-cb4d71c10bc0 Manufacturer: Sercomm Corp. Model: Tripper [1]: Basic, PowerConfiguration, Identify, IASZone, PollControl, Diagnostics 2023-03-14T12:27:39.106914295+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:27:39.108184962+00:00 TRACE Zigbee Contact Mc Received event with handler _resync 2023-03-14T12:27:39.109315629+00:00 TRACE Zigbee Contact Mc Received event with handler environment_info 2023-03-14T12:27:39.131537629+00:00 TRACE Zigbee Contact Mc Found DeviceLifecycleDispatcher handler in zigbee_contact 2023-03-14T12:27:39.132714962+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAFEF, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0020 > > > 2023-03-14T12:27:39.145446962+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"Waiting Zigbee Message"},"visibility":{"displayed":false}} 2023-03-14T12:27:39.175224296+00:00 DEBUG Zigbee Contact Mc Sercomm Open/Closed Sensor device thread event handled 2023-03-14T12:27:39.176427629+00:00 TRACE Zigbee Contact Mc Received event with handler environment_info 2023-03-14T12:27:39.207456962+00:00 DEBUG Zigbee Contact Mc Z-Wave hub node ID environment changed. 2023-03-14T12:27:39.208319629+00:00 TRACE Zigbee Contact Mc Received event with handler device_lifecycle 2023-03-14T12:27:39.209456962+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> received lifecycle event: added 2023-03-14T12:27:39.211098296+00:00 TRACE Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> received unhandled lifecycle event: added 2023-03-14T12:27:39.212285296+00:00 DEBUG Zigbee Contact Mc Sercomm Open/Closed Sensor device thread event handled 2023-03-14T12:27:39.213422629+00:00 TRACE Zigbee Contact Mc Received event with handler device_lifecycle 2023-03-14T12:27:39.214836962+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> received lifecycle event: doConfigure 2023-03-14T12:27:39.225444962+00:00 TRACE Zigbee Contact Mc Found DeviceLifecycleDispatcher handler in zigbee_contact -> Temp-Sensor 2023-03-14T12:27:39.226275629+00:00 PRINT Zigbee Contact Mc subdriver do_configure 2023-03-14T12:27:39.227414296+00:00 ERROR Zigbee Contact Mc Sercomm Open/Closed Sensor thread encountered error: [string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)>: arg1: doConfigure arg2: table: 0x1c5d330 [string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)>: arg1: doConfigure arg2: table: 0x1c5d330 [string "temperature/init.lua"]:39: attempt to perform arithmetic on a nil value (field 'maxTime') 2023-03-14T12:27:39.242849962+00:00 DEBUG Zigbee Contact Mc Sercomm Open/Closed Sensor device thread event handled 2023-03-14T12:27:39.497131296+00:00 TRACE Zigbee Contact Mc Received event with handler device_lifecycle 2023-03-14T12:27:39.498098629+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> received lifecycle event: infoChanged 2023-03-14T12:27:39.525467962+00:00 TRACE Zigbee Contact Mc Found DeviceLifecycleDispatcher handler in zigbee_contact 2023-03-14T12:27:39.526317629+00:00 PRINT Zigbee Contact Mc * infoChanged ***** 2023-03-14T12:27:39.527463629+00:00 PRINT Zigbee Contact Mc device.preferences[infoChanged]= No preferences: signalMetricsVisibles 2023-03-14T12:27:39.528593296+00:00 PRINT Zigbee Contact Mc << Preference changed name: signalMetricsVisibles old value: nil new value: No 2023-03-14T12:27:39.529719296+00:00 PRINT Zigbee Contact Mc device.preferences[infoChanged]= preferences: version 2023-03-14T12:27:39.531182629+00:00 PRINT Zigbee Contact Mc << Preference changed name: version old value: nil new value: 2023-03-14T12:27:39.532687296+00:00 PRINT Zigbee Contact Mc Device ID <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> 2023-03-14T12:27:39.535867962+00:00 PRINT Zigbee Contact Mc Manufacturer >>> Sercomm Corp. Manufacturer_Len >>> 13 2023-03-14T12:27:39.537950629+00:00 PRINT Zigbee Contact Mc Model >>> Tripper Model_len >>> 7 2023-03-14T12:27:39.540028962+00:00 PRINT Zigbee Contact Mc Memory >>>>>>> 1072.5146484375 Kbytes 2023-03-14T12:27:39.542328962+00:00 PRINT Zigbee Contact Mc <<<<< Firmware Version >>>>> Unknown 2023-03-14T12:27:39.544536962+00:00 DEBUG Zigbee Contact Mc Sercomm Open/Closed Sensor device thread event handled 2023-03-14T12:27:39.779414629+00:00 TRACE Zigbee Contact Mc Received event with handler zigbee 2023-03-14T12:27:39.780387962+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAFEF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xC8, rssi: -66, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7B, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0020, ZclStatus: SUCCESS, DataType: Uint8, BatteryVoltage: 0x1B > > > > 2023-03-14T12:27:39.806115962+00:00 TRACE Zigbee Contact Mc Found ZigbeeMessageDispatcher handler in zigbee_contact -> Battery Voltage 2023-03-14T12:27:39.806968962+00:00 INFO Zigbee Contact Mc Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage 2023-03-14T12:27:39.809776296+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"<em table style='font-size:70%';'font-weight: bold'GMT: 2023/03/14 Time: 12:27
DNI: 0xAFEF LQI: 200 RSSI: -66dbm
"},"visibility":{"displayed":false}} 2023-03-14T12:27:39.831717629+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> emitting event: {"attribute_id":"battery","capability_id":"battery","component_id":"main","state":{"value":100}} 2023-03-14T12:27:39.833062629+00:00 DEBUG Zigbee Contact Mc Sercomm Open/Closed Sensor device thread event handled 2023-03-14T12:28:06.325127642+00:00 TRACE Zigbee Contact Mc Received event with handler zigbee 2023-03-14T12:28:06.326317642+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x02, < AddressHeader || src_addr: 0xAFEF, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: OnOff >, lqi: 0xD0, rssi: -68, body_length: 0x0009, < ZDOMessageBody || < ZDOHeader || seqno: 0x02 >, GenericBody: FD FF 04 01 00 01 00 05 > > 2023-03-14T12:28:06.330070308+00:00 DEBUG Zigbee Contact Mc Sercomm Open/Closed Sensor device thread event handled 2023-03-14T12:28:08.949855310+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:28:38.957911324+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:29:08.961589338+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:29:38.971983686+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:30:08.981083700+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:30:38.991191444+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:31:09.014890459+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:31:39.022638473+00:00 INFO Zigbee Contact Mc Doing health check read for [AFEF]:0500:0002 2023-03-14T12:31:39.031358806+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAFEF, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > > 2023-03-14T12:31:39.036932473+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:32:09.017119821+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:32:39.104747835+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:33:09.014010516+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:33:39.021347864+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:34:09.023513878+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:34:39.031154402+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:35:09.033682417+00:00 DEBUG Zigbee Contact Mc driver device thread event handled 2023-03-14T12:35:39.041277098+00:00 DEBUG Zigbee Contact Mc driver device thread event handled

Mariano-Github commented 1 year ago

Hi, Fixed in this driver version. It was assigned to wrong temperature subdriver ─────────────────────────────────────────────────── Name Zigbee Contact Mc Version 2023-03-15T10:12:35.340186136 ───────────────────────────────────────────────────

vvicked commented 1 year ago

Hi Mariano. Forgive my ignorance, but how do I get that version of the driver?

Mariano-Github commented 1 year ago

This new version will bee updated in your hub automatically in 12 hours máximum

vvicked commented 1 year ago

Awesome. Thank you for the prompt response.