Debug node's data is displayed collapsed

General
1

I’ve just updated to node-RED 4.1.0. One think that is bothering me is that, in the debug window, data is displayed collapsed. Is there a way to see it complete, as in previous versions?

This was very useful for me, as I often connect to the RPi remotely, copy the entire debug column and analyse it locally, which I cannot do now.

2

Maybe a screen shot of the problem?

(Just saying.)

1 Like
3

If you select a nested property and pin it, the output will expand all the way down to this property.

Can you advise how you could get it fully expanded in previous versions?

4

Here it is, how I saw it previously and how I see it with 4.1. As I said, I used to copy the entire column to see and analize data from three devices and now I can´t, as is it trunked

previous
previous1366×768 179 KB

4.1
4.11366×768 176 KB

5

ok, so its not expanded or collapsed, it is truncated for visual purposes. This was introduced recently.

Besides, that is what the Copy Value button is for and it (should) put the full value (not the truncated value) into your clipboard.

image
image354×145 52.7 KB

6

The problem is data scrolls too fast: I have no time to copy or uncollapse (that’s why I copy the entire column). Even more, when I’m connectd remotely, it may have connection issues (lags) that makes it more complicated.

7

Then do something else. Write it to DB or write it to file. Or disable the debug node to keep values from scrolling off screen. Use something like flogger or the newer (and excellent) @zigasebenik/node-red-log-io to simplify and enhance writing debug data to log files even easier. Then you could use dashboard to view logs at will (keep a rolling batch etc)

2 Likes
8

That’s what I’m doing (activating a deactivating debug node). If there’s no other solution….

9

There are lots of other solutions that are infinitely better than copying debug messages from a text panel for manual inspection, but regardless, I doubt the new truncated view is going to go away. And TBF, it could change at any time. If you want reliable logging, then set something up that reliably logs.

I would probably recommend logging to DB or file (via an enable/disable) toggle but I don't know what your MQTT data is or what it is supposed to be because if it were a fixed topic and expected format, I would actually write some flow logic to analyse it for me (so I didn't have to copy strings from a text panel and manually inspect them in the first place - but that's just me.)

10

I usually don't need this information and the debug node is disabled. It is only when the equipment has problems, from time to time, that I have to check these values. A permanent log or sending them to a database would consume too many resources on a RPi with only 2Gb of RAM

11

i.e. enable it when required.

This node has an enable/disable feature built in

1 Like
12

Apparently not. On a Pi with v4.1.0 the debug is truncated to 1000 characters. Using the copy button and pasting into a file yields 1003 characters (1000 + ...)

13

The short visual truncation is the change in 4.1. The 1000 character limit has always been in place (setting.js setting). If the OPs debug messages are greater than 1000 characters each, they were never getting them anyway?

14

But regarding the ellipsis being appended to the copied value, I am not certain if that's new or existing behaviour. Either way, IMO, that behaviour is undesirable. I'm just not certain how else you can convey that the message was truncated at server side. Perhaps debug messages should have a flag (to indicate not full value) rather than just appending an ellipsis to the string?!?

15

For anyone else reading, this is why i recommend sending debug messages to console or to a database or file rather than depending on a sidebar text panel. Messages in the runtime (server side) will not be truncated. An additional side benefit of not sending messages to the sidebar is a speed up of the user interface (the less you send in debug, the more snappy things are)

16

As you can see in the images above, it is new. I've get one on an updated RPi. The other is still on previous version.

I'll give sending it to the console a try (if I can manage it).