2022.2: Let's start streamlining!

[aidbish (Adrian)]

@GrizzlyAK

One week? Who is the group of testers, and how big is it? Are users allowed to opt-in to this beta testing program to assist, or is this just reserved for devs? Is there any formal user testing done beyond the dev-built programmatic tests? Otherwise, the feedback you get is after a user’s installation breaks, their home is dark, and they’re really pissed off. Not all problems that occur on releases are the result of breaking changes. It is impossible, as you said, to foresee all possible problems and label them as “breaking changes”. Dev’s clearly don’t like people complaining; but then again, users of YOUR SW don’t like surprises. Perhaps we can help (if you choose to let us).

For someone who says they are active here, statements like this sound like your just trolling. Anyone can and do participate in the beta, its not closed off and has been mentioned on this forums so many times how

[olddawgpowers]

Since you only have Arm Disarm notifications enabled could you do me a favor and look in the EyezOn app or online and do a HA restart and see if you get a *1 Event. Thanks John

[oopsuser]

In my understanding,
The Works for Nest API was depreciated, on developers.nest.com
Implying the same might turn unstable, in which the unexpected behavior might confuse people?
Not only can the API stop anytime, but the worse, since its actively being turned down, the API developer does not guarantee any contract, implying when calling the API, some fields might turn missing or malformed.
I am sure there exists some repo on HACS which will allow this until the API is completely dead.
I found this useful : Works with Nest - HA Page

[CO_4X4 (Colorado Four Wheeler)]

EXACTLY what I do as well. The whole setup to the Google API was overly complicated and I could never get it to work, so HomeBridge rescued me.

[bamzero]

Thanks, saved me a lot of time. I’m running the community plugin on TrueNAS and updated late last night to get this message as well.

I’m not sure if its the best way to do it, but I appended the switch in /usr/local/etc/rc.d/homeassistant in my jail to get back up and running, if it helps anyone in the same situation as me.
Line #98
HA_CMD="${_srv_} --ignore-os-check"
Found the proper place for it on line #116
HA_ARGS="--ignore-os-check --config ${homeassistant_config_dir}"

However this doesn’t help when restarting HA from it’s own server controls so have to find a way to make it a permanent option until the OS check is a little more inclusive.

Update: Plugin fix for restarting from GUI is here:

add -R restart delay

Can manually update the rc.d file or just update the plugin from TrueNAS (gotta hand it it Troy, had actually fixed this 2 days ago)

[koying (Chris B)]

@bamzero

However this doesn’t help when restarting HA from it’s own server controls

If that’s the case, it’s surely an oversight worth opening an issue.

[bamzero]

Looks like someone just did…

https://github.com/home-assistant/core/issues/65733

Actually, I guess the failing OS check is one thing, not ignoring OS check on restart is another.
Seems the OS check issue not going to be fixed as has been closed as not a breaking change and ignoring os check is the only option so guess better open a new one.

[jazzyisj (Jason)]

If you want a sneak peak at what’s happening with the next release bookmark this link. It will always take you to the latest release notes, including betas. So when the next beta drops this link will show you the beta release notes.

If you see something that might affect you in the beta release notes join the beta (see the link petro provided) and submit any issues you have right away. That’s your very best chance to get the dev’s attention if something is wrong - beta fixes are top priority.

Home Assistant

[tom_l]

Also there is an easy way to join the beta program if you are running HASOS. Just go to the Supervisor / System box and click the Join Beta button. You can leave the beta testing program same way.

And have backups. Lots of Backups. That are copied off your system (automate it). The beta releases are usually quite stable but you need this insurance.

Also know how to revert to an earlier version in case something does not work quite right in a beta release.

[GrizzlyAK]

@jazzyisj

If you want a sneak peak at what’s happening with the next release…

Thanks Jason! Bookmarked and will follow up.

@tom_l

Also there is an easy way to join the beta program if you are running HASOS

Thanks Tom. Appreciate the links and details. Cheers.

[GrizzlyAK]

@petro

This is literally covered every single release thread by people who think only 5 people join the beta.

Surprisingly, I’ve been reading every release note for 2 years, and I must have literally missed it every time! . And I didn’t assume it was 5 people, that’s why TF I asked, but in typical form, you strive to make people feel like shite.

@cgtobi and @nickrout
Thanks guys!

@aidbish, still not sure why you’re here tbh.

[nickrout]

Guys, you can stop now.

[aidbish (Adrian)]

@GrizzlyAK

@aidbish, still not sure why you’re here tbh

me niether, but being active here since 2017 must be i like the software and not the people, well some

[petro]

Lets take a break please

[GrizzlyAK]

Not sure why I embroiled myself in this release thread anyway, since I don’t use GPIO, nor do I anticipate any issues with this release. I did, however, take issue with the responses provided by some individuals here who, purposely or otherwise, belittled those who expressed concern. I don’t think that’s acceptable. But I yield. I’m both tired and disgusted.

[aidbish (Adrian)]

No problem

[calisro (Rob)]

Anyone attempt to upgrade to HA 2022.2.2? Had issues in the logs related to HACS and other things immediately. Wondering if I am the only one.

EDIT: Actually I think I am rate limited on HACS causing that issue. Might all be well. idk.

[aidbish (Adrian)]

Just done the upgrade and i cant see anything in the logs related to HACS or other stuff,
What are logs showing?