bkbartk

Don’t forget to join our release party live stream on YouTube 3 April 2024, at 20:00 GMT / 12:00 PST / 21:00 CEST!

shouldn’t that be 19:00 GMT? It’s DST now

1 reply

petro Great contributor

Yes, Yes it should. It starts in 9ish minutes.

Krispkiwi

This is a fantastic update. UI changes across the board and the tagging feature is going to be used extensively. I was titling my automations like Lights: (Name of light automation) so yay for inbuild organization.

Is there any update to polygon area/zones?

Xypod

As someone with ADHD im really looking forward to organizing everything haha! PACKED update, really glad to finally have all these tools at our disposal. The team is KILLING it!

daywalker03

I actually like Floors and Labels, even though I haven’t used the latter yet. I also like having the option of Categories, but I don’t yet know how I will use them.

Edwin_D Regular

I’ve been trying the beta without any issues. Thanks for the hard work and listening to us. This will really help a lot organizing automations, scenes and scripts and will make it easier finding the right devices and entities based on tags. Lots of automation platforms do not acknowledge that not all lights are equal, even though they are in the same area. Being able to tag the right ones is key.

1 reply

silfax

Is devices batch delete ever coming?

1 reply

pabloaugusto

Great news! The ui changes are awesome!

Cougar

I’d like to see device (firmware) version info and sort/filter by that. Would be so helpful in case you have dozens of similar devices and try to manage their versions.

Krispkiwi

Looks like I can finally get rid of old yaml groups for different types of devices and lights. Can just create a label for them.

1 reply

parautenbach

Totally, now I can label lights as ambient or main.

But then there’s this. Ideally one would like to call e.g. light.turn_on and specify a label. I think if you want to get rid of groups, you’ll have to use some templating to use the new labels. For example, using the new label_entities function.

KennethLavrsen

Thank you so much for categories. I can finally move my 150 or so automations from yaml files in a directory structure to GUI (which can still be yaml edited).

I am deeply thankful. I love you guys and girls that made this

1 reply

tom_l

Frontend tables improvements are excellent. Well done.

2 replies

kslb

Still dinosaur slow restart speed if Kodi integration is used and Kodi device is powered off…

atlflyer

I’m thrilled about this update, but very that integrations can’t be categorized or labeled (as far as I can tell). It would also be great for browsing if categories (or any group by option) could be collapsed.

Holzglocke

Hey great work you do. I just started using HomeAssistant and it’s amazing.

Hope to get to know more of it in the future. I learn so much and it’s so cool.

Thanks to the team.

ShadowFist Regular

Amazing release! Now I just need to decide whether the stairway gets labelled as ground floor or first floor!

1 reply

petro Great contributor

why not make a separate floor with the same index?

1 reply

ShadowFist Regular

I was half joking, but that’s not a bad idea

1 reply

Virmian

Being ever greedy, can I have two more grouping functionalities:
Group by label - multiple labels on a single item gets its own group, just like it would work in sql
Multiple groupings - first group by device, then by label

catellie

