Logger

[elfin kettle]

on the other hand the Logger from the Scanner worked absolutely fine 🙂

you can check the signals sequence in my Scanner log

[dire magnet]

I'll try to take a look at it tonight. 73, Highpoint

[dire magnet]

Unfortunately, I didn't get around to it yesterday, because I installed the Rotator plugin for an English DXer remotely and we also had the best Tropo conditions and still have them now. At the moment, Northern Germany and Denmark are here. I won't be able to take care of it until next week.

[dire magnet]

@elfin kettle Good morning! Can you please describe the problem with the RDS logger to me again in detail? For information: If they only receive one station, it will of course be overwritten again and again, because the plugin assumes that there was no Pi + frequency change and it has to continue to update the entry, regardless of whether they stay on the frequency or find it again and again through the scanner. This also makes sense if you log live (zap through the frequencies) and want to get as much information as possible. A new entry (next line) only occurs when it is detected a pi code on a different frequency. In my opinion, live logging is also the main use case for the RDS logger, as the scanner has its own log protocol with its own (optimized) conditions.

[elfin kettle]

Hello @dire magnet

there are two cases I have seen

First one:

1. Station 1 is found => one entry in the log

2. Next loop of the scan the same station is found => second entry in the log

3. Next loop of the scan and the same station is found => The second entry is updated

from this point the second entry is updated

the Scanner logger logs all of these as separate entries => this is ok I would say

Second case;

1. Station 1 is found => one entry in the log

2. Next loop of the scan the same station is found => second entry in the log

3. Next loop of the scan and the same station is found but during the hold time the signal drops and a fake PI appears => The log entry is updated with the wrong one that cannot be identified

the Scanner logger works just fine... if the UI would work the same way would be nice

I do not see a reason to have differences

unless is impossible to do 🙂

example: http://188.24.148.184:8080/logs/SCANNER_2024-08-31_filtered.html

the entry at 15:14:52

in the UI logger the correct entry (from previous loop) was overwriten.. I do not have the UI log anymore, just the Scanner one which is correct

[elfin kettle]

any manybe one more idea: the unique filter could be added to the html template... everyone can filter offline the data... in this case nothing is lost

[dire magnet]

The idea is not bad, but it would require that all raw data must always be stored and we would have a very, very long document, which is processed very sluggishly by the browser. you are welcome to test it with the current functions and a longer RAW LOG of the scanner.

Nothing is lost if you call up the RAW log instead of the filter, right? The RDS Logger always writes both log files to the array, so that you can also retrieve both.

[elfin kettle]

I think you missunderstood me 🙂

[dire magnet]

Regardless of whether the filter is active or not. I had corrected this in one of the last versions.

[elfin kettle]

the Scanner log is filtered and just fine

if the same will be for the UI one then we are good 🙂

however you may be right regarding the fitering in the html... now thinking how many stations you get in the log

but RAW and html is a bad idea... when that bug with multiple entries in the log happend my server was running into small issues

(there where 2500 records in the html at that time)

[dire magnet]

@elfin kettle You can test! I think I have found the error:
https://github.com/Highpoint2000/webserver-logger
A new entry is now created every time a frequency or PI change occurs. 😉 If you give your ok I would finalize and release the 1.6 today. I have adapted the log table analogous to the scanner.

[elfin kettle]

nice, I will try it 🙂

[dire magnet]

I'm curious 🤗

[elfin kettle]

DATE TIME FREQ PI PS NAME CITY ITU POL ERP DIST AZ
2024-09-05 17:54:26 106.400 826E EBSRadio EBS Radio Vârful Postavarul ROU V 0.3 11 194
2024-09-05 17:54:26 106.400 826E EBSRadio EBS Radio Vârful Postavarul ROU V 0.3 11 194
2024-09-05 17:54:26 106.400 826E EBSRadio EBS Radio Vârful Postavarul ROU V 0.3 11 194

please update the hour

