Configuring NG relays

That's interesting, but I thought Indigo could manage the NG devices.
Does that mean that the NG devices don't work at all in Indigo, or are you referring to only the MQTT configuration of the Indigo settings? Hopefully, the latter, in which case something(s) is/are still wrong. - in Indigo, there the State field is blank.

This is because you have not properly configured it yet.

Per my last message, this is what you need to do based on the incorrect trigger I saw in your screenshots.

-- Begin Action Item --

The only trigger we are about right now is the MQTT Connector Event type. It is what listens to all MQTT traffic and determines which messages are put into the message queue to be processed by the Shelly Plugin.

You have a trigger named "MQTT Connector Event", and you have it configured to match on "shellies" and then "ANY". Therefore, this trigger will be executed any time a message comes across under the "shellies/<some_topic_path_here>" topic path. This is sufficient to match on ALL gen1 shelly device traffic. So we configured the trigger to then queue ALL these messages into a queued with a message type of "shellies". This works ONLY for the ShellyMQTT plugin.

Gen2 devices have basically no overlap in how they communicate with MQTT. Hence the need for this different plugin. This means we use a 2nd queue of messages (a different message type) and therefore a second trigger. I recommend you delete your existing trigger named "MQTTNG Connector Event" and make a new one. You need to configure it with:

Code: Select all

Match: shellies-ng
Any:

and queue the message with a message type of "shellies-ng". This will result in all MQTT messages in topics under the "shellies-ng/<ANY_TOPIC_NAME_HERE>" to be put into a queue named "shellies-ng". This works because you correctly set the MQTT Prefix in the Web UI to be "shellies-ng/shelly1plus-b8d61a885b6c". It will match this new trigger's topic pattern because it is using the "shellies-ng/<SOMETHING>" topic pattern.

-- End Action Item --

You are very patient to take the time to explain the MQTT intricacies to me. Thank you. But, it is getting very awkward as I continue to strike out..
I deleted both trigger and device, for a fresh restart. The new device and trigger are set per the attached screen shots. For both MQTT and MQTTNG triggers, there are no "/#" wild cards. Is that significant?
There's no device state for the device. (I can control it from the internet). When I was creating the new device, there is a device state of "off" (which is inactive) until I configure the Indigo page, at which point, the device state disappears.
I understand you earlier comment to mean that the Edit Device Settings - System, Wifi and BLE pages are superfluous.
I'm sorry to do this, but once again, I'm asking you look at the attached - I hope we're getting close.
Bob

It's getting a little clearer.
The MQTT Connector plugin acts as a client for all of Indigo and allows you to subscribe to any mqtt topics. In this case we recommend you make a single topic subscription, "shellies/#", that will ensure ALL shelly messages are captured into Indigo. So at this moment: Shelly traffic makes it into the MQTT Connector plugin, but nothing happens with the messages.

Going verbatim from your screenshot, I also subscribed to "plex/#, Shellies-ng/#, and tasmotas/#. I gather those three for some other purpose.

I was looking at a thread from when you configured your gen1 Shelly device in Feb. Look at your MQTT broker configurations for your subscriptions and make sure you don’t have the subscription shellies-ng/# using an uppercase “S” as you have it written above.

PNG image.png (97.65 KiB) Viewed 34323 times

I've attached a screenshot for my connector event trigger.
My intuition: one connector event should work for both generations of shelly relays. The one I created especially for NG strikes me as redundant. Correct?

Sorry you need a trigger for each. Put your gen1 trigger back the way you had it as it was working.

I wanted to see what your Indigo MQTT Broker shows first.

PNG image.png (216.58 KiB) Viewed 34291 times

Attached is a screenshot of my MQTT broker (#1).
Two issues occur to me:
1) IThe NGMQTT trigger ((#2) is attached - note that the type is "MQTT Connector Event", and not "NGMQTT...". The MQTT trigger matches "shellies" and "Any", message type "shellies" - and this one works. When working with the type, "ShellyNGMQTT Event", none of the event choices look appropriate (#3). The NGMQTT trigger like it's focused on relays with switches.
2) the device, 46 NGMQTT in the device custom states window shows "online-no". Until it's online, how can the triggers/broker function? It seems that the mistake must be in the MQTT configuration of the LAN. I've attached (#4) a screenshot for the MQTT settings from the LAN connection.
BTW, I'm very grateful for your assistance. Thank you.
Bob

I don’t see anything obviously incorrect.

I don’t understand where/why you showed the 2nd to last graphic. Screenshot 2023-03-31 at 14.54.06.png

Can you show us the Shelly Plus 1 device windows. For the Shelly Plus 1 Tab?

I don’t understand where/why you showed the 2nd to last graphic. Screenshot 2023-03-31 at 14.54.06.png

I included this to explain why I don't have a trigger of type," NGMQTT Connector Event" , in the hope that I was missing something.

I selected only those screenshots where I have made changes to the default settings.

FWIW, from the LAN Diagnostics tab, downloaded the debug log - MQTT settings:

"mqtt": {
"enable": true,
"server": "192.168.3.20:1883",
"client_id": "shellyplus1-b8d61a885b6c",
"user": "RSS",
"topic_prefix": "shellies-ng/shellyplus1-b8d61a885b6c",
"rpc_ntf": true,
"status_ntf": false,
"use_client_cert": false,
"enable_rpc": true,
"enable_control": true
},

Thanks Bob. And lastly, what do the Indigo Device settings show for your Shelly Plus 1?

i.e.

Screen Shot 2023-03-31 at 7.47.13 PM.png (64.37 KiB) Viewed 34270 times

I don’t understand where/why you showed the 2nd to last graphic. Screenshot 2023-03-31 at 14.54.06.png

I included this to explain why I don't have a trigger of type," NGMQTT Connector Event" , in the hope that I was missing something.

Why would you expect to?

You need two MQTT Connector Event triggers, because you need to queue up the messages for the two different topics separately, because they're going to two different plugins.

I asked because I'm grasping at straws as to what might be wrong.
I do have two triggers, with two different message types: shellies and shellies-ng. The match strings for the original shellies are "shellies" and "Any"; for NG, 'shellies-ng" and "Any". No wildcards for either.
While MQTT is starting to make sense to me, my understanding is not adequate to find what's wrong with my NG setup.

Good News & Bad News:
I figured it out (good) - and for the bad, in the Plus boxes are first generation devices. Actually, I just checked, and the devices themselves are labled with the "Plus" designation. What a huge waste of time.
Very annoying - I'm sorry to have troubled you with this. Thank you for your time and attention.
For anyone reading this chain, Beware.

Before I raise hell with Shelly, can someone confirm that the NG settings work for Shelly relays with the Plus designation?

Good News & Bad News:
I figured it out (good) - and for the bad, in the Plus boxes are first generation devices. Actually, I just checked, and the devices themselves are labled with the "Plus" designation. What a huge waste of time.
Very annoying - I'm sorry to have troubled you with this. Thank you for your time and attention.
For anyone reading this chain, Beware.

I don’t follow. All of your Shelly Plus 1 screen captures of the Shelly device GUI around 7:41 this evening are of a Plus, NG model?

The Plus, NG ShellyPlus1 has squared off corners. The gen1 original Shelly 1 is rounded.

My devices have 6 facets, which makes them NG?
Does it make sense that Indigo could connect with an NG device with MQTT settings?