llopisdon / skies-adsb Goto Github PK

I have followed the instructions here including the steps needed for Flask server.

But all I am getting is just a few circles and no flights.

In the .env file I have included

VITE_SKIES_ADSB_HOST_EXISTING=127.0.0.1:30003

Since I already have dump1090-mutability running locally on a headless server. I even tested by telnet to port 30003 from another computer and I can see the SBS1 formatted messages.

And somehow after running the run_existing.sh script, port 5000 and port 5173(??) are responding to web requests.
Port 5000 just gives 404 no matter what I tried (e.g. http://ip:5000/ or http://ip:5000/skies-adsb/)
Port 5173 responded, but just a plain of circles even when I zoomed out I still didn't see any flights

BTW I modified the last line of run_existing.sh to npx vite --host so I can use the web browser on my Windows machine.

 ./run_existing.sh
 * Debug mode: off
WebSocket server settings:
  - Listen on :30006
  - No SSL/TLS support (no cert file)
  - proxying from :30006 to 192.168.x.x:30003
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on all addresses (0.0.0.0)
 * Running on http://127.0.0.1:5000
 * Running on http://192.168.x.x5000
Press CTRL+C to quit

  VITE v5.1.5  ready in 1876 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: http://192.168.x.x:5173/
  ➜  press h + enter to show help
192.168.x.y - - [20/Mar/2024 13:14:26] "GET / HTTP/1.1" 404 -
192.168.x.y - - [20/Mar/2024 13:14:26] "GET /favicon.ico HTTP/1.1" 404 -
192.168.x.y - - [20/Mar/2024 13:14:57] "GET / HTTP/1.1" 404 -
192.168.x.y - - [20/Mar/2024 13:15:24] "GET /skies-adsb/ HTTP/1.1" 404 -

Problem, any thoughts?

Cloning into ‘skies-adsb’…
[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

https://github.com/llopisdon/skies-adsb/blob/main/docs/INSTALL-GUIDE.md

The guide seems to couple dump1090 into your setup procedure.
It would be much nicer if you could separate that so people already running a decoder like readsb (https://github.com/wiedehopf/adsb-scripts/wiki/Automatic-installation-for-readsb) or dump1090-fa, don't install dump1090-mutability making 2 decoders fight over the SDR.

Also i'm not sure why you wouldn't want a systemd service to start dump1090-mutability.

Not an issue, just a comment.
I am looking forward to checking this out, but currently the way its setup, I just don't have the time to dig into your code and figure out how to run it without an SDR dongle. Like most of those of us doing ADSB we already have existing systems and data on port 30003 so just want to point your app to our feeds without needing another dongle and antenna splitter.
Once I figure that out, I will be able to provide more feedback I suspect.