I just set up new hue motion sensor to turn on the LED lights in the kitchen where’s a movement. It really sucks. The flow is set up to keep the lights on when there was a movement for 15 minutes. The light goes off when the movement is off. No disapointment. That product is a c r a p. So many issues. €300 gone. It’s ben like that for over a year. Issue after issue w
th no reply from support. Classic.
1 Like
And what is your question exactly?
3 Likes
Not using motion sensors from Philips, but is it possible you’ve configured turn off lights in the app from Hue?
No. The only Hue device is the motion sensor. I have a flow that is configured as follows:
- when - The motion alarm turned on (Hue motion sensor)
- and - Luminance (Motion Sensor) is less than 50
- then - Kitchen lights - Turn on and Turn off - Delay 15 minutes
I set the delay to still have the lights on when I stand still when doing something in the kitchen.
The Hue Motion sensor is unpredictable with Homey. E.g. when there’s movement the lights turn on for the period when the sensor detects movement than they go off despite the setting in the flow. Sometimes they stay on for 2 or 4 minutes. I tried both Hue App available in Homey Apps and there’s no difference in the way they work.
And the question is if the Homey OS will ever be stable?
I have another multisensor just beside the door to the garden - outside and sometimes it turns on the lights in the garden and sometimes it only detects movement and the lights stay off. I’ve been having issues with Homey since I bought that.
Another thing is its Apps. Updates to them are very rare. I bought Ikea Tradfri gateway and motion sensor but read about what type of devices it supports and it was too late - motion sensor not supported.
I could multiply the issues but it’s too late I have to live with that device. I’ve invested too much money just to dump it.
Are you sure you don’t need the count down timer, it kinda sounds like the flow is being triggered whenever it detects motion (regardless of whether or not the light is already on) which in turn means that every 15 minutes after it detects motion … the lights are turned off …
ie, you walk into the room at 13:00pm - light turns on, at 13:15 the light is scheduled to turn off.at 13:02 you turn around to open a draw, the light is already on, but the light is now also scheduled to turn off at 13:17, etc etc etc. It was cause some pretty ‘sucky’ behavior.
You might want to have a look at :
https://apps.athom.com/app/nl.bevlogenheid.countdown
Create a flow, if motion - and light off and lux turn on light, set timer to 15min.
On motion and light on reset timer to 15 min
When timer = 0, turn off light
1 Like
As per your example re flows, do I need three of them?
Yes, there are multiple examples shared on this forum before showing the 3-flow approach commonly used:
- turning on the light is based on the motion alarm trigger (and light intensity and possible time)
- timer is (re)set at each motion alarm cancellation
- turning off the light is when the timer reaches zero.
1 Like
I have hue motion sensor set up to switch the lights on at low lux. And switch radio on at movent and off after 15 min if no movement.
Works fine!
So I think you have an issue in you flow.
I would avice you to add logging ( papertrails) so you can log the behaviour of your flows
1 Like
You’re probably right. I was so frustrated and wrote this. I did what Jamie advised but still something wrong. The light goes on but never turns off.
Flows are as follows ( I had to merge them as one file as I’m not allowed tpo attach more that one file as a new user):
Any one could help, please?
Thanks
The way you trigger those flows will not work, Turned off is a momentary situation and the flow will only fire precisely then. You should rather trigger the flow with motion and have a check in AND if the light is on or not.
Your second flow should be changed into one that checks for movement during the countdown and if so resets the countdown, this to ensure you don’t end up in the dark when walking around in your kitchen late at night. 
If I trigger with motion then in the second column “…and” I can’t change the light behavior. It only allows - Is turned on - can’t change to anything else.
The second flow checks if there was a movement and light were on and resets the countdown, I guess. I can’t see the exact option to reset. It’s only - Start countdown timer, which I believe is the one that is required here. Sorry, for you it’s easy-peasy but I have only just started. Thanks
@rafi check the flow example of the first search result; it shows the exact 3 flows to rebuild with your Philips HUE motion sensor:
https://community.homey.app/search?context=topic&context_id=2983&q=Motion%20flow&skip_context=true
direct link of @Rocodamelshekima’s flow example: Motion flow
1 Like
I agree with johan, your flows will not work this way (and they dont).
The way you created them they wil only be triggered at the precise moment that you turn of the cupboard.
Thats not what you want.
Flow 1 you want to trigger (WHEN) every time your motion detector does not see motion anymore. to prevent a lot of switching use a countdown timer. (See example flows mentioned above)
Your flows are almost right… but you’ll need to swap the motion alarm to the IF column and the Cupboard condition to the AND colum.
-
WHEN…
the motion alarm turned on(Motion sensor) | …AND…LUX < 60,Is turned off(Cupboard) | …THENReset countdown timer(Kitchen Cupboard),Set brightness(Cupboard) -
WHEN…
the motion alarm turned off(Motion sensor) | …AND…Is turned on(Cupboard) | …THEN start countdown timer -
WHEN…
timer reaches zero (0)| …AND…Is turned on(Cupboard) | …THENTurn offCupboard light
In 1. it is for the Fibaro dimmer-2 not needed to first turn on the cupboard light and then set brightness, setting brightness when the device is turned off, will automatically turn on the light.
2 Likes
Typo?
Blockquote WHEN…
the motion alarm turned off(Motion sensor) | …AND…Is turned ✅ON✅(Cupboard) | …THEN start countdown timer
Where? 
Thanks a mill for that. All worked as a charm.Lesson learned.
I had to set up the brightness as this is Fibaro rgb controller and behaves oddly. Sometimes it sets brightness to the lowest level.
@rafi cool!
Now it is solved, do you mind changing the title of this topic to a bit (?) less explicit??
And pls give the solution credit by marking it solved 
