Are there any guidelines as to how long one should wait before reading a device's data after querying the device? I'm trying to gather CURRENT data from Insteon Motion Sensor II, Light Level of 2476/7 switches, and Thermostat. 

22 minutes ago, shunsader said:

Are there any guidelines as to how long one should wait before reading a device's data after querying the device? I'm trying to gather CURRENT data from Insteon Motion Sensor II, Light Level of 2476/7 switches, and Thermostat. 

If the MS II is battery powered, I don't think you're going to get current data, as I believe it only periodically updates to save battery.  If it's powered by USB, then I suspect you can query it, wait a bit for the query to complete and be good to go, though I think the data should be current in the ISY, as the data is sent as it changes.  Same for the switches and thermostat, though I don't have any Insteon thermostats.

You can run a program to query a battery powered MS II upon motion detection, and it will update the values, such as this:

MSIIQuery - [ID 00FF][Parent 00DF]

If
        'Devices / dirGarage / msGarage' is switched On
 
Then
        Set 'Devices / dirGarage / msGarage' Query
 
Else
   - No Actions - (To add one, press 'Action')
 

 

@Bumbershoot, is there a reason to query right after the motion detection? Perhaps because the device communications have been 'awakened'?

6 minutes ago, shunsader said:

@Bumbershoot, is there a reason to query right after the motion detection? Perhaps because the device communications have been 'awakened'?

Yes.

5 minutes ago, gzahar said:

Yes.

But what purpose is there to query when it just reported that it was switched On ?

Edited September 13, 20205 yr by asbril

14 minutes ago, asbril said:

But what purpose is there to query when it just reported that it was switched On ?

There is other data besides motion.

1 minute ago, gzahar said:

There is other data besides motion.

I understand, but I would assume that once it sends status then it also sends the other data ?????

18 minutes ago, asbril said:

But what purpose is there to query when it just reported that it was switched On ?

@asbrilI want the Luminance and Temperature values. I was hoping to be able to use these to determine whether I can open an East facing shade, or close during the winter.

Just now, shunsader said:

@asbrilI want the Luminance and Temperature values. I was hoping to be able to use these to determine whether I can open an East facing shade, or close during the winter.

My point/question is only that when the MS establishes communication and the AC registers that it is switched On, I would assume that at the same time it sends all data. If that is not the case, then I understand the need to query.

2 minutes ago, asbril said:

My point/question is only that when the MS establishes communication and the AC registers that it is switched On, I would assume that at the same time it sends all data. If that is not the case, then I understand the need to query.

That is not the case.

@asbril, I'm noticing on my Console that data is stale, even though I've been tripping the outside motion sensors. Only when I use the "Query" button on the console do the numbers update. What's more is that there seems to be a hitch that I'm missing, because the data that I'm stuffing into the variables doesn't quite match the data that I see in the Level 3 Event data. Perhaps I need to upgrade to V 5.2.0. I upgraded last week from 4.8.0 to 5.0.14. I have a relatively large build in my home, and little time to fix things that don't go well during an upgrade.

Just now, shunsader said:

@asbril, I'm noticing on my Console that data is stale, even though I've been tripping the outside motion sensors. Only when I use the "Query" button on the console do the numbers update. What's more is that there seems to be a hitch that I'm missing, because the data that I'm stuffing into the variables doesn't quite match the data that I see in the Level 3 Event data. Perhaps I need to upgrade to V 5.2.0. I upgraded last week from 4.8.0 to 5.0.14. I have a relatively large build in my home, and little time to fix things that don't go well during an upgrade.

Understood. Some have issues with upgrade to 5.2, but I did not. However I had issues when going from 5.0.16 to 5.1, and then reverted back to 5.0.16, before finally going to 5.2 .

It is important that you make backups before upgrading.