Weather34 TEMPLATE

[weatherist34]

as per information provided by Boris to use with Davis Air Quality

[air0pm-act:--] PM1
[air1pm-act:--]PM 2.5
[air2pm-act:--]PM 10


thats what I worked with think your trying to add something onto the template that doesn't conform to the API . as per previous Ive not seen those strings or seen any reference to those like. I think you are using a plugin ? self compiled .

here is what I was sent in the week I simply worked of those simple standard strings your working with something totally different I have no reference too or see the requirement.

Screenshot at Sep 20 22-26-23.png (67.56 KiB) Viewed 4633 times

[weatherist34]

now what you could do is simply edit the config file , simply do a backup of config file to your desktop

open your editor

find this at the bottom

xhwstemplate %s/mb.php?d=[DD]/[MM]/[YYYY] [hh]:[mm]:[ss] [th0temp-act:--] [th0hum-act:--] [th0dew-act:--] [wind0avgwind-act:--] [wind0wind-act:--] [wind0dir-act:--] [rain0rate-act:--] [rain0total-daysum:--] [thb0seapress-act:--] [wind0dir-avg5:--] [wind0wind-act=bft.0:--] m/s C hPa mm [wind0wind-avg5:--] [thb0seapress-val60:--] [rain0total-monthsum:--] [rain0total-yearsum:--] [rain0total-ydaysum:--] [thb0temp-act:--] [thb0hum-act:--] [wind0chill-act:--] [th0temp-val60:--] [th0temp-dmax:--] [th0temp-dmaxtime:--] [th0temp-dmin:--] [th0temp-dmintime:--] [wind0avgwind-dmax:--] [wind0avgwind-dmaxtime:--] [wind0wind-dmax:--] [wind0wind-dmaxtime:--] [thb0seapress-dmax:--] [thb0seapress-dmaxtime:--] [thb0seapress-dmin:--] [thb0seapress-dmintime:--] [mbsystem-swversion:--] [mbsystem-buildnum:--] [wind0wind-max10:--] [mbsystem-platform:--] -- [uv0index-act:--] [rain0total-sum24h] [sol0rad-act:--] [wind0dir-avg10:--] [rain0total-sum60:--] [th0dew-mmax:--] [th0dew-mmaxtime:--] [th0dew-mmin:--] [th0dew-mmintime:--] [th0dew-ydmax:--] [th0dew-ydmaxtime:--] [th0dew-ymax:--] [th0dew-ymaxtime:--] [th0dew-ymin:--] [th0dew-ymintime:--] [uv0index-dmax:--] [th0hum-dmax:--] [th0hum-dmaxtime:--] [th0hum-dmin:--] [th0hum-dmintime:--] [th0dew-dmax:--] [th0dew-dmaxtime:--] [th0dew-dmin:--] [th0dew-dmintime:--] [th0temp-val15:--] [th0hum-val15:--] [th0dew-val15:--] [thb0temp-val15:--] [thb0hum-val15.0:--] [wind0wind-avg15:--] [wind0wind-avg30:--] [lgt0energy-act:--] [lgt0dist-act:--] [lgt0dist-age:--] [lgt0total-daysum.0:--] [lgt0total-monthsum.0:--] [lgt0total-yearsum.0:--] [sol0rad-dmax:--] [mbsystem-uptime:---] [th0temp-ydmax:--] [th0temp-ydmaxtime:--] [th0temp-ydmin:--] [th0temp-ydmintime:--] [th0temp-mmax:--] [th0temp-mmaxtime:--] [th0temp-mmin:--] [th0temp-mmintime:--] [th0temp-ymax:--] [th0temp-ymaxtime:--] [th0temp-ymin:--] [th0temp-ymintime:--] [wind0wind-ydmax:--] [wind0wind-ydmaxtime:--] [wind0wind-mmax:--] [wind0wind-mmaxtime:--] [wind0wind-ymax:--] [wind0wind-ymaxtime:--] [rain0total-ydmax:--] [rain0total-mmax:--] [rain0total-mmintime:--] [rain0total-ymax:--] [rain0total-ymaxtime:--] [sol0rad-dmax:--] [sol0rad-dmaxtime:--] [sol0rad-ydmax:--] [sol0rad-ydmaxtime:--] [sol0rad-mmax:--] [sol0rad-mmaxtime:--] [sol0rad-ymax:--] [sol0rad-ymaxtime:--] [uv0index-dmaxtime:--] [uv0index-ydmax:--] [uv0index-ydmaxtime:--] [uv0index-mmax:--] [uv0index-mmaxtime:--] [uv0index-ymax:--] [uv0index-ymaxtime:--] [th0dew-ydmin:--] [th0dew-ydmintime:--] [mbsystem-lastgooddata:--] [th0temp-avg60:--] [rain0total-nonzerotime:--] [th0temp-amax:--] [th0temp-amaxtime:--] [th0temp-amin:--] [th0temp-amintime:--] [th0dew-amax:--] [th0dew-amaxtime:--] [th0dew-amin:--] [th0dew-amintime:--] [wind0wind-amax:--] [wind0wind-amaxtime:--] [thb0seapress-ydmax:--] [thb0seapress-ydmaxtime:--] [thb0seapress-ydmin:--] [thb0seapress-ydmintime:--] [thb0seapress-mmax:--] [thb0seapress-mmaxtime:--] [thb0seapress-mmin:--] [thb0seapress-mmintime:--] [thb0seapress-ymax:--] [thb0seapress-ymaxtime:--] [thb0seapress-ymin:--] [thb0seapress-ymintime:--] [thb0seapress-amax:--] [thb0seapress-amaxtime:--] [thb0seapress-amin:--] [thb0seapress-amintime:--] [rain0total-allsum:--] [th0temp-davg:--] [mbsystem-lunarsegment:--] [mbsystem-lunarpercent:--] [mbsystem-daylength:--] [mbsystem-moonrise:--] [mbsystem-moonset:--] [wind0wind-davg:--] [th0hum-mmax:--] [th0hum-mmaxtime:--] [th0hum-mmin:--] [th0hum-mmintime:--] [th0hum-ymax:--] [th0hum-ymaxtime:--] [th0hum-ymin:--] [th0hum-ymintime:--] [th0hum-ydmax:--] [th0hum-ydmaxtime:--] [th0hum-ydmin:--] [th0hum-ydmintime:--] [thb0lowbat-act:--] [th0lowbat-act:--] [rain0total-max@M1] [rain0total-max@Y1] [air0pm-act:--] [th0temp-avg5:--] [thb0seapress-avg5:--] [uv0index-avg5:--] [wind0avgwind-avg5:--] [air0pm-act:--] [air1pm-act:--] [air2pm-act:--] [th0hum-avg5:--] [th0temp-yavg:--] [wind0wind-yavg:--] [th0temp-starttime:--] [wind0wind-starttime:--] [wind0dir-davg:--] [wind0wind-dmax=bft.0:--] [wind0wind-davg=bft.0:--] [wind0dir-mavg:--] [th0heatindex-ymax:--] [th0heatindex-ymaxtime:--] [wind0chill-ymin:--] [wind0chill-ymintime:--] _[forecast-text:]


