I have noticed what appears to me to be a difference between how a query operates from the administrator console to how a query operates from a program.  For example, if I query my thermostats via the admin console, much more information is pulled from the thermostat.  I can even see all the communication traffic and thermostat data in the ISY log.  However, if I do the, "Set Thermostat Query" command from a program, I don't get much information at all.  In the log, I can see the query command issued from the program but little to no response from the thermostat.

 

Is this something that is normal behavior for the query command from a program or am I looking at an issue with my ISY?

 

Thanks for the information!

I really can't comment on the program aspect but know there is indeed a difference from the 3:00 AM Query. And those invoked from a user by right mouse clicking on any Insteon hardware device in the *Device Tree*.

 

Off the top of my head I don't recall why the system does this but its not a bug and is by design.

Yes, exactly.  I initially noticed that the 3:00 AM query is different, which made me start to investigate the query in a custom program.

 

I suppose the next question would be, is there a way for a program to invoke the query command that is used in the admin tool?

Yes, exactly. I initially noticed that the 3:00 AM query is different, which made me start to investigate the query in a custom program.

 

I suppose the next question would be, is there a way for a program to invoke the query command that is used in the admin tool?

As of the writing no but you can certainly post this question under the feature request forum and perhaps this can be added in future releases.

 

I noticed the discrepancy when I turned off query on reboot to speed up my boot times. I noticed the actual (different) states like the ramp rate wasn't fully updated unless you manually selected query vs 3:00 AM query?!? [emoji53]