[weewx-user] Re: Acurite 01536 (Costco)

[Scott Beard]

Marcus,

I have been running one of these units with weewx on a RPI3 since mid 
October.  The console is telling me the log is full and to connect it to 
the PC to clear it out.  It has been telling me that since 12 days after I 
set it up.  But it still works fine with weewx.  From what I can tell, the 
Acurite 01536 is based on the 02064 but is specific to Costco and has a 
slightly different screen layout.

Thanks
Scott

On Sunday, December 25, 2016 at 1:17:58 PM UTC-6, Marcus Watkins wrote:
>
> For Christmas today I received an Acurite 01536 5-in-1 weather station 
> with USB connection (from Costco). I set it up with weewx and was excited 
> to see it works out of the box for the most part.
>
> One difference from the docs is there's no 'USB Mode' switch on this base, 
> so I'm interested to see if the log fills up over time.
>
> The only real 'issue' is the barometer reads outside the values allowed by 
> weewx by default. I'm also seeing values vary by quite a bit, but it's 
> super windy out right now. I added an adjustment to match the display, 
> we'll see how it lines up over time.
>
> Does anyone know if the display reports barometer or pressure?
>
> All in all, seems to be working great.
>
> -Marcus
>
>
>
>

-- 
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: Create backup image of the running system

[Scott Beard]

I use raspiBackup to make online image of my SD card after I saw it 
mentioned by someone else on this board.

https://www.linux-tips-and-tricks.de/en/raspberry/303-pi-creates-automatic-backups-of-itself

I keep my database, config files and webpages on a NFS share which has its 
own backup.  Because of this, once a month I run raspiBackup to make a DD 
image of the RPI.  It does slow the RPI3 down to the point it will not 
generate the weewx HTML pages, but it will still log the archive interval 
and post info to wunderground.

Scott


On Sunday, December 25, 2016 at 3:55:39 AM UTC-6, Per Edström wrote:
>
> I run my Weewx on Raspberry Pi and on a  "PC" (Ebox 3350 and Ubuntu 10). 
> Both have the OS on an SD/SDHC-card.
>
> Now, I find it messy to create a backup image:
> 1. Halt system
> 2. Power down
> 3. Remove SD-card
> 4. Put in laptop and create an image to file (5-10 min)
> 5. Insert SD-card in taget again and power up.
> 6. Write image file to new SD-card (15-20 min).
>
> (NB! I have noted that not all 16GB SD-card have the exact same size, it 
> varies quite a lot. This became an issue the trying to find a new SD-card 
> for the one that failed..)
>
> This procedure takes time and requires quite a lot of physical 
> intervention.
>
> Is there any way of to create or maintain an updated image from the 
> running system. Maybe it's Ok to just backup some files (user installed)?
>
> Also, it would be nice to have this "backup SD" as an alternative boot 
> SD-card in case the primary one fails. I don't know if that is possible..
>

-- 
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: AWEKAS

[mwall]

On Wednesday, December 28, 2016 at 2:26:40 PM UTC-5, Barton Phillips wrote:
>
> Here is what it says in my log file:
> Dec 28 11:20:17 raspberrypi weewx[18233]: restx: AWEKAS: Failed to publish 
> record 2016-12-28 11:20:00 PST (1482952800): server returned ' - Temperatur 
> administrativ gesperrt - Luftfeuchte administrativ gesperrt - Luftdruck 
> administrativ gesperrt - Niederschlag administrativ gesperrt - Windmessung 
> administrativ gesperrt - Regenrate administrativ gesperrt  - Transfer OK'
>
> It means the the values were "blocked" by an administrative function.
>

barton,

go to the awekas web site and log in to your account.

go to the bottom of the page and click on the 'Go to quality checking 
system' link

http://www.awekas.at/en/qualcheck.php?id=X

there you should see when locks were applied to your system, and whether 
those locks are still in place.

i'm not sure how one goes about removing locks, especially when they are 
'permanent'.

i once had a fine offset reporting to awekas, and it lost contact with the 
sensor unit when the batteries died.  it took me a week or two to get to 
the station to replace the batteries, and in that time awekas decided the 
station was flat-lining, so it did a permanent lock on the station.

