I think this is can be a problem with your Crontab permission and cloud authentication
Could you please elaborate? I thought the Cloud API authentication/authorization is based on the key I get from the Shelly App ("Access and permissions" -> "Authorization cloud key"), which is exactly same in both cases. What information of the process calling the REST API is passed to the server, based on which the server could sometimes allow and sometimes deny the service?
Hello all,
I have a couple of PHP applications for controlling Shelly devices. One of them has a HTML user interface, using which I can switch Shellys on and off. The other one is run automatically via cron, and it turns a Shelly on and off depending on outside temperature. Both applications are running on a same server (same IP), and use the same PHP function to call the Shelly cloud API. For some reason, the call initiated from the HTML UI will always succeed, whereas the call initiated from the application started with cron will always fail with "Request limit reached!".
This doesn't seem to have anything to do with the amount of requests, if I turn the same Shelly on or off from UI immediately after the other call has failed, it will succeed. In both cases the actual REST call is identical.
What is causing this and how may I fix or circumvent this?
