I was not sure if it is problem with a Logbook in the new HA version or my own internal problems.
Today many people in my country are trying to recover their Internet connection due to Gov efforts for isolating Russian networks from Internet, VPN clients are not working, my Linux host is stuttering, lots of erros in HA logs, … - these things could cause these freezes, I thought. Great time for a science-making.
I was thinking the exact same thing.
it must be like this.
not sure it has been improved, but even old format couldn’t had been reloaded if added for the first time. For example if you had no any mqtt template at all and have added the first one, the reload was not effective.HA restart was needed. But since this, each further modification could be reloaded with reload button.
just thinking loud, if this is not the same issue
Mine when crazy, I get a different value (wrong one) every few seconds, and I think is due the update, it was working before. Any ideas??
Hi
After midnight mine reset and is now working correctly.
Yeah after I sent you the message, I started looking for the reset option for the host, I couldn’t find it, so ended up restarting HA and it seems to be working now. Lot’s of particular readings on logbook but other than that it looks ok now, Thanks.
It is likely this issue if you have both includes and excludes
1 Like
Way to scare someone. Correct me if I am wrong, I think the replies are for the “Version Integration” calls a NUC as a Generic X-86?
If this is so, why didn’t they simply say that?
When Ubuntu support was dropped, I bought a new Intel Nuc i5 just for Home Assistant. The reliability and speed have been amazing. You can imagine how upset I would be if the Nuc were no longer supported. BTW, I saw this “breaking changes” a couple of days after installing 2022.6. No brick.
What the heck is the Version Integration used for? Just to tell you what version you are running? Is this the same information you see in “System Health”?
has a binary sensor as well to alert you when updates are available and it works perfectly on my NUC
Thanks for the ongoing work.
I’d really love to see full in-built support for peak/offpeak & daily supply charges for the Electricity/Energy so I can accurately monitor the prices/bills. I know there’s a 3rd party integration with some partial support for this but really would love it to be baked in & displayed on Energy page.
Similarly - would love to see an API for obtaining the hourly/daily values for what is being shown in the Energy console. I write my own dashboard app (using existing Websockets & Rest API) so would at least be able to do some of this here if data was available.
You can add and remove application credentials here without restarting Application Credentials - Home Assistant
You can’t just change the credentials before either. If you change configuration.yaml it doesn’t do anything at all unless you delete and re-add the integration. That hasn’t really changed, right? If i’m misunderstanding and there is an actual use case here i’m happy to consider the improvements, but the semantics should be exactly the same, if not better.
For example, you use to have to entirely restart home assistant to change the credentials. Now you can add/remove without restarting.
No third party integration required. Just set up tariffs using the Utility Meter.
1 Like
Many thanks! I was already wondering what’s the difference between “last_changed” and “last_updated”… on that page it’s explained in detail.
Since i read temperature in my case it’s not important which entry i read, since they are always the same.
1 Like
After 2022.06 update my Xiaomi vacuum and the google home mini not working. Today update to 2022.06.01 but the problem is the same. How can I fix this? TY
Edit: My fault. After home mini restart come back, and my Xiaomi vacuum ip adress changed somehow.
Some valid points there.
Yes, the whole concept if yaml based config means that in practice, all integrations are “recreated” on a restart.
And that is in line with how the modern container-based world of software deployments works, rather than the old days of struggling to keep a VM alive.
Remember the days when “uptime” was a metric to be proud of 
I picked up this quote on an event recently. “Services are cattle, not pets”
I guess we all treat our Home Assistant differently. For me it has always been a bunch of disposable deployments, a true cattle farm.
But I guess there are a lot of users treating it as a long running application, not really sure how it will behave if they have to reboot it.
2 Likes
Something just added in this release isn’t it? Good to see.
Oauth2 is only one method of authentication though.
I must say that logbook was really slow for me on the betas and 2022.6.0, but seems fixed on 2022.6.1.
Sorry team that I didn’t have time to look into it and post here or in the beta thread or on github. Really busy week, and no time to do more than click on the update button. (God knows why I did that when I had no time to fix anything!)
It was particularly troubling on the devices pages, where the delay in the logbook working seemed to delay the whole page, including state update for the entities, so it was a real PITA. I was going to analyse some more and post tomorrow.
Glad to see it working as designed in 2022.6.1 and sorry again for not contributing much at all to this beta cycle.
PS, forgot to say thanks to the team, I hope it was kinda implied in the above!
1 Like