Just do a screenshot then look at the screenshot. Against each entry in the debug it will have a timestamp followed by a node name (which will be a random string if the node is not named). Use the Search feature (Ctrl+F) and enter that name (or as much as is necessary) and it should show you the node. Assuming that is a Function node then open it and comment out any node.warn() statements by adding // at the front of the line. Then deploy and those messages should no longer appear. Repeat as necessary.
There's a bit of fun to be had with this // node.warn() . Furthermore, most debug messages are from other nodesānot just Function node.warn()ābut also nodes like PoolState or Action. There's no way to // comment this out. It's clear why the debug filter option should be able to exclude messages from other Flows. It would be very convenient. This is precisely the kind of filter option I'm asking the Node developers to provide.
Why revert to the previous version? I had such a bad experience with ESP32Home Builder that after updating, my automations stopped working. It took me a few days to revert to the previous version of ESPHome Builder. For some reason, I became very cautious. First, security, then experimentation.
I am unable to find any such node as PoolState.
Do you have a github URL for it?
Perhaps it is part of a group of nodes for pool management?
Have you verified if these messages can already be filtered out in Node-red v4.1?
It is a perfectly reasonable request.
However, if they were to change the editor to allow filtering out all messages (assuming that it's not already possible), they won't backdate the change to whatever version you are running, you will still need to upgrade.
I presume that those are HA nodes. Is there an option in HA to show/hide those messages?
In the latest version of node-red messages from Function nodes on other flows are hidden when the Filter is set to Current Flow, so there is no need to ask the developers to add this option. Whether it will also hide HA node messages I don't know. The only way to find out is to update node red and see. It probably will hide them.
For the possible issues when updating, keep an image backup of your SD card, then you can fairly easily recover in the event of catastrophe. Apart from anything else SD cards do occasionally fail so an image backup of important systems is an absolute requirement I believe.
Unfortunately HomeAssistant gives Node-red it's own (different) version number.
I don't know if they have made v4.1 available yet, or what version number they will have given it.
I think your best hope of progress is to ask in the HomeAssistant forum.
I assume these are HA nodes. Is there an option to show/hide these messages in HA?
These aren't HA messages ā if I block all flows, I don't get any messages. Besides, why would HA messages appear in node red?
In the latest version of node-red, messages from function nodes in other flows are hidden when the filter is set to the current flow, so there's no need to ask developers to add this option.
Which one is the latest?
In case of any update issues, it's a good idea to keep a backup of your SD card image so you can easily restore it in the event of a failure. SD cards also sometimes fail, so I consider image backups of important systems absolutely essential. I have HA running in a virtual machine on a Win11 PC. Backups are performed regularly and automatically. I'm not sure if Node Red is included in these backups.
As far as I can see, home assistant nodes are making these messages. The name on the debug messages in the screenshot on your first post match the names on the blue HA nodes your later screenshot.
So either those nodes have an option to disable these extra messages or HA is setting a lower debug level in the node-red settings.js file causing log level messages to appear in the debug panel.
This language, undoubtedly specialized, is completely abstract to me. I'm unable to use it. I'm an electronics engineer, I'm antediluvian. I'm also a lover of simplicity. I'll try to update Node Red. I don't have much hope. I think I'll wait for the next update, hoping for a functional fix for the Node Red filter. Thanks.
