Indigo Domotics

Colly,

grateful for your assistance even if you’re not an expert, you solved the message type that I missed.


Skickat från min iPad med Tapatalk

You're welcome. For info I've edited my earlier post where I incorrectly suggested to Match "Any".

Thanks Colly and Joe for helping!

tazswe wrote:

Yes,

The change of any to Any(Wildcard) solved everything.

Thanks a lot Flying diver, Colly and Aaron for all the help.

The steps you have just completed are mostly setup related and won't be required to be completed over and over when adding new devices. With that being said, I will go through my wiki and see if I have missed some instructions for getting started. My screenshots may be out of date by now as I haven't updated my guides in a while.

Please let me know if there was a part of this setup that could have been made much more clear. I have realized that I don't have any links to my guides from the forum here. Did you use the wiki on my GitHub to get this setup?

Thanks,
Aaron

Aron, I used your wiki and have probably read most of the forum for help.

The wiki shows the correct use of the “any” but it is not foolproof so it can be improved.


Skickat från min iPad med Tapatalk

To run Mosquitto in Docker on an old mini Mac wasn’t successful, it slowed down the cpu and I had to turn it of. Can’t run Docker on my old Synology.
Replaced it with a RPI Zero W and now is it up and running again.


Skickat från min iPad med Tapatalk

I'm running into a similar issue as Tazswe. - all components appear to be set up correctly, but unable to get Shelly1 relay to operate from Indigo. The MQTT connector seems to be working (Connected 0), Mosquitto installed and running, Shelly1 showing in MQTT Explorer, and when I toggle from on to off from Indigo, the relay command changes are reflected as such. Shelly1 web interface has "Enable action execution via MQTT" selected, and have tried several server combinations, including localhost:1883, 192.168.1.1:1883 (Mac Mini), etc.

Any suggestions as to what might be causing the Shelly1 not to respond would be greatly appreciated.
______________________

1. MQTT Connector:

Connection Info:



a. Topic Subscriptions:



b. Published Devices:



2. MQTT Trigger:



3. Shelly MQTT Device:



4. Shelly1 Web Interface:



5. MQTT Explorer:

First thing I see is you have "shellies" misspelled in the Topic subscription.

Thanks Flying Diver. An embarrassing error, but correcting the spelling didn't fix the issue. Any other ideas?

Not really, hopefully Aaron can figure it out.

You mentioned you had tried a few different ways of connecting to the broker. From your screenshots, it looks like ShellyMQTT is able to publish valid Shelly commands over MQTT to your broker, so you should't need any additional changes within Indigo.

The screenshot of your Shelly web console shows your server listed as "localhost:1883". This is from the perspective of the Shelly device so, as configured, that would indicate that your broker is running on the Shelly device itself (which wouldn't be the case). This should point to the IP address of the broker, which I believe is your Mac mini. Can you confirm the IP address that your Mac mini has been assigned?

aaronlionsheep wrote:

You mentioned you had tried a few different ways of connecting to the broker. From your screenshots, it looks like ShellyMQTT is able to publish valid Shelly commands over MQTT to your broker, so you should't need any additional changes within Indigo.

The screenshot of your Shelly web console shows your server listed as "localhost:1883". This is from the perspective of the Shelly device so, as configured, that would indicate that your broker is running on the Shelly device itself (which wouldn't be the case). This should point to the IP address of the broker, which I believe is your Mac mini. Can you confirm the IP address that your Mac mini has been assigned?

Aaron,
Does the broker have to be selected or will "- Any Broker - " still work?

Colly wrote:

aaronlionsheep wrote:

You mentioned you had tried a few different ways of connecting to the broker. From your screenshots, it looks like ShellyMQTT is able to publish valid Shelly commands over MQTT to your broker, so you should't need any additional changes within Indigo.

The screenshot of your Shelly web console shows your server listed as "localhost:1883". This is from the perspective of the Shelly device so, as configured, that would indicate that your broker is running on the Shelly device itself (which wouldn't be the case). This should point to the IP address of the broker, which I believe is your Mac mini. Can you confirm the IP address that your Mac mini has been assigned?

Aaron,
Does the broker have to be selected or will "- Any Broker - " still work?

"Any Broker" should work, but I would probably choose the specific broker.

You seems to only have received a single message on mqtt.

Try to reboot the Shelly device and after that reload the mqtt connector and Shelly mqtt.


Sent from my iPad with Tapatalk

tazswe wrote:

You seems to only have received a single message on mqtt.

Try to reboot the Shelly device and after that reload the mqtt connector and Shelly mqtt.


Sent from my iPad with Tapatalk

Actually it doesn't look like the Shelly has sent ANY messages into the broker. All of those messages have come from ShellyMQTT and the MQTT connector. I'm fairly certain this is a configuration issue with getting the Shelly pointed to the broker.

I use the actual ip no and not localhost.

Changed some of my Shellies today to a new server with aanother ip no.
Wasn’t enough to change pointing to the new address in Shelly, had to reboot the as well to get them to show up.

At the end of the process I reload the mqtt connect and Shelly mqtt, not know if it’s needed but it doesn’t do any harm,


Sent from my iPad with Tapatalk