Many zigbee devices randomly go offline, network very unstable

I have three zigbee devices that update a lot>my solar panel drivers that update their wattage a lot. However i doubt they are the cause of drama, as the issues are mostly apparant in the evening, and then the solar panels do not have new readings to update’ they stick to 0 when the sun is gone.
For the rest i dont know what can cause all the trouble, but i really hope the logcat file will give me some insight in the evening, and hope you guys might have some time to help out digging into this, to find and eliminate the “ghost” in the house.

Edit: i do have a virtual switch that i turn on and off all the time(every 8s or so non-stop) because it acts as a trigger. (For example if i have a routine that turns on the lights in the living room if movement is detected, it wont execute if there is already movement detected. I have to move away and return for it to re-trigger) if i add a 8s virtual switch to the routine, it will work together with the real condition and this virtual switch to execute the routine, if that makes sense.

Hi again everyone.

So, i have a 230mB log file. Is it save to share this file or does it contain sensitive info?

Where do i start to finding the culprit with the search function?
During the day and logging, i made a few notes regarding the ghost in the smart home/house.

16:10-16:15 perfect executions smartthings routines. Light kitchen, hallway and tv turn on.

18:53: no reaction from kitchen lights routine. None of the 4 devices turn on. (one smart plug and 3 zigbee bulbs)

19:11 lights in kitchen turned on very slowly, but are all working. (one smart plug and 3 zigbee bulbs)

21:47 lights in kitchen((one smart plug and 3 zigbee bulbs)) not turning on.

21:47 plant light bulbs not turning off when i press the button on a ikea remote.

At the risk of derailing the thread …

If you have a routine that turns on the lights if movement is detected and movement has been detected, what happens to the lights to need the routine to execute again?

If you look at your mobile app History (the one you get with the Menu > History) at those times, what do you see related to the triggering event (e.g. device reporting motion) and the routines running?

Not at all, or not first time? Some buttons, including Ikea ones, do seem to take a nap after a while and need the first press to start paying attention. What does the app History show around this time?

That’s all a step back from looking at the logcat output. I’m just curious to get the ‘systems’ idea of what is going on when you see problems as an intermediate stage between your view and logcat.

I dont understand this question…

As for your other reply, i will check the times tommorow and dig around, thanks! Although not sure what you mean with your last part.
The problems are certainly smartthings/hub related, as normally the routined execute fine. But every day i have stuff not working, that are completely random.

My Zigbee devices are unstable after the update.

Hub V2, Sonoff SNZB-04 devices, Zigbee Contact MC edge driver.

1 Like

You mentioned a virtual switch being turned on every eight seconds or so in order to trigger routines.

Your example was a routine that turned on lights in the living room when motion was detected that needed a secondary trigger to execute it if motion was already detected. I was assuming it was a real life example.

Given that any such routine should have turned on the lights when motion started I was wondering why you would need to execute the routine again while motion was still being reported. Why would you turn the lights off when motion was still being detected if you are going to turn them on within about eight seconds? I could see what the virtual switch was doing but as a real example it didn’t seem to make sense.

My other comment was really that going straight to logcat seemed to be jumping a few pages and using the basic app tools might be a better start. So, for example, if nothing happens when you press a button it would be good to know if the button press has been noticed and if that made a routine run.

The real life scenario is that smartthings does nothing unless a state changes.
The presense sensor detects us at all times when in the room. If we stay in there, the lights wont turn on sometimes because of my ghost in the house, it misses the other activation criteria of lux requirement. When having a virtual switch constantly going on and off and including that in routines, smartthings basically constantly checks if conditions are met instead of waiting for a state to change. Because the virtual switch is constantly changing state.

As for the last part of your reply, i do not see the button press in the history of the device in the smartthings app.
I do see history earlier that day.
So the “ghost” was active at that time i guess.

However, the motion sensor in the kitchen did got recorded into history…while the routine did not execute. Which is super odd…the button did not save anything in history but the motiom sensor did, and no actions were taken.

Do you use edge drivers from mariano?
Also @gmoscard are you?

@nayelyz this is worth checking out. This thread got linked from here as well: Smartthings hub connected devices very unstable

If you want to use my hub or access to my home for testing, thats ok. Issues are every day, and multiple users are reporting issues now. Would love some smartthings dev’s to also look into this, as the issue is now here for around a month or so.

Confirmed my drivers are from mariano

1 Like

So, now looking into the logs…Before i wanted to check the reportings of my kitchen motion sensor, i see it reports motion now, for 11 minutes straight, while no one is in the kitchen room for the last 11 minutes…

But let’s check the logcat logbook.

There was no routine executed while i expected lights to turn on in the kitchen(4 devices) at 18:53. I see motion was detected at 18:54. could be i got a minute off in my notition making.
Looking at logcat, i don’t see anything special unfortunately.
Here are the 2 minutes where this happened(or rather, nothing happened while there should have been, lol)
https://justpaste.it/7a4xw

The motion sensor was noted in the logcat logbook:

2023-06-18T16:54:46.586641128+00:00 TRACE frient Motion Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-06-18T16:54:46.587482461+00:00 INFO frient Motion Executing ZclClusterAttributeValueHandler: cluster: OccupancySensing, attribute: Occupancy

This followed afterwards: Some warn messages as well.

