hi brent, happy to hear that the interceptor is working for you. does your lw30x report pressure regularly?
see below for responses to your enquiries... On Sunday, November 27, 2016 at 10:10:14 PM UTC-5, Brent Wesley wrote: > > I have dug in to the code and can see the call from the wxservices.py to > calculate the value and even put some code in to print the outTemp, > outHumidity and winSpeed values to the syslog. > > For example: > Nov 28 03:00:33 ip-172-31-29-42 weewx[8599]: outTemp 84.47 > Nov 28 03:00:33 ip-172-31-29-42 weewx[8599]: outHumidity 41.5 > Nov 28 03:00:33 ip-172-31-29-42 weewx[8599]: windSpeed 8.61224753558 > Nov 28 03:00:33 ip-172-31-29-42 weewx[8599]: appTemp 82.3462555515 > the unit system for the values you posted is US, as expected. this is because the StdWXCalculate service converts everything to US to do its calculations. > It is my understanding that if the system, database and data coming back > from the sensors is in metric values, it should be stored in the database > as a metric value and all calculations are metric. > units and unit systems are all over the place, but weewx has mechanisms to make sense of it all. some hardware does METRIC, others do US, many do a mix of US and METRIC. the driver is responsible for ensuring that the readings it reports are in a single unit system. any service that operates on LOOP or REC data must ensure that it returns results in the unit system of the LOOP or REC dict that it received. the StdArchive service saves to database in the unit system you specified in weewx.conf. > Also I don't see anywhere in the database schema (sqlite) that any appTemp > values are being stored. > appTemp is not in the default (wview) schema, so you should see appTemp in LOOP and REC, but it will not be saved to database until you add an appTemp column to your database. > From my understanding that as of version 3.5 this is meant to be done. > tom recently made it so that you can use $current to access every observation, not just those in the database schema. this change was made after 3.6.2 and has not yet been released. > When I try and use the $current.appTemp value in the skin template it is > not able to get a value, probably because the value it being bounds checked > as being and invalid temperate for degrees_C. > the easiest fix would be to add an appTemp column to your database, then rebuild the dailies, something like this: sudo /etc/init.d/weex stop sudo sqlite3 /var/lib/weewx.sdb sqlite3> alter table archive add appTemp REAL; sudo wee_database --drop-daily sudo /etc/init.d/weewx start please see the customization guide for details about modifying the database schema. another option would be to pull from the repository and do a setup.py install to try the $current fix. m -- 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.
