Topic: FOSHKplugin - brief introduction

[Gyvate]

Hi!

The given URL is unreachable or not correct.
A 404 error normally indicates that the requested resource is not available or accessible.

What happens if you enter http://192.168.12.140/public/ecowitt0.cgi in your web browser? Error message: not found?

Oliver

this will provide a "FAILED" 404 message even though MB can receive and process data

[Gyvate]

@KC5JIM
can you try to connect your console directly to Meteobridge - just for a short while and see if the live data arrive !?
hostname/IP: 192.168.12.140
path: /public/ecowitt0.cgi
port: 80
interval: 8

I tried with a new station and the Ecowitt Custom Upload driver - and it worked well - the only difference is that the format chosen was RAWEW and not EW (but this shouldn't make a difference)
we may have a firewall issue here

there may still be a MB issue
leave what you have as primary station and add another station, station #1 with the same driver (Ecowitt Custom Upload) and have FOSHKplugin post its data to  http://192.168.12.140/public/ecowitt1.cgi, format RAWEW and see what it gives

[KC5JIM]

Not Found
The requested URL /public/ecowitt0.cgi was not found on this server.

[KC5JIM]

@KC5JIM
can you try to connect your console directly to Meteobridge - just for a short while and see if the live data arrive !?
hostname/IP: 192.168.12.140
path: /public/ecowitt0.cgi
port: 80
interval: 8

I tried with a new station and the Ecowitt Custom Upload driver - and it worked well - the only difference is that the format chosen was RAWEW and not EW (but this shouldn't make a difference)
we may have a firewall issue here

there may still be a MB issue
leave what you have as primary station and add another station, station #1 with the same driver (Ecowitt Custom Upload) and have FOSHKplugin post its data to  http://192.168.12.140/public/ecowitt1.cgi, format RAWEW and see what it gives

Connecting console directly to Meteobridge still does not provide data.
Creating station 1 using RAWEW from FOSHKplugin also does not provide data.

So, I looked in the /public directory of Meteobridge, and there are no ecowitt0 or ecowitt1 files, which explains the problem.

[Gyvate]

@KC5JIM
can you try to connect your console directly to Meteobridge - just for a short while and see if the live data arrive !?
hostname/IP: 192.168.12.140
path: /public/ecowitt0.cgi
port: 80
interval: 8

I tried with a new station and the Ecowitt Custom Upload driver - and it worked well - the only difference is that the format chosen was RAWEW and not EW (but this shouldn't make a difference)
we may have a firewall issue here

there may still be a MB issue
leave what you have as primary station and add another station, station #1 with the same driver (Ecowitt Custom Upload) and have FOSHKplugin post its data to  http://192.168.12.140/public/ecowitt1.cgi, format RAWEW and see what it gives

Connecting console directly to Meteobridge still does not provide data.
Creating station 1 using RAWEW from FOSHKplugin also does not provide data.

what Meteobridge do you have ? Model
what software version are you on ?
do you have an Ecowitt console with local API (GW1x00, GW2000 etc.) ?
if so, can you retrieve data with the MB GW1000 driver ?
what's the MB connection ? WLAN or LAN
IP address static ?

[Gyvate]

I see from the MB forum that you are running a MB VM and claim that there is no ecowitt0.cgi in your installation ...
did you connect via SSH to your VM and check the /www/public folder ?
If it is really missing, try to re-install the VM.
Before you do this, go back to an earlier version (System --> Administration), have the old version installed, check if it works now ...
VMs can be pretty tricky in the network context ... what VM do you have ? what's your network type chosen for the VM ?
Where do you run the VM ? Is the IP address the VM address or the server address ?
Blaming MB might not be the right thing to do - my MB VM runs properly !

[Gyvate]

there was potentially a bug though as today, 29-May-2025, a bug fix was leased:
Meteobridge PRO2, VM: fixes a bug that prevents from Ecowitt custom upload option being used successfully
does upgrading to the last software build fix your issue ?

[KC5JIM]

there was potentially a bug though as today, 29-May-2025, a bug fix was leased:
Meteobridge PRO2, VM: fixes a bug that prevents from Ecowitt custom upload option being used successfully
does upgrading to the last software build fix your issue ?

Yes, the update resolved the issue.

[KC5JIM]

Trying to forward to Awekas, but the data is not populating at Awekas.

Forward:

[Forward-8]
FWD_CMT = Forward in Awekas API format
FWD_TYPE = AWEKAS
FWD_URL = http://data.awekas.at/entry-exam.php?
FWD_SID = ??????
FWD_PWD = xxxxxxxx
FWD_INTERVAL = 60
FWD_ENABLE = True

fwdstat:

FWD-08   AWEKAS   http://data.awekas.at/entry-exam.php?   06.24.2025 16:20:44      404, queued   4 (10)

Questions:
1) Is the Awekas SID my Awekas user ID, my Awekas station ID, or my Awekas API key? I am currently using my Awekas user ID.

2) What have I broken, and how can I fix it?


Thank you!

[olicat]

Hi!

FWD-08   AWEKAS   http://data.awekas.at/entry-exam.php?   06.24.2025 16:20:44      404, queued   4 (10)

The URL is wrong - that's why the 404 error.
Please use http://data.awekas.at/eingabe_pruefung.php? as FWD_URL. This looks like a problem with a translation - the examples on the FOSHKplugin support page are correct.

1) Is the Awekas SID my Awekas user ID, my Awekas station ID, or my Awekas API key? I am currently using my Awekas user ID.

FWD_SID should be your Awekas username (not station number). I have now concretised this on the FOSHKplugin page (Awekas-username not the ID). Thanks for the hint.

2) What have I broken, and how can I fix it?

Adjust the FWD_URL and use your Awekas username instead of your Awekas ID in FWD_SID. Then it should work.

BTW:
You could send the saved data to Awekas afterwards. All you have to do is open the CSV created by FOSHKplugin with Excel, save the file as XLSX and then import it into Awekas.
See also here.

In your case you should find the queue file for Forward 8 as FOSHKplugin-queued-data-8.csv in directory /opt/FOSHKplugin/FOSHKplugin-queue/FWD-08/.

Oliver

[KC5JIM]

Thank you, that fixed everything.