The problem was that "local" IP address, when a sysop is connected locally, was shown somewhere in the USA. Tried to fix it.

So, from the beginning, ignore everything above:

1.- Download and put these files in PhantomSDR-Plus/frontend/public
PhantomSDR-Plus
          └──frontend
                  └──public
                        ├── analyze_users.py
                        ├── stats.html
                        └── users.html

2.- Download and put in PhantomSDR-Plus this file:
fix_local_geo.py

and run it
cd PhantomSDR-Plus/
python3 fix_local_geo.py
python3 fix_local_geo.py --apply
This will clean all databases in logs/*jsonl files, with "local" fake IP data. It will not affect all the other data.
It is not needed to run it every time. Once only is enough. You can repeat the check from time to time, but there is no need more often.

3.- Recompile ONLY frontend.

4.- Refresh the webpage and check.
your_ip:port/users.html and e.g. http://phantomsdr.no-ip.org:8900/users.html
your_ip:port/stats.html e.g. http://phantomsdr.no-ip.org:8900/stats.html
will be there and in the history of stats.html fake "local" IP address will not be shown any more in the USA.

You are right!!!
So, please download the newer files from above and recompile frontend.
Now local IP address is not shown, a "local" only is, indicating that there is a user connected from the local network, and the .py does not search for an external IP and don't count it to the map.
This was the simplest way, because associating Local IP with the QTH info in "site_information.json" was pretty complex. Maybe until the "cumulative" update of the version, I'll find a way to associate also "local" with the real IP address of the server.

I live in America! 

http://9a7aof.ddns.net:8905/users.html

I suggest that local be linked to the
QTH locator of the PhantomSDR-Plus server, if possible.

73!
Darko,9a7aof

A map is added in frontend/public: users.html and stats.html.
You can see now on the maps:
- real time users location (users.html) on a map.
- history of the users (stats.html). Because this file stats.html reads the data from the .jsonl files located in the folder log, it would take some time to load this data and put it on the map, but after this you'll have all you users that visited your server during the dates you collect.

Download these files and put them:

PhantomSDR-Plus
          └──frontend
                  └──public
                        ├── analyze_users.py
                        ├── stats.html
                        └── users.html
recompile only frontend and refresh the webpage.

Please check here: http://phantomsdr.no-ip.org:8900/

P.S. Don't forget that you can see these webpages without to call them from the GUI. Jast load:
- your_public_server:port/users.html
- your_public_server:port/stats.html

Ok, I'll see how to fix that. Thanks, Emmanuel, for the information about the waterfall. I'll get to work on it and hope to achieve a good display that makes the receiver easier for users to use. We'll keep fine-tuning PhantomSDR+.

73s.

But let us talk now about brightness and contrast of the waterfall.
There are 2 ways to make waterfall less (or more) bright.

1.- Use by default the button Auto Adjustment. This is the "lazy" method.

• Find (line 320 in .svelte) let AutoAdjustEnabled = false; and make it let AutoAdjustEnabled = true;

• Find (line 397 in .svelte) onMount(() => { and add: 

onMount(() => {
  // ... your existing onMount code ...
 
  // Auto-enable adaptive auto-adjust on page load
  if (autoAdjustEnabled) {
    // Configure waterfall with adaptive settings
    if (typeof waterfall.setAutoAdjustConfig === "function") {
      waterfall.setAutoAdjustConfig(autoAdjustConfig);
    }
   
    // Enable auto-adjust
    if (typeof waterfall.enableAutoAdjust === "function") {
      waterfall.enableAutoAdjust(autoAdjustConfig);
    }
   
    // Start monitoring (if using adaptive)
    if (typeof startStatusMonitoring === "function") {
      startStatusMonitoring();
    }
   
    // Update UI button state
    const btn = document.getElementById("autoAdjustBtn");
    if (btn) btn.classList.add("active");
   
    console.log('🎯 Auto-adjust enabled by default');
  }

• recompile only frontend and reload the webpage

2.- More efficient method:

• Find (line 1933 in .svelte)  let min_waterfall = -30; and make it e.g.  let min_waterfall = -5;

• Open the file bands-config.js and adjust min and max for every band separately, until you will have the best visible results.

For example in MW you can set: min: min: 35, max: 130.
For 49m you can set min: -5, max: 130etc. etc.

Recompile only frontend and reload the webpage.From now on you and your users will see much less general 0-30 MHz brightness, and for each band a better visual waterfall.Try it!

Of course, you can use together methods 1 & 2. You will be tired to make a good balance, but the result will be good for you and your users. None of the users uses the sliders of Waterfall Control, they usually prefer "ready solutions"  .

Quote from: lu5dnp on May 11, 2026, 12:03 AMI'm not sure if it's because it's Android or if some configuration is missing.

The previous was a screenshot from my Samsung (Android) Nestor, using Edge. Maybe you need to clean the cache and retry.
The new screenshot is from the same mobile, using Mozilla.

Well, but on my mobile phone the indicator is there, but it only shows zeros. I'm not sure if it's because it's Android or if some configuration is missing. I'll see what I can find and whether I can fix it. Thanks.

Quote from: lu5dnp on May 10, 2026, 09:05 PMthe frequency indicator numbers do not appear

It is appeared! Maybe a cleaning of the cache is required??

Hello, greetings. I see that on mobile phones, the frequency indicator numbers do not appear. Everything works except that. Can this be fixed?