Lightning

[Nossie]

Code: Select all

Lightning	
  Strikes today	0
  Time last strike	02:04
  Distance last strike	17.059003999999998

Excellent progress on this Hans,

A few things, can we round down the distance? and - the data so far suggests the strike was at 02:04 this morning ....

However my display shows 167 days ago and the cumulus software shows 15/08/22 - the data without this context is a bit weird, anyway of extracting that somehow?

hmmmm I've also just noticed some of my data is missing again - CO2..... where are youuuuuu?

cheers!

[HansR]

Code: Select all

Lightning	
  Strikes today	0
  Time last strike	02:04
  Distance last strike	17.059003999999998

A few things, can we round down the distance? and - the data so far suggests the strike was at 02:04 this morning ....

What do you mean by round down the distance... aha, you are in miles which is converted from the km coming from the sensor.
OK, I'll format to an F0 for any distance (meaning no decimals at all)

However my display shows 167 days ago and the cumulus software shows 15/08/22 - the data without this context is a bit weird, anyway of extracting that somehow?

Well, it says no lightning strikes today (zer0) so the time and distance must be from another strike remembered by CMX.
I use the webtags <#LightningStrikesToday> <#LightningTime> <#LightningDistance> to fill the data to the extrasensorsrealtime.txt. Those numbers come from CMX. Maybe Mark can shed a light on this? Ultimately I could make some logic to set it all to 0.

hmmmm I've also just noticed some of my data is missing again - CO2..... where are youuuuuu?

I have no CO2 sensor myself but I did not change anything there either.
So what is the value of the CO2 parameter in the ExtraSensors section?

[Nossie]

I created a new thread for the CO2 issue.

Rounding down might be the best option, so is that going to reset back to 0 and still show another time when there was a strike? My understanding of this data is that if it was zero'd it would only make sense until another storm.

I'd probably rather have
Last strike : 08/15/22 02:04

if possible.

[HansR]

I created a new thread for the CO2 issue.

OK

Rounding down might be the best option, so is that going to reset back to 0 and still show another time when there was a strike? My understanding of this data is that if it was zero'd it would only make sense until another storm.

I'll round (javascript function) the for the distance so you get it rounded to the nearest integer.
Apparently distance and date do not reset to zero, I just display what I get..

I'd probably rather have
Last strike : 08/15/22 02:04

I'll add the date

[Nossie]

Hi Hans,

now showing the unit mi, however the data is still in km - sorry for being British XD

[HansR]

Hi Hans,

now showing the unit mi, however the data is still in km - sorry for being British XD

Actually, that surprises me (the data in km that is, not the British XD, have no idea what that is )

The value retrieved from the webtag is in km (I think you can't change that can you?) and I convert it to the unit used by the CMX setting for distance unit which in your case is mile:

Code: Select all

             tmpDistance = ExtraSensorRT[23] * 1.60934;

So the value you see is higher than the value retrieved from the sensor (through CMX). And the conversion is to miles.
So afaics it is correct now.

Where do you see your data is in km?

[freddie]

Sorry to butt in - surely if you convert km to miles then the values will be smaller? 1 mile = 1.6 km.

[HansR]

Sorry to butt in - surely if you convert km to miles then the values will be smaller? 1 mile = 1.6 km.

To avoid confusion, that is more or less what I say:

So the value you see is higher than the value retrieved from the sensor (through CMX).

Where the value you see is the value you observe on the website after the conversion I apply and where the value retrieved from the sensor is what you get through the webtag from CMX and what you see on ecowitt.net.

[Nossie]

The value on the ecowitt display and cmx is currently 11 miles...

And if you convert 11 miles into km - you get?


EDIT: My data is in miles, you are currently converting it to eurometers and adding the Mi

[HansR]

So, where did you set it to miles?
Or does the unit adapt to the settings of the GW1100 (there is no distance setting there!) ?

[HansR]

The value on the ecowitt display and cmx is currently 11 miles...

And if you convert 11 miles into km - you get?


EDIT: My data is in miles, you are currently converting it to eurometers and adding the Mi

No I think your data is in km and am converting it to miles

[Nossie]

I think maybe not?

Not sure what else to say - unless the data is in km and the display and cmx are changing it to miles.

Let me check the manual to see if I'm missing a setting or forgot something

[HansR]

OK. You have data in miles and I convert it to miles because I think it is in km. That is obviously not correct.

So my question is where is this unit set? Because as far as I can see there is no unit setting for distance unless the unit for speed (in your case miles/hour) is extended to distance. I assume it is.

Anyway, I will remove the conversion and only display the unit which is used by CMX for distance.

I assume the other things are OK now, also the tooltips. The percentage I see in the charts for LeafWetness and SoilMoisture must have been added by you (axis Free and you modified the text).

[HansR]

I will create a new release now.

[Nossie]

Everything else so far is perfect Hans =) thank you.

Yeah I found three references to miles in the manual and none of them point to where it can be changed to km Maybe it uses a previous setting from something else?

I did add the percentages to the language text yes.

Is there also a language section to add (miles) to distance to last strike?