so i am writing a device type purely as a Sonos TTS Announcer using VoxCommando it would work extremely well if only the following code would actually work as i need a delay when dissolving and creating sonos groups. cmds = [] cmds << Command one cmds << Command two cmds << Command two delayBet…

Not sure if it’s related, but the delay parameter in commands like: switch.on([delay: 2000]) is currently broken and they’re working on a fix. Not exactly the same problem though, in that case it’s reading 2000 as seconds instead of milliseconds. But maybe both are part of some wider underlying pr…

[image] Fuzzyligic: is there a maximum time limit for the delay of 3 digits rather than 4? No. Most of the z-wave DHs have delays of up to 5000 ms.

ok well for me on the UK servers all options to delay in the device handler do not work. It’s the second time I’ve noticed this but I definitely need the delay or things don’t work

Write to support, get a ticket number, and write to Jody.

Jody, is there an issue with device handlers delay between also? That could explain a lot of weird device failures the last few days.

Bruce, Yes there is. The delay in and delay between both used a seconds to milliseconds conversion that was not moved over to the new scheduler. We have a hotfix to put the conversion back in and a unit test to make sure that it’s not removed unintentionally in any future updates.

Ok thanks guys, I thought I was losing my mind :slight_smile: I didn’t raise a ticket, but am happy to wait. I do hope this hotfix hits the EU shard as well and not just the US ones!

[image] jody.albritton: Bruce, Yes there is. The delay in and delay between both used a seconds to milliseconds conversion that was not moved over to the new scheduler. We have a hotfix to put the conversion back in and a unit test to make sure that it’s not removed unintentionally in any futur…

[image] Mike_Maxwell: probably could have headed off a few issues had it been mentioned then. A great number of z-wave commands rely on delay-between measured in milliseconds. Devices have been misbehaving. Hmmmm.

delayBetween(cmds,<timeinms>) does not work

Developer Programs Writing Device Types

jody.albritton (Jody) March 30, 2016, 9:59pm 6

Delay in milliseconds should be restored in a hotfix tomorrow. If you do have a ticket number send it to me anyway.

Alternative to The Flasher and The Big Switch

Topic		Replies	Views
Command delay parameter broken? Writing SmartApps	8	1737	May 4, 2016
Delay not working? SmartApps & Automations	33	5399	April 19, 2016
Syntax: How to delay a command? General Discussion developers	15	3778	April 11, 2017
Sleep n seconds in Device Type General Discussion archive_developers	2	655	December 19, 2013
Edge Driver support for "delayBetween" Writing Edge Drivers	0	328	January 7, 2023

delayBetween(cmds,<timeinms>) does not work

Related topics