MQTT Broker

Hi Joe,
I have (had) a trigger than restarts the MQTT Connector plugin if my Broker Status was "Disconnected 0".
I realised today that this trigger wasn't working, I've now changed it to trigger on Status = "Stopped". Was this changed in the last version? Is using a trigger for Status = "Stopped" the best approach here?

My trigger is set to “not equal to Connected 0”. But it doesn’t work. I’m embarrassed to say that my “solution “ is to reload both plugins every 10 min. That reduced the failures, but did not eliminate them. There has to be a better way.

Once I updated it to “Stopped” it works fine. Problem was I was tracking an incorrect status as I see it.

That’s interesting. I have never seen a status. “stopped“. Was this for the connector device or something else?

That is the status of the broker.

You're correct - the device is the broker (when I first started with Shelly, I incorrectly named the broker "Connector").
So back to my question, - have you seen the broker status "Stopped"? - the third line in custom states for the device? And what exactly does your trigger do?

Hi Joe,
I have (had) a trigger than restarts the MQTT Connector plugin if my Broker Status was "Disconnected 0".
I realised today that this trigger wasn't working, I've now changed it to trigger on Status = "Stopped". Was this changed in the last version? Is using a trigger for Status = "Stopped" the best approach here?

Damifino. Open. GitHub issue and I’ll look into this when I get back from vacation.

Hi Joe,
I have (had) a trigger than restarts the MQTT Connector plugin if my Broker Status was "Disconnected 0".
I realised today that this trigger wasn't working, I've now changed it to trigger on Status = "Stopped". Was this changed in the last version? Is using a trigger for Status = "Stopped" the best approach here?

Damifino. Open. GitHub issue and I’ll look into this when I get back from vacation.

Done

You're correct - the device is the broker (when I first started with Shelly, I incorrectly named the broker "Connector").
So back to my question, - have you seen the broker status "Stopped"? - the third line in custom states for the device? And what exactly does your trigger do?

Hi Smuseby,
My trigger is as per screenshots attached. Hope this helps.
My actions is to reload the connector plugin.

That's very interesting. Maybe I have a device issue? - as my broker is of type "MQTT Connector", model: "MQTT Broker"., whereas yours is "Shelly NG Broker". - (which might explain why I called mine a connector?)
Anyway, following your lead, my trigger screenshot - which shows the device as "Shelly Broker", not your "Shelly NG Broker". (see screenshot)
Creating a new device, there are 3 Shelly options - I picked the first. This was months ago, and I don't recall why I picked it, and today, I don't know which one is correct. (I have both Shelly and Shelly Plus devices installed).
Are you aware of any documentation? Lacking that, can you advise me as to what is the correct device(s)?
Thanks,
Bob

This is why I switched to running Mosquitto on my indigo server.

This is why I switched to running Mosquitto on my indigo server.

Did you install Mosquitto on macOS?

THanks

Yes. Runs on my indigo server Mac mini. But could also run on a raspberry pi.

Yes. Runs on my indigo server Mac mini. But could also run on a raspberry pi.

I have installed but struggling to get the plugins connected to it.
Could you please paste here your config if possible?

Thanks

EDIT: the port was not defined in the standard config, now it works fine.

My 'solution' to the lack of reliability of MQTT/Shelly controls, is to initiate all commands with a reload of the broker plug-in and delay the commands 1 sec . It works, but it's awkward. I'm hopeful that running the MQTT broker independent of Indigo is a better solution.
I googled 'Mosquito' and found "Eclipse Mosquito". Is this the broker referred to? Could you please provide a little information on how to deploy it with Indigo?
Thanks,
Bob