question

nuxland avatar image
nuxland asked

Node-Red exception

For some time I have at random time's this in my node-red log file.

And I can not figure out what is causing it. It seems to be one of Victron own nodes but what exactly?

@400000006399809207dd9e54 14 Dec 09:51:36 - [red] Uncaught Exception:

@400000006399809208d6236c 14 Dec 09:51:36 - [error] TypeError: Cannot set property 'deviceInstance' of undefined

@400000006399809208d64e64 at Object.<anonymous> (/usr/lib/node_modules/@victronenergy/node-red-contrib-victron/src/services/dbus-listener.js:124:57)

@400000006399809208d661ec at EventEmitter.<anonymous> (/usr/lib/node_modules/@victronenergy/node-red-contrib-victron/node_modules/dbus-native/lib/bus.js:138:19)

@400000006399809208d67574 at EventEmitter.emit (events.js:412:35)

@400000006399809208d67d44 at /usr/lib/node_modules/@victronenergy/node-red-contrib-victron/node_modules/dbus-native/index.js:106:14

@400000006399809208da22dc at Socket.<anonymous> (/usr/lib/node_modules/@victronenergy/node-red-contrib-victron/node_modules/dbus-native/lib/message.js:55:9)

@400000006399809208da3e34 at Socket.emit (events.js:400:28)

@400000006399809208da49ec at emitReadable_ (internal/streams/readable.js:550:12)

@400000006399809208da55a4 at processTicksAndRejections (internal/process/task_queues.js:81:21)

@400000006399809217892774 *** starting node-red-venus ***

@40000000639980921a697b74 *** Waiting for localsettings...

@40000000639980921d4483fc *** Starting in normal mode

@400000006399809738f3662c [info]: loading /data/home/nodered/.node-red/settings-venus.js failed

@40000000639980991c70a5b4 14 Dec 09:51:43 - [info]

@40000000639980991c70c8dc

@40000000639980991c70ccc4 Welcome to Node-RED

@40000000639980991c70d494 ===================

@40000000639980991c70d87c

@40000000639980991d6765ac 14 Dec 09:51:43 - [info] Node-RED version: v3.0.2

@40000000639980991dcde00c 14 Dec 09:51:43 - [info] Node.js version: v14.17.4

@40000000639980991dcdff4c 14 Dec 09:51:43 - [info] Linux 5.10.109-venus-8 arm LE


Node-RED
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

1 Answer
Dirk-Jan Faber (Victron Energy) avatar image
Dirk-Jan Faber (Victron Energy) answered ·

Which version of firmware are you running?

9 comments
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

nuxland avatar image nuxland commented ·
Latest Release: v2.92
0 Likes 0 ·
Dirk-Jan Faber (Victron Energy) avatar image Dirk-Jan Faber (Victron Energy) ♦♦ nuxland commented ·
Thanks. Do you mind sharing your flows with me (you can mail them if you prefer that) so I can take a closer look? And can you tell me what hardware is connected?
0 Likes 0 ·
nuxland avatar image nuxland Dirk-Jan Faber (Victron Energy) ♦♦ commented ·

My VRM portal id is: 48e7da8999bd

So you can look there what hardware I have.

And I have a lot of flows together 6 or more tabs. So I can export them and compress to zip file but where do I find your email to mail them?

0 Likes 0 ·
Dirk-Jan Faber (Victron Energy) avatar image Dirk-Jan Faber (Victron Energy) ♦♦ nuxland commented ·
Thank you. With the vrm id I was able get de device list. And am also able to fetch the flows, so mailing is not needed. You do indeed have quite a lot of flows.

I am fairly sure that the problem will be solved with the next release candidate which will carry version 1.4.25 of node-red-contrib-victron. But that is of no help right now.

I will try to replicate the reproduce your issue on my test system and report back. Note that that might take a few days.

0 Likes 0 ·
Dirk-Jan Faber (Victron Energy) avatar image Dirk-Jan Faber (Victron Energy) ♦♦ nuxland commented ·

I did some checks on different systems and am quite sure that it is one of the connected devices that is causing it. Question is which one. I checked some of the devices that I have around (grid meter, shunts and mulitplus). But those do not seem to cause it. Do you mind enabling remote support on your system, so I can login, check the logging and the dbus and hopefully locate the cause?

0 Likes 0 ·
Show more comments