Error Adding Flows

When I load node red from the browser it says "Error Adding Flows, Imported duplicate node" the node in question is Victron-Client-id [victron-client]

As it has taken me a few days to get to the point I can talk to the Victron wondered if someone could help me please ........ I'm very new to node red and have don Eno programming!!

Welcome to the forum @davenrea

Please stop node red then start it in a terminal copy/paste the startup log here. When you paste it in click the </> button at the top of the forum entry window and paste the text in.
Also tell us what OS/HW node red is running on.

Hi Colin, thanks for the quick reply. It is running on a raspberry pi, not sure how I see exactly what OS it is running - I'm seriously new to this!!

login as: pi
pi@nodered's password:
Linux nodered 5.4.72-v7l+ #1356 SMP Thu Oct 22 13:57:51 BST 2020 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Nov 29 08:28:54 2020 from 192.168.10.141
\pi@nodered:~ $ \
>
pi@nodered:~ $ npm install node-red-contrib-telegrambot
npm WARN deprecated request@2.88.2: request has been deprecated, see https://git                                  hub.com/request/request/issues/3142
npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated b                                  ecause it extends the now deprecated request package, see https://github.com/req                                  uest/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.jso                                  n'
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.

+ node-red-contrib-telegrambot@8.8.0
added 81 packages from 134 contributors and audited 253 packages in 15.749s

20 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

pi@nodered:~ $ npm install node-red-contrib-influxdb
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.jso                                  n'
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.

+ node-red-contrib-influxdb@0.5.1
added 3 packages from 7 contributors and audited 303 packages in 5.441s

20 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

pi@nodered:~ $ sudo reboot
login as: pi
pi@nodered's password:
Linux nodered 5.4.72-v7l+ #1356 SMP Thu Oct 22 13:57:51 BST 2020 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Nov 29 10:30:44 2020 from 192.168.10.141
supi@nodered:~ $ sudo reboot
pi@nodered:~ $
login as: pi
pi@nodered's password:
Linux nodered 5.4.72-v7l+ #1356 SMP Thu Oct 22 13:57:51 BST 2020 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Nov 29 10:47:27 2020 from 192.168.10.141
pi@nodered:~ $ sudo reboot
login as: pi
pi@nodered's password:
Linux nodered 5.4.72-v7l+ #1356 SMP Thu Oct 22 13:57:51 BST 2020 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Nov 29 14:38:09 2020 from 192.168.10.141
pi@nodered:~ $ ^C
pi@nodered:~ $
pi@nodered:~ $ node-red-stop

Stop Node-RED

Use   node-red-start   to start Node-RED again

pi@nodered:~ $ node-red-start

Start Node-RED

Once Node-RED has started, point a browser at http://192.168.10.223:1880
On Pi Node-RED works better with the Firefox or Chrome browser

Use   node-red-stop                          to stop Node-RED
Use   node-red-start                         to start Node-RED again
Use   node-red-log                           to view the recent log output
Use   sudo systemctl enable nodered.service  to autostart Node-RED at every boot
Use   sudo systemctl disable nodered.service to disable autostart on boot

To find more nodes and example flows - go to http://flows.nodered.org