do not add the same hour every time

I have tested with white list where I only added a station with signal

all the rest do not have signal

the scanner logger shows correctly all this

DATE TIME FREQ PI PS NAME CITY ITU P ERP DIST AZ ID MAP FMLIST
2024-09-05 17:53:41 106.400 826E EBSRadio EBS Radio Vârful Postavarul ROU V 0.3 11 194 6600099 FMDX FMLIST
2024-09-05 17:54:22 106.400 826E EBSRadio EBS Radio Vârful Postavarul ROU V 0.3 11 194 6600099 FMDX FMLIST
2024-09-05 17:55:01 106.400 826E EBSRadio EBS Radio Vârful Postavarul ROU V 0.3 11 194 6600099 FMDX FMLIST
2024-09-05 17:55:40 106.400 826E EBSRadio EBS Radio Vârful Postavarul ROU V 0.3 11 194 6600099 FMDX FMLIST
2024-09-05 17:56:03 106.400 826E EBSRadio EBS Radio Vârful Postavarul ROU V 0.3 11 194 6600099 FMDX FMLIST
2024-09-05 17:56:25 106.400 826E EBSRadio EBS Radio Vârful Postavarul ROU V 0.3 11 194 6600099 FMDX FMLIST

[dire magnet]

ok I'm still updating the time, but otherwise ok?

[elfin kettle]

I will try in a moment with a low signal station to see how it goes

I have to change the antenna that is connected

[elfin kettle]

all good except for the time which is stuck

[dire magnet]

ok, I corrected the time. You are welcome to test!

[elfin kettle]

thank you so much 🙂

let's see

[dire magnet]

I think now we have it. I will format the code again and revise the comments, then the 1.6 can be released,

[elfin kettle]

yes, now we have it 🙂

all good 🙂

[dire magnet]

I'm glad! At this point, thank you again for your cooperation!

[elfin kettle]

thank you for the patience and fixing the bugs 🙂

[dire magnet]

The new RDS logger version 1.6 is now available for download:
https://github.com/Highpoint2000/webserver-logger/releases/tag/1.6
All features and changes can be found in the attached description! I recommend every user to update to this version.

[elfin kettle]

@dire magnet I have an improvment suggestion for the Logger. The FMDX button does the same job as the click on the PI code from the webserver UI. What about changing the functionality of this button to become a MAP ALL like in the html report so it has a functionality of it's own that is missing in the UI?

[dire magnet]

Good morning! They are awake early. 😉 Yes, that could work. I'll release the 1.7 soon anyway. I can build the feature into it right away. Thank you very much!

[elfin kettle]

It wasn't my choice to get up so early 😦

but I used the time for other things too

[dire magnet]

I'm also usually awake early. We call this "old age senile bed escape" 🤣

[elfin kettle]

what old age? I do not think you are old... unless I am wrong 😛

[dire magnet]

Unfortunately, I have already exceeded the half-life of 100. 😩

[elfin kettle]

ha! I always though you are much yunger than me (I was confused by the number in your email :))) )

i still have 3years till half of 100

[dire magnet]

Haha, in that year I created the email address.

[dire magnet]

We're not that far apart.

[elfin kettle]

apparently yes 🙂

[dire magnet]

Good morning, you are welcome to test your new feature. I uploaded the beta version of the logger to Github. 🙂

[elfin kettle]

Good morning, I will try 🙂

[elfin kettle]

well... something is wrong and the plugin doesn't get loaded

@dire magnet have you done other changes?

I have rolback to the old version

very, very strange... I also took the script from your server where is working but for me is not 🤨

funny thing... on your manual server the scanner is not responding to comands

[dire magnet]

Yes, it's certainly due to the missing config file or path on Linux. I'll have to expand the code for this later, sorry! But thanks for testing!

[elfin kettle]

no problem 🙂

glad to help

[dire magnet]

But that's right, they can test the feature on my servers. The beta is running there

