Replies: 3 comments
-
Like that idea. I was already thinking about option define regions so can show the table in a grouped way (Port of A, Channel A, Port of B, Rest, perhaps color coded). I would like that for my own station covering two ports, river and some sea. PlaneAlerter seems to be a nice concept to build out for AIS. Thanks for sharing! Didn't know it. Idea is though to define the areas and rules on aiscatcher.org which than are pulled locally into the webviewers via the sharing key. Otherwise need to build too much logic. ps and great to hear that you love the app! |
Beta Was this translation helpful? Give feedback.
-
This may be useful for others https://github.com/sdr-enthusiasts/docker-vesselalert?tab=readme-ov-file#introduction |
Beta Was this translation helpful? Give feedback.
-
I wrote my own notifier based on Node-Red. I send data over MQTT qnd pick it up in Node-Red. I then can filter and create what I want to alert on and send it ot a number of sources. Currently I have my alerts going to a telegram bot but I understand the Pushover is easy as well. I'd be happy to share flows if you are interested. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Absolutely love the app!
A fun suggestion would be to have an alerts functionality. So maybe AIS Catcher could fire an email or pushover alert if a vessel which the user has specified enters a certain port or area?
Same could be done for specified SAR helicopters.
This can be useful if an alert comes in for a SAR asset that pings perhaps late at night, which may mean that a SAR is underway not just training.
https://github.com/Dom2364/PlaneAlerter has done something similar for ADSB data but it is limited to one location.
Marinetraffic have the option as part of their premium alerts package also.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions