[weewx-user] Re: unable to get data from weather station lw30* (oregon weather anywhere)

[Andrew Milner]

The log seems to show it is listening on port 80 but you seem to have 
specified port 8080.  Try and change the port in .conf to 80

On Monday, 3 December 2018 21:25:43 UTC+2, G Dupuis 89 wrote:
>
> Hi,
> I am new with weewx: it is installed on a Raspberry pi and my oregon lw30x 
> is connected to my LAN (ip of lw30x: 192168.1.19), 
> i am not able to get data from it, i have the following messages in Syslog 
> when running "weewxd /etc/weewx/weewx.conf" 
>
> root@raspberrypi:/etc/weewx# weewxd /etc/weewx/weewx.conf
> root@raspberrypi:/etc/weewx# tail -f /var/log/syslog
> Dec  3 20:22:11 raspberrypi weewx[3558]: engine: Initializing engine
> Dec  3 20:22:11 raspberrypi weewx[3558]: engine: Loading station type 
> Interceptor (user.interceptor)
> Dec  3 20:22:11 raspberrypi weewx[3558]: interceptor: MainThread: driver 
> version is 0.41
> Dec  3 20:22:11 raspberrypi weewx[3558]: interceptor: MainThread: device 
> type: lw30x
> Dec  3 20:22:11 raspberrypi weewx[3558]: interceptor: MainThread: sensor 
> map: {'inTemp': 'ot.2:*.*', 'outTemp': 'ot.1:*.*'}
> Dec  3 20:22:11 raspberrypi weewx[3558]: interceptor: MainThread: mode is 
> listen
> Dec  3 20:22:11 raspberrypi weewx[3558]: interceptor: MainThread: listen 
> on 192.168.1.19:80
> Dec  3 20:22:11 raspberrypi weewx[3558]: import of driver failed: [Errno 
> 99] Cannot assign requested address ()
> Dec  3 20:22:11 raspberrypi weewx[3558]: engine: Unable to load driver: 
> [Errno 99] Cannot assign requested address
> Dec  3 20:22:11 raspberrypi weewx[3558]:   Exiting…
>
> apache web server is stopped
>
> currently, the weewx.conf contents:
> station_type = Interceptor
> ….
> driver = user.interceptor
> # Specify the hardware device to capture.  Options include:
> #   acurite-bridge - acurite internet bridge
> #   observer - fine offset WH2600/HP1000/HP1003, aka 'observer'
> #   lw30x - oregon scientific LW301/LW302
> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
> device_type = lw30x
> address = 192.168.1.19
> port=8080
> [[sensor_map]]
> inTemp = ot.2:*.*# sensor on channel 2
> outTemp = ot.1:*.*# sensor on channel 1
>
> not sure that i have to redirect trafic from the weather station to the 
> Raspberry ? and how ?
> or the config file is not complete ?
>
> thanks in advance,
>

-- 
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: weewx abends with no reason

[vk3anz]

I'm not sure what procedure you are talking about with the 'historic' 
values.

As far as the HP1000 driver is concerned, it looks at the last date in the 
weewx database and then queries the weather station for any records it has 
for after that date. Therefore it typically only downloads historic data 
since the last time the driver talked to the weather station (often hours 
or perhaps a day or two).

Even when I was testing it out (about a year ago), I managed to download 
all of the data from the weather station back to about September 2016. I 
know that this is the "my light bulb works; don't know why yours is broken" 
defence but I do know that it *can* work.

Also, does the weewx database hold the historic data for you? You might not 
be able to push that back to the weather station but does that really 
matter?

Susan

On Monday, December 3, 2018 at 9:54:07 PM UTC+11, Gary Hopkins wrote:
>
> OK Update.
>
> I did get the new Pi but I've not installed it with weewx.
>
> I was "fiddling" with the historic values on the WS and I went to delete 
> all the 2017 ones. Instead I accidentally deleted the 2018 ones so by then 
> it was too late.
>
> Once I'd gone back and deleted all the 2017 entries and there was no 
> longer any historical data to download everything is working fine and has 
> been since Saturday.
>
> I suspect that there is something "wrong" with pulling down the historical 
> data that was causing something to fail. Downloading "live" data and 
> running all the reporting scripts is working without a hitch. I'll just 
> live with the fact that I've lost all my historic data on the WS. 
>
> Thanks again for all your suggestions and 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.

Re: [weewx-user] Re: Fine Offset WH-2650 and weewx

