Hello
I'm currently running dzvents 3.0.9. I'm wondering whether the command item.switchOn().at("18:35") and item.switchOff().at("18:36") will stay active until item.cancelQueuedCommands() is sent. If not, how should it be handled?
Thank you
Mastering the "at" command [Solved]
Moderator: leecollings
-
Number8
- Posts: 374
- Joined: Friday 23 May 2014 7:55
- Target OS: Linux
- Domoticz version: 2022.1
- Location: Saint Pierre de Jards
- Contact:
Mastering the "at" command
Debian buster on NUC and three RPi with buster.
- waaren
- Posts: 6028
- Joined: Tuesday 03 January 2017 14:18
- Target OS: Linux
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: Mastering the "at" command [Solved]
Underlying the at method is translated to an afterSec method with the calculated number of seconds. So behavior is the same and it stays active until cancelled explicitly (using the cancelQueuedCommand() or -implicitly (by a domoticz restart)Number8 wrote: Saturday 18 July 2020 19:37 Hello
I'm currently running dzvents 3.0.9. I'm wondering whether the command item.switchOn().at("18:35") and item.switchOff().at("18:36") will stay active until item.cancelQueuedCommands() is sent. If not, how should it be handled?
Thank you
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
Who is online
Users browsing this forum: No registered users and 1 guest