i never figured out how to remove the locks, so if you figure it out, 
please post!

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.

[weewx-user] Re: USB-reset changes /dev/ttyUSB0 to /dev/ttyUSB1

[vince]

google for "usb device number changes linux" - there are a 'lot' of links 
that come up.

Impossible to say much more without knowing what os you are running.

-- 
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] USB-reset changes /dev/ttyUSB0 to /dev/ttyUSB1

[Per Edström]

This is probably related to my HW i.e. the Ebox3350 and the 
RS232-to-USB-unit )PL2303). But maybe other Weewx-users have experienced a 
change in USB-device?

Questions:
- Why is the USB reset?
- Why does it change device number?
- Is there any way to lock the PL2303 to /dev/ttyUSB0 so it doesn't change?

After a reboot it is back to /dev/ttyUSB0

"
Dec 28 03:49:14 Ebox3350 kernel: [43641.405860] usb 1-2.3: input irq status 
-75  received
Dec 28 03:49:16 Ebox3350 weewx[3202]: wmr9x8: Received WMR9x8 data packet.
Dec 28 03:49:19 Ebox3350 kernel: [43646.533834] usb 1-2.3: input irq status 
-75  received
Dec 28 03:49:24 Ebox3350 kernel: [43651.465190] *usb 1-2: USB disconnect, 
address 2*
Dec 28 03:49:24 Ebox3350 kernel: [43651.465211] usb 1-2.1: USB disconnect, 
address 3
Dec 28 03:49:24 Ebox3350 kernel: [43651.465929] usb 1-2.3: USB disconnect, 
address 4
Dec 28 03:49:24 Ebox3350 kernel: [43651.485257] *usb 1-2.4: USB disconnect, 
address 5*
Dec 28 03:49:24 Ebox3350 kernel: [43651.485679] *usb 1-2: clear tt 4 (9053) 
error -19*
Dec 28 03:49:24 Ebox3350 kernel: [43651.527638] *pl2303 ttyUSB0: pl2303 
converter now disconnected from ttyUSB0*
Dec 28 03:49:24 Ebox3350 kernel: [43651.527996] pl2303 1-2.4:1.0: device 
disconnected
Dec 28 03:49:24 Ebox3350 kernel: [43651.817456] usb 1-2: new high speed USB 
device using ehci_hcd and address 6
Dec 28 03:49:24 Ebox3350 kernel: [43651.941412] usb 1-2: New USB device 
found, idVendor=1a40, idProduct=0101
Dec 28 03:49:24 Ebox3350 kernel: [43651.941436] usb 1-2: New USB device 
strings: Mfr=0, Product=1, SerialNumber=0
Dec 28 03:49:24 Ebox3350 kernel: [43651.941453] usb 1-2: Product: USB 2.0 
Hub [MTT]
Dec 28 03:49:24 Ebox3350 kernel: [43651.946294] hub 1-2:1.0: USB hub found
Dec 28 03:49:24 Ebox3350 kernel: [43651.946695] hub 1-2:1.0: 4 ports 
detected
Dec 28 03:49:24 Ebox3350 kernel: [43652.214202] usb 1-2.1: new full speed 
USB device using ehci_hcd and address 7
Dec 28 03:49:24 Ebox3350 kernel: [43652.304159] usb 1-2.1: New USB device 
found, idVendor=1781, idProduct=0c31
Dec 28 03:49:24 Ebox3350 kernel: [43652.304183] usb 1-2.1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
Dec 28 03:49:24 Ebox3350 kernel: [43652.304200] usb 1-2.1: Product: 
TellStick Duo
Dec 28 03:49:24 Ebox3350 kernel: [43652.304213] usb 1-2.1: Manufacturer: 
Telldus
Dec 28 03:49:24 Ebox3350 kernel: [43652.304226] usb 1-2.1: SerialNumber: 
A501IW2P
Dec 28 03:49:25 Ebox3350 kernel: [43652.380956] usb 1-2.3: new low speed 
USB device using ehci_hcd and address 8
Dec 28 03:49:25 Ebox3350 kernel: [43652.510039] usb 1-2.3: New USB device 
found, idVendor=051d, idProduct=0002
Dec 28 03:49:25 Ebox3350 kernel: [43652.510062] usb 1-2.3: New USB device 
strings: Mfr=3, Product=1, SerialNumber=2
Dec 28 03:49:25 Ebox3350 kernel: [43652.510080] usb 1-2.3: Product: 
Back-UPS ES 700 FW:829.D2 .I USB FW:D2
Dec 28 03:49:25 Ebox3350 kernel: [43652.510096] usb 1-2.3: Manufacturer: APC
Dec 28 03:49:25 Ebox3350 kernel: [43652.510109] usb 1-2.3: SerialNumber: 
5B0823T19645
Dec 28 03:49:25 Ebox3350 kernel: [43652.864594] generic-usb 
0003:051D:0002.0002: hiddev96,hidraw0: USB HID v1.10 Device [APC Back-UPS 
ES 700 FW:829.D2 .I USB FW:D2 ] on usb-:00:0a.1-2.3/input0
Dec 28 03:49:25 Ebox3350 kernel: [43652.940824] usb 1-2.4: new full speed 
USB device using ehci_hcd and address 9
Dec 28 03:49:25 Ebox3350 kernel: [43653.025405] usb 1-2.4: New USB device 
found, idVendor=067b, idProduct=2303
Dec 28 03:49:25 Ebox3350 kernel: [43653.025428] usb 1-2.4: New USB device 
strings: Mfr=1, Product=2, SerialNumber=0
Dec 28 03:49:25 Ebox3350 kernel: [43653.025446] usb 1-2.4: Product: 
USB-Serial Controller D
Dec 28 03:49:25 Ebox3350 kernel: [43653.025460] usb 1-2.4: Manufacturer: 
Prolific Technology Inc.
Dec 28 03:49:25 Ebox3350 kernel: [43653.031091] *pl2303 1-2.4:1.0: pl2303 
converter detected*
Dec 28 03:49:25 Ebox3350 kernel: [43653.034439] *usb 1-2.4: pl2303 
converter now attached to ttyUSB1*
Dec 28 03:49:25 Ebox3350 kernel: [43653.119773] usb 1-2.3: input irq status 
-75  received
Dec 28 03:49:26 Ebox3350 modem-manager: (ttyUSB1) opening serial device...
Dec 28 03:49:26 Ebox3350 modem-manager: (ttyUSB1): probe requested by 
plugin 'Generic'
Dec 28 03:49:29 Ebox3350 kernel: [43656.783741] usb 1-2.3: input irq status 
-75  received
Dec 28 03:49:34 Ebox3350 kernel: [43661.911701] usb 1-2.3: input irq status 
-75  received
Dec 28 03:49:38 Ebox3350 modem-manager: (ttyUSB1) closing serial device...

