I get that, but there may have been loading changes that exposed an issue with your configuration or there’s a legitimate bug.
Could be. Need some time for investigation.
What about the tado integration?
I saw this error when i updated to 2024.1.0
Configuring the Tado Device Tracker using YAML is being removed.
The import was aborted, due to an existing config entry being the same as the data being imported in the YAML. Remove the YAML device tracker configuration and restart Home Assistant. Please use the UI to configure Tado.
When i removed the data in the yaml file, there is nothing to configure in the UI.
What to do about it?
Have you checked your Tado integration, for new entities / device-trackers ( even disabled ! )
Do not update if you use SONOFF integration. There are confirmed issues with reporting devices state back to HA after update. Integration may require fixes.
8 Likes
For testing purposes I left this alone to see that the temp would actually drop, interestingly it’s since increased to 100F and the heater is still on and drawing power.
The device itself reports that the setpoint is 37F but also reports that the heater is still on. Definitely something funky going on with the new thermostat card but hopefully this means nobody ends up cold tonight accidentally
Heads up: 2024.1 breaks the Salus IT600 integration as per HA 2024.01 breaking changes · Issue #54 · epoplavskis/homeassistant_salus · GitHub
Thnx man, i didn’t saw it in the first place, but you’re right.
There is a new device tracker entity.
I hope for the people after me that the last sentence in the error is removed, because it is quite confusing.
I hope it will be resolved fast🤞!
In the card configuration ui there is an option “Show current temperature as primary information” (or in yaml show_current_as_primary: true)
3 Likes
Yes, please open an issue on github.
Well done guys, update went smooth!
- good rework on the automation editor, this will definitely help newcomers a lot
- it’s good to repeat the option to use shortcut buttons
How is this done to get an emoji in the automation name? 
Using 2024.1.0. Startup continuously repeats the following entries in log:
Jan 04 00:34:35 ubuntu hass[1003]: 2024-01-04 00:34:35.318 INFO (SyncWorker_2) [pyfritzhome.fritzhome] Updating Devices ...
Jan 04 00:34:35 ubuntu hass[1003]: 2024-01-04 00:34:35.416 INFO (SyncWorker_2) [pyfritzhome.fritzhome] Updating Templates ...
Jan 04 00:35:05 ubuntu hass[1003]: 2024-01-04 00:35:05.319 INFO (SyncWorker_2) [pyfritzhome.fritzhome] Updating Devices ...
Jan 04 00:35:05 ubuntu hass[1003]: 2024-01-04 00:35:05.397 INFO (SyncWorker_2) [pyfritzhome.fritzhome] Updating Templates ...
Jan 04 00:35:35 ubuntu hass[1003]: 2024-01-04 00:35:35.316 INFO (SyncWorker_0) [pyfritzhome.fritzhome] Updating Devices ...
Jan 04 00:35:35 ubuntu hass[1003]: 2024-01-04 00:35:35.411 INFO (SyncWorker_0) [pyfritzhome.fritzhome] Updating Templates ...
Jan 04 00:36:05 ubuntu hass[1003]: 2024-01-04 00:36:05.319 INFO (SyncWorker_2) [pyfritzhome.fritzhome] Updating Devices ...
Jan 04 00:36:05 ubuntu hass[1003]: 2024-01-04 00:36:05.396 INFO (SyncWorker_2) [pyfritzhome.fritzhome] Updating Templates ...
Jan 04 00:36:35 ubuntu hass[1003]: 2024-01-04 00:36:35.317 INFO (SyncWorker_7) [pyfritzhome.fritzhome] Updating Devices ...
Jan 04 00:36:35 ubuntu hass[1003]: 2024-01-04 00:36:35.428 INFO (SyncWorker_7) [pyfritzhome.fritzhome] Updating Templates ...
Jan 04 00:37:05 ubuntu hass[1003]: 2024-01-04 00:37:05.317 INFO (SyncWorker_1) [pyfritzhome.fritzhome] Updating Devices ...
Jan 04 00:37:05 ubuntu hass[1003]: 2024-01-04 00:37:05.414 INFO (SyncWorker_1) [pyfritzhome.fritzhome] Updating Templates ...
Yep…
Don’t get status from devices…
Rolling back here.
1 Like
How are you controlling your lazyspa? I ask as the Bestway integration has been down for me for two days and I’m looking for an alternative 
Since updating to 2024.1 core mobile devices no longer show sensors provided by the mobile app in HA. Log shows -
Logger: homeassistant.config_entries
Source: config_entries.py:406
First occurred: 07:35:49 (2 occurrences)
Last logged: 07:35:49
Error setting up entry SM-G950F for mobile_app
Error setting up entry SM-T505 for mobile_app
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 406, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/mobile_app/init.py”, line 125, in async_setup_entry
Hmm, I guess I found a reason of this error:
In some my package I had this “secrets.yaml” file:
# used for MariaDB
#recorder_url: "mysql://xxxxx/home_assistant?unix_socket=/var/run/mysqld/mysqld.sock&charset=utf8mb4"
i.e. the file is empty.
And it was considered as a wrong “secrets” (i.e. “not a dict”).
This is really new.
And more interesting: I may create a similar “secrets.yaml” file with same content in another package - and the check passes.
If I delete a content of this faulty “secrets.yaml” - it anyway causes an error.
May be it is somehow related to this particular “secrets.yaml” file, it has diff. properties:
No, weirder. Same file placed into another package may / may not cause the error.
OH CRAP!! Yeah it broke the Sonoff/AlexxIT Integration. No Energy readings available and throws all kinds of errors on Sonoff devices I do not even have.
3 Likes
Seems like this release has broken a lot of integrations that were not listed or reported. Hopefully, there’ll be addressed soon.
3 Likes
So I’ve avoided .0 releases like the plague for a year now because something always goes south on me. I decided “hey, this one doesn’t have too much going on and literally two new features that are useful to me, so why not”. I am already seeing a key integration “SecuritySpy” lost three sensors, not sure why, but fortunately the cameras still feed into HA so I’m sort of on the fence of keeping or restoring. I guess I’ll know in a couple hours after things happen.
I’ll be chuffed if it fixes some ongoing errors I’ve been dealing with, which is a big reason I updated.