Stubborn Caseta switch won't turn off on timer

#1

1) Give a description of the problem
I have a bunch of lights set to turn off at sunrise minus X minutes. I have one Caseta switch that refuses to cooperate. It will not turn off when the piston executes every day. The switch works fine because it turns on as programmed every night at sunset but it absolutely refuses to turn off when the piston runs in the morning. All other lights on the piston turn off as expected.

One thing that may be an issue: the icon in the ST app sometimes doesn’t reflect the actual state of the light. For example, if I open the ST app, sometimes it will show the light as OFF but when I actually walk downstairs and check, it shows as ON. When I click the icon in the app, it will change to ON, but no change to the light (they stay on) but if I click it again once the icon shows ON the icon will show OFF and the lights will turn off. So there is a mismatch sometimes between what shows in the app versus what state the light is actually in.

I don’t know if this has anything to do with the issue as to why the lights will not turn off at sunrise. I posted this same question in the Smartthings community forums but no one was able to answer my question, they just kept suggesting to unplug the hub and plug it back in.

For some further info: the hub is located less than 20 feet away from this Caseta switch. There isn’t a range issue because the lights will turn on/off with no problem when I use the ST app manually. I have removed and re-added this switch to my Caseta hub/ST hub multiple times and it won’t fix the issue.

2) What is the expected behaviour?
Light should be turning off at sunrise minus X number of minutes.

3) What is happening/not happening?
Lights will not turn off as programmed.

**4) Post a Green Snapshot of the piston![image|45x37]

download%20(1)
download (1).png1178×640 64.1 KB

5) Attach logs after turning logging level to Full
10/27/2022, 6:59:59 AM +58ms
+1ms ╔Received event [Home].time = 1666868400000 with a delay of -942ms
+206ms ║RunTime Analysis CS > 17ms > PS > 141ms > PE > 47ms > CE
+208ms ║Runtime (38747 bytes) successfully initialized in 141ms (v0.3.114.20220203) (206ms)
+209ms ║╔Execution stage started
+252ms ║║Comparison (time) 25199273 happens_daily_at (time) 1666869900000 = false (1ms)
+254ms ║║Cancelling condition #2’s schedules…
+255ms ║║Condition #2 evaluated false (39ms)
+259ms ║║Cancelling statement #2’s schedules…
+265ms ║║Requesting time schedule wake up at Fri, Oct 28 2022 @ 6:55:00 AM EDT
+267ms ║║Cancelling condition #1’s schedules…
+268ms ║║Condition group #1 evaluated false (state changed) (53ms)
+274ms ║║Comparison (time) 25199329 happens_daily_at (time) 1666869900000 = true (0ms)
+275ms ║║Time restriction check passed
+277ms ║║Cancelling condition #6’s schedules…
+278ms ║║Condition #6 evaluated true (6ms)
+283ms ║║Cancelling statement #6’s schedules…
+288ms ║║Requesting time schedule wake up at Fri, Oct 28 2022 @ 7:00:00 AM EDT
+291ms ║║Cancelling condition #5’s schedules…
+291ms ║║Condition group #5 evaluated true (state changed) (20ms)
+294ms ║║Cancelling statement #7’s schedules…
+303ms ║║Skipped execution of physical command [Front Cutout 1].off([]) because it would make no change to the device. (5ms)
+304ms ║║Executed [Front Cutout 1].off (6ms)
+324ms ║║Skipped execution of physical command [Front Foyer Front Porch].off([]) because it would make no change to the device. (16ms)
+325ms ║║Executed [Front Foyer Front Porch].off (18ms)
+344ms ║║Executed physical command [Front Porch Front Door].off() (16ms)
+345ms ║║Executed [Front Porch Front Door].off (18ms)
+352ms ║║Skipped execution of physical command [Stairs 1].off([]) because it would make no change to the device. (5ms)
+353ms ║║Executed [Stairs 1].off (6ms)
+387ms ║║Skipped execution of physical command [Stairs 2].off([]) because it would make no change to the device. (31ms)
+388ms ║║Executed [Stairs 2].off (33ms)
+391ms ║╚Execution stage complete. (182ms)
+393ms ║Setting up scheduled job for Fri, Oct 28 2022 @ 6:55:00 AM EDT (in 86100s), with 1 more job pending
+398ms ╚Event processed successfully (398ms)
10/27/2022, 6:54:59 AM +62ms
+0ms ╔Received event [Home].time = 1666868100000 with a delay of -938ms
+55ms ║RunTime Analysis CS > 17ms > PS > 5ms > PE > 33ms > CE
+58ms ║Runtime (38742 bytes) successfully initialized in 5ms (v0.3.114.20220203) (57ms)
+59ms ║╔Execution stage started
+98ms ║║Comparison (time) 24899127 happens_daily_at (time) 1666869900000 = true (1ms)
+99ms ║║Time restriction check passed
+101ms ║║Condition #2 evaluated true (36ms)
+105ms ║║Cancelling statement #2’s schedules…
+110ms ║║Requesting time schedule wake up at Fri, Oct 28 2022 @ 6:55:00 AM EDT
+112ms ║║Condition group #1 evaluated true (state did not change) (48ms)
+114ms ║║Cancelling statement #3’s schedules…
+129ms ║║Skipped execution of physical command [Dining Room Chandelier].off([]) because it would make no change to the device. (5ms)
+130ms ║║Executed [Dining Room Chandelier].off (7ms)
+149ms ║║Skipped execution of physical command [Door Flood 1].off([]) because it would make no change to the device. (17ms)
+150ms ║║Executed [Door Flood 1].off (19ms)
+157ms ║║Skipped execution of physical command [Door Flood 2].off([]) because it would make no change to the device. (4ms)
+158ms ║║Executed [Door Flood 2].off (6ms)
+166ms ║║Skipped execution of physical command [Foyer Edison].off([]) because it would make no change to the device. (4ms)
+167ms ║║Executed [Foyer Edison].off (5ms)
+179ms ║║Skipped execution of physical command [Front Foyer Chandelier].off([]) because it would make no change to the device. (10ms)
+180ms ║║Executed [Front Foyer Chandelier].off (11ms)
+186ms ║║Skipped execution of physical command [Front Step Flood 1].off([]) because it would make no change to the device. (4ms)
+187ms ║║Executed [Front Step Flood 1].off (6ms)
+193ms ║║Skipped execution of physical command [Front Step Flood 2].off([]) because it would make no change to the device. (4ms)
+194ms ║║Executed [Front Step Flood 2].off (6ms)
+206ms ║║Skipped execution of physical command [Great Room Center].off([]) because it would make no change to the device. (9ms)
+207ms ║║Executed [Great Room Center].off (11ms)
+219ms ║║Skipped execution of physical command [Great Room Left].off([]) because it would make no change to the device. (10ms)
+220ms ║║Executed [Great Room Left].off (11ms)
+240ms ║║Skipped execution of physical command [Great Room Right].off([]) because it would make no change to the device. (18ms)
+241ms ║║Executed [Great Room Right].off (20ms)
+247ms ║║Skipped execution of physical command [Kitchen Side 1].off([]) because it would make no change to the device. (4ms)
+248ms ║║Executed [Kitchen Side 1].off (6ms)
+254ms ║║Skipped execution of physical command [Kitchen Side 2].off([]) because it would make no change to the device. (4ms)
+255ms ║║Executed [Kitchen Side 2].off (6ms)
+266ms ║║Skipped execution of physical command [Master Bedroom lamp].off([]) because it would make no change to the device. (9ms)
+267ms ║║Executed [Master Bedroom lamp].off (11ms)
+273ms ║║Skipped execution of physical command [Pond Side 1].off([]) because it would make no change to the device. (4ms)
+274ms ║║Executed [Pond Side 1].off (6ms)
+280ms ║║Skipped execution of physical command [Pond Side 2].off([]) because it would make no change to the device. (4ms)
+281ms ║║Executed [Pond Side 2].off (6ms)
+292ms ║║Skipped execution of physical command [Shelley Office].off([]) because it would make no change to the device. (8ms)
+293ms ║║Executed [Shelley Office].off (9ms)
+299ms ║║Skipped execution of physical command [Side Yard 1].off([]) because it would make no change to the device. (4ms)
+300ms ║║Executed [Side Yard 1].off (6ms)
+306ms ║║Skipped execution of physical command [Side Yard 2].off([]) because it would make no change to the device. (4ms)
+307ms ║║Executed [Side Yard 2].off (5ms)
+318ms ║║Skipped execution of physical command [Study Lights].off([]) because it would make no change to the device. (9ms)
+319ms ║║Executed [Study Lights].off (11ms)
+332ms ║║Skipped execution of physical command [Upstairs Hallway Spot Lights].off([]) because it would make no change to the device. (9ms)
+332ms ║║Executed [Upstairs Hallway Spot Lights].off (11ms)
+339ms ║║Comparison (time) 24899398 happens_daily_at (time) 1666869900000 = false (0ms)
+340ms ║║Condition #6 evaluated false (4ms)
+346ms ║║Cancelling statement #6’s schedules…
+351ms ║║Requesting time schedule wake up at Thu, Oct 27 2022 @ 7:00:00 AM EDT
+353ms ║║Condition group #5 evaluated false (state did not change) (18ms)
+356ms ║╚Execution stage complete. (298ms)
+358ms ║Setting up scheduled job for Thu, Oct 27 2022 @ 7:00:00 AM EDT (in 300s), with 1 more job pending
+363ms ╚Event processed successfully (363ms)

