A.R. - I am writing a flow that can generate a ...
I am writing a flow that can generate a POB alert. If I have understood the documentation correctly I need to set a specific message topic with a unique id for each alert. Example:
vessels.609ea296-b561-4f1f-81af-0b497c783868.notifications.mob.tracker1 But when I look at the data path in SignalK it is just notifications. Is that correct?20 Replies
Yeah, that id does not go there.
Where did you see that?
https://signalk.org/specification/1.7.0/doc/notifications.html and then at alarm processes
Other alarms: "In the case of an emergency, create a unique key: The alarm is : vessels.[uuid].notifications.[alarm.key]"
hmm. Ok. Don’t think ever saw that. Might want to wait for others to chime in.
Well hmm. If I read it again it says "unique key" not UUID.
and key is at the end and unique, since it is for a tag.
🙂
But could I do self.notifications too or do I have to retrieve my vessel urn and create that path?
I can tell you this, WilhelmSK and any plugins I’ve written that look at notifications, would not see that.
KIP did see it.
I guess since it’s just something for you in node-red, I wouldn’t worry about it too much. As long as it works with stuff you are using.
Definitely won’t hurt to leave the id out
Yeah ID is out. Just wondering if the path self. notifications is enough. Or how to get vessels.urn:
And it is working for me but it raises alarms in KIP and Openplotter and that are a lot of alarms which would chime in a stress-full situation. So getting something that is inituitive for such a moment is something to aim for.
Are using the the send-notification node?
yes
then the Path should just be "mob.tracker1"
I need to fix the docs for that node...
🙂
Let me test that.
I just verified with the code too, it puts "notifications." on the front of what you enter for Path.
and this is probaby why it was working for you with id
Okay but I set the path by using the message topic, is that the same just
mob.tracker1 because the message still appears at notifications. and not notificatons.mob.tracker1 Yes, setting by topic is the same. It automatically adds the notifications. prefix
Ok I found that if I set the path in the send-notification node like
mob.test it lands at notifications.mob.test But if I set it using the message topic it arrives at notifications. So I think maybe the node does not properly process the .topic of the incoming message?oh!
you are correct
it's ignoring topic
oh, it's look for "msg.path"
which is what the docs say
Ah who reads those!
😉
🤣
I am definitely going to make some fixes/changes here…
Well for now I will set both .topic and .path
And.... it still lands at
notifications. .....
Well read the manual... I have to provide the full path within the payload.
so not msg.path but message.payload.path
Coming back to this if you don´t mind
For the MOB alert I send a postion with the alert so this can be picked up by FreewindSK. But the signalk-send-notification node does not pass anything else through then what is has as parameters.
Example message I want to send. FreeboardSK does this too (but does not yet set the path correct)