[2.2.4.139] Woke up to Slowwwww world - delays & non-responsive

At least yours wakes up :stuck_out_tongue: mine just stopped entirely. Another datapoint if it helps anyone is I’m using a C4.

I skipped from .145 to .148 and see this in the .147 release notes:

Hub core: revised memory settings for C4 hubs.

I wonder what that entailed and if it’s at all related.

After restoring, just experience a 20 second wait for the basement lights to go on.
image

Walling off the basement seems to be the only logical step at this point.

4 Likes

I probably focus on that automation since it's just a few steps from the couch.

1 Like

OK, question -- do you have zwave devices and automations that work reliably, all of the time?

S.

2 Likes

I'm gonna say no. It's not like it's all contact sensors...even motion is affected.

However, one closet does have a motion detector directly associated with a switch for a light. I also have a couple of directly associated switches in the basement for 3-way purpose. They are reliable.

I'd like to make some of those Ecolink sensors directly associated as well, but haven't found a way.

OK. Hmmm.

Do you have a basic time based automation, or any automations you run on a schedule? Just curious really, I think if we could isolate a case that works it might point us to why the others don't. Personally, I've experienced specific rules (Motion lighting with some of the built in conditionjs) that I could never get to to work, but I have other automations that work first time, every time.

So try to automate a simple light switch (zwave or zigbee) or plug to come on and go off on a set (periodic) schedule, and see what happens.

S

I have a floor lamp plugged into a switched outlet that comes on at sundown. I haven't noticed screwing up except around the daylight saving time switch, as I recall. As I've said, these rules work: you just have to wait for them....sometimes.

I would submit that you have a chatty device or several that are spamming the hub. How do your logs look while the hub is running?

1 Like

+1

Did you ever do that hub statistics that I posted in one of your other threads? That might point to a specific app or device that is causing problems.

1 Like

I found three links: enable, disable, and report. It didn't seem like it provided anything useful. I might have not let it run long enough or I had the wrong links:

I do have a presence sensor that reports in every 20 seconds.

I'm going to look into this more:

You should end up with a huge list of app numbers, times, and so on.

So you enabled, let run for 5 minutes or more, then went to stats and it was blank?

Here is stats before enabling.

stat

Here is after I enabled.

stats1

Here is after running for a minute, and hitting browser refresh button.

Do you not get something like this?

running now...

This is what I got after five minutes:
image

So what are device 175 and 147?

You can either browse your devices, or go to (your hub's IP)/device/edit/175 or /device/edit/147

You also may want to let this run for a while and see if anything slows or shows changes over time. I wouldn't let it run continuously, but I don't think letting it go for maybe an hour will hurt.

How do you track down the device and app ids? The links in @lewis.heidrick 's post don't work.

They are both ST presence sensors which report in every 20 seconds.
I'll try to run it when things slow down.

The AppID is similar, (your hub's IP)/installedapp/configure/(insert app number here)/mainPage

1 Like