Has something been changed with the delay parameter for commands? I haven’t changed anything on my end but they seem to have stopped working. Anyone have any ideas?
Example from the docs:
mySwitch.on([delay: 2000])
Trying this out in a bare bones app just to test, my switch doesn’t turn off at all.
Well, it is clearly a bug that was introduced after their latest changes. And I figured out a workaround for now.
That parameter that you have for the delay you have to divide it by a number around 500 and you will get the behavior that is expected. I cannot tell you the exact correction factor but 500 works for me. So basically the old code becomes:
Known issue, discussed on a couple of forum threads. Milliseconds are being processed as seconds. (So a factor of 1,000 for now.) ST is aware of it, so there should be a fix eventually.
@bravenel or @rboy might remember where it was previously discussed.
1 Like
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
5
Interesting, was not aware but that does explain a lot of what I’m seeing. Through I’m super curious as to why ST would break such a fundamental things and not fix it right away! Poor SDLC for even letting something as basic as this come in. I wonder if anyone even does code reviews or it’s a free for all?