Updates and wifi

Installation Home Assistant OS
1

Greetings
First of all - i tired to install updates every day. Please, stop it. Test twice prior running, compabane in one and push after that. Really annoying
But this is not main problem
After last few updates I start losing wifi connection, and I have to enable dhcp/connect to network manually
Im using Rpi 3 with two different network wired and wireless, as you may understand networks are separated.

2

Completely up to yourself…just don’t update….

Impossible…there is no developer that runs all 2132 integrations (not even talking about the rest of them through HACS)
A developer only works/fixes the things he has running himself, and those he tests before pushing…

1 Like
3

WiFi isn’t something Home Assistant has any influence over. That’s a feature of the host OS.

1 Like
4

funny but not related. I did not say nothing about 2132 integration at once.

5

did i choose alpine as core OS or you? I’m pointing you to bug - nothing more

6

Heere’s how I started managing updates:

  1. I don’t upgrade to .0 versions, I will wait at least until a .1 is out - unless there’s new general functionality I just cannot wait to try.
  2. For following .X versions I read the release notes and if there’s nothing in there that concerns general functionality or integrations I use, I simply skip them until the next major version change comes around.

This approach has saved me a lot of testing time as well as time spent upgrading and general downtime of my system.

So, just as @aceindy so well put it:
“Completely up to yourself”

7

Funny but might not be related: Joining, reading 4 minutes and having a good moan over received replies and imaginary bugs.

My friendly advise: Hurry, go for some other and paid Smart Home solution and rant there if you think you have found some shortcomings.

3 Likes
8

Just my 5 cents:
I find it very rude to complain on something that’s free and developers do that on their own (free) time. VERY rude! And even worse: that someone registers on this forum just for that….
Nobody’s forcing you to update. Heck…noone is even forcing you to use HA instance. If you’re not happy with it, use something else.

4 Likes
9

But your past issues are most probably related to one of them or even from a HACS integration, which isn’t even supported by the development team:

  • We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
  • We found a custom integration duepi_evo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

The core itself is rock solid…
Most of the times it is a core change that affects one (or more) addons…

  1. The core developers will not know which (unsupported) addons will be affected, they might use a few addons, but for sure not all 2132…
  2. The Addon developer on his turn needs to update their part (if the addon is not abandoned). Note that there are many addons that are abandoned (as the creator replaced it with something else for whatever reason). If you are lucky, it will be continued by someone else :wink:
  • custom_components.localtuya.number::LocaltuyaNumber is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom integration author.

So my local tuya (hacs integration) will stop working properly, if the addon won’t be corrected before 2022.10 release….

1 Like