meteohub.de

Yes, I can build from scratch. Thanks for the suggestion.

I was running a VM on a different machine and needed to change machines because WSV3 would not run with virtualization enabled.

When I try to start the VM, it hangs with the following errors:

Virtual Box: Version 7.2.0_BETA1 r169020 (Qt6.8.0 on windows)
Windows: Windows 11 Pro Insider Preview ...

admin wrote: Sat May 31, 2025 11:54 am Thanks for providing details. Inspecting the code shows that support for air quality was missing in GW3000 driver. Please give just released update a try.

Sorry, that still is not populating air quality in the Meteotemplate API. It is populated in the Live Data display.

I'm using the GW3000.
I'm including a few screenshots to hopefully help.
The last one shows what the FOSHKplugin sends to the Meteotemplate API.

Hi,

I have the PM2.5 sensor in my Ecowitt system. When I feed Meteotemplate from the FOSHKplugin, I can see the PM2.5 data, but using MB, the data is not there. It's not in live data, nor on my website.

Any suggestions?

Please try with just released update. I saw that there is a bug on PRO2 and VM.

However, using custom uploads is an edge case (at least that is my excuse). When you have one one of the GWxxxx devices, please, please load data from there. It is much better. Custom uploads is just meant for users ...

Updating now.

And I understand why to use the GW3000 upload.

Sorry for my confused rantings.

I just looked in /public, not www/public—my mistake.

Either way, pointing to 192.168.12.140:80/public/ecowitt0.cgi returns a 404 error.
I created a second station that points to 192.168.12.140:80/public/ecowitt1.cgi and also returns a 404 error.

I'm running Meteobridge VM and having problems feeding it with Ecowitt Custom Upload. These are my settings, as provided by Meteobridge, using the Ecowitt protocol type:

Ecowitt Custom Upload
IP/Server: 192.168.12.140
Connection: Path:/public/ecowitt0.cgi
Port: 80

No data is uploaded to ...

I have FOSHK feeding one website, MB feeding another, and Ecowitt feeding Ecowitt.net. All of this comes from one GW1000, so the data is the same.

FOSHK rain fall = .48", Ecowitt rain fall = .48", MB rain fall = 0.00"

The rain rate is 2.91"/hr (seriously!) MB does show that correctly, but it still ...

Meteotemplate dev does NOT need to tell Boris anything, Boris only needs to use the CORRECT FIELD NAMES AS DOCUMENTED in the ECOWITT API.

The API is from ECOWITT, it's documented. Boris has been ARGUING because HE cannot comprehend the CLEARLY WRITTEN documentation of the Ecowitt API. Even when ...

FOSHKplugin never actually used the Ecowitt HTTP gateway plugin. I posted about how I could feed the plugin with FOSHK, but it now uses the API and I've deleted the plugin.

I am quite aware that the data is in MB, as my post said MB is not "sending the data to Meteotemplate". Meteotemplate is NOT the issue as shown in the attached screenshot. That lightning data is being reported to Meteotemplate by the FREE FOSHKplugin using the Ecowitt API.

You would think that a ...

718 lightning strikes in the last 90 minutes and MB Pi is reporting 0 to Meteotemplate. Mapping is correct in MB. I really do not understand why MB thinks that lightning is nothing important and refuses to fix this. FFS, the iz0qwm / ecowitt_http_gateway that is TWO YEARS OLD can report lightning ...

What is the "Upload Interval:" for WU set to on the NANO SD?