Issue with Node Red HAS and mqtt sensors- InputError: Integration not loaded

[2rkoester]

I have created in node red, several MQTT reads from a mosquitto broker which I in turn flow to HAS sensors. These sensors are then entities in HAS which were all working for days and suddenly failed. The mqtt connection is still good. The data from the broker is valid, but now the sensors indicate an error message "InputError: Integration not loaded". I am unable to troubleshoot why they fail I have reviewed the logs but not sure where else to check. Any suggestions where to turn next?
I am using node red companion.

the node red logs:

27 Jul 19:35:03 - [debug] [server:Home Assistant] States Loaded
27 Jul 19:35:03 - [error] [ha-sensor:EV Odometer] InputError: Integration not loaded
27 Jul 19:35:03 - [error] [ha-binary-sensor:EV Charge Status] InputError: Integration not loaded
27 Jul 19:35:03 - [error] [ha-sensor:EV Range] InputError: Integration not loaded

my flows look like this:

[zachowj]

Please post your diagnostic info:
https://zachowj.github.io/node-red-contrib-home-assistant-websocket/guide/diagnostics.html

[zachowj]

My first guess is that the MQTT nodes are sending data to the Home Assistant node before the Node-RED integration has fully loaded in Home Assistant.

[2rkoester]

Interesting thought. Is there the concept of a delay that can be introduced possibly between the Mqtt node and the sensor node would do it? I will try that.

…

On Sun, Jul 27, 2025 at 8:17 PM Jason ***@***.***> wrote: My first guess is that the MQTT nodes are sending data to the Home Assistant node before the Node-RED integration has fully loaded in Home Assistant. — Reply to this email directly, view it on GitHub <#342 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOYCS3BHLHXO674UCIAP4BD3KV225AVCNFSM6AAAAACCPPXUQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOJQGQ3DAMY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[zachowj]

You could install a queue node from the Node-RED palette manager to buffer the MQTT messages. Then use an events: all node listening for the home_assistant_client:running event to flush the queue once Home Assistant is ready.

You’ll also probably want to check if Home Assistant is already in the running state — if it is, send the message directly to the entity node; if not, route it into the queue.

This is a great use case for a subflow, so you can reuse the logic across multiple parts of your flow with minimal effort.

Docs for the event:
https://zachowj.github.io/node-red-contrib-home-assistant-websocket/node/events-all.html#client-events

[2rkoester]

Version: 0.77.1 Home Assistant version: 2025.7.3 Companion version: 4.1.2 Node-RED version: 4.0.9 Docker: yes Add-on: 20.0.0 Node.js version: v22.16.0 arm64 linux OS: Linux 6.12.25-haos-raspi arm64

…

________________________________ From: Jason ***@***.***> Sent: Sunday, July 27, 2025 8:16 PM To: zachowj/hass-node-red ***@***.***> Cc: 2rkoester ***@***.***>; Author ***@***.***> Subject: Re: [zachowj/hass-node-red] Issue with Node Red HAS and mqtt sensors- InputError: Integration not loaded (Discussion #342) Please post your diagnostic info: https://zachowj.github.io/node-red-contrib-home-assistant-websocket/guide/diagnostics.html — Reply to this email directly, view it on GitHub<#342 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOYCS3DOW3LIVXG6DVA7AA33KV2WFAVCNFSM6AAAAACCPPXUQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOJQGQ2TSMY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[2rkoester]

I took the simple route and just added a 30 second delay and all is working now! Not as eloquent as using the queue and probably still can result in an issue but good for my purpose.Thank you for the assistance.Rodger KoesterSent from my iPhoneOn Jul 27, 2025, at 8:33 PM, Jason ***@***.***> wrote: You could install a queue node from the Node-RED palette manager to buffer the MQTT messages. Then use an events: all node listening for the home_assistant_client:running event to flush the queue once Home Assistant is ready. You’ll also probably want to check if Home Assistant is already in the running state — if it is, send the message directly to the entity node; if not, route it into the queue. This is a great use case for a subflow, so you can reuse the logic across multiple parts of your flow with minimal effort. Docs for the event: https://zachowj.github.io/node-red-contrib-home-assistant-websocket/node/events-all.html#client-events —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>