Current Block (v18.1) - Now showing UV

[MonyMony]

I have noticed that my Current Conditions block is now showing UV information. What is odd is not a sensor I have nor did I do anything knowingly to start showing this. How do I hide this once again as I do not see any option for this in the SETTINGS for this block?

Thanks!

http://www.cecilweather.com/weather/cec ... esktop.php

[Jachym]

I have noticed that my Current Conditions block is now showing UV information. What is odd is not a sensor I have nor did I do anything knowingly to start showing this. How do I hide this once again as I do not see any option for this in the SETTINGS for this block?

Thanks!

http://www.cecilweather.com/weather/cec ... esktop.php

You didnt tell us what you are using to send data to the template (which SW), but whatever you use, it is sending UV information:

Raw data, notice the UV value:
http://www.cecilweather.com/weather/cec ... teLive.txt

This must be sorted in whatever is sending data to the template. If there is UV available, the template will think it is available.

[MonyMony]

You didnt tell us what you are using to send data to the template (which SW)

Using WeatherCat v2.42B15. You are right that somehow in the software, where I have not looked at the preferences in months the UV setting was active.

Thanks for pointing me in the right direction to resolve this.

[MonyMony]

Ok, spoke too soon. While there is an option in WeatherCat to show the UV gauges in the software, everything else related to this is automatically set. I have checked and my local software databases are showing all "0" for UV, and the UV sensor is showing invalid. That said the API is reporting a 16.0 for UV. I will post separately on the WeatherCat forum to make sure I am not missing a setting within the software that might explain this behavior. Still have odd it just started displaying this in the Current block in the past few days.

[Reinhard]

MonyMony

Shot in the blue: Go to the control panel in Meteotemplate (NOT to main setup) and in the database section look for additional sensors. Maybe herein you can disable UV - at least you can disable saving UV readings to database.

[Jachym]

This will have no effect on the Current block, the current block does not use db and uses whatever it finds in the current conditions file. This needs to be sorted in WC

[nikokara - BANNED]

Monymony

I can tell you how to hide it (by changing the code in the block),
but first I need Jachims permission.

[Jachym]

I dont mind But this should be sorted in WC because it will cause problems at other places too. If there is UV value sent to the template, it assumes it is available.

[Reinhard]

Now you know that I am using WeatherCat as well, and after all I do have no problems with the auto-API-feed WC offers. MonyMony, maybe we can discuss this issue in the WeatherCat forum.

[MonyMony]

Now you know that I am using WeatherCat as well

Yes, I know you are a fellow WeatherCat user! I even checked your page before posting. I am going to post this to the WC page later this evening we we can certainly discuss there.

[MonyMony]

I can tell you how to hide it (by changing the code in the block),

Thank you for the offer. Depending on what I find out from the software side I might just do this but for the moment I will just wait.

[MonyMony]

MonyMony

Shot in the blue: Go to the control panel in Meteotemplate (NOT to main setup) and in the database section look for additional sensors. Maybe herein you can disable UV - at least you can disable saving UV readings to database.

Sorry, forgot to respond to this that I have already checked this and I am not saving this value. Good thought though!

[MonyMony]

Hello All,

I have heard back from the WeatherCat developer who provided me a process to see exactly what the software is sending to the Meteotemplate API. When I do this I see this:

Code: Select all

WeatherCat[266]: MeteoTemplate:  ?U=1507753881&B=80&W=1.6&G=3.2&H=77&T=23.0&HIN=50&TIN=29.6&RR=0.00&R=0.00&P=1016.32&S=1746&LW4=0

The developer went on to state that if UV information was being sent by WeatherCat I would see '&UV=x.x' in the string which I do not.

I also noticed that the temperature values I am seeing in the string sent by WeatherCat do not match what is shown in the cache files 'latestApiCache.txt' and 'latestApiLog.txt' where there are a crazy amount of places after the decimal place shown.

{"U":1507757127,"B":13,"W":0,"G":1.600000000000000088817841970012523233890533447265625,"H":82,"T":21.89999999999999857891452847979962825775146484375,"HIN":50,"TIN":29.5,"RR":0,"R":0,"P":1016.490000000000009094947017729282379150390625,"S":1747,"LW4":0,"SW":"WeatherCatV2.42B15","UTime":1507757127,"BTime":1507757127,"WTime":1507757127,"GTime":1507757127,"HTime":1507757127,"TTime":1507757127,"HINTime":1507757127,"TINTime":1507757127,"RRTime":1507757127,"RTime":1507757127,"PTime":1507757127,"STime":1507757127,"LW4Time":1507757127,"SWTime":1507757127,"UV":16,"UVTime":1507757127,"D":18.699999999999999289457264239899814128875732421875,"DTime":1507757127,"A":25,"ATime":1507757127}

After seeing this I have noticed that WeatherCat is reporting my information in Metric values but the API looks to be converting them to Imperial Units if I look at 'latestApiLog.txt.