Starting as a systemd service.
29 Nov 16:07:57 - [info]
Welcome to Node-RED
===================
29 Nov 16:07:57 - [info] Node-RED version: v1.2.5
29 Nov 16:07:57 - [info] Node.js  version: v12.19.1
29 Nov 16:07:57 - [info] Linux 5.4.72-v7l+ arm LE
29 Nov 16:07:57 - [info] Loading palette nodes
29 Nov 16:08:00 - [info] Settings file  : /home/pi/.node-red/settings.js
29 Nov 16:08:00 - [info] Context store  : 'default' [module=memory]
29 Nov 16:08:00 - [info] User directory : /home/pi/.node-red
29 Nov 16:08:00 - [warn] Projects disabled : editorTheme.projects.enabled=false
29 Nov 16:08:00 - [info] Flows file     : /home/pi/.node-red/flows_nodered.json
29 Nov 16:08:00 - [info] Server now running at http://127.0.0.1:1880/
29 Nov 16:08:00 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
29 Nov 16:08:00 - [info] Starting flows
client.startDiscovery({"discoveryInterval":10000,"offlineTolerance":1,"breakoutC                                  hildren":false})
client.getDevice({"deviceOptions":{"host":"192.168.1.112"}})
client.getSysInfo({"host":"192.168.1.112","port":9999})
TplinkConnection(TCP 192.168.1.112:9999).send({"payload":"{\"system\":{\"get_sys                                  info\":{}}}","timeout":1000})
TcpConnection(TCP 192.168.1.112:9999).getSocket()
[1] TplinkSocket(TCP).createSocket()
client.startDiscovery({"discoveryInterval":10000,"offlineTolerance":1,"breakoutC                                  hildren":false})
client.getDevice({"deviceOptions":{"host":"192.168.1.112"}})
client.getSysInfo({"host":"192.168.1.112","port":9999})
TplinkConnection(TCP 192.168.1.112:9999).send({"payload":"{\"system\":{\"get_sys                                  info\":{}}}","timeout":1000})
TcpConnection(TCP 192.168.1.112:9999).getSocket()
[1] TplinkSocket(TCP).createSocket()
29 Nov 16:08:00 - [info] Started flows
[1] TplinkSocket(TCP).send({"payload":"{\"system\":{\"get_sysinfo\":{}}}","port"                                  :9999,"host":"192.168.1.112","timeout":1000})
[1] TcpSocket: socket:send payload.length 33
[1] TcpSocket: socket:send attempting to connect. host:192.168.1.112, port:9999
[1] TplinkSocket(TCP).send({"payload":"{\"system\":{\"get_sysinfo\":{}}}","port"                                  :9999,"host":"192.168.1.112","timeout":1000})
[1] TcpSocket: socket:send payload.length 33
[1] TcpSocket: socket:send attempting to connect. host:192.168.1.112, port:9999
client.socket: UDP IPv4 listening on 0.0.0.0:44470
client.sendDiscovery(255.255.255.255, [], 1)
client.socket: UDP IPv4 listening on 0.0.0.0:56993
client.sendDiscovery(255.255.255.255, [], 1)
29 Nov 16:08:00 - [error] [influxdb in:Query InfluxDB] Error: connect ECONNREFUS                                  ED 127.0.0.1:8086
[1] TcpSocket: socketTimeout(1000)
[1] TcpSocket#destroy(),
[1] TplinkSocket(TCP).send() Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/                                  src/network/tcp-socket.ts:67:17)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
TCP 192.168.1.112:9999 Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/                                  src/network/tcp-socket.ts:67:17)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
29 Nov 16:08:01 - [error] [kasa:Fan Heater - HS100(UK)] Error connecting to devi                                  ce 192.168.1.112: Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
TCP 192.168.1.112:9999 Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/                                  src/network/tcp-socket.ts:67:17)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
[1] TcpSocket: socketTimeout(1000)
[1] TcpSocket#destroy(),
[1] TplinkSocket(TCP).send() Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/                                  src/network/tcp-socket.ts:67:17)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
TCP 192.168.1.112:9999 Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/                                  src/network/tcp-socket.ts:67:17)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
29 Nov 16:08:01 - [error] [kasa:Fan Heater - HS100(UK)] Error connecting to devi                                  ce 192.168.1.112: Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
[1] TcpSocket: socket:close, hadError:false
[1] TcpSocket: socket:close error
[1] TcpSocket: socket:close, hadError:false
[1] TcpSocket: socket:close error
29 Nov 16:08:05 - [error] [influxdb in:Query InfluxDB] Error: connect ECONNREFUS                                  ED 127.0.0.1:8086
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
8086
[1] TcpSocket: socketTimeout(1000)
[1] TcpSocket#destroy(),
[1] TplinkSocket(TCP).send() Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/                                  src/network/tcp-socket.ts:67:17)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
TCP 192.168.1.112:9999 Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/                                  src/network/tcp-socket.ts:67:17)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
29 Nov 16:08:01 - [error] [kasa:Fan Heater - HS100(UK)] Error connecting to devi                                  ce 192.168.1.112: Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
TCP 192.168.1.112:9999 Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/                                  src/network/tcp-socket.ts:67:17)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
[1] TcpSocket: socketTimeout(1000)
[1] TcpSocket#destroy(),
[1] TplinkSocket(TCP).send() Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/                                  src/network/tcp-socket.ts:67:17)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
TCP 192.168.1.112:9999 Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/                                  src/network/tcp-socket.ts:67:17)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
29 Nov 16:08:01 - [error] [kasa:Fan Heater - HS100(UK)] Error connecting to devi                                  ce 192.168.1.112: Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
[1] TcpSocket: socket:close, hadError:false
[1] TcpSocket: socket:close error
[1] TcpSocket: socket:close, hadError:false
[1] TcpSocket: socket:close error
29 Nov 16:08:05 - [error] [influxdb in:Query InfluxDB] Error: connect ECONNREFUS                                  ED 127.0.0.1:8086
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
8086
[1] TcpSocket: socketTimeout(1000)
[1] TcpSocket#destroy(),
[1] TplinkSocket(TCP).send() Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/                                  src/network/tcp-socket.ts:67:17)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
TCP 192.168.1.112:9999 Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/                                  src/network/tcp-socket.ts:67:17)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
29 Nov 16:08:01 - [error] [kasa:Fan Heater - HS100(UK)] Error connecting to devi                                  ce 192.168.1.112: Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
TCP 192.168.1.112:9999 Error: TCP Timeout after 1000ms
192.168.1.112:9999 {"system":{"get_sysinfo":{}}}
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/tplink-smarthome-api/                                  src/network/tcp-socket.ts:67:17)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)
client.sendDiscovery(255.255.255.255, [], 1)

