I would like to use persistent functional calls in my project but didn’t find a ton of documentation. The closest thing I could find was a post by @mdma here: Power issues for uses that requires commands sent. Since that post hasn’t been updated since August I figured that I would start a new thread on persistent functional calls through the particle cloud network.
Solar Powered Sensor Box Project Overview
I am making a solar powered perpetual sensor box that hooks in to numerous other devices. Because the power draw is greater than what the solar power can provide it will have to sleep to recharge. The length and time of these sleeps cycles can vary drastically depending on use and I don’t want power limitations impacting critical user functionality.
After some research, it seems like my best approach is to sleep in 15-30 minute cycles. When the photon wakes up it will check another website to determine how long it should sleep, it at all. It will report back current power levels and will prevent the user from creating unreasonable power cycles. At first glance persistent function calls appear to be the best approach.
- Have there been any updates to persistent function calls with the latest firmware updates? Is there anything scheduled for the near future?
- Are there any workarounds in place now? What would you recommend that we use in the interim?
- Will it be possible to overwrite commands already sent out? For example, if I want to change the sleep time to 60 minutes in one command but decide to change the sleep time to 90 minutes later?
- Can we duplicate persistent function calls through scripted curl commands? Are there any downsides to this approach?
- Will there be any methods to interrupt the photon sleep cycle?
- Are there any power scheduling examples that would be a good place to start?
Thank you for all your time, help, and feedback