Self service project to control Shelly relays, question on which APIs to use.

Hi,

I have a project in mind (call it project X) that would allow Shelly users to register to this service online and control their Shelly devices (relays mostly) based on different parameters.

My question is, what Shelly API:s is recommended to be used in this kind of project?

So the need is to switch on/off shelly device via shelly cloud api.

Simplest would be to use "Cloud Control API" so that each user would register their API token (and server URL) to project X so that it can have access to users device and control it via the API. But this API has limitation of 1 request per second but is it per one shelly account?, in that case that limitation would not be a problem.

Thank you in advance!

Zitat

Hi and welcome to the forum.

Honest answer:

I would never provide real account data to an unknown project X.

The potential for abuse is very big. (keyword presence detection, for example).

Sorry, this is my personal opinion.

Hi, yes I do realise that it would require trust from end user side. Project X is just a working name though until we get things going on (plan is to create a real company and business around this). It's related to electricity prices and controlling relays. Anyways, that outbound websocket connection seems interesting, although we would not need this type of real time or constantly connected devices. The need is simply to send scheduled commands to switch relays on/off.

Thanks for the honest opinions!

So is the answer that the preferred way would be to use outbound websokcet connection (on GEN2 devices)?