Configuring NG relays

ShellyPlus1 (Uses ShellyNGMQTT Plugin)

46D3B06D-98F5-4C3F-989B-487F6A77BBE1.jpeg (50.81 KiB) Viewed 36518 times

Shelly1 (Uses ShelllyMQTT Plugin)

C98B8BA9-7993-46B1-81B0-9CB05EB9201C.jpeg (18.26 KiB) Viewed 36518 times

Mine are plus.
But they do not respond to NGMQTT settings, only gen1.
Can anyone explain this?

I misspoke - when I created a new device, using the old type, ShellyMQTT, indigo reported a state - on/off. I was excited to see a state, but didn't check the operation., The device actually is off-line, and can't be controlled. I've deleted that failed experiment, and returning to trying to figure what is wrong.

I can control the device from its IP. Below are all my settings for one device, shelly triggers and plug-ins (all reloaded). Hopefully this format is easier than screenshots to spot my error(s).

Device settings:
Type: ShellyNGMQTT
Model: Shelly Plus 1
MQTT Topic: shellies-ng/shellyplus1-b8d61a8a6954
Message Type: shellies-ng

Trigger (1 of 2 - the other for first generation):
Type: MQTT Connector Event
Event: Topic Component Match
Topicstrings for matching:
Match: shellies-ng
Any:

Plugins:
MQTT Broker
MQTT Connector
ShellyMQTT
ShellyMQTTNG (v0.4.0)

And lastly, the device settings (again) - here, a screenshot seems simpler.
Is there any other setting that I've missed?

You are missing the leading shellies-ng/ in the MQTT Prefix in your last attachment. I had that in one of my responses to you yesterday.

I'm sorry that I didn't implement your last comment. You had my hopes up, but, I still do not have a connection with Indigo.
The MQTT settings on the device page are:
- the first four boxes are ticked; the Generic status update over MQTT is not.
Connection type: No SSL
MQTT Prefix: shellies-ng/shellyplus1-[mac address]
Client ID: shellyplus1-[Mac address]
Screenshot attached for confirmation.
Maybe it's something simple, like a colon, spelling, device name, upper/lower case?
Clearly, I do not have a basic understanding of this technology. What I am good at is following a recipe. Once this riddle is solved, I will be happy to document this for those who follow and who are similarly challenged.
Bob

Have you tried using one of the MQTT client apps to see what messages are actually being published?

More info, svp: what might be an MQTT client app? (
The many settings are starting to make sense to me - everything seems to conform. (Although I have no idea what a shim is - I’m hoping that’s for implementations that involve more than managing a relay.)
There has to be a brain dead mistake I’m missing.

Something like https://apps.apple.com/us/app/mqtt-expl ... 1455214828 or https://apps.apple.com/us/app/mqttx/id1514074565

Is this screenshot useful?
The first NG device is not powered.
The second one (C049EF8CAB3C) is connected as is the server (3.20).
Any way to use this tool to help understand how to connect the device to Indigo? The shellies are working.
I'm adding this tool to yet another MQTT mystery.

Ok MQTT Explorer confirms the device is connected to the MQTT Broker. We can focus on getting the data from the broker into the plugin.

The screenshots below are not meant to be used to copy my configuration - they are for my devices, ip addresses, Mac addresses, and naming. I think you've figured this out by now, but we will work with you to get the specific values set for your devices.

1) Please send a screenshot of your MQTT Broker connection configuration. It has a Model of "MQTT Broker" and a Protocol of "MQTT Connector". Specifically the "Connection Info" and "Topic Subscriptions" sections. Also confirm the device shows a status of "Connected".

Broker Device

Screen Shot 2023-04-03 at 8.25.36 PM.png (81.18 KiB) Viewed 36361 times

Broker Connection Info

Screen Shot 2023-04-03 at 7.59.54 PM.png (45.15 KiB) Viewed 36361 times

Broker Topic Subscriptions

Screen Shot 2023-04-03 at 8.01.11 PM.png (33.78 KiB) Viewed 36361 times

2) Send a screenshots of your triggers of type "MQTT Connector Event" with an event of "Topic Component Match". If your are only using MQTT for my Shelly plugins, then you should have two of these triggers. Please send a screenshot for any and all triggers of the specific type.

ShellyNG trigger

Screen Shot 2023-04-03 at 8.05.35 PM.png (101.59 KiB) Viewed 36361 times

3) Send a screenshot of the Indigo configuration section for your Shelly Plus 1.

Indigo Device Configuration

Screen Shot 2023-04-03 at 8.10.30 PM.png (82.94 KiB) Viewed 36361 times

By the way, I don't think FlyingDiver, cuhouse, or myself would waste our time helping you if none of this worked. 100% of my home automation is Shelly. 100% my Shelly plugins and FlyingDiver's MQTT plugin. If this ecosystem/flow didn't work, then I'd have no lights right now, my aquarium would be dark, and my coffee wouldn't have brewed this morning. We just have to get you configured correctly.

I have complete confidence that these things work - I have 18 queued up for installation, replacing the Insteon stuff that has plagued me for years.
I'm hoping that I will be embarrassed soon, but to be honest, I don't see how my stuff varies from yours (aside from what I named the broker).
I'm looking forward to your reply.
BTW, repeating what I wrote to cuhouse, while I am unable to contribute to the technical aspects of anything related to Indigo, I can document (from the perspective of a person with no technical expertise), and would be happy to prepare a draft and contribute it for editint so others can avoid the struggles I've experienced.
Bob

Can you please screenshot a current window of the ShellyPlus1 MQTT Settings GUI for the same device as that you replied to Aaron?

Thanks.

Attached is the screenshot for the MQTT settings for the device used for my Aaron reply. I apologize for the confusion.
Lacking anything better, I resort to guess and check: when the 1Pplus device didn't work, I tried the 1 Plus PM that I also have available. Same result.

That is a different device. A Shelly Plus 1 PM. Can you power up the Shelly Plus 1 ending in 5B6C that was being used throughout this thread and post a current screenshot of the Shelly MQTT Setting?

Thanks.

This one should match.
I tried 3 different devices to rule out a defective device, to try a different device name, and starting fresh to test myself.