Thanks to the new config files, I can apply any change to all servers at the touch of a button. This makes it much easier.

[elfin kettle]

any idea what is wrong with the Scanner on your server? hope is not a conflict with the changes to the other plugin's

the <<>> buttons do nothing there

also I think the way the MapALL button is enabled needs to be changed... now it gets disabled if no RDS is on the current station

with MapALL is should stay enabled if there is at least one station in the list and ramain enabled till the list is cleared (refresh of the page)

and maybe a safety feature... the MapALL to be enabled only in Filtered mode... with RAW will generate too many requests to the maps.fmdx.org

it just got complicated 😦

if it is too complicated then you can leave it as it was on the previous version

[dire magnet]

Hello, you can now test again. I have adjusted the BETA again so that it should now work without a config file. The MAPALL button also lights up as soon as a station has been identified. By the way, the requests in the RAW log are no more than in the filter, exactly one at the moment when you click on the button 😉

[elfin kettle]

Hello, I will have a look

[dire magnet]

That was just a config issue. The headless TEF expects false instead of true in the PE5PVB modes.
😉

[elfin kettle]

regarding RAW I hope you are right and there are not 1000 requests when the PS is dynamic

[dire magnet]

I don't make any requests to the database at all. That's what the web server does now. In the past, everything was done via the proxy ...

I agree with them, now Noobish would be the cause of a database nockout

[elfin kettle]

ok 🙂

the MAP ALL works fine

but a small, small issue appared

[dire magnet]

Which one

[elfin kettle]

1. Enable blacklist
2. Go on a station with a frequecny that is in the blacklist
3. Press refresh in the browser
   Result: The local station that is in the black list appears in the Logger

[dire magnet]

Was that with the old version too?

I actually only changed the button functionality, so I'm surprised by this behavior

I have just tested myself. But it only occurs sometimes. Refresh several times - sometimes the entry is displayed, sometimes not 🤔

This seems to be a loading or timing problem. We will still get that solved.

[elfin kettle]

indeed on the previous versions it used to do this from time to time but now it has become always

not sure why

also in the previous versions it used to go away after a new refresh (so not really a problem) but not it sticks and the user cannot get rid of that entry

[elfin kettle]

I have checked this and apparently there is no flood of requests. Apparently even if there are 50 entries of the same station in the Logger is added only once in the map request. This is really good 🙂

[dire magnet]

Please test the updated BETA again now. I can no longer delete entries that are already in the list. Therefore, the blacklist button must always be pressed before starting logging!

[elfin kettle]

ok, I will have a look

[dire magnet]

There were several parts in the code duplicated but not identical. Understandably, the script couldn't cope with that. That's why the entry was sometimes there and sometimes not there, at least that's how it was for me.

[elfin kettle]

🙂

[elfin kettle]

well if there is a start frequency that is in the blacklist then that is always in the list

the only way to get rid of that is to move to a frequency with no signal and then refresh the page

I do not see any change in this last version

[dire magnet]

Please test my dev server:
http://highpoint2000.selfhost.de:4080/
there I have the frequency 106.9 MHz in the blacklist. Is the behavior the same?

[elfin kettle]

@dire magnet there is no Logger there 🙂

[dire magnet]

He?

[elfin kettle]

now it has appeared

I will check

[dire magnet]

A new bug?

[elfin kettle]

and now is gone

as soon as I refresh the page the logger is gone... completely

[dire magnet]

A ghost? 😜

[elfin kettle]

kind off 😂

I will make a recording in a sec

only once I have seen the logger and as soon as I used Refresh it was gone

[dire magnet]

@elfin kettle Please try again now:
http://highpoint2000.selfhost.de:4080/

[elfin kettle]

@dire magnet well... now the plug in appears but the station in the black list is still added to the Logger after page refresh

and there is one more... the Scanner button sometime appears sometimes it is not 😦

[dire magnet]

the 106.9 MHz?