-- 
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: Process Monitoring on Debian Installation

[vince]

On Wednesday, December 28, 2016 at 12:19:09 PM UTC-8, Phil Green wrote:
>
> Yes,systemctl status weewx give me the process number.
> ps and the process number, shows me the process but it only lists it as 
> python. Whereas my other system it actually comes up as weewxd !
> Must be the difference between the setup.py method and the Debian install 
> method. 
>
>
Is there something not working ?

Yes the two ways have slightly different output, one has the full pathname 
to the python interpreter and each uses its own ideas of where files should 
be located, but I'm not seeing any problem.  Both work.


= setup.py method ===
root@jessie:/home/vagrant# ps axu|grep wee|grep -v grep
root 12838  0.1  3.8  66156 19400 ?S21:45   0:00 
/usr/bin/python /home/weewx/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid /home/weewx/weewx.conf

root@jessie:/home/vagrant# systemctl status weewx
● weewx.service - weewx weather system
   Loaded: loaded (/etc/systemd/system/weewx.service; enabled)
   Active: active (running) since Wed 2016-12-28 21:45:17 GMT; 2min 47s ago
 Main PID: 12838 (weewxd)
   CGroup: /system.slice/weewx.service
   └─12838 /usr/bin/python /home/weewx/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid /home/weewx/weewx.conf

= apt-get method ===

root@jessie:/home/vagrant# ps axu|grep wee|grep -v grep
root 11895  0.7  3.2  46084 16696 ?S21:52   0:00 python 
/usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf

root@jessie:/home/vagrant# systemctl status weewx
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx)
   Active: active (running) since Wed 2016-12-28 21:52:08 GMT; 19s ago
   CGroup: /system.slice/weewx.service
   └─11895 python /usr/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf


-- 
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: AWEKAS

[mwall]

Take a look at the thread "data quality system locking" in the awekas forum.

Awekas would often complain if a station sends partial packets, for example if 
a the station lost contact with the wind sensor.

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: AWEKAS

[m...@erwinheger.de]

As you can see: Weewx works. What happens on the other side at Awekas ... ask 
them. For me, the Weewx direct link didn't work either, I used to have the 
data-file transfered to my webspace. Because of too many restrictive 
administrative action by Awekas I quit the service.

Erwin Heger

> Am 28.12.2016 um 20:26 schrieb Barton Phillips :
> 
> Here is what it says in my log file:
> Dec 28 11:20:17 raspberrypi weewx[18233]: restx: AWEKAS: Failed to publish 
> record 2016-12-28 11:20:00 PST (1482952800): server returned ' - Temperatur 
> administrativ gesperrt - Luftfeuchte administrativ gesperrt - Luftdruck 
> administrativ gesperrt - Niederschlag administrativ gesperrt - Windmessung 
> administrativ gesperrt - Regenrate administrativ gesperrt  - Transfer OK'
> 
> It means the the values were "blocked" by an administrative function.
> 
>> On Tuesday, December 27, 2016 at 11:24:03 AM UTC-8, Barton Phillips wrote:
>> How do I set up AWEKAS? At one point I had it working with a awekas.html 
>> file but I no longer have that file. I went to the website and tried to set 
>> it up to use 'weewx direct connect' but that does not seem to work. What am 
>> I missing?
> 
> -- 
> 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 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: Integration with Alexa

[Rob Cranfill]

FWIW, I haven't quite "closed the loop" in my own 
Davis->weewx->HomeAssistant->Alexa setup, but I was thinking about just 
trying to get Alexa to access my WeatherUnderground data, which of course 
comes from my station. So I guess that would then be 
Davis->weewx->WeatherUnderground->Alexa. And WU certainly has the past data 
- not sure about their API.

 /rob

On Thursday, December 15, 2016 at 8:24:21 AM UTC-8, Matt Sargent wrote:
>
> Hi all,
>
> I am writing an Alexa skill that would be able to interface to Weewx. 
> Pretty simple for the current data and such, but I am hoping to add the 
> ability to query past weather conditions. Has anyone developed an API of 
> any sort that allows you to query data from the weather station? 
>
> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Process Monitoring on Debian Installation

[vince]

On Wednesday, December 28, 2016 at 11:14:50 AM UTC-8, Phil Green wrote:
>
> I have a live installation running with a Vantage View on a Pi using the 
> setup.py method. 
> I have now tried on another Pi installing using the Debian method. For the 
> time being it's running a simulated weather station. 
>
> On my live system in can see the processor usage using the ps command and 
> see the process weewxd. However on the Debian Installation I can't see the 
> weewxd process. 
> How do I see the weewxd process on the Debian installation?
>

Same way you do for every other process, but without a transcript of what 
you did it's hard to debug.

How about

   - ps aux | grep weewx | grep -v grep
   - or 'systemctl status weewx'


-- 
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: AWEKAS

[Barton Phillips]

Here is what it says in my log file:
Dec 28 11:20:17 raspberrypi weewx[18233]: restx: AWEKAS: Failed to publish 
record 2016-12-28 11:20:00 PST (1482952800): server returned ' - Temperatur 
administrativ gesperrt - Luftfeuchte administrativ gesperrt - Luftdruck 
administrativ gesperrt - Niederschlag administrativ gesperrt - Windmessung 
administrativ gesperrt - Regenrate administrativ gesperrt  - Transfer OK'

It means the the values were "blocked" by an administrative function.

On Tuesday, December 27, 2016 at 11:24:03 AM UTC-8, Barton Phillips wrote:
>
> How do I set up AWEKAS? At one point I had it working with a awekas.html 
> file but I no longer have that file. I went to the website and tried to set 
> it up to use 'weewx direct connect' but that does not seem to work. What am 
> I missing?
>

