Zigbee light turns on daily but can't find corresponding routine

[sd_mark]

My Kitchen light is a Sylvania A19 Zigbee bulb.

As part of my Almost Evening routine, it comes on an hour before sunset.

As part of no routine at all, it turns off at sunset. Every day. (I do have an Evening routine that runs at sunset, but it’s not in there.) I can see the Off event in the app history, but I can’t tell where it the Off command came from.

In the AWA Devices list, I found Summary-lighting-group. Is this just recording the status and levels of some of the lights? Kitchen is in the group. I can’t find this group in the Android app.

Why is the Kitchen light turning off at Sunset? I will try to capture the Zigbee event in logcat but so far I haven’t even found the corresponding routine.

[jkp]

First question we always ask when someone has a device that acts on its own… do you use Alexa? If yes, check if Hunches is enabled and creating Routines in Alexa that turns the light off. Turn off Hunches if you don’t need it and remove the Routine it creates.

[sd_mark]

Thanks @jkp. Yes I use Alexa. I found Hunches in the app (no thanks to the awful Alexa AI that sent me on a wild goose chase - ugh). .There are five suggested hunches, things like “turn off lights while you’re away,” none of them active. It looks like it executed a hunch in August, assigning an inactive bulb to a room. I just clicked Undo on that. The Hunches suggestions toggle is Off..

[orangebucket (Graham)]

It may be worth checking the Routines tab in the device details in case there are any preset routines enabled that don’t also show in the main Routines tab. The mobile app does like to hide stuff.

As mentioned, Alexa ‘hunches’ are known for creating routines without you realising so it may be worth checking beyond the hunches settings (I don’t use Alexa and I got the impression hunches never made it to the UK). Also check any other voice assistants and other third party apps that you have linked to SmartThings.

@sd_mark

In the AWA Devices list, I found Summary-lighting-group. Is this just recording the status and levels of some of the lights? Kitchen is in the group. I can’t find this group in the Android app.

Before all the Home Insights branding came along, the dashboard at the top of the Favourites page was referred to as the Location ‘summary’. The lights selected for the lighting summary button are placed in the Summary-lighting-group which is hidden from the mobile app.

[sd_mark]

@orangebucket

It may be worth checking the Routines tab in the device details in case there are any preset routines enabled that don’t also show in the main Routines tab.

In the mobile app, device > Routines shows no active routines.

In AWA, In Use By shows several expected routines, nothing at sunset, plus Summary-lighting-group.

@orangebucket

Before all the Home Insights branding came along, the dashboard at the top of the Favourites page was referred to as the Location ‘summary’.

So this is an artifact that is no longer accessible at all? The app’s Home page has a “Dashboard” section showing energy, humidity, count of devices turned on, temperature, and count of offline devices. Below that is a “Favorites” section listing first 9 manual routines and then 26 of my 40 devices, many that I haven’t used it months. I don’t see a direct correspondence to Summary-lighting-group devices. Basically the Favorites section on the Home page is a big, useless jumble that I never use–I go straight to the Devices and Routines pages if I have to open the app at all.

[orangebucket (Graham)]

Sorry, I confused the issue by referring to the app Home page as the Favourites page.

I’m talking about the Lighting button in the dashboard section of the home page. You should find the selected switches/lights match the Summary-lighting-group.

Aside: I only have ‘favourites’ so the app will stop banging on about them. I guess there are many users who use the mobile app for day to day control but I am not one of them. Also for me the whole idea of ‘favourites’ should be to avoid having to open the app in the first place.

[sd_mark]

Thanks @orangebucket, I see the “Lights” list now. It also includes some TP-Link outlets, one of which controls a Synology NAS. I certainly would not want that to turn off and on, or to “dim,” when controlling lights. I use manually-programmed routines for All [lights] Off and All On.

Sunset in San Diego was at 6:54pm today. Here is the Zigbee trace of Kitchen bulb around that time. The main “off” came at 01:53:38.019743083Z: “hub handled command: 9b..e6:main:switch:off“. Is there any way to figure out where that Off command originated?

2026-03-12T01:52:11.390331169Z INFO Zigbee Switch  hub handled ZigbeeRxMessage { send_type: 0x0, src_addr: 0xE5AF, src_endpoint: 1, dst_addr: 0x0, dst_endpoint: 1, profile_id: 0x104, cluster_id: 0x6, lqi: 0xFF, rssi: 0xFFFFFFBF, body: [0x08, 0x2D, 0x0A, 0x00, 0x00, 0x10, 0x01] }
2026-03-12T01:52:11.391547419Z INFO Zigbee Switch  hub emitting event 9b..e6: {“component_id”:“main”,“capability_id”:“switch”,“attribute_id”:“switch”,“state”:{“value”:“on”}}
2026-03-12T01:52:11.447886794Z TRACE Zigbee Switch  Received event with handler device_lifecycle
2026-03-12T01:52:11.448347377Z INFO Zigbee Switch  <ZigbeeDevice: 9b..e6 [0xE5AF] (Kitchen)> received lifecycle event: update

