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

It made a big difference in speed on that automation. In its heyday there would be a little lag between one string of lights turning on and another. Almost no lag now. (now being the operative word)

Slowwww again this morning. 15 seconds. It was real sharp and snappy at 12:30am, and slowwww at 7:30am.

Still snappy from dashboard.

It's at 145. I redid several other automations. Revisited EVERY automation and hit "done". Visited many devices and did the same. Shut down, pulled power, restarted.

Do I have to stay awake all night, opening doors, to find the exact time where things slow down? Maybe I'll pull the lan cord tonight. Something's going on overnight, and I don't think it's me.

This is starting to piss me off.

19 seconds:
image

15 seconds:

I lied. I went to bed after 1:30, because here is the real snappy response from the same automation last night:

Does it slow down after nightly maintenance I wonder?

7 seconds:
image

The ones above that I pasted are now running normally.

Followed all the recommended steps. All devices have been reading « ok » and a few of the routes cleaned up a bit, but performance is still unusable. After one or two automations or scene activations, the hub totally chokes. Seems to be very similar to what @velvetfoot is dealing with.

I’m rolling-back to 2.2.3 :confused: Although z-wave performance was lacklustre, it was still semi-usable. Regrettably each public 2.2.4 build has been super problematic on my system.

Odd...maybe @gopher.ny can look at your logs, @rjlynch and @velvetfoot. When my hub was cratering Victor found some issues related to the Chromecast integration by looking at more detailed logs on his end, that I would not have been able to see. Maybe that could help w/your problems.

Speaking of Chromecast integration, I've searched in the forums and couldn't find any reference from staff about this.
I see that many people use the Chromecast helper by bptworld to keep the devices alive. What's annoying is that it generates 2 log entries per device per refresh, which, if you have lots of devices, can really crowd your logs.
Turning off debug logging doesn't stop the initialize messages.
Any thoughts?

I'd ask him directly on the release thread he created for his helper app.

Thanks, but it's not his app, it's the actual chromecast drivers that generate the logs

Ah, sorry, the way I read your post it sounded like the helper app was generating the log entries.

@gopher.ny is also probably the guy to ask for that. :slight_smile:

Late night again.
Working with @bobbyD in support.
Did soft reset and restore from backup. I understand Hubitat "sanitizes" backups...
Lost 12 devices, as in listed on z-wave details with no device name; do not appear on device list.
Lost 18 apps. When I say lost, I mean I can't get into them to edit for say, a missing device. Do I really remember what I did?
edit: Oh, and I lost ALL the zigbee devices.

OUCH!

Did you try just the one backup file? I always create a new one as backup, but you should have a couple of recent ones to choose from. Maybe a different one will have the missing stuff?

I was going back and forth on revisions, so I think there was only the one I used.
Maybe it's for the best, as far as building a better mesh.
But, I think the apps are going to a downer-no apparent recovery, not even printed documentation. Only the title simple auto gives to the app, and my imperfect memory.
Hey, but maybe they will also emerge better and stronger, lol.

1 Like

Well, I spent the last couple of days excluding and including devices. Have 3 Utilitech water sensors to go.

So, tonight I slowly started to add automations back in. 3 simple rules, 3 machine rules, a couple of notifications, and the zooz garage app.

Things were going really quick a little earlier.

Just now, I open the basement door, and.... 10 seconds before the lights turn on.

I'm fed up at this point. When I think of the money I wasted on all those devices...

edit: I'm gonna delete apps until I get to just the one.
Deleted the Zooz garage door app. That sped things up. Gotta get some sleep.

I think I would be too. But this isn't normal. Something is sure causing you issues. :frowning_face:

@velvetfoot, for sure man, I’d be fed up too.
Just a thought though ... you’re not doing too much pairing, too quickly eh ?
Since I got a Zwave stick and started Zniffing, I’ve been able to actually SEE how much chatter and communication is going on and it’s way more than I thought. Messages are being sent by Hub and Devices when I figured there was none and I convinced I used to make changes too quickly and screwed things up. Probably both Hub and Devices not getting complete messages etc.
So it caused me to “let things be” for a few hours after pairing 3-4 devices.
It sounds terribly time consuming but I limited pairing Zwave devices to no more than 6-8 per day. Zigbee seems more resilient (IMHO) and I’ve been able to add 12 devices at once.
I broke the installation down into zones and made sure that each zone was communicating and working before adding another.
Garage was first. Simple lighting and door.
Once that was sorted, I did just the light control (switches and sensors) in 2 x gnd floor bedrooms. Etc.
Zwave - you Must pair some repeater devices first and work outwards. then grab a couple of beers and come back to it tomorrow.
Also I’ve found in-wall repeaters like Fibaro do not have great range due to building materials muting the radio signals.
My external Zigbee repeaters have WAY more range.
Sorry there’s no magic wand but slow, steady and methodically worked for me.
All the best

2 Likes

I followed the guidelines.

All devices are at 100kbps, except for the water sensors and a contact at 40.

1 Like

I added 2 Ring Extenders last week to shore up a couple weak points in my mesh and it took a little over 72 hours for the routes to renegotiate completely.