this update is disaster for me. I’ve lost my HA. And can’t to load restore data. I’m not even sure if it’s worth restoring. It’s taken so many months to build.
OrangePI 4b 4G 64G
Same problem . Both solar logs are returning index out of range. Did you find a solution ? Thx
If you’re expecting help, post at least your logs and installation method.
Thank you for answer. I logged in via ssh and am trying to find them. It seems that HA sometimes starts, but then loses connection again. Updated using standard tools. Via WEB on 2024.10.0 → 2024.10.1
The log file is in the same directory as configuration.yaml.
Do you have alexa media players?
No, but there was integration with Dahua and some others. I deleted everything. And left only automation for solar power plant control. It seems to me that the system has stabilized.
Shows that there is an update. But it can’t be updated. Stuck on attempts. I have no idea why.
I try from console too and looks no access more to update.
Hallo everybody.
With the upgrade I have 2 issues. I cannot seem to pin point why I am having these issues. So if anyone has a clue that can be helpful would be much appreciated.
Thanks up front !
-
Daikin / Onecta. Response time is so slow. Example if I change temperature it takes 2 minutes before it changes in lovelace. It does change immediately in the unit itself.
I do not have this problem in 2024.10.9.4 -
SolarLog is not working “string index out of range”. Solarlog is out of service. As I use this app to control my energy consumption many off my automatisations are not working anymore. I do not have this problem in 2024.10.9.4.
I am back in 2024.10.9.4 without problems
Thank you
Bart
Tibber is working for me, and has since quite a long time.
Headings, nice way how to replate entities tile and get more at one place 
1 Like
Hi all,
I faced problems with switches in 2024.10.0&1.
In case I do external action with physical switch - this action appears in integration log (z2m, tasmota, esphome), but HA state does not change and also automation based on state was not triggered.
I switched back to 2024.9.3 for now…
- Core 2024.9.3
- Supervisor 2024.09.1
- Operating System 13.1
- Frontend 20240909.1
Updated to 2024.10.1 from 2024.9.3 and ran into issues with emoncms integration that we rely on. I understand change for making it easier with UI setup, but
a) why couldn’t the setup be migrated?
b) setting up new entities keep the sensors names or at least include the feed id
Now I have 48 entities named like sensor.emoncms_emoncms__temp_nn to sort through and rename
1 Like
We had such a fantastic reaction when we released our [renewed badges]<<<<<
Everywhere in these blogs I have noticed there are more people opposing these changes than welcoming it so how does it make it a “fantastic reaction”.???
5 Likes
You are in a squeaky wheel echo chamber. This is not the only place feedback was received.
2 Likes
What other places are used for getting a feedback from new badges?
It would be useful then to post a short research here with evidence that this reaction was positive - otherwise based on Community posts an expression is quite opposite.
1 Like
Usually there are only negative posts because the ones that like it dont express it.
I love the new badges.
7 Likes
New badges allow more customization for showing info, much less customization for styling and considered as small by some users. Myself never used both old and new ones, only posted tutorials about styling the old ones. More worried about a more general issue about interaction between devs and users.
2 Likes
This applies for both sides of the medal, has someone counted all reactions here in the forum as „research“?
I love the new badges a lot, so count me on the positive side 
3 Likes