meteohub.de

We had a short power outage today and I noticed in meteobridge the lightning sensor and historic data in the ‘Min/Max’ tab had disappeared, therefore nothing was being sent to my Weather34 template and the data in the lightning module had nothing in it (using the new ecowitt lightning module). I managed to generate a ‘false’ strike which was then picked up in meteobridge and the data in the ‘Min/Max’ tab came back as it was before – which then got my lightning module in my Weather34 template back up and running.

I then replicated a power outage and the same thing happened – when this happens it seems meteobridge is waiting for a strike to then repopulate the historic data. Until that happens the lightning module in the Weather34 template will be empty.

I am not sure if this how it always, or was or a result of the recent changes. It’s not a big issue but I thought I would raise it. Can anybody else replicate this and see what I am seeing, or am I doing something wrong?

It happens to me with RPI, not with TP-link or DIR-505.

It happens to me with RPI, not with TP-link or DIR-505.

Thanks for confirming - yes I am using the RPI version.

cheffy wrote: ↑Wed Aug 18, 2021 6:52 am We had a short power outage today and I noticed in meteobridge the lightning sensor and historic data in the ‘Min/Max’ tab had disappeared, therefore nothing was being sent to my Weather34 template and the data in the lightning module had nothing in it (using the new ecowitt lightning module). I managed to generate a ‘false’ strike which was then picked up in meteobridge and the data in the ‘Min/Max’ tab came back as it was before – which then got my lightning module in my Weather34 template back up and running.

You have observed that after an RPI reboot, the lightning sensor and historic data in the ‘Min / Max’ reappear.

If I reboot the RPI the ‘Min/Max’ remains, so no issue.

It happens if the GW1000 is powered off at the same time - so a like a power outage. When it powers back on the ‘Min/Max’ disappears and all the lightning data on meteobridge is gone - therefore no data passing through to my Weather34 template.

You have to wait for another lightning strike to register before all the lightning data returns in meteobridge.

So I have this configuration - added a GW1000 and WH57. My raw sensor data shows a strike from yesterday. I assume that's by design - it registers the last strike until the next.

Guy

Meanwhile some fixes have been made by Boris and
- the lightning values remain in the Min/Max overview
- the last strike info (EPOCH date/time and distance) are recorded and can be retrieved with e.g. [lgt0total-nonzerotime=epoch],
even when the GW1100/GW1000/WH2650/HP2551 consoles "forget" the info after a reset, restart, firmware update.
All the earlier known and reported issues in this thread and another similar one have been resolved.
Thanks, Boris !

even when the GW1100/GW1000/WH2650/HP2551 consoles "forget" the info after a reset, restart, firmware update.

Using the RPI I am still seeing meteobridge lose the lightning sensor/data if the GW1000 is powered off/firmware update. It returns when another lightning strike is recorded.

I tested again today with the latest update of meteobridge and it is still happening.

I think Josep confirmed it only happens with the RPI - TP-link or DIR-505 seems to working fine.

It's not a big issue because it doesn't happen very often, but it would be nice to get it fixed when Boris has some spare time.

cheffy wrote: ↑Mon Oct 25, 2021 12:01 pm

even when the GW1100/GW1000/WH2650/HP2551 consoles "forget" the info after a reset, restart, firmware update.

Using the RPI I am still seeing meteobridge lose the lightning sensor/data if the GW1000 is powered off/firmware update. It returns when another lightning strike is recorded.
...

I'm also using a RPi and 2 MB Pro - what you say
is correct for the live data - and that's "normal" as the GW1000 doesn't send a time stamp after a restart.
So what is MB supposed to show as live data when none are sent ?
However, the last strike time stamp can still be retrieved from the database [lgt0total-nonzerotime] !
That hadn't been the case before.
"Fixing" the GW1000 at the MB would be sort of tricky - like if there is an empty last strike time stamp, then take the one ([lgt0total-nonzerotime]) from the database...
Hopefully future GW1000 and GW1100 firmware updates will solve this issue at the device end.

Hopefully future GW1000 and GW1100 firmware updates will solve this issue at the device end.

Yes I agree, ultimately the best way to fix this would be at the device end.

When this happens I also lose the data in meteobridge in the 'Min/Max' tab and therefore no data is passed onto the Weather34 template. When a new strike is registered it reappears.

What I don't understand is this didn't happen in the TP-link version I had - the historic data in the 'Min/Max' tab would remain, so based on this I assume meteobridge must know how to retain the historic data even when the lightining sensor is lost.

Maybe it's me and I am doing something wrong my end, or maybe that's how it works, but I know Josep managed to replicate this when I first raised it.

Can you test the following with yours to see what happens?
Turn off GW1000
Turn on GW1000
Reboot meteobridge
Do you still have lightning data in the 'Min/Max' tab?

