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

Why would pulling repeaters enable you to bootstrap back to working, and why did you think to try that?

Just trying to figure out:

(1) what is different about my C-7’s setup that lets my installation work fine on 2.2.4.153, and

(2) an intelligent way for me to proceed if a similar thing happens to me on a future update.

Mine is a fairly simple setup, almost all lights on Hue hub and Lutron Pro hub, less than 20 Z-Wave devices (all plus except for one), and 6 of the devices are Ring V2 repeaters.

1 Like

The Iris 3210-L2's were the only suspect devices I had on my mesh. Removing them was a first step troubleshooting step. Given the large number of devices on my z-wave mesh, coverage is not an issue. Loading .153 after removing the repeaters also let me upgrade without issue. Guess we'll see how it goes from here.

1 Like

So you were using the Z-Wave part of those plugs - I have tried to stay away from doing that - it always seemed so hit or miss. The Zigbee side has been good though.

I ripped both the zigbee and zwave 3210's out. I've never had any issues with the zigbee side but decided to pull them all for the time being.

2 Likes

Same here, I don't have a ton of them (maybe four or five) but I'm only using them for Zigbee repeating.

BTW, 2.2.4.153 has a new URL to reset (wrong -> firmware <- wrong) z-wave stack to the version used by 2.2.4.148 and prior:
/hub/advanced/installZipgateway714

And another one to download 2.2.3 if it's gone from the hub after several 2.2.4 updates:
/hub/advanced/download223

I hope nobody ever needs these... but they're there just in case.

3 Likes

WHAT firmware? I don't remember seeing that there was a firmware update in the release notes? Or did I miss it?

(See below, no mention of any firmware updates)

Release 2.2.4.153 Available

This hot fix includes:

App Features

  • Rule-4.0: Set Boolean variable to another variable.
  • Thermostat Controller: Added optional restrictions.
  • SharpTools: added documentation and video links.

Platform Changes

  • C7: Z-Wave single node repair now works in the new repair GUI.
  • C7: Changed Z-Wave startup order to prevent busy messages.
  • Hub mesh: advertise available devices in pings. WARNING: not fully compatible with earlier hub mesh versions. You must run 2.2.4.153 on both hubs in the mesh or devices will be disabled and will not update.
  • Hub mesh: store all remote device state, attributes, and data in local database.
  • Hub core: revised memory settings.

Bug Fixes

  • C7: Z-Wave stability and performance improvements.
  • C7: Bug fixes for Z-Wave Repair.
  • Mode Manager: Fixed earlier/later of two times bug for daily settings.
  • HSM and HSM Custom Rule: Fix alert set lights to level.
  • Motion and Mode Lighting Apps: Fixed import list for exported rules.
  • AppUI: Adjust min width for 24 time input on desktop view.
  • SharpTools: fixed issue with devices not unsubscribing properly.

Did you mean that that URL is used to set the database to the version used by the prior versions of firmware? I'm a little confused.

Ok, I probably used a wrong word for it. It's the Z-wave stack. It's just another piece of software running on the hub, nothing in that update gets flashed into a chip or anything like that.

Yup. More super secret changes that aren't listed anywhere, just like the magic platform changes.
eye roll

Yes, that is sarcasm, but it is annoying. I'll get over it - your company, your rules, your decision on what to list in release notes.

Z-wave stack should rolls back when a version gets rolled back. But it is a separate executable. If something goes wrong and it doesn't, there's a way to force it to a clean previous version without doing anything more extreme. We can't anticipate all potential issues, but we can provide a plan B once we see someone running into them.

3 Likes

Just to clarify do we think there is a bug with .153 ? I'm on a c5

Got it. Thanks.

Ta, got my threads mixed

1 Like

Slow in upstairs master bath and snappy in basement-the usual offenders, probably because they are most observed, but maybe not.

I have to troubleshoot while the delay is happening...it changes at any time.

So I had the bright idea of trying to pinpoint something or other by turning off breakers and see if that had an effect.

First one I tried was the garage sub panel. That had no effect other than opening up the doors upon power restoration

Second one I tried was for the basement lights. That got things upstairs snappy again. I'm not sure what it's telling me, but maybe I can isolate the problem to some small degree.

Woke up to 8 second delay in upstairs bath and basement. No other automations affected.

Tripped various breakers, including for those involved, outlets as well as lighting, disconnected the usb power to the zooz motions, paused an involved app, modified another involved app, REBOOT, nothing got it off the schneid.

Took down the bathroom contact sensor and removed battery. Basement started working. Reinstalled battery and sensor upstairs; that started working.

I didn't do a lot of exercising (openings and closings) of the door, which usually gets things going, because I wanted to troubleshoot. However, maybe the cumulative effect of my troubleshooting door operations got it going.

I'm also not totally sure of the sequence of battery removal...I'm pretty sure it was just the upstairs bath. It was early.

Next time, and there will be a next time, I'll focus on the sensors.

Also, I ordered 6 zigbee contact sensors at 10 bucks apiece off eBay. There's nothing definitive that Ecolink is to blame, and I do believe things started screwing up after the initial upgrade from 2.2.3, but it's only money. I like the brown plastic on the Ecolink though, and of course the external contacts, which, as I've said before, I use on the high temp alert for my wood burning insert.

I just got mine in .. I’ll let you know.. I’m hoping it’s something we can fix at the driver level and that It’s not doing something crazy.

3 Likes

Me too, lol.

let me know if you find something too. my automations were also not working as you know on 2.2.4 with ecolink contact but also motion..