How many lights are on?

[new-to-this]

As you can tel from the name I am very new to this. I decided at 61 I need to challenge myself to start a new hobby and this looked the perfect fit after having sonoff products for a few years. Three plus weeks in and OMG what cant HA do!! I am in awe of the amount of codes flying about on here to enable all sorts of intergrations, only thing is I havent got a clue what I am doing. Is there a novice page anywhere? I have managed to copy a bit of code from somewhere (forgotten where) and put it in a template card to count how many of my lights are on.

{{ states.outlet|selectattr('state','equalto','on')|list|length }}

Is there any way of showing how many are on in bed 1 or in the longe etc this just counts all of the lights. Any help will be appreciated.

Thanks

[jchh (my username is my initials (and my first name isn't John))]

Absolutely, you can.

Let’s reformat your code a little - it makes no functional difference, but it’s easier to break it down:

{{ states.outlet
  |selectattr('state','equalto','on')
  |list
  |length
}}

OK, so line 1 is referring to all states, line 2 selects all things that are on. line 3 lists them and line 4 essentially counts them
What you want to to is only have the Ines that are say, “lounge”

We’d add an extra filter for that…

{{ states.outlet
  | selectattr('state','equalto','on')
  | selectattr('entity_id','search','lounge')
  | list
  | length
}}

That extra line is a filter that looks for entity_Id's that have the word lounge in them (bearing in mind it is only choosing from a list that is already set to on).

btw, I’m not sure about states.outlet, I’d use sates.light and also count

{{ states.light
  | selectattr('state','equalto','on')
  | selectattr('entity_id','search','lounge')
  | list
  | count
}}

…also, the filter that looks for entity_id could also look for friendly_name…

  | selectattr('attributes.friendly_name','search','lounge')

The search function uses RegEx, so you can play with that as well.

[new-to-this]

Thank you so much for that, I will have a play tomorrow, she who must be obeyed is back… Lol. Where I put outlet I had actually changed it to light but was playing with the same Idea with sockets. I’ll post how I get on after having a play.

[jchh (my username is my initials (and my first name isn't John))]

Sure thing. Just pop back and ask any questions you have!

[OlliVa]

Interesting. In my case, it shows one light more than I really have, because I have a group “light.all_lights” wich is also shown as “on”, if I turn on a light.
How can I exclude only this device from the counter?

BTW: I have an automation, that turn off all lights after a power failure and I will change it to work with this sensor “if more than 15 lights on → turn off all lights”

[123 (Taras)]

@OlliVa

How can I exclude only this device from the counter?

A Light Group has an entity_id attribute. The template can be designed to exclude any light entities having an entity_id attribute.

{{ states.light | selectattr('state', 'eq', 'on')
  | rejectattr('attributes.entity_id', 'defined')
  | map(attribute='entity_id')
  | list | count }}

[jchh (my username is my initials (and my first name isn't John))]

My lights are all via Z2M as are my scenes and groups so this doesn’t work for me. I need to select entities with the attribute linkquality (there are other attributes that my lights have but groups don’t have that I could choose from).

{{ states.light
  | selectattr('state','equalto','on')
  | selectattr('attributes.linkquality', 'defined')
  | list
  | count
}}

edit: typo.

[123 (Taras)]

@jchh

so this doesn’t work for me

The example I posted was specifically for Light Groups and won’t work for a legacy group of lights or for a Hue group of lights (or Z2M groups and potentially other types of groups of lights). However, the principle it employs, rejecting/selecting entities based on the presence of a distinguishing attribute, can certainly be used for other applications.

[new-to-this]

jchh,

Sorry for the late reply, however, I’m back with good news. It worked fine for me, thank you. I played a little and changed it to show all of my sockets that are on as well. As I said I’m very new to this so it’s a huge learning curve, next task if to google Yaml for complete novices and see if I can start playing with that (I have a second Rpi 4 running homeassistent on it just to play with so if I break it there’s no great loss) I’m that much of a novice i’m yet to find out where I type the code into… wish me luck

[jchh (my username is my initials (and my first name isn't John))]

Good luck!

[new-to-this]

Okay, i have tried and failed. I would like to exclude a specific switch from a count and try as I might I cant do it, I have searched and tried a few different things but i am having to put my hand up for help. I know it’s possibly simple but to me … Maybe not. I have pasted below what I have at the moment I just need to exclude “switch.xyz”

Thanks again

{{ states.switch | selectattr(‘state’,‘equalto’,‘on’)
| selectattr(‘entity_id’,‘search’,‘lounge’)
| list | count }} sockets on

[new-to-this]

With a bit more trying i managed it…

sockets on {{ states.switch | selectattr(‘state’,‘equalto’,‘on’)
| selectattr(‘entity_id’,‘search’,‘lounge’)
| rejectattr(‘name’, ‘search’, ‘Lounge Light’)
| list | count }}

[stnickt]

@jchh
This is the best breakdown/explanation of each line and filter I’ve seen. I’ve been trying to create these counts (windows/doors/motion/lights) and now filtering by “area” or room. This helps so much…thanks!

[jchh (my username is my initials (and my first name isn't John))]

@stnickt

I’ve been trying to create these counts (windows/doors/motion/lights) and now filtering by “area” or room.

Feel free to ask if you have any questions.

[madjetey (Michael)]

Is it possible to exclude all the members of a group? In my case I have a WLED light with 5 sections and a master switch. The sections stay on but the master switch is automated and what I keep track of.

[jchh (my username is my initials (and my first name isn't John))]

Yes, you can either put them in a group and exclude that group or exclude them by name (easier if they have part of their name in common).