Motion Lighting Gone Rogue Or Something Else


Recently I have been seeing a light that is part of a Motion Lighting configuration turning off when the time is out of the normal range. This light is only automated to turn off by Motion Lighting. I am trying to figure out how to troubleshoot this.

My ML config is set to turn on “Hue Color Candle 2” at night when motion is detected. It turns on and set it to Red. Light turns off 1 minute after motion stops so usually 2 or so minutes when accounting for the motion sensor to clear.

I forgot to get a shot of the app this morning but I have it set automate until 5:45am every day. Below is the shot of the logs where the light goes on and off. How to I figure out why the light is turning off and what should I do about it? I have deleted and recreated the routine already and that did not seem to help.

Thank you!

There are separate time restrictions for turning on and turning off. Be sure you have it selected appropriately.

Good advice.

The times check out with the correct night start and morning stop. In the logs I see at7:36am on and off at 7:48am. That does not match what I would expect from the Motion Lighting. That is usually much shorter.

How do I know what app:201 is as shown in the logs?

App settings:

Also very interesting that just now at ~930pm this light turned on as RED. That should not happen for another 20 or so minutes.

Only this Motion Lighting acts on this light.

Anybody else having trouble with the timing or timing post time change (from DST) with HE?

You might want to check the “in use by” section of the device to verify that it is not being used by any other rule.

I now believe the app:201 is an old or removed app. If I click info from Logs I get a 500 page.

How do we determine what a app is from the Logs? What do I need to do to find app:201?


Something is really weird. I have completely removed Motion Lighting and all child instances. The lights for each rule turn off.

If I add the Motion Lighting App back and recreate apps I observer two things:

  1. If there is not motion on the configured motion sensor OUTSIDE the configured time range the lights stay on.
  2. If the motion sensor detects motion OUTSIDE the configured time the light turns off.

This is happening for all of my Motion Lighting Apps. The removal/reconfigure is repeatable and consistent. It is interesting that the light does not turn ON outside the range and the child apps work correctly.

Anybody see similar things on their hub?

Do not turn off from what? Please show logs wrt all of the things you are describing. Turn on logging in the ML instance. Do this with the simplest case possible.


Typo. Should be "The lights for each rule turn off."

Here are logs for my "Hue color candle 2 ". A Hue light bulb that my Motion Lighting App is set to to turn on to Red at level 1 between 10:00pm and 5:45am.

I manually turned on the Hue color candle 2 at 12:23:51 pm. I took no action to show that time can pass without the light turning off.

You can see the Upstairs Hallway Motion/Light Sensor goes active at 12:37.11 pm. Triggered this by walking by.

Upstairs Hallway Motion/Light Sensor goes INACTIVE at 12:37.27 pm.

Hue Color Candle 2 is turned off at 12:38.28 pm.

What I hope to show here is that the Motion Lighting App seems to be turning off the Hue Color Candle 2 OUTSIDE of the configured Motion Lighting time. Removing the child app stops this behavior. Recreating the child app causes the behavior to return.

I can reproduce this will all motion lightning apps. I can reproduce this with non-Hue lights. App settings are shown in an early post.

Thoughts on this?

Turn on logging for Motion Lighting and show those logs.