Um, I may be in a small minority here, but I think there was an issue in the 32 bit image: I get into a boot loop with:

     from cryptography.hazmat.bindings._rust import (
 ImportError: Error loading shared library /usr/local/lib/python3.12/site-packages/cryptography/hazmat/bindings/_rust.abi3.so: Exec format error

So I suspect the 32 bit version of this library is b0rken…

3 replies

OddyAte

Regarding the new Map and Webpage dashboards, how are you supposed to add them? I do not have them as an option in the Add Dashboard menu.

2 replies

petro Great contributor

I didn’t come up with it, came from balloob himself in beta channel a few days ago.

Nick4 Regular

Going into my automations gives me this:

So my existing automations are not showing even though if I open VSCodium they are still there.
Refreshing my browser doesn’t change it…

1 reply

petro Great contributor

refresh your page. But you just click “add dashboard” then select those dashboards, then configure.

1 reply

petro Great contributor

look for errors in your logs, did you alter configuration.yaml recently?

1 reply

catellie

Possibly someone having a variation of this problem fairly recently:

OddyAte

After I went to my profile it prompted for a frontend reload. Refresh did not seem to help before but now it’s ok, thank you!

Also, I noticed in the livestream that the profile picture should appear in the bottom corner. I just have my initials there, even though I have a picture assigned to my profile. Does this only work for Home Assistant Cloud accounts?

1 reply

petro Great contributor

No, that works for any account that’s attached to a person.

Nick4 Regular

Hi Petro, I made some changes days ago in the configuration.yaml regarding the recorder.
There are warnings and some errors but they seem not to be related to this.

Don’t know if this is normal: upgraded from 2024.3.3 → 2024.4.0 and it took quite a long time (never had that before like this) to load everything

1 reply

pschneider87

Thanks for this awesome release. I’m organising my house since b0 and still find ways to optimise

One question: I love the new lock feature, but is there a card so I can place it on my dashboard?
Or even put it on my home screen on my android phone with this double-check for opening?

1 reply

petro Great contributor

if you have an issue with configuration.yaml it may not load everything. Post the errors you’re seeing.

1 reply

DerekO

I really like the idea of labels, but just wondering how flexible you can be with them.

I’d rather not have too many labels so would prefer to use combinations. For example, I could label all lighting devices, heating devices, security devices, etc. I could also add labels for, say, people, events, etc.

What I’d really like to do is to be able to use multiple labels as selectors when running actions in automations - e.g. turn on devices with labels of Lights and Christmas - rather than have lots of labels such as Christmas Lights, BBQ Lights, …

I can see that I can select using a label, but not using a combination - e.g. Lights AND Christmas or Lights, but NOT Christmas.

Probably not that easy - is there some way of maybe using a template to select based on combinations of labels?

1 reply

petro Great contributor

the only way to do not with labels in the target selector is with templates.

catellie

As you probably have more pressing issues to handle, I’ve backed down to the 2024.3 docker image for now and as expected it runs fine. Let me know if you want me to file a proper bug report for this.

Roxy

Hiya, Feedback to the team.

Thanks for the hard work - good work Bram.

Enjoying the updates, need to seriously look at my ‘want’ list as you seem to be crossing them all of lately.

pplucky

Hi there.

Anyone knows if labels can be assigned in YAML, or is it UI-only?

Thanks a lot.

2 replies

petro Great contributor

UI only, just like areas and floors. If your yaml entity has a unique_id, you can add it to the yaml entity via the UI.

Mariusthvdb

being able to do this:

and not having to go to the dev tools states (horrid response) to add a filter ‘status’ is very nice indeed, and allows me to do away with some auto-entities cards that were doing heavy lifting.

nice.
o, and finally being able to do away with Maps in the menu and still use default_config (though I am not sure that isnt browser dependent…)

made me discover this page is very much out of date and doesnt list a lot of integrations thats are included Default Config - Home Assistant

needs some editing

ofc it could also be that after Move core fundamental components into bootstrap by frenck · Pull Request #105560 · home-assistant/core · GitHub the documentation on those moved integrations (to bootstrap) has not been updated, as they still mention them being part of default_integration…

1 reply

Ildar_Gabdullin

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:

1 reply

gerd1

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

1 reply

Cadster

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

KNXBroker

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

cogneato

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

1 reply

cogneato

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

Stooovie

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.

HappyCadaver

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.

mchk Guidance Counsellor

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

1 reply

tom_l

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

oklahsam

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.

1 reply

rjing001

WE NEED Packages in the UI

2 replies

dumbdevice

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

1 reply

_pm

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

boheme61

WOW, overwhelming ! , yes i am a fan of structure and “order” , this release is absolutely amazing !

sparkydave Know-it-All

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?

2 replies

dunxd

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.

Briandr73

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

1 reply

Eugene_Niemand

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 replies

Nardol

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.

1 reply

allard77

Haven’t actually tried it yet, but big kudos to the dev team for adding labels not just in addition to, but even at the same time as floors. And so much more stuff too! I will need some time to explore all the possibilities.

1 reply

sparkydave Know-it-All

It’s per user, per device.

1 reply

bdraco Great contributor

Try enabling debug logs for homeassistant.bootstrap as it may catch the culprit that is delaying startup

logger:
  default: info
  logs:
    homeassistant.bootstrap: debug
    homeassistant.setup: debug
    homeassistant.loader: debug
    homeassistant.config_entries: debug

1 reply

Nardol

I was not enough fast, after a restart it looks thing went better, even if I had Bluetooth related errors.

2024-04-04 01:47:36.346 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [00:1A:7D:DA:71:15] due to timeout after 5 seconds
2024-04-04 01:47:36.350 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [00:1A:7D:DA:71:15]: [Errno 1] Operation not permitted
2024-04-04 01:47:36.352 WARNING (MainThread) [bluetooth_auto_recovery.recover] Bluetooth management socket connection lost: [Errno 22] Invalid argument
2024-04-04 01:47:41.351 WARNING (MainThread) [bluetooth_auto_recovery.recover] Bluetooth adapter hci0 [00:1A:7D:DA:71:15] could not be reset: 
2024-04-04 01:47:41.357 WARNING (MainThread) [bluetooth_auto_recovery.recover] Closing Bluetooth adapter hci0 [00:1A:7D:DA:71:15] failed: [Errno 9] Bad file descriptor
2024-04-04 01:49:27.251 WARNING (MainThread) [switchbot.devices.device] None (C0:5A:8A:D2:ED:CF): Error disconnecting: [org.freedesktop.DBus.Error.NoReply] Remote peer disconnected; RSSI: -47
2024-04-04 01:51:31.301 ERROR (MainThread) [habluetooth.scanner] hci0 (00:1A:7D:DA:71:15): Error stopping scanner: [org.bluez.Error.DoesNotExist] Does Not Exist

I restarted bluetooth.service then reloaded the Bluetooth integration and no other error until now.
I did not have these errors before when starting Home Assistant.

For the information, I use passive scan.
Until now some thermometers have no battery information available.

EDIT: IIRC battery often takes some time to be displayed correctly, except that it looks to be OK until now.
First start after update has been a little bit chaotic but second start looks OK.

balloob Founder of Home Assistant

Labels are just that? Go to your entities tab and filter by label.

1 reply

sparkydave Know-it-All

So putting this into the template dev tool now spits this same error… it worked before 2024.4. Is this a bug or a problem with my template?

1 reply

Ildar_Gabdullin

Although tables were reworked - sorting is still questionable: after the 2nd tapping on a header a sorting order becomes weird. This is an old issue.

NathanCu

What’s the state of that switch at the time of the check. If it’s unavailable I think it’s going to blow up. Because you’re trying to divide unavailable by 2…

1 reply

sparkydave Know-it-All

Hmm. Now I’m confused… Yes, that switch was for some reason ‘off’, but even when I turn it ‘on’, it doesn’t have a brightness_pct attribute. The brightness I’m supposed to be dividing by 2 is that of the light entity.

So it should be a simple fix but I’m confused as to how it could have ever worked.

In theory it should actually be this:

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

So I’ll change it and see how it goes…but how did it EVER work?

1 reply

Nardol

Another good addition for me is the new settings for Home Assistant Cloud voice which now provide more voice also for tts.cloud_say, we have more possible voice same as Assist, not only male and female.
Thanks!

odwide

Isn’t the disable toggle on the Automations page too accessible now, making it risky to disable automations accidentally?

2 replies

sh00t2kill

Tell me you’re in the northern hemisphere without telling me you’re in the northern hemisphere

1 reply

sparkydave Know-it-All

Who are you replying to? I’m in the southern hemisphere…

1 reply

sh00t2kill

no one specifically – the blog post is about spring cleaning, but its autumn
i thought it was just posting, but its been a long morning.

1 reply

odwide

I’m on the Ecuator.

sparkydave Know-it-All

Yeah fair point. We seem to get a lot of that on here.

1 reply

tom_l

“Equinoctial clean” doesn’t have the same ring to it. I only know that word because last week I was looking for a word to describe my Spring and Autumn blinds schedule.

martamoonpie

No! I’m so glad they brought this back. It was very annoying when they removed the toggles.

Ildar_Gabdullin

I would say - “labels” are misplaced here since they may not be related to “locations”:

Discussion

At least this note about locations should be edited.

2 replies

teskanoo

I would love to see Bayesian make the cut as a UI candidate - live preview would really help tweak

mcarty

The new Ring Intercom integration from the beta didnt pass the cut?

1 reply

grahamj

Wow thanks so much for this! I’ve been mostly happy using a naming convention plus search to organize and find automations but my mind is spinning considering the possibilities of targeting entities by label! That plus the new table options have me very excited for this install to finish!

teskanoo

I have had several templates/automation exhibit issues over the last few months. It has almost always been related to the reduced startup time. HASS is starting up so fast that I think my templates/automation started triggering before all of the entities with which they interact (Zigbee devices) were actually available.

In most cases I have managed to resolve the issues by adding availability to the template or a condition to the automation

An availability template may be defined to suppress rendering of the state template.

1 reply

tom_l

Yeah I got this in the beta testing. A light brightness automation I’d been using for ages suddenly turned off all the lights if I restarted at night. Guarding against unknown and unavailable states did the trick. I commented along the lines of:

Start-up is too fast now!

justone

Wow, the new webpage dashboard finally allows for Logitech Media Server using the Material Design to be added to HA. This never worked using the old iframe solution.

ehn

It’s great to see the addition of floors. Would it be possible to also add buildings as a way to group floors? Many single-family homes consist of more than one building and may have a guesthouse, boathouse, stand-alone garage etc.

Arguably, the addition of floors alone makes that situation even more awkward, as it might now seem like things are on the same floor while they are in fact in different buildings.

Alternatively, what about the more general option of allowing nested areas as suggested elsewhere in this thread? That could neatly accomodate for buildings, floors, sections of floors (family area consisting of multiple bedrooms, say), rooms and parts of rooms (dining area and sitting area in a living room, say).

2 replies

francisp

Just upgrade my Pi2 (32bit) from the beta to release, no issues.

1 reply

123 Regular

When the concept of floors was proposed in the Architecture repo, nested areas were suggested as an alternative. The suggestion was rejected.

The entire discussion can be reviewed here:

2 replies

marnau

Hello,

Who are using Huawei solar integration: GitHub - wlcrs/huawei_solar: Home Assistant integration for Huawei Solar inverters via Modbus
Can confirm that it’s working fine with this version of HA?

3 replies

denverpilot

Didn’t go well here. All devices connected via the Tasmota integration (via MQTT) went “unavailable”.

Too late at night to deal with it, mess with it this weekend. Reverting.

2 replies

sparkydave Know-it-All

I had some issues with MQTT earlier and restarted the Mosquitto add-on… so far so good but I’ll do more testing when I get home from work this afternoon.

1 reply

denverpilot

Trying a complete restart now, may see if bouncing MQTT brings it back… otherwise I’ll kick off the restore from backup.

Clearly it’s something about MQTT, but I’m definitely not in the mood. LOL…

c.ciprian

The floors do no reflect in the labeling of the automations.

olwater

After upgrading to the latest 2024.4.0 system, SNMP entity values that were previously functioning correctly under 2024.3.3 now fail with an error when encountering negative values.

Update for sensor.hwacbgroupbatcurr_96 fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 951, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1268, in async_device_update
    await self.async_update()
  File "/usr/src/homeassistant/homeassistant/components/snmp/sensor.py", line 218, in async_update
    await self.data.async_update()
  File "/usr/src/homeassistant/homeassistant/components/snmp/sensor.py", line 264, in async_update
    self.value = self._decode_value(resrow[-1])
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/snmp/sensor.py", line 273, in _decode_value
    bytes(value),
    ^^^^^^^^^^^^
ValueError: negative count```

Laffer

First off; great changes this release. Very much appreciated!

A couple things:

• Filters sometimes seems to not filter correctly. For example, in the Automations view, Filters, Areas – when selecting an area, areas that are in different areas show up. I could be selecting “Office” and a couple items from “Bathroom” would show up.
• It would be great to be able to collapse groups.
• It would be nice to be able to add multiple items to an area, like we are able to with categories.

Mariusthvdb

made that same remark during Beta, and the answer was: they have to go somewhere.

Since they’re so unique in HA, and, more importantly, pertain to almost everything in HA, they should probably get their own entry in that listing

Mariusthvdb

that discussion really is about Floors (which is a true asset to HA now, almost cant imagine how it was before), as is pointed out more than once in that thread.

The resistance/reasoning against nested areas still feels illogical to me. I can see the challenge from a developers point of view.

However, when taking the User’s pov, nested areas are so obvious.

my usecase for those would be that I have a larger condo consisting of a single Floor (well except for the attic and basement…), and that single floor has 3 major parts. Areas. Like separate structures, connected by a few corridors.

Inside those I have rooms etc, which are my current Areas.

It was suggested to change those (areas) to labels, but that is not what a label is for imho.
Next, Paulus suggested I use several Floors on the same level.

So I did, and with the current tools, that indeed seems to be the most elegant approach.

I cant stop feeling it is a ‘hack’ though, and not a real solution to my quest for finding the most succinct reflection of the architectural design of my home.

The idea to have more than 1 Floor on a single level (0 in my case) goes against my understanding of the concept…

because like the release notes say:

Floors are a new way to organize your areas per level of floors in your home.

panhans

Can I edit/delete categories in the automation view?

//EDIT: found

In the filter menu you can edit your categories.

1 reply

adorobis

Indeed! Now I can finally clean up all those orphan entities

Mariusthvdb

are people removing groups, in favor of labels? wondering if we should go that way, and still be able to template those easily enough.

example: grouped media_player s, test for them being available, and/or playing. Set volume on the group etc etc.

what would be most efficient? do we still need to test for availability to prevent None errors etc etc.

didnt get a chance to test the during Beta, so hope others have already done so.
Group vs Label

or should we just keep using both

groups:

{{state_attr('light.feest_lampen','entity_id')|select('has_value')|list|random}}

labels:

{{label_entities('feest_lampen')|select('has_value')|list|random}}

or can we do:

{{label_entities('feest_lampen')|random}}

need to find out what happens on an unavailable light

1 reply

Holdestmade

Click filters, then categories and the list of categories is shown, click on the 3 dots to edit / delete whichever you want