mreyn2005 wrote:Now I get it... Ok, so I setup my subscriptions as Indigo Server Startup triggers. Now I see the incoming trigger activate - yay! Now I just need to play with parsing the payload. I got to do some house work for awhile, but I will be back on later.
Subscriptions are persistent across restarts, they're stored in the Broker device's pluginPrefs, and re-sent to the Broker whenever the client (the plugin) connects. You can do them in a startup action group, or you could do them manually (once) using the plugin menu commands.
mreyn2005 wrote:If my goal is to update a device (on or off) from the incoming payload (which contains the device name/id and the on|off value I want to use) what is the best Action to run to do that with the current implementation? Execute script? I need to read up on the variable substitution for accessing the incoming payload...
At this time, a script is required. But I'd like to create some pre-defined parsing routines that would do it for you. What's the source of these payloads? Is it a standard format or something you created?
Please post an example of your payload. I'll give you a sample script to parse it.