Hello!
SMUSEBY wrote:... I'm guessing that the first one is the ShellyMQTT plug-in itself: the dot to the left of it is Yellow.
Nope, that is fine. The yellow indicates the plugin is using the Indigo 2.x API instead of the 3.0 API. I have a version that will be 3.0 compatible that I'm still testing before releasing. Then, the plugin orb will turn green.
SMUSEBY wrote:when trying to add the device in Indigo, in "Edit device settings", "use information from device" is grayed out. I've reloaded the plug-in, it's freshly installed. (The broker is installed).
That dropdown is populated from an internal list of devices, and yours is empty. When the plugin sees an announcement message from a device not in Indigo, then the announcement details go into this internal list. Then this "new" device is shown in that list to auto-fill some of the device settings.
Your shelly has not announced itself fully yet, so the plugin does not know about the device.
SMUSEBY wrote:Skipping ahead, I'm confused as to topics subscripts. Reading the "Getting Started" guide, I understand that it's important to limit the number of topics (I hope to install about 30 Shelly1 controls). What is/are the topic(s) to which I should subscribe?
That was written at a time when the inter-plugin communication was new, and we only had a few shelly devices. I don't think you need to worry about the number of devices at this point.
I now recommend you create a single trigger that matches on shellies/# (I think this is "shellies" and then the "Any" option) and set this is a message type of "shellies". Then you only have to remember that your message type is "shellies" when creating new devices.
Here is my MQTT Connector device subscriptions. I create a subscription on "shellies/#" to capture all shelly traffic.
- Connector config with subscribed topic
- Screen Shot 2023-02-12 at 6.56.43 PM.png (96.02 KiB) Viewed 1171 times
Then I create a single trigger that matches on shellies/# and queues all the messages with a message type of "shellies". Use the Any option instead of match with # for the wildcard.
- Trigger for all shelly messages
- Screen Shot 2023-02-12 at 6.53.44 PM.png (89.55 KiB) Viewed 1171 times
Here is an example of the working configuration for one of my devices.
- Device configuration with message type
- Screen Shot 2023-02-12 at 6.55.27 PM.png (166.57 KiB) Viewed 1171 times