[steeple ian]

Hi Massimiliano and Tanwe,

I have got it working by replicating the OrangePi hotspot set up on a 
RasberryPi. I am letting it stabilise for a few days before I transfer the 
hotspot setup to my public facing server. I will post a link when it is up and 
running.

Thanks for all your help. Would never had made this far so quickly without your 
help.

Cheers,
Ian

> On 2 Dec 2018, at 18:31, Massimiliano Neri  wrote:
> 
> Yes, yes, I chose to do a HotSpot with my Orangepi Pi Zero H2.
> As an operating system I chose Armbian Bionic mainline kernel 4.14.y, which 
> can be found at this link:
> https://www.armbian.com/orange-pi-zero/
> 
> I have done this procedure to install the weewx and the driver interceptor:
> 1) Launched on the command line "armbian-config", set the time zone, the 
> keyboard and the language, find all this under the heading 'Personal'.
> 2) return to the main menu and go to "Network", select 'IP' and assign a 
> static address to the network card eth0 (mine is 192.168.10.66) save and run 
> on reboot.
> 3) restart "armbian-config", go to 'System' and install the beta version 
> packages with the voice 'Nightly', then restart.
> 4) run the command line command 'apt-get update' and 'apt-get upgrade'.
> 5) run on the command line "armbian-config", go to 'Network' and activate 
> your access point with the 'HotSpot' entry.
> 6) install weewx from the documentation found on the program website: 
> http://www.weewx.com/
> 7) install the extension for weewx "interceptor" following the indications 
> you find on this link: https://github.com/matthewwall/weewx-interceptor
> 8) Connect your smartphone with the Orange Pi access point (your case with 
> the Raspberry), install the "WS View" app that you find in the google app 
> store, open the app itself and with this colleague the WH-2650 weather 
> station bridge to the access point of the used device.
> Check that the station emits on your wunderground account that you should 
> have created and always configured with the same with "WS View".
> Before moving on with "Ws View", you need to calibrate the sensors of the 
> station or make the setting operations you believe.
> 9) Now at the command line of Orange Pi Zero, type: "iptables -t nat -A 
> PREROUTING -s 172.24.1.65 -p tcp --dport 80 -j DNAT --to-destination 
> 192.168.10.66:666", where 172.24.1.65 is the ip of the station bridge and 
> 192.168.10.66 is the ip of the Orange Pi eth0 network card. the final door 
> 666 you could choose it as you want, as long as it is not occupied.
> Clearly you have to replace the example ip with your ip that you will soon 
> have discovered with a program of scanning the ports (there are also for 
> smartphones, and I suggest you install one from google play).
> Save the configuration of this iptables with the command:
> iptables-save> /etc/iptables/iptables.ipv4.nat
> This last one is used to load the typed iptables every time, every time the 
> Orange is turned on.
> To verify that the iptables command has been loaded, type:
> iptables -t nat -L --line-numbers
> This displays all the iptables of your card, and you should also find the one 
> that directs your weather bridge on the eth0.
> 10) open the weewx.conf file at the command line by typing:
> nano /etc/weewx/weewx.conf
> Scroll to the end of the file and set the [Interceptor] section with these 
> lines:
> 
> [Interceptor] 
> driver = user.interceptor
> device_type = observer
> port = 666
> 
> The [[Wunderground]] section should be set up with your account:
> 
> [[Wunderground]]
> # This section is for configuring posts to the weather
> Underground.
> # If you wish to do this, set the option 'enable' to true,
> # and specify a station (e.g., 'KORHOODR3') and
> password.
> # To guard against parsing errors, put the password into
>quotes.
>   enable = true
>   station = XXX
>   password = YYY
> 
> Save the edited file with CTRL + O.
> 
> 11) Restart weewx with the command:
> /etc/init.d/weewx restart
> 
> If the Raspberry is the same as my Orange Pi Zero, you should see the WH-2650 
> data on wunderground and weewx.
> 
> Greetings from the MAX.
> 
> Il giorno venerdì 23 novembre 2018 00:11:49 UTC+1, Massimiliano Neri ha 
> scritto:
> Hi, I just bought a WaldBeck Halley WH-2650, basically a clone of the WH-2650 
> Fine Offset, can you tell me how to configure weewx.conf to intercept its 
> data string?
> 
> I thank you in advance.
> 
> -- 
> 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 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To 

[weewx-user] Re: Belchertown skin for weewx now available!

[Pat]

