Your Home Assistant server node (in the config nodes) is not connected and working.
The dotted line around the config node suggests that it is not set up and connected to HA.
The ‘0’ in the used box suggests that it is not actively connected to any of the HA websocket nodes that use this server to connect back to HA.
When I distribute Node-RED flows I use the scrubber
https://zachowj.github.io/node-red-contrib-home-assistant-websocket/scrubber/
to remove all the HA service configuration settings. This is done to prevent my copy of my HA server config node from being exported and imported into your flow. In most cases you will already have an active and working HA server config node, so you don’t want a second (third / fourth …) one.
To get the flow working requires re-connected the HA websocket nodes back to your working Home Assistant config node. AND if you don’t already have a working HA server config node, then that needs creating and setting first.
There is no API key required. The Agile prices can be pulled from Octopus without any API key.
Your Home Assistant server node should not require any authorisation either.
Assuming that you are running Node-RED as an addon, all the necessary bits are included, however do make sure that you:
- are running the latest version of the included Node-RED addon (see addons)
- have the latest (matching) version of the home assistant websocket nodes (see NR pallet manager)
- have the latest (matching) version of the Node RED companion (see integrations)
It is important that each of these three components match. The latest version is not essential, however old version of the NR Companion do not work with the later websocket nodes.
First, check your nodes are correctly set up
Take each websocket sensor node (with the error triangles) and edit them
You will see the ‘entity config’ which is the configuration node behind the flow node. Edit this.
You will see in the ‘ha entity config node’ the ‘server’ entry, which when you import the flow will be blank (see the scrubber). You need to connect this node to the Home Assistant server. If you already have a Home Assistant server config node then it will auto-select this. You just have to accept and save the edits. This will update the config node, then the entity (sensor) node will work.
If you do not have a Home Assistant server node already set up and working (perhaps this is your first Node-RED flow) then you will need to ‘add new server’
NOTE that for Node-RED addons the HA server node manages the internal connection when you select ‘using the Home Assistant Add-on’. If you are using NR outside of HA then you will have to set up your own connection back to HA.
Once you have the Home Assistant server (config) node working the dotted line should go.
Once you have the entity config nodes corrected connected to the HA server node, the red triangles should go.
Then it should all work.