Ah yes. Any routine with a lock or security setting is unusable with the Echo for security reasons (unlock, disabling security). Unfortunately, there is no differentiation with routines for lock vs unlock and Echo usability. Maybe there will be in the future.
I have gotten around this with CoRE. Take the lock out of the routine and have CoRE lock it when the routine is executed. Or you can use the newer version webCoRE.
UPDATE DEC 19 2017:
If you are still using CoRE, please update to the latest version as soon as you can. Here’s what changed:
v0.3.16e.20171219 - RC - Replaced recovery safety nets using unschedule() with a much more optimized method that does not affect ST as much as unschedule() does
This is important as CoRE has been identified as a major choke point on a certain method that it uses (ST describes that as expensive in their documentation. As it turns out, it is. With ST’s help, CoRE is now able to recover from timeouts much faster and with a lot less resources than by using its own recovery safety net. You should also consider moving on to webCoRE instead, as CoRE is no longer actively maintained and only gets critical updates.
Thank you
Continuing in the BETA process of CoRE (mil…
Continuing the webCoRE development cycle, we’ve now reached Beta Milestone 2. This milestone will focus on adding missing (important) features, bug fixes, and performance improvement. Things should be smoother now, with less chances of breaking during updates.
And now, again, the warnings:
WARNING #1
The legal boring stuff. This software is free to use, modify, distribute, install on a potato, anything you wish to do with it. As it happens, by using it, you must understand that I cannot be held responsible for anything that stems from the use of this software.
WARNING #2 This software is currently in a BETA release stage. If you don’t know what that means, PLEASE read this !
WARNING #3
If you see any white text on a red banner reading “DO NOT SHARE WITH ANYONE”, it is probably best yo…