Examples of using different parameters

[eacxx]

Hello man
I used to use the Occupancy blueprint until a week ago or so...
In fact until I discovered your BP that is looking much more professional to me. Well, it's true that it gets beyond the "wasp in the box" routine, but this is making it even more attractive.
The problem is my English and my beginner skills in HA.
These two make me helpless in front of all the parameters you offered to us in your add-on.
If you or any other more skilled user than me can put here some examples of using all these parameters, it would be of big, big help. Not only for me, I'm pretty sure about this.
How can we use the open/close delays for the door?
How can we use the bypass collection of parameters? etc...
Yes, you put there some explanations, but like I've said, for my English knowledge...was not enough :(
I'm just using it, let's say, basic: a door sensor, a group of movement sensors, a switch and an occupancy helper. That's all.
So any help we can get is more than welcome!

Thank you a lot for this piece @asucrews

[asucrews]

Sure, I think I can come up with some. What is you primary language? Maybe if I translate my readme to you language via Google or something it might help?

[asucrews]

@eacxx, please check this new document link. I quickly put it together, so it might not be perfect. I'd like to know if the format is helpful and if you have any suggestions for improvements. Let me know. Over the next few days add more advance usage guide.

https://github.com/asucrews/ha-blueprints/blob/main/automations/witb_plus/docs/basic_usage_guide.md

[eacxx]

Thank you very much my friend for your support.
I'll go right now to the link above and I'll get back.
My native language is Romanian.
I can translate myself the readme, either with Google or ChatGPT, but everytime I miss something in the meaning...
But with your help, I'll win! :)

[eacxx]

Hey, Jeremy!
What you do have in that document yet, it's already part of my vast knowledge :)
Like I've said, I have a door open sensor, two movement sensors declared in a group and a switch which is controlling a light.
For the moment I have this issue very often, but not every time:
When I enter the room the boolean helper is switching on (and this is starting an automation), the light is turning on, everything is good.
When I leave the room, the door sensor gets open then closed, after almost 30sec the movement sensors go off, but the boolean helper keep staying on.
Sometimes it is going off, immediately after the movement sensors going off, as it supposed to do, and my automation stops, but most of the times it doesn't.
That's why I hopped that all that collection of parameters you implemented, maybe will help me tuning this, but unfortunately I don't completely understand how they work.

[asucrews]

door_sensor_open_delay, door_sensor_close_delay, and motion_sensor_delay are settings that add a delay after the related sensors are triggered. You can adjust these delays to see if it helps. Try setting them all to 0 initially. Not all sensors are the same, so differences in sensor configurations could be causing issues. That's why I included these settings.

what version of the blueprint are you using?

[eacxx]

v0.3.3
So if I set a delay of 5sec, for example, after the door opens. Then if I'll close the door back in less than 5sec, then the open_door event will not be triggered? Or the event it is triggered, but 5sec later? Well, this could happen if the door remains open, I suppose... Because if it's closed before the delay expires, the event disappears.

[asucrews]

that is the idea, it was added to reduce the light turning off and on if people comin right after each other.

[asucrews]

@eacxx i am working on a debugging methond and clean up so i see if there any bugs

[asucrews]

@eacxx just pushed out a new dev version after the clean up. if you want you can test it out to see if clear your issue

https://github.com/asucrews/ha-blueprints/blob/main/automations/witb_plus/dev/witb_plus_dev.yaml

[eacxx]

I'll give it a try, of course!

---

Later EDIT
Man, it's weird, but I'm still facing this issue with the occupancy helper remaining set on ON.

1. I enter the room
2. The sensors, both movement and door, gets triggered, the helper is set ON.
3. I'm going out the room
4. The door sensor gets open then closed
5. The movement sensors gets cleared
6. The occupancy helper remains ON
7. :(

---

Much more later EDIT
If I let the door open, then the occupancy helper gets OFF as long as the movement sensor clear its status.
If on the contrary, I'm closing the door when I left the room, the helper remains ON.

[asucrews]

I think I understand what is happening. The blueprint assumes the door remains open when no one is in the room and that the door is closed when someone is in the room.

I haven't found a way to handle the situation where the door can be closed regardless of whether someone is in the room.

Workarounds:

1. Create an Idle Timer: Set an idle timer in the blueprint. For example, the blueprint will start a timer, and after the idle timer expires, it will check for motion. If no motion is detected, it will turn off the lights and occupancy helper. The downside is that you need more motion sensors or similar devices, and if you rely on PIR sensors, remaining still for too long will cause them to shut off.

2. Use an mmWave Sensor: I don't have any mmWave sensors, so I'm unsure how they would affect the blueprint.

3. Brainstorm: Help me brainstorm a better way to handle the scenario where no one is home when the door is closed