:) True I sent an email to Dark Sky about the accuracy of their data for my area, where does the cloud base info the skin picks up?
On Monday, 28 January 2019 16:27:13 UTC+3, Pat wrote: > > That comes from the DarkSky forecasting (which is updated every > forecast_stale > <https://github.com/poblabs/weewx-belchertown#forecast-options> interval > - about 1 hour). So they may not be as up to date as your pilot friend is :) > > On Monday, January 28, 2019 at 8:25:33 AM UTC-5, Adnan Mumtaz wrote: >> >> Thanks a lot Pat i will try it, one more thing we have heavy winds with >> dust and low visibility but the skin is showing me 9km visibility where as >> aviation weather shows only 585 meters. I sent it a friend who is a pilot >> and he pointed out, he is in cockpit right now taxiing and giving me >> feedbacks :) >> >> On Monday, 28 January 2019 16:22:19 UTC+3, Pat wrote: >>> >>> To be clear, there's 2 things that are going on and I want to try to >>> make sure we're on the same page. >>> >>> When the page initially loads, that's from weewx's core. So the metric >>> settings come from the skin settings. >>> >>> Once MQTT is connected, then that data comes from the weewx-mqtt >>> extension. This extension has the ability to be calibrated individually for >>> metric/imperial, etc. >>> >>> If the issue is when MQTT updates the page, perhaps you need to set the >>> MQTT extension's units to send. >>> >>> Take a look at this post >>> <https://github.com/poblabs/weewx-belchertown/issues/23#issuecomment-440529099>. >>> >>> Under MQTT extension's settings, you can define which unit to send for >>> which observation. Again, I did not write the MQTT extension, but this >>> should be able to help you. >>> >>> [[MQTT]] >>> **snip** >>> [[[inputs]]] >>> [[[[rainRate]]]] >>> name = rainRate_mm_per_hour >>> units = mm_per_hour >>> >>> >>> >>> >>> >>> On Monday, January 28, 2019 at 3:35:53 AM UTC-5, Adnan Mumtaz wrote: >>>> >>>> Hi my cloud base shows in meters as I have group_altitude = meter , >>>> but when I change it to foot the skin calculates fine but when MQTT >>>> updates >>>> the data it changes to meter readings, MQTT setting is also set as METRIC. >>>> I see yours in feet too. >>>> >>>> On Tuesday, 1 January 2019 15:50:49 UTC+3, Pat wrote: >>>>> >>>>> I've just released version 0.8.2 of the Belchertown skin which fixes >>>>> the New Year bug some of you are seeing. It also adds some other >>>>> features. >>>>> >>>>> >>>>> Download and install instructions here: >>>>> https://github.com/poblabs/weewx-belchertown/releases >>>>> >>>>> >>>>> * Fixed an error where the skin would fail when the date rolls to the >>>>> New Year due to no data being in certain tables in the database yet. >>>>> * Added the ability to show any weather alerts provided by the DarkSky >>>>> API. Weather alerts are off by default, use forecast_alert_enabled in >>>>> weewx.conf skin options to enable it. >>>>> * New option to show cloudbase. You must have your database schema >>>>> extended for the cloudbase observation to be calculated by weewx. Check >>>>> the >>>>> Belchertown skin wiki for details. >>>>> * Fixes an issue where the MQTT updates showed altimeter instead of >>>>> barometer. >>>>> * Updated Google Analytics page to be in header based on Google >>>>> recommendations. >>>>> * Updated Google Analytics to a more recent script block. >>>>> * Added a Google Analytics page view per MQTT update as per Google >>>>> Recommendations on background updates. >>>>> >>>>> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
