Do you know why your plugin is pulling so often?
-
New plugin [pimatic-wunderground]
-
Everytime you refresh your browser or every {interval} minutes.
Check your log, when nobody uses the frontend.
See: https://forum.pimatic.org/topic/4149/new-plugin-pimatic-wunderground/39
and https://forum.pimatic.org/topic/4149/new-plugin-pimatic-wunderground/45 -
I was definitely not using the Frontend before 7 a.m
-
I cannot answer this. But as you can see, there are totally different intervals used for refreshing the data. This can’t be a programmatical issue.
-
version 0.2.1 released 2018-04-06
- fixed calculation of correct historical observation entry
- refactoring
-
My two cents: Pulling the data on browser refresh should be made optional. Otherwise, users with an API key on the free plan will quickly run out budget if they frequently use the Web UI.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig Could you please have a look at the code?
The frontend part only subscribes to the weather variable and changes the HTML accordingly. There is no explicit refresh triggered.
The _reloadWeather method is only called dependent on the configured interval. I really don’t know why it’s called more often at some users installation. I cannot reproduce this.
-
@saxnpaule said in New plugin [pimatic-wunderground]:
Could you please have a look at the code?
The frontend part only subscribes to the weather variable and changes the HTML accordingly. There is no explicit refresh triggered.
The _reloadWeather method is only called dependent on the configured interval. I really don’t know why it’s called more often at some users installation. I cannot reproduce this.Sure, will do.
Sorry, btw. I have been mistaken by your earlier comment “Everytime you refresh your browser or every {interval} minutes.” So, I expected a browser refresh triggers it."It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Yes, I also meant it in this way, because it’s the only possible explaination. But I can’t find any evidence in my code for this.
-
@saxnpaule said in New plugin [pimatic-wunderground]:
version 0.2.1 released 2018-04-06
- fixed calculation of correct historical observation entry
- refactoring
Now everything seems to work again. The values are refreshed on the frontend.
But im totally confused right now ^^ Calculating with different timezones is absolutely brain fuck
These are the last lines of your json request:"date": { "pretty": "5:00 PM +07 on April 06, 2018", "year": "2018", "mon": "04", "mday": "06", "hour": "17", "min": "00", "tzname": "Asia/Ho_Chi_Minh" }, "utcdate": { "pretty": "10:00 AM GMT on April 06, 2018", "year": "2018", "mon": "04", "mday": "06", "hour": "10", "min": "00", "tzname": "UTC" }, "tempm":"20.0", "tempi":"68.0","dewptm":"12.0", "dewpti":"53.6","hum":"60","wspdm":"24.1", "wspdi":"15.0","wgustm":"-9999.0", "wgusti":"-9999.0","wdird":"10","wdire":"North","vism":"10.0", "visi":"6.2","pressurem":"1019", "pressurei":"30.09","windchillm":"-999", "windchilli":"-999","heatindexm":"-9999", "heatindexi":"-9999","precipm":"-9999.00", "precipi":"-9999.00","conds":"Mostly Cloudy","icon":"mostlycloudy","fog":"0","rain":"0","snow":"0","hail":"0","thunder":"0","tornado":"0","metar":"METAR VVNB 061000Z 01013KT 9999 FEW010 BKN076 20/12 Q1019 NOSIG" }, { "date": { "pretty": "5:30 PM +07 on April 06, 2018", "year": "2018", "mon": "04", "mday": "06", "hour": "17", "min": "30", "tzname": "Asia/Ho_Chi_Minh" }, "utcdate": { "pretty": "10:30 AM GMT on April 06, 2018", "year": "2018", "mon": "04", "mday": "06", "hour": "10", "min": "30", "tzname": "UTC" }, "tempm":"20.0", "tempi":"68.0","dewptm":"13.0", "dewpti":"55.4","hum":"64","wspdm":"18.5", "wspdi":"11.5","wgustm":"-9999.0", "wgusti":"-9999.0","wdird":"10","wdire":"North","vism":"10.0", "visi":"6.2","pressurem":"1019", "pressurei":"30.09","windchillm":"-999", "windchilli":"-999","heatindexm":"-9999", "heatindexi":"-9999","precipm":"-9999.00", "precipi":"-9999.00","conds":"Mostly Cloudy","icon":"mostlycloudy","fog":"0","rain":"0","snow":"0","hail":"0","thunder":"0","tornado":"0","metar":"METAR VVNB 061030Z 01010KT 9999 FEW010 BKN078 20/13 Q1019 NOSIG" }, { "date": { "pretty": "6:00 PM +07 on April 06, 2018", "year": "2018", "mon": "04", "mday": "06", "hour": "18", "min": "00", "tzname": "Asia/Ho_Chi_Minh" }, "utcdate": { "pretty": "11:00 AM GMT on April 06, 2018", "year": "2018", "mon": "04", "mday": "06", "hour": "11", "min": "00", "tzname": "UTC" }, "tempm":"19.0", "tempi":"66.2","dewptm":"13.0", "dewpti":"55.4","hum":"68","wspdm":"13.0", "wspdi":"8.1","wgustm":"-9999.0", "wgusti":"-9999.0","wdird":"10","wdire":"North","vism":"-9999.0", "visi":"-9999.0","pressurem":"1020", "pressurei":"30.12","windchillm":"-999", "windchilli":"-999","heatindexm":"-9999", "heatindexi":"-9999","precipm":"-9999.00", "precipi":"-9999.00","conds":"Clear","icon":"clear","fog":"0","rain":"0","snow":"0","hail":"0","thunder":"0","tornado":"0","metar":"METAR VVNB 061100Z 01007KT 330V040 CAVOK 19/13 Q1020 NOSIG" }
As you can see, the latest entry is from 11:00 UTC and 18:00 Asia/Ho_Chi_Minh.
At the moment its not possible to see the actual temperatures in UTC time. There should be an entry with 14:30 UTC and 21:00 Asia/Ho_Chi_Minh time.Best regards,
André -
@andre3000 said in New plugin [pimatic-wunderground]:
But im totally confused right now ^^ Calculating with different timezones is absolutely brain fuck
Agree on this
It can be a total pain in the neck and it often takes several iterations to get it right.I found the following site useful which contains information about current time, weather, sunrise, and history weather data. For example, see the following link. If you scroll a little bit further down you get table the half-hour values of the past 24 hours. If you use CEST as base time. Ho Chi Minh is five hours ahead. If you use UTC+1, it is six hours ahead of base time.
https://www.timeanddate.com/weather/vietnam/ho-chi-minh/historic
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@saxnpaule said in New plugin [pimatic-wunderground]:
Mhh that’s strange. On my phone 5" FHD everything looks well.
With some delay I just want to show you what the plugin is looking like on my phone (Honor8, 5,2", FHD).
This is the original view of version 0.2.1
And this is my try to reduce the size. But I don’t get the forcast colum adjusted separatly without changing col1.
@SaxnPaule Do you have an idea how to solve this?
-
@saxnpaule said in New plugin [pimatic-wunderground]:
version 0.1.0 released 2018-03-25
- Provided heatindex as a variable
- Provided dewpoint as a variable
Is it possible to provide humidity as a variable?
-
Hi, I am totally new to the game!
first of all thx for this nice plugin!
Everything is running fine but I dont have now clou where and how to edit the appearence in the GUI. Like I want to add sunset/rise and the size of the columns etc. Which file do I have to edit???
Thx for pointing me in the right direction
Philipp
-
Sunset/rise isn’t provided by the wunderground plugin. Please refer to the sunrise plugin.
Editing the appearence is also not possible for the normal enduser. If you have CSS skills, you could try to edit the corresponding css file by your own.
-
@googlyeyz said in New plugin [pimatic-wunderground]:
Is it possible to provide humidity as a variable?
version 0.2.2 released 2018-04-08
- Provided humidity as a variable (currentHumidity)
-
@fabian said in New plugin [pimatic-wunderground]:
And this is my try to reduce the size. But I don’t get the forcast colum adjusted separatly without changing col1.
@SaxnPaule Do you have an idea how to solve this?
version 0.2.3 released 2018-04-08
- refactored CSS to auto size line height
I changed the line-height to auto and added a nbsp; to the icon html. Now you should be able to style it on your own.
-
@SaxnPaule thanks a lot. I will try it later and give you feedback.
-
@SaxnPaule thanks a lot. Its working fine now.
-
Since a day or two, i guess since the last update, used in a variables device i get for both $wunderweather.currentWindDir and $wunderweather.currentWindString a value of -1. Restarting Pimatic and/or emptying cache does not help. Can anybody reproduce that?
Edit: according to the variables overview the attributes should give respectively ‘West’ and ‘Calm’