Preference is to have all options in weewx.conf under the Belchertown 
Extras section 
. 
Then (as I understand it), weewx joins skin.conf and the weewx.conf Extras 
together with weewx.conf as a priority. 

My suggestion is to put skin.conf back to the original state and then move 
your options into weewx, and then restart weewx. 

On Monday, December 3, 2018 at 5:59:07 PM UTC-5, Gary Hopkins wrote:
>
> Hi Pat,
>
> Which file takes priority, weewx.conf or skin.conf? By that I mean if you 
> have something set to 1 in skin.conf and something set to 0 in weewx.conf 
> which wins?
>
> Or
>
> Am I right in thinking skin.conf gets parsed every single run but 
> weewx.conf only gets parsed when you re-start weewx? I ask because I'm 
> scratching my head why certain changes are not picked up all the time.
>
> Thanks
>
> 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.

[weewx-user] Re: Belchertown skin for weewx now available!

[Gary Hopkins]

Hi Pat,

Which file takes priority, weewx.conf or skin.conf? By that I mean if you 
have something set to 1 in skin.conf and something set to 0 in weewx.conf 
which wins?

Or

Am I right in thinking skin.conf gets parsed every single run but 
weewx.conf only gets parsed when you re-start weewx? I ask because I'm 
scratching my head why certain changes are not picked up all the time.

Thanks

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: Extra temperature sensor / New weather station?

[ponolan]

Thanks for the link. It's not accessible in the EU; will check with a VPN 
later. 

Would you recommend something different if I had wi-fi or Ethernet in place?

-- 
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] unable to get data from weather station lw30* (oregon weather anywhere)

[G Dupuis 89]

Hi,
I am new with weewx: it is installed on a Raspberry pi and my oregon lw30x 
is connected to my LAN (ip of lw30x: 192168.1.19), 
i am not able to get data from it, i have the following messages in Syslog 
when running "weewxd /etc/weewx/weewx.conf" 

root@raspberrypi:/etc/weewx# weewxd /etc/weewx/weewx.conf
root@raspberrypi:/etc/weewx# tail -f /var/log/syslog
Dec  3 20:22:11 raspberrypi weewx[3558]: engine: Initializing engine
Dec  3 20:22:11 raspberrypi weewx[3558]: engine: Loading station type 
Interceptor (user.interceptor)
Dec  3 20:22:11 raspberrypi weewx[3558]: interceptor: MainThread: driver 
version is 0.41
Dec  3 20:22:11 raspberrypi weewx[3558]: interceptor: MainThread: device 
type: lw30x
Dec  3 20:22:11 raspberrypi weewx[3558]: interceptor: MainThread: sensor 
map: {'inTemp': 'ot.2:*.*', 'outTemp': 'ot.1:*.*'}
Dec  3 20:22:11 raspberrypi weewx[3558]: interceptor: MainThread: mode is 
listen
Dec  3 20:22:11 raspberrypi weewx[3558]: interceptor: MainThread: listen on 
192.168.1.19:80
Dec  3 20:22:11 raspberrypi weewx[3558]: import of driver failed: [Errno 
99] Cannot assign requested address ()
Dec  3 20:22:11 raspberrypi weewx[3558]: engine: Unable to load driver: 
[Errno 99] Cannot assign requested address
Dec  3 20:22:11 raspberrypi weewx[3558]:   Exiting…

apache web server is stopped

currently, the weewx.conf contents:
station_type = Interceptor
….
driver = user.interceptor
# Specify the hardware device to capture.  Options include:
#   acurite-bridge - acurite internet bridge
#   observer - fine offset WH2600/HP1000/HP1003, aka 'observer'
#   lw30x - oregon scientific LW301/LW302
#   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
device_type = lw30x
address = 192.168.1.19
port=8080
[[sensor_map]]
inTemp = ot.2:*.*# sensor on channel 2
outTemp = ot.1:*.*# sensor on channel 1

not sure that i have to redirect trafic from the weather station to the 
Raspberry ? and how ?
or the config file is not complete ?

thanks in advance,

-- 
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: Belchertown skin for weewx now available!

[Pat]

Agree on the 24 hour format - not sure why I never thought of it! I'll add 
it as a skin option in a future release


