Page 1 of 1

Plugin returned initial code 17 (Unsatisfied)

Posted: 23 May 2020 19:33
by Sven
Everything was working how I wanted, I've set up multiple Flows and set everything up via Pushbullet (Google Home) etc.
Now, all of a sudden my flows are not getting 'pushed' into Automagic from Pushbullet (but they do get pushed through from Pushbullet and IFTT).
Does anyone know what the error message Plugin returned initial code 17 (Unsatisfied) means and how I can fix that the flows get executed again?

Re: Plugin returned initial code 17 (Unsatisfied)

Posted: 23 May 2020 19:47
by Martin
17/Unsatisfied means that the plugin returned that the condition is false which usually means for triggers that the trigger should not fire/execute.
16/Satisfied means that the condition is true respectively that the trigger should be executed. Unfortunately there's no way to debug on the Automagic side why the plugin returned the code 17 when you expected to get 16. Maybe try to configure the plugin in Automagic again. Some plugins store some information in the plugin app that might have been lost in an app update or similar event.

Regards,
Martin

Re: Plugin returned initial code 17 (Unsatisfied)

Posted: 25 May 2020 21:45
by Sven
Even after remaking the flows it still returns as code 17. It's just outta nowhere, kinda annoying. Hope you can help.

Kind regards

Re: Plugin returned initial code 17 (Unsatisfied)

Posted: 01 Jun 2020 19:43
by Martin
Unfortunately it's likely caused by the plugin itself. Try to uninstall/reinstall the plugin and ensure that it has all permissions granted and that it's not battery optimized in the system settings. Check out this page for some guides to turn off battery optimizations for your device: https://dontkillmyapp.com/

Regards,
Martin