WE do but the new “target audience” likely doesn’t. At least until they’ve been around for a while.
1 Like
You are the very rare one that does then.
well that’s probably cus they follow people on Youtube who make out its not
i have always said those making YT videos about HA should noteat the start what version it running against etc
I’ve also noticed an increasing lack of interaction from the key Devs on the forums unless something really blows up. I know they are busy, but…
2 Likes
not really, there will be thousands who manage large numbers of them.
if they dont, well they are the ones that post in forums complaining something broke with an update
Actually any online resource should do so, or at least state a date!
How would they know otherwise? It’s not spelled out anywhere at all on the official HA site.
damned if they do, damned if they don’t
honestly if i was a developer i would not even entertain opensource development, it evident here that there are developers on here that think they can do better, but never seem to help them out.
There is a least one dev who has quit doing it recently due to the hassle from people when he didn’t sort their issues out
3 Likes
AFAIK HA is not in beta stage anymore.
A few people responded to my previous posts in order to point me to the fact that a lot of 3rd party addons require hardware or are not easily trackable by core team.
On the other hand a lot of failures reported here comes with incomplete manifests. Such a shortcomming could be easily recognized showing HA admin an alert. Showing such message/confirmation after clicking Update, informing him what addons will stop working if he proceed could be a way.
don’t you think it’s HA (initiative) problem?
1 Like
Yeah sure a notification saying “The custom component xxxx did not load because the developer needs to include a version in manifest.json. Please contact them via the issues feature in their github” would have been good.
2 Likes
Problem is maxym, they have tried in the past with notifications being prominent and warning them of something, and it didn’t go down to well with a fair few.
Like i said before there isnt any happy medium
2 Likes
7 Likes
tbh I don’t remember such.
The most recent was seccurity alerts and yes, the way how those were implemented was “weak”.
I’m not talking about nagging every user by messages like this. I mean performing pre-update system check prior to its execution, reporting all recognized impacts
I know it requires additional work. But really I have imoression, that it would help in a lot (if not most) of cases reported on the forum.
1 Like
I remove the integration and add it again and it works now. Maybe I had some weird in the configuration.
1 Like
sorry i disagree, they warned upfront, had to work out what issue was, implement and divulge
just wish companies like ubuiquty were as open
but im not going to get into an argument how that was done, thats not the issue
they warned people and got pulled for it
1 Like
Who are “they”? 3rd party devs or users?
I mean, to maximize user experience (or minimize frustration) HA should do the best to not break already working installations.
There are obviously several ways to achieve that, but based on number of user reports blogs/change logs seem to be not enough to prevent that.
I quite like the idea of having an in-app (persistent) notification (with a setting, I’d say) for admins as suggested.
I also want to point out that a custom integration for (some) breaking changes exists. True, it’s another thing to install and would be nice to have part of the core installation, and this won’t catch all kinds of errors, but I saw this a few months ago and started using it.
I analyzed the hue_events and noticed the problem. I listen to the event 1002, which apparently is the button release and is delayed by 1-2 seconds. Switching to event 1000 solves the issue, and the button presses are now without any delay.
Problem is, when you listen to 1000 (button down), you can no longer use long button presses (1001).
I do have Garmin. Might upgrade again and try to disable it.
i have the same problems with tuya smartplugs… but Tuya integration doesn’t handle the energy consumption so I went back to core-2021-5.5 version