-- 
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] Process Monitoring on Debian Installation

[Phil Green]

I have a live installation running with a Vantage View on a Pi using the 
setup.py method. 
I have now tried on another Pi installing using the Debian method. For the time 
being it's running a simulated weather station. 

On my live system in can see the processor usage using the ps command and see 
the process weewxd. However on the Debian Installation I can't see the weewxd 
process. 
How do I see the weewxd process on the Debian installation?
Regards
Phil

-- 
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: AWEKAS

[Barton Phillips]

That doesn't really answer my question. I have the weewx.conf file setup 
correctly (I think). What I want to know is what I should do at the AWEKAS 
site. They have an dropdown for the "Report mode" with "Weewx Direct Link". 
That is what I have selected, but I don't get any uploads. What should I 
select. There is a "wview" option which I think I was using before but it 
asks for a filename and I don't have a file and I don't know what the 
format should be or how to create it.



On Tuesday, December 27, 2016 at 11:44:09 AM UTC-8, Andrew Milner wrote:
>
> If you are trying to submit data to awekas see
> http://weewx.com/docs/usersguide.htm#[StdRESTful]
>  
>
>
> On Tuesday, 27 December 2016 21:24:03 UTC+2, Barton Phillips wrote:
>
>> How do I set up AWEKAS? At one point I had it working with a awekas.html 
>> file but I no longer have that file. I went to the website and tried to set 
>> it up to use 'weewx direct connect' but that does not seem to work. What am 
>> I missing?
>>
>

-- 
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: New User - Issues with reading WVIEW sdb during conversion to WeeWX.

[Oscar]

Here is the process I use to convert my wview to weewx.  The word None and 
possibly some special characters are in the wview archive table.  The 
following process will clean up those columns.

1.  copy wview-archive.sdb to weewx.sdb
2.  run the attached script weewx-wviewCleanup.sql.  It will change those 
values to NULL. This change the command below to the appropriate paths.

sqlite3 -init PATH_TO_FILE/weewx_wviewCleanup.sql PATH_TO_DATABSE/weewx.sdb.

3.  run wee_database again.  
   If it fails, run wee_database --string-check PATH_TO_CONFIG/weewx.conf
   if that fails, note the error.  If the error identifies a column has 
None in it, modify the weewx_wviewCleanup.sql script to null out that 
column and run it again.

That process resolved my issues.

After the database has been converted by wee_database, you may want to run 
the script zkwx_wviewHiLow.py.  It reads the view-hilow.sdb data base.  
It reads most of the tables and identifies the max(high) and min(low) for 
each day.  It updates the appropriate archive_day_XXX table in weewx.sdb.  
It doesn't touch rain and rainRate.  I wasn't sure how I should total them, 
so I'm using the weewx calculation.  The script requires python3.  See 
disclaimer 2.

to run it
zkwx_wviewHiLow.py -f PATH_TO/wview-hilow.sdb -t PATH_TO/weewx.sdb

Disclaimers:
1.  Use at your own risk
2.  I don't know python.  If you (or anyone) looks at the code and asks 
themselves why did he do that, the answer is I found an example and made it 
work.

Good Luck,
Oscar




On Tuesday, December 27, 2016 at 7:07:02 PM UTC-7, Punch Card wrote:

> So I think I have gotten the configuration file correct where it is seeing 
> the weather station.
>
> But it seems that there is some errant data in my wview sdb. Also I tried 
> the *" wee_database --string-check"* there seem to be only one row in the 
> data that had an issue, but it does not look like it corrected the row.
> Is there a way to start weewx in a debug mode so I can find the errant 
> data and either correct the data, or just delete the row.
> Or do you have another suggestion?
>
> [root@weewx]# wee_database --string-check
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'wx_binding', which is bound to database 
>> 'archive_sqlite'
>> Checking archive database for strings...
>> Timestamp = 1347032100; record['rain']= u'0\n0'; ... ignored.
>> [root@weewx]# 
>>
>
> Last /var/log/messages for weewx attempt 
>
> Dec 27 08:43:10 md-centos systemd: Stopping SYSV: start and stop the weewx 
> weather system...
> Dec 27 08:43:10 md-centos weewx: Shutting down weewx: [FAILED]
> Dec 27 08:43:10 md-centos systemd: Stopped SYSV: start and stop the weewx 
> weather system.
> Dec 27 09:32:16 md-centos systemd: Starting SYSV: start and stop the weewx 
> weather system...
> Dec 27 09:32:16 md-centos weewx[31695]: engine: Initializing weewx version 
> 3.6.2
> Dec 27 09:32:16 md-centos weewx[31695]: engine: Using Python 2.7.5 
> (default, Nov  6 2016, 00:28:07) #012[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)]
> Dec 27 09:32:16 md-centos weewx[31695]: engine: Platform 
> Linux-3.10.0-514.2.2.el7.x86_64-x86_64-with-centos-7.3.1611-Core
> Dec 27 09:32:16 md-centos weewx[31695]: engine: pid file is 
> /var/run/weewx.pid
> Dec 27 09:32:16 md-centos weewx[31699]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> Dec 27 09:32:16 md-centos weewx[31699]: engine: Loading station type 
> WMR200 (weewx.drivers.wmr200)
> Dec 27 09:32:16 md-centos weewx: Starting weewx: [  OK  ]
> Dec 27 09:32:16 md-centos systemd: Started SYSV: start and stop the weewx 
> weather system.
> Dec 27 09:32:16 md-centos weewx[31699]: wmr200: MainThread: I Created 
> watchdog thread to poke for live data every 30 seconds
> Dec 27 09:32:16 md-centos weewx[31699]: wmr200: MainThread: I Created USB 
> polling thread to read block on device
> Dec 27 09:32:16 md-centos weewx[31699]: wmr200: Thread-2: I USB polling 
> device thread for live data launched
> Dec 27 09:32:16 md-centos weewx[31699]: wmr200: MainThread: I Reset 
> console device
> Dec 27 09:32:17 md-centos weewx[31699]: wmr200: Thread-2: I USB polling 
> device thread signaled to start
> Dec 27 09:32:17 md-centos weewx[31699]: engine: StdConvert target unit is 
> 0x1
> Dec 27 09:32:17 md-centos weewx[31699]: 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 27 09:32:17 md-centos weewx[31699]: wxcalculate: The following 
> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Dec 27 09:32:17 md-centos weewx[31699]: engine: Archive will use data 
> binding wx_binding
> Dec 27 

[weewx-user] Re: Missing forecast display on exfoliation index page

[mwall]

On Wednesday, December 28, 2016 at 9:34:35 AM UTC-5, Dan'l B wrote:
>
> I know I'm missing something obvious here but what is required to display 
> the NWS and/or WU forecast details on the index page when the forecast skin 
> is installed?
>

dan'l,

the exfoliation skin recently got an update to match the latest 
capabilities of the forecast extension.

try installing exfoliation 0.39 and forecast 3.2.6

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.

[weewx-user] Re: Missing forecast display on exfoliation index page

[Andrew Milner]

https://github.com/weewx/weewx/wiki/forecasting

tells you how to include forecast data in pages other than forecast.html 

is this what you were looking for??

On Wednesday, 28 December 2016 16:34:35 UTC+2, Dan'l B wrote:

> I know I'm missing something obvious here but what is required to display 
> the NWS and/or WU forecast details on the index page when the forecast skin 
> is installed?
>
> Dinkins Bayou Weather 
>
> weewx 3.6.2
> forecast 3.2.4
>

-- 
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] Missing forecast display on exfoliation index page

[Dan'l B]

I know I'm missing something obvious here but what is required to display 
the NWS and/or WU forecast details on the index page when the forecast skin 
is installed?

Dinkins Bayou Weather 

weewx 3.6.2
forecast 3.2.4

-- 
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: Realtime.txt, realtime.xml and sunbird.txt

[Janez Kranjski]

On Friday, December 16, 2016 at 6:37:41 PM UTC+1, mwall wrote:
>
> if you could point me to an official specification for realtime.xml and 
> sunbird.txt, i can update the crt extension to emit realtime.xml and 
> sunbird.txt in addition to realtime.txt
>
> m
>

@mwall:
Any news?
:-) 

-- 
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.