[warn] Skipping field 'value': unsupported type object

General
1

i'm getting this warning in the console and the online debug window sometimes.

18 Feb 08:33:41 - [warn] Skipping field 'value': unsupported type object

image

My project is HUGE (flows.json is 3.8Mb). So it is hard to track down.
There is no other info about where this message is coming from in the output

Is there a way to find out? can i enable more debug info?

2

Should also appear in the Node-RED log. You may need to up the logging level to get more clues.

3

I changed logging to trace. but get the same output.

i'm using "node-red-log".

is there a log with more details than that somewhere?

4

With trace, you should at least get an idea of where in your processes the warning is being generated. You could also turn on the audit feature of the log though the output can be rather crazy. There is no other log.

You might also think about what nodes you have installed. Generally disconnected warnings and errors come from contributed nodes but looking at that one, could it possibly be from Dashboard 2?

Next steps will be trying to disable parts of your flows or doing a filing system search through your userDir folder (including the node_modules folder) for the text "Skipping field". It's a long slog though unfortunately.

5

That message is not one Node-RED core outputs so it is either written in your flows or coming from a contrib package.

Have you searched your flows (CTRL-F) for Skipping?

6

Yes i have. no results.

searched the source of the suspected contrib node

and here it is. the debug output should show where the warning comes from.

image
image1066Ă—306 36.7 KB

7

Ideally it would. But this is a limitation of how node.js works. Sometimes, things are so deeply embedded that Node-RED cannot know where the message came from. In my nodes, I always make sure that every message is prefixed with the node name and function name, somthing like this: [nodename:fnname] Some error.

8

that's a good practice

1 Like
9

If you've the time, you should raise an issue against that repo.

10

Already done. Thanks :slight_smile:

1 Like
11

Does node-red-contrib-influxdb not work with v3?

12

No

image
image292Ă—257 3.69 KB

13

Have you tried it? I suspect that the API for v1 is upwards compatible to 3.

14

If you add a Debug node showing what is being sent to the node, set it to Output Complete Message and to Send to Console then it will log all the messages you send it in the node red log. Then after it occurs you can look back through the log and see what you sent it. The warning suggests that you are sending an object to the value field.

Note that the warning from the node may appear immediately before you debug information as the message into the debug node may be serviced after it is handled by the influx node.

1 Like