[elfin kettle]

yes

if I use < or > is not added to the list

as soon as I refresh the list is always added

[dire magnet]

Please try now, feel free to delete
the cache beforehand

[elfin kettle]

ok, I will try agian

[dire magnet]

That's really crazy, it works for me here without any problems

[elfin kettle]

for me it is not on your server 😦

I think that in your code somehow the filter is applied too late in some cases

I have checked on Edge (windows) and Chromium (on Linux)

[dire magnet]

Please test again now, I have set the timing a little higher.

[elfin kettle]

ok

[dire magnet]

Is it possible now?

[elfin kettle]

first time it worked fine... then 4 times it hasn't

[dire magnet]

I've loaded the code on github. Test it locally. I'm going to eat first.

[elfin kettle]

guten Appetit 🙂

I have added the plug in on my server and if I access it from windows it works fine. From Raspberry PI the station is always in the list. I would assume that this happens because the RaspberryPI is slower.

it takes time till the filter is applied as result is listed

[dire magnet]

Please set this value higher to 500 or 750 ms. It delays the call of the frequency after the filter has been initialized.

[elfin kettle]

in order to work an all I had to add 1000

however from 500 I have jumped to 1000

I will try with 750 in a few minutes

[paper tinsel]

wouldn't it be better to use a mutation observer or promise for this? setTimeout is unreliable

[dire magnet]

Ok, thanks for tip! Maybe that's exactly why?

[elfin kettle]

just in case it still matters with 750 is not working well... so 1000 is the good value

[dire magnet]

Please test the current GITHUB beta version, if it all works now!? Thank you!

[elfin kettle]

on windows is 100% correct... on Raspberry PI with Linux is so, so... sometimes is ok, sometimes not

I would say that we can leave it as it is

[dire magnet]

I have just released the logger version 1.6a (small update):
https://github.com/Highpoint2000/webserver-logger/releases/tag/1.6a
The most important new feature is the change of the FMDX button in MAPALL. This now shows the connections in the map for all log entries.

[dire magnet]

I found some time today to deal with her requirement. I think I have found the ideal solution. Just watch the video 😉

[elfin kettle]

looks nice 🙂

no need of a separate plug in 🙂

and considering that you worked with my server I would assume it already works 😉

[dire magnet]

Yes, it is a programmed Chrome extension (JS+JSON). I will also write one for Firefox and then publish it. With the FMDX MAP, you can then control any web server that is not blocked. Super awesome!! 😎

[elfin kettle]

yes, it is 🙂

[dire magnet]

It would have been far too time-consuming and cumbersome to first build a query with representation via the database, when there is already a solution for it.

[elfin kettle]

true 🙂

[cobalt spruce]

Excellent! This is an idea that I've had for a long time already but I haven't had knowledge how to modify maps.fmdx.pl to get tuning working like this!

[dire magnet]

This certainly works for other databases, such as FMLIST etc. You would have to take a look at that.

[dire magnet]

maps.fmdx.pl didn't modify it either. I just read out the selected frequency and send it to the websocket of the web server. Actually a simple principle. The most difficult thing was to read the dynamic websocket from the browser, so that you can control any web server.

[cobalt spruce]

This will move SpE FMDXing to a whole new level!

[dire magnet]

Cheers to @elfin kettle for his idea! 🥂

[dire magnet]

It's just a pity that the SpE season is over.

[cobalt spruce]

You mean reading the dynamic data from the websocket - I've done that already but I do not know how to read the selected frequency info from a web page. I haven't done browser extensions. Tried to search for a solution a couple of times but this is completely different world I know nothing about.

[elfin kettle]

it isn't... today there was ES in western EU.... nothing for me in RO though

I have checked your servers and there was no ES for you either

just have a look over the

quite a big one

[dire magnet]

It's a pity, but I haven't had much luck the last few times either.

