Homey MQTT broker & suscriber (node-red)

hi dears,

im trying to use the Hemy like MQTT broker to share information with my oters devices (Raspberry pi 3 with node-red) in order to learn and “play” with this data.

imagen

after many mistakes with the ports (1183 instead 1883 LOL)

Eureka… my node-red was connected to my Homey
232

but… and now that??
node is suscribed and sent the birth message but no menssages from homey to Node
i has one folder in homey named Doors and nothing from Homey

maybe one beginers manuals to use the MQTT borker??

thanks in advance

Homey itself doesn’t use MQTT at all, so the broker is “only” useful if you need to run an MQTT broker for devices that use it (like the Sonoff Tasmota devices) and don’t have an always-on computer to run that broker on.

Which does give me a new app idea: an app that broadcasts all realtime data from Homey over MQTT, like capability changes, new/deleted devices, and whatever else.

bad news for me…

and then how can i serve the data (temperatature for example) to others? or MQTT?

BR

You can use the MQTT client app as part of a flow that will publish changes over MQTT.

I’m afraid you need to read a little about a broker and a client.

https://www.hivemq.com/blog/mqtt-essentials-part-3-client-broker-connection-establishment
You could read them there.

I’v got Homey working as a client, Node Red as a client and an Docker image as MQTT broker.
I use it to send data (like sensors temp data) via MQTT to a SQL database which is then plotted to a nice graph using Grafana.
Also build my custom dashboard for use on a tablet in Node Red dashboard.

i’ll read and try it

Homey as a client, node as broker and use simple dashboard

thank you so much

Node red can also act like a broker.
Install the MQTT Musquito client on Homey and use the same topics to send and receive data to and from Homey.
I used this client: https://apps.athom.com/app/nl.scanno.mqtt

Interested… particularly if I can update device capabilities too via MQTT

1 Like

Have to look closer, but from first looks it seems that not all sensor data is being “broadcast” in realtime.

That said, updating device capabilities should be easy to implement.

Hi, I am also interested to pass all data from Homey to mqtt broker. Currently I add in some flows the MQTT Client to send a message in a topic, this is not really manageable with 30+ devices.

You could run node-red on a docker image on your NAS (if you have one). It is also possible to install a MQTT broker in node-red. For an example of an MQTT broker installation in node-red take a look here

Hi Marlon, that is what I am running already, Mosquitto, Node-Red with Influx database and Grafana are already running in docker on my NAS. What I am looking for is an easy way to get all messages with mqtt instead that I have to create many extra flows to get the info. So connection which transfer all messages to mqtt.

I see your point. I don’t know if what you want is possible with mqtt and node-red.

Maybe worth checking out is the Prometheus exporter app for Homey (Beta). I haven’t used it yet, though. (Still on my todo list) As an added bonus, Grafana supports querying Prometheus. Take a look a the info here

Status?

Current status: I stopped using Homey entirely almost a year ago. But take a look at the MQTT Gateway/Hub app.

yes, thats the problem. Hub dosent support “local and presence” (Owntracks), so no topics.