2023-06-18T16:54:46.610582461+00:00 DEBUG Zigbee Sensors Edge Driver [YG] 1.8.16  driver device thread event handled
2023-06-18T16:54:46.631682794+00:00 INFO frient Motion  <ZigbeeDevice: 6e577da2-b8af-438f-bd4e-86b7b35ef85e [0x2457] (Kitchen Motion Sensor)> emitting event: {"state":{"value":"inactive"},"component_id":"main","capability_id":"motionSensor","attribute_id":"motion"}
2023-06-18T16:54:46.657688794+00:00 DEBUG Ikea Styrbar Remote  driver device thread event handled
2023-06-18T16:54:46.723182128+00:00 INFO Personal Tuya Devices - main  <ZigbeeDevice: d39a5edc-0f4d-44fa-9ad5-f15277ca0605 [0x1903] (Presense Sensor PC Corner)> emitting event: {"component_id":"main","attribute_id":"value","state":{"value":"<table style=\"font-size:0.6em;min-width:100%\"><tbody><tr><th align=\"left\" style=\"width:50%\">detection_delay</th><td style=\"width:50%\">50</td></tr><tr><th align=\"left\" style=\"width:50%\">fading_time</th><td style=\"width:50%\">1</td></tr><tr><th align=\"left\" style=\"width:50%\">far_detection</th><td style=\"width:50%\">95</td></tr><tr><th align=\"left\" style=\"width:50%\">near_detection</th><td style=\"width:50%\">9</td></tr><tr><th align=\"left\" style=\"width:50%\">sensitivity</th><td style=\"width:50%\">7</td></tr></tbody></table>"},"capability_id":"valleyboard16460.settings"}
2023-06-18T16:54:46.891962794+00:00 INFO Hue Motion Sensor  Doing health check read for [ADB9]:0400:0000
2023-06-18T16:54:46.900580794+00:00 INFO Hue Motion Sensor  <ZigbeeDevice: 9f165afa-17d5-4170-a901-c51d6d245dc8 [0xADB9] (Outdoor Sensor Garage)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xADB9, dest_endpoint: 0x02, profile: 0x0104, cluster: IlluminanceMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2023-06-18T16:54:46.927817461+00:00 INFO Hue Motion Sensor  Doing health check read for [ADB9]:0402:0000
2023-06-18T16:54:46.977431128+00:00 TRACE Zigbee Switch  Found ZigbeeMessageDispatcher handler in zigbee_switch
2023-06-18T16:54:46.978274794+00:00 INFO Zigbee Switch  Executing ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ActivePower
2023-06-18T16:54:46.990515461+00:00 INFO Zigbee Switch  <ZigbeeDevice: 83df0323-f994-4a8b-9575-72d5b4a4c9c4 [0xA867] (Keuken Led Strip)> emitting event: {"component_id":"main","capability_id":"powerMeter","state":{"value":13.0,"unit":"W"},"attribute_id":"power"}
2023-06-18T16:54:47.283987795+00:00 DEBUG frient Motion  Kitchen Motion Sensor device thread event handled
2023-06-18T16:54:47.298464461+00:00 DEBUG frient Motion  driver device thread event handled
2023-06-18T16:54:47.309885795+00:00 TRACE frient Motion  Received event with handler zigbee
2023-06-18T16:54:47.329456795+00:00 INFO frient Motion  <ZigbeeDevice: 6e577da2-b8af-438f-bd4e-86b7b35ef85e [0x2457] (Kitchen Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2457, src_endpoint: 0x23, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xB4, rssi: -86, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x70, ZCLCommandId: 0x00 >, < ZoneStatusChangeNotification || zone_status: 0x0031, extended_status: 0x00, zone_id: 0x01, delay: 0x0064 > > >
2023-06-18T16:54:47.535280461+00:00 DEBUG Zigbee Switch  Keuken Led Strip device thread event handled
2023-06-18T16:54:47.599413795+00:00 INFO Hue Motion Sensor  <ZigbeeDevice: 9f165afa-17d5-4170-a901-c51d6d245dc8 [0xADB9] (Outdoor Sensor Garage)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xADB9, dest_endpoint: 0x02, profile: 0x0104, cluster: TemperatureMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2023-06-18T16:54:48.191991128+00:00 DEBUG Zigbee Switch  driver device thread event handled
2023-06-18T16:54:48.358545128+00:00 INFO Hue Motion Sensor  Doing health check read for [ADB9]:0406:0000
2023-06-18T16:54:48.523349795+00:00 INFO Hue Motion Sensor  <ZigbeeDevice: 9f165afa-17d5-4170-a901-c51d6d245dc8 [0xADB9] (Outdoor Sensor Garage)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xADB9, dest_endpoint: 0x02, profile: 0x0104, cluster: OccupancySensing >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2023-06-18T16:54:48.777796795+00:00 DEBUG Hue Motion Sensor  driver device thread event handled
2023-06-18T16:54:48.835378129+00:00 TRACE frient Motion  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-06-18T16:54:48.850286795+00:00 INFO frient Motion  Executing ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
2023-06-18T16:54:48.852014462+00:00 DEBUG frient Motion  Received IAS Zone Change:{byte_length=2, field_name="zone_status", value=49}
2023-06-18T16:54:48.853236129+00:00 WARN frient Motion  Attempted to generate event for 6e577da2-b8af-438f-bd4e-86b7b35ef85e.main but it does not support capability Tamper Alert
2023-06-18T16:54:48.893255462+00:00 DEBUG frient Motion  Kitchen Motion Sensor device thread event handled
2023-06-18T16:54:48.910571129+00:00 TRACE frient Motion  Received event with handler zigbee
2023-06-18T16:54:48.912092795+00:00 INFO frient Motion  <ZigbeeDevice: 6e577da2-b8af-438f-bd4e-86b7b35ef85e [0x2457] (Kitchen Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2457, src_endpoint: 0x22, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, lqi: 0xAE, rssi: -84, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x73, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Bitmap8, Occupancy: Occupancy[0x01] > > > >
2023-06-18T16:54:48.958881795+00:00 WARN Personal Tuya Devices - main  Unexpected component for datapoint	6	111	nil	[string "st/device.lua"]:121: attempt to index a nil value (local 'component')	nil
2023-06-18T16:54:49.039573795+00:00 INFO Personal Tuya Devices - main  Datapoint negative.	-111
2023-06-18T16:54:49.042332462+00:00 DEBUG Personal Tuya Devices - main  Presense Sensor PC Corner device thread event handled
2023-06-18T16:54:49.043627129+00:00 TRACE Personal Tuya Devices - main  Received event with handler zigbee
2023-06-18T16:54:49.044828129+00:00 INFO Personal Tuya Devices - main  <ZigbeeDevice: d39a5edc-0f4d-44fa-9ad5-f15277ca0605 [0x1903] (Presense Sensor PC Corner)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1903, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xCC, rssi: -47, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0xD5, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x005E (BE), < DatapointSegment || dpid: 0x6E, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x00000032 (BE) > > > >
2023-06-18T16:54:50.146996129+00:00 TRACE Personal Tuya Devices - main  Found ZigbeeMessageDispatcher handler in personal-tuya-devices -> GenericEF00 -> Model
2023-06-18T16:54:50.207236463+00:00 INFO Personal Tuya Devices - main  Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-06-18T16:54:50.224599129+00:00 TRACE frient Motion  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-06-18T16:54:50.226787129+00:00 INFO frient Motion  Executing ZclClusterAttributeValueHandler: cluster: OccupancySensing, attribute: Occupancy
2023-06-18T16:54:50.240151129+00:00 INFO frient Motion  <ZigbeeDevice: 6e577da2-b8af-438f-bd4e-86b7b35ef85e [0x2457] (Kitchen Motion Sensor)> emitting event: {"state":{"value":"active"},"component_id":"main","capability_id":"motionSensor","attribute_id":"motion"}
2023-06-18T16:54:50.298461796+00:00 DEBUG frient Motion  Kitchen Motion Sensor device thread event handled
2023-06-18T16:54:50.387655463+00:00 INFO Personal Tuya Devices - main  pref_name	prefDetectionDelay	50	-
2023-06-18T16:54:50.571131796+00:00 TRACE Virtual Devices V2  Received event with handler capability
2023-06-18T16:54:50.672860130+00:00 TRACE Zigbee Switch  Received event with handler capability
2023-06-18T16:54:51.660064797+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> received command: {"capability":"switch","args":{},"command":"off","component":"main","positional_args":{}}
2023-06-18T16:54:51.700977797+00:00 TRACE Virtual Devices V2  Found CapabilityCommandDispatcher handler in vedgeDriver
2023-06-18T16:54:51.711561463+00:00 INFO Virtual Devices V2  Virtual switch turned >> off <<
2023-06-18T16:54:51.774031797+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> emitting event: {"component_id":"main","state":{"value":"off"},"attribute_id":"switch","capability_id":"switch"}
2023-06-18T16:54:51.777303463+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> emitting event: {"component_id":"main","state":{"value":"closed"},"attribute_id":"contact","capability_id":"contactSensor"}
2023-06-18T16:54:51.947931130+00:00 INFO Personal Tuya Devices - main  <ZigbeeDevice: d39a5edc-0f4d-44fa-9ad5-f15277ca0605 [0x1903] (Presense Sensor PC Corner)> emitting event: {"component_id":"main","attribute_id":"value","state":{"value":"<table style=\"font-size:0.6em;min-width:100%\"><tbody><tr><th align=\"left\" style=\"width:50%\">detection_delay</th><td style=\"width:50%\">50</td></tr><tr><th align=\"left\" style=\"width:50%\">fading_time</th><td style=\"width:50%\">1</td></tr><tr><th align=\"left\" style=\"width:50%\">far_detection</th><td style=\"width:50%\">95</td></tr><tr><th align=\"left\" style=\"width:50%\">near_detection</th><td style=\"width:50%\">9</td></tr><tr><th align=\"left\" style=\"width:50%\">sensitivity</th><td style=\"width:50%\">7</td></tr></tbody></table>"},"capability_id":"valleyboard16460.settings"}
2023-06-18T16:54:51.982042797+00:00 INFO Zigbee Switch  <ZigbeeDevice: 4dcac771-2df0-414c-b7b1-61759926da8f [0xB587] (Bijkeuken lamp)> received command: {"capability":"switch","component":"main","command":"on","args":{},"positional_args":{}}
2023-06-18T16:54:52.014378464+00:00 TRACE Zigbee Switch  Found CapabilityCommandDispatcher handler in zigbee_switch -> ZLL Dimmer Bulb
2023-06-18T16:54:52.015846130+00:00 INFO Zigbee Switch  <ZigbeeDevice: 4dcac771-2df0-414c-b7b1-61759926da8f [0xB587] (Bijkeuken lamp)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xB587, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On ||  > > >
2023-06-18T16:54:52.025402797+00:00 DEBUG Virtual Devices V2  vEdge Living Room Presense device thread event handled
2023-06-18T16:54:52.084171130+00:00 WARN Personal Tuya Devices - main  Unexpected component for datapoint	5	110	nil	[string "st/device.lua"]:121: attempt to index a nil value (local 'component')	nil
2023-06-18T16:54:52.085067797+00:00 INFO Personal Tuya Devices - main  Datapoint negative.	-110
2023-06-18T16:54:52.086255464+00:00 DEBUG Personal Tuya Devices - main  Presense Sensor PC Corner device thread event handled
2023-06-18T16:54:52.087478130+00:00 TRACE Personal Tuya Devices - main  Received event with handler zigbee
2023-06-18T16:54:52.088688797+00:00 INFO Personal Tuya Devices - main  <ZigbeeDevice: d39a5edc-0f4d-44fa-9ad5-f15277ca0605 [0x1903] (Presense Sensor PC Corner)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1903, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xCA, rssi: -45, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0xD6, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x005F (BE), < DatapointSegment || dpid: 0x6D, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x00000000 (BE) > > > >
2023-06-18T16:54:52.231029797+00:00 DEBUG Zigbee Switch  Bijkeuken lamp device thread event handled
2023-06-18T16:54:52.231977130+00:00 TRACE Zigbee Switch  Received event with handler capability
2023-06-18T16:54:52.337579130+00:00 TRACE Virtual Devices V2  Received event with handler capability

What i also find weird is that it seems like a outdoor motion sensor (garage) is reporting things to the smartthings v3 hub, that is shown offline in my smartthings app for a long long time already.

Really crazy stuff.

Then perhaps it is his drivers that are not playing nicely with some update that smartthings pushed.

EDIT: Investigated issue 2. A slow response/reaction time:

2023-06-18T17:11:46.173178518+00:00 TRACE frient Motion  Received event with handler zigbee
2023-06-18T17:11:46.174459491+00:00 INFO frient Motion  <ZigbeeDevice: 6e577da2-b8af-438f-bd4e-86b7b35ef85e [0x2457] (Kitchen Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2457, src_endpoint: 0x22, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, lqi: 0xBA, rssi: -85, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x1C, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Bitmap8, Occupancy: Occupancy[0x01] > > > >
2023-06-18T17:11:46.191969909+00:00 TRACE Virtual Devices V2  Received event with handler capability
2023-06-18T17:11:46.192841011+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> received command: {"capability":"switch","args":{},"command":"off","component":"main","positional_args":{}}
2023-06-18T17:11:46.200588549+00:00 TRACE Virtual Devices V2  Found CapabilityCommandDispatcher handler in vedgeDriver
2023-06-18T17:11:46.209579709+00:00 INFO Virtual Devices V2  Virtual switch turned >> off <<
2023-06-18T17:11:46.210862350+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> emitting event: {"component_id":"main","state":{"value":"off"},"attribute_id":"switch","capability_id":"switch"}
2023-06-18T17:11:46.667136374+00:00 TRACE Zigbee Switch  Received event with handler zigbee
2023-06-18T17:11:46.690354310+00:00 INFO Zigbee Switch  <ZigbeeDevice: 1bb21603-e391-4e2a-9a64-96976ef89cdb [0x6CA8] (Coaster hallway)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6CA8, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xBC, rssi: -85, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x05, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2023-06-18T17:11:46.692200900+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> emitting event: {"component_id":"main","state":{"value":"closed"},"attribute_id":"contact","capability_id":"contactSensor"}
2023-06-18T17:11:46.693938101+00:00 TRACE Personal Tuya Devices - main  Found ZigbeeMessageDispatcher handler in personal-tuya-devices -> GenericEF00 -> Model
2023-06-18T17:11:46.740751163+00:00 INFO Personal Tuya Devices - main  Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-06-18T17:11:46.743231069+00:00 WARN Personal Tuya Devices - main  Datapoint not found. Using default	9	datatype	2
2023-06-18T17:11:46.773053639+00:00 TRACE frient Motion  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-06-18T17:11:46.780882552+00:00 INFO frient Motion  Executing ZclClusterAttributeValueHandler: cluster: OccupancySensing, attribute: Occupancy
2023-06-18T17:11:46.809478843+00:00 INFO frient Motion  <ZigbeeDevice: 6e577da2-b8af-438f-bd4e-86b7b35ef85e [0x2457] (Kitchen Motion Sensor)> emitting event: {"state":{"value":"active"},"component_id":"main","capability_id":"motionSensor","attribute_id":"motion"}
2023-06-18T17:11:46.813219379+00:00 DEBUG frient Motion  Kitchen Motion Sensor device thread event handled
2023-06-18T17:11:47.002937524+00:00 DEBUG Virtual Devices V2  vEdge Living Room Presense device thread event handled
2023-06-18T17:11:47.009548161+00:00 TRACE Virtual Devices V2  Received event with handler capability
2023-06-18T17:11:47.104619339+00:00 TRACE Zigbee Switch  Found ZigbeeMessageDispatcher handler in zigbee_switch
2023-06-18T17:11:47.105844952+00:00 INFO Zigbee Switch  Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2023-06-18T17:11:47.152106404+00:00 INFO Zigbee Switch  <ZigbeeDevice: 1bb21603-e391-4e2a-9a64-96976ef89cdb [0x6CA8] (Coaster hallway)> emitting event: {"component_id":"main","capability_id":"switch","state":{"value":"on"},"attribute_id":"switch"}
2023-06-18T17:11:47.208060034+00:00 TRACE frient Motion  Received event with handler zigbee
2023-06-18T17:11:47.295698164+00:00 INFO frient Motion  <ZigbeeDevice: b7a55348-c74d-4e8b-868e-0e2b7e848c50 [0xD028] (Motion Sensor Hallway)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD028, src_endpoint: 0x23, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xC4, rssi: -79, body_length: 0x000E, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x22, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0020, DataType: Uint8, BatteryVoltage: 0x1E >, < AttributeRecord || AttributeId: 0x003E, DataType: Bitmap32, BatteryAlarmState: 0x00000000 > > > >
2023-06-18T17:11:47.323022153+00:00 WARN Personal Tuya Devices - main  Unexpected component for datapoint	9	9	nil	[string "st/device.lua"]:121: attempt to index a nil value (local 'component')	nil
2023-06-18T17:11:47.340221415+00:00 INFO Personal Tuya Devices - main  Datapoint negative.	-9
2023-06-18T17:11:47.341435688+00:00 DEBUG Personal Tuya Devices - main  Presense Sensor Billiard Room device thread event handled
2023-06-18T17:11:47.342652296+00:00 TRACE Personal Tuya Devices - main  Received event with handler zigbee
2023-06-18T17:11:47.343818546+00:00 INFO Personal Tuya Devices - main  <ZigbeeDevice: d39a5edc-0f4d-44fa-9ad5-f15277ca0605 [0x1903] (Presense Sensor PC Corner)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1903, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xD0, rssi: -46, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x60, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x00E3 (BE), < DatapointSegment || dpid: 0x6D, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x00000000 (BE) > > > >
2023-06-18T17:11:47.562799982+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> received command: {"capability":"switch","args":{},"command":"on","component":"main","positional_args":{}}
2023-06-18T17:11:48.169308752+00:00 TRACE Virtual Devices V2  Found CapabilityCommandDispatcher handler in vedgeDriver
2023-06-18T17:11:48.191746298+00:00 INFO Virtual Devices V2  Virtual switch turned >> on <<
2023-06-18T17:11:48.195418800+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> emitting event: {"component_id":"main","state":{"value":"on"},"attribute_id":"switch","capability_id":"switch"}
2023-06-18T17:11:48.638660310+00:00 DEBUG Zigbee Switch  Coaster hallway device thread event handled
2023-06-18T17:11:48.640573600+00:00 TRACE Zigbee Switch  Received event with handler zigbee
2023-06-18T17:11:48.658613282+00:00 INFO Zigbee Switch  <ZigbeeDevice: 1bb21603-e391-4e2a-9a64-96976ef89cdb [0x6CA8] (Coaster hallway)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6CA8, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xBC, rssi: -83, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0xB3, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2023-06-18T17:11:48.675473374+00:00 TRACE frient Motion  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-06-18T17:11:48.722574246+00:00 INFO frient Motion  Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
2023-06-18T17:11:48.792221386+00:00 INFO frient Motion  <ZigbeeDevice: b7a55348-c74d-4e8b-868e-0e2b7e848c50 [0xD028] (Motion Sensor Hallway)> emitting event: {"state":{"value":100},"component_id":"main","capability_id":"battery","attribute_id":"battery"}
2023-06-18T17:11:48.809325934+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> emitting event: {"component_id":"main","state":{"value":"open"},"attribute_id":"contact","capability_id":"contactSensor"}
2023-06-18T17:11:48.825384959+00:00 TRACE Personal Tuya Devices - main  Found ZigbeeMessageDispatcher handler in personal-tuya-devices -> GenericEF00 -> Model
2023-06-18T17:11:48.826651259+00:00 INFO Personal Tuya Devices - main  Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-06-18T17:11:48.879317245+00:00 WARN Personal Tuya Devices - main  Datapoint not found. Using default	109	datatype	2
2023-06-18T17:11:48.880641574+00:00 DEBUG Hue Motion Sensor  driver device thread event handled
2023-06-18T17:11:48.881856848+00:00 DEBUG Ikea Styrbar Remote  driver device thread event handled
2023-06-18T17:11:48.920245032+00:00 DEBUG Virtual Devices V2  vEdge Living Room Presense device thread event handled
2023-06-18T17:11:48.930548848+00:00 DEBUG Zigbee Sensors Edge Driver [YG] 1.8.16  driver device thread event handled
2023-06-18T17:11:49.170323676+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> received command: {"capability":"switch","args":{},"command":"off","component":"main","positional_args":{}}
2023-06-18T17:11:49.480363619+00:00 TRACE Virtual Devices V2  Found CapabilityCommandDispatcher handler in vedgeDriver
2023-06-18T17:11:49.550087797+00:00 INFO Virtual Devices V2  Virtual switch turned >> off <<
2023-06-18T17:11:49.552321913+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> emitting event: {"component_id":"main","state":{"value":"off"},"attribute_id":"switch","capability_id":"switch"}
2023-06-18T17:11:49.554295900+00:00 DEBUG frient Motion  Motion Sensor Hallway device thread event handled
2023-06-18T17:11:49.557770636+00:00 DEBUG frient Motion  driver device thread event handled
2023-06-18T17:11:49.781632178+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> emitting event: {"component_id":"main","state":{"value":"closed"},"attribute_id":"contact","capability_id":"contactSensor"}
2023-06-18T17:11:49.825415392+00:00 WARN Personal Tuya Devices - main  Unexpected component for datapoint	109	109	nil	[string "st/device.lua"]:121: attempt to index a nil value (local 'component')	nil
2023-06-18T17:11:49.880590632+00:00 INFO Personal Tuya Devices - main  Datapoint negative.	-109
2023-06-18T17:11:49.924401527+00:00 DEBUG Personal Tuya Devices - main  Presense Sensor PC Corner device thread event handled
2023-06-18T17:11:49.925668160+00:00 TRACE Personal Tuya Devices - main  Received event with handler zigbee
2023-06-18T17:11:49.926866425+00:00 INFO Personal Tuya Devices - main  <ZigbeeDevice: 540595a6-eea4-450e-9bd1-b65ecd33038d [0xBFFE] (Presense Sensor Billiard Room)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFFE, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xB2, rssi: -84, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x10, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x00CD (BE), < DatapointSegment || dpid: 0x09, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x00000100 (BE) > > > >
2023-06-18T17:11:49.990961123+00:00 TRACE Zigbee Switch  Found ZigbeeMessageDispatcher handler in zigbee_switch
2023-06-18T17:11:49.992973462+00:00 INFO Zigbee Switch  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2023-06-18T17:11:50.060713649+00:00 INFO Zigbee Switch  <ZigbeeDevice: 1bb21603-e391-4e2a-9a64-96976ef89cdb [0x6CA8] (Coaster hallway)> emitting event: {"component_id":"main","capability_id":"switch","state":{"value":"on"},"attribute_id":"switch"}
2023-06-18T17:11:50.090628599+00:00 DEBUG Virtual Devices V2  vEdge Living Room Presense device thread event handled
2023-06-18T17:11:50.364238002+00:00 TRACE Personal Tuya Devices - main  Found ZigbeeMessageDispatcher handler in personal-tuya-devices -> GenericEF00 -> Model
2023-06-18T17:11:50.486837604+00:00 INFO Personal Tuya Devices - main  Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-06-18T17:11:50.519586304+00:00 WARN Personal Tuya Devices - main  Datapoint not found. Using default	9	datatype	2
2023-06-18T17:11:50.620540422+00:00 DEBUG Zigbee Switch  Coaster hallway device thread event handled
2023-06-18T17:11:50.659655303+00:00 TRACE Zigbee Switch  Received event with handler zigbee
2023-06-18T17:11:50.663689986+00:00 INFO Zigbee Switch  <ZigbeeDevice: 1bb21603-e391-4e2a-9a64-96976ef89cdb [0x6CA8] (Coaster hallway)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6CA8, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xBE, rssi: -81, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0xB4, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2023-06-18T17:11:50.955510157+00:00 TRACE Zigbee Switch  Found ZigbeeMessageDispatcher handler in zigbee_switch
2023-06-18T17:11:51.004849148+00:00 INFO Zigbee Switch  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2023-06-18T17:11:51.022810124+00:00 INFO Zigbee Switch  <ZigbeeDevice: 1bb21603-e391-4e2a-9a64-96976ef89cdb [0x6CA8] (Coaster hallway)> emitting event: {"component_id":"main","capability_id":"switch","state":{"value":"on"},"attribute_id":"switch"}
2023-06-18T17:11:51.084919163+00:00 WARN Personal Tuya Devices - main  Unexpected component for datapoint	9	9	nil	[string "st/device.lua"]:121: attempt to index a nil value (local 'component')	nil
2023-06-18T17:11:51.085807940+00:00 INFO Personal Tuya Devices - main  Datapoint negative.	-9
2023-06-18T17:11:51.087008207+00:00 DEBUG Personal Tuya Devices - main  Presense Sensor Billiard Room device thread event handled
2023-06-18T17:11:51.088198802+00:00 TRACE Personal Tuya Devices - main  Received event with handler zigbee
2023-06-18T17:11:51.152507273+00:00 INFO Personal Tuya Devices - main  <ZigbeeDevice: 540595a6-eea4-450e-9bd1-b65ecd33038d [0xBFFE] (Presense Sensor Billiard Room)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFFE, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xBE, rssi: -82, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x11, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x00CE (BE), < DatapointSegment || dpid: 0x09, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x00000110 (BE) > > > >
2023-06-18T17:11:51.220899786+00:00 DEBUG Zigbee Switch  Coaster hallway device thread event handled
2023-06-18T17:11:51.263368009+00:00 TRACE Zigbee Switch  Received event with handler capability
2023-06-18T17:11:51.313944618+00:00 TRACE Personal Tuya Devices - main  Found ZigbeeMessageDispatcher handler in personal-tuya-devices -> GenericEF00 -> Model
2023-06-18T17:11:51.333769859+00:00 INFO Personal Tuya Devices - main  Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-06-18T17:11:51.353784195+00:00 WARN Personal Tuya Devices - main  Datapoint not found. Using default	9	datatype	2
2023-06-18T17:11:51.541603724+00:00 INFO Zigbee Switch  <ZigbeeDevice: 4dcac771-2df0-414c-b7b1-61759926da8f [0xB587] (Bijkeuken lamp)> received command: {"capability":"switch","component":"main","command":"on","args":{},"positional_args":{}}
2023-06-18T17:11:51.571412621+00:00 TRACE Zigbee Switch  Found CapabilityCommandDispatcher handler in zigbee_switch -> ZLL Dimmer Bulb
2023-06-18T17:11:51.572647238+00:00 INFO Zigbee Switch  <ZigbeeDevice: 4dcac771-2df0-414c-b7b1-61759926da8f [0xB587] (Bijkeuken lamp)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xB587, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On ||  > > >
2023-06-18T17:11:51.661388920+00:00 WARN Personal Tuya Devices - main  Unexpected component for datapoint	9	9	nil	[string "st/device.lua"]:121: attempt to index a nil value (local 'component')	nil
2023-06-18T17:11:51.680134955+00:00 INFO Personal Tuya Devices - main  Datapoint negative.	-9
2023-06-18T17:11:51.698892996+00:00 DEBUG Personal Tuya Devices - main  Presense Sensor Billiard Room device thread event handled
2023-06-18T17:11:51.728545482+00:00 TRACE Personal Tuya Devices - main  Received event with handler zigbee
2023-06-18T17:11:51.751107424+00:00 INFO Personal Tuya Devices - main  <ZigbeeDevice: 6542bb7d-cab0-4dfa-beaa-a5500f3bee8b [0x9EE1] (Presense Sensor Living Room)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x9EE1, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xCE, rssi: -70, body_length: 0x000A, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x7A, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x0020 (BE), < DatapointSegment || dpid: 0x01, DatapointSegmentType: Enum, length: 0x0001 (BE), value: 0x00 > > > >
2023-06-18T17:11:51.791864792+00:00 TRACE Personal Tuya Devices - main  Found ZigbeeMessageDispatcher handler in personal-tuya-devices -> GenericEF00 -> Model
2023-06-18T17:11:51.792727557+00:00 INFO Personal Tuya Devices - main  Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-06-18T17:11:51.840514438+00:00 INFO Personal Tuya Devices - main  Default datapoint	1	0
2023-06-18T17:11:52.052850220+00:00 DEBUG Zigbee Switch  Bijkeuken lamp device thread event handled
2023-06-18T17:11:52.090569737+00:00 TRACE Zigbee Switch  Received event with handler capability
2023-06-18T17:11:52.091855713+00:00 INFO Zigbee Switch  <ZigbeeDevice: 83df0323-f994-4a8b-9575-72d5b4a4c9c4 [0xA867] (Keuken Led Strip)> received command: {"capability":"switch","component":"main","command":"on","args":{},"positional_args":{}}
2023-06-18T17:11:52.110707801+00:00 TRACE Zigbee Switch  Found CapabilityCommandDispatcher handler in zigbee_switch
2023-06-18T17:11:52.217239374+00:00 INFO Personal Tuya Devices - main  <ZigbeeDevice: 6542bb7d-cab0-4dfa-beaa-a5500f3bee8b [0x9EE1] (Presense Sensor Living Room)> emitting event: {"component_id":"main","attribute_id":"presence","state":{"value":"not present"},"capability_id":"presenceSensor"}
2023-06-18T17:11:52.275566856+00:00 DEBUG Zigbee Switch  Keuken Led Strip device thread event handled
2023-06-18T17:11:52.309260361+00:00 DEBUG Zigbee Switch  Bijkeuken lamp device thread event handled
2023-06-18T17:11:52.310585357+00:00 DEBUG Zigbee Switch  driver device thread event handled
2023-06-18T17:11:52.507751557+00:00 INFO Personal Tuya Devices - main  Additional event...	1	1	contactSensor
2023-06-18T17:11:53.059821121+00:00 TRACE Virtual Devices V2  Received event with handler capability
2023-06-18T17:11:53.063513966+00:00 WARN Personal Tuya Devices - main  Attempted to generate event for 6542bb7d-cab0-4dfa-beaa-a5500f3bee8b.main but it does not support capability Contact Sensor
2023-06-18T17:11:53.066142280+00:00 WARN Personal Tuya Devices - main  Unexpected component for datapoint	1	1	nil	false	Attempted to generate event for 6542bb7d-cab0-4dfa-beaa-a5500f3bee8b.main but it does not support capability Contact Sensor
2023-06-18T17:11:53.155253146+00:00 INFO Personal Tuya Devices - main  Datapoint negative.	-1
2023-06-18T17:11:53.184860276+00:00 DEBUG Personal Tuya Devices - main  Presense Sensor Living Room device thread event handled
2023-06-18T17:11:53.186230294+00:00 TRACE Personal Tuya Devices - main  Received event with handler zigbee
2023-06-18T17:11:53.187434562+00:00 INFO Personal Tuya Devices - main  <ZigbeeDevice: d39a5edc-0f4d-44fa-9ad5-f15277ca0605 [0x1903] (Presense Sensor PC Corner)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1903, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xCE, rssi: -46, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x61, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x00E4 (BE), < DatapointSegment || dpid: 0x6D, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x00000000 (BE) > > > >
2023-06-18T17:11:53.232144906+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> received command: {"capability":"switch","args":{},"command":"off","component":"main","positional_args":{}}
2023-06-18T17:11:53.245381521+00:00 TRACE Virtual Devices V2  Found CapabilityCommandDispatcher handler in vedgeDriver
2023-06-18T17:11:53.246680170+00:00 INFO Virtual Devices V2  Virtual switch turned >> off <<
2023-06-18T17:11:53.263339829+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> emitting event: {"component_id":"main","state":{"value":"off"},"attribute_id":"switch","capability_id":"switch"}
2023-06-18T17:11:53.380766180+00:00 TRACE Personal Tuya Devices - main  Found ZigbeeMessageDispatcher handler in personal-tuya-devices -> GenericEF00 -> Model
2023-06-18T17:11:53.425178375+00:00 INFO Personal Tuya Devices - main  Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-06-18T17:11:53.426969937+00:00 WARN Personal Tuya Devices - main  Datapoint not found. Using default	109	datatype	2
2023-06-18T17:11:53.428163867+00:00 INFO Virtual Devices V2  <Device: 5388c003-a5c6-4843-b0e6-ed4a4925ebf8 (vEdge Living Room Presense)> emitting event: {"component_id":"main","state":{"value":"closed"},"attribute_id":"contact","capability_id":"contactSensor"}
2023-06-18T17:11:53.493067636+00:00 DEBUG Virtual Devices V2  vEdge Living Room Presense device thread event handled
2023-06-18T17:11:53.859840598+00:00 WARN Personal Tuya Devices - main  Unexpected component for datapoint	109	109	nil	[string "st/device.lua"]:121: attempt to index a nil value (local 'component')	nil
2023-06-18T17:11:53.874268141+00:00 INFO Personal Tuya Devices - main  Datapoint negative.	-109
2023-06-18T17:11:53.875527437+00:00 DEBUG Personal Tuya Devices - main  Presense Sensor PC Corner device thread event handled
2023-06-18T17:11:53.876730038+00:00 TRACE Personal Tuya Devices - main  Received event with handler zigbee
2023-06-18T17:11:53.929746200+00:00 INFO Personal Tuya Devices - main  <ZigbeeDevice: 540595a6-eea4-450e-9bd1-b65ecd33038d [0xBFFE] (Presense Sensor Billiard Room)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFFE, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0x80, rssi: -89, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x12, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x00CF (BE), < DatapointSegment || dpid: 0x09, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x00000112 (BE) > > > >
2023-06-18T17:11:53.968815391+00:00 INFO Zigbee Switch  <ZigbeeDevice: 4dcac771-2df0-414c-b7b1-61759926da8f [0xB587] (Bijkeuken lamp)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xB587, dest_endpoint: 0x03, profile: 0x0104, cluster: Level >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2023-06-18T17:11:54.110426828+00:00 INFO Zigbee Switch  <ZigbeeDevice: 4dcac771-2df0-414c-b7b1-61759926da8f [0xB587] (Bijkeuken lamp)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xB587, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2023-06-18T17:11:54.121587406+00:00 TRACE Personal Tuya Devices - main  Found ZigbeeMessageDispatcher handler in personal-tuya-devices -> GenericEF00 -> Model
2023-06-18T17:11:54.122913068+00:00 INFO Personal Tuya Devices - main  Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-06-18T17:11:54.141472677+00:00 WARN Personal Tuya Devices - main  Datapoint not found. Using default	9	datatype	2
2023-06-18T17:11:54.146565555+00:00 INFO Zigbee Switch  <ZigbeeDevice: 4dcac771-2df0-414c-b7b1-61759926da8f [0xB587] (Bijkeuken lamp)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xB587, dest_endpoint: 0x03, profile: 0x0104, cluster: ColorControl >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0007 > > >
2023-06-18T17:11:54.218725284+00:00 DEBUG Zigbee Switch  Bijkeuken lamp device thread event handled

The devices in the kitchen are called “keuken” because that’s dutch for kitchen.
Using the search function, i can indeed find that a full 5 seconds passed before the automation was executed here, normally it’s a half second before the automation is executed.

But i can’t seem to find out why it was delayed at that time.

I don’t know why you refer to my drivers in general as possible culprits for your network problems and in the links you are posting there is no device that is using my driver.

You are using these drivers in your logs posted:
- friend Motion from the channel friend
- zigbee switch stock
- personal Tuya Devices: With many WARN logs constantly due to the use of nil index
- Hue Motion sensor
- [YG] driver
- Virtual Devices v2
- Ikea Styrbar Remote

I also see several devices that do not send messages and run health check that use zigbee switch stock and none use a driver of mine.

I also see some very bad rssi intensities.

I do not see in the logs that you have published any errors, nor logs of devices that use a driver of mine

1 Like

I am not talking bad about your drivers, but another user who has issues has your drivers/devices as well. I did not always have issues, so my current suspectation is that a smartthings update may have broken something related to your drivers…But it would be a lot of effort to find out, as i use many, many devices with your drivers.

Ah and you are correct. The current logs show other drivers as i attempted to switch a good amount of them to “smartthings driver for zigbee switch devices” from your “Zigbee switch power MC”.

Again, i don’t mean to attack, i just really want to find the cause of these issues.
And it seems im not alone in these issues.

I will tommorow attempt to remove everything related to your drivers to rule out these can cause this.

EDIT: In all honesty i’m just fiddling around in the end, trying to see what can be the culprit, and ruling out things. when i hear someone else has the same and using your drivers as well, i am getting suspicious of that. I am not a coder.

And if you ask them if they use stock drivers or TAutin drivers, most likely they will also tell you Yes, they use them, because most of us use them.

If you think it’s my drivers that you’re using, which I’m not saying could be your problem, then use others and try to clear up any doubts.

What I do recommend is that you do not change many things at the same time, follow an order, the one you want, change something and let the changes settle before changing more things.
uninstalling and installing devices can affect the network and needs to be rebuilt and is not instantaneous.

Changing driver devices will not always make the devices work well, even if the driver and device are good. I explain:

With the DTH’s, when you changed to another DTH, equivalent to changing the driver, the configuration of the device was carried out always.
With edge the stock drivers and most of the custom drivers that use the default settings do not perform the configuration on the device when you change from one driver to another and can sometimes cause the device to not work as the new driver expects.

If you have doubts about a specific device, it is better in my opinion, to uninstall it and pair it directly with the driver you want.

By the way, in the list of installed drivers, which you posted yesterday, there are some obsolete ones that you shouldn’t use. We are in a beta phase and smartthings changes things in the firmware all the time that might cause old drivers to not work correctly. Keep in mind that even own stock drivers sometimes stop working correctly with own firmware changes

3 Likes

i currently uninstalled a lot of drivers, probably over half, and currently not using any of your (awesome-made i should add) drivers. also uninstalled them to be sure. Hope that might solve things. Also noted another stuck “frient” motion sensor, that kept reporting motion for over 20 minutes now. swapped the drivers to a normal driver as well, and found it switched state into “no motion detected”.

So if things are not working out, i should then re-add them again. can this be done by forcing them into setup and letting smartthings find them again? Or do i really have to uninstall them first?

The Mc drivers, which I consider need a specific configuration when they might come from another driver with an unwanted configuration, force the device to be configured when a driver change is executed.
For example, when a device is changed to the Zigbee Switch Power Mc from another driver, to ensure the correct configuration of the divisors and multipliers.
Also when there are custom temperature report settings.

Now that you have uninstalled drivers, if you are going to use them again then install the latest version.

I hope your problems will be solved soon

Hi, @goosetapo, so, do you mean you send the command in the app 5 seconds before the log of that event appears in the logcat command?

If so, have you checked if it only happens with automation (Routine) or with direct commands in the app? (by direct commands, I mean when you enter the device and click on the “switch” button.

Please, could you publish a screenshot of you routine?
I think could have a logic reason for the delay reponse