need help for ecowitt wh57 lightning device

[meteoesine]

Hello everybody,
I bought an wh57 with gw1100 to monitor lightning.
Since the informations in the forum on installing ecowitt modules are quite scattered and diversified, I kindly ask - starting from the beginning - which plugins and scripts I have to install to receive only the lightning data from that single device (wh57).
I'm using meteobridge nano

Futhermore, where can i find the block in the image?
many thanks in advance for any comments

[davidefa]

1) you need to install a modified api.php, update/apiSetup.php and update/saveAPISettings.php scripts ( to support lightning data saving ). This mod is ok, for example
2) you need to pass to api.php the following fields

Code: Select all

L ( number )
LD ( distance )
LT ( timestamp )

( this post shows how Gerrit does it with meteobridge, this thread on wxforum has also great informations )
3) you need to save those fields in the database ( via meteotemplate control panel -> extra sensors )
4) you need to install the lighningew block ( this is ver 2.0 from raffaello di martino )

[meteoesine]

grazie Davide,
fatto quanto suggerito ma rimane però ancora il problema del trasferimento dati da meteobridge a meteotemplate
boh

[meteoesine]

lasciamo perdere meteobridge e provo il plugin (vrs 2.10a)...
anche qui non va.... non capisco cosa c'e' di sbagliato
i 3 file dell'api e update sono stati aggiornati

vedi screenshot allegato: tutti gli altri campi li ho lasciati vuoti

dal lato cell ho attivato solo questa. (i server WU, WOW, weathercloud sono disabilitati -vuoti)

Screenshot_20220518_192518_com.ost.wsview (FILEminimizer).jpg (252.15 KiB) Viewed 3926 times

grazie

[davidefa]

- in server ip/hostname devi mettere solo: meteoesine.it
- purtroppo questo non basta perchè il gw1000 non può inviare i dati ai siti 'in https' ( per il gw1100 dovrebbe essere uguale )
- devi disabilitare 'https rewrite rule' almeno per la directory template/plugins/ecowitt/report ( o per tutto il sito )
- su questo post di wxforum spiegano come disabilitarlo sia se il server ( apache ) usa i file .htaccess sia per server IIS ( microsoft ). Io su altervista l'ho disabilitato su tutto il sito.
- altra possibilità è utilizzare un piccolo 'forwarder' ( una piccola utility in php ) su un 'sito http': configuri il custom upload per inviare i dati a questo forwarder ed il forwarder lo reinvia al tuo sito meteoesine.it. Il sito http lo puoi, ad esempio, prendere gratuitamente su altervista ( ho usato questo metodo con un utente francese che aveva due meteohelix che non ne volevano sapere di inviare i dati al suo server )

P.S.
La configurazione del plugin è ok

[meteoesine]

grazie per la dritta.
ho optato per la soluzione più semplice e funziona:
ho modificato il file .htaccess mettendo una regola che ignora il redirect su https su template/plugins/ecowitt/report

RewriteCond %{REQUEST_URI} !^/template/plugins/ecowitt/report/

[xBenny]

Is lighningew block compatible with php8.1? It works in 7.4, but in 8.1 it gives an error. Thanks

https://www.pocasi-klabava.cz

[davidefa]

You should save in the database the L, LD and LT fields ( I see you save only L field ), you can do it via the meteotemplate control panel -> Extra Sensors.

This mod has a few bugs correction ( a few still remaining ) and the option to show a background map and is compatible with php 8.1.
The map should be a 200x200px image representing a 80x80km map ( centered on your location )

lightningew2.png (46.49 KiB) Viewed 3766 times

[xBenny]

I modified the database storage, I have all three parameters in the database now. I uploaded a new version and created a config. Unfortunately, the block still doesn't work :-/ is there anything else to try? Thanks

Edit: with 7.4 I have 2 files in the cache with 8.1. none

[davidefa]

Checking your cache/apiLog.txt I see the following:

Code: Select all

update L: 0
update LD: 
update LT:

It should mean that your wh57 did not record any strike ( and the lightningewupdater.php script stops in error with php 8.1, but not with php 7.4 ).
You need to record at least a strike.
You could try putting your wh57 near en electromagnetic noise generator ( a switching power supply should do ).
Or you can try the attached mod ( not sure if it fixes the issue )

[xBenny]

I have WH57 new, there hasn't been a storm yet

Edit: The switching power supply helped 2.1a not

[alexvanuxem]

just got an ecowitt lighning sensor just now

i added a .htaccess file in my wwwroot

got records saving every minute in csv and json format, but the reports/index.php isn't updating?

this is what is wriiten in the htaccess file

RewriteCond %{REQUEST_URI} !^/template/plugins/ecowitt/report/

i added screenshots of the settings, is there something I missed?

i added reports/inde.php?PASS=mypassword