Because it's going so well right now - I'm putting a database on top of it with fmscan.org with which you can control the web server 🙂 In principle, you can set a SpE position there, display the frequencies and then click through individually to see if you receive something.

I haven't gotten FMLIST to work yet, but maybe it's not necessary 🤔

[elfin kettle]

you do not need two browser windows... there is an option to split the screen in browser between two tabs

[dire magnet]

Yes, of course that is also possible.

[dire magnet]

So it is of course ideal !

I'll make sure that I finish the browser plugin tonight. Then they can play
with it from tomorrow morning 🤗

Are there any other databases that I should connect?

[cobalt spruce]

Is it possible to use with db.wtfda.org ?

[elfin kettle]

sorry I have shown you the wrong setting

is actually Split screen followd by link tabs.... so the PI code always opens in the window to the right

[dire magnet]

I'll take a look!

[dire magnet]

Unfortunately, you can't click on anything or is there still a subpage?

[cobalt spruce]

I think there's no subpages. It's just a database giving a list based on search criteria.

[dire magnet]

And the logger
https://wlogger.app/accounts/login/?next=/
?

[cobalt spruce]

So howabout https://www.fcc.gov/media/radio/fm-query and choosing list as a form of output?

[dire magnet]

I have to see, I haven't found a direct frequency link either. But maybe I can manipulate the pages in such a way that all detected frequencies are made easily clickable. This would then work for any kind of table or database. 😉

[cobalt spruce]

Wlogger is for DXers logs. The UI was renewed just recently. There's a "Quick Find and Log" search area for easy finding the station to be logged. I think it uses db.wtfda.org data like the RadioLand app.

[cobalt spruce]

If such page manipulation is possible then it would work for almost any station listing.

[paper tinsel]

Is there a specific reason? We also have FMLIST data for USA now 👀

[cobalt spruce]

A spesific reason for what? What do you mean?

[paper tinsel]

Well, WTFDA is for the US database of FM stations

I thought Logger works without any issues for USA stations already with the FMLIST dataset

[cobalt spruce]

WTFDA is a DX club, the Worldwide TV-FM DX Association. The WTFDA FM station database has always been with it's own data to my knowledge. WTFDA DB and FMLIST has been "competing" sources. DXers in North America have always found FMLIST difficult to use. That's the impression I've got. I have never heard that FMLIST was used for WTFDA's logger.

[paper tinsel]

Ah, right, so you want to make the logger be able to work with the WTFDA's logger?

[cobalt spruce]

No, WTFDA logger is a different thing. Also what we call with the name "logger" is meaning a bit different thing forthe WTFDA logger and FMDX Webserver's RDS-Logger plugin. What I answered here, is that I answered what other databases there might be for which it would be good to have compability with the new expanded direct-tuning principle.

[dire magnet]

@cobalt spruce @elfin kettle I managed to do it. All frequencies found are now provided with a link. the whole thing also works with log list from the scanner as well as
https://db.wtfda.org/
and of course with any website (example WDR)

Now I just have to merge the scripts, clean them up and then I can publish them.

[cobalt spruce]

This is amazing!

[dire magnet]

A huge step forward, I would say!

Of course, it also marks other numbers that are indicated with x.xx or x,xx. But I don't think that's so bad.

[dire magnet]

The Chrome version is ready: #1284674859020058727

[vast dock]

@dire magnet Causing all browsers to show "Translate from German"

[elfin kettle]

that file belongs to the Scanner, not Logger 🙂

[vast dock]

ah I am getting confused again !!! 😕

[elfin kettle]

probably Highpoint will reply here anyway 🙂

[dire magnet]

@vast dock Hello Ryan, you can access the logging file of the scanner via the logger, that's what NuMerci meant. Thanks for the hint!

[dire magnet]

@vast dock I have included the correction of the HTML tag in the current Logger version 1.6a and the Scanner version 2.6b.

[oblique coral]

if anyone finds scrolling up to be buggy, i replaced this code with this:

