💡 Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time - Light Control - Device Tracker - Night Lights

Blueprints Exchange
, , , ,
2953

@J273

It all depends on what each mean.

Normally motion = PIR sensor. Like the ones that has been around for decades. They act fast so the automation can respond fast but may not detect you if you sit still.

Occupancy = Normally a mmWave sensor. They act slower at the start but are good at detecting movement even if you are still.

If we use them both then you have fast reaction and good detection.

If this is what your sensor is then what you can do is group your occupancy and motion and use the group as the trigger so you have the best of both. A link in the blueprint next to the trigger input shows you how to group them.

Blacky :smiley:

1 Like
2954

Thanks for the reply and I will try this out. How would this handle say the fact I’m sitting in the desk zone and someone else walks into the other zone? I don’t want it want it to change to cold white if that’s case

2955

@shunopoli

Because we are using your Desk Zone to activate night lights, whenever it is ON night lights will be applied. Then we use all of your zones as the trigger to turn the lights ON. It is critical you select If lights are ON, adjust the lights when crossing over for it to work.

Test it out and let us know how you go.

Blacky :smiley:

2956

I don’t think that enabling legacy features back is a solution. It’s a mere workaround, because the core problem is still there. There will be only struggle maintaining it down the road.

@Blacky, do you think it would be possible to incorporate the device triggers in the blueprint please?

2957

Hello,
Z2M also updated over the night to version 2.0.0 (HA is 2025.1.0).
As I have prepared the configuration, all is good except some automations.
I’m facing exactly the same issue as @beurdy
I’ve also noticed this error that I didn’t have previously

image
image2115×568 55.4 KB

Perhaps are we facing a kind of inconsistency with the evolution in Z2M 2.0?

Thanks

2958

Z2M changed the illuminance sensor id, removing the “_lux” at the end. You’ll have to delete the old lux sensor and enable the new one, in each device, then change all the automations that use the old _lux sensor id.

3 Likes
2959

@lukas423

It is a workaround for sure, but for everyone with non working zigbee buttons(including me) due to the sudden change in Z2M, it’s a good one, until everything else is sorted. :slight_smile:

2960

Thank you @dreadino, this did the trick :tada:

2961

@lukas423

Re Z2M, I think @dreadino provided the correct solution for this.

No it will break the blueprint. Targets are tricky and I break down everything into their correct domains so the blueprint can handle them. If you have devices then more has to be broken down and possibly filtered out. If you add a device then just expand it down to entities using <> then removing any entities that are not needed and the blueprint will work faster without any problems.

Blacky :smiley:

1 Like
2962

Never mind stumbled across areas vs lights :man_facepalming:

2963

Hey everyone,
quick question, as Ctrl+F was not helpful. I have the automation set to turn on my dinner table lights. However, I often just walk by the table and it turns it on. I would like to delay it so that only if someone is sitting at the table for 3 minutes to perform the automation. Any ideas? I have tried setting a helper and toggling it on and off via automations and then set that helper as the toggle for the automation but to no avail…

2964

Thanks a lot @Blacky. At least I can save and use it now. :+1:
Unfortunately I need to find out, how to manipulate the Brightness of the white channel of my Shelly Plus RGBW PM only. It seems, I need to understand controlling it in HA first.

Danny5

1 Like
2965

Create an automation that turns on an input boolean helper, with a state trigger of “presence at the table” selecting 3 minutes in the bottom left of the trigger card. You should also handle the turn off of the helper. Use the helper as the actual presence at the table for this blueprint.

2966

Hi dreadino,

thanks! I tried that, however, it’s not letting me pick the boolean/helper as trigger for the blueprint. The trigger can only be a binary sensor, as it seems. :frowning:

Any ideas?

2967