{"timestamp":["1507756226","1507756286","1507756346","1507756406","1507756466"],"date":["2017-10-11 17:10:26","2017-10-11 17:11:26","2017-10-11 17:12:26","2017-10-11 17:13:26","2017-10-11 17:14:26"],"T":[71.960000000000007958078640513122081756591796875,71.960000000000007958078640513122081756591796875,71.960000000000007958078640513122081756591796875,71.780000000000001136868377216160297393798828125,71.780000000000001136868377216160297393798828125],"H":["81","80","80","80","80"],"P":[30.008956275600002783221498248167335987091064453125,30.008956275600002783221498248167335987091064453125,30.008956275600002783221498248167335987091064453125,30.01102337420000054635238484479486942291259765625,30.011909273600000602755244472064077854156494140625],"W":[0,0.99419360000000001065245669451542198657989501953125,0.99419360000000001065245669451542198657989501953125,0,0.99419360000000001065245669451542198657989501953125],"G":[0.99419360000000001065245669451542198657989501953125,1.9883872000000000213049133890308439731597900390625,1.9883872000000000213049133890308439731597900390625,0.99419360000000001065245669451542198657989501953125,1.9883872000000000213049133890308439731597900390625],"B":["38","38","38","38","37"],"R":[0,0,0,0,0],"RR":[0,0,0,0,0],"D":[65.840000000000003410605131648480892181396484375,65.4800000000000039790393202565610408782958984375,65.4800000000000039790393202565610408782958984375,65.30000000000001136868377216160297393798828125,65.30000000000001136868377216160297393798828125],"A":[77.539999999999992041921359486877918243408203125,76.81999999999999317878973670303821563720703125,76.81999999999999317878973670303821563720703125,77.18000000000000682121026329696178436279296875,76.6400000000000005684341886080801486968994140625]}

Could this translation be where I am picking up the UV? I also noticed in the latestApiCache.txt file that initial values reported at the top of the file do not show anything related to UV.

[quote]Authorized access.

Current date/time: 2017-10-11 17:25:27

api called by http

update U: 1507757127

update B: 13

update W: 0.0

update G: 1.6

update H: 82

update T: 21.9

update HIN: 50

update TIN: 29.5

update RR: 0.00

update R: 0.00

update P: 1016.49

update S: 1747

update LW4: 0

update SW: WeatherCatV2.42B15[/quote]

Hopefully we are starting to zero in on the root cause here.

[Jachym]

Hi,
the data sent to the API should always be in metric and the template therefore performs no conversion to it because it needs it in metric.

Check: meteotemplateLive.txt - this is the raw data sent to the template taken from the string sent by WC and saved before further processing

[MonyMony]

Checked and file shows this:

{"U":1507758388,"B":5,"W":0,"G":0,"H":85,"T":21.5,"HIN":50,"TIN":29.699999999999999289457264239899814128875732421875,"RR":0,"R":0,"P":1017.1000000000000227373675443232059478759765625,"S":1746,"LW4":0,"SW":"WeatherCatV2.42B15","UTime":1507758388,"BTime":1507758388,"WTime":1507758388,"GTime":1507758388,"HTime":1507758388,"TTime":1507758388,"HINTime":1507758388,"TINTime":1507758388,"RRTime":1507758388,"RTime":1507758388,"PTime":1507758388,"STime":1507758388,"LW4Time":1507758388,"SWTime":1507758388,"UV":16,"UVTime":1507758388,"D":18.89999999999999857891452847979962825775146484375,"DTime":1507758388,"A":24.699999999999999289457264239899814128875732421875,"ATime":1507758388}

WeatherCat is reporting sending this:

WeatherCat[266]: MeteoTemplate: ?U=1507758388&B=5&W=0.0&G=0.0&H=85&T=21.5&HIN=50&TIN=29.7&RR=0.00&R=0.00&P=1017.10&S=1746&LW4=0

Something odd is going on before the meteotemplateLive.txt file is created.

[Jachym]

You can ignore the decimals, thats due to the variable type, but that UV... it must come from somewhere I guess we will need to do some test script to really save the raw data even before meteotemplateLive.txt is created. Email me your admin password and I will look at it tomorrow.

[Luc]

Hi,
the data sent to the API should always be in metric and the template therefore performs no conversion to it because it needs it in metric.

Check: meteotemplateLive.txt - this is the raw data sent to the template taken from the string sent by WC and saved before further processing

Since v16 adjustment variables are added to Temperature and Pressure and multiplied for Daily precipitation and Wind Speed. See section 'Adjustments' in the main settings file.

May be we should save the results of the adjustments in meteotemplateLive.txt with three decimals.

[Jachym]

The problem here is where the uv is coming from

[MonyMony]

Email me your admin password and I will look at it tomorrow.

Private email sent... thank you!

[Luc]

Hi MonyMony,
Can you please delete the file meteotemplateLive.txt?
Then the UV information should be gone in your current block.
Luc

[Jachym]

This needs to be taken into account in the next update (v17), there is a problem with the API and how it handles the data. In particular, once you send UV to the template, the reference to it stays there forever regardless of whether you are still sending it. Deleting meteotemplateLive.txt should solve it.

[MonyMony]

Deleting meteotemplateLive.txt should solve it.

I can confirm removing the file resolved this. Now how the UV reading initially got in there in the first place is anyone's guess. At least there is a work-around and an understanding of what is going on. Thanks everyone for the help!

[Luc]

Now how the UV reading initially got in there in the first place is anyone's guess.

For me it's not because you told us yourself how it got there!

Using WeatherCat v2.42B15. You are right that somehow in the software, where I have not looked at the preferences in months the UV setting was active.

[MonyMony]

I guess the software is the possible source by sending a random one-time UV entry, but no way to prove. I would have to turn on logging for everything sent by WeatherCat to try and catch a stray entry. Maybe a crash that I did not know about caused a garbage submission... I really have no idea.

[Reinhard]

Glad you sorted it out!