Bug report: C7 stops working periodically, logs LimitExceededException

🛎️ Get Help
1

Every few months or so, my C7 stops running its timer-driven and trigger-driven routines (Simple Automation Rules). During this time the logs are full of the following LimitExceededException errors. Restarting the device through the web UI restored its functions.

Platform version: 2.3.5.121
Hardware version: Rev C-7

dev:81 2023-06-18 21:18:03.170 error com.hubitat.app.exception.LimitExceededException: Device 81 generates excessive hub load on line 230 (method parse)
dev:81 2023-06-18 21:18:03.162 info Porch Floor 2 West was turned on [physical]
dev:81 2023-06-18 21:18:03.153 error com.hubitat.app.exception.LimitExceededException: Device 81 generates excessive hub load on line 166 (method parse)
dev:81 2023-06-18 21:18:03.145 info Porch Floor 2 West button 1 was pushed
dev:82 2023-06-18 21:17:48.728 error com.hubitat.app.exception.LimitExceededException: Device 82 generates excessive hub load on line 230 (method parse)
dev:82 2023-06-18 21:17:48.720 info Porch Floor 2 East was turned on [physical]
dev:82 2023-06-18 21:17:48.704 error com.hubitat.app.exception.LimitExceededException: Device 82 generates excessive hub load on line 166 (method parse)
dev:82 2023-06-18 21:17:48.689 info Porch Floor 2 East button 1 was pushed
dev:31 2023-06-18 21:16:30.067 error com.hubitat.app.exception.LimitExceededException: App 4 generates excessive hub load on line 57 (method on)
dev:31 2023-06-18 21:16:30.046 info Backyard On was turned on
dev:32 2023-06-18 21:16:21.292 error com.hubitat.app.exception.LimitExceededException: App 4 generates excessive hub load on line 57 (method on)
dev:32 2023-06-18 21:16:21.269 info Porch On was turned on
dev:73 2023-06-18 21:16:18.036 error com.hubitat.app.exception.LimitExceededException: Device 73 generates excessive hub load on line 230 (method parse)
dev:73 2023-06-18 21:16:18.027 info XXX's Room Main was turned on [physical]
dev:73 2023-06-18 21:16:18.019 error com.hubitat.app.exception.LimitExceededException: Device 73 generates excessive hub load on line 166 (method parse)
dev:73 2023-06-18 21:16:18.009 info XXX's Room Main button 1 was pushed
dev:72 2023-06-18 21:15:35.901 error com.hubitat.app.exception.LimitExceededException: Device 72 generates excessive hub load on line 230 (method parse)
dev:72 2023-06-18 21:15:35.893 info Floor 2 Hallway was turned on [physical]
dev:72 2023-06-18 21:15:35.855 error com.hubitat.app.exception.LimitExceededException: Device 72 generates excessive hub load on line 166 (method parse)
dev:72 2023-06-18 21:15:35.846 info Floor 2 Hallway button 1 was pushed
dev:91 2023-06-18 21:15:05.821 error com.hubitat.app.exception.LimitExceededException: Device 91 generates excessive hub load on line 166 (method parse)
dev:91 2023-06-18 21:15:05.821 error com.hubitat.app.exception.LimitExceededException: Device 91 generates excessive hub load on line 230 (method parse)
dev:91 2023-06-18 21:15:05.773 info Floor 2 Stairs was turned on [physical]
dev:91 2023-06-18 21:15:05.769 info Floor 2 Stairs button 1 was pushed
dev:114 2023-06-18 21:00:23.195 error com.hubitat.app.exception.LimitExceededException: Device 114 generates excessive hub load on line 123 (method parseUdp)
dev:113 2023-06-18 21:00:19.262 error com.hubitat.app.exception.LimitExceededException: Device 113 generates excessive hub load on line 123 (method parseUdp)
dev:96 2023-06-18 20:59:51.413 error com.hubitat.app.exception.LimitExceededException: Device 96 generates excessive hub load on line 230 (method parse)
dev:96 2023-06-18 20:59:51.405 info Powder Sink was turned on [physical]
dev:96 2023-06-18 20:59:51.375 error com.hubitat.app.exception.LimitExceededException: Device 96 generates excessive hub load on line 166 (method parse)
dev:96 2023-06-18 20:59:51.365 info Powder Sink button 1 was pushed
dev:95 2023-06-18 20:54:30.365 error com.hubitat.app.exception.LimitExceededException: Device 95 generates excessive hub load on line 166 (method parse)
dev:95 2023-06-18 20:54:30.357 info Powder Main button 2 was pushed
dev:95 2023-06-18 20:53:11.041 error com.hubitat.app.exception.LimitExceededException: Device 95 generates excessive hub load on line 230 (method parse)
dev:95 2023-06-18 20:53:11.033 info Powder Main was turned on [physical]
dev:95 2023-06-18 20:53:10.983 error com.hubitat.app.exception.LimitExceededException: Device 95 generates excessive hub load on line 166 (method parse)
dev:95 2023-06-18 20:53:10.973 info Powder Main button 1 was pushed
dev:113 2023-06-18 20:47:49.184 error com.hubitat.app.exception.LimitExceededException: Device 113 generates excessive hub load on line 123 (method parseUdp)
dev:114 2023-06-18 20:47:49.147 error com.hubitat.app.exception.LimitExceededException: Device 114 generates excessive hub load on line 123 (method parseUdp)
dev:102 2023-06-18 20:47:05.100 error com.hubitat.app.exception.LimitExceededException: Device 102 generates excessive hub load on line 166 (method parse)
dev:102 2023-06-18 20:47:05.100 error com.hubitat.app.exception.LimitExceededException: Device 102 generates excessive hub load on line 230 (method parse)
dev:102 2023-06-18 20:47:05.048 info Kitchen Main button 1 was pushed
dev:102 2023-06-18 20:47:05.047 info Kitchen Main was turned on [physical]
app:10 2023-06-18 20:24:00.134 error com.hubitat.app.exception.LimitExceededException: App 10 generates excessive hub load on line 730 (method doAction)
app:10 2023-06-18 20:24:00.123 info Porch Timer Turn On
app:26 2023-06-18 20:19:00.147 error com.hubitat.app.exception.LimitExceededException: App 26 generates excessive hub load on line 730 (method doAction)
app:26 2023-06-18 20:19:00.063 info Backyard Timer Turn On
dev:107 2023-06-18 17:30:42.808 error com.hubitat.app.exception.LimitExceededException: Device 107 generates excessive hub load on line 188 (method parse)
dev:95 2023-06-18 17:14:33.518 error com.hubitat.app.exception.LimitExceededException: Device 95 generates excessive hub load on line 166 (method parse)
dev:95 2023-06-18 17:14:33.508 info Powder Main button 2 was pushed
dev:95 2023-06-18 17:13:18.807 error com.hubitat.app.exception.LimitExceededException: Device 95 generates excessive hub load on line 166 (method parse)
dev:95 2023-06-18 17:13:18.807 error com.hubitat.app.exception.LimitExceededException: Device 95 generates excessive hub load on line 230 (method parse)
dev:95 2023-06-18 17:13:18.759 info Powder Main was turned on [physical]
dev:95 2023-06-18 17:13:18.752 info Powder Main button 1 was pushed
dev:109 2023-06-18 16:35:03.797 error com.hubitat.app.exception.LimitExceededException: Device 109 generates excessive hub load on line 188 (method parse)
dev:73 2023-06-18 14:07:14.440 error com.hubitat.app.exception.LimitExceededException: Device 73 generates excessive hub load on line 166 (method parse)
dev:73 2023-06-18 14:07:14.397 info XXX's Room Main button 2 was pushed
dev:73 2023-06-18 13:59:56.906 error com.hubitat.app.exception.LimitExceededException: Device 73 generates excessive hub load on line 230 (method parse)
dev:73 2023-06-18 13:59:56.898 info XXX's Room Main was turned on [physical]
dev:73 2023-06-18 13:59:56.883 error com.hubitat.app.exception.LimitExceededException: Device 73 generates excessive hub load on line 166 (method parse)
dev:73 2023-06-18 13:59:56.872 info XXX's Room Main button 1 was pushed
dev:105 2023-06-18 13:47:39.758 error com.hubitat.app.exception.LimitExceededException: Device 105 generates excessive hub load on line 166 (method parse)
dev:105 2023-06-18 13:47:39.694 info Kitchen Counter button 2 was pushed
dev:108 2023-06-18 12:44:38.413 error com.hubitat.app.exception.LimitExceededException: Device 108 generates excessive hub load on line 188 (method parse)
dev:100 2023-06-18 12:04:14.130 error com.hubitat.app.exception.LimitExceededException: Device 100 generates excessive hub load on line 230 (method parse)
dev:100 2023-06-18 12:04:14.081 info Dining Room Table was turned on [digital]
dev:73 2023-06-18 11:11:07.431 error com.hubitat.app.exception.LimitExceededException: Device 73 generates excessive hub load on line 166 (method parse)
dev:73 2023-06-18 11:11:07.391 info XXX's Room Main button 2 was pushed
dev:73 2023-06-18 11:01:28.112 error com.hubitat.app.exception.LimitExceededException: Device 73 generates excessive hub load on line 230 (method parse)
dev:73 2023-06-18 11:01:28.112 error com.hubitat.app.exception.LimitExceededException: Device 73 generates excessive hub load on line 166 (method parse)
dev:73 2023-06-18 11:01:28.071 info XXX's Room Main was turned on [physical]
dev:73 2023-06-18 11:01:28.059 info XXX's Room Main button 1 was pushed
dev:105 2023-06-18 10:25:24.295 error com.hubitat.app.exception.LimitExceededException: Device 105 generates excessive hub load on line 230 (method parse)
dev:105 2023-06-18 10:25:24.285 info Kitchen Counter was turned on [physical]
dev:105 2023-06-18 10:25:23.576 error com.hubitat.app.exception.LimitExceededException: Device 105 generates excessive hub load on line 166 (method parse)
dev:105 2023-06-18 10:25:23.536 info Kitchen Counter button 1 was pushed
dev:100 2023-06-18 10:07:55.191 error com.hubitat.app.exception.LimitExceededException: Device 100 generates excessive hub load on line 230 (method parse)
dev:100 2023-06-18 10:07:55.180 info Dining Room Table was turned on [physical]
dev:100 2023-06-18 10:07:55.149 error com.hubitat.app.exception.LimitExceededException: Device 100 generates excessive hub load on line 166 (method parse)
dev:100 2023-06-18 10:07:55.135 info Dining Room Table button 1 was pushed
dev:109 2023-06-18 10:06:55.959 error com.hubitat.app.exception.LimitExceededException: Device 109 generates excessive hub load on line 188 (method parse)
2

