Topic: FOSHKplugin - brief introduction

[thunder.ky]

Wow, Oli, you're really making FOSHKplugin more and more advanced. 

I'll take a look at the new TAGFILE functionality over the next week!

[broadstairs]

Oliver I was wondering if there was a setting in the plugin like there is in both Weather Display and CMX (and perhaps others) to limit wind gust values. My WS80 today sent a max gust value of 85.9mph which I think is unlikely yes it is windy here but I've never had a gust in excess of 65mph since I started recording in 2005. Obviously WD and CMX both will ignore this value as I've now set the limit to 65mph. Is this something you would consider adding in the plugin as it would then not send this bad data to my Android display  or anywhere else for that matter.

Stuart

[olicat]

Hi Stuart!

Interesting approach. I wasn't aware that CMX and WD handled it that way.

No, so far there is no comparable possibility with FOSHKplugin - it stubbornly sends the values it has received from the weather station.
I also have a certain stomachache about reacting to the reported values in this way - after all, it is not impossible that there really are gusts of wind with this speed. Even without announcing them in advance.

But I am thinking about an optional cut-off function. However, this can only be value-related and does not consider the historical development (FOSHKplugin is event- and not database-based and has hardly any knowledge about the past - although: for wind speed, direction and gusts there is a 10-minute history).
If necessary, one could define the value from which onwards transmission does not take place:

cut_off = windgustmph=65

This would mean that the windgustmph key would not be processed further if the value is greater than or equal to the specified value (here: 65).
Would this be an acceptable approach?
Or should the history and/or the wind be taken into account? But in which way? After all, gusts can indeed occur suddenly and without notice.

Can anyone think of other sensor values that should also be protected in this way? Or does this only apply to wind gusts?

Oliver

[broadstairs]

Oliver the issue today was 85.9 mph was so far above any other wind speed recorded today that it must have been an aberration. I have never seen anything near that recorded locally. As I said my highest ever gust recorded since 2005 was around 65mph. I'd suggest perhaps either capping it or I believe what CMX does is to ignore it and just not send it, I thinnk I'd prefer the latter so no value gets recorded for that interval. I believe this is a WS80 issue and possibly WS90.

Certainly wind gust is the only one I have had an issue.

Stuart

[Rover1822]

No chance someone aimed a leaf blower at it? . I am kidding

[broadstairs]

No chance someone aimed a leaf blower at it? . I am kidding

      

Stuart

[olicat]

Hi!

if there was a setting in the plugin like there is in both Weather Display and CMX (and perhaps others) to limit wind gust values

With FOSHKplugin v0.10 there will be such an option:

Export\LIMIT_WINDGUST = value            # ignore windgustmph if >= value (key will be renamed to _windgustmph) and use last "good" maxdailygust

I'll test this now ...

add:
testing done - works as expected

Oliver

[olicat]

Stuart,

85.9 mph was so far above any other wind speed recorded today

doesn't maxdailygust then also show the wrong value?
And just to be sure:
We are talking about windgustmph and not windspeedmph?

Oliver

[broadstairs]

Yes it does.....

Stuart

[broadstairs]

Thinking about this some more I'm not sure if either CMX or WD actually ignore that max reading and just use the wind gust supplied value and use the max received from that. The max gust sent by the gateway is also in my case that 85.9mph which I believe to be invalid. So to be sure I think if either wind gust of max gust are in excess of the limit value both should be ignored. I noticed that CMX has a default value for max gust in settings of 999 so effectively allows anything, WD does something similar. I have no idea what other software does.

Stuart

[olicat]

Hi!

I think if either wind gust of max gust are in excess of the limit value both should be ignored.

With the wind gust value, a wrong value can indeed be ignored - it comes again with the next interval - hopefully correct again.

However, maxdailygust is sent again and again by the console until 24:00 - so it does not make sense to completely dispense with this value for the rest of the day. Because this would mean that a real maximum wind gust would no longer be recorded and forwarded.

So in future FOSHKplugin will cache the last valid maxdailygust and output it as maxdailygust instead of the value >= IGNORE_WINDGUST.

Actually, I would expect this behaviour already in the firmware of the console ...

Oliver

[broadstairs]

Hi!

I think if either wind gust of max gust are in excess of the limit value both should be ignored.

With the wind gust value, a wrong value can indeed be ignored - it comes again with the next interval - hopefully correct again.

However, maxdailygust is sent again and again by the console until 24:00 - so it does not make sense to completely dispense with this value for the rest of the day. Because this would mean that a real maximum wind gust would no longer be recorded and forwarded.

So in future FOSHKplugin will cache the last valid maxdailygust and output it as maxdailygust instead of the value >= IGNORE_WINDGUST.

Actually, I would expect this behaviour already in the firmware of the console ...

Oliver

I think your suggestion is a good one. I'm not sure there is anything in f/w to alter the max gust value, certainly I have found no options to allow capping of wind speeds max or otherwise on either GW1000 or GW1100 and I suspect it is unlikely to happen on anything other than a WS80 or WS90.

Stuart