Hi Blacky!
i have some questions for you:

  1. i have a 4-button switch in Z2M, but i cannot specify it’s buttons as a bypass. In Z2M, it seems that it only has a ‘action’ entity that tells whether button 1 was pressed or button 3 was held and so on, but i cannot find it or reference it in any way, in HA. I cannot choose the action entity as a bypass either. However, i can choose the automation that controls what the buttons do, but it doesn’t seem like that’s the right way to proceed. Is it possible for me to still use that as bypass? If so, please tell :slight_smile:
    From Z2M exposes:
    billede
    From HA:

    billede
    billede1562×775 40.7 KB

  2. In my bathroom, i have 2 separate lights that are both controlled by the same automation, one in ceiling and one by the mirror. The ceiling light is bright, so i always set that at about 70% which means that the mirror light is also turned on at 70%, since brightness cannot be controlled individually. The problem is that the mirror light is not too happy about being brightness controlled and will make a high-pitched screeching noise while not being at 100%. How can i control the brightness level of the two lights individually, while still using your automation?

  3. In the Bypass section, you mention that one should not use the same entity in more than one bypass option. I have a shelly relay attached to one of my lights and two physical, spring-loaded switches, effectively only giving me one input per switch (which is toggle). The switches are both connected to the same channel on the shelly relay and both are used for turning on and off. Im not sure how to make the automation understand correctly that i just turned on (or off) the lights manually. Any advice?

I’ve been looking through your documentation, but haven’t been able to find answers for these questions. I hope you’re willing to help! Thanks for all your time, the effort and your help! :slight_smile:

2968

I think you need a binary sensor. You can create another helper, a template binary sensor, that mirrors the value of the first helper, then use this template binary sensor in the blueprint.

Or alternatively, you can skip the automation and just use the template binary sensor, writing the 3 minutes rule in the template. Ask ChatGPT or Gemini for help on how to write the template, they’re great with this kind of requests.

I went ahead and asked myself. This should work, just change “motion_sensor” to the id of your motion sensor.

{{ (states.sensor.motion_sensor.state == 'on') and 
           (as_timestamp(now()) - as_timestamp(states.sensor.motion_sensor.last_changed)) > 180 }}
1 Like
2969

Thank you - it´s working!

1 Like
2970

hi @Blacky ,
huge fan of your bluebrint, just saying cause I usually come here with errors.

One of my blue prints topped working. I get an error at the step where there is a first " choose"

Error: UndefinedError: ‘homeassistant.util.read_only_dict.ReadOnlyDict object’ has no attribute ‘brightness’

What could this be?

edit: I found it but can’t solve it. IN teh automation config screen (traces) it still shows an old switch as an entity. Is there a way to remove this?

edit 2: This didn’t seem to be the problem,
I remade the automation by coping the correct automation config.
I gives an error:

Stopped because an error was encountered at January 6, 2025 at 3:35:34 PM (runtime: 104.91 seconds)

2971

@Icecoke7

You will have to create a template binary sensor and add it to your config file. I have a FAQ for this click here for more information but your code is below.

It is similar to REF - TS-2

Once you create it add it into the trigger.

template:
  - binary_sensor:
      - name: 'Dinner Table Delay Motion'
        device_class: motion
        icon: mdi:motion-sensor
        state: >
          {{ is_state('binary_sensor.your_motion_sensor_entity_id_here','on')}}
        delay_on:
          minutes: 3

Blacky :smiley:

1 Like
2972

@Strux

  1. Your entity must have an ON / OFF state. Normally buttons can have no state or a quick ON / OFF. You will have to try and make the button toggle a toggle helper. You could try this blueprint and see if it works then use the toggle helper in the bypass. :nazar_amulet: Press Button - Turn ON & OFF Entities
  2. This is the perfect use case for a scene. Create a scene with your ceiling and mirror lights and adjust the brightness on each entity to your liking. You will then need to create a toggle helper and another scene with everything OFF. Look in the Lights section on were to put everything so it works well.
  3. Have a read of the FAQ on bypasses. It explains everything, click here

Blacky :smiley: