tutorials
One of the features of the GhostXML plugin is that it will automatically disable a device when communication has been unsuccessful (you can adjust the number of failed attempts before the device is disabled). This feature is meant to protect Indigo resources by reducing unproductive communication effort. However, it may be desirable to automatically re-attempt communication at a later time to let the system "repair itself".
One way to do this is to set up an Indigo Trigger to re-enable the device after a specified amount of time has elapsed. This is easy with the help of a GhostXML event (Note that the Device Disabled event was added to the plugin with version v0.4.35).
- Create a new Indigo Trigger.
- Trigger: Select "GhostXML Event" and then "Device Disabled".
- Condition: Add any conditions you like (optional).
- Actions: Select "Server Actions" and then "Enable/Disable/Reload Actions" and then "Enable Device". Select the GhostXML device you want to (re)enable.
- Select "Delay by" and set an amount of time that should elapse before Indigo (re)enables the device.
When Indigo (re)enables the device, the plugin will again attempt to establish communication with the data source. If communication is still not possible, the plugin will (re)disable the device and the Trigger will fire again. So for example, if you set the delay time to be 1 hour, the device will be (re)enabled each hour until communication is restored.
You may wish to also add some type of notifications to alert you to the fact that the plugin has disabled the device (to alert you to a communication failure) and when the trigger (re)enables the device so that you're notified that things are back to normal.