dataCanvas.scrollTop = dataCanvas.scrollHeight - dataCanvas.clientHeight;

const { scrollTop, scrollHeight, clientHeight } = dataCanvas;
userIsAtBottom = scrollTop + clientHeight >= scrollHeight - 20; // Adjusted threshold
if (userIsAtBottom) dataCanvas.scrollTop = dataCanvas.scrollHeight - dataCanvas.clientHeight;

[dire magnet]

Thanks for the code suggestion! The scrolling behavior has really improved as a result 🙂 I immediately implemented the code in version 1.6b:
https://github.com/Highpoint2000/webserver-logger/releases/tag/1.6b

[elfin kettle]

in the next release would it be possible to replace the message that pops up when the scanner log is not available with a toast message? The current one stops the audio while is diplayed

[void agate]

How to set blacklist?

[dire magnet]

You must be create a file /web/logger/blacklist.txt . For example, the frequencies that should not be logged must be: 89,800 89,400 100.80 ... They can be written next to or below each other with spaces. 😉

Then activate the function via the blacklist button.

[void agate]

Thanks. I just have web/logs folder , it’s ok? But i can’t activate « blacklist » button.

Ah, must create directory too! Button « blacklist » is ok now… but frequency blacklisted are not blacklisted by rds-logger 🤔

[dire magnet]

Have you entered the frequencies that are not to be logged? For example, I entered the frequency 106.900. When I call the FRequenz I don't get a log entry (see screenshot!) The logger blacklist has nothing to do with the scanner. This requires its own blacklist to skip frequencies. It is also logical that there are two plugins that can be used independently of one.

[elfin kettle]

@dire magnet and @oblique coral there seem to be a conflict between the Logger and the Spectral Scan plug in

I think one of you, or both should do changes....

the plug in's fight on the same spot on the screen

update: it seem that the problem actually appears only when the Spectral Scan is already open and the user tries to open the Logger. The other way arround it works well.

[oblique coral]

Yep that issue i am aware of. latest beta, when i upload it, will now not open the graph if the signal graph has been hidden (by another plugin)

if @dire magnet wants to also include the line of code:

function toggleLogger() {
    if (!document.querySelector("#signal-canvas")?.offsetParent && !isLoggerOn) return;

[dire magnet]

Thanks for the line of code. I have implemented it in the new version:
https://github.com/Highpoint2000/webserver-logger/releases/tag/1.6c
In addition, the logger plugin now also performs a daily update check.

[elfin kettle]

@dire magnet thanks for the new version. It is fixing the conflict with the Spectral Scan

but

why there is a config json if is ignored?

the config I still need to add in the main script otherwise is not read

[dire magnet]

Why is it ignored? The script header only contains the values if no json file is found. However, it is quite possible that Linux does not access to the json file again and you therefore have to enter the values in the script header.

[elfin kettle]

yes, till I have not added the values in the script itself it has not picked them up

no matter if these where in the json file

strange that for Scanner and DX-Alert it works but not for Logger

[dire magnet]

There, the associated server services access the JSON files. They have complete access to the local file system (node js module). The logger plugin only accesses the JSON file as a browser plugin via a web path - that's the problem!

[elfin kettle]

ah, you are right 🙂

[dire magnet]

Shortly before Christmas, a small update. In the latest version 1.6d, the error verification of the PS display has now been optimized. As a result, fewer question marks are now visible:
https://github.com/Highpoint2000/webserver-logger/releases/tag/1.6d

[dire magnet]

https://tenor.com/view/merry-xmas-christmas-gif-8504960197267383668

[elfin kettle]

Hello @dire magnet

Merry Christmas

the new Logger doesn't read the config on Linux at least

the config is in the same folder but is not being picked up

has the folder changed?

[dire magnet]

No, no change! I only changed the PS exam. Strange!

[elfin kettle]

I have reverted to the old version from 4.12.2024 and it works fine

this new version is not reading the config no matter what I do...

[oblique coral]

This is a very rushed update to get it working with 1.3.5. Highpoint obviously a few plugins to get through, and i wanted to test this one, so here's an unofficial update

https://github.com/AmateurAudioDude/webserver-logger

[spring rose]

Thanks for this, working well for me. I should try to figure out MutationObserver for audio recorder as well

[oblique coral]

yes it's the best method

[dire magnet]

Thank you! This helps me to update the plugins faster. 🙂

[paper tinsel]

when you have time ofc

it's cut off

[dire magnet]

I have already corrected that. It comes with the official update of the logger plugin.

[paper tinsel]

perfect

[dire magnet]

Here is the adapted version for the web server 1.3.5:

https://github.com/highpoint2000/webserver-logger/releases/tag/1.7
Thanks for the helpful preparatory work!

[elfin kettle]

@rancid trellis let's continue here

I have read your request and from what I know if you disable the filter should log every entry no matter is is identified or not

have you tried like this?

regarding the csv splitting and saving to the log folder that would be hard to do as the Logger doesn't have a server component like the scanner

not impossible but more complicated to implement

as a note Highpoint is on vacation so it will take a bit of time till he will reply

[rancid trellis]

Yes I've tried that but the unfiltered file shows is up to seven lines of entry for each frequency - it looks like the logger plugin reads the frequency multiple times and logs it each time. The filter option appears to just log the final entry.
The unfiltered scanner html attached shows what I mean

[elfin kettle]

yes, it logs every little change of the RDS data and this is why there are several entries

[rancid trellis]

If it can't be done in RDS logger maybe it could be done in the scanner plug-in, separate to the csv file that is linked with the URDS plugin.
I'd be happy to see the filtered Scanner HTML file showing the functionality

[elfin kettle]

well, there have been so many discussions how it should work... everyone has a different request how it should work 🙂

we will see what Highpoint can do when he is back

[rancid trellis]

Here is a pdf file created from the RDS logger HTML file by printing to pdf.
As you say there are many different ways of doing it.
I look forward to seeing what happens - I'm happy to help testing.

[elfin kettle]

@dire magnet I have noticed on your mobile server a problem for the RDS logger... the horizontal scrollbar appears under to buttons and it cannot be used

[dire magnet]

Thanks for the important information. The new version runs there with more lines. There still seem to be problems. I'll fix it before the release.
🙂

[autumn finch]

I have still this error

[elfin kettle]

you are probably running an older version of the plugin on the 1.3.6

try the latest version of the plugin

[paper tinsel]

have you considered utilizing the popup windows for this possibly?

[dire magnet]

Good morning! Not yet, because I don't currently see the added value and don't know how complicated the conversion will be.

[paper tinsel]

It shouldn't be too complicated, the value would be extra vertical space for sure

[pulsar oak]

Massive E opening here, so I used RDS Logger along with the Scanner plugin, I've noticed that when the scanner plugin gets the spectrum update the server briefly disconnects then reconnects, after this the RDS logger no longer logs any data.

[elfin kettle]

are you on wifi?

I mean the webserver connection to the network is by wifi?

[pulsar oak]

Yeah I'm on wifi

[elfin kettle]

I also have disconnect issues from time to time on the webserver that is connected by wifi and on autoscan

on the one that is connected by cable it never happens

[hollow galleon]

Where i go wrong, my logger publish nothing to FMLIST. org My ID is filled in the config

[pulsar oak]

Yeah this is a disconnect just for a split second when the spectrum graph updates. It happens every time the frequency goes back to the start (in my case 87.3)

[dire magnet]

The logger doesn't publish anything automatically. Only the scanner plugin can do that. You have to press the FMDX button (when it's highlighted) for each log to publish the log. This function is now obsolete, as the web server can publish logs manually directly.

[hollow galleon]

Scanner is the next step, i have installed but is also not uploading anything to fmlist