Weather34 TEMPLATE

[Lespius]

Hi,

I have noticed something strange about the dewpoint:

Weather34 --> 8.5°


Meteobridge --> 7.7°


Meteotemplate, which uses Meteobridge as well --> 7.9°(it moved to 7.9 from 7.7 during the captures of the images)


Conclusion: Weather34 does report the dewpoint, but something else. I have even noticed recently that the dewpoint was higher that the temperature !
Weird, isn't it?

[xray77]

Brian,
The cronjob service is now up and running: no change. The file "luftdaten.txt" on the server is still empty.
What else can it be? Should I perhaps run the complete installation? Something seems to be missing in template...

regards,
Mike

[weatherist34]

now check file permission on that file you created..

[xray77]

Brian,
have set it to "777", no change after a run of stationcron.. "luftdaten.txt" with 0 Bytes..
the cron works, updated the WU-forecast but not the luftdaten.txt.

[weatherist34]

Hi,

I have noticed something strange about the dewpoint:

Weather34 --> 8.5°


Meteobridge --> 7.7°


Meteotemplate, which uses Meteobridge as well --> 7.9°(it moved to 7.9 from 7.7 during the captures of the images)


Conclusion: Weather34 does report the dewpoint, but something else. I have even noticed recently that the dewpoint was higher that the temperature !
Weird, isn't it?

weird it is but i’ll emphasize once again template only reads and displays what is stored in the api file it does NOT use any formula for dewpoint has meteobridge provides that data. only time i ever saw a dewpoint higher than temperature was way back 2018 with a weatherflow air unit that would go above 100% humidity causing a weird dewpoint and for whatever reason would frequently go
higher than 100% humidity , it wasnt a template issue or meteobridge simply poorly designed sensor data output from weatherflow which they eventually resolved.but it was all too easy to point at template but the reality there is nothing in the template to create this scenario..

[weatherist34]

Brian,
have set it to "777", no change after a run of stationcron.. "luftdaten.txt" with 0 Bytes..
the cron works, updated the WU-forecast but not the luftdaten.txt.

please send template password via pm you can change at anytime

[weatherist34]

mike I am at a complete loss

if do this https://data.sensor.community/airrohr/v1/sensor/50525/

I get your data returned ok
[{"sensor":{"pin":"1","id":50525,"sensor_type":{"manufacturer":"Nova Fitness","id":14,"name":"SDS011"}},"id":2187121194,"sensordatavalues":[{"value_type":"P1","id":4723112626,"value":"2.80"},{"value_type":"P2","id":4723112629,"value":"1.53"}],"location":{"country":"DE","indoor":0,"exact_location":1,"id":36474,"longitude":"9.66316223145","latitude":"54.32018412738","altitude":"13.2"},"timestamp":"2020-10-10 12:05:29","sampling_rate":null}]

if I run your ID 50525 in my demo here it returns the correct data as seen in above and stored in the file luftdaten.txt

[{"sensor":{"pin":"1","id":50525,"sensor_type":{"manufacturer":"Nova Fitness","id":14,"name":"SDS011"}},"id":2187121194,"sensordatavalues":[{"value_type":"P1","id":4723112626,"value":"2.80"},{"value_type":"P2","id":4723112629,"value":"1.53"}],"location":{"country":"DE","indoor":0,"exact_location":1,"id":36474,"longitude":"9.66316223145","latitude":"54.32018412738","altitude":"13.2"},"timestamp":"2020-10-10 12:05:29","sampling_rate":null}]

if I run the same through your website it creates a blank file which indicates something amiss with either out of date stationcron.php or file refuses to be written to .

so here is what ill do an update the simple update file will be called FORMIKE.zip in a moment for you to run and install no need to run a new full install.
just run it as you would a normal update .then simply let me know when you have run it.

ill pm the download link to FORMIKE.zip

IF THIS FAILS im at a total loss because I simply unable to replicate it locally

give

[weatherist34]

have a good day mike that worked as your air quality just updated ... now lets all go and have a nice weekend...take care Brian ..

[xray77]

Brian,
it works!!
Thank you very much for your support! I am very happy! I wish you also a nice weekend!
Best regards
Mike

[weatherist34]

rica ederim ...your welcome.. over the next few weeks you will have chart data but i cant promise a date but it will appear in due course once ive set up,davis airlink properly in a proper diy shield with a sealed power inlet..at the mo its on the balcony near a combi boiler outlet which aint much use as its on and off all day .. the charts will be compatible with luftdaten,purple air,davis, mb assigned and will have there own chart page to keep it contained within design ..so something to look forward too over the coming weeks or months..

[xray77]

