Does Sensibo have a polling interval setting by any chance? If yes, setting it higher may help.
If C3 is still around (I can't ping it from the support tool), try offloading the app on it. The AC device can be shared in hub mesh if there are C7 specific automations that use it.
Three of your apps are ones that have caused issues on a hub that I maintain - Sensibo, Echo Speaks and Lifx Master.
Make sure you’re running the latest versions of Echo Speaks and LiFX Master. And that none of your LiFX devices are powered off.
I do have a C-3 which I could possibly move Sensibo over to. I'll have to look into updating the other two.
Are you running any zooz stuff? Any ghosts? (this may have been addressed in your last ticket so me asking may be redundant)
I have the Zooz dual outlet (ZEN25?). I don't think I have any other Zooz devices currently connected.
FYI ...
3 Likes
Yes, that was months ago and I took all of those steps.
It locked up again - interestingly, the hub web interface is accessible but no devices are working and logging stopped about 4 hours ago - the last entries are shown below. Device 28 is Lutron Telnet, 127 is a Zwave plug, 128 is a Zwave plug, 147 is a Zwave plug, and 146 is a Zwave plug. Hmmmmmm......
dev:282021-06-09 03:32:48.593 pm inforcvd: DEVICE,13,3,3
dev:1272021-06-09 03:00:21.529 pm debugMeterReport(meterType: 1, precision: 3, scale: 0, size: 4, meterValue: [0, 0, 65, 239], rateType: 1, deltaTime: 10, previousMeterValue: [0, 0, 65, 239])
dev:1272021-06-09 03:00:21.526 pm debugparse:zw device: 0D, command: 3202, payload: 21 64 00 00 41 EF 00 0A 00 00 41 EF , isMulticast: false
dev:1282021-06-09 03:00:19.703 pm debugSensorMultilevelReport(precision:3, scale:0, sensorType:4, sensorValue:[0, 8, 44, 22], size:4, scaledSensorValue:535.574)
dev:1282021-06-09 03:00:19.700 pm debugparse:zw device: 0E, command: 3105, payload: 04 64 00 08 2C 16 , isMulticast: false
dev:1282021-06-09 03:00:19.444 pm debugMeterReport(meterType: 1, precision: 3, scale: 0, size: 4, meterValue: [0, 1, 68, 14], rateType: 1, deltaTime: 10, previousMeterValue: [0, 1, 68, 14])
dev:1282021-06-09 03:00:19.440 pm debugparse:zw device: 0E, command: 3202, payload: 21 64 00 01 44 0E 00 0A 00 01 44 0E , isMulticast: false
dev:1472021-06-09 03:00:17.297 pm debugSensorMultilevelReport(precision:3, scale:0, sensorType:4, sensorValue:[0, 0, 0, 0], size:4, scaledSensorValue:0.000)
dev:1472021-06-09 03:00:17.294 pm debugparse:zw device: 12, command: 3105, payload: 04 64 00 00 00 00 , isMulticast: false
dev:1472021-06-09 03:00:17.203 pm debugMeterReport(meterType: 1, precision: 3, scale: 0, size: 4, meterValue: [0, 0, 47, 109], rateType: 1, deltaTime: 10, previousMeterValue: [0, 0, 47, 109])
dev:1472021-06-09 03:00:17.199 pm debugparse:zw device: 12, command: 3202, payload: 21 64 00 00 2F 6D 00 0A 00 00 2F 6D , isMulticast: false
dev:1462021-06-09 03:00:14.503 pm debugSensorMultilevelReport(precision:3, scale:0, sensorType:4, sensorValue:[0, 0, 0, 0], size:4, scaledSensorValue:0.000)
The Zwave plugs are the older Aeotec DSC06106 models and have worked great all this time. Maybe I should start moving them over to the cheap Centralite Zigbee ones? I tried accessing Runtime stats but it times out - going to need to reboot.
It looks like the default refresh interval is 1 minute for Sensibo. I just brought my C-3 back online, updated it, and just added the Sensibo integration. From what I remember, the Sensibo integration always acted kind of weird on the C-3. Anyway, I have a webcore piston which controls Sensibo on my C-7 based on the temp of a Konke Temp and Humidity sensor in my office. It has been super rock solid and stable.
I upgraded Echo Speaks (also removed it as an active app, since I am not currently using it) and Lifx. Let's see what happens and if the lockups continue, Sensibo is the next step.
1 Like
So far, so good - did notice one issue with some of my automated lights but I'm guessing that it is a low battery on the door sensor which trips it.
Check the events tab on the device page for that sensor. It'll tell you whether the sensor registered an event or not. If it did register an event, we'll have to figure out why the automation didn't get triggered.
It hasn't registered an event in about 4 hours - it's on the door into my garage and my wife and I left AND came back within the last 90 minutes. The light on the sensor is working when it's triggered but it seems to be having issues talking to Hubitat. I may try a battery swap tomorrow if it continues and see if that fixes it. Automations on those particular lights are working because they're also tied to my garage doors and when I opened my garage door, they came on as expected.
Locked up hard again this morning.
At the last 3 lockups, I've looked at the logs and almost every time, it locks up after talking to several of the Aeotec DSC06106. I'm hesitant to remove Sensibo at this stage because it works so well. I guess I can try creating a local backup and restoring it and see if that helps. I'm also wondering if I should start replacing the old Aeotec plugs.
Those are old Zwave, not plus. Are you polling them? Do you have energy monitoring turned on for these?
1 Like
They're at the default settings, whatever those may be. They do monitor energy. Yes, I know they're old Zwave but they've worked fine across 3 platforms now and have been fine on Hubitat.
Turn off all energy monitoring and see if you still are getting crashes.
That could be very bad depending upon what defaults are. While I don't have these plugs, many of these Zwave plugs do power, voltage, current, percentage of change, and so on. So you potentially get 5-6 power reports every couple seconds bombarding the hub and the Zwave mesh. Multiply that by "several" that you have, and no wonder the hub is brought to it's knees.
It doesn't appear to let me disable reporting. However, I can set the report interval very high - it's currently set to 10 seconds.
@agnes.zooz Have there been any updates to the Zen 25 firmware beyond 2.0 ? If so, can that be posted here.
