I have been toying with several different flows, and am now getting unidentified error messages.
Does anyone recognize where this is coming from?
msg : string[74]
"HttpActions:reportState(): skipped reporting states, no devices registered"
You should be able to double click the error in the sidebar, it should take you to the node that throw the error. you could also look at the log.
Nothing happens when I doubleclick the message. Neither the header, nor the body.
Which log are you referring to?
You really haven't provided enough information. What are the nodes you are toying with?
What version of NR and node.js are you using? (check the NR startup log)
Are you using Docker or Home Assistant?
Can you provide your flow so we can take a look a it?
In order to make code readable and usable it is necessary to surround your code with three backticks (also known as a left quote or backquote ```)
```
code goes here
```
You can edit and correct your post by clicking the pencil 
icon.
See this post for more details - How to share code or flow json
The node red startup log, which has, near the start, 'Welcome to Node Red'
Are you sure? If you go to a different flow tab and click it again does the flow tab change?
Also, are you using Home Assistant? That sounds like an error that might come from an HA node.
There is no flow left, after playing with Google Home I removed everything. The message I posted earlier does not have an ID section at all.
This morning I removed some "unused" nodes, I'll keep an eye on it to see if that error still appears.
The NR startup log does not show anything weird.
I have removed Google from the palette, and now the error message has not appeared anymore.
Weird. There were no Google nodes in any flows, but still the error came up just from the presence of the nodes in the left sidebar...
If you mean unused Configuration nodes then the error was probably coming from one of them.
I think you are right.
Last week I played with the Google nodes a bit and created a flow, but was unhappy with the result and deleted the flow. This may have resulted in a config node that was not correctly configured.
I never thought this would still be "active" somehow after deleting the flow......
Config nodes remain active after you have deleted nodes using them, they don't automatically delete themselves when there are no nodes using them. Often this is useful as you may want to start using the config node again and it might be complex to setup.
Makes sense.
But it is strange to see an error without the obvious node that is causing it.
The node should not do that. I would class that as a bug on that package, whichever it was.
Some config nodes are real sketchy, like the modbus node silently disables itself once you delete a node that references it. And re-enables when you add a node that uses it. Which is great as long as you only have max 1 node, but when you add 2, it gets crazy.
Have you submitted a bug report for that?
I have.
Hans
Colin via Node-RED Forum schreef op 16-04-2025 11:59:
Can you post a link to that please, I can't see it on the github issues page.
That isn't the issue I was referring to. I meant the one you described in the message I replied to.