Are these wifi based devices?

3

The hub is wired, most of the devices use z-wave. The logs seem to indicate a hub load issue related to (message?) parsing. Given that this happens infrequently and there's no clear trigger event, this smells like slow resource growth over time? I'm not sure how to further diagnose resource issues like memory pressure on this device.

4

I am getting the same issue here since this morning. Very weird.
I am restarting the hub. If it happens again, I will update the software, but just checking if it is some sort of building up, and I can reproduce it before the update. @martijneken look like we have the same platform version.

Also, this happens to me in physical and virtual devices. Basically every device (I believe) throws this exception on refresh.

Platform Version
2.3.5.121

Hardware Version
Rev C-7

5

Wow.... So many bug fixes and addons since then...

1 Like
6

Hm, it's only 3 months old (Mar 27) and I don't see anything super relevant in the release notes since then. But I've updated to 2.3.5.146 and I'll report if it happens again.

2 Likes
7

I have the latest update, and my hub is inaccessible every three days. I have to unplug and replug. Not the best for the hub. I have several similar errors after I reboot on a variety of devices.

dev:62023-07-06 06:28:47.771 PMerrorcom.hubitat.app.exception.LimitExceededException: Device 6 generates excessive hub load

Platform Version
2.3.5.152

8

I have 2.3.5.152 now, and another symptom of overload-after-time (other than actions not working) is that the system claims every active device generates excessive load (logs below).

