Upset users more likely to post- Please take poll to indicate IF issues with the latest update 2.2.3

Rxich · August 15, 2020, 1:20am

I guess that's possible too. But you know the routine, people more likely to post about a problem, in general.
I made the title a little "click-baitey" to hopefully get more responses, and a more balanced reply pool, not consisting of only people with issues

danabw · August 15, 2020, 2:06am

So you're saying I have "issues?!" Well let me tell you...

danabw · August 15, 2020, 2:07am

There is no 12 Step program equipped to combat that.

michael.l.nelson · August 15, 2020, 3:24am

Issues? I have a subscription!

Rxich · August 15, 2020, 4:44pm

Ok folks, it's seems clear to me that most had no problem. I'll leave the pool up for the rest of the day, c'mon over and take a swim, er uh I meant poll, and will be closing it later tonight.

This is what I had hoped to see, as I know how easy it is for negative sentiment to take over, just look at our epidemic of TDS.

marktheknife · August 15, 2020, 4:48pm

I’m not really sure that a convenience sample of 100 users really allows for much of a conclusion either way.

abler2 · August 15, 2020, 6:53pm

Hi, new ST defector here just been playing with new C7 for a few days and reviewing some of the forums. One issue I've seen raised is that the new release has reduced the event storage per device (and per attribute as I understand) from 1000 to 100. This is a fairly significant reduction that I would expect could impact some users. Without getting into specifics of whether this is an appropriate change or not, I'd like to ask what kind of notification is provided to the community before such changes are made? I look over the release notes and I see no mention of it. In other forums I see that some time in the past sms service was dropped (albeit with a 3'rd party path to implement the function). I don't mind at all being pleasantly surprised when new features are added, but I would really want advance notification of an intent to remove features or reduce functionality. As a new user, can someone let me know if there is a formal process hubitat follows for this?
Thanks.

Rxich · August 15, 2020, 6:54pm

I'm honestly not going for a published journal article. Maybe more of wanting to stop my hands from shaking when I pickup my unopened C7 box

It won't let me edit the poll, so see tally below

bertabcd1234 · August 15, 2020, 7:28pm

Presumably, it just falls under the general "performance and stability enhancements" item in the release notes. But yes, calling this out specifically might be a good idea. There is, as far as I've seen, no formal process for doing this, but usually staff note important changes in the reless notes (like they did for the major Z-Wave changes or like they do when a platform firmware version intoduces a database or app incompatibility problem if you roll back and don't take the FB with you).

But in this case, you didn't really lose any features. The default just changed. You can change it back--or set it to whatever you want--by doing the following:

ddalder · August 16, 2020, 8:22pm

I decided since I had a couple of days off, I would have the time to try and resolve issues if this update did not go well. It completed with no problems. I have several rules, but the extent of my automation isn't anywhere near what some people have. There are no unusual or unexpected log entries. Performance in most cases has been better, but I sill have one Z-Wave Plus motion dimmer (GE) that is sometimes VERY slow (8-10 seconds). Considering it's on the other side of a wooden wall (6 feet) from the hub, I have no idea why this is an issue. Anyway, I don't believe it's related to any of the past updates.

jtmpush18 · August 16, 2020, 8:32pm

Unfortunately, I had issues with the upgrade on my C5's.
(I have since rolled back).
So, I can readily understand the frustrations of newer owners who upgraded immediately.

csteele · August 16, 2020, 8:45pm

I upgraded 6 hubs.

C-3
C-4
C-5
C-5
C-7
C-7

All are running .119 No problems on any of them. Obviously the problem occurrence is not very high.. except for those people that are having the problem! For them it's quite high, quite frustrating.

erktrek · August 17, 2020, 11:14am

I upgraded my 2 C4's and a C5, also my clients current C5. Left my C7's alone for now. Hubs are working fine so far.

marktheknife · August 17, 2020, 11:57am

My C3 and C5 have been fine since upgrading from v. 2.2.2 (C3 initially to .118 then .119 hot fix, and C5 to .119).

erktrek · August 17, 2020, 4:43pm

Oops my C5 control hub just stopped responding except for the diag page. Restored back to previous and everything is okay.

I do not have Zigbee or Z-Wave enabled on this hub.

Will keep watching this...

edit: My client's C5 is still okay - both Zigbee/Z-Wave are enabled.

jtmpush18 · August 17, 2020, 5:29pm

Exactly what happened to me.... Why is the big question...

erktrek · August 17, 2020, 5:40pm

The only differences on the working hub (updated around the same time btw) vs non working was non working had radios turned off and had both Alexa and Lutron apps installed.

jtmpush18 · August 17, 2020, 5:43pm

I now have one hub with Zigbee & Zwave devices (with the Zwave devices being moved to a C7)
And, one control Hub with all radios turned off. Control Hub has all rules, interfaces, etc.

My control Hub just wouldn't respond - I had to roll back from the 8081 port.

erktrek · August 17, 2020, 6:44pm

same.. is very odd but no big deal for now fortunately. Everything still working fine with the rollback.

danabw · August 19, 2020, 5:29am

Moved the last of my devices on ST over to HE C7 today. Moved a Schlage BE469, Watercop valve, Linear/GoControl garage door, and a bunch of leak sensors. All went well. I had the hub on a 50' ethernet cable to get it close to the lock and the Linear/Watercopy in the garage. All devices joined w/out issues and have been configured and are working. The Schlage took a few tries w/the Lock Code Manager app to get one of the four users/code to take for some reason, but no other issues. Performance has been good, both automations/switches, and button controls.

I'm still working on getting all my non-Webcore automations up and running in Simple Automations, Motion Lighting, and configuring Picos in ABC button control, etc., but the process has been going well. A couple switches were unresponsive and had to be excluded and added again for some reason, and I have one switch that repeatedly adds as a "Device" and needs to have its driver set manually.

I've had a couple of automation glitches...but because I was hacking around on the hub for several days, playing w/different apps and devices w/out really being disciplined, I frankly can't point fingers too much becuase I was never sure who's fault the glitch was. (Hint: Probably mine.)

The most spectacular error I made was having a 60' outdoor light string in two different autmations. It resulted in a crazy/manic on/off blinking that never ended. It was beautiful, like I had moved to Christmas Town.

So overall the good times are continuing for me w/the C7 and 2.2.3 and devices.