Same is about languages like C, Pascal etc: functions (or procedures) should contain a code which is used in many places, and this helps to “structure” a code, debug it etc. Ofc a developer must check for possible performance issues like “calling a function may need more time due to stack allocate/fill processes” - but I think this is mainly in past; actually, whole object-oriented-programming is an impact to performance…
1 Like
Thanks for the link, I missed that.
Reading the post it looks like I might have been right 
As of today, I’m now seeing frequent reboots (~15 minutes) of my system. I’m on 2023.4.2 on an NUC, but have been unable to find anything that helps me understand what is causing the system to reboot. The only changes I’ve made since 2023.4.2 was reducing my MariaDB purge from 90 to 60 days. I had some DB upgrade issues reported previously above, but I thought resolved itself after the forced reboot after 24 hours of upgrading to 2023.4.0.
Anyone else seeing frequent reboots following 2023.4.2 or have recommendations on what to look for to troubleshoot further?
@petro I’ve read almost all comments and I’m still not sure if it good idea to proceed with the upgrade since I use the following custom cards:
button-card
Bar Card
mini-graph-card
Stack In Card
Simple Thermostat
Weather Radar Card
Power Flow Card
Irrigation unlimited Card
How do I know/check if a card use the the deprecated Polymer library or not?
Thank you.
They may use it, but polymer hasn’t been removed yet.
1 Like
@Joao-Sousa-71 First of all , if you do Not see the warning in Inspector, your cards are not using it .
If you do see the warning, you need to look for the actual usage of the Polymer, not the simple mention in the copyright notice.
That raised all the red flags in my earlier screenshot.
See Deprecating Polymer - #3 by Mariusthvdb what to actually look for
1 Like
Think you replied to the wrong guy
Start with HA logs and the supervisor logs.
Sadly 2023.4.2 didnt fix the issue for me. Now frequently each day the recorder takes the full value from my energy monitor rather than the change, and so I have to manually edit my consumption data.
Tried to fix that, but the original reply seems to stick
thank you @Mariusthvdb and @petro for your prompt answers. I will perform the upgrade over the weekend.
Given a 50GB database, its possible the migration is still going on and the problem will resolve itself.
If it doesn’t, please open an issue with any queries that are coming up in the slow query log and we will try to address them.
Anyone else’s button entity in lovelace broke after updating to 2023.4.3? It was fine in 4.2
5 Likes
Mine was also gone. I just rolled back to 2023.4.2.
I lost my Telldus Live integration with 2023.4.3. Ticket Unable to add Telldus Live integration with Home Assistant 2023.4.3 · Issue #91323 · home-assistant/core · GitHub created
I have problem with panel card (when only 1 panel is on the frontend). Lost side sroll bal, and can not move down and have no access for the card button in my tablet. Problem is occured after 4.0 update. A tested 4.1-4.3 but does not changes. I do not know how can i solve without downgrade.
It was a problem on Telldus side. Working fine now, ticket closed.
Any info when the navigation bar chevron issue will be fixed? It’s still there in 2023.4.3 version 
I have not sene any solution yet…