I've sent Wim a note about the issue
Thanks to both of you, working on it.
But is seems a strange problem to me, so i commented the two stations for today and will test what is happening tomorrow my time,
Wim
As i vaguely remember somewhere in 201? I could have added a "use last valid data if station data is not available"-feature.
The latest BNLWN-conditions.txt is read and the latest value of every station is saved before loading the fresh stations data.
I probably thought: if the station does not answer in the allowed 4 seconds, better use the previous data then no data at all.
The forced move from old to new provider introduced garbage in some files in almost all of my websites.
Mostly because of cron-jobs failing or running concurrently and DNS pointing to old sites.
Sadly also in the BNLWN-conditions.txt some garbage texts were introduced.
That garbage was handled by the scripts as real data for some (non-existing) stations.
As there can be no new data for none-existing stations, the garbage was copied to the new BNLWN-conditions.txt file as "old' data for those non-existing stations..
Setting the stations around the garbage as inactive did not help as the garbage only seemed to belong to those real-stations data.
But every line in the BNLWN-conditions.txt is a new station. Also a garbage line.
I removed the garbage lines and all is functioning OK for now.
GIGO
I forget the first lesson in programming "Garbage In results in Garbage Out"
Wim