Topic: (meteobridge) posting to Meteotemplate: port 443: Connection timed out" SOLVED

[alexvanuxem]

hi,

on my meteotemplate site, data loaded via meteobridge and the mt network plugin: I added a ecowitt gw1100 lihtning detector.
Trying to custom upload the data.

Had to write a .htaccess file to redirect from https to http.
Data seems to go through, but in the cache/ecowittlog.txt file it says : port 443: Connection timed out
when trying to access the api file.

What does this mean and how to resolve it?

Many thanks

[Rover1822]

If going to 443 on ecowitt.net , if that is what you are doing, I don't believe that will work. Needs to be 80.
As you appear to be familiar with Apache , you can proxy it and change the port to 80, if it is coming in HTTPS and you are going to HTTP.

[Gyvate]

hi,

on my meteotemplate site, data loaded via meteobridge and the mt network plugin: I added a ecowitt gw1100 lihtning detector.
Trying to custom upload the data.

Had to write a .htaccess file to redirect from https to http.
Data seems to go through, but in the cache/ecowittlog.txt file it says : port 443: Connection timed out
when trying to access the api file.

What does this mean and how to resolve it?

Many thanks

I think your answer lies in the post
https://www.wxforum.net/index.php?topic=40447.0
where you already asked similar questions regarding your air quality sensors
and specifically for the lightning sensor
you have already posted the same/similar question in the Meteobridge forum - there is also a respective post - needs some digging

there are two ways to go - via http-ecowitt gateway or standard Meteotemplate API - both work (I use MB via MT API only)
but you have to choose the proper variables which you send with the Meteotemplate markers: e.g. L=[lgtx!0total-dmax.0:], LD=lgtx!0dist-lastval.1:], LT=[lgtx!0total-nonzerotime=EPOCH]
 (x: your station number in Meteobridge. ) remember: variable: sensor-selector=conversion.decimal:replacement (see Meteobridge WiKi - section templates)

For "L" (number of strikes per day, increasing like rain) a database column already exists, for LD (distance) and LT (last lightning time stamp) columns might need to be created in the database.
But even without a database field existing, the markers will arrive in the API and will be available there - only not archived.


not sure what you mean by "MT network plugin" ...
normally MB posts to MT are http posts (no https) - of course if your server in the web doesn't accept http posts, you'll have to sort this out with your hosting provider

[Gyvate]

your http request in Meteobridge for the Meteobridge API string should be:
http://your-domain/your-path-from-www-root/template/api.php?U=[epoch.1:]&....&L=[lgt0!0total-dmax.0:]&LD=[lgt0!0dist-lastval.0:]&LT=[lgt0!0total-nonzerotime=epoch:]&PP1=[air0!0pm-lastval.2:]&PP2=[air0!1pm-lastval.2:]&PP3=[air0!4pm-lastval.2:]&PP4=[air0!5-lastval.2:]&....&PASS=your-password
the numbers in front of the "!" will depend on the station number your sensors belong to. Primary station=0, Station 1 = 1 etc.
The above example is for station 0 (primary).
The ... are for additional sensors you may have or may not have - make sure there is only one "&" between a "]" and the next marker (e.g. "L")

[Rover1822]

I defer to Gyvate, I just saw you making changes to .htaccess , a Apache webserver specific file . (I work a lot with various webservers, so a light went off, when I saw the 443 error)

I really don't know anything else as far as Meteobridge.

So in essence, go with whatever Gyvate suggests.

-Rover

[Gyvate]

one (or two) more thing(s):
if selector "lastval" doesn't work, try "avg"
I suggest you first create an export event in Meteobridge with the API string and check if the results are what you expected - once they fit, create the http post

[alexvanuxem]

sorry for the confusion.

I use meteobridge, In the tab 'networks' , I selected the 'plugin' Metetemplate, where I only need to enter the website name and my update pasword. No http request, this is the easy way, cron job included.

For the lightning sensor of ecowitt: there's a ecowitt plugin that allows custom upload, even if you use my way.

if I pass https://www.sint-katelijne-waver-meteo.be/template/api.php?U=1654861129&PASS=MYPASSWORD&P=1023.79&TIN=25.28&HIN=50&L=0&LD=&LT=&LBAT=3&Station=GW1100A&FW=V2.0.2

it gets through without a problem, and the api is updated with the lightning,

but for a reason I dont  know, and yes im asking different people, just to  get an answer, the ecowittlog gives a 443 error.

 [ You are not allowed to view attachments ]

so ecowitt plugin in meteotemplate gets the data from my gw1100, and wants to update the api.php file.
and there's something wrong, I guess with at my providers end? I also asked them for an explanation.

ps: i tried also to add the gw1100 as an extra station inside meteobridge, but no lightning data gets through. I have seen posts here that explain way, its a meteobridge issue, from what I have read.

thx for helping.

[Gyvate]

you can do it the easy way = the way it works  - see my API string as http request

or you can do it your way

dealing with the incomplete posting of the standard MB posting to MT - and the ecowitt-http-plugin
and potential issues

@davidefa is an experienced user for the ecowitt-http plugin, the lightning plugin etc. with Meteotemplate
if he doesn't react by himself on this post after some time - ping him with a PM

it also depends on what you want to do with the lightning data ...

ps: i tried also to add the gw1100 as an extra station inside meteobridge, but no lightning data gets through. I have seen posts here that explain way, its a meteobridge issue, from what I have read.

you need to know what you (want to) do and what Meteobridge standard does - it only sends the data from the primary station.
If you add the GW1x00 as station1, 2 ... the standard won't send its data - that's why you need a custom string and a custom http request with the sensors of your GW1x00 station in it, e.g. lgt1!0total if you added your GW1100 as station 1 - if it's station 2, the sensor is lgt2!0total (for the # of lightnings) the whole variable will be, as mentioned before, [lgtx!0total-dmax.0:] x= station number
You can also have the GW1x00 post via its custom server function (and use ecowitt-http-plugin), which is at the end of the also just another http request posted by the console custom server functionality instead of having MB do the post

if I pass https://www.sint-katelijne-waver-meteo.be/template/api.php?U=1654861129&PASS=MYPASSWORD&P=1023.79&TIN=25.28&HIN=50&L=0&LD=&LT=&LBAT=3&Station=GW1100A&FW=V2.0.2
it gets through without a problem, and the api is updated with the lightning,

of course, sending this string will transfer L=0 and you will find a "0" for your time stamp in the MT API. The question is how to make MB create this value behind "L=" - and post it.
The answer is: L=[lgtx!0total-dmax.0:]  where x= station number

Maybe you care to amend your original posting subject like " (meteobridge) posting to Meteotemplate: port 443: Connection timed out" for better understanding of the other forum users paging through the list of threads
(you have to do this in the very first post)

[alexvanuxem]

thank you for reply.

Learned a lot from your last answer.

Got a reply from Davidefa: 'Please try this updated plugin ( it simply replaces the call to api.php via 'curl library', that fails with a timeout on your server, with a 'require', that should work in your case )'.

And it works.Many thanks to Davidefa.

Learning day by day,

Thank you for patience with me.