Provide ability to tie connector state to general network / connectivity state within the Tulip Player and an app

Thank you Pete for taking a closer look into this. I totally understand that this is not easy to resolve.

I think 3 is already there given that there is the option that you can ask Tulip to stop execution of any further triggers if an error has occurred.

I would certainly look for 1 to be implemented to gain more control about a graceful fallback. See also this post here for additional discussion of the pattern Multi-level conditions in triggers - #14 by pete

The automations approach could be a nice addition for sure, but for our challenge I think its is too generic as you would be loosing the context under which the error occurred within the app.

4 I am not sure I understood…

1 Like