2026-03-12T01:53:38.019743083Z INFO Zigbee Switch  hub handled command: 9b..e6:main:switch:off 
2026-03-12T01:53:38.020584620Z INFO Zigbee Switch  hub sending: Zigbee message (9b..e6): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0xe5af, dest_endpoint: 0x1, profile: 0x104, cluster: 0x06, data: [01, 00, 00]>
2026-03-12T01:53:38.171360278Z INFO Zigbee Switch  hub handled ZigbeeRxMessage { send_type: 0x0, src_addr: 0xE5AF, src_endpoint: 1, dst_addr: 0x0, dst_endpoint: 1, profile_id: 0x104, cluster_id: 0x6, lqi: 0xFF, rssi: 0xFFFFFFBF, body: [0x08, 0x75, 0x0B, 0x00, 0x00] }
2026-03-12T01:53:38.172948275Z INFO Zigbee Switch  hub emitting event 9b..e6: {“component_id”:“main”,“capability_id”:“switch”,“attribute_id”:“switch”,“state”:{“value”:“off”}}
2026-03-12T01:53:38.179236754Z TRACE Zigbee Switch  Received event with handler device_lifecycle
2026-03-12T01:53:38.179667872Z INFO Zigbee Switch  <ZigbeeDevice: 9b..e6 [0xE5AF] (Kitchen)> received lifecycle event: update
2026-03-12T01:53:38.194059173Z INFO Zigbee Switch  hub handled ZigbeeRxMessage { send_type: 0x0, src_addr: 0xE5AF, src_endpoint: 1, dst_addr: 0x0, dst_endpoint: 1, profile_id: 0x104, cluster_id: 0x6, lqi: 0xFF, rssi: 0xFFFFFFBE, body: [0x08, 0x2E, 0x0A, 0x00, 0x00, 0x10, 0x00] }
2026-03-12T01:53:38.195076289Z INFO Zigbee Switch  hub emitting event 9b..e6: {“component_id”:“main”,“capability_id”:“switch”,“attribute_id”:“switch”,“state”:{“value”:“off”}}
2026-03-12T01:53:38.200510237Z TRACE Zigbee Switch  Received event with handler device_lifecycle
2026-03-12T01:53:38.201045470Z INFO Zigbee Switch  <ZigbeeDevice: 9b..e6 [0xE5AF] (Kitchen)> received lifecycle event: update

2026-03-12T01:54:27.280394953Z INFO Zigbee Switch  hub handled ZigbeeRxMessage { send_type: 0x0, src_addr: 0xE5AF, src_endpoint: 1, dst_addr: 0x0, dst_endpoint: 1, profile_id: 0x104, cluster_id: 0x8, lqi: 0xFE, rssi: 0xFFFFFFBF, body: [0x08, 0x2F, 0x0A, 0x00, 0x00, 0x20, 0xFE] }
2026-03-12T01:54:27.281619828Z INFO Zigbee Switch  hub emitting event 9b..e6: {“component_id”:“main”,“capability_id”:“switchLevel”,“attribute_id”:“level”,“state”:{“value”:100}}
2026-03-12T01:54:27.294145245Z TRACE Zigbee Switch  Received event with handler device_lifecycle
2026-03-12T01:54:27.294603578Z INFO Zigbee Switch  <ZigbeeDevice: 9b..e6 [0xE5AF] (Kitchen)> received lifecycle event: update

[Declankh]

Don’t forget that manually run routines (scenes) don’t feature in the device->routines tab even if the device is referenced in a manually run routine. Also manually run routines can be called from automated routines or from alexa

[orangebucket (Graham)]

@sd_mark

Is there any way to figure out where that Off command originated?

Not that I am aware of. It pretty much only confirms that the switch off is being initiated via SmartThings, rather than SmartThings just receiving a report from the light.

[sd_mark]

@Declankh

Don’t forget that manually run routines (scenes) don’t feature in the device->routines tab even if the device is referenced in a manually run routine. Also manually run routines can be called from automated routines or from alexa

Good point. I’m relying on the “In Use By” section of the device’s AWA page. Unfortunately that doesn’t show any events at sunset.

[jkp]

some users elect to remove the device, which removes it from any Routines… then add the device back.

[orangebucket (Graham)]

@sd_mark

As part of my Almost Evening routine, it comes on an hour before sunset.

As part of no routine at all, it turns off at sunset.

Just a thought, could it be that it is being turned off because it has been on for an hour, or it has been an hour since it was turned on, rather than because it is sunset?

[sd_mark]

I found the problem. I have this Smart lighting routine in the app. Note that it only runs “0 minutes After Sunrise”:

However in AWA, that Rule is recorded as follows:

Why does it have a second condition to turn off at Sunset? It’s very clear in the routine’s Time detail that there is no Sunset condition:

But wait: when I open the Sunrise condition, there is a toggle “Turn off at sunset”:

Turning off that toggle should fix it, but seriously, why control the Sunset behavior from the Sunrise rule? That’s why there is a Sunset rule. And when you add a subsidiary rule, put it in the main Time description: “0 minutes After Sunrise and 0 Minutes after Sunset.”

[sd_mark]

@jkp

some users elect to remove the device, which removes it from any Routines… then add the device back.

Great minds… It was when I was preparing to add a “new sunrise” lighting routine, before deleting the old routine, that I discovered that the Sunrise condition can also control Sunset.

Tip to future users: if something unexpected is happening at Sunset, check your Sunrise rules.

[orangebucket (Graham)]

Interesting. Given that Smart Lighting creates rules I had assumed they would show up in the app history.

Bear in mind that Smart Lighting is about handling common lighting and switching scenarios which are defined as ‘recipes’. If the developers haven’t allowed for a particular scenario then Smart Lighting can’t handle it. You are basically being guided through the process of selecting a recipe (a rule template) and filling it in.

The recipe starts by asking you which action you require and then it will present you with a limited choice of conditions that can trigger this action. For time you can have either sunrise or sunset but not both. As the action is to turn something on the developers have allowed for turning it off again at the end of the day or night.

[sd_mark]

@orangebucket

As the action is to turn something on the developers have allowed for turning it off again at the end of the day or night.

I kinda get that but IMO it would be, um, smarter (i.e. clearer and more obvious) to let the user create another routine if they want to turn it off at sunset. It is counterintuitive for an Off action to be hidden behind what the UI says is an On action. If they really need both in one, then the Action should say “On and Off” and the Time should say “Sunrise and Sunset”.