I can see when these messages started, but there wasn't a clear trigger in the log. Just a physical press on a lightswitch.

Months elapsed between these events, so it's going to be pretty hard to track down. At this point I've scheduled a weekly Hubitat restart to hopefully work around it, so you may not see more reports from me :-/

If I do see it again I'll report back here.

dev:109 2023-09-16 13:02:15.205 warn Device 109 generates excessive hub load
dev:109 2023-09-16 13:02:15.201 warn Device 109 generates excessive hub load
dev:109 2023-09-16 13:02:15.198 warn Device 109 generates excessive hub load
dev:108 2023-09-16 13:01:07.636 warn Device 108 generates excessive hub load
dev:108 2023-09-16 13:01:07.627 warn Device 108 generates excessive hub load
dev:107 2023-09-16 13:00:01.997 warn Device 107 generates excessive hub load
dev:107 2023-09-16 13:00:01.989 warn Device 107 generates excessive hub load
dev:101 2023-09-16 10:38:37.073 warn Device 101 generates excessive hub load
dev:101 2023-09-16 10:38:37.071 info Kitchen Island was turned off [physical]
dev:101 2023-09-16 10:38:36.809 warn Device 101 generates excessive hub load
dev:101 2023-09-16 10:38:36.807 info Kitchen Island button 2 was pushed
dev:102 2023-09-16 10:38:36.579 warn Device 102 generates excessive hub load
dev:102 2023-09-16 10:38:36.578 warn Device 102 generates excessive hub load
dev:102 2023-09-16 10:38:36.577 info Kitchen Main was turned off [physical]
dev:102 2023-09-16 10:38:36.566 info Kitchen Main button 2 was pushed
dev:108 2023-09-16 09:41:55.613 warn Device 108 generates excessive hub load
dev:105 2023-09-16 09:31:24.426 warn Device 105 generates excessive hub load
dev:105 2023-09-16 09:31:24.424 info Kitchen Counter was turned on [physical]
dev:105 2023-09-16 09:31:23.565 warn Device 105 generates excessive hub load
9