Like I said before, it's not a big issue. These events don't happen very often and when they do I can easily generate a 'false' lightning strike to get the data back.

cheffy wrote: ↑Tue Oct 26, 2021 11:22 am

Hopefully future GW1000 and GW1100 firmware updates will solve this issue at the device end.

Yes I agree, ultimately the best way to fix this would be at the device end.

When this happens I also lose the data in meteobridge in the 'Min/Max' tab and therefore no data is passed onto the Weather34 template. When a new strike is registered it reappears.

What I don't understand is this didn't happen in the TP-link version I had - the historic data in the 'Min/Max' tab would remain, so based on this I assume meteobridge must know how to retain the historic data even when the lightining sensor is lost.

Maybe it's me and I am doing something wrong my end, or maybe that's how it works, but I know Josep managed to replicate this when I first raised it.

Can you test the following with yours to see what happens?
Turn off GW1000
Turn on GW1000
Reboot meteobridge
Do you still have lightning data in the 'Min/Max' tab?

Like I said before, it's not a big issue. These events don't happen very often and when they do I can easily generate a 'false' lightning strike to get the data back.

I have no lightning data !! After a power outage, it is a nuisance to create a false beam to recover the data again. I do not understand that in TP-link the data is recovered and not in RPI?

cheffy wrote: ↑Tue Oct 26, 2021 11:22 am

Hopefully future GW1000 and GW1100 firmware updates will solve this issue at the device end.

Yes I agree, ultimately the best way to fix this would be at the device end.

When this happens I also lose the data in meteobridge in the 'Min/Max' tab and therefore no data is passed onto the Weather34 template. When a new strike is registered it reappears.

What I don't understand is this didn't happen in the TP-link version I had - the historic data in the 'Min/Max' tab would remain, so based on this I assume meteobridge must know how to retain the historic data even when the lightining sensor is lost.

Maybe it's me and I am doing something wrong my end, or maybe that's how it works, but I know Josep managed to replicate this when I first raised it.

Can you test the following with yours to see what happens?
Turn off GW1000
Turn on GW1000
Reboot meteobridge
Do you still have lightning data in the 'Min/Max' tab?

Like I said before, it's not a big issue. These events don't happen very often and when they do I can easily generate a 'false' lightning strike to get the data back.

There is still an issue with the WH57 lightning count and last strike time stamp.
There seem to be several events which trigger MB to forget the lightning data on RPi - I keep on reporting to Boris about the issue, but until now he doesn't seem to have figured out the reason.

1. one reason is a reboot - after a reboot the data disappears from min/max and the variable [nonzerotime] provides an empty string even though
the data is still in the database
2. if only one strike occurs after the reboot, the strike count reappears, the last time stamp becomes available again, but the time stamp is still the time stamp of the last strike before that i.e. the time stamp which disappeared after the reboot.
MB records a strike count 0 (zero). The database records "--" ever since the new lightning occurred, before the history shows just an empty field. Only if a 2nd strike occurs, then the count will be one and the correct time stamp of that 2nd one becomes available as [nonzerotime] (e.g. [lgt0total-nonzerotime=epoch]) - but the total count is 1 and not 2 as it should be.
3. there seems to be also a time related cause for the disappearance - I'm still observing that
It happens with the RPi and the MB Pro.
It is interesting that in the non-database versions (repurposed routers - that what TP-Link refers to I assume) this doesn't or didn't appear. That may be a hint pointing at the database/software communication.

@woolfg
could you change the subject in the initial post from "solved" into "unsolved"
otherwise it gives the impression that all is fine (what we earlier thought it were)

meanwhile the availability of lgt0total-nonzerotime has stabilized. (I haven't rebooted my MB/RPi yet ever since though - there was no need - it's running on build 2671 for over 100 days ).

this might be a old thread, but please help me

primary station is davis wll
1st and 2nd are air davis airlinks

1st airlink is reportiing to meteotemplate , 2nd isn't mapped although i have temp and hum of 1st and 2nd

third station is gw1100 only lightning, got temp and hum reporting to meteotemplate.

read the threads: what do I need to do exactly to get airlink2 and the gw1100 lightning reporting to meteotemplate?

thx

alex

alexvanuxem wrote: ↑Wed Jun 08, 2022 10:44 pm this might be a old thread, but please help me

primary station is davis wll
1st and 2nd are air davis airlinks

1st airlink is reportiing to meteotemplate , 2nd isn't mapped although i have temp and hum of 1st and 2nd

third station is gw1100 only lightning, got temp and hum reporting to meteotemplate.

read the threads: what do I need to do exactly to get airlink2 and the gw1100 lightning reporting to meteotemplate?

thx

alex

have a look at https://www.wxforum.net/index.php?topic ... #msg447807
if this thread here and some others here regarding either the WH57+MT or MT didn't get you any farther