Efficiency check and advice before moving forward


#1

1) Give a description of the problem
no problem it is working as I intended at this point - really just double checking my thought processes before I get too deep into the rabbit hole and adding more functions.

2) What is the expected behavior?
planning to add if statements around humidity to detect shower usage so you are not stuck waiving your arm out the shower door when the lights blink

3) What is happening/not happening?
again just looking for efficiency advice or simplification to what I have started.

**4) Post a Green Snapshot of the piston!

And Yes my home status is currently being used as a day status. I need to add my location status’s and rework the piston to include those but was just working through this one before going threw and doing all my rooms and customization them too much.


#2

I am working on making it a tad cleaner. here we go

I think I got the idea of what you are trying to do. See if this fancies your pickle.

This way it’s only one tree when you get the motion, and each piece only activates based on the location mode which you had as part of embedded if statements.

If I didn’t get it all feel free to adjust obviously, but I think I got most of it?


#3

that is much cleaner than what I had. quick question following your logic on how you grouped things together since the else statement for home and night are the same can I just truncate the night and add a or night to the home else.

i.e.
only when location mode is home or night

and delete the last else statement.


#4

You mentioned your shower and humidity sensor to you don’t have to wave your arms about.
I have this which works for me.
Lights will turn on and off with motion but if the humidity is above a certain level, I’m taking a shower, the lights stay on with the fan.
Not sure if this is what you were thinking of.


#5

bobbles - what you are explaining is what I am trying to accomplish because who wants to wave there hand out of the shower or have the lights shut off while taking one and the whole point of automation is to make things efficient and reduce power usage right so why have a really long timer. Just have a few questions about your piston.

I assume yours applies to multiple bathrooms which is why you have multiple motion sensors - I am still new to this and was limiting a piston to a single room for trouble shooting purposes but the more I learn about webcore it seems the more you can do with as little number of pistons the better for the instance.

Your lux rating is that percent not luminence? because mine seem to be reporting a luminence rating not percentage. Because your values on my sensors would be very little light.

And last what is at the bottom of your piston referring too for the colors piece.


#6

No. It’s for the en suite. They are strategically placed so that they trigger the light on before we get in the room. Especially in the middle of the night.

Lux value.
My lux sensors are Fibabo ones and are placed in an area where they will get no light pollution from artificial light. This means that they read quite low, but it works.

These bits are for the piston state. If you look at the top of the piston you will see piston state is disabled. This means that the statement will appear in the dashboard. So when you look at the piston list in the dashboard you will see the state of the light.

It all works OK up to a point. If it’s before 7:30 the light level will be low until the required humidity is reached but it’s no big deal. I do need to revisit this to cure this if I can.


#7

absolutely