Tuning off Virtual Dimmer, high ST resource usage

#1

This a note so much a design help question but an operational query.
In the old C0RE I had a piston that, when the bedroom light was physically tuned off, it also tried to turn off a virtual dimmer which was attached to the 2 bedside lights. It always too 10 seconds for the bedside lights to turn off after the bedroom light went off. Never could get it to go off at the same time.
ST contacted me while I was trying to get this to function saying my resource usage spikes every time I execute this piston and wanted to know what I had running.
I ended up removing that line to stop the code spikes.
I have tried the same thing now that I’m in webC0RE and I get the same 10 second delay :frowning:
Does anyone have any insight into what might be causing this phenomenon?
I have included the end chunk of my bedroom piston. Logs never have anything bad to say.
+251ms â•‘â•‘Condition group #15 evaluated true (state changed) (10ms)
+254ms ║║Cancelling statement #18’s schedules…
+260ms â•‘â•‘Executed virtual command [Master Bedroom Bedside VD, Master Bedroom Light].wait (0ms)
+261ms â•‘â•‘Requesting a wake up for Wed, Nov 8 2017 @ 10:11:01 AM PST (in 300.0s)
+267ms â•‘â•šExecution stage complete. (55ms)
+268ms â•‘Setting up scheduled job for Wed, Nov 8 2017 @ 10:11:01 AM PST (in 299.995s)
+289ms â•šEvent processed successfully (289ms)

image

#2

how many devices in the device variable?

is there other things the piston does? a green snapshot would be helpful/

#3

The bedside just has 2 lights on the virtual dimmer.
The piston is a template I wrote and have applied it all over the house without issue. It’s just strange that whatever endless loop I’m causing migrated from both iterations of C0RE but written totally differently. The old C0RE version had 2 pistons involved in each virtual dimmer and I redid them to be only one.
Here is the Bedside piston and the Master bedroom calling piston.

Bedside
Bedside.png1178Ă—1271 140 KB

MB
MB.png1178Ă—1016 104 KB

#4

probably because of the only when restriction at the top of the piston. if you look at the first piston y4aqt at lines 51 & 52 it refers to other modes outside of the only when restriction so that will not work.

there may be other issues, but that one stands out a glance.

request: when replying to this post please use the reply button on this post and not the blue reply button at the bottom of all posts. the blue reply button does not notify the poster you are replying to by default.

#5

Yeah, I only use this during the Evening mode. It always turns off the virtual bedside dimmer, it just takes 10 seconds for some strange reason.
Thanks for clarifying Reply from Reply, wan’t aware of the functionality difference.

#6

say there is motion 1 minute before mode changes from evening to night and with motion the lights get switched. then motion changes to inactive but by this time mode has changed from evening to night. in this case did you still want the wait then turn off at line 69 & 70 to be executed?

for the 10 second turn off have you checked in the logs when the turn off switch is executed are there any errors in the ST IDE logs?