Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no topic for incomming message #29

Open
zero1974 opened this issue Apr 27, 2022 · 3 comments
Open

no topic for incomming message #29

zero1974 opened this issue Apr 27, 2022 · 3 comments

Comments

@zero1974
Copy link

Hi all,
first of all: amazing project!! Thanks for all the work done.
I am new here and i deal with signalk and the node-red plugin since some weeks. I think i didn't understand how to create a topic witch is sent to signalk. I build a trigger and send temperature update via signalk-send-pathvalue. I made a screenshot also. I hope someone can help to fix the problem. Thanks a lot!!

@sbender9
Copy link
Member

I don't see a screenshot. Better yet, export your flow and post it here.

@zero1974
Copy link
Author

Many thanks for your quick response.

ok, i exported the flow and will paste it here. i modified it and the error "no topic for incomming message" is fixed. i forgot to declare the topic correctly...SORRY, i installed openplotter not so long ago... Now the flow works, but signalk cant xfer it to nmea2000 output. My goal is the following:

i would like to send data from my boat (nmea network and actisense NGT-1running on openplotter at raspberry 4 ) to my home-raspberry4 , running openplotter, too. So i have 2 signalk servers up. vpn things will be done in the future.

I want to test if it is possible to visualize the nmea2000 data from the boat at home, on my b&G Triton2 display, witch is connected to another NGT-1 by sending data from boat to my home signalk and trasform the data by using the plugin "signal-k to nmea2000" at home.
The flow works now, but

  1. it connects to the local (boat) signalk server because of using the node-red predefined flows and
  2. in the data browser (boat pi) i can see : Path, Value, units, timestamp and source correctly, but behind the source value, witch is 1.1,(coming from node red) there is no pgn number in brackets available like other source entries have: e.g nmea2000.2 (127258). Further on, the source: "node-red" printed below have no keys like other sources have, for example the nmea2000 source with 4 keys.

i would be very! happy about some help or ideas or maby a link to get some more input.
I hope you can comprehend .....
Here is the exported code:

[
{
"id": "ae7635f29dd78094",
"type": "tab",
"label": "Flow 1",
"disabled": false,
"info": "",
"env": []
},
{
"id": "604444910f84b34b",
"type": "signalk-send-pathvalue",
"z": "ae7635f29dd78094",
"name": "SendToSigK",
"source": "node-red",
"meta": "",
"x": 830,
"y": 320,
"wires": []
},
{
"id": "7cee26dd8febc84f",
"type": "inject",
"z": "ae7635f29dd78094",
"name": "manual trigger via timestamp",
"props": [
{
"p": "payload"
}
],
"repeat": "1",
"crontab": "",
"once": false,
"onceDelay": 0.1,
"topic": "",
"payload": "",
"payloadType": "date",
"x": 210,
"y": 240,
"wires": [
[
"611b087fa2c6276c"
]
]
},
{
"id": "1d067e73554dacc5",
"type": "debug",
"z": "ae7635f29dd78094",
"name": "",
"active": true,
"tosidebar": true,
"console": true,
"tostatus": true,
"complete": "payload",
"targetType": "msg",
"statusVal": "payload",
"statusType": "auto",
"x": 840,
"y": 160,
"wires": []
},
{
"id": "611b087fa2c6276c",
"type": "function",
"z": "ae7635f29dd78094",
"name": "",
"func": "msg.topic="environment.wind.angleApparent";\nmsg.path="environment.wind.angleApparent";\nmsg.source={"label":"node-red","type":"NMEA2000","pgn":130306,"src":"35"};\nmsg.$source="node-red";\nmsg.payload=1.1;\nreturn msg;\n",
"outputs": 1,
"noerr": 0,
"initialize": "",
"finalize": "",
"libs": [],
"x": 580,
"y": 240,
"wires": [
[
"604444910f84b34b",
"1d067e73554dacc5"
]
]
}
]

Thank you very much!

@sbender9
Copy link
Member

The source will always be node-red in this case.

Why do you care what the source is?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants