❌

Modalità di lettura

↗️

Re: AIS and APRS disappear in menu .

✇OpenWebRX
di: luarvique@... (Marat Fayzullin)
On Sat, Jun 13, 2026 at 12:05 AM, EA5TB - Luis wrote:
Hi Again. 
 
I tried to perform apt remove and again install direwolf but didn't noticed any fix. 
 
 
The answer is staring you in the face from your last screenshot. You just need to read it.
  •  
  • ↗️
↗️

Re: AIS and APRS disappear in menu .

✇OpenWebRX
di: mail@... (EA5TB - Luis)
Hi Again. 
 
I tried to perform apt remove and again install direwolf but didn't noticed any fix. 
 
To be sure, i created new VM with ubuntu 24.04, and perform installation again of openwebrxplus directly, and with the clean and initial setup ,
In this new setup, I also don't see Packet option by default as I always have seen when I have installed openwebrx. 
 
I have no more ideas to investigate. 

any help.?. Thanks ! 
 
 
  •  
  • ↗️
↗️

Re: Native OpenWebRX Client for Android

✇OpenWebRX
di: luarvique@... (Marat Fayzullin)
The OpenWebRX Android Client v1.4 is now available from Google Play. It adds RDS data display for FM stations, extends magic key use, and fixes a few bugs. See below for all the changes:

— Added RDS display in WFM mode.
— Added multiple reconnection attempts.
— Added separate "connecting" icon.
— Fixed potential crash when updating bookmarks.
— Magic key can now unlock locked sources and profiles.
— Magic key now added to the web UI URL.
 
Screenshot_20260611_202529_OpenWebRX.jpg
  •  
  • ↗️
↗️

Re: Feature request OpenWebRX+

✇OpenWebRX
di: luarvique@... (Marat Fayzullin)
On Thu,
While this thread is going, I'll chime in that it'd be nice to have a feature to speed up and slow down the vertical time display.
 
This is configurable via "Settings | General | Waterfall Settings".

As well, I'd like to see the WFM mode be adjustable in bandwidth. I am monitoring some LoRa signals (a form of FM). I don't listen to broadcast FM radio, instead I use the WFM mode to "hear" the  LoRa frames and symbols
 
 
I do not believe this is how WFM mode was supposed to be used.
  •  
  • ↗️
↗️

Re: Feature request OpenWebRX+

✇OpenWebRX
di: n7uv.jon@... (Jon Adams)
Marat - thanks again for providing this very nice tool to observe radio spectrum. I'm always surprised by people who have no real idea of what's going on in the frequency domain, especially when there are apps like this.
 
What the OP suggested, having a peak/average holding spectrum display, would be pretty sweet.
 
While this thread is going, I'll chime in that it'd be nice to have a feature to speed up and slow down the vertical time display. Right now it seems to be about 70 seconds top to bottom, I am monitoring our local 70 cm LoRa network, and the digipeaters are really fast, so a single frame could get digipeated several times in 1 second. Some of the blobs below are actually multiple LoRa transmissions closely spaced in time. (Most of the frames below are saturating the SDR receiver due to the antennas being only 2 m apart.)
 
As well, I'd like to see the WFM mode be adjustable in bandwidth. I am monitoring some LoRa signals (a form of FM). I don't listen to broadcast FM radio, instead I use the WFM mode to "hear" the  LoRa frames and symbols (it's an easy way to translate a very wide-band signal into something that a human can hear). Being able to adjust the bandwidth to fit the LoRa bandwidth will help with the signal to noise ratio my ear hears. 
mceclip1.png
 
Cheers and 73 - Jon N7UV
  •  
  • ↗️
↗️

Re: [new] Improved OpenWebRX Packages Available

✇OpenWebRX
di: luarvique@... (Marat Fayzullin)
The new OpenWebRX+ 1.2.116, available from the repository, adds Sondehub reporting and a few fixes. See below for all changes.
 
- Added Sondehub reporter for RS41 telemetry [Hai Tran].
- Added paho-mqtt 2.0 compatibility [Marc Fontaine].
- Added per-profile PPM correction option.
- Fixed exception when stopping AdsbParser.
- Fixed exception when stopping services.
 
Sondehub-Reporter.png
 
PS: Short cheat sheet for people who just cannot get things to work:

1) If it does not work for you, reload OpenWebRX page while holding the SHIFT key.
2) If it does not work for you, check "Settings | Feature report" page to see what you are missing.
3) If it does not work for you, wait for a day or two, maybe it starts working or you figure it out.
4) If it does not work for you, create a separate forum thread and explain your problem there. Attach the logs, obtained with "sudo journalctl -u openwebrx". Do not paste the entire log into the message, attach it as a file instead.

  •  
  • ↗️
↗️

Re: AIS and APRS disappear in menu .

✇OpenWebRX
di: mail@... (EA5TB - Luis)
Sorry for my delay in reply Martin; I was in a trip. 
 
in the feature report , I don't see AIS in the list (strange), and about packet, I see that is not installed. 

Maybe I need to install Direwolf package. I didn't see that Warning and I supposed that it was installed by default.
I'm going to try. 
 
mceclip0.png
  •  
  • ↗️
↗️

Re: Native OpenWebRX Client for Android

✇OpenWebRX
di: luarvique@... (Marat Fayzullin)
The OpenWebRX Android Client v1.3 is now available from Google Play. It adds APRS and AIS packet display, magic key entry, and lets you jump outside the current profile by long-pressing the double arrow buttons. See below for all the changes:

* Added APRS, AIS, and radiosonde log display.
* Added band frequencies (FT8 etc) as bookmarks.
* Added magic key entry.
* Fixed monospaced display font on some devices.
* Fixed step tuning from unaligned frequency.
* Fixed server search bar in dark mode.
* Long press on double arrows jumps frequency.
* Sorted list of modulation types.
* Improved decoder log formatting.

Screenshot_20260528_192405_OpenWebRX.jpg
  •  
  • ↗️
↗️

Fix input frequency in khz

✇OpenWebRX
di: cfgiordani@... (Carlo)
Is it possible (is there a setting) to set the default input frequency in kHz instead of MHz?
Entering
mceclip0.png
 
the frequency returns in MHz
 
mceclip1.png
 
Not a big issue, anyway 😊
 
Carlo
  •  
  • ↗️
↗️

Re: Feature request OpenWebRX+

✇OpenWebRX
di: ivanmarcus@... (ivanmarcus)
Perhaps, in the meantime, and getting back to your original question, if anyone wants to alter the height of their spectrum display you can do so simply by *editing .../htdocs/css/openwebrx.css

Look for a line that begins ".openwebrx-spectrum-container" (line #2069 in the file I just viewed) and change the "max-height:" directive in the block below from 50px to your preference - for example 100px.

Do the same for the following block beginning ".openwebrx-spectrum-container.expanded"

This should be all that's needed, you may need to refresh your session and/or restart for the result to be observed.

Note: If you're at all uncertain you would be advised to back up your installation before making any changes.

That said it's an easy change and I'd encourage people to experiment and learn more about their systems. Who knows, one day you may be able to contribute some code back to further improve OpenWebRX.

*A good editor for many Linux distributions is 'nano'.
  •  
  • ↗️
↗️

Re: Feature request OpenWebRX+

✇OpenWebRX
di: ivanmarcus@... (ivanmarcus)
Martin,
 
I downloaded Marat's recent work and had a look re your request. It turns out he's changed things quite a lot since I originally implemented the spectrum display, so although I still think you should have a go I also took pity on you ;) 
 
Per the images below I've implemented a 'peak hold' line as well as reintroducing the spectral colour that I used to have in my version. The latter is simply personal preference, or vanity if you prefer, as it happens I quite like Marat's single colour display but while I was messing around with things I thought why not?
 
Did additionally consider adding the relative dbFS lines I had but was running out of [solar] battery and had spent quite enough time trying to find a working SDR unit and set up a machine etc etc (sadly my Mirics-based device appears to have died, so had to find an old 'TV' RTL device instead) therefore this is what you've got.
 
For the present the peak hold line will remain until the spectrum display is toggled off, at which point it's cleared. It could also be easily set to decay over a long period if that was preferable. If it's of interest I can tell you what to alter/add in the requisite file, or maybe just email said file to you....
 
Frequencies removed from images to protect the innocent:
 
Screenshot_2026-06-02_10-40-06.jpgScreenshot_2026-06-02_10-45-51.jpg
 
 
  •  
  • ↗️
↗️

Re: OpenWebRx, Airspy r2, Raspberry Pi 4

✇OpenWebRX
di: nigel@... (Nigel G4ZAL)
I have recently switched to using an Intel NUC i5.
When compared to the price of a new R-Pi 5, there was no contest and the performance is much better.  The NUC is around twice the physical size of a cased R-Pi and about half the price of a R-Pi5 4Gb.
A good used NUC i5 (or i3) can be had on the famous auction site for not too much money.
If you shop wisely, you can get one with 4 or 8Gb RAM and a 120Gb SSD, most are without a PSU, but a suitable laptop PSU will work fine (they will run from 12v - 19v).
I struck lucky and got a 'barebones' NUC5i5 for under £20 (20GBP) delivered as I had a suitable 4Gb stick of RAM, 120Gb SSD and PSU from a dead laptop - winner!

Nigel, G4ZAL
  •  
  • ↗️
↗️

Re: Feature request OpenWebRX+

✇OpenWebRX
di: martin_ehrenfried@... (Martin)
Yes, OWR uses dBFS, it has to be this way because it can use different receiver hardware, each with different gain settings.
 
It could be possible to calibrate using a signal generator, but most admins don't have access to such things.
 
The Kiwi uses standard hardware, so the software can be roughly calibrated using pre-determined average values, however these do vary from batch to batch, and there is an offste value that can be applied by the admin, if they have a suitable calibration source available.
 
Regards,
 
Martin
 
On Sun, May 31, 2026 at 02:22 PM, <franzmann@...> wrote:
  •  
  • ↗️
↗️

Re: Feature request OpenWebRX+

✇OpenWebRX
di: franzmann@...
Yes, it was me to mention the FW-deviation issue.

Yet, I am still convinced that OWRX still works with dB_FS and does not offer and dBm-calibrated reference.
The latter is found with Kiwi and web-888.
But I can live with that - as well with the unavailable GPS-reference.

openwebrx is and remains attractive - thanks to Jakob and Marat!

Am 31.05.26 um 07:03 schrieb ivanmarcus via groups.io:
  •  
  • ↗️
↗️

Re: Feature request OpenWebRX+

✇OpenWebRX
di: franzmann@...

Well, if 10 people are sitting on a table, a normal conversation is no longer possible:
Everyone steps up by 3, 6 or even 10 dB.

--> in the end, all of them are "pirates".

Am 31.05.26 um 10:19 schrieb Martin via groups.io:
  •  
  • ↗️
↗️

Re: Feature request OpenWebRX+

✇OpenWebRX
di: martin_ehrenfried@... (Martin)
The peak hold outline will provide an indication of the maximum deviation over a period of time.
 
I worked on broadcast transmitters in the UK, during a period of time we called "the loudness wars", it was when stations started to use more processing on their FM transmissions, and the deviation kept on creeping up, as they tried to sound louder than the other stations on the dial. Some were really excessive, and you couldn't listen to them for more than a few minutes before they became fatiguing.
 
Fortunately some sense prevailed and things improved, but there are still a reasonable number of FM pirate stations around London, that use so much deviation and processing that they make your ears bleed.
 
Regards,
 
Martin
 
On Sat, May 30, 2026 at 11:19 PM, <franzmann@...> wrote:
  •  
  • ↗️
↗️

Re: Feature request OpenWebRX+

✇OpenWebRX
di: ivanmarcus@... (ivanmarcus)
It's been a while but as I recall I coupled the scale to the waterfall display so it changed appropriately as that was altered.

No-one ever asked for deviation measurement, the image I posted was simply a (then) example of some of the changes I'd made - including the 'peak hold' that Martin was asking about.
  •  
  • ↗️
↗️

Re: Feature request OpenWebRX+

✇OpenWebRX
di: franzmann@...

Looks interesting. 
Is your scale "calibrated" in dBm?

For WFM, however, the (peak) deviation is essential since commercial stations frequently work with
excessive values >> 50 kHz and often more than 100 kHz. 
There are, indeed, some supervisors in some countries, and they do dispose of professional
equipment.
However, sometimes, I think, they are Trump-followers and are dozing, drowsing, snoozing, catnapping
and maundering - the usual occurrence in many public services...

73, Wolfgang

Am 31.05.26 um 00:34 schrieb ivanmarcus via groups.io:
  •  
  • ↗️
❌