It should, use your HA user/password, not what you entered on the config tab.
1 Like
Thank you ! It seems to work!
So I was having problems with the inject and debug nodes. This started after the latest nodered update.
My inject nodes were not greyed out but would show the move mouse icon when I hovered over them. I too could inject when I opened the node up. I able to get the ability to hit the button on the inject node if I opened up a HA node in the flow and clicked edit home assistant config…update…then redeployed all flows (wouldn’t work if I just hit redeploy for that flow). When I did this the entity ID would disappear from whichever HA node I selected…however I could successfully inject to turn on a light elsewhere in the flow.
Debug nodes also were not displaying any debug information.
Going to the localaddress:noderedport did not help…
I was also having sporadic occurrences where automations didn’t work…I’d check the flow and an entity id was missing from a HA node.
Nodered logs were not showing any errors.
Was getting ready to pull the trigger and reinstall nodered when I opened up the config nodes panel and found that a duplicate HA server config node had been created and being used by 0 nodes. I deleted it…redeployed all flows…and the inject and debug nodes immediately started working.
To verify if it worked I did a full system reboot…nodered seems to be working perfectly.
1 Like
SOLUTION: Just highlighting @mike5879 's last post as the SOLUTION for this issue (at least in my case). I had recently imported some flows which added a couple “Home Assistant” config nodes which somehow disabled all the stuff described in this thread. Clicking on the config node and pressing delete was all I needed to do for both additional configs. The main one was obvious given the much larger number next to it.
(config nodes already deleted in this snapshot)
I also thank @Mikefila for the “use the HA username/password to log into NR directly” as I kept using the credentials I had in NR’s configuration tab… which do not work. While that restored NR functionality accessed outside of HA, @mike5879 's solution fixed it within HA.
Thank you !
1 Like
hat jemand eine Lösung? Bitte eine “allgemeinverständliche” Erklärung 
I have the issue again, but this time I have no rogue Home Assistant Server Configurations.
I think it began when I updated the websocket but I am not sure. It is quire frustrating and I cannot find any solution. The only workaround is using NR outside HA via the ha_ip:1880 URL.
If anyone found alternative causes/solutions, please let me know.
For as long as I used NR, about 4 years, this issue has sporadically popped up a number of times. I always use 1880.
I had 2 configurations for the Home Assistant server, one with “Using the Home Assistant Add-on” and one with HA URL.
I deleted the configuration with URL and now, with only 1 server configuration, it works again, I can start inject and see the debugs even from HA link
It also seems now like switch nodes output everything instead of outputting based on state, i.e. my lights run off of a BigTimer node which outputs “on” at sunset and “off” at sunrise. At sunrise both outputs of the switch node connected are activated so that my lights are trying to turn on and off at the same time. Also, many entities are coming up as “not found” and function nodes often don’t work at all.This is a complete disaster! I sure hope someone can get this fixed soon. Is there any way to roll back to the previous version of NR?
I just started having this issue after the last NR and NR Helper update. I had second HA server instance with no use. Deleted that but injects still don’t work. I can log in to :1880 and I can do all the things. However, some of my injects are running flows at a specific time and those don’t fire. Not sure what to make of this but I’ll post anything I might find.
1 Like
Same here… I recently upgraded Node Red Companion HACS, but that’s about it. I reverted that change, but still no luck. I noticed that inject nodes aren’t working, but I also don’t see nodes that get the state of HA entities are also not showing under the nodes anymore. However it does appear that Node-Red flow are still working…
Did you reboot your host? When you open the restart popup, you should have a reboot host option in the advanced options. Also reboot your router.
I will try that in a moment… I am updating all the packages, just incase missing something
Negative. Rebooting the host did not resolve the problems.
However, going to IP:1800 to hit node-red directly works… so this tells me this isn’t a NR issue… this is how HA is embedding the NR WebUI.
I still have the issue that inject nodes that are supposed to fire at a certain time do not. Using the interface directly at the port works for editing and manually running things. Flows that don’t start with the inject at a specific time all work best I can tell.
I just did an NR restore to the previous version and things appear to be normal again. Now to figure out what is causing the newer version to have issues…
I’m opening an issue on the node-red github. I will share the link shortly so we can work together with them to resolve.
Thank you!
Here is the open issue, if you want to add your details:
For the nodes that need to execute a specific time? Are these just the Poll nodes or are they using a HA entity?
They are just inject nodes set to run at a specific time daily.