then lets say use the [sol0rad-dmax:--] [sol0rad-dmaxtime:--] [sol0rad-ydmax:--] strings and replace them with your strings you want to add

the 3 strings [sol0rad-dmax:--] [sol0rad-dmaxtime:--] [sol0rad-ydmax:--]
replace with for example
[air1!0pm:--] [air1!12pm:--] [air1!2pm:--]

once you edited and replaced then upload the config and save

however you will lose these upon every firmware update applied so if have reboot set to get newest then it will be overwritten

in the template these 3 strings are positioned with

105 [sol0rad-dmax:--]
106 [sol0rad-dmaxtime:--]
107 [sol0rad-ydmax:--]

you could then replace in the livedata.php

105 [air1!0pm:--]
106 [air1!12pm:--]
107 [air1!2pm:--]

then build your module accordingly with the new livedata values

only thing I can suggest you try however do it at your risk but I use a different compiled API from the firmware released API for my own personal use in this manner .this is how I test new values/strings in the API before requesting/sending to Boris too update the API ..

[admin]

Next week I will think about how to best map any air sensors to the default air0pm, air1pm, etc by selecting them as primary on the "historical data" tab in Meteobridge. When you can wait, please modify the data stream as lined out by Brian and help yourself that way.

Multi-station feature gives tons of new options and when you want to leverage the full potential in your individual sensor/station setup situation, you will need to adapt a few things on your own. Neither me nor Brian will be able to provide the perfectly adapted solution for your specific mix and match of stations.

[jasonmfarrow]

now what you could do is simply edit the config file , simply do a backup of config file to your desktop

open your editor

find this at the bottom

xhwstemplate etc.

I get the jist of the change but where do I find the config file to edit? Is this on the NanoSD or one of the weather34 template files?

[rzelle-K1TTC]

Hi Brian,

Been busy with work and getting end of season things done around here so haven't been watching the forum until today. It looks like I have that charts issue from Sept 17th how do I fix it at this point. My site should be up to date version wise since I have been paying attention to my Github App and applying changes as I see them each day.

73s

..Ron

[weatherist34]

Hello Ron

check your email 2 csv files were sent this morning ..Brian

[weatherist34]

now what you could do is simply edit the config file , simply do a backup of config file to your desktop

open your editor

find this at the bottom

xhwstemplate etc.

I get the jist of the change but where do I find the config file to edit? Is this on the NanoSD or one of the weather34 template files?

config file is on your NANOSD . goto system tab and backup your current config file . make a duplicate and edit the duplicate.(so if goes a bit pete tong-- means wrong you have the original)..done at completely your own risk

conf.jpg (109.3 KiB) Viewed 4592 times

[jasonmfarrow]

SUCCESS!
Changing the [air1pm-act:--] and [air2pm-act:--] to [air1!1pm-act:--] and [air1!2pm-act:--] in the NanoSD configuration file did the job.

