So I turned off authentication and enabled anonymous access on my broker (using mosquitto built into HASSIO). I still see that the plugin connects with no errors, but it does not seem to send or receive anything. I even tried a short test topic just incase my topics had to many characters, but still nothing. Has anyone got this to work with Mosquitto as their broker with no authentication?

-Eric

Sorry Eric I missed your reply.

I have been using mosquitto all along during development, but without authentication.

I’m actually finding it very fiddly to set up auth on mine, which is why debugging your issue is taking me so long! (Well, that and I only get a couple of hours a week to work on stuff like this lol)

Starting dead cold here, as I don't even know what MQTT means. But I get it's some sort of interface between devices using a web communication protocol.

My super broad question is: If I have some other device (specifically, a camera running the Xiomi hack software) , and that software includes MQTT functionality, can I potentially use this plugin to integrate the camera(s) with Indigo?

It seems the cameras do motion detection and such, and can supply this info via MQTT to SmartThings. I no longer user SmartThings, but can I skip that middleman with this plugin? There's a "._mqtt-status" and an "._mqtt-control" script configurable in the camera software.

The broker manages the communications from clients and if desired other brokers.

A client creates a topicA client publishes to that topic textOne or more clients Subscribe to that topicAny client subscribed to that topic receives in real time the message published to that topic

So for Indigo, The indigo MQTT client connects to the brokerThe hardware device mqtt client connects to the broker and creates a topic such as /switch1/statusWhen on or off is published to that topic the subscribed device is turned on or off.

So for your camera you can probably integrate motion detection as thats a value that can be sent, but not images or files.

The Broker is basically a "server" app that handles the communication between clients. Depending on how many clients are connected, depends what spec machine is required.

There are many versions of MQTT broker free out there. HiveMQ is a good place to start i think as it is already compiled and you dont have to mess with python versions on your mac, its java based and limited to 25 connections unless you pay but for a fast test, i find this the quickest. Mosquito is probably the widest used but you would have to compile it or install using brew (or a separate VM or PI or something if you don't want it on the same box)

4GB and 2 CPU with 40GB disk space can support about 50,000 clients as a rough estimate. This is based on OpenDXL which is based on MQTT which is actually why I know anything about MQTT at all

So I turned off authentication and enabled anonymous access on my broker (using mosquitto built into HASSIO). I still see that the plugin connects with no errors, but it does not seem to send or receive anything. I even tried a short test topic just incase my topics had to many characters, but still nothing. Has anyone got this to work with Mosquitto as their broker with no authentication?

-Eric

Sorry Eric I missed your reply.

I have been using mosquitto all along during development, but without authentication.

I’m actually finding it very fiddly to set up auth on mine, which is why debugging your issue is taking me so long! (Well, that and I only get a couple of hours a week to work on stuff like this lol)

Sent from my iPhone using Tapatalk

No worries, I know how it goes . I tried using mosquitto with no authentication running on the same Mac as Indigo instead of the mosquitto install on my raspberry pi, and I am still not getting any messages to send from Indigo. I can send a message using the terminal to the broker fine, but when I create a MQTT switch device, nothing shows up on the broker when I toggle the on and off buttons in Indigo. I feel like I am missing something simple since other people have got this to work, but I just cant see anything to set up differently.

I´ve just updated to the newest version, and i cant get it to work. (it was working before with the 1.version)My broker is working properly and i see the messages is going through, but no updates in indigo.

i dont have user/pass on my broker. am i supposed to put something in the Superbridge pattern?

So I turned off authentication and enabled anonymous access on my broker (using mosquitto built into HASSIO). I still see that the plugin connects with no errors, but it does not seem to send or receive anything. I even tried a short test topic just incase my topics had to many characters, but still nothing. Has anyone got this to work with Mosquitto as their broker with no authentication?

-Eric

Sorry Eric I missed your reply.

I have been using mosquitto all along during development, but without authentication.

I’m actually finding it very fiddly to set up auth on mine, which is why debugging your issue is taking me so long! (Well, that and I only get a couple of hours a week to work on stuff like this lol)

Sent from my iPhone using Tapatalk

No worries, I know how it goes . I tried using mosquitto with no authentication running on the same Mac as Indigo instead of the mosquitto install on my raspberry pi, and I am still not getting any messages to send from Indigo. I can send a message using the terminal to the broker fine, but when I create a MQTT switch device, nothing shows up on the broker when I toggle the on and off buttons in Indigo. I feel like I am missing something simple since other people have got this to work, but I just cant see anything to set up differently.

I tried this early on, MQTT.FX does not see any messages being sent from Indigo. I tested both with a local MQTT broker and one on my Pi, both with and without authentication. In all four variations I do not see any messages being sent on any topic from the plugin (indigo). But if I manually send a message via the terminal, or from HASSIO it shows up in MQTT.FX so I know the broker is working properly.

Hmm. That is weird. I wonder if the plugin is actually connecting to the broker then. In the connections in mqtt.fx is the count of clients what you would expect? Try putting in a rubbish ip and restart the plugin, does it error? If not in lieu of debug logs id get Wireshark on the case and capture packets on 1883 as it just worked for me but i upgraded from v1 so dont know if that has any bearing?