Latest stable version

[DavidFW1960 (David)]

@wellsy

Is it truly wise to have posted this to the front page?

Yes it is. It’s a bugfix for the current 0.103 version. You’re just losing your way in the weeds here.

[Silicon_Avatar]

Comment Removed.

[aidbish (Adrian)]

Really, what are you trying to achieve here, before it was about what’s not documented, now it’s with documented changes.
I am really at a loss for your motives. So I think I may bail on this thread.
Have fun.

[finity]

@aidbish

The support is only for the services Nabu casa provides and that isn’t core HA support

without HA Nabu Casa wouldn’t exist. If Ha stopped existing tomorrow, so would Nabu Casa.

And they are getting paid out of the Nabu Casa funds to develop HA not Nabu Casa. As a matter of fact, that was one of the biggest reasons given as to why Nabu Casa was started (“…and to support further development of Home Assistant…”)

@aidbish

Plus I don’t think burningstone said the core developers were volunteers but said they live of donations to Nabu casa.

Maybe but that’s not how I read this. But I could be wrong.

@Burningstone

Developers and contributors do all this in their free time and don’t get paid anything (The core team lives from donations made through users applying for the Nabu Casa cloud and paying a monthly fee).

And I’ll say it again…payments to Nabu Casa aren’t “donations”. They are payment for services rendered. Just like the customers who buy a service plan from any other company that also offers a free tier aren’t making “donations” to the company for it. They are paying for a service.

@aidbish

The rest of the Devs who contribute do do it in their spare time for free

I completely agree.

@aidbish

saying if they are not willing to support everyone they shouldn’t do it

I never said that at all. But I also think that there is some kind of a “social contract” that you enter into (no matter how minimal) when you put something out in public that at least trying to support your contribution should be attempted.

Honestly, I think the vast majority of devs actually do that so I’m not taking anything away from those that do in any way. But strangely, it seems that the ones who complain about it the most are the ones who should be complaining about it the least.

But my statements were just about the idea that since this is an open source product one has no right at all to expect any support whatsoever from any developer at all - even the ones who are paid by users to develop HA.

But whatever, the “wagon circling” has already begun in earnest so no further point in continuing.

[wellsy (Steve Wells)]

@finity

But whatever, the “wagon circling” has already begun in earnest so no further point in continuing.

It’s a pity but I absolutely agree with your sentiment!

@aidbish

I am really at a loss for your motives.

My motivation:

@wellsy

AIM: Happier first time users or those looking for greater reliability

Thats it!

[DavidFW1960 (David)]

@finity

They are payment for services rendered.

The service paid for specifically is HA Cloud access… not HA itself.

[finity]

Yeah, I know…

[finity]

@wellsy

It’s a pity but I absolutely agree with your sentiment!

Thanks, (I think…) but unfortunately, I don’t agree with most of yours.

Because HA is under continuous development there is never (and by virtue of that fact always) a by-definition “stable” version that has to be released in order for issues to be found and then corrected.

As has been said many times already - we are all beta testers. You can’t expect things to never break. If that’s not something you want to risk then don’t update. The only problem is that when you want to update for some new desirable integration because of the way HA is built it’s way more painful to catch up.

As far as v100.x up to present completely destroying your system did I miss a post about that somewhere in which you asked for help? Or heck, maybe I saw it (or even contributed to it) since I see dozens of threads every day (and reply to many of them. ).

My point is, did you try to get help on here for the problems you were experiencing?

[wellsy (Steve Wells)]

@finity

Thanks, (I think…)

@finity

“wagon circling”

I tried to help myself and monitored the threads that seemed helpful…Once the UI was working (albeit with Massive Memory and CPU usage) I just managed that with frequent container restarts and tested as many other versions as I thought may help…none did too much but as I found better I stopped on them…then 0.103.3 solved my problems.

Been an interesting yarn but I’m off now so catch you all later!
Oh, Merry Christmas!

[nickrout]

I think a tolerable way of thinking about it is that a .0 release will be improved by point releases, ie .1 will fix some stuff, .2 some more. Some release get up to .4 or more.

So the most likely way to get something really stable is

(latest_release - 1).(maximum it got to)

So we are presently on 0.103.x so a really stable release would be 0.102.3, which is the highest point release of the previous series.

Of course 0.102.3 MAY give some individual users grief, but that is very dependant ontheir setup.

[wellsy (Steve Wells)]

Just to say thanks for posting your ideas here Nick.

I have to report that 0.103.4 is looking equally as good as 0.103.3 and in fact I may be seeing slightly less busts of CPU usage and possibly slightly lower continous CPU and Memory usage…only from my observations as I dont have my QNAP metrics to back that up. ZERO errors after around 8 hours runtime.

Update:
Ended up switching back to 0.103.3 this morning as overnight there was a mountain of errors and warnings running 0.103.4…CPU and Memory usage was also up.

So far today all stable running 0.103.3 so sticking with it.