# MQTT Hub/Gateway

**URL:** <https://community.homey.app/t/mqtt-hub-gateway/6766>\
**Category:** Apps\
**Created:** [January 14, 2019, 6:59pm UTC](https://community.homey.app/t/mqtt-hub-gateway/6766 "2019-01-14T18:59:50Z")\
**Posts on this page:** 1\
**Showing post:** 703

<div class="post-metadata">

**Author:** ![Magnus\_P](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/magnus_p/32/4344_2.png) [@Magnus\_P](https://community.homey.app/u/Magnus_P)\
**Post date:** [December 17, 2019, 10:23am UTC](https://community.homey.app/t/mqtt-hub-gateway/6766/703 "2019-12-17T10:23:51Z")

</div>

Hi all!  
Trying to use MQTT Hub to integrate in [Node-RED](https://nodered.org/) using the [Homie-Convention Node](https://flows.nodered.org/node/node-red-contrib-homie-convention).

The problem I encounter, also expressed from the developer is this Node-Red Homie Convention Node relies on the mqtt broker as a persistent database i.e the MQTT messages should be set as **retained**. Link to [Node-RED forum topic](https://discourse.nodered.org/t/announce-node-red-contrib-homie-convention/16329/11)

I use the Homey MQTT Broker app, and It may be there the problem is since I read the MQTT Hub send retained messages, anyone who can guide me?

> **[node-red-contrib-homie-convention](https://flows.nodered.org/node/node-red-contrib-homie-convention)**
>
> Node-RED nodes for MQTT communication according to the MQTT HOMIE convention

According to the homie convention:

> 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

I interpret that if the device can’t do it the broker needs to handle it. Storing and saving QoS=0 Messages with retained flag is within the MQTT spec 3.3(?). The broker even should keep those messages. My question is if the Homey MQTT Broker capable of doing that?

---

_[View the full topic](https://community.homey.app/t/mqtt-hub-gateway/6766)._