If you are just starting I suggest you spend an hour watching the Node red Essentials videos which are linked from the node-red docs.

I see you have been trying to install nodes manually from the command line. You can do that if you want to, but you must do it from the .node-red folder. However it is usually easier to do it from within node-red using the Manage Palette option from the hamburger menu.
You seem to have some issues with the tplink smarthome node, which I don't know anything about, but for some reason it won't connect, similarly your influxdb node won't connect. Have you installed the influxdb server?

I don't see any messages there about the victron node. It might be worth clearing the browser cache and refreshing the node-red page to see if the error goes away, I have never seen that error. Is there a Recovery tab if you look in node-red? If so then it will contain 'lost' nodes that node red has found, you can safely delete those.
Finally there were some fixes in node-red 1.2.6, so it would be worth running the pi install/upgrade script again to update.

Thanks agin, started the videos, look helpful, will have to finish later wife is using words like nurd and geek!! I did start installing from the command line because that's what I thought I had to do but since found otherwise. The uplink was something in someone else's flow, I don't need them and will be deleting them as I and trying to set something up for controlling my Victron solar pv with the octopus agile tariff, Maybe I should try a fresh install after the videos and learning how to do the installing of 1.2.6.

Just so you don't think I am mad look at this project, I was working on it with a friend who is a software engineer and he was writing it as a bespoke program but unfortunately he died 5 weeks ago, young chap and marathon runner, had a heart issue no one knew about so I am determined to finish the project and this seems the only way I stand a chance!!

cheers

Dave

If you want to start again with a blank canvas all you need to do is to stop node red, delete the .node-red folder and restart node red.

excellent!!, I've just been trying to find out how to do this, thanks

OK, so I have updated to latest. deleted the .node-red folder loaded @victronenergy/node-red-contrib-victron and then just brought in a single node from Victron to monitor the battery and connected the output to debug. As soon as I refresh the page from a clean browser it tells me there is a duplicate of the * victron-client-id [ victron-client ] node. Even tried it on a different computer.

The flow I made continues in the background showing the battery voltage in the debug section but I can't see the flow on the main screen and I can't get rid of the error box without going through the deleting .node-red folder and starting again

any thoughts please?

When you have an error with a node it is always worth looking at node's github page (assuming it has one, it should be linked from the node's page in the node red flows site) and checking the issues there. This one, though the title no longer matches your symptom, explains the problem. I think you will just have to wait for a new release of the node. You could add a comment to the issue asking if there was any progress on it as it is preventing you from using the node. https://github.com/victronenergy/node-red-contrib-victron/issues/66

Colin

Thanks once again, just waiting for an update from them or a suggested work around.