After upgrading to 0.67.1 debug nodes / inject are greyed out, HA nodes shows no status

[cpuks]

Documentation URL

No response

The problem

Problem/Motivation

Running latest version of NR within HA as and add-on I decided to upgrade node-red-websocket to latest which is 0.67.1 and after that I've been prompted to upgrade HA nodes and I did but realized that all of my debug nodes and inject nodes are grayed out, nothing displays inside debug window nor any HA node shows connection status. Nodes work as intended, but there's no feedback is provided by Node-Red. I've enabled heartbeat - set 60 sec and for over 10 min I had no connection drop.

I don't have anything fancy installed and didn't change anything except nr-websocket upgrade - double checked that.

Expected behavior

Proper feedback from NR<->HA connection, debug nodes / inject nodes work as intended, providing data.

Actual behavior

No feedback from NR - debug/inject and no connection status on any of HA nodes.

Steps to reproduce

Latest HA NR addon 18.0.5 - go to palette and upgrade node-red-ha-websocket to 0.67.1, then restart NR.

Proposed changes

Unknown

[zachowj]

Are you using the NR UI through the iframe in Home Assistant? If so, try connecting directly to NR. Check your browser console for errors.

This package doesn't modify anything related to the inject/debug nodes.

[jjvelar]

Are you using the NR UI through the iframe in Home Assistant? If so, try connecting directly to NR. Check your browser console for errors.

This package doesn't modify anything related to the inject/debug nodes.

I am experiencing the same issue but can confirm that connecting directly to Node-RED makes the nodes non-grayed again. I am afraid I don't know how to check browser console for errors.

[sanderlv]

Are you using the NR UI through the iframe in Home Assistant? If so, try connecting directly to NR. Check your browser console for errors.

This package doesn't modify anything related to the inject/debug nodes.

I think I hacve this eaxact same issue... When using NR addon and nodered via HA I get not status... When I go to IP:1880 all is fine... I started after I updated to node-red-contrib-home-assistant-websocket 0.67.2 (from the latest in the addon).

Problem is not with cache or browser as it is consistent in inprivate and among browsers. It always works with IP:1880... weird though?

[mike5879]

I had the same issue after upgrading from 0.65 to 0.68. I downgraded to 0.67.2 and the inject nodes started working again as they should.

However...there is no auto complete now within the nodes for action, entity, device id, area, floor, or label. it will give me a list of entities...but only about 10 or so. Nothing at all is listed under action, even if I put in a light for the entity. I have to type in the entire light.office_lamp and light.turn_on. Even typing them out fully doesn't bring up any match.

Disabled autocaching in server config node...restarted nodered...no change...re-enabled it...restarted...no change.

But when I connect to IP:1880 autocomplete works fine. Any thoughts? Not unusable...but a pain.

Update...was able to fix the issue by deleting all the browser data...then disabled caching of autocomplete...restarted node red...renabled caching...restarted nodered (entities worked after this but only entities)...restarted node red again...then everything else started working.

[cpuks]

I had the same issue after upgrading from 0.65 to 0.68. I downgraded to 0.67.2 and the inject nodes started working again as they should.

However...there is no auto complete now within the nodes for action, entity, device id, area, floor, or label. it will give me a list of entities...but only about 10 or so. Nothing at all is listed under action, even if I put in a light for the entity. I have to type in the entire light.office_lamp and light.turn_on. Even typing them out fully doesn't bring up any match.

Disabled autocaching in server config node...restarted nodered...no change...re-enabled it...restarted...no change.

But when I connect to IP:1880 autocomplete works fine. Any thoughts? Not unusable...but a pain.

Update...was able to fix the issue by deleting all the browser data...then disabled caching of autocomplete...restarted node red...renabled caching...restarted nodered (entities worked after this but only entities)...restarted node red again...then everything else started working.

So debug and inject nodes are all working fine after you deleted browser data and played with caching?

[HaraldGithub]

Today, I've updated to 68.6 and run into the same problem. I would appreciate if the next release will fix this issue, otherwise I'll try the solution of @mike5879

Update: Solution of @mike5879 doesn't work for me, so I've to wait until the developers will fix this issue.

[zachowj]

@HaraldGithub Are you accessing the Node-RED UI through an iframe, such as within Home Assistant, or directly? If it's through an iframe, have you tried accessing it directly to see if the issue persists? If it works directly, the problem may not be with this package but with the add-on.

[HaraldGithub]

The problem persists if i connect by iframe, directly over HA sidebar. If i connect to NR by HA-IP:1880 connection closes within 10 seconds, so I couldn't adjust the above mentioned work around.

1. Update: Connection over Chrome works, so I'll try it again on weekend.

2. Update The solution above don't work for me. After starting NR or reload i've to wait 15 to 25 minutes before inject-node is working and NR display node-status. Also with 0.69.1!

[dannycohn]

Still seeing this in 0.72.0. Using IP:port works, but seemingly intermittently, or only after waiting a while after a restart? Haven't nailed down a pattern yet.

[tomadan1968]

Same problem for me....