Maybe. I'm not quite sure how to handle this one. Your MQTT published message may have both barometer_inHg as well as altimeter_inHg - or even other pressure values.
For example my station it's the altimeter_inHg that matches my console. I almost wonder if this needs to be a variable on which one to show? On Monday, September 24, 2018 at 9:15:51 AM UTC-4, [email protected] wrote: > > Hi I changed this in the index.html template file. should this be included > in the next release? Should fix the metric code also. > > if ( data.hasOwnProperty("altimeter_inHg") ) { > jQuery(".wx-barometer-value").text( parseFloat( data["barometer_inHg"] > ).toFixed(2) + " $unit.label.pressure" ); > // Barometer US > > > On Monday, September 24, 2018 at 7:23:13 AM UTC-4, [email protected] > wrote: >> >> Hi All, >> >> I have installed the Belchertown skin and have the real time updates >> working but I have notices the pressure reading on the static page is the >> barometer_inHg and the MQTT uses the altimeter_inHg. When the pages loads >> I see the altitude adjusted pressure then it drops to the altimeter >> pressure when the real time updates start coming in. My station, an old >> WM-918, send both pressures to weewx and I want to keep the barometer_in >> displayed. >> >> I see in the web page source code that the MQTT updates are coded for the >> altimeter pressure. I am also running mosquito on my own PC and can >> subscribes to the feed and see it posting both altimeter and barometer. >> >> My page is on my internal network at the moment and cannot be accessed >> outside my house. >> >> How can this be fixed? >> >> Matt >> > -- 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.
