Motion Lights App Removed But Lights Keep Shutting Off

🛎️ Get Help
1

I used to have a motion rule set up to turn on the downstairs lights automatically when you use the stairs. The motion detector has since been moved and well the wife never trusted the automatic shut off of the lights because every time she went to check on them, she tripped the motion sensor. BUT that's a different story =]

Anyways I removed the motion app but now the lights turn off right away when you turn them on.
It's not in use by the app anymore. The logging doesn't show what turned off the light either.

dev:972021-08-26 12:41:24.597 pm infoMotion Sensor: motion is active

dev:372021-08-26 12:41:20.287 pm debugdescMap:[raw:CAE501000808000020FF, dni:CAE5, endpoint:01, cluster:0008, size:08, attrId:0000, encoding:20, command:0A, value:FF, clusterInt:8, attrInt:0]

dev:382021-08-26 12:41:20.277 pm debugdescMap:[raw:556E01000808000020FF, dni:556E, endpoint:01, cluster:0008, size:08, attrId:0000, encoding:20, command:0A, value:FF, clusterInt:8, attrInt:0]

dev:372021-08-26 12:41:18.499 pm debugdescMap:[raw:catchall: 0104 0006 01 01 0040 00 CAE5 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CAE5, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:372021-08-26 12:41:17.173 pm infoDownstairs Light 1 was turned off

dev:372021-08-26 12:41:17.169 pm debugdescMap:[raw:CAE50100060800001000, dni:CAE5, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]

dev:372021-08-26 12:41:16.877 pm infoDownstairs Light 1 was turned on

dev:372021-08-26 12:41:16.872 pm debugdescMap:[raw:CAE50100060800001001, dni:CAE5, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0]

dev:372021-08-26 12:41:15.493 pm debugdescMap:[raw:catchall: 0104 0006 01 01 0040 00 CAE5 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CAE5, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

I cannot figure this out. I tried to remove the bulbs and re-add them but it recognizes them as previously added.

2

I tried deleting the group and recreating it... still the same thing.
This is frustrating....

3

If you open the light on the device page, is there anything in the 'In Use By' area at the bottom of the page?

4

Nope. Just the group and Google Home

The motion detector is not in use by anything now either.

image
image915×73 1.88 KB

5

Alexa has "hunches" that turn things on and off as she sees fit. Supposedly it learned from past usage or something? It sure messes with things to have that active.

And I understand Google might have something similar, but I don't use Google for home automation. So I would remove it from the Google integration, or see if there is some predictive software in Google itself.

1 Like
6

Google Home is doing this to you.

1 Like
7

That's all I can think fo too, but I cannot find any options (ala predictive hunches) in Google Home that might cause this...

Assuming this is a real thing with Google (and not just due to a routine a user may have set up long ago and since forgotten about), do you (or anyone else!) know specifically where/how this "feature" is managed within the Google Home or Google Assistant apps?

Thanks!

8

I don't personally know. But if you start a topic about it, someone probably does. This just came up a couple of days ago, and someone had the same problem as you (but with a removed RM rule). You can easily prove it for yourself by removing this device from Google Home as a test. Evidently, with whatever setting it is, the actions of an app regularly doing something causes Google Home to copy that and do it for you -- so helpful.

2 Likes
9

Roger that - yeah, I don't doubt it's true, but I can't find any setting buried anywhere that might be related... I may be missing something obvious or maybe Google is just up to shenanigans behind the curtain. Sadly, that wouldn't surprise me either. Thanks for your insight -- it's appreciated!!

10

I cannot find an equivalent to hunches in google home either. I've had a search on the web and my early searches are not throwing anything up either.
As suggested above, if you can remove the device from GH, give it a go and see if it stops turning off.

1 Like
11

It wasn't Google Home. I removed it and the group and it still did it.

dev:972021-08-27 10:41:38.135 am infoMotion Sensor: motion is active

dev:972021-08-27 10:41:24.122 am infoMotion Sensor: motion is inactive

dev:372021-08-27 10:41:24.038 am infoDownstairs Light 1 was turned off

dev:372021-08-27 10:41:23.954 am infoDownstairs Light 1 was turned on

dev:382021-08-27 10:41:23.334 am infoDownstairs Light 2 was turned on

I removed the battery from the motion sensor too. Still did it....

1 Like
12

Removed the motion sensor from the hub...not just the battery
Still does it.

Think we're going to have to go with normal bulbs for this section

13

Maybe I missed it, but what brand/model (bulb? switch?) is doing this? Maybe that will be a clue to someone.

14

Sengled Element Classic

  • manufacturer: sengled
  • model: E12-N14

It's the BR30's

15

Have you looked at the In Use By section at the bottom of the device page for Downstairs Light 1 and Downstairs Light 2? What else is there?

16

Nothing.
I removed all the items it was used by. The group has been removed and the Google Home access has been removed as well.

I removed the motion sensor too.

17

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.