update to version 0.0.2 Hello, I released version 0.0.2-beta of a custom node to handle communication over mqtt via the homie convention . [image] node-red-contrib-homie-convention Node-RED nodes for MQTT communication according to the MQTT HOMIE convention Thi…

Take a look at the homie convention: 3.3 QoS and retained messages The nature of the Homie convention makes it safe about duplicate messages, so the recommended QoS for reliability is QoS 1 . All messages MUST be sent as retained , UNLESS stated otherwise. So if your device can’t do it you ha…

Now I have moved over to another MQTT Broker on my Synology NAS drive and things starting to be much better :grinning:. I have another problem now... Everything works fine to import the data to Node-RED, the switches, buttons updates fine. But when I try to change a light status from Node-Red the c…

Hi Magnus, It seams like the homue implentation on the Homey side is bot correct. A command is transferred (i.e. from Node-RED) via the set topic and should be executed and then acknowledged via the property topic. Either your controller is not receiving the /set command or it is not responding pro…

Something is a little bit strange since this configuration works fine when using ordinary MQTT in/out nodes! Now I can both receive and send the commands where the light turn on/off correctly. I will continuing to fault trace further… [image] [{"id":"d6672b1f.e58f48","type":"ui_switch","z":"f6a…

Good Morning from Berlin. I have to dig a little bit deeper. I could not import your flow (there is something missing at the end and an error in between: [image] So perhaps you can "resend" both flows (homie version & "manual" version). You wrote that the homie/homey-topic/lucasfonster/onoff/set …

God afternoon from Gothenburg! @Christian-Me - Finally I have now everything up and running :ok_hand: the problem was the different applications I use in the Homey and the MQTT Broker which needed to be restarted in order to be in sync. THANK YOU - for helping me out, even if i misled you in my co…

[image] Christian-Me: Good Morning from Berlin. Good afternoon from Yorkshire (UK). Well done on this Christian, really useful to me - The password bit is working fine in latest version btw. However I have some issues getting the dropdown list of 'devices' to be correct. I have 10 homie dev…

[image] Christian-Me: make sure that most messages has to be sent as retained messages with QoS=2 according to the homie convention homie is lightweight with QoS=0 and supports QoS=1 but QoS=2 is not appropriate. It's very hard work on the broker and all clients. /set messages must not be se…

Hi Kevin, Hi, fine that the password now working. You will find a lot of information on the console to nail problems down to trace level. Just adjust your log level. The "ghost" devices are strange because the node subscribe only to homie/#. That then must be an issue in the used mqtt module (whic…

[Announce] node-red-contrib-homie-convention

Share Your Nodes

zenofmud 18 December 2019 09:25 21

@Magnus_P

This is caused by not using the </> code function to insert flows. Use three back tic's (`) one a line before and after your flow and it should be able to be imported by others (see How to share code or flow json)

Topic		Replies	Views
MQTT Homie Convention Node - questions about usage General	22	2545	16 July 2020
MQTT Node: Subscribing to `+/+/$homie` does not work? General	44	1760	13 May 2020
Am I using the right program/hardware? General	25	2167	18 December 2019
[Announce] node-red-contrib-esphome Share Your Nodes	49	2246	12 April 2025
Need some opinion on smart home creation Dashboard	46	1662	30 December 2020

[Announce] node-red-contrib-homie-convention

Related topics