Shelly devices

[amotl]

Introduction

Coming from GH-108 and #69 (comment), this issue is about unlocking support for devices by manufacturer Shelly.

[amotl]

Dear @wetterfrosch,

at #69 (comment), you shared an insight about how Shelly devices publish their data to the MQTT broker. Thanks.

I am stumbling upon devices from the manufacturer shelly where the last part of the realm is always expanded with /info or /settings, like realm/of/topic/data.json/info. Is for those devices a tweak in the config file possible?

Would you mind adding a more extensive report either here, or better use a dedicated issue, to share the full output of the corresponding payload, including the designated default MQTT topic, also outlining which fragments/prefix/suffix can be adjusted? Please also share the type of your device, and maybe a link to its documentation, to save keystrokes.

With kind regards,
Andreas.

NB: Kotori has a release pending about all the router updates coming from adding data acquisition from TTN, so if there would be updates required to support a Shelly device in one way or another, I will be happy to squeeze it into the next release.

[amotl]

May I ask if we are looking at a Gen1 or Gen2 device here, and which specific one?

• https://shelly-api-docs.shelly.cloud/gen1/#mqtt-support
• https://shelly-api-docs.shelly.cloud/gen2/ComponentsAndServices/Mqtt#step-6-receive-notifications-over-mqtt

It looks like Gen1 devices use MQTT prefixes like shellies/<model>-<deviceid>, while Gen2 devices just use <topic_prefix>, where <topic_prefix> is a custom prefix if set, or otherwise defaults to <device_id>.