If you can put some log of what the controller is doing and be able to analyze what happens?
I don’t know what could be happening
(EDGE Driver-Mc): Zigbee Temp Sensor and Child Thermostat Mc, Zigbee Temp Sensor with Thermostat Mc
If you can put some log of what the controller is doing and be able to analyze what happens?
i applied your zigbee temp sensor for all my aqara temp sensors today. Most of them seem to go offline after a certain amount of time? except the one that i set as zigbee temp with thermostat that is still online. since most of them went offline it doesnt seem like an individual error. Changed batteries for some of them while readding them to the hub.
It is very important that they are configured correctly in the installation so that they send the reports regularly.
If one is far from the hub, it is convenient to bring it closer during installation.
if they are configured correctly and the zigbee network is fine, they do not have to stay offline
What settings should I change to make this happen then?
You do not have to change anything if you do not consider it necessary.
If you have not changed anything, it is configured with the default values.
I was referring to the configuration process that is always carried out when installing a device.
In this process, be configured the reports sent to hub for the attributes of the different capabilities of the device, temperature, humidity, battery…
This process is no longer repeated after pairing is complete.
In this why it is important that the device correctly receive the configuration messages and reply with the result of the configuration.
And that’s also why manufacturers recommend placing the device near the hub during installation.
The hub software and driver monitor the attributes of the device and decide whether it is online or offline.
The custom temperature and humidity settings that the driver has in preferences can be changed at any time, but not all devices accept configuration changes with the same ease, for example, Smartthings (Samjin), accept them very well.
The Sonoff TH01 does not always accept them, what I do is:
- put it near the hub or have a good connection with repeaters
- repeat the change more times if it has not been successful the first time
- check the response of the SUCCESS device with the CLI.
In this example change the temperature max interval report from 60 min to 61 minutes
(In bold type are the data to check)
2022-02-21T10:34:45.244455818+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 9ea4a325-0393-4760-9059-d2cd06f47250 [0x4AC3] (Sensor Mov-3)> received lifecycle event: infoChanged
2022-02-21T10:34:45.260816485+00:00 TRACE Zigbee Motion Sensor Mc Found DeviceLifecycleDispatcher handler in zigbee-motion
2022-02-21T10:34:45.299889151+00:00 PRINT Zigbee Motion Sensor Mc Manufacturer, Model Samjin motion
2022-02-21T10:34:45.306143151+00:00 PRINT Zigbee Motion Sensor Mc device.preferences[infoChanged]= preferences: version
2022-02-21T10:34:45.312524818+00:00 PRINT Zigbee Motion Sensor Mc device.preferences[infoChanged]= 61 preferences: maxTime
2022-02-21T10:34:45.318761818+00:00 PRINT Zigbee Motion Sensor Mc << Preference changed: name, old, new >> maxTime 60 61
2022-02-21T10:34:45.325205485+00:00 PRINT Zigbee Motion Sensor Mc maxTime y changeRep: 3660 100
2022-02-21T10:34:45.340576818+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 9ea4a325-0393-4760-9059-d2cd06f47250 [0x4AC3] (Sensor Mov-3)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4AC3, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 286D9700010D37F8, src_endpoint: 0x01, cluster: TemperatureMeasurement, dest_addr_mode: 0x03, dest_address: 286D97000204B680, dest_endpoint: 0x01 > > >
2022-02-21T10:34:45.355231818+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 9ea4a325-0393-4760-9059-d2cd06f47250 [0x4AC3] (Sensor Mov-3)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4AC3, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Int16, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x0E4C, reportable_change: 100 > > >
2022-02-21T10:34:49.254232487+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2022-02-21T10:34:49.277412153+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 9ea4a325-0393-4760-9059-d2cd06f47250 [0x4AC3] (Sensor Mov-3)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4AC3, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xFF, rssi: -30, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x36 >, < BindRequestResponse || status: 0x00 > > >
2022-02-21T10:34:49.298117820+00:00 DEBUG Zigbee Motion Sensor Mc Sensor Mov-3 device thread event handled
2022-02-21T10:34:49.304167487+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2022-02-21T10:34:49.320245153+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 9ea4a325-0393-4760-9059-d2cd06f47250 [0x4AC3] (Sensor Mov-3)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4AC3, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, lqi: 0xFF, rssi: -30, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x2E, ZCLCommandId: 0x07 >, < ConfigureReportingReponse || ZclStatus: SUCCESS > > >
Ah I see. Yes I did sync them in their rooms not close to the hub. I’ll try moving them all closer. Thx.
I noticed though that the temp thermostat one isn’t disconnecting and it’s one of the further away ones so that driver seems to keep its connection better then the one without thermostat.
Both drivers use the same default settings at installation.
The difference may be that although it is further away, it connects to the hub through a repeater with a good signal.
in the my device example, is very far, about 10 m and different floor, but connect with a repeater and the signal recived is very good:
lqi: 0xFF, rssi: -30,
Install them slowly, give the device time to receive the messages, configure itself and answer.
In the App the process seems very fast, but the real process requires time, messages sent, received, processing and executing, …
Just a quick Q…anyone having any issues…my 4 devices using this driver disconnected last night at the same time and so far are not reconnecting.All other ZigBee devices are ok.
Just B4 I start fiddling about!
With these drivers it is so fast to delete and reconnect them…that solved it!
Last night I made a small update to print in logcat the hub memory used by the controller.
Maybe when the update was installed something went wrong, it shouldn’t, but sometimes it does.
We are in Beta phase, to see if it is solved.
I was having issues , but with zigbee switch mc driver, a reboot of the hub fixed it.
I don’t know what the Hub does when it updates the drivers, I try not to look at the IDE for things that have to do with Edge drivers, since they don’t make much sense and I can’t interpret them.
Yesterday I updated all the my drivers to add the print in the logcat of the hub memory used by the driver.
This impression is made when executing an infochanged lifecycle, that is, changing some preference, installation…
2022-03-31T09:41:30.719475641+00:00 PRINT Zigbee Light Multifunction Mc Device ID <ZigbeeDevice: 84944c69-fa8e-417e-bb62-92b7d5087d63 [0x1786] (Luz Mesita)> 2022-03-31T09:41:30.725277974+00:00 PRINT Zigbee Light Multifunction Mc Manufacturer >>> OSRAM Manufacturer_Len >>> 5 2022-03-31T09:41:30.731149641+00:00 PRINT Zigbee Light Multifunction Mc Model >>> Classic A60 W clear - LIGHTIFY Model_len >>> 30 2022-03-31T09:41:30.737341641+00:00 PRINT Zigbee Light Multifunction Mc Memory >>>>>>> 1184.23046875 Kbytes
I also updated all my drivers at same time and before of publish these in shared channel. Nothing strange happened in any of them.
Nothing should happen when updating the drivers automatically, if something goes wrong, the beta phase is the time to come out and fix it.
The ZigBee part of my system crashed about 1AM EDST this morning. 100% of my ZigBee devices, most of my Z-wave devices, and 1 WiFi device use Edge Drivers.
A 120v AC siren connected to an eWeLink ZigBee relay briefly sounded at 1AM. When I went into app to see what happened everything was off line.
Part of the problem was my router was connected to an eWeLink ZigBee plug, so my router also went off line. I have since removed that plug.
When I got my WiFi back up and rebooted the ST hub most of my ZigBee stuff was off line.
The AC powered Sonoff & eWeLink stuff was easy to bring back up. I just ran scan nearby and they reconnected. My Ikea and Tuya stuff had to be manually put into pairing mode and running scan nearby brought them back on line.
My battery powered Sonoff sensor which are fussy had to be manually paired.
My ST system is back to normal, but my wife was not happy to be woken up at 1AM.
Only the devices with Mc drivers were left disconnected?
Mariano something similar happened to me. All zigbee plugs and lights that are using your drivers, crashed, and got disconnected. Some of them came back with Network error, but some are no longer connected to the hub. It happened yesterday after noon. I didn’t noticed when happened, as most of the lights were off at that time, however, my 3 monitors that are connected to the smart plug went off, as I was working. I had to manually turn the plug On, as it has physical switch. Some of the lights became uncontrollable from the app. I had to turn them on and off from the switch. Some become responsive, but some lost connection to the hub, even that are exactly the same model. That is why i checked hub activities, and seen that on/off command going every 5 minutes
Yes, all the devices that had to be repaired were using Mc drivers.
The AC powered Sonoff & eWeLink ZigBee devices are nice because they automatically going into pairing mode when there is an upset.
Yes I have eWeLink plugs, and they all went to pairing mode
3 posts were split to a new topic: [SmartThings Edge] Issue after several drivers updates