On Monday, December 3, 2018 at 2:18:53 PM UTC-5, Jan wrote:
>
>
> 1. To disable the UV/solar radiation, you can change the plot for chart 6 
>> . 
>> Maybe you can do humidityplot instead. 
>>
>
> That's easy, already done and updated! Thanks for the hint and your rapid 
> reply... 
>
> 2. This is the first request for 24 hour format and I haven't thought of 
>> testing that! I will look into this. 
>>
>
> Standard in Germany and some other European countries! ;-)
> Would be a good idea to add something like that in a future update. Right 
> now, I would rate that a cosmetic option. 
>

-- 
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: Belchertown skin for weewx now available!

[stellingorama]

> 1. To disable the UV/solar radiation, you can change the plot for chart 6 
> . 
> Maybe you can do humidityplot instead. 
>

That's easy, already done and updated! Thanks for the hint and your rapid 
reply... 

2. This is the first request for 24 hour format and I haven't thought of 
> testing that! I will look into this. 
>

Standard in Germany and some other European countries! ;-)
Would be a good idea to add something like that in a future update. Right 
now, I would rate that a cosmetic option. 

-- 
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: Belchertown skin for weewx now available!

[Pat]

Glad you like the skin. 

1. To disable the UV/solar radiation, you can change the plot for chart 6 
. 
Maybe you can do humidityplot instead. 
2. This is the first request for 24 hour format and I haven't thought of 
testing that! I will look into this. 


On Monday, December 3, 2018 at 1:55:45 PM UTC-5, stelli...@gmail.com wrote:
>
> Just converted from CumulusMX to weewx with your Skin. Everything runs 
> fine, only two minor things I want to get changed:
>
>1. My weather station is a very basic FineOffset WH1080 with sensor 
>for UV/solar radiation. Is there a simple way to deactivate the solar 
>radiation plot?
>2. Another thing is the time format that is in am/pm format but shows 
>up without am or pm indicators. Can this be set to 24 hour format?
>
> My site: https://wetter.teamstelling.de/
>
> Besides that brilliant piece of software and nice responsive skin!
>

-- 
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: Belchertown skin for weewx now available!

[stellingorama]

Just converted from CumulusMX to weewx with your Skin. Everything runs 
fine, only two minor things I want to get changed:

   1. My weather station is a very basic FineOffset WH1080 with sensor for 
   UV/solar radiation. Is there a simple way to deactivate the solar radiation 
   plot?
   2. Another thing is the time format that is in am/pm format but shows up 
   without am or pm indicators. Can this be set to 24 hour format?

My site: https://wetter.teamstelling.de/

Besides that brilliant piece of software and nice responsive skin!

-- 
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: weewx abends with no reason

[Gary Hopkins]

OK Update.

I did get the new Pi but I've not installed it with weewx.

I was "fiddling" with the historic values on the WS and I went to delete 
all the 2017 ones. Instead I accidentally deleted the 2018 ones so by then 
it was too late.

Once I'd gone back and deleted all the 2017 entries and there was no longer 
any historical data to download everything is working fine and has been 
since Saturday.

I suspect that there is something "wrong" with pulling down the historical 
data that was causing something to fail. Downloading "live" data and 
running all the reporting scripts is working without a hitch. I'll just 
live with the fact that I've lost all my historic data on the WS. 

Thanks again for all your suggestions and help

G

On Monday, 3 December 2018 02:19:55 UTC, Thomas Keffer wrote:
>
>
>> I must be missing something but I can't see any error messages in the 
>> logs posted so far. Without those it i shard to guess what is going on.
>>
>>
> Exactly. That's why I suspect it's a kernel-level problem. If the problem 
> were in user's space, it should have generated an exception.
>
> -tk
>

-- 
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] UnicodeDecodeError

[erika . bostrm392]

Hello Thomas
I have not changed any template, it seems to be problem with more skins ...
I have done the installation with sudo apt-get install weewx

here comes a new log:

