I guess he is doing fine 
I have something weird happening now.
If I look at the tar1090 page, the airplane’s position don’t update unless I move the map with the mouse
or use the mouse wheel to zoom in-out. Sometimes just hovering the mouse makes the planes move.
Anyone has that happening?
Not yet so far.
Did you delete browser cache/cookies?
1 Like
It was the cache… Thanks!
1 Like
I’ve a strange issue. No matter what I adjust in /usr/local/share/tar1090/html/config.js the changes just dont seem to take effect in the webinterface. For example I’ve added ‘flightawareLinks = true;’ to the very bottom of config.js and yet the webinterface wont show the links.
I’ve even tried another computer to make sure it wasnt cache/cookies and thats the same.
Any ideas?
Did you restart tar1090 after making the change to the config file?
sudo systemctl restart tar1090.service
Yep - even went as far as rebooting, but still no changes.
This is grasping for straws but if you added that line to the very bottom, is this line
// flightawareLinks = true;
still in the file (double slash)? Like it reads that line first and ignores the conflicting command?
In my case it’s buried in amongst these lines (I have removed the double slash to enable the links):
//labelFont = ‘bold 12px tahoma’;
//displayUATasADSB = false;
//uatNoTISB = true;// Don’t display any TIS-B planes
// filterTISB = false;flightawareLinks = true;
//shareBaseUrl = ‘https://globe.adsbexchange.com/’;
// planespottersLinks = false;// show links to various registration websites (not all countries)
// registrationLinks = true;
There is a specific section in the tar1090 README about enabling/disabling FA links. It pretty much does what you manually edited so not sure why it is not working for you. But you could just revert back to the default (//flightawareLinks = false;) then run the suggested command to see if that works. FWIW, I ran the command on an instance of combine1090 used to view HFDL data and it enabled the links as advertised.
The most likely issue is that you have wrong syntax. somewhere in the file.
Have you tried other settings and if they take effect?
cat config.js | nc termbin.com 9999
Can you use this command and share the link, someone can then the check the js file for errors.
Welcome back @wiedehopf !
Glad to see you after a long gap.
2 Likes
Thanks for the reply @wiedehopf here’s the output of the command you provided.
I used to have the adsbx map as my default in tar1090, I changed the entry in /usr/local/share/tar1090/html/config.js a few days ago to be this:
// which map is displayed to new visitors
MapType_tar1090 = "openstreetmap";
Even after restarting the service and clearing my cache (and rebooting the Pi to be sure), I’m still getting the silly no-map map as the default.
Can anyone check their config for me please and tell me what I’ve done wrong.
Also…
Is there any way to stop the map from defaulting to ‘dark’ mode? Not dimming, I’ve got that set to false in the config file, it’s the actual dark mode I’d like to have switched off.
Thanks.
// which map is displayed to new visitors
MapType_tar1090 = "osm";
//
// valid values for the above setting:
// osm
// esri
// carto_light_all
// carto_light_nolabels
// carto_dark_all
// carto_dark_nolabels
// gibs
// osm_adsbx
// chartbundle_sec: "Sectional Charts",
// chartbundle_tac: "Terminal Area Charts",
// chartbundle_hel: "Helicopter Charts",
// chartbundle_enrl: "IFR Enroute Low Charts",
// chartbundle_enra: "IFR Area Charts",
// chartbundle_enrh: "IFR Enroute High Charts"
Ahh, thanks. My version doesn’t have those valid type values below.
Now what about Dark Mode, is there any way to stop that being the default?
1 Like
Toward the end of my config.js is this line:
darkModeDefault = false; // turn on dark mode by default (change in browser possible)
3 Likes
Perfect, added that line, restarted the service, cleared the cache on the browser and it comes up in light mode.
I am content
1 Like
Glad to hear that helped. Like you I am not a fan of “dark mode”, it just makes me squint and very sleepy. The snips I provided are from the config.js as installed from running wiedehopf’s script. Maybe your version is a little out of date? I re-ran the script several weeks ago to pull in any changes - upper right corner of tar1090 GUI shows 230731.
2 Likes