Problem/Motivation

I am using Node-Red as middle aware between various devices, including light systems and alarms. I have previously used a standalone installation of Node-Red; but have opted to move to the addon.

However, within Node-Red I am using MQTT (node-red-contrib-mqtt-broker: mosca in) - when rebooting the host, all the entities provided via MQTT and Node-Red display as Entity not available: entity.name

In the logs of Home Assistant it reports that it is unable to connect to the MQTT broker, and wait to connect. It does eventually connect - but at this point I'm guessing there is no data to provide to Home Assistant, and hence the Entity is flagged as not available.

Expected behavior

Node-Red would start before home assistant.

Actual behavior

Node-Red starts after home assistant

Steps to reproduce

Proposed changes

The config.json for this add on is set to application (which means it will start after home assistant has started). If it was set to service it would start before home assistant