Repeatable Crash about node-red-contrib-home-assistant HOT 11 CLOSED

Eagerly awaiting this fix. My Node-Red crashes every 30 minutes due to not handling Null states.

from node-red-contrib-home-assistant.

Yep, it's been merged into the dev-master branch. You could pull from that branch or wait a little longer for the release.

from node-red-contrib-home-assistant.

It looks like Home Assistant is generating an event with a null state that is crashing Node-RED.

You could start disabling some of your serve-state-changed (events: state) nodes to find the problematic node.

Or, if you are an advanced user, you could put something like socat between Home Assistant and Node-RED to log all the events and use the timestamp from the crash to identify the entity.

from node-red-contrib-home-assistant.

Yeah that's what I assumed. Hopefully someone with better knowledge of this plugin can attempt to catch the null states that cause the plugin to crash and to handle them better. I'm also having issues with only a single node where something in the plugin code seems to stop my flow and I have to restart it making the whole system unstable. It's no fun when you press a light switch and nothing happens because the flow needs to be redeployed ;)

from node-red-contrib-home-assistant.

It seems like there is a missing try/catch that could fix the problem in onHaEventsStateChanged.
Try/catch is used in poll-state.js and trigger-state.js so I think adding one to server-events-state-changed.js wouldn't hurt even though it doesn't fix the source of the problem which probably is home assistant sending a null event to node red.

from node-red-contrib-home-assistant.

When will this change be released?

from node-red-contrib-home-assistant.

I have the same issue. Any update regarding this?

from node-red-contrib-home-assistant.

Glad I found this report. I thought it was my MQTT causing issues. Now I see that HA is just sending null states to node-red.

from node-red-contrib-home-assistant.

Not to get testy here, but a lot of people's node-red instances (including mine of course) are unstable and unusable without this change being merged #51. Seems like a very simple change that should be merged ASAP, yet the dev seems to be ignoring this?
Again no disrespect, but this is kind of blocker bug :)

from node-red-contrib-home-assistant.

Ok great, sorry for the misunderstanding.

from node-red-contrib-home-assistant.

Merged and released

from node-red-contrib-home-assistant.