actions

Adjust Device Refresh Time

Invoking this action item will allow you to programmatically change the refresh frequency of an individual device. Perhaps an example would help to explain it best.

Say you have an automated lawnmower, and you'd like to track its function based on what it was doing at the time. In other words, you might want to check on its status less frequently when it's charging as compared to when it was mowing. You can now do this by setting the refresh frequency using the "Adjust Device Refresh Time" Action Item.

1. Create a new Action Item that sets the refresh frequency of the lawnmower device to 5 seconds (or whatever number of seconds you choose). This will be the frequency when the lawnmower is mowing.
2. Create a second Action Item that sets the refresh frequency of the lawnmower device to 30 seconds (or whatever number of seconds you choose). This will be the frequency when the lawnmower is charging.
3. Create an Indigo Trigger that fires when the mower device state becomes "Mowing" (or whatever is the appropriate state value for your purpose.) This trigger will fire the MOWING action item.
4. Create an Indigo Trigger that fires when the mower device state becomes "Charging" (or whatever is the appropriate state value for your purpose.) This trigger will fire the CHARGING action item.

Note

If you elect to use the String Type device, all GhostXML device states are stored as strings, so you'll need to convert them as needed for comparisons other than string comparisons.

Note

When you have set the refresh frequency of a GhostXML device to something other than a standard refresh frequency, the device's configuration dialog will show "Custom". You can change the value from Custom to a standard frequency from the device configuration dialog at any time if you choose.

---

Refresh Data for All Devices

Invoking this action item will cause all devices to refresh their data. It will not cause a new CSV observations to be saved.

---

Refresh Data for Device

Invoking this action item will cause a single specified device to refresh its data. It will not cause a new CSV observation to be saved.