#2

Two things…

  1. Are you still using webcore in the ST environment? I thought that was dead.
  2. Sending multiple device commands in one webcore command may be flooding your network and the command for your Caseta may be getting lost. Try controlling it in a command by itself.
#3

I’m not familiar with the casita switch, however as a general point, If ST sees the switch as already off, it will not turn it off when webcore tries to. When it turns on via its own schedule, does ST see the switch as on? If not it could be a device handler issue.
There maybe a refresh method you can call before you try to turn it off. I do this with a fibaro relay which auto turns off after 1 sec, but WC does not get updated by the DH.

#4

And another thing you can add is to disable command optimization so that wc sends the off command even if it sees it as being already off.

#5

Ahhh I wasn’t aware that the sunsetting of Samsung support meant that Webcore wasn’t going to work anymore…I guess it makes sense that my lights have been acting goofy lately. It’s weird though, most of my pistons still work.

Is there any further use case for Webcore if it’s not supported within the ST environment anymore? If not, do you know any comparable replacement for Webcore? I have some complex pistons that I’d like to continue using if I can set them up in another app or something like that.

#6

Webcore has a very active and thriving community. I have a little over 100 active pistons and many in the webcore arena have many more. ST was the first smart environment that I set up when I dove into home automation. I liked ST. But when the announcement came that ST was no longer supporting webcore, I moved to Hubitat, and I have been quite impressed. Hubitat has a very active webcore community, and I do not see that going away any time soon. There are several other options other than webcore. I am not familiar with most of them. Node-Red seems to be a popular platform. Like you, I have several quite complex pistons that I just did not want to have to transition to another platform. So, for me, the switch to Hubitat was inevitable.

#7

I’ve just moved to hubitat and am very impressed.
Given the imminent end of WC on ST, I’d advise you to backup all your pistons asap. Also take a red screenshot of each as you have to re select all devices following the migration to HE and that can be tricky for a piston with many devices.