Brian,
That sounds good! Will certainly be a nice thing with the charts for the AQ,
Have a nice weekend (here it's raining "Cats & Dogs") and stay healthy,
regards
Mike

[xray77]

Hello Brian,
I'm just playing around with the AQ modules. I have added the NOVA SDS11 - sensor to my MeteoBridge via plugin and the MB also outputs the values in the API for the template:

12/10/2020 12:28:02 11.1 88.0 9.2 1.4 0.4 193.0 0.0 0.2 1016.5 191.0 1 m/s C hPa mm 1.5 1016.8 57.4 646.2 3.4 22.4 47.0 11.1 9.7 11.8 20201012121242 2.1 20201012081948 1.4 20201012103106 4.0 20201012122104 1017.0 20201012090608 1016.1 20201012000009 4.4 3467 4.0 VOCORE2 -- 0.9 0.2 130.0 199.0 0.0 14.4 20201003203722 1.7 20201012081948 10.2 20201011144843 20.7 20200810132336 -13.0 20200329175211 2.2 98.0 20201012091520 86.0 20201012121534 10.1 20201012121148 1.7 20201012081948 11.8 89.0 10.0 22.3 47 1.4 1.3 -- -- -- -- -- -- 606.0 222496 13.6 20201011155043 5.6 20201011072814 18.5 20201001135925 2.1 20201012081948 31.8 20200816145445 -3.2 20200314061716 9.9 20201011034508 15.4 20201004111902 23.3 20200312064428 3.4 57.4 20201001000001 646.2 20200108210000 606.0 20201012120720 642.0 20201011135358 703.0 20201007135739 1281.0 20200715133911 20201012121006 1.8 20201011131126 2.4 20201009124205 6.0 20200703135441 5.0 20201011072814 0 10.6 20201012060028 31.8 20200816145445 -3.2 20200314061716 20.7 20200810132336 -13.0 20200329175211 23.3 20200312064428 1016.1 20201011232408 1012.2 20201011143808 1017.0 20201012090608 989.9 20201003225410 1044.7 20200120101900 975.8 20200210014000 1044.7 20200120101900 975.8 20200210014000 646.2 4.4 7 25.4 10:45 00:54 17:27 0.2 98.0 20201012091520 65.0 20201004112904 99.0 20200109063800 25.0 20200325144757 97.0 20201011075308 70.0 20201011155402 0.0 0.0 33.2 -- 2.2 11.2 1016.5 0.8 1.3 -- 1.3 2.2 87.4 11.3 2.8 20200101001400 20200101000000 279.0 3 0 185.0 33.1 20200811144358 -6.5 20200323073950 _Increasing clouds with little temperature change. Precipitation possible within 24 to 48 hours.
i think, the bold values are the PM25 and PM10-Values?

Furthermore I have shown the AQ module for MeteoBridge (right in the screenshot) and left of it the Davis AQ module, which gets its values from the API values at the same place, right?

Bildschirmfoto 2020-10-12 um 12.28.18.png (83.2 KiB) Viewed 3865 times

Nevertheless both modules show significantly different AQ values, how is that possible? Or is the Davis module really only compatible with the values of a Davis Airlink which report also the PM1-Value? It seems so, the Davis-Module reports here only the PM25-Value, no AQI-Calculations?

Which would be the more correct one for me, probably the AQ-Meteobridge module, or? As I said, it's just a little gimmick to display both modules but it would be interesting to know why the values are different... Many thanks for your explanation, it isn't a issue-report from me, only interested..
Best regards
Michael

[weatherist34]

sorry but i dont know anymore fed up with all this aqi stuff its very confusing..sorry i have no idea , too many different end user configurations , requests for different scales going to get or becoming difficult to get any sense of a common useage.. in short davis outputs pm 1,2.5 ,10 in raw the davis modules does not convert to AQI simply because i have requests for so many different regional scaling its impossible to make anything reliable. so I gave up , i have had numerous emails over the last week or so for aqi and not one of them from each individual uses the same method , its tough enough dealing with metric vs non metric vs kts,ms,kmh,mph now aqi regional , country differences ..so back to basics luftdaten or purple air choice in next version never had these scenarios when they were the only choices and data came from there API ..sorry i sound non enthusiastic but i cant find a happy medium for all scenarios its too much work and guessing .. i have my davis airlink setup it simply works as i expected but im not adding my nova sensor into the equation just keeping it simple so i can use it for what i bought it for to monitor relative air quality not to sit there compare one against the other continuously.. seriously i would look at wim van de kuil offering it may be what your looking for in terms multiple data from numerous sensors.. give it a try https://pwsdashboard.com/ it might be what your looking for..brian all this multiple assigned sensor use has gone beyond me..brian

[woolfg]

Hi Brian

I agree -it must be an absolute nightmare with all the different air quality sensors around

However there does seem to be one common standard that is used worldwide and maybe you could adapt this

This is shown in the attached

airquality.jpg (32.34 KiB) Viewed 3847 times

If you just output the 2.5 and 10 values in your module as you do now with the bars so now have two bars - or if you made the module the same size as the UV module you could include the 1.0p.m and have 3 bars

then base the AQ Index on the combination of values of 2.5 and 10 and where you have the large numbers in your module just display the AQ index ie GOOD -MODERATE -UNHEATHY etc based on attached

Regards

Graham

[RABrand]

Brian,

I thought I would also comment on the AQI issue, now that it is working perfectly on my site.....

The additional modules you added which use Meteobridge API slot 175 shouldn't be an issue.

The modules work fine, and show the proper values for AQI, using the particle count supplied by the Ecowitt sensor.

I would like to see the support for slot 175 retained (it IS labeled Ecowitt in the API listing), since it will ALWAYS be PM2.5.

I agree with woolfg (the previous post) that the chart shown is the most widely accepted particle count to AQI mapping. (This is the same mapping used in the Meteobridge modules which are working).

Just my opinion and thoughts, but now that it works properly, I would really hate to see it go away!!

Thanks for listening....

Ron B.

https://hillsdale-98404.com