Jump to content

Query in Schedules


Guest

Recommended Posts

What purpose does Query serve in Schedules?

 

If I have some lights scheduled to go off @ 11pm…and someone accidentally turns them off @ 7pm…If I schedule a Query @ 9pm…will they come back on?

Link to comment

HAS,

 

As you may already know, INSTEON - including others except Lutron - does not respond back with the status of the command that was issued; it simply acknowledges the receipt of the command (like echo). [Lutron is suing anyone who does].

 

As such, the only way to retrieve the current status of a device is by explict request for status which is a very expensive operation (2-3 seconds per command). Therefore, and in order to make ISY more responsive, the state of all the devcies in ISY is determined by algorithmic "predictions" of what the outcome of any command should be (regardless of where/how it was issued) and not by explicit status requests. These predictive alogrithms are accurate 99% of the time with a deviation of +/- 1%.

 

The scheduled query is there to do:

1. Address that 1% of the time where the device does not acknowledge the command but it actually performs the operation or vice versa

2. The +/- 1% deviation

3. Allow you to note if any of the devices have stopped responding (red exclamation marks)

 

If you are not running any "level" sensitive triggers and do not actively seek the most accurate state of all your devices, then you may safely remove this schedule with no impact to anything else. You can then manually run a query in case you think ISY is out of synch with the devices.

 

I hope this answered your question,

With kind regards,

Michel

 

What purpose does Query serve in Schedules?

 

If I have some lights scheduled to go off @ 11pm…and someone accidentally turns them off @ 7pm…If I schedule a Query @ 9pm…will they come back on?

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...