[weewx-user] Re: driver/wmr200.py - DEBUG_PACKETS_TEMP is never reached
On Saturday, November 10, 2018 at 1:07:05 PM UTC-8, Per Edström wrote:
>
> So it seems like this part resets the settings made at the top of the
> wmr200.py file. If DEBUG is needed then one needs to set "1" here too..
>
>
I didn't notice that previously. Cool.
But I'm not so sure. My reading is that it's showing the default mapping
if you don't set that variable in the driver section of weewx.conf at all.
I'd try setting DEBUG_WHATEVER=1 there in weewx.conf and resetting the
daemon.
To check, perhaps add a line to the following block so you can see what
_init_ is doing:
if DEBUG_CONFIG_DATA:
logdbg('Configuration setup')
logdbg(' Log sensor faults: %s' % self._sensor_stat)
logdbg(' Using PC Time: %s' % self._use_pc_time)
logdbg(' Erase archive data: %s' % self._erase_archive)
logdbg(' Archive interval: %d' % self._archive_interval)
logdbg(' Archive threshold: %d' % self._archive_threshold)
* logdbg(' DEBUG_WHATEVER: %s' % DEBUG_WHATEVER)*
or something along those lines.
--
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.
[weewx-user] Re: driver/wmr200.py - DEBUG_PACKETS_TEMP is never reached
Ok..
So it seems like this part resets the settings made at the top of the
wmr200.py file. If DEBUG is needed then one needs to set "1" here too..
*# Restart counter when driver crashes and is restarted by
the# weewx engine.global STAT_RESTARTSTAT_RESTART
+= 1if STAT_RESTART > 1:logwar(('Restart count: %d') %
STAT_RESTART)# Reset any other state during startup or after a
crash.PacketArchiveData.rain_total_last = None# Debugging
flagsglobal DEBUG_WRITESDEBUG_WRITES =
int(stn_dict.get('debug_writes', 0))global DEBUG_COMM
DEBUG_COMM = int(stn_dict.get('debug_comm', 0))global
DEBUG_CONFIG_DATADEBUG_CONFIG_DATA =
int(stn_dict.get('debug_config_data', 1))global
DEBUG_PACKETS_RAWDEBUG_PACKETS_RAW =
int(stn_dict.get('debug_packets_raw', 1))global
DEBUG_PACKETS_COOKEDDEBUG_PACKETS_COOKED =
int(stn_dict.get('debug_packets_cooked', 0))global
DEBUG_PACKETS_ARCHIVEDEBUG_PACKETS_ARCHIVE =
int(stn_dict.get('debug_packets_archive', 0))global
DEBUG_PACKETS_TEMPDEBUG_PACKETS_TEMP =
int(stn_dict.get('debug_packets_temp', 0))global
DEBUG_PACKETS_RAINDEBUG_PACKETS_RAIN =
int(stn_dict.get('debug_packets_rain', 0))global
DEBUG_PACKETS_WINDDEBUG_PACKETS_WIND =
int(stn_dict.get('debug_packets_wind', 0))global
DEBUG_PACKETS_STATUSDEBUG_PACKETS_STATUS =
int(stn_dict.get('debug_packets_status', 0))global
DEBUG_PACKETS_PRESSUREDEBUG_PACKETS_PRESSURE =
int(stn_dict.get('debug_packets_pressure', 0))global
DEBUG_CHECKSUMDEBUG_CHECKSUM = int(stn_dict.get('debug_checksum',
0))global DEBUG_MAPPINGDEBUG_MAPPING =
int(stn_dict.get('debug_mapping', 0))*
--
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.
[weewx-user] Re: Suggestion: Debug-format - sensor packet on one row instead of multiple rows
So this is no longer a suggestion about new function, it is a fault report about functions not working as it should.. -- 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.
[weewx-user] Re: driver/wmr200.py - DEBUG_PACKETS_TEMP is never reached
I change in the wmr200.py file but it doesn't have any effect on the
if-statements e.g.
*# weewx configurable flags for enabling/disabling debug verbosity.# Prints
processed packets with context from console.DEBUG_PACKETS_COOKED = 0#
Prints raw pre-processed packets from console.DEBUG_PACKETS_RAW = 1# Prints
respective packets individually.*
*:*
*def _process_packet_complete(self):"""Process a completed
packet from the wmr200 console."""#PEED#if
DEBUG_PACKETS_RAW:logdbg(self._pkt.to_string_raw('Packet
raw:'))# This will raise exception if checksum fails.
self._pkt.verify_checksum()*
--
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.
[weewx-user] Re: Suggestion: Debug-format - sensor packet on one row instead of multiple rows
Oh I have been playing around with the file now.. Apparently the DEBUG-settings in wmr200.py doesn't work. The "if DEBUG_xxx: " don't work but the DEBUG_PACKETS_RAW is what I have been looking for. I had to # the if-statement in order to make it work.. *wmr200: MainThread: D Packet raw:d7 10 24 15 0a 0b 12 40 fe 00 27 6e 00 00 1a 03* -- 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.
[weewx-user] Re: driver/wmr200.py - DEBUG_PACKETS_TEMP is never reached
On Saturday, November 10, 2018 at 10:05:27 AM UTC-8, Per Edström wrote: > > If I set: > > *DEBUG_PACKETS_TEMP = 1* > > weewx will still never enter this part of the code: > > > Where are you setting it ? It looks hard-coded to 0 at the top of wmr200.py I don't see anything obvious that reads that from weewx.conf to supersede the hard-coded values, but I might be missing where that might be done... -- 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.
[weewx-user] Re: Suggestion: Debug-format - sensor packet on one row instead of multiple rows
On Saturday, November 10, 2018 at 10:02:42 AM UTC-8, Per Edström wrote:
>
> I'm not that skilled in Python but I guess the code to adjust might be
> this:
> (wmr200.py)
>
>
>
>
>
> * if DEBUG_READS:buf = ''for
> byte in report[1:report[0] + 1]:buf += '%02x ' %
> bytelogdbg('read_device(): %s' % buf)*
>
> Maybe it doesn't loop properly before writing to syslog?
>
One of the fun things about weewx is that 'you' can make it do what you
want.
Save the existing code someplace for safekeeping and hack/play any way you
want.
Tom always appreciates pull requests to review and perhaps integrate tweaks
from the community
--
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.
[weewx-user] driver/wmr200.py - DEBUG_PACKETS_TEMP is never reached
If I set:
*DEBUG_PACKETS_TEMP = 1*
weewx will still never enter this part of the code:
*if DEBUG_PACKETS_TEMP:logdbg('peed')
logdbg(' Temperature id:%d %.1f C trend: %s' %
(sensor_id, temp, TRENDS[temp_trend]))logdbg(' Humidity id:%d
%d%% trend: %s' % (sensor_id, humidity,
TRENDS[hum_trend]))logdbg((' Dew point id:%d: %.1f C' %
(sensor_id, dew_point)))if heat_index is not
None:logdbg(' Heat id:%d index:%d' % (sensor_id,
heat_index))return record*
But if I remove the DEBUG-condition then the code is executed:
*#PEED#if DEBUG_PACKETS_TEMP:logdbg('peed')
logdbg(' Temperature id:%d %.1f C trend: %s' % (sensor_id, temp,
TRENDS[temp_trend]))# % (sensor_id, temp,
TRENDS[temp_trend]))logdbg(' Humidity id:%d %d%% trend: %s' %
(sensor_id, humidity, TRENDS[hum_trend]))# % (sensor_id,
humidity, TRENDS[hum_trend]))logdbg((' Dew point id:%d: %.1f C' %
(sensor_id, dew_point)))if heat_index is not None:
logdbg(' Heat id:%d index:%d' % (sensor_id, heat_index))return
record*
--
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.
[weewx-user] Re: Suggestion: Debug-format - sensor packet on one row instead of multiple rows
I'm not that skilled in Python but I guess the code to adjust might be this:
(wmr200.py)
* if DEBUG_READS:buf = ''for byte
in report[1:report[0] + 1]:buf += '%02x ' %
bytelogdbg('read_device(): %s' % buf)*
Maybe it doesn't loop properly before writing to syslog?
--
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.
[weewx-user] Suggestion: Debug-format - sensor packet on one row instead of multiple rows
I'm trying to find the battery status from the extra sensors on WMR200 and maybe there already a way to do this as described below.. When using the debug settings the data is written in a not too userfriendly format. One data packet is written not only over multiple rows but also with varying number of bytes per row. Like this (D7-packet from WMR200): *> Time/Date> TEMP/HUM/DEW---> CHSUM**00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15* ...byte nr*ID LL mm-hh dd-mm-yy tS TT-sT HU DD-sD HI cL-cH* ...notation*- -- -- - -- - -- -**d7 10 2f 0d 06 0c 0a 91 22 01 1b 14 80 52 8a 02* ...data *---* *Nov 10 16:17:13 RPi3B-Roses weewx[2547]: wmr200: MainThread: D Queuing live packet rx:21 live_queue_len:21Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): d7Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 10Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 11 10Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 0a 0b 12Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 52 af 00Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 47 82 00Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 00 f9 02* *Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: MainThread: D Queuing live packet rx:22 live_queue_len:22Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): d7Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 10Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 11 10Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 0aNov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 0bNov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 12 00Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): fcNov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 00Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 25Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 64Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 00Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 00 b4Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 02* *Nov 10 16:17:16 RPi3B-Roses weewx[2547]: wmr200: MainThread: D Queuing live packet rx:23 live_queue_len:23* I would find it more readable and searchable if the packets above was written in one line like this: *Nov 10 16:17:13 RPi3B-Roses weewx[2547]: wmr200: MainThread: D Queuing live packet rx:21 live_queue_len:21* *wmr200: Thread-2: D read_device():d7 10 11 10 0a 0b 12 52 af 00 47 82 00 00 f9 02 (B7:L = 2 => extraTemp2 + extraHumid2)* *Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: MainThread: D Queuing live packet rx:22 live_queue_len:22* *wmr200: Thread-2: D read_device():d7 10 11 10 0a 0b 12 00 fc 00 25 64 00 00 b4 02 (B7:L = 0 => inTemp + inHumidity)* *Nov 10 16:17:16 RPi3B-Roses weewx[2547]: wmr200: MainThread: D Queuing live packet rx:23 live_queue_len:23* It is then easy to grep on the log (for ":d7 10" and directly compare the content. -- 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.
Re: [weewx-user] Re: Negative rain-value. Need quality-control?
Personally I disagree and would rather there were NO preset values in weewx.conf!! Certainly I do not like anything that is in weewx.conf to be in US units anyway so Farenheit is out as far as I am concerned, and I prefer to use knots for wind speed. Since it is not possible to satisfy everybody my option would be to leave all of them out and let users add the ones which they wish to use - which is pretty much the way it is now. Users should read the manuals anyway before using the software, and so would discover all about the QC section!! On Saturday, 10 November 2018 15:45:49 UTC+2, Per Edström wrote: > > I would also suggest that all extra sensors are pre-added in the quality > control. If they are not used by the weather station or the user then I > guess that there is no harm done anyway. > > Oregon WMR200 can have a total of 10 sensors (where channel = 1 is the > outdoor sensor but it can be replaced with e.g. THGR-810 set on channel 1). > As we don't know where the user might place the extra sensors we might have > to extend the quality range to outdoor usage: > > [[MinMax]] > barometer = 26, 32.5, inHg > outTemp = -40, 120, degree_F > inTemp = 10, 120, degree_F > extraTemp2 = -40, 120, degree_F > extraTemp3 = -40, 120, degree_F > extraTemp4 = -40, 120, degree_F > extraTemp5 = -40, 120, degree_F > extraTemp6 = -40, 120, degree_F > extraTemp7 = -40, 120, degree_F > extraTemp8 = -40, 120, degree_F > extraTemp9 = -40, 120, degree_F > extraTemp10 = -40, 120, degree_F > outHumidity = 0, 100 > inHumidity = 0, 100 > extraHumid2 = 0, 100 > extraHumid3 = 0, 100 > extraHumid4 = 0, 100 > extraHumid5 = 0, 100 > extraHumid6 = 0, 100 > extraHumid7 = 0, 100 > extraHumid8 = 0, 100 > extraHumid9 = 0, 100 > extraHumid10 = 0, 100 > windSpeed = 0, 120, mile_per_hour > UV = 0, 6 > rain = 0, 6, inch > pressure = 24, 34.5, inHg > > -- 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.
Re: [weewx-user] Re: Negative rain-value. Need quality-control?
On Saturday, November 10, 2018 at 8:31:37 AM UTC-5, Per Edström wrote: > > Also, there is not quality control för the UV-sensor (Oregon UV ranges > 0-4). I seem to have that entry in some older weewx.conf. Not sure if I > added it myself.. > > I suggest that > > UV = 0, 6 > > is added too.. > unfortunately we cannot do that generically. different hardware has different valid ranges. for example, oregon scientific, davis, and rainwise each have a different range for valid UV values. however, it is feasible for the driver's configuration editor to inject the hardware-specific UV range when the driver is installed. the only side effect would be possible confusion if someone switches from one hardware to another, only to find that their UV values are not longer shown. pull requests welcome :) 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: Belchertown skin for weewx now available!
Many thanks for the tip. I tried it, but so far it hasn't worked; the records have the same errors as before. Do I have to wait a while to allow the records to be recalculated? I am a bit puzzled by how a change to code whose name appears to relate to charts can fix a numerical records page, but maybe there is some dependency of the records calculation that means this makes sense. On Saturday, 10 November 2018 13:30:33 UTC, WILWetter25 wrote: > > or download this file in the attachment > > Am Donnerstag, 8. November 2018 16:18:23 UTC+1 schrieb hind...@gmail.com: >> >> Yes, but from what I can see, no solution has been suggested for the >> records problem, except maybe manually adjusting the unit conversion code >> in the records python code - has anyone done that and if so what changes >> are needed? >> >> On Thursday, 8 November 2018 11:23:33 UTC, Praveen Chandrasekaran wrote: >> >> Issue already exists for this: >> >> https://github.com/poblabs/weewx-belchertown/issues/8 >> >> >> On Thu, 8 Nov 2018 at 16:11, wrote: >> >> I have been using this skin with MQTT extension for a while now, without >> any problems, and think it is excellent. However, since the initial >> installation the records page shows some very strange anomalies. See >> attached png file - which, for example, has odd max temperature range and >> rain records. Has anyone else seen similar issues and worked out how to >> solve them? Perhaps something to do with units, although other records >> such as min and max temperature are correct? I have >> >> ... > > -- 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.
[weewx-user] I need change decimal comma by decimal point
Hi, You can turn off localisation for a given tag by using the little documented .toString formatting option. Try something like (untested): $current.barometer.toString($localization=False) in lieu of $current.barometer Gary -- 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.
Re: [weewx-user] Re: Negative rain-value. Need quality-control?
I would also suggest that all extra sensors are pre-added in the quality control. If they are not used by the weather station or the user then I guess that there is no harm done anyway. Oregon WMR200 can have a total of 10 sensors (where channel = 1 is the outdoor sensor but it can be replaced with e.g. THGR-810 set on channel 1). As we don't know where the user might place the extra sensors we might have to extend the quality range to outdoor usage: [[MinMax]] barometer = 26, 32.5, inHg outTemp = -40, 120, degree_F inTemp = 10, 120, degree_F extraTemp2 = -40, 120, degree_F extraTemp3 = -40, 120, degree_F extraTemp4 = -40, 120, degree_F extraTemp5 = -40, 120, degree_F extraTemp6 = -40, 120, degree_F extraTemp7 = -40, 120, degree_F extraTemp8 = -40, 120, degree_F extraTemp9 = -40, 120, degree_F extraTemp10 = -40, 120, degree_F outHumidity = 0, 100 inHumidity = 0, 100 extraHumid2 = 0, 100 extraHumid3 = 0, 100 extraHumid4 = 0, 100 extraHumid5 = 0, 100 extraHumid6 = 0, 100 extraHumid7 = 0, 100 extraHumid8 = 0, 100 extraHumid9 = 0, 100 extraHumid10 = 0, 100 windSpeed = 0, 120, mile_per_hour UV = 0, 6 rain = 0, 6, inch pressure = 24, 34.5, inHg -- 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.
Re: [weewx-user] Re: Negative rain-value. Need quality-control?
Also, there is not quality control för the UV-sensor (Oregon UV ranges 0-4). I seem to have that entry in some older weewx.conf. Not sure if I added it myself.. I suggest that UV = 0, 6 is added too.. -- 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.
Re: [weewx-user] Re: Belchertown skin for weewx now available!
or download this file in the attachment
Am Donnerstag, 8. November 2018 16:18:23 UTC+1 schrieb hind...@gmail.com:
>
> Yes, but from what I can see, no solution has been suggested for the
> records problem, except maybe manually adjusting the unit conversion code
> in the records python code - has anyone done that and if so what changes
> are needed?
>
> On Thursday, 8 November 2018 11:23:33 UTC, Praveen Chandrasekaran wrote:
>
> Issue already exists for this:
>
> https://github.com/poblabs/weewx-belchertown/issues/8
>
>
> On Thu, 8 Nov 2018 at 16:11, wrote:
>
> I have been using this skin with MQTT extension for a while now, without
> any problems, and think it is excellent. However, since the initial
> installation the records page shows some very strange anomalies. See
> attached png file - which, for example, has odd max temperature range and
> rain records. Has anyone else seen similar issues and worked out how to
> solve them? Perhaps something to do with units, although other records
> such as min and max temperature are correct? I have
>
> ...
--
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.
#
#Copyright (c) 2016 Gary Roderick
#https://github.com/gjr80/weewx-highcharts
#
#See the file LICENSE at the URL above for your full rights.
#
#Author: Gary Roderick
#Modified by: Pat O'Brien
#Revised for the BelchertownWeather.com weewx skin
#
import calendar
import datetime
import time
import weewx
import syslog
import json
import os
import configobj
from weewx.cheetahgenerator import SearchList
from weeutil.weeutil import TimeSpan, to_int, archiveDaySpan, archiveWeekSpan, archiveMonthSpan, archiveYearSpan, startOfDay
def logmsg(level, msg):
syslog.syslog(level, 'Belchertown Highcharts Extension: %s' % msg)
def logdbg(msg):
logmsg(syslog.LOG_DEBUG, msg)
def loginf(msg):
logmsg(syslog.LOG_INFO, msg)
def logerr(msg):
logmsg(syslog.LOG_ERR, msg)
def roundNone(value, places):
"""round value to 'places' places but also permit a value of None"""
if value is not None:
try:
value = round(value, places)
except Exception, e:
value = None
return value
class highchartsDay(SearchList):
def __init__(self, generator):
SearchList.__init__(self, generator)
def get_extension_list(self, timespan, db_lookup):
# Get the skin options for the parent Belchertown skin
# Help from https://github.com/weewx/weewx/blob/master/bin/weewx/reportengine.py#L67-L182
belchertown_skin_config_path = os.path.join(
self.generator.config_dict['WEEWX_ROOT'],
self.generator.config_dict['StdReport']['SKIN_ROOT'],
self.generator.config_dict['StdReport']["Belchertown"].get('skin', 'Standard'),
'skin.conf')
belchertown_skin_dict = configobj.ConfigObj(belchertown_skin_config_path, file_error=True)
# Merge weewx.conf into skin.conf for overrides
belchertown_skin_dict.merge(self.generator.config_dict['StdReport']["Belchertown"])
# First make sure the user wants to use the extension. If not, return right away.
if belchertown_skin_dict['Extras']['highcharts_enabled'] == "0":
# Return an empty SLE
search_list_extension = { }
return [search_list_extension]
# Get our start time
_start_ts, _end_ts = archiveDaySpan( timespan.stop )
stop_struct = time.localtime( timespan.stop )
utc_offset = (calendar.timegm(stop_struct) - calendar.timegm(time.gmtime(time.mktime(stop_struct/60
# Get our temperature vector
(time_start_vt, time_stop_vt, outTemp_vt) = db_lookup().getSqlVectors(TimeSpan(_start_ts, _end_ts), 'outTemp')
outTemp_vt = self.generator.converter.convert(outTemp_vt)
usageRound = int(self.generator.skin_dict['Units']['StringFormats'].get(outTemp_vt[2], "1f")[-2])
outTempRound_vt = [roundNone(x, usageRound) for x in outTemp_vt[0]]
time_ms = [float(x) * 1000 for x in time_stop_vt[0]]
outTemp_json = json.dumps(zip(time_ms, outTempRound_vt))
# Get our dewpoint vector
(time_start_vt, time_stop_vt, dewpoint_vt) = db_lookup().getSqlVectors(TimeSpan(_start_ts, _end_ts), 'dewpoint')
dewpoint_vt = self.generator.converter.convert(dewpoint_vt)
usageRound = int(self.generator.skin_dict['Units']['StringFormats'].get(dewpoint_vt[2], "1f")[-2])
dewpointRound_vt = [roundNone(x, usageRound) for x in dewpoint_vt[0]]
time_ms = [float(x) * 1000 for x in time_stop_vt[0]]
dewpoint_json = json.dumps(zip(time_ms, dewpointRound_vt))
# Get our wind
Re: [weewx-user] Re: Belchertown skin for weewx now available!
1. Go to this Link: https://github.com/poblabs/weewx-belchertown/blob/master/bin/user/belchertown_highchartsSearchX.py 2. download this file 3. go to /usr/share/weewx/user/ 4. replace the old file with the new 5. restart weewx this worked for me :) Am Donnerstag, 8. November 2018 16:18:23 UTC+1 schrieb hind...@gmail.com: > > Yes, but from what I can see, no solution has been suggested for the > records problem, except maybe manually adjusting the unit conversion code > in the records python code - has anyone done that and if so what changes > are needed? > > On Thursday, 8 November 2018 11:23:33 UTC, Praveen Chandrasekaran wrote: > > Issue already exists for this: > > https://github.com/poblabs/weewx-belchertown/issues/8 > > > On Thu, 8 Nov 2018 at 16:11, wrote: > > I have been using this skin with MQTT extension for a while now, without > any problems, and think it is excellent. However, since the initial > installation the records page shows some very strange anomalies. See > attached png file - which, for example, has odd max temperature range and > rain records. Has anyone else seen similar issues and worked out how to > solve them? Perhaps something to do with units, although other records > such as min and max temperature are correct? I have > > ... -- 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.
Re: [weewx-user] I need change decimal comma by decimal point
Vlad Mastenitsa writes: > I need change decimal comma by decimal point values in weewx Standard > Reports. > The file, wich create from template is processing as JSON, and I get error > processing. > json_decode() uncorrect split values by comma. It seems to me that json is a data representation, and that values in it should not be localized. How did you get pressure as '1014,1 mbar' in json, and why? Certainly converting standard-form data to a user's display locale is sensible, and that seems more tractable. But perhaps I do not understand the grand plan. -- 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.
[weewx-user] I need change decimal comma by decimal point
I need change decimal comma by decimal point values in weewx Standard
Reports.
The file, wich create from template is processing as JSON, and I get error
processing.
json_decode() uncorrect split values by comma.
in tmpl I have:
"obs":[{"timestamp":"$current.dateTime",
"air_temperature":'$current.outTemp',
"barometric_pressure":'$current.barometer',
in json file I have:
"obs":[{"timestamp":"10.11.2018 15:00:00",
"air_temperature":'1,3ТАC',
"barometric_pressure":'1014,1 mbar'
after json decode I have:
obs => { timestamp=>"10.11.2018 15:00:00",
air_temperature=>1,
3TAC=>null,
barometric_pressure=>1014,
1=> "mbar"
}
Please help!
--
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.
[weewx-user] Re: Transmitter ID
Hallo Gir 80 Danke fü die Info, ich werde das in den nächsten tagen mal Testen. cu. kalli Am Sonntag, 4. November 2018 10:58:18 UTC+1 schrieb Kalli: > > Hallo > > gibt es eine möglichkeit , das man sich die Transmitter IDs anzeigen > lassen kann . > > Ich möchte gerne sehen ob die sich ändern. > > cu. kalli > -- 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.
