This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
Just wondering if anyone has looked at how to get Node Red to send a message to a NMEA 2000 device. I am looking to install a yacht devices YSDC-04, and want to to switch the switches within Node Red flows.
Just asking if anyone has any pointers.
I am aware of the @signalk/node-red-embedded for when node-red is embedded in Signal
Hi @Bathnm,
I don't know of any way other than using the nodes from node-red-embedded within SignalK. Unfortunately their nodes are working only when embedded.
I've two YDCC-04 and switch them remotely using SignalK -> signalk-n2k-switching-plugin -> WilhelmSK
Looks like you an do it, but requires a fair amount of work.
watched this Youtube Video. Open a session to port 8375, then parse the msg payload for what is required. Not sure how to push data back to SignalK,
Wonder if we just load the Victron contrib into the embedded node red?
Not really much work. But I use WilhelmSK for visualisation and control. This makes things a lot easier.
Have been following his channel on youtube for quite a while. Parsing msg.payload is the easy part, push into N2K is not because it's RAW data and needs to be converted.
Yes, installing @victronenergy/node-red-contrib-victron into SignalK Node-Red embedded should work.
Do you know if we can install the Victron components into the embedded node red. If so then we just do that and turn the main node red off...
I could try, but currently I have wrecked my node-red installation from the large image. But I'm pretty sure that this will work.
I have node red embedded in SignalK with the Victron palette installed.
So it comes down to which node do you build flows in! Both could be a bit confusing.
It depends on what you want.
For switching the YDCC-04 via node-red, you don't need the Victron nodes.
Provided that your n2k network is connected to signalk, n2k raw data is converted to signalk paths. Then use the signalk-input-handler node to read the state of the switching device channel, change the state with a change node and send it back to n2k with signals-send-nmea2000 node.
Do you have a further example of switching a data channel on the YDCC-04
You mean from within node-red? No, sorry. As said earlier, I'm doing this via Signalk Server.
What exactly you are looking for?
Just wondering how you are using SignalK to switch a channel on or off.
But you might run into a bit of trouble with the victron nodes. At least for the moment until the issue is fixed. I just got the same problem:
https://github.com/victronenergy/node-red-contrib-victron/issues/66
Hey @Stefanie, that issue was fixed by sbender in v1.4.0 or v1.4.1 - so I'm not sure how you can run into that.
Yes I know, Matthijs.
NPM is showing 1.4.1, but when installing the nodes into a SignalK installation without Venus, they show up as 1.3.2.
I don't know how to check node-red-contrib-victron version, but I'm pretty sure they install as 1.3.2. At least that's what the screenshots and duplicate nodes message suggest.
I
@Stefanie, I have managed to get 1.4.1 installed in the embedded node-red.
I tried running this command in the directory /data/conf/signalk/red which is the embedded node red
npm install /usr/lib/node_modules/\@victronenergy/node-red-contrib-victron
This should have created a link to the installed version, and it kept failing. I then ran this command
npm i @victronenergy/node-red-contrib-victron
in the same directory and all sorted. I now have 2 node red's, one that has no knowledge of the NMEA2000 capabilities of signalK and one that does.
Making the embedded the one accessible via port 1880 would be brilliant as it means only one is installed.
