Hi Brent, The issue you have is not one of units I suspect but rather appTemp is not being stored in the database. By default weewx calculates appTemp and adds it to the archive record and loop packets received from the weather station (if it does not already exist - I don't know of any stations that supply it). Once weewx has an archive record (which now has appTemp in it) weewx stores the archive record in the archive table and updates the daily summaries. The problem is weewx only saves data for those fields in the database schema; appTemp is not in the default schema so it is not saved. Since appTemp is not in the database you cannot plot it nor can you use it in any tags in reports (eg $day.appTemp.max - when the next version of weewx is released you will be able to use $current.appTemp but nothing else). To be able to make use of appTemp in plots and reports you need to add it to the database schema.
The Customization Guide <http://weewx.com/docs/customizing.htm> has a section on this Adding a new observation type <http://weewx.com/docs/customizing.htm#Adding_a_new_observation_type>. It is a good place to start, note that you do not need to worry about 'Creating a custom service', that is just to get your data into the archive record - appTemp is already there. So you can start at Adding a new type to the archive database <http://weewx.com/docs/customizing.htm#add_archive_type>. Seems overly complex, I know, for something that is already there but I guess there are some historical reasons why it is like this. Probably will find though that this sort of thing will be a lot easier in the future. Gary On Monday, 28 November 2016 13:10:14 UTC+10, Brent Wesley wrote: > > Hi Everyone > > I have a brand new weewx site built around the Responsive skin with the > interceptor driver collecting data from a Oregon Scientific setup. Weewx is > configure with the target_unit set to Metric and the database configured to > do so. > > The site is working well ( http://weather.gotgeeks.com:8080/ ) except the > appTemp information. I am not getting back a metric value sent to and from > the calculation. > > 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 > > 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. Also I don't see > anywhere in the database schema (sqlite) that any appTemp values are being > stored. > > From my understanding that as of version 3.5 this is meant to be done. > > 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. > > Is there a step I have missed in the set up regarding the setup? I have > tried to read as much posts and documentation as I can but still not > getting anywhere. > > Please help. > TIA > Brent > -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
