I think every software releases new features and breaking changes. This has nothing to do with stability of the product.
Samsung SmartThings was Stable in Hub V2, but they released a new firmware with new features recently.
I could use Windows as an example as well, but there are some that will argue Windows is never stable…
1 Like
Sorry perfect example is Ubuntu there is a LTS (Long Term Stable) it only gets bug and security updates.
There is then another “unstable” release which continues to grow.
Technically the desktop version is stable, they do a LTS for server environments as a version that has long term support rather than the usual desktop lifecycle.
I think the distinguishing factor may be more referring to the difference between what is perceived as beta and what is perceived as production 
And therefore gets out of date.
1 Like
Out of date in whose language?
No it has nothing to do with Beta, please go and read the definition of LTS.
The non LTS release cycle are not Beta’s there is a completely different release cycle. The release is not a beta.
Oh by the way desktop has a LTS
1 Like
I haven’t done an LTS version of ubuntu for sometime, so was not sure of the Desktop LTS.
Even LTS versions have a lifecycle though. My old LTS 8.x is nothing like LTS 20.
I think in the home automation space everything is changing so quickly that having an LTS version is not viable. It would be high maintenance from both the core developers and everyone developing add-ons. Of course I see the advantage from both sides, but in my opinion a year of no new features would be death in smart home space.
1 Like
You have answered your own questions.
The differential between LTS versions is exactly the point. I have achieved what I want with automating my home, I don’t need any more add ons so why can’t I just stay on an LTS version and make the choice when I want to go through all the breaking changes etc and just receive security updates and bug fixes.
I have spend thousands of dollars in my home automation and countless hours. I just want to leave it alone.
All to often on this forum people are out to prove people wrong when their opinion differs from yours. Just appreciate that people want different things and let their views be heard.
I work in fast moving technology my day is full of planning and executing new and updated technology, for which I get paid very well for. I like tinkering and is why I love HA, but sometimes I just want some extended downtime when I am happy with what I have achieved, as I do have a life I like to enjoy away from technology.
2 Likes
In anyone’s language. EG 18.04 LTS is outdated if you want to run home assistant in a venv as it ships python 3.7.
Who said anything about HA.
I provided the Ubuntu LTS model as an example of what I would like to see for HA.
I have a multi billion enterprise running on Ubuntu LTS. The two years between Ubuntu LTS is perfect.
For my HA I am running HAOS on a NUC
Well just stop updating, if you have a version running as you like it, use it.
2 Likes
No because I won’t get bug fixes and security updates.
What happens when a manufacturer whose devices you use changes their method of operation? And you need a new or changed integration? Or you want a to buy a new device that is only recently supported in HA?
2 Likes
I have better things to do. I’m going flying.
1 Like
Off the top of my head: TP-Link, MyQ and Harmony all had breaking changes that required something to be updated/changed to continue working. I am sure there are dozens of more examples of things that become out of our control. Firmware is one thing since it requires an explicit update, but API changes on a website can be brutal at times. Its not like they actively tell us in advanced about breaking changes, at least HA can give you a 1 week heads up LOL.
Exactly what I meant.
Hi,
Any idea, what to do with sensor like this:
sensor:
- platform: snmp
name: 'Printer uptime'
host: !secret m476dw_ip
baseoid: 1.3.6.1.2.1.1.3.0
accept_errors: true
unit_of_measurement: 'minutes'
value_template: '{{((value | int) / 100 ) | int}}'
- platform: template
sensors:
hp_uptime:
value_template: >-
{%- macro parse_time(sec) -%}
{%- set w = sec // 604800 -%}
{%- set d = sec % 604800 // 86400 -%}
{%- set h = sec % 604800 % 86400 // 3600 -%}
{%- set m = sec % 604800 % 86400 % 3600 // 60 -%}
{%- set s = sec % 604800 % 86400 % 3600 % 60 -%}
{%- set comma = joiner(', ') -%}
{{- comma() ~ w ~ ' week' ~ ('s' if w != 1) if w -}}
{{- comma() ~ d ~ ' day' ~ ('s' if d != 1) if d -}}
{{- comma() ~ h ~ ' hour' ~ ('s' if h != 1) if h -}}
{{- comma() ~ m ~ ' minute' ~ ('s' if m != 1) if m -}}
{{- comma() ~ s ~ ' second' ~ ('s' if s != 1) if s -}}
{%- endmacro -%}
{{ parse_time(states('sensor.printer_uptime')|int) }}
The result from SNMP is uptime in timeticks which is number of 100th minutes
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (2232042626) 258 days, 8:07:06.26
Thing is that this is standard OID and all systems that can be managed with SNMP have it. The reason is that not all systems have RTC or any other type of clock and it is very easy to keep track of uptime.
I would convert this uptime to boot time but problem is that HA clock is not in sync with printer clock and therefore now() - sensor.printer_uptime is unstable with ±1 unit (whatever is it sec, min or hour).
One idea is calculate the boot time but then use the previous boot time if these are close enough. Would be great if HA can handle that but AFAIK there is no better way at the moment. In lovelace I’d still like to see uptime but this should work if I move this template calculation to the panel I guess. Not sure, if the entities panel can be used any more or does it work only with custom panel.
Or does anyone have any great idea for that?
I solved this with two new sensors created by template like this:
sensor:
- platform: template
sensors:
ha_version_minor:
value_template: "{{ states('sensor.ha_version')[5:] }}"
I got bit by the HACS config error after I updated.
I have no HACS icon (yes, I refreshed the browser) and I get a notification that HACS has an error in the config.
The notification says to check the config and the logs.
There is literally nothing in the logs that could be even tangentially related to an issue with HACS (aside from the “you using a custom component…” yada yada). So the logs are no help at all.
So I thought I’d try to remove and re-add the integration but it’s not listed in the integrations page so I can’t remove it from there.
If I try to re-add the integration at this point it says:
So, I am at the state that I have an invalid config for HACS, I don’t show it listed in the integrations so I can’t remove it using the UI, And I can’t add it because the system thinks that I already have it installed. 
Seriously, I really think the devs need to come up with a way to fix stuff like this without needing to go into the .storage files and removing things manually - which we are told never to do and when inquiries are made on how to do it then we are always asked “but why would you ever need to do that!?”.
Well, for this exact reason.
Supposedly this is supposed to be the (differently named) HA 1.0!! release but yet we still have no way of troubleshooting something like this. And are forced into editing protected system files.
How is a person who can’t even figure out how to write their own automations…from a UI…and needs a blueprint…supposed to figure out how to fix this?
@tom_l ran into a similar issue to this a few days ago as well and asked a similar question. The silence on the reply has been pretty loud and clear not only here but in other threads over months where this has question has been raised and completely ignored.
Did you enable debug logging for HACS?
I had the same problem after 2020.12.0 but after a few more restarts the issue was gone and HACS worked.