what is device 105 and 108?

1 Like
10

And do you have any of those devices in any automations where they might be trying to turn on and off repeatedly due to something like a misconfigured rule?

It is odd that you have multiple devices saying this, it is likely to be you have all the same device brand/type and that device is overly chatty, that you are doing something to the configurations of these devices like power reporting settings to make them "noisy", or these devices have rules/automations that are all very similar to each other.

11

It's not only device 105 or 108 -- those are UltraPro (Jasco) Z-Wave switches. This was just an example snippet of logs. Once this triggers, every active device on my network shows the same logs.

I'm skeptical about that, since the issue only manifests after weeks if not months of uptime. Also, going by the "Device stats" and "App stats" pages, no device/app uses >0.1% "of total" (is that CPU or wall time?). I just rebooted though, so I can take another look in a few days.

I'm guessing the most intensive thing we do is invoke Google Home automations (by voice command) that configure 5 or so devices in quick succession.

If it helps, a quick rundown of my setup:

Devices

  • 50 Jasco z-wave switches + dimmers
  • 3 Sinope TH1300ZB thermostats
  • 2 Kasa Plug switches
  • 1 GE outdoor z-wave switch

Apps

  • Google Home integration
  • Kasa integration
  • 5 Scene-1.2 groups used by rules below
  • 4 Simple Automation Rules based on time of day
  • 4 Simple Automation Rules based on trigger + delay
12

Can you post your z-wave details page?

1 Like
13

@martijneken Did you ever get this figured out? I've got just shy of 30 of the Zooz Zen15 devices and they're all configured to report on a change of 5w or 15 seconds, which seems to be fine... most of the time, but sometimes it just goes nuts and the log is filled with "generates excessive hub load" messages. I use the InfluxDB app to send stuff to grafana, but even with the app disabled, I'm still getting probably 5 or 6 of the load messages every 1 or 2 seconds (so, a lot - a "metric sh*tton" to be precise").

This setup is in place purely to monitor power (I don't have access to the room with the breakers so when we accidentally trip one, facilities has to come out and reset it, which is a hassle). There's only a small handful of mostly unused apps (I could probably ditch the dashboard and rule machine entirely but I don't think it would change anything.)

For what it's worth, ironically, the Zooz switches I'm using right now I'm using because they gave me less trouble than the other two devices I had tried. The whole setup is in a lab where there's almost certainly an excessive amount of noise (which includes audible noise...). I couldn't get zigbee to work reliably which was unfortunate, but I attributed that to most likely being a lot of noise in that frequency range, but all things considered, it's probably all over the spectrum and I don't have the background to be able to get real data on that noise.

I'm currently running 2.3.8.118 (with a pending update to 119 that I'll probably kick off shortly - though I don't expect it to fix anything).

14

to monitor failure do you really need 5w change.. that seems excessive. if you set it to liek 20 w i imagine your problems will go away. also 15 sec.. if a machine is down for a minute i would think that would suffice.

15

Agreed, the very frequent reporting is probably causing the problems. 30 devices reporting at a minimum every 15 seconds is at least 2 messages a second, non stop, all the time, 24/7.

16

Well, not everything fluctuates by that much, but some do have a wider range now that I'm thinking about it - closer to 15-20w. As for 15 seconds, that's actually up from what it used to be, but it was fine with the current settings, right till it wasn't. That said, the host that the db sits on has gone down a few times in the last day or so because of some re-wiring in the lab.

I think I've got it working for the moment - followed this post and split the devices across 3 instances and I'm not seeing any errors. For a couple of devices I've used (and now beaten with a hammer), regardless of what things were set to, it would just report wildly inaccurate numbers constantly - didn't matter what I had it set to report. It was flooding the z-wave network - no idea what the max capacity is, but it can't have been good...

We'll see what tomorrow brings... lol