thx

Schermafbeelding 2022-06-09 130115.png (42.19 KiB) Viewed 3675 times

Schermafbeelding 2022-06-09 130045.png (133.98 KiB) Viewed 3675 times

[Dehatter]

OK - So I am trying to play catchup with these 'new' additions and I really love what you have been doing, but I hope someone can help me.

I updated my Meteobridge to send the lightning date L, LD, and LT.

The values show in the apiLog.txt and in the meteotemplateLive.txt file.

Screenshot 2022-08-06 165845.jpg (87.13 KiB) Viewed 3253 times

BUT... I can't save LD or LT in the database because these 2 lines do not show up in the control panel for extra sensors.

Screenshot 2022-08-06 162454.jpg (99.71 KiB) Viewed 3253 times

How to I get them saved/added to the database so that they show up in the API Viewer?

Also - The information shows up in the v2.1a block, but it says there is an error at the bottom, but I do not know what is expected or what the error is.

Screenshot 2022-08-06 165443.jpg (41.59 KiB) Viewed 3253 times

Thanks in advance for any assistance with this.

Tom

[davidefa]

The lightning block need the L, LD and LT fields from the database.
To enable these fields you could install this mod ( that extends extra sensors to 8 and add lightnings fields also ): viewtopic.php?f=50&t=2064

P.S.
The apiviewer needs an update too...

[Dehatter]

This is the apiViewer you sent me on Thursday. I just installed it this morning.

Also, any chance the distances can be converted to miles?

Tom

[Dehatter]

So I have a potential bigger issue now.

Woke up this morning after changing the api.php, and the 2 files in the update folder, then monitoring it several times throughout the day yesterday - without any issues at all.

The extra sensors were all added to the database and everything was good.

Woke up a few minutes ago and noticed that my station status says offline. hmmmm
checked the api - all working
all site data is updating....

Then I checked database from the control panel and it seems the main database AND the extra sensor database quit updating at exactly 5AM eastern daylight time.

So even though i have api data, and the website is displaying data updates, something is preventing the 5min update to the database. And why would it stop at 5AM?

Any insight at all would be appreciated.

Tom

[davidefa]

You should have an error in your api.php script, to visualize the error call the script with your browser ( insert your update password ):

Code: Select all

http://www.meckweather.com/template/api.php?T=30&errors&PASS=YOURUPDATEPASSWORD

and post the result

[Dehatter]

Well I do:

Screenshot 2022-08-07 103401.jpg (161.01 KiB) Viewed 3233 times

I will try and see what it is but honestly I am not code worthy at all.

Not sure if this is a factor or just a coincidence but I have 7 extra sensors selected to save in the database and there are 7 errors from line 974.

Tom

[davidefa]

My mistake, forgot that the 'standard version' I previously linked, does not contain corrections for php 8.0/8.1 compatibility.
This version should fix it

[Dehatter]

Working. Thanks for everything - especially the quick response.

Not sure where we would be without you.

Tom

[Dehatter]

Hello David.

So, after using this for a couple of days, I have 3 ideas on my wish list.

1) I would like to have the option to use a running yearly total at the bottom or the existing storm movement line. I personally would prefer the running annual total number of strikes. Something like "Last Distance: 17km - Total strikes this year: 2485"

2) I personally would prefer a timestamp for the last strike line as opposed to saying how long ago it was.

3) I think the units should conform to the rest of the template data (miles in my case).

Not sure what others think, but that's my opinion.

And just so you know, I am very happy with it 'as is' as well.
I can only thank you again for the time and effort you have put into everything, not just this block.

Tom

[johnathan]

Before beginning the development process, it is important to define what the client wants. This will help them understand what they need, as well as the time frame in which they need the product by https://mlsdev.com. This will also help them determine what to prioritize. Often, the custom software development process requires multiple phases, including research, design and specification, programming and testing. Businesses should decide what's most important and choose the right team. The right resources can help streamline the process.

[davidefa]

ver 2.2
- supports mi/km ( according to distance settings )
- cleanup of the block
- added option to set storm activity max interval
- added options to set cache duration, show last strike timestamp and lightnings in current year

ver2.3
- corrected 'image reset' after 'storm active time' elapsed

ver2.4 ( Aug 10, 2022 )
- changed name of 'updater' function ( which 'collided' with block current )

P.S.
As the block queries the database every 10 seconds, to lighten the load on the database, I've added an option to cache these results. During this caching interval daily/yearly counts wont update ( set caching interval to 0 to disable this effect )

[Dehatter]

OK---Wow! That was fast.

All looks great except I have a red ring at 18 miles. I think this is the remnant of the last strike.

You ae definitely THE MAN - THE LEGEND!!

Tom

[meteoesine]

why is my last strike on Jan 01 1970?