2024.4: Organize all the things!

Blog
41

Wanted to ask the same question.
Pity we have no possibility to assign labels in yaml.

Very useful changes anyway.
Many things to analyse.

Added FR for a yaml support for labels:

2 Likes
42

The new feature ā€œWebpage dashboardā€ is very nice!

But how can I change the URL after saving such a dashboard?

In the old iframe_panel i could chang this on the fly

Best regards
Gerd

43

I love the startup-speed and the organisation tools of the new release!
Great work!

44

Great release and beta! It was really impressive in which speed new features and improvements came in during beta testing. Thank you

1 Like
45

Does your lock have the unlatch feature? Not all locks do.

46

Open the dashboard, click the edit pencil icon in the upper right corner.

1 Like
47

Filtering doesnā€™t work for me other than Categories and Blueprints. Filtering by Devices and Areas does not filter the view. And yes, Areas are properly assigned.

48

Nice, I can now do away with basement_bedroom_1_ceiling_light_1_etc. Thankfully Iā€™m still new to HA and donā€™t have that many entity IDā€™s to rename.

1 Like
49

Thanks for the new version :pray:
I still ask you to add z-masonry support in future versions to remove gaps.

image
image713Ɨ211 26.8 KB

4 Likes
50

Please create a feature request in the correct category. This is not the place for them.

2 Likes
51

Adding floors is definitely a nice to have for those with multiple floors. As a single floor home-owner, Iā€™ll have to think if thereā€™s something I can use it for. I suppose it could just be used as a group of Areas, and not necessarily an actual FLOOR. Though that does make me wonder why Areas werenā€™t just upgraded to be able to contain Areas. Nesting Areas would add the same functionality as floors while being more flexible.

8 Likes
52

WE NEED Packages in the UI

2 Likes
53

Awesome new features!

Here is quick feedback:

  1. Option to add category/label when creating a new automation
  2. Show number of items in each category
  3. Maybe save the filter view (and group by) for the next time when you open Automations/Scenes, etc
  4. Group by filter for Devices not applied when you open Devices page again like Automations
3 Likes
54

Very nice to see the automatioms automatically have the option to be filtered by floor/area. This works when entities have an area linked but not when they have the setting ā€˜inherit from deviceā€™ active, would be nice to have that covered too.

Thanks for another epic release!!

I also really like the new section gui. My nice to have there: support merging columns (for example have one wide (2 sections) column and 1 standard next to eachother

55

WOW, overwhelming ! , yes i am a fan of structure and ā€œorderā€ , this release is absolutely amazing !

1 Like
56

My system was working during the beta (at least up until some point, I missed the last couple due to them coming out over last night) other than a random reboot loop that happened a few time. This morning I jumped onto the stable and now my MQTT isnā€™t working and one of my automations is spitting errors.

The lighting automation is failing on this part:

service: light.turn_on
data:
  entity_id: light.kitchen_light_level
  brightness_pct: >-
    {{ state_attr('switch.adaptive_lighting_kitchen', 'brightness_pct') /2 |
    int(100) }}

with this error:
Error: Error rendering data template: TypeError: unsupported operand type(s) for /: 'NoneType' and 'int'

This worked fine before the 2024.4.0 stable, even during betaā€¦

Not sure what is going on with MQTT just yet. Still investigating. Anyone else have MQTT issues? (it might only be a particular section of my config so still hunting it down)

EDIT: seems the MQTT issue I have is likely related to a device being disconnected from HA MQTT serverā€¦

2024-04-04 05:24:35: New connection from 192.168.30.12:52162 on port 1883.
2024-04-04 05:24:35: New client connected from 192.168.30.12:52162 as 84:0D:8E:B1:0B:8D (p2, c1, k15, u'hassio_mqtt').
2024-04-04 05:24:40: New connection from 192.168.30.241:53966 on port 1883.
2024-04-04 05:24:40: New client connected from 192.168.30.241:53966 as bedroom_fan (p2, c1, k30, u'hassio_mqtt').
2024-04-04 05:25:47: New connection from 172.30.32.1:60457 on port 1883.
2024-04-04 05:25:47: New client connected from 172.30.32.1:60457 as 511DgkSGcCtPJ0WbuW0YlJ (p2, c1, k60, u'homeassistant').
2024-04-04 05:26:31: New connection from 172.30.32.1:57330 on port 1883.
2024-04-04 05:26:31: New client connected from 172.30.32.1:57330 as frigate (p2, c1, k60, u'hassio_mqtt').
2024-04-04 05:29:46: Client 84:0D:8E:B1:0B:8D has exceeded timeout, disconnecting.

Anyone know how I can prevent that timeout?

1 Like
57

Probably everyone with more than one floor in their home has at least one area that spans two or more floors - a staircase or hallway for example.

Currently that might be split into two areas to allow controlling lights in one level but not the other, but sometimes you might want to consider it as a single area - all hallway lights on with an automation based on presence, or detecting temperature for the whole room.

This is one thing where I am currently using brackets or naming conventions for labelling rooms and devices that the floors doesnā€™t appear to help with.

58

Does anyone know if the Whirlpool integration is fixed in this release? Recently the integration was not accepting logons

59

Great to see dashboards getting some love. Please tell me why we still canā€™t set a default dashboard for a user. It seems to be device and network specific? When Iā€™m at home I get my default selected one but on 5G or office WiFi I get the overview. Please allow assigning a dashboard to a user

2 Likes
60

This version does not look promising at first start. More than ten minutes have passed and a lot of entities are unavailable (Switch Bot thermometers, ESPHome devices, tracker entities for personā€¦).
Database migration has been done but after that nothing happens so I donā€™t know if I should restart HA or continue to wait.
Or simply go back to 2024.3.3 after restoring the backup I made before updating HA core.

2024-04-04 01:22:32.647 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration livebox which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-04 01:22:32.648 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-04 01:22:32.649 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration pollens which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-04 01:25:45.197 WARNING (MainThread) [homeassistant.bootstrap] Setup timed out for stage 1 waiting on set() - moving forward
2024-04-04 01:25:48.067 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-04-04 01:31:45.201 WARNING (MainThread) [homeassistant.bootstrap] Setup timed out for stage 2 waiting on set() - moving forward
2024-04-04 01:31:45.663 ERROR (MainThread) [homeassistant.components.automation.suppression_notification_de_maj_de_home_assistant] Suppression notification de MAJ de Home Assistant: Error executing script. Service not found for call_service at pos 1: Service notify.mobile_app_pixel_4a not found
2024-04-04 01:31:45.695 WARNING (Recorder) [homeassistant.components.recorder.migration] Database is about to upgrade from schema version: 42 to: 43
2024-04-04 01:31:45.695 WARNING (Recorder) [homeassistant.components.recorder.migration] Adding columns last_reported_ts to table states. Note: this can take several minutes on large databases and slow computers. Please be patient!
2024-04-04 01:31:45.715 WARNING (Recorder) [homeassistant.components.recorder.migration] Upgrade to version 43 done
2024-04-04 01:31:48.196 ERROR (MainThread) [homeassistant.components.automation.suppression_notification_de_maj_de_hacs] Suppression notification de MAJ de HACS: Error executing script. Service not found for call_service at pos 2: Service notify.mobile_app_pixel_4a not found

At 01:42 nothing new.

Realy think I will try to restart then go back to 2024.3 if it is still not OK.