Did not discover your tuturial until now (someone responded to it making it come up)
Nice to see how you structured you flows almost exactly the way I do.
See my post about how to structure flows
I do this too, but use some more categories (and different tags)
Also defining scenes and using virtual devices too
And check on that too (using papertrails for itâŚ)
Did not use this yet, but I do like the idea and flow
This is used if you manually overwrite your light configuration. Image you have set the brightness of your lights to 100% via the wall switch, if you wouldnât have the memory function, it would reset it to the value configured in Homey when it detects movement.
@Marvin_Schenkel I think you made a typo in your flow.
The name of the variable you check is âBR_darklightâ the name of the variable you set is âBR_lightdarkâ
This is exactly what the memory function + reset flows are used for. Whenever you manually set the brightness via a physical switch, it will update the variable with the brightness and will use that brightness value from then on. In my reset flows, I reset that variable back to itâs default value, so my preconfigured values are used again the night after.
60 seconds is a bit low when youâre reading in the bedroom. Iâve got it set to 15 minutes in the living room, but feel free to tune the variables to your liking . Thatâs why I chose to use variables, so itâs easy to tweak .
It is probably because you have not provided a value for the variable âBR_DarkLightâ before hitting âtestâ. Before testing a flow, you have to provide values for any variables that are used in the flow
I would need a bit more context before I can help you out with the lux sensor
It sure is a lot of work, but it does allow granular control over your lights. It is definitely possible to stick to the Hue scenes, but I donât really see how that would help with the memory functions. A nice âmiddle wayâ is disabling the automatic light flows whenever manual control is used. That way you do not have to store the brightness in variables, but can still override the programmed values for your lights. Then you can use a timer to re-enable automatic lights when you please.
The flows with Lum sensor are inactive. Flow_inactive_with_Lum_sensor|602x500 Does the motion sensor needs to be configured in the hue app? Now it is also already detecting motion and its working.
You probably need to supply a value for âHelderheidâ in order to test your flow. I wouldnât worry too much about it, this flow looks fine and should work as expected
Your flow is not disabled. The grayed-out icon means you just cannot run this flow on demand (by pressing the icon). This is usually the case for flows the trigger based on events that supply data that is used in the flow (e.g. the âHelderheidâ in your case). Flows that just âdo stuffâ without using data from the event can be manually triggered :).
Just wanted to say that this is a really fantastic tutorial! Have set it up this afternoon for my living room and entrance way, now just waiting for it to start getting darker to see it in action. Thanks for spelling everything out so clearly, itâs super appreciated!
Hi there. Little bit of an update. I added a (THEN) âStop Countdownâ step in the BR_ev_Motion_on_dark flow as I kept finding that my lights would randomly (or not randomly, but actually when the timer hits zero) go out and leave me in the dark. Think itâs because my Light/motion sensors (Develco) donât detect lux/motion nearly often enough. Will see if this step helps keep the lights on, literally
Also, Iâm trying to wrap my brain around how to make it so that in my Kitchen, when lux is between two values (i.e. 40 & 100) then only one of my four lights (kitchen bench) comes on. Then, once lux drops below 40, it reverts back to all lights. Will this require new flows and additional variables? Or is there some way to strong-arm it in somewhere? Iâm new to Homey so all the flows and variable can get a bit overwhelming
There is a problem with Fibaro Dimmer 2. When turning off, the Dim_Level is set to zero. Any idea on how this can be resolved? The result is that the light doesnât turn on again since the parameter is set to zero.
It itâs with Fibaro Dimmer 2, it sounds like you either have an error in the settings, or in the Flow. Try reset the Dimmer 2, I had an issue that was similar, and used the dimmer from an old Smartthings config. Resetting the dimmer, solved it. But the problem with Dimmer 2 is still that turning it off, sets the dimming to zero
The problem is that Fibaro sets the DimLevel to zero when it turns off. I canât see how your rule will help in any way? Maybe you can avoid storing the DimLevel when turning off somehow, but I canât figure out how.