I now have my AQI data using the Davis AQI fields in the weather34 template and now airqualitydavismod.php works fine.

I just have to remember to undo the config changes, or update NanoSD firmware, when I get my real Davis Airlink.

You can now see the comparison between my UK AQI version (on the left) and the default Davis AQI version (on the right)

AQI4.PNG (55.48 KiB) Viewed 4583 times

FYI: There are different AQI scales in various global regions. https://en.wikipedia.org/wiki/Air_quality_index and the UK has a more graded but narrower scale to that of Europe or the USA even though the underlying pm2.5 and pm10 raw values are very similar. Obviously the Davis Airlink will default to the USA scale. Could a future update to the template allow regional AQI scales to be selected according to the station location in the console-settings?

[jasonmfarrow]

Brian, in weather34-airquality-mod.php you have the "purpleAir" conversion code to take the raw PM2.5 and PM10 microgramme values and and convert these to the US AQI health ranges. These ranges are then used to colour the AQI scales for the data bars.

In weather34-airquality-davis.php & weather34-airquality-davismod.php you do not have this conversion code. Thus the AQI scales 0, 50, ..., 300+ are being selected and coloured off the raw microgramme data not the US AQI health ranges. I think this also applies to the Ecowitt and Luftdaten modules as well.

Cheers.

[xray77]

Hello Brian,
I testing the new MeteoBridge native W34-Dashboard.. It runs good, but I have found two issues:
1. the WU forecast = I use exactly the same WU-API-Key as I do for my webspace-based W34-Dashboard, the forecast on the MB-Based Dashboard is still different..

2. The sunrise/sunset-times on the MB-Dashboard differs from the times on the webspace-based Dashboard. MB is configured to use the internal coordinates saved in MB, this coordinates are definitively correct. It seems so, that MB-Dashboard uses much more southerly coordinates but they can't set in the setup-screen here, so I think the MB-coordinates are used?

Bildschirmfoto 2020-09-21 um 13.54.07.png (20.01 KiB) Viewed 4562 times

Here are the correct display from web-based-Dashboard:

Bildschirmfoto 2020-09-21 um 13.22.55.png (189.1 KiB) Viewed 4569 times

and here the wrong values from MB-based Dashboard:

Bildschirmfoto 2020-09-21 um 13.22.37.png (187.94 KiB) Viewed 4569 times

The moon-phases and times are correct on both displays, so it seems so, only the latitude-set is wrong on the MB-Based Dashboard-Setup.
Is there an issue because it runs two times, first on MB and second on Web-based?
At last: in the MB-Dashboard almanac-screen the icon for graphical display are shown but it is not supported, it should be removed like the normal Dashboard-Screen..
Best regards
Mike

[weatherist34]

with internal version on nanosd it should be identical 9.34 to web version apart from internal has no chart facility. as it is the internal version this is a question for Boris perhaps open up a thread , questions does the internal version handle lat,lon differently is the UTC offset correct.?
only thing at this point i can think of is compare the settings between the two perhaps a,minor oversight of settings set .other than that i dont know the answer.

[weatherist34]

Brian, in weather34-airquality-mod.php you have the "purpleAir" conversion code to take the raw PM2.5 and PM10 microgramme values and and convert these to the US AQI health ranges. These ranges are then used to colour the AQI scales for the data bars.

In weather34-airquality-davis.php & weather34-airquality-davismod.php you do not have this conversion code. Thus the AQI scales 0, 50, ..., 300+ are being selected and coloured off the raw microgramme data not the US AQI health ranges. I think this also applies to the Ecowitt and Luftdaten modules as well.

Cheers.

jason must be a brexit thing with uk being different as before Jason i will focus on air quality when mine arrives .

[xray77]

Hello Brian,
In the internal Version no Latitude-Longitude-Settings are possible:

Bildschirmfoto 2020-09-21 um 14.22.35.png (82.32 KiB) Viewed 4559 times

In the web-Version:

Bildschirmfoto 2020-09-21 um 14.20.26.png (105.1 KiB) Viewed 4559 times

I know that you can't support the internal version but maybe Boris will read this.
I'll let the internal version run until tomorrow for testing, maybe something will change at the change of day?
Best regards
Mike

[weatherist34]

question here is where does the lat lon come from if its location ip address then could be why the difference , there are times here when im suddenly in ankara 300km away not istanbul simply the isp route has changed .i always know because i start seeing
ankara based news not istanbul related news. once again just guessing . the difference in forecast would also point to lat lon as that is based on lat lon..

[xray77]

Brian,
you are probably right, if the IP-location is taken here, there can be big differences. But it would not make sense, because the correct coordinates are actually stored in the MB. But only Boris knows that...

Edit:
I have now stopped the data feed for the internal template. The system load of MeteoBridge increases from round about 10% to round about 30%. It is a nice feature for local checking of weather data, especially if the small problems are still solved by the developer (WU forecast, sunrise/sunset data --> coordinates dependent, which seem to be set wrong in the internal template).
regards,
Mike