This page was generated from the source of RoboHub. Edit the source, not this page.
Shelly Plug M Gen3
A Wi-Fi smart plug with a switch and a power meter, reached through Shelly's
JSON-RPC. The integration presents RoboHubSwitch and produces a
RoboHubPowerReading; a caller does not know which transport carried it.
Transports
- HTTP RPC —
GET /rpc/Shelly.GetStatusreads the switch and the power
figures;GET /rpc/Switch.Set?id=0&on=true|falsedrives the switch. - MQTT — the integration publishes
Switch.Setto
shellyplugmgen3-<id>/rpcand receives the status document from
shellyplugmgen3-<id>/status/switch:0. The platform supplies the broker
client through therobohub-mqttseam.
The same cached state and power reading are produced either way, so a gateway,
a relay or the Mesh application can treat the plug like any other switch.
In a plan
The manifest describes both transports as data, so an application reads and
switches the plug without knowing it is a Shelly:
- HTTP —
telemetry.http_pathandtelemetry_http_fieldssay what to read;
actions.switch.httphow to switch it. The plan names the plug's address. - MQTT —
telemetry_mqtt.status_topicandtelemetry_mqtt_fieldssay what to
read,actions.switch.mqtt_topicandmqtt_payloadhow to switch it. The plan
names the plug's device id (shellyplugmgen3-<id>) as its address, and the plug
is pointed at the keeper's broker, with a broker user the keeper made for it.