Dec  3 10:59:31 stretch4 systemd[1]: Starting LSB: weewx weather system...
Dec  3 10:59:32 stretch4 weewx[5711]: engine: Initializing weewx version 
3.8.2
Dec  3 10:59:32 stretch4 weewx[5711]: engine: Using Python 2.7.13 (default, 
Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Dec  3 10:59:32 stretch4 weewx[5711]: engine: Platform 
Linux-4.14.79-v7+-armv7l-with-debian-9.6
Dec  3 10:59:32 stretch4 weewx[5711]: engine: Locale is 'sv_SE'
Dec  3 10:59:32 stretch4 weewx[5711]: engine: pid file is /var/run/weewx.pid
Dec  3 10:59:32 stretch4 weewx[5715]: engine: Using configuration file 
/etc/weewx/weewx.conf
Dec  3 10:59:32 stretch4 weewx[5715]: engine: Loading station type Airmar 
(weewx.drivers.airmar)
Dec  3 10:59:32 stretch4 weewx[5700]: Starting weewx weather system: weewx.
Dec  3 10:59:32 stretch4 systemd[1]: Started LSB: weewx weather system.
Dec  3 10:59:32 stretch4 weewx[5715]: airmar: driver version is 0.28
Dec  3 10:59:32 stretch4 weewx[5715]: airmar: using serial port /dev/ttyUSB0
Dec  3 10:59:32 stretch4 weewx[5715]: engine: StdConvert target unit is 0x1
Dec  3 10:59:32 stretch4 weewx[5715]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Dec  3 10:59:32 stretch4 weewx[5715]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Dec  3 10:59:32 stretch4 weewx[5715]: engine: Archive will use data binding 
wx_binding
Dec  3 10:59:32 stretch4 weewx[5715]: engine: Record generation will be 
attempted in 'hardware'
Dec  3 10:59:32 stretch4 weewx[5715]: engine: Using archive interval of 300 
seconds (specified in weewx configuration)
Dec  3 10:59:32 stretch4 weewx[5715]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Dec  3 10:59:32 stretch4 weewx[5715]: manager: Starting backfill of daily 
summaries
Dec  3 10:59:32 stretch4 weewx[5715]: restx: StationRegistry: Registration 
not requested.
Dec  3 10:59:32 stretch4 weewx[5715]: restx: Wunderground: Posting not 
enabled.
Dec  3 10:59:32 stretch4 weewx[5715]: restx: PWSweather: Posting not 
enabled.
Dec  3 10:59:32 stretch4 weewx[5715]: restx: CWOP: Posting not enabled.
Dec  3 10:59:32 stretch4 weewx[5715]: restx: WOW: Posting not enabled.
Dec  3 10:59:32 stretch4 weewx[5715]: restx: AWEKAS: Posting not enabled.
Dec  3 10:59:32 stretch4 weewx[5715]: engine: Starting up weewx version 
3.8.2
Dec  3 10:59:32 stretch4 weewx[5715]: engine: Starting main packet loop.
Dec  3 10:59:32 stretch4 weewx[5715]: airmar: Garbled message
Dec  3 11:00:16 stretch4 weewx[5715]: manager: Added record 2018-12-03 
11:00:00 CET (1543831200) to database 'weewx.sdb'
Dec  3 11:00:16 stretch4 weewx[5715]: manager: Added record 2018-12-03 
11:00:00 CET (1543831200) to daily summary in 'weewx.sdb'
Dec  3 11:00:18 stretch4 weewx[5715]: cheetahgenerator: Generate failed 
with exception ''
Dec  3 11:00:18 stretch4 weewx[5715]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Standard/week.html.tmpl
Dec  3 11:00:18 stretch4 weewx[5715]: cheetahgenerator:  Reason: 'utf8' 
codec can't decode byte 0xf6 in position 11: invalid start byte
Dec  3 11:00:18 stretch4 weewx[5715]:   Traceback (most recent call 
last):
Dec  3 11:00:18 stretch4 weewx[5715]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
Dec  3 11:00:18 stretch4 weewx[5715]:   print >> _file, 
compiled_template
Dec  3 11:00:18 stretch4 weewx[5715]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Dec  3 11:00:18 stretch4 weewx[5715]:   rc = getattr(self, 
mainMethName)()
Dec  3 11:00:18 stretch4 weewx[5715]: File 
"_etc_weewx_skins_Standard_week_html_tmpl.py", line 813, in respond
Dec  3 11:00:18 stretch4 weewx[5715]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 595, in filter
Dec  3 11:00:18 stretch4 weewx[5715]:   filtered = 
self.filter(str(val))
Dec  3 11:00:18 stretch4 weewx[5715]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 593, in filter
Dec  3 11:00:18 stretch4 weewx[5715]:   filtered = 
val.decode('utf-8').encode('ascii', 'xmlcharrefreplace')
Dec  3 11:00:18 stretch4 weewx[5715]: File 
"/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
Dec  3 11:00:18 stretch4 weewx[5715]:   return 
codecs.utf_8_decode(input, errors, True)
Dec  3 11:00:18 stretch4 weewx[5715]:   UnicodeDecodeError: 'utf8' 
codec can't decode byte 0xf6 in