Re: [weewx-user] Re: wind chill for Vantage Pro 2

[Andrew Milner]

probably. Try and plot min wind chill instead of avg and for heat index 
plot max and you may get what you expect.


On Sunday, 2 August 2020 06:06:35 UTC+3, Praveen Chandrasekaran wrote:
>
> I see an issue where graph doesn't match the lowest wind chill in stats. 
> That's because of averaging?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0f872c14-da1d-4081-bf2b-488424f0e937o%40googlegroups.com.

Re: [weewx-user] Re: wind chill for Vantage Pro 2

[Andrew Milner]

set aggregate_type in the appropriate graph section(s) of skin.conf



On Sunday, 2 August 2020 08:32:36 UTC+3, Praveen Chandrasekaran wrote:
>
> And how do I do that?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d2900cb8-c117-434b-adcf-92205ba4d90do%40googlegroups.com.

[weewx-user] Re: How do I fully integrate a new custom data field? I've got it working somewhat, but...

[Andrew Milner]

did you change the binding to use the new database with the extra field??
http://weewx.com/docs/customizing.htm#add_archive_type



On Tuesday, 4 August 2020 07:15:45 UTC+3, Kevin Key wrote:
>
> Hi all,
>
> So today I added the following code to a new file 
> in usr/share/weewx/user/evapcooler.py :
>
>
> import weewx
> from weewx.engine import StdService
>
> class MyEvapCooler(StdService):
> def __init__(self, engine, config_dict):
> super(MyEvapCooler, self).__init__(engine, config_dict)
> self.bind(weewx.NEW_ARCHIVE_RECORD, self.new_archive_record)
>
> def new_archive_record(self, event):
> try:
> event.record['evapcoolerdelta'] = event.record['outTemp'] 
> - event.record['extraTemp2']
> except KeyError:
> pass
>
>
> import schemas.wview_extended
>
> schema_with_evapcoolerdelta = {
> 'table': schemas.wview_extended.table + [('evapcoolerdelta', 'REAL')],
> 'day_summaries' : schemas.wview_extended.day_summaries + 
> [('evapcoolerdelta', 'SCALAR')]
>
>
> ---
>
> I'm able to bring up the new field "evapcoolerdelta" in current.inc under 
> /skins/Seasons/ , but I'm having trouble getting the min/max archive data 
> for day, week, month, and year to appear. Are there other places in the 
> code where I need to make it know that I've added a new data field?
>
> Thanks,
>
> Kevin
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d67c468f-431c-45d7-b154-8e6cf3ee27eeo%40googlegroups.com.

[weewx-user] Re: Moonrise and Moonset strange

[Andrew Milner]

what makes you think something is wrong??  I just checked nicosia (cyprus) 
with my weewx station and another website and we have moonrise at 6am and 
moonset at 8pm at the moment.



On Wednesday, 19 August 2020 11:38:38 UTC+3, Hans Cilker wrote:
>
> Hallo Together,
> i am Running WeeWX version 4.1.1. When i take a look at the datas for 
> Moonrise and moonset, it seams to be strange, Moonrise:  06:11:23 and 
> Moonset:  21:22:48. In this cases i could just change the Lable, but 
> highest point of the moon at 13:56:18is not to solve with changing the 
> lable. I have taken a look at som stations around, i found no one with the 
> right lable. Anybody an idea whats to do to solve this problem?
> Best wishes
> Hans
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c05b1d9b-755b-4921-81ef-3fd6db099825o%40googlegroups.com.

[weewx-user] Re: Moonrise and Moonset strange

[Andrew Milner]

You cannot often see the moon during the daytime - so when it rises in the 
nmorning you tend not to see it

see
https://www.timeanddate.com/moon/cyprus/nicosia replace cyprus and nicosia 
with your country and city if you wish



On Wednesday, 19 August 2020 12:28:49 UTC+3, Hans Cilker wrote:
>
> OK, then ei do not understand the meaning, for me, the moon is rising in 
> the evenening and moonset is in the moment, as i was writing, it seams 
> strange to me to that moonrise is in the morning, but may be i do not 
> understand it.
>
>
> andrew.s...@gmail.com schrieb am Mittwoch, 19. August 2020 um 11:05:36 
> UTC+2:
>
>> what makes you think something is wrong??  I just checked nicosia 
>> (cyprus) with my weewx station and another website and we have moonrise at 
>> 6am and moonset at 8pm at the moment.
>>
>>
>>
>> On Wednesday, 19 August 2020 11:38:38 UTC+3, Hans Cilker wrote:
>>>
>>> Hallo Together,
>>> i am Running WeeWX version 4.1.1. When i take a look at the datas for 
>>> Moonrise and moonset, it seams to be strange, Moonrise:  06:11:23 and 
>>> Moonset:  21:22:48. In this cases i could just change the Lable, but 
>>> highest point of the moon at 13:56:18is not to solve with changing the 
>>> lable. I have taken a look at som stations around, i found no one with the 
>>> right lable. Anybody an idea whats to do to solve this problem?
>>> Best wishes
>>> Hans
>>>
>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/79c92031-e9ad-44f8-ab7b-1dafd1195e1eo%40googlegroups.com.

[weewx-user] Re: WH1080 sender / receiver appears to have died, suggestions?

[Andrew Milner]

read the manual - there is a button to press (i forget which) to regain 
communications.  Just looked - press and hold the down key for 4 seconds 
until the console beeps.

Register transmitter If no outdoor weather data is displayed or the signal 
to the sensors is lost during setting up, mounting, changing of batteries 
to the sensor or plugging or unplugging cables, simply press and hold the 
DOWN/- key for 4 seconds and a short beep will sound to synchronize the 
base station to sensors. Without being synchronized, weather data will not 
be received. NOTE: Wait two minutes before re-insert the batteries of 
transmitter for proper reset. Note: The best condition for reception is at 
night, between midnight and 6:00am – when there is less atmospheric 
interference.



On Thursday, 20 August 2020 21:10:43 UTC+3, James Muirhead wrote:
>
> My WH1080 sender / receiver appears to have died. 
>
> The battery low indicator had been on for some time and died about 0130 
> this morning.
>
> I changed out the batteries in the sender today and it does not want to 
> communicate with the receiver now. LED in the sender comes on and receiver 
> appears normal.
>
> I've reset receiver and sender in both orders and left for an hour, etc, 
> etc. WeeWX WebUI shows no signal (but I don't know how this is generated).
>
> The communication icon on receiver comes up sporadically for a minute at 
> start and for quarter of a second once in a while.
>
> I'm gonna take apart the sender tomorrow and give everything a good clean, 
> see if it helps.
>
> Has anyone got a suggestion, other than "buy a new weather station"?
>
> Thanks.
>
> PS - WeeWX is working perfectly. But I have WeeWX installed on an Orange 
> Pi PC (1.3GHz Quad, 1GB RAM). Shout if you want anymore information.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7cffbaeb-c08c-4ddc-b0cc-ce4cda005b6do%40googlegroups.com.

Re: [weewx-user] Re: WH1080 sender / receiver appears to have died, suggestions?

[Andrew Milner]

from memory I THINK that when you press the down button the icon starts to 
flash and it beeps and then it is hunting for the transmitter.  If it does 
not beep it is not searching.  Did you change the batteries in the 
transmitter AND the console?  Did you wait 2 minutes before reinserting new 
batteries in the transmitter?  You could also try with the console outside 
closer to the transmitter - and the manual suggests doing this resync at 
night.  Otherwise maybe it has died a death ... RIP...



On Friday, 21 August 2020 15:20:29 UTC+3, James Muirhead wrote:
>
> I lost my manual aeons ago, have downloaded. It's on it's 10th (ish) set 
> of batteries now!
>
> I tried to press down arrow for 4 seconds, but has no effect (backlight 
> goes off, about it).
>
> I tried to remove batteries for about 30 minutes yesterday (so I could 
> give whole thing a good clean). And they died at some point in middle of 
> night anyhow.
>
> Manual also says it will attempt to reconnect every hour, and I've so far 
> left it for almost a whole day and still no connection.
>
> Any other ideas?
>
> Many thanks.
>
> On Fri, 21 Aug 2020, 05:07 Andrew Milner,  > wrote:
>
>> read the manual - there is a button to press (i forget which) to regain 
>> communications.  Just looked - press and hold the down key for 4 seconds 
>> until the console beeps.
>>
>> Register transmitter If no outdoor weather data is displayed or the 
>> signal to the sensors is lost during setting up, mounting, changing of 
>> batteries to the sensor or plugging or unplugging cables, simply press and 
>> hold the DOWN/- key for 4 seconds and a short beep will sound to 
>> synchronize the base station to sensors. Without being synchronized, 
>> weather data will not be received. NOTE: Wait two minutes before re-insert 
>> the batteries of transmitter for proper reset. Note: The best condition for 
>> reception is at night, between midnight and 6:00am – when there is less 
>> atmospheric interference.
>>
>>
>>
>> On Thursday, 20 August 2020 21:10:43 UTC+3, James Muirhead wrote:
>>>
>>> My WH1080 sender / receiver appears to have died. 
>>>
>>> The battery low indicator had been on for some time and died about 0130 
>>> this morning.
>>>
>>> I changed out the batteries in the sender today and it does not want to 
>>> communicate with the receiver now. LED in the sender comes on and receiver 
>>> appears normal.
>>>
>>> I've reset receiver and sender in both orders and left for an hour, etc, 
>>> etc. WeeWX WebUI shows no signal (but I don't know how this is generated).
>>>
>>> The communication icon on receiver comes up sporadically for a minute at 
>>> start and for quarter of a second once in a while.
>>>
>>> I'm gonna take apart the sender tomorrow and give everything a good 
>>> clean, see if it helps.
>>>
>>> Has anyone got a suggestion, other than "buy a new weather station"?
>>>
>>> Thanks.
>>>
>>> PS - WeeWX is working perfectly. But I have WeeWX installed on an Orange 
>>> Pi PC (1.3GHz Quad, 1GB RAM). Shout if you want anymore information.
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/ySocUy01e_M/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/7cffbaeb-c08c-4ddc-b0cc-ce4cda005b6do%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/7cffbaeb-c08c-4ddc-b0cc-ce4cda005b6do%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/32d5f35a-9cda-4fb4-b153-3bf907ea8575o%40googlegroups.com.

[weewx-user] Re: Forecast skin stopped working

[Andrew Milner]

posting your log may help identify any problems


On Saturday, 29 August 2020 16:53:43 UTC+3, Timothy Buchanan wrote:
>
> I I've been using Forecast within a modified exfoliation skin with no 
> problems until it stopped fetching the forecasts. I use NWS and Open 
> Weather and these dwindled from a seven day to five, three, one, then none. 
> Running the Forecast skin gives the same non-result.  Where would I look 
> for the problem? I tried an uninstall/reinstall to no avail. Thanks for 
> help.
>
> Timothy 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ab106499-53e4-496d-9c7a-0a2ec3951d88o%40googlegroups.com.

[weewx-user] Re: New User trying Rpi Install with Errors

[Andrew Milner]

what does the log say???



On Thursday, 3 September 2020 08:21:00 UTC+3, lodewyk...@gmail.com wrote:
>
> Hi Everyone,
>
> I just can seem to get my WeeWX to run smoothly. I installed everything 
> and it was running fine a month ago (in the office). So thinking everything 
> was good I deployed the weather station (Davis Vantage Vue) outside for a 
> month. 
> When I tried to look for the data the archive stopped before I deployed 
> the logger outside but in the office, it worked again. So I deployed it 
> again and the something but now it doesn't want to work at all. 
>
> I reinstalled Weewx but no luck even formatted the SD card and reinstalled 
> but no luck. 
>
> Is there something I am missing? 
>
>
>
> On Wednesday, August 26, 2020 at 7:25:58 AM UTC+12 damc...@gmail.com 
> wrote:
>
>> Think I have this solved now. Finally found that the Weewx install would 
>> not work because I have a Davis Weatherlink Live in use. Had to add another 
>> driver for WLL. Found this at https://github.com/jonotaegi/weewx-wll. 
>> Thanks to Vince here and jonotaegi
>>
>> On Tuesday, August 25, 2020 at 11:25:06 AM UTC-7 Dennis Clark wrote:
>>
>>> Always a possibility but I have gone back in terminal to review all my 
>>> commands and it looks like sudo was always used. using ssh for everything 
>>> as I dont have an external monitor.
>>>
>>> i.e. sudo apt-get install weewx
>>> Went through the setup dialogs then
>>>
>>> sudo tail -f /var/log/syslog. was used to get errors shown in last post.
>>>
>>>
>>> I am at the point of doing a fresh install of the pi followed by all the 
>>> weewx install steps again.
>>>
>>>
>>>
>>> On Tuesday, August 25, 2020 at 11:16:53 AM UTC-7 vince wrote:
>>>
 On Tuesday, August 25, 2020 at 9:11:55 AM UTC-7, Dennis Clark wrote:
>
> So yes, found I omitted the comma between latitude and longitude. 
> Tried a new install with correctly added comma and now it apperas I may 
> have it narrowed down to some sort of permissions error???
> When I did a manual weeconfig --reconfigure to check things out it 
> errors after entering the IP of my Weatherlink.
> Any thoughts ?
>
>
 Permission denied on a pi, for new pi users especially, is always the 
 user forgetting to preface their commands with 'sudo' 

>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/fc9290b3-345e-475a-b0e2-94c1ebee3690o%40googlegroups.com.

Re: [weewx-user] Re: New User trying Rpi Install with Errors

[Andrew Milner]

you appear to have a voltage issue - nothing to do with weewx - check with 
the pi forums.  Check your power supply and make sure you are using a beefy 
enough one.  if using usb to power devices use a powered usb hub.  
otherwise all looks good from the weewx point of view.




On Friday, 4 September 2020 06:07:20 UTC+3, Graham Eddy wrote:
>
> selected some lines from log, shown below. 
> looks like RPi is reporting under-voltage THEN a high-speed usb hard drive 
> is added on top of that... 
> weewx not reporting problems but not surprised if strange things are 
> happening 
>
> but, repeating: weewx not reporting errors, images are being generated, so 
> i don’t know what is being reported as the problem 
> --- 
>
> Sep  4 07:14:52 raspberrypi kernel: [   10.716358] Under-voltage detected! 
> (0x00050005) 
> Sep  4 07:15:09 raspberrypi kernel: [   27.356236] Voltage normalised 
> (0x) 
> Sep  4 07:15:20 raspberrypi weewx[517] INFO weewx.manager: Added record 
> 2020-08-05 07:15:00 NZST (1596568500) to database 'weewx.sdb' 
> Sep  4 08:22:54 raspberrypi systemd-timesyncd[309]: Synchronized to time 
> server for the first time 46.40.123.212:123 (2.debian.pool.ntp.org). 
> Sep  4 08:22:54 raspberrypi kernel: [   39.836265] Under-voltage detected! 
> (0x00050005) 
> Sep  4 08:22:59 raspberrypi kernel: [   43.996306] Voltage normalised 
> (0x) 
> Sep  4 08:23:03 raspberrypi kernel: [   48.156305] Under-voltage detected! 
> (0x00050005) 
> Sep  4 08:23:09 raspberrypi kernel: [   54.396218] Voltage normalised 
> (0x) 
> Sep  4 08:26:21 raspberrypi gvfsd[629]: mkdir failed on directory 
> /var/cache/samba: Permission denied 
> Sep  4 08:27:56 raspberrypi kernel: [  341.439091] 
> rpi_firmware_get_throttled: 4 callbacks suppressed 
> Sep  4 08:27:56 raspberrypi kernel: [  341.439098] Voltage normalised 
> (0x) 
> Sep  4 08:28:00 raspberrypi kernel: [  345.599302] 
> rpi_firmware_get_throttled: 5 callbacks suppressed 
> Sep  4 08:28:00 raspberrypi kernel: [  345.599317] Under-voltage detected! 
> (0x00050005) 
> Sep  4 08:28:06 raspberrypi kernel: [  351.839299] Voltage normalised 
> (0x) 
> Sep  4 08:28:11 raspberrypi kernel: [  355.999447] Under-voltage detected! 
> (0x00050005) 
> Sep  4 08:28:44 raspberrypi kernel: [  389.279727] Voltage normalised 
> (0x) 
> Sep  4 08:28:48 raspberrypi kernel: [  393.439877] Under-voltage detected! 
> (0x00050005) 
> Sep  4 08:29:30 raspberrypi kernel: [  435.610099] usb 1-1.2: new 
> high-speed USB device number 6 using dwc_otg 
> Sep  4 08:29:30 raspberrypi weewx[517] INFO weewx.manager: Added record 
> 2020-08-28 18:15:00 NZST (1598595300) to database 'weewx.sdb' 
> Sep  4 08:29:30 raspberrypi weewx[517] INFO weewx.manager: Added record 
> 2020-08-28 18:15:00 NZST (1598595300) to daily summary in 'weewx.sdb' 
> Sep  4 08:29:30 raspberrypi kernel: [  435.821976] usb 1-1.2: New USB 
> device found, idVendor=0bc2, idProduct=231a, bcdDevice= 7.10 
> Sep  4 08:29:30 raspberrypi kernel: [  435.822028] usb 1-1.2: New USB 
> device strings: Mfr=1, Product=2, SerialNumber=3 
> Sep  4 08:29:30 raspberrypi kernel: [  435.822042] usb 1-1.2: Product: 
> Expansion 
> Sep  4 08:29:30 raspberrypi kernel: [  435.822057] usb 1-1.2: 
> Manufacturer: Seagate 
> Sep  4 08:29:30 raspberrypi kernel: [  435.822070] usb 1-1.2: 
> SerialNumber: NAA8Q86P 
> Sep  4 08:29:30 raspberrypi kernel: [  435.823355] usb 1-1.2: The driver 
> for the USB controller dwc_otg_hcd does not support scatter-gather which is 
> Sep  4 08:29:30 raspberrypi kernel: [  435.823406] usb 1-1.2: required by 
> the UAS driver. Please try an other USB controller if you wish to use UAS. 
> Sep  4 08:29:30 raspberrypi kernel: [  435.823422] usb-storage 1-1.2:1.0: 
> USB Mass Storage device detected 
> Sep  4 08:29:30 raspberrypi kernel: [  435.843662] scsi host0: usb-storage 
> 1-1.2:1.0 
> Sep  4 08:29:31 raspberrypi mtp-probe: checking bus 1, device 6: 
> "/sys/devices/platform/soc/3f98.usb/usb1/1-1/1-1.2" 
> Sep  4 08:29:31 raspberrypi mtp-probe: bus: 1, device: 6 was not an MTP 
> device 
> Sep  4 08:29:31 raspberrypi kernel: [  436.067373] usbcore: registered new 
> interface driver uas 
> Sep  4 08:29:31 raspberrypi weewx[517] INFO weewx.manager: Added record 
> 2020-08-28 18:30:00 NZST (1598596200) to database 'weewx.sdb' 
> Sep  4 08:29:37 raspberrypi udisksd[383]: The disk contains an unclean 
> file system (0, 0). 
> Sep  4 08:29:37 raspberrypi udisksd[383]: The file system wasn't safely 
> closed on Windows. Fixing. 
> Sep  4 08:30:04 raspberrypi ntfs-3g[1701]: Version 2017.3.23AR.3 
> integrated FUSE 28 
> Sep  4 08:30:04 raspberrypi ntfs-3g[1701]: Mounted /dev/sda1 (Read-Write, 
> label "Seagate Expansion Drive", NTFS 3.1) 
> Sep  4 08:30:04 raspberrypi ntfs-3g[1701]: Cmdline options: 
> rw,nodev,nosuid,uid=1000,gid=1000,uhelper=udisks2 
> Sep  4 08:30:04 raspberrypi ntfs-3g[1701]: Mount options: 
> nodev,nosuid,uhelper=udisks2,allow_other,none

[weewx-user] Re: Generating multiple web pages simultaneously

[Andrew Milner]

yes


On Sunday, 6 September 2020 06:56:08 UTC+3, ExprmntAl wrote:
>
> Will WeeWx produce multiple web pages simultaneously?  I would like to set 
> it up to run Belchertown + Weather34 + the default Seasons Skin all at the 
> same time.
>
> I'm pretty sure the answer is yes, but I am about to try out the weather34 
> install and want to leave the seasons skin going at the same time.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4740bb81-603b-4710-af5d-90700aed4d71o%40googlegroups.com.

Re: [weewx-user] weewx-Weather34 installation questions

[Andrew Milner]

try the ip address of the php enabled web server if it is local on your 
network or the external URL to the web host if extenal



On Thursday, 10 September 2020 15:36:58 UTC+3, ExprmntAl wrote:
>
> Hi Glen.  Thanks for trying to help me out.   
>
> You need to access that file via
> http://your_web_server_with_php_enabled/weewx/weather34/index.php  
>
> Can you give me an example of what this would look like?  I don't know 
> what to use for the "your_web_server_with_php_enabled 
> " 
> portion of the address.  Though I didn't mention it, I have tried "
> http://www/html/weewx/weather34/index.ph 
> p 
> " in 
> Chromium on the RPi and this did not work either.  
>
> On Thursday, September 10, 2020 at 6:06:56 AM UTC-5 Glenn McKechnie wrote:
>
>> On 10/09/2020, ExprmntAl <72604...@compuserve.com> wrote: 
>> > Tried your suggestion and still no go. See below. 
>> > 
>> > *pi@raspberrypi:~ $ sudo apt-get install libapache2-mod-php* 
>> > *Reading package lists... Done* 
>> > *Building dependency tree* 
>> > *Reading state information... Done* 
>> > *libapache2-mod-php is already the newest version (2:7.3+69).* 
>> > *The following packages were automatically installed and are no longer 
>> > required:* 
>> > * libexiv2-14 libgfortran3 libgmime-2.6-0 libncurses5 libssl1.0.2 
>> > rpi-eeprom-images* 
>> > *Use 'sudo apt autoremove' to remove them.* 
>> > *0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.* 
>> > *pi@raspberrypi:~ $ sudo a2enmod php7.3* 
>> > *Considering dependency mpm_prefork for php7.3:* 
>> > *Considering conflict mpm_event for mpm_prefork:* 
>> > *Considering conflict mpm_worker for mpm_prefork:* 
>> > *Module mpm_prefork already enabled* 
>> > *Considering conflict php5 for php7.3:* 
>> > *Module php7.3 already enabled* 
>> > *pi@raspberrypi:~ $ sudo systemctl restart apache2* 
>> > *pi@raspberrypi:~ $ * 
>>
>> Everything you have done above allows a php file to be executed by 
>> your webserver and therefore the html content generated and displayed 
>> in the browser that views it. 
>>
>> > This is how I am entering the address in Chromium on the RPi. 
>> > 
>> > file://www/html/weewx/weather34/index.php 
>>
>> That's never going to work. 
>>
>> When you use the file:// method of browser access you are accessing 
>> the file via your filesystem. You are bypassing the php interpreter 
>> that you installed on your webserver. The browser does not know what 
>> to do with it, so it displays it (the php contents) Nothing gets 
>> executed. Nothing has been converted to html. 
>>
>> You need to access that file via 
>> http://your_web_server_with_php_enabled/weewx/weather34/index.php 
>>
>> > The address "file://www/html/weewx/index.html" seams to work fine for 
>> the 
>> > seasons skin so I have been going off the assumption that a similar 
>> address 
>>
>> It's a html file, the browser knows what to do with html. It displays it. 
>>
>> > format to the php file should work as well but when I click enter, it 
>> just 
>> > downloads the index.php file instead of opening it in the browser. 
>>
>> Yep, that's exactly what it will do - no interpreter is available. No 
>> html is generated. Access it via your webserver and you will get the 
>> html page it generates. 
>>
>> -- 
>>
>>
>> Cheers 
>> Glenn 
>>
>> rorpi - read only raspberry pi & various weewx addons 
>> https://github.com/glennmckechnie 
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/efbc48c1-6e01-4e07-ba5a-879a8c8149fao%40googlegroups.com.

[weewx-user] Re: Transfer data from an older Versionto 4.1.1

[Andrew Milner]

you do not have to use the new xtended schema with 4.1.1 unless you NEED 
the extra fields.  My first question therefor is @do you need the extra 
fields@??


On Thursday, 15 October 2020 17:55:40 UTC+3, vince wrote:
>
> On Thursday, October 15, 2020 at 7:46:59 AM UTC-7, rolz...@gmail.com 
> wrote:
>
>> can someone please explain me how to get the records from the database of 
>> version 3.9.2 to the database of version 4.1.1. 
>>
>> The current installation (4.1.1) is on a new computer.
>>
>>
> If you have a station with a data logger (such as a Davis), you can simply 
> stop weewx, copy the old database to the new computer, and restart weewx.  
> Weewx will catch up the database with whatever records are in the 
> datalogger.
>
> Or you can dump the old database to a file and restore it to the new 
> database, then rebuild_daily to build the summary tables.
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/da1c5334-49ad-47da-89e9-7502a5873800o%40googlegroups.com.

[weewx-user] Re: Cheetah Rounding Values

[Andrew Milner]

If you are using weewx tags it would be something like
$current.outTemp.format("%.1f") for one decimal place

On Sunday, 26 April 2020 07:54:54 UTC+3, gjr80 wrote:
>
> Rich,
>
> How you format data in a Cheetah generated report really depends on the 
> source of the data. If you are using a WeeWX generated tag, eg 
> $current.outTemp, then you have all the formatting and unit conversion 
> options of a WeeWX tag available to you (as linked by Tom). If the data 
> comes from some inline python in your Cheetah template then you are 
> responsible for formatting the data, for example, if your template had the 
> following:
>
> #set $pie_temperature = 22/7
>
> and you wanted to use $pie_temperature in your template then you would be 
> responsible for formatting the output, you might do something like:
>
> #set $pie_temperature_2d = round($pie_temperature, 2)
>
> and then use $pie_temperature_2d to display $pie_temperature to two 
> decimal places (or you might just have used #set $pie_temperature = 
> round(22/7, 2) up front). Bottom line is, formatting/unit conversion etc 
> is your problem, not WeeWX'
>
> If your data comes from a Search List Extension (SLE) then it depends on 
> what the SLE provides. Let's say the SLE provides a tag $pie_temp that is 
> a temperature. If $pie_temp is just a number then just like 
> $pie_temperature you need to format it yourself. However, is the SLE is a 
> little more sophisticated and provides $pie_temp as a special WeeWX 
> object known as a ValueHelper, then $pie_temp has all of the formatting 
> and unit conversion abilities of a WeeWX tag such as $current.outTemp. 
> Generally speaking it is quite easy to have a SLE return a ValueHelper(), 
> whilst it does make the SLE code a little more complex it provides for a 
> much more flexible output. 
>
> At the end of the day a SLE does not allow formatting per se, rather it is 
> the type of output from a SLE that determines what formatting/unit 
> conversion is available. Have a read of the section Defining new tags 
>  in the 
> Customization Guide, it covers ValueHelpers and SLEs with examples.
>
> Gary
>
> On Sunday, 26 April 2020 14:29:11 UTC+10, rich T wrote:
>>
>> Thanks I tried your suggestions, but still does not round to the decimal 
>> point. I did create a new tag. Do I need to create a new search list 
>> extension to allow formatting?
>>
>> Thanks 
>> Rich
>>
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d198e5e0-dca1-4c2b-b5eb-eda02b5316e9%40googlegroups.com.

Re: [weewx-user] Raspberry pi USB disconnects

[Andrew Milner]

what model pi are you using?
are you using a separate powered usb hub or one of the ports on the rpi?




On Tuesday, 28 April 2020 07:14:05 UTC+3, Praveen Chandrasekaran wrote:
>
> Attached output of lsusb.
>
> I dont see anything in lsof output probably because nothing is using it at 
> the moment (shouldnt weewx be using it continuously in rapidfire mode?)
>
> Also can I edit weewx to add lsob whenever the error occurs?
>
> On Tue, 28 Apr 2020 at 01:04, Tom Keffer > 
> wrote:
>
>> Things to try:
>>
>> 1. Ferrite coils might help, although you are getting a lot more errors 
>> than what is normally associated with EMI.
>>
>> 2, Another possibility is that something else is trying to claim 
>> /dev/ttyUSB0. For example, modemmanager has been known to do this.
>>
>> To see a list of processes using /dev/ttyUSB0. 
>>
>> lsof | grep ttyUSB0
>>
>> Unfortunately, this will only tell you if something is using it at the 
>> moment.
>>
>> 3. It's worth looking at the details of your USB connection:
>>
>> lsusb -v -d 0403:6015
>>
>>
>>
>>
>> On Mon, Apr 27, 2020 at 11:04 AM Praveen Chandrasekaran <
>> prave...@gmail.com > wrote:
>>
>>> Attached syslog (all today's entries). The USB disconnect has happened 
>>> around 6 times today). No major issue as it recovers but just wondering 
>>> why. Need to buy a ferrite coil. 
>>>
>>> On Mon, 27 Apr 2020 at 23:24, Praveen Chandrasekaran >> > wrote:
>>>
 Sorry, just ignore the part of serial/USB. I got confused with 
 different data logger types available. Will attached detailed log in a few 
 minutes.

 On Mon, 27 Apr 2020 at 22:07, Tom Keffer >>> > wrote:

> Don't know what you mean by "Mine is a serial port on Vue side."  
>
> "usb issue must be on pi side." Not sure what you're asking here but, 
> yes, the USB plugs into the pi, and that's where the assignment to /dev 
> occurs. 
>
> The very short screenshot you included doesn't offer many clues as to 
> the cause.
>
> The output from 'dmesg' may also give clues.
>
> Yes, ferrite coils tend to help.
>
> -tk
>
>
>
> On Mon, Apr 27, 2020 at 9:13 AM Praveen Chandrasekaran <
> prave...@gmail.com > wrote:
>
>> Thanks. I already hav the udev which is why it auto recovers. Mine is 
>> a serial port on Vue side. So the usb issue must be on pi side I assume? 
>> Ferrite coil should solve the problem?
>>
>> On Mon, 27 Apr 2020, 21:26 Tom Keffer, > > wrote:
>>
>>> See the section *Davis cp2101 converter problems 
>>> *
>>>  in 
>>> the Wiki.  The following section, *Installing a udev script 
>>> *
>>>  shows 
>>> how to solve the problem.
>>>
>>> On Mon, Apr 27, 2020 at 8:24 AM Praveen Chandrasekaran <
>>> prave...@gmail.com > wrote:
>>>
 Hi,

 Weewx log is reporting USB disconnects to Vantage Vue now and then 
 (uploaded snippet, not able to copy from putty to windows)

 It recovers on its own everytime. Any idea why this is happening?

 Regards,
 Praveen


 -- 
 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...@googlegroups.com .
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/41c861bd-6733-4112-b5ef-39289a61d34b%40googlegroups.com
  
 
 .

>>> -- 
>>> You received this message because you are subscribed to a topic in 
>>> the Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/weewx-user/5mAHXO5pLzU/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> weewx...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEAQynSvy_ZThKbaT1DYPGgEahZxUqnCxXLAHCJ0CSMfZg%40mail.gmail.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>>

Re: [weewx-user] Raspberry pi USB disconnects

[Andrew Milner]

will you please stop pushing NUC which is not at all coimparable with an 
RPI - it is like comparing apples to pears.




On Tuesday, 28 April 2020 22:44:37 UTC+3, Rich Altmaier wrote:
>
> Ah, but that NUC order of magnitude cost is equal to how many hours of Pi 
> troubleshooting?   
> Rich
>
>
> On Tuesday, April 28, 2020 at 7:15:02 AM UTC-7, Tom Keffer wrote:
>>
>> A NUC is also an order of magnitude more expensive!
>>
>> Andrew's suggestion of an externally powered USB hub is a good one. A 
>> good power supply for the RPi is also essential.
>>
>> On Tue, Apr 28, 2020 at 7:12 AM 'Rich Altmaier' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>>> Praveen, as I have advised before, consider upgrading to the Intel NUC.  
>>> All USB electrical problems gone!
>>> Yes it costs more. Yes it is 10-20x faster. Yes it is trouble free!
>>> Good luck.
>>> Rich
>>>
>>> -- 
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/1256cab2-9622-49ea-bcfb-d249652b5905%40googlegroups.com
>>> .
>>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d56c47e3-b37d-4cfa-8c19-744dde1f6bb2%40googlegroups.com.

Re: [weewx-user] Re: Mqtt read all information

[Andrew Milner]

did you install it??  have you tried using sudo??



On Tuesday, 12 May 2020 08:42:07 UTC+3, Wifi75 wrote:
>
> I don't have comand mosquitto_sub.
> why?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d5fdf049-8474-4f35-9ae2-52cbe786d243%40googlegroups.com.

[weewx-user] suggestion for a future release

[Andrew Milner]

I have seen many posts where there has been confusion or doubt as to how 
weewx has been installed or updated.  As a suggestion would it not be good 
idea for this information to be included in weewx.conf together with the 
version.
ie if installing or updating via setup.py this is included together with 
the current version (and ideally the previous version)
and similarly if using one of the other installes / updaters.
Just a thought for a future release/update

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8d14ca3a-91a2-4835-ba27-aeb043f73fa4%40googlegroups.com.

[weewx-user] Re: Noticed that the statistics.html page giving wrong data.

[Andrew Milner]

very hard to say from the screenshot!!  Do you have any rain recorded for 
between september 2019 and january 2020 which you believe should be added 
to the rain year total??

On Friday, 15 May 2020 08:49:14 UTC+3, Banana Bob wrote:
>
> [image: Screenshot from 2020-05-15 17-46-11.png]
> Please look at the screenshot and notice that the Year and the Rain Year 
> columns give the same data. I suspect that this is not correct. 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/40500c3d-b6c6-48eb-aaa2-9a5b7db4a7eb%40googlegroups.com.

[weewx-user] Re: Noticed that the statistics.html page giving wrong data.

[Andrew Milner]

Oh - I see what you mean - the year column and the rain year column are 
showing same values for ALL readings.

Doesn't that just imply that your rain year start is set to start January 
1st rather than to some date in 2019??



On Friday, 15 May 2020 09:06:19 UTC+3, Banana Bob wrote:
>
> If you right click on the screenshot and select view image you will get a 
> large version. It will show exactly what I said that the last row contains 
> the same data as the previous row.
>
> On Friday, 15 May 2020 18:01:39 UTC+12, Andrew Milner wrote:
>>
>> very hard to say from the screenshot!!  Do you have any rain recorded for 
>> between september 2019 and january 2020 which you believe should be added 
>> to the rain year total??
>>
>> On Friday, 15 May 2020 08:49:14 UTC+3, Banana Bob wrote:
>>>
>>> [image: Screenshot from 2020-05-15 17-46-11.png]
>>> Please look at the screenshot and notice that the Year and the Rain Year 
>>> columns give the same data. I suspect that this is not correct. 
>>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/93746b89-7e64-48c4-a2ce-07dec4f80e95%40googlegroups.com.

[weewx-user] Re: Noticed that the statistics.html page giving wrong data.

[Andrew Milner]

rain_year_start is a date set in weewx.conf - in the station_url section, 
and should be set to the month in which the rain year starts.

the rain year is then the period from rain year start to current date

so yes, i think you are misreading the column - the column represents a 
time period



On Friday, 15 May 2020 09:24:27 UTC+3, Banana Bob wrote:
>
> Sorry but maybe I am reading this page incorrectly. I was assuming that 
> Rain Year was a column for how much Rain fell in the year. Does it have 
> another meaning? 
>
> On Friday, 15 May 2020 18:18:10 UTC+12, Andrew Milner wrote:
>>
>> Oh - I see what you mean - the year column and the rain year column are 
>> showing same values for ALL readings.
>>
>> Doesn't that just imply that your rain year start is set to start January 
>> 1st rather than to some date in 2019??
>>
>>
>>
>> On Friday, 15 May 2020 09:06:19 UTC+3, Banana Bob wrote:
>>>
>>> If you right click on the screenshot and select view image you will get 
>>> a large version. It will show exactly what I said that the last row 
>>> contains the same data as the previous row.
>>>
>>> On Friday, 15 May 2020 18:01:39 UTC+12, Andrew Milner wrote:
>>>>
>>>> very hard to say from the screenshot!!  Do you have any rain recorded 
>>>> for between september 2019 and january 2020 which you believe should be 
>>>> added to the rain year total??
>>>>
>>>> On Friday, 15 May 2020 08:49:14 UTC+3, Banana Bob wrote:
>>>>>
>>>>> [image: Screenshot from 2020-05-15 17-46-11.png]
>>>>> Please look at the screenshot and notice that the Year and the Rain 
>>>>> Year columns give the same data. I suspect that this is not correct. 
>>>>>
>>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2655282c-f1e3-4385-a5b7-f211e6cb02a0%40googlegroups.com.

[weewx-user] Re: Noticed that the statistics.html page giving wrong data.

[Andrew Milner]

countries often measure annual rainfall as being the 12 monthes from the 
start of the rainy period (often september) rather than the annual calender 
period from january 1.  weewx caters for this by allowing the user to 
define the month when the annual period should start, in this case the 
reported annual rainfall will be for the current rain year rather than the 
calendar year.  If you want your rain year to start in september edit 
weewx.cong rain_year_start to be 9 rather than the default 1 (=january), 
and then you will see the two columns (year and rain year) will contain 
different values, one will be measuring from start of calendar year and one 
from start of rain year (as defined in weewx.conf).  Rain year is thus the 
timespan from from start of current rain year.



On Friday, 15 May 2020 10:38:52 UTC+3, Banana Bob wrote:
>
> Andrew
> Thanks very much for your help
> What does the term Rain Year mean?
> James
>
> On Friday, 15 May 2020 18:35:05 UTC+12, Andrew Milner wrote:
>>
>> rain_year_start is a date set in weewx.conf - in the station_url section, 
>> and should be set to the month in which the rain year starts.
>>
>> the rain year is then the period from rain year start to current date
>>
>> so yes, i think you are misreading the column - the column represents a 
>> time period
>>
>>
>>
>> On Friday, 15 May 2020 09:24:27 UTC+3, Banana Bob wrote:
>>>
>>> Sorry but maybe I am reading this page incorrectly. I was assuming that 
>>> Rain Year was a column for how much Rain fell in the year. Does it have 
>>> another meaning? 
>>>
>>> On Friday, 15 May 2020 18:18:10 UTC+12, Andrew Milner wrote:
>>>>
>>>> Oh - I see what you mean - the year column and the rain year column are 
>>>> showing same values for ALL readings.
>>>>
>>>> Doesn't that just imply that your rain year start is set to start 
>>>> January 1st rather than to some date in 2019??
>>>>
>>>>
>>>>
>>>> On Friday, 15 May 2020 09:06:19 UTC+3, Banana Bob wrote:
>>>>>
>>>>> If you right click on the screenshot and select view image you will 
>>>>> get a large version. It will show exactly what I said that the last row 
>>>>> contains the same data as the previous row.
>>>>>
>>>>> On Friday, 15 May 2020 18:01:39 UTC+12, Andrew Milner wrote:
>>>>>>
>>>>>> very hard to say from the screenshot!!  Do you have any rain recorded 
>>>>>> for between september 2019 and january 2020 which you believe should be 
>>>>>> added to the rain year total??
>>>>>>
>>>>>> On Friday, 15 May 2020 08:49:14 UTC+3, Banana Bob wrote:
>>>>>>>
>>>>>>> [image: Screenshot from 2020-05-15 17-46-11.png]
>>>>>>> Please look at the screenshot and notice that the Year and the Rain 
>>>>>>> Year columns give the same data. I suspect that this is not correct. 
>>>>>>>
>>>>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/60bb32f8-13d0-4f67-b346-dec9ad397321%40googlegroups.com.

[weewx-user] Re: Belchertown Graph Error

[Andrew Milner]

I think you have a mismatch between OutTempBatteryStatus in the chartcode 
and outTempBatteryStatus which is the name in the database.  Change the O 
to an o






On Sunday, 17 May 2020 16:07:45 UTC+3, Ron Sell wrote:
>
> Anyone see this error:
>
> Weewx 4.0:
> Belchertown 1.1
>
> The database has those fields:
>
> 107|windBatteryStatus|REAL|0||0
> 69|outTempBatteryStatus|REAL|0||0
>
> Chart Code:
> [[Battery]]
> title = Battery Status
> [[[OutTempBatteryStatus]]]
> name = Air Battery
> zIndex = 1
> color = blue
> [[[windBatteryStatus]]]
> name = Sky Battery
> color = gray
>
> Error Log:
> pi@raspberrypi:~ $ sudo wee_reports
> Using configuration file /etc/weewx/weewx.conf
> Generating for all time
> Traceback (most recent call last):
>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
> obj.start()
>   File "/usr/share/weewx/weewx/reportengine.py", line 280, in start
> self.run()
>   File "/usr/share/weewx/user/belchertown.py", line 1374, in run
> series_data = self.get_observation_data(binding, archive, 
> observation_type, minstamp, maxstamp, aggregate_type, aggregate_interval, 
> time_length, xAxis_groupby, xAxis_categories, mirrored_value, 
> weatherRange_obs_lookup)
>   File "/usr/share/weewx/user/belchertown.py", line 1827, in 
> get_observation_data
> raise Warning( "Error trying to use database binding %s to graph 
> observation %s. Error was: %s." % (binding, obs_lookup, e) )
> Warning: Error trying to use database binding wx_binding to graph 
> observation OutTempBatteryStatus. Error was: OutTempBatteryStatus.
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/61fb1bd4-afd8-40c9-903f-9a36f05040b5%40googlegroups.com.

[weewx-user] Re: TE923 Nexus: daily max. wind gust on WU and weewx website

[Andrew Milner]

try and set loop_hilo = true in [StdArchive] which will then store loop 
values as highs and lows.  The default is to use only the archive records.  
This should give you the mmissing values.


On Wednesday, 27 May 2020 19:46:51 UTC+3, Felix Maltzahn wrote:
>
> Hello,
>
> I have a little problem with my RPI and TE923 TFA Nexus...
>
> The daily max wind gust (shown on the weather stations display) is all 
> time much higher than the value uploaded on WU, PWS, Awekas or on the weewx 
> generated website.
> The archive interval is set to 60 seconds. The update intval on the TE923 
> for wind data is 33 seconds. I think a lot of gusts are simply missed... 
> Is there any solution available?
>
> With wee_device --minmax I can read the correct daily max gust value... 
> But how can I use this for my website and for my upload to WU, Awekas 
> etc??
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5c4a2c9d-a1c0-40b3-b827-f69b7a1904c1%40googlegroups.com.

Re: [weewx-user] Wrong wind speeds on AWEKAS

[Andrew Milner]

I don't think anyone measures rain in cm ..



On Monday, 1 June 2020 15:31:20 UTC+3, gjr80 wrote:
>
> I’d really like to find that fella that measures his rain in cm, he has a 
> lot to answer for :) 
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/395f3220-0652-4bfb-a5b5-0709fa83165a%40googlegroups.com.

Re: [weewx-user] Wrong wind speeds on AWEKAS

[Andrew Milner]

but that chart seems more to be a derived unit - how about when dealing 
with local or even regional weather reporting rather than global ocean 
contributions ...


On Monday, 1 June 2020 17:50:19 UTC+3, Tom Keffer wrote:
>
> I don't think anyone measures rain in cm ..
>
>
> Not true at all. I'm probably showing my bias as an earth scientist, but 
> we *only* measured precip and evaporation in centimeters. Example map 
> below, from Ray Schmitt, a friend and former colleague at the Woods Hole 
> Oceanographic.
>
> [image: image.png]
>
> On Mon, Jun 1, 2020 at 7:36 AM Andrew Milner  > wrote:
>
>> I don't think anyone measures rain in cm ..
>>
>>
>>
>> On Monday, 1 June 2020 15:31:20 UTC+3, gjr80 wrote:
>>>
>>> I’d really like to find that fella that measures his rain in cm, he has 
>>> a lot to answer for :) 
>>>
>>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/395f3220-0652-4bfb-a5b5-0709fa83165a%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/395f3220-0652-4bfb-a5b5-0709fa83165a%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/28b9cb1c-a996-43fb-8dfd-801a33b378ce%40googlegroups.com.

[weewx-user] Re: Registering on weewx map.

[Andrew Milner]

It can take up to a week to actually register on the site.




On Wednesday, 3 June 2020 08:56:18 UTC+3, Bent Jensen wrote:
>
> Hi again
>
> I just wanted for the fun to see if my Weewx station was registered on the 
> Weewx map. But it is not!
>
> I checked if I had set the station_register variable to true, which I had. 
> And according to the documentation that should be enough as long as there 
> allready is set a station_url in the [Station] paragraph (which is set 
> to station_url = https://detlillehus.info/weewx).
>
> I have also tried to set a station_url in the paragraph of
> [StdRESTful]
>
> [[StationRegistry]]
>
> And tried with both my own domain and that of WU, but with no change. By 
> the way WU works just fine.
>
> Is there something else I could have done wrong?
>
> Best regards
> Bent (who is awed by 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/75c6fe37-49ef-4f2f-90a8-4b9f85e9ebdb%40googlegroups.com.

[weewx-user] Re: FUN with Windows

[Andrew Milner]

I agree with Vince


On Wednesday, 10 June 2020 01:16:28 UTC+3, vince wrote:
>
> On Tuesday, June 9, 2020 at 2:16:26 PM UTC-7, Xant wrote:
>>
>> Properly posted at WeeWX User's Group, not Development
>>
>
> My opinion - long discussions not relevant to weewx at all aren't properly 
> posted.
> Others of course might differ in opinion, which is fine too.
> Have a nice day.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d2568396-5321-4b63-b642-5feb0ca24b52o%40googlegroups.com.

[weewx-user] Re: Multi-year Graphs

[Andrew Milner]

I have done something similar at
http://andrewmilner.online/Bootstrap/history.html
and it is very useful for comparing one year with another.  I think graphs 
would get cumbersome when there are more than a few previous years of data 
to consider.


On Friday, 3 July 2020 12:55:16 UTC+3, Jarmo Seppänen wrote:
>
> Multiple years as graphs might not work that well as figures. I have 
> resolved this like presented at 
> http://kuusamantie22.altervista.org/history.html 
>
> Wonder if it’d work for you? 
>
> jaMO

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d548f0ac-1922-4e7f-914a-03736a73a54do%40googlegroups.com.

Re: [weewx-user] Re: Apache is not showing /weewx on Ubuntu 16.04.1

[Andrew Milner]

setting station type to simulator effectively creates a station which 
pretends to create data and gives the data to weewx.  weewx then does 
everything it should do with the 'received' data including generate 
reports.  it will also store the dta in the database, so when you have 
finished using simulator you will need to clear out the simulation data 
from the database - usually just deleting the database file is sufficient.


On Monday, 13 July 2020 01:01:25 UTC+3, Michael Grossie wrote:
>
> Andre,
> Thanks for the response - in the [StdReport] section of the weewx.conf, it 
> shows, "where generated reports should go, relative to WEEWX_ROOT  
> HTML_ROOT= public_HTML"
>
> Since the station is set to Simulation, will there be any reports 
> generated?
>
> TIA
>  
>  
> Michael H Grossie
> mhgr...@sbcglobal.net 
>
>
> On Sun, Jul 12, 2020 at 2:41 PM Andre > 
> wrote:
>
>> First, take a look to your weewx.conf
>> Section [StdReport]
>> There is HTML_ROOT = /path/name/path
>>
>> If you have only have one website you can point to your default Apache2 
>> path or you can edit your /etc/apache2/sites-available/000-default.conf
>> After editing restart Apache2 with sudo /etc/init.d/apache2 restart
>>
>>
>> Am Sonntag, 12. Juli 2020 20:59:03 UTC+2 schrieb Michael Grossie:
>>>
>>> Answered one of my questions - I changed the Weather Station to 
>>> Simulator and the weewx/public_HTML folder was created and populated.
>>> However running http://localhost/weewx 
>>> 
>>>   
>>> yields the Page Not Found error.
>>>  
>>>  
>>> Michael H Grossie
>>> mhgr...@sbcglobal.net
>>>
>>>
>>> On Sun, Jul 12, 2020 at 12:18 PM Michael Grossie  
>>> wrote:
>>>
 This is a very old thread - but it relates to my question - with the 
 exception of Ubuntu
 Raspberry Pi 2 B
 Raspbian Stretch
 Station: Argent WS1

 I have got Apache2 installed, followed the setup and completed the 
 Apache configuration snippet. I have checked and the various files and 
 directories are in place, however I do not find the 
 /home/weewx/public_html 
 file.
 Since I am not connected to active weather instruments at this time, 
 could it be that this file will not be created until the weewx program 
 receives data - 
 the http://localhost/weewx  gives me a 404 page not found error.

 TIA

 On Friday, September 16, 2016 at 2:28:31 PM UTC-5 valken...@gmail.com 
 wrote:

> How did you guys configure Apache?
> Apache2 for instance is able to serve multiple/different sites from 
> different directories based on the requesting url.
>
> I created a virtualhost in Apache based on the url, which tells Apache 
> to serve the weewx pages from the directory where they are located.
> You could read this:
> https://help.ubuntu.com/lts/serverguide/httpd.html
>
> i placed 
>
> DocumentRoot /var/www/weewx
>
> In the configuration file for the site, and this works
>
> -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups "weewx-user" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/weewx-user/kzXjvLjWI-k/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 weewx...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/7ff66258-27e1-4418-83c2-11ed49e5c77an%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/kzXjvLjWI-k/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/0a0eeb25-e5b4-4767-a254-92168ff6ed72o%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1b232c4f-e536-4ab5-9952-ea862c0576cfo%40googlegroups.com.

Re: [weewx-user] Re: Apache is not showing /weewx on Ubuntu 16.04.1

[Andrew Milner]

if you used setup.py the .sdb file will be in /home/weewx/archive and 
should contain all your simulator data.  It may be useful to edit 
weewx.conf and set debug=1 to get more detailed logging - remember to set 
it back to 0 when you have finished.



On Monday, 13 July 2020 16:58:38 UTC+3, Michael Grossie wrote:
>
> Andrew,
>
> Thanks for the response - That answered my question regarding the 
> Simulator Station. I now need to find out where the data it is generating 
> is going. 
>  
>  
> Michael H Grossie
> mhgr...@sbcglobal.net 
>
>
> On Mon, Jul 13, 2020 at 12:18 AM Andrew Milner  > wrote:
>
>> setting station type to simulator effectively creates a station which 
>> pretends to create data and gives the data to weewx.  weewx then does 
>> everything it should do with the 'received' data including generate 
>> reports.  it will also store the dta in the database, so when you have 
>> finished using simulator you will need to clear out the simulation data 
>> from the database - usually just deleting the database file is sufficient.
>>
>>
>> On Monday, 13 July 2020 01:01:25 UTC+3, Michael Grossie wrote:
>>>
>>> Andre,
>>> Thanks for the response - in the [StdReport] section of the weewx.conf, 
>>> it shows, "where generated reports should go, relative to WEEWX_ROOT  
>>> HTML_ROOT= public_HTML"
>>>
>>> Since the station is set to Simulation, will there be any reports 
>>> generated?
>>>
>>> TIA
>>>  
>>>  
>>> Michael H Grossie
>>> mhgr...@sbcglobal.net
>>>
>>>
>>> On Sun, Jul 12, 2020 at 2:41 PM Andre  wrote:
>>>
>>>> First, take a look to your weewx.conf
>>>> Section [StdReport]
>>>> There is HTML_ROOT = /path/name/path
>>>>
>>>> If you have only have one website you can point to your default 
>>>> Apache2 path or you can edit your 
>>>> /etc/apache2/sites-available/000-default.conf
>>>> After editing restart Apache2 with sudo /etc/init.d/apache2 restart
>>>>
>>>>
>>>> Am Sonntag, 12. Juli 2020 20:59:03 UTC+2 schrieb Michael Grossie:
>>>>>
>>>>> Answered one of my questions - I changed the Weather Station to 
>>>>> Simulator and the weewx/public_HTML folder was created and populated.
>>>>> However running http://localhost/weewx 
>>>>> <http://www.google.com/url?q=http%3A%2F%2Flocalhost%2Fweewx&sa=D&sntz=1&usg=AFQjCNHBxcaES0Yn82J1BxYpDZCPLsAvGg>
>>>>>   
>>>>> yields the Page Not Found error.
>>>>>  
>>>>>  
>>>>> Michael H Grossie
>>>>> mhgr...@sbcglobal.net
>>>>>
>>>>>
>>>>> On Sun, Jul 12, 2020 at 12:18 PM Michael Grossie  
>>>>> wrote:
>>>>>
>>>>>> This is a very old thread - but it relates to my question - with the 
>>>>>> exception of Ubuntu
>>>>>> Raspberry Pi 2 B
>>>>>> Raspbian Stretch
>>>>>> Station: Argent WS1
>>>>>>
>>>>>> I have got Apache2 installed, followed the setup and completed the 
>>>>>> Apache configuration snippet. I have checked and the various files and 
>>>>>> directories are in place, however I do not find the 
>>>>>> /home/weewx/public_html 
>>>>>> file.
>>>>>> Since I am not connected to active weather instruments at this time, 
>>>>>> could it be that this file will not be created until the weewx program 
>>>>>> receives data - 
>>>>>> the http://localhost/weewx  gives me a 404 page not found error.
>>>>>>
>>>>>> TIA
>>>>>>
>>>>>> On Friday, September 16, 2016 at 2:28:31 PM UTC-5 valken...@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> How did you guys configure Apache?
>>>>>>> Apache2 for instance is able to serve multiple/different sites from 
>>>>>>> different directories based on the requesting url.
>>>>>>>
>>>>>>> I created a virtualhost in Apache based on the url, which tells 
>>>>>>> Apache to serve the weewx pages from the directory where they are 
>>>>>>> located.
>>>>>>> You could read this:
>>>>>>> https://help.ubuntu.com/lts/serverguide/httpd.html
&

Re: [weewx-user] Re: Apache is not showing /weewx on Ubuntu 16.04.1

[Andrew Milner]

see documentation
http://weewx.com/docs/usersguide.htm#Where_to_find_things



On Monday, 13 July 2020 17:15:31 UTC+3, Andrew Milner wrote:
>
> if you used setup.py the .sdb file will be in /home/weewx/archive and 
> should contain all your simulator data.  It may be useful to edit 
> weewx.conf and set debug=1 to get more detailed logging - remember to set 
> it back to 0 when you have finished.
>
>
>
> On Monday, 13 July 2020 16:58:38 UTC+3, Michael Grossie wrote:
>>
>> Andrew,
>>
>> Thanks for the response - That answered my question regarding the 
>> Simulator Station. I now need to find out where the data it is generating 
>> is going. 
>>  
>>  
>> Michael H Grossie
>> mhgr...@sbcglobal.net
>>
>>
>> On Mon, Jul 13, 2020 at 12:18 AM Andrew Milner  
>> wrote:
>>
>>> setting station type to simulator effectively creates a station which 
>>> pretends to create data and gives the data to weewx.  weewx then does 
>>> everything it should do with the 'received' data including generate 
>>> reports.  it will also store the dta in the database, so when you have 
>>> finished using simulator you will need to clear out the simulation data 
>>> from the database - usually just deleting the database file is sufficient.
>>>
>>>
>>> On Monday, 13 July 2020 01:01:25 UTC+3, Michael Grossie wrote:
>>>>
>>>> Andre,
>>>> Thanks for the response - in the [StdReport] section of the weewx.conf, 
>>>> it shows, "where generated reports should go, relative to WEEWX_ROOT  
>>>> HTML_ROOT= public_HTML"
>>>>
>>>> Since the station is set to Simulation, will there be any reports 
>>>> generated?
>>>>
>>>> TIA
>>>>  
>>>>  
>>>> Michael H Grossie
>>>> mhgr...@sbcglobal.net
>>>>
>>>>
>>>> On Sun, Jul 12, 2020 at 2:41 PM Andre  wrote:
>>>>
>>>>> First, take a look to your weewx.conf
>>>>> Section [StdReport]
>>>>> There is HTML_ROOT = /path/name/path
>>>>>
>>>>> If you have only have one website you can point to your default 
>>>>> Apache2 path or you can edit your 
>>>>> /etc/apache2/sites-available/000-default.conf
>>>>> After editing restart Apache2 with sudo /etc/init.d/apache2 restart
>>>>>
>>>>>
>>>>> Am Sonntag, 12. Juli 2020 20:59:03 UTC+2 schrieb Michael Grossie:
>>>>>>
>>>>>> Answered one of my questions - I changed the Weather Station to 
>>>>>> Simulator and the weewx/public_HTML folder was created and populated.
>>>>>> However running http://localhost/weewx 
>>>>>> <http://www.google.com/url?q=http%3A%2F%2Flocalhost%2Fweewx&sa=D&sntz=1&usg=AFQjCNHBxcaES0Yn82J1BxYpDZCPLsAvGg>
>>>>>>   
>>>>>> yields the Page Not Found error.
>>>>>>  
>>>>>>  
>>>>>> Michael H Grossie
>>>>>> mhgr...@sbcglobal.net
>>>>>>
>>>>>>
>>>>>> On Sun, Jul 12, 2020 at 12:18 PM Michael Grossie  
>>>>>> wrote:
>>>>>>
>>>>>>> This is a very old thread - but it relates to my question - with the 
>>>>>>> exception of Ubuntu
>>>>>>> Raspberry Pi 2 B
>>>>>>> Raspbian Stretch
>>>>>>> Station: Argent WS1
>>>>>>>
>>>>>>> I have got Apache2 installed, followed the setup and completed the 
>>>>>>> Apache configuration snippet. I have checked and the various files and 
>>>>>>> directories are in place, however I do not find the 
>>>>>>> /home/weewx/public_html 
>>>>>>> file.
>>>>>>> Since I am not connected to active weather instruments at this time, 
>>>>>>> could it be that this file will not be created until the weewx program 
>>>>>>> receives data - 
>>>>>>> the http://localhost/weewx  gives me a 404 page not found error.
>>>>>>>
>>>>>>> TIA
>>>>>>>
>>>>>>> On Friday, September 16, 2016 at 2:28:31 PM UTC-5 
>>>>>>> valken...@gmail.com wrote:
>>>>>>>
>>>>>>>> How did you guys configure Apache?
>>>>

[weewx-user] Re: NOAA error ?

[Andrew Milner]

Your monthly summary is in mm and the daily details are in cm.  What 
exactily is your problem?
Have you been making changes to the NOAA reports??



On Friday, 24 July 2020 07:30:34 UTC+3, Olivier GARNIER wrote:
>
> How is it possible... Look at the total rain of mars...
>
>
> The NOAA-2020-03.txt file :
>
>MONTHLY CLIMATOLOGICAL SUMMARY for mars 2020
>
>
> NAME: Le Plessis Placy, France  
> ELEV: 130 mtresLAT: 49-03.48 NLONG: 002-59.22 E
>
>
>TEMPERATURE (C), RAIN (cm), WIND SPEED (km/h)
>
>  HEAT   COOL AVG
>   MEAN   DEGDEG  WIND 
>   DOM
> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   HIGH   
> TIMEDIR
> ---
>  01
>  02
>  03
>  04
>  05
>  064,37,2  19:572,2  23:57   14,00,0   0,000,00,0  
> 19:57 90
>  076,4   10,8  14:571,1  05:57   11,90,0   0,002,6   10,8  
> 13:57215
>  088,2   10,3  16:445,9  23:25   10,10,0   0,368,6   37,4  
> 14:35198
>  097,6   12,0  15:444,5  04:29   10,70,0   0,107,3   33,5  
> 11:37237
>  10   11,1   14,1  16:567,0  02:057,30,0   0,31   12,4   37,8  
> 01:45201
>  11   13,8   16,3  13:15   11,6  23:544,50,0   0,00   14,8   42,5  
> 11:40203
>  12   10,3   12,9  15:326,0  23:578,00,0   0,15   12,8   35,3  
> 04:22243
>  137,7   12,5  16:034,0  07:22   10,60,0   0,005,7   25,2  
> 09:25227
>  148,0   10,3  17:165,6  07:35   10,30,0   0,104,2   29,5  
> 13:52172
>  15   10,9   16,0  14:596,9  03:227,40,0   0,005,9   32,0  
> 14:35168
>  169,2   12,0  11:216,0  05:309,20,0   0,000,8   15,8  
> 16:25328
>  17   10,5   15,1  16:136,9  07:347,80,0   0,000,18,6  
> 01:25343
>  18   12,7   17,9  15:599,0  00:595,60,0   0,000,3   11,9  
> 14:41191
>  19   13,7   20,1  13:437,6  06:484,60,0   0,000,9   20,2  
> 13:25105
>  20   11,8   16,9  13:387,9  23:576,50,0   0,004,5   30,6  
> 18:09 12
>  217,18,3  14:395,7  07:42   11,20,0   0,057,8   26,6  
> 09:24 27
>  227,6   12,2  17:194,5  08:24   10,70,0   0,007,4   49,0  
> 00:39 20
>  236,4   12,2  15:331,1  07:01   11,90,0   0,003,3   20,5  
> 14:09 13
>  246,4   13,1  17:250,0  06:10   11,90,0   0,001,8   16,2  
> 14:24 23
>  256,6   12,2  16:230,6  06:55   11,80,0   0,002,9   17,6  
> 15:25 22
>  266,2   11,0  15:561,1  06:50   12,10,0   0,004,3   34,6  
> 10:50 23
>  278,0   14,1  15:201,8  07:25   10,40,0   0,002,6   20,2  
> 11:20346
>  289,6   17,1  14:172,0  06:358,80,0   0,004,4   31,0  
> 21:34353
>  296,19,0  14:003,6  07:50   12,20,0   0,009,6   51,8  
> 16:01 11
>  304,8   10,0  16:35   -0,3  08:06   13,50,0   0,008,0   31,3  
> 15:06 24
>  316,5   12,1  16:321,4  07:55   11,90,0   0,003,6   20,9  
> 12:32 24
> ---
>8,7   20,1 19   -0,3 30  255,00,0   1,095,4   51,8 
> 29265
>
>
>
> =
>
> The NOAA-2020.txt file :
>
>   PRECIPITATION (mm)
>
>   MAX ---DAYS OF RAIN---
>   OBS.   OVER
>  YR  MO  TOTALDAY  DATE   0.30   3.00  30.00
> 
> 2020 01
> 2020 02
> 2020 03   10,93,608  6  2  0
> 2020 04   17,67,229  6  3  0
> 2020 05   16,19,310  5  2  0
> 2020 06   49,7   13,027 13  4  0
> 2020 073,62,102  2  0  0
> 2020 08
> 2020 09
> 2020 10
> 2020 11
> 2020 12
> 
>   97,9   13,0   juin 32 11  0
>
>
>
> How can i correct this?
>
> it's because it's the begening of the file ?
>
>
> Thanks,
>
> -- 
> Olivier GARNIER
> La ferme du pré
> 77440 Le Plessis Placy
> +33 (0)6.11.99.92.62
>
>
>
> 
>  Garanti 
> sans virus. www.avast.com 
> 
>  
> <#a0851048-5667-297b-89ad-5b4eb2e7c293@gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

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

[weewx-user] Re: Weewx on RPi Zero

[Andrew Milner]

see the wiki pages regarding RPi and weewx - especially with regards to RTC.



On Monday, 18 November 2019 07:09:47 UTC+2, peter wrote:
>
> Does weewx run OK on RPi Zero W? I want to connect a Vantage Envoy to the 
> USB-on-the-go port.
> Thanks!

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/cedc5149-1058-4113-9b9e-580f45e30033%40googlegroups.com.

[weewx-user] Re: daily graph with point only

[Andrew Milner]

Have you checked 'dots in the plots' in the user guide??

http://weewx.com/docs/usersguide.htm#dots_in_plots



On Monday, 18 November 2019 13:42:11 UTC+2, Inod wrote:
>
>
> Hi 
>
> I just installed weewx on a new server wih a driver vantage , the first 
> graphs that are displayed are composed only of point for the daly report.
> Week and Month are normal
>
>
> Which was not the case with the simulator.
> Is this normal ?
>
> Ubuntu 18.04
> Weewx 3.9.2
>
> thank for your help
>
> [image: graph01.png]
>
>
>
>
>
>
>
>
>
>
>
> [image: graph02.png]
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/264c0e02-71d1-4922-a8f2-a35fc8e4e437%40googlegroups.com.

[weewx-user] Re: Weewx "off line"

[Andrew Milner]

are you running 3.9.2??

search the forum for non-positive value for record field 'interval' and you 
will find many other threads



On Tuesday, 19 November 2019 07:36:37 UTC+2, Teva MERVIN wrote:
>
> Hello.
> I have a problem that I can not identify.
> It happens at least once a day, and I have to restart weewx.
> Do you have ideas?
>
> root@Nas:~# service weewx status
> ● weewx.service - LSB: weewx weather system 
>   Loaded: loaded (/etc/init.d/weewx; generated) 
>   Active: active (exited) since Sun 2019-11-17 19:09:21 +11; 1 day 21h 
> ago 
> Docs: man:systemd-sysv-generator(8) 
>  Process: 2094 ExecStart=/etc/init.d/weewx start (code=exited, 
> status=0/SUCCESS) 
>
> nov. 19 13:34:26 Nas weewx[2110]: File 
> "/usr/share/weewx/weewx/engine.py", line 601, in new_archive_record 
> nov. 19 13:34:26 Nas weewx[2110]:  
>  dbmanager.addRecord(event.record, accumulator=self.old_accumulator) 
> nov. 19 13:34:26 Nas weewx[2110]: File 
> "/usr/share/weewx/weewx/manager.py", line 246, in addRecord 
> nov. 19 13:34:26 Nas weewx[2110]:  
>  self._addSingleRecord(record, cursor, log_level) 
> nov. 19 13:34:26 Nas weewx[2110]: File 
> "/usr/share/weewx/weewx/manager.py", line 1212, in _addSingleRecord 
> nov. 19 13:34:26 Nas weewx[2110]:   _weight = 
> self._calc_weight(record) 
> nov. 19 13:34:26 Nas weewx[2110]: File 
> "/usr/share/weewx/weewx/manager.py", line 1582, in _calc_weight 
> nov. 19 13:34:26 Nas weewx[2110]:   raise 
> ValueError("Non-positive value for record field 'interval': %s" % 
> (record['interval'], )) 
> nov. 19 13:34:26 Nas weewx[2110]:   ValueError: Non-positive 
> value for record field 'interval': 0 
> nov. 19 13:34:26 Nas weewx[2110]:   Exiting.
>
> Thank you.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/937cbea7-28c8-4bb6-95c7-9a6cc43779cd%40googlegroups.com.

Re: [weewx-user] Re: Weewx on RPi Zero

[Andrew Milner]

for what it is worth I do not use a UPS - and we get frequent power outages 
here.  I do use a usb hard drive though instead of the SD card on my rpi.  
Weewx has always recovered the data from my current davis and my earlier 
fineoffset without any issues, so i see no need for a ups.  Anyways 
sometimes our outages are for 3,4,5 hours so it is doubtful the ups would 
keep things running anyway even if I had one.  I do have an RTC installed 
to make sure there are no hiccups in recovering the data from the station 
logger though!!



On Tuesday, 19 November 2019 20:18:46 UTC+2, David VE3STI wrote:
>
> Susan: Do you have a Davis system? The reason I ask is that, from my 
> reading of the comments over the last few years, this 'argument' between 
> the RPi starting up and the weather station hardware may be limited to the 
> Davis systems with their logging interface. Would you be willing to share 
> your coding/scripts/etc with the rest of us? Although I have added an RTC 
> and a UPS, I wish that my system was robust enough to reliably deal with 
> power interruptions without these additions. (The RTC and UPS cost more 
> than the RPi!)
>
> David
>
> On Mon, 18 Nov 2019 at 21:32, Susan Mackay > 
> wrote:
>
>> I use an RPi Zero W for Weewx and Nginx as well.
>> I use systemd to manage it and have pre-requisites that the 'ntp.service' 
>> and 'time-sync.service' have completed before it will start.
>> Susan
>>
>> On Monday, November 18, 2019 at 11:52:38 PM UTC+11, David VE3STI wrote:
>>>
>>> The problems occur during the startup, before the RPi sets its clock 
>>> from the Internet, and appear to be issues with the RPi and the Davis 
>>> equipment disagreeing on the time and getting muddled. It has been the 
>>> topic of much discussion and you can read the gory details in the wiki. I 
>>> won't go into the details here. If you have a UPS and rarely reboot, it 
>>> becomes almost a non-issue.
>>>
>>> David
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/I5C5Wqvtw7c/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/c6136128-8d33-450f-84b0-e70e75c49330%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/44bc2cd3-0c5d-45d1-8f6d-1913424916d0%40googlegroups.com.

[weewx-user] Re: Weewx "off line"

[Andrew Milner]

it was my understanding from one of the threads that there was a version of 
the driver supposed to address this issue - have you used that version of 
the wmr driver??



On Wednesday, 20 November 2019 04:00:18 UTC+2, Teva MERVIN wrote:
>
> Some details of my installation:
>
> - Debian server 5.2.17-1
> - Weewx 3.9.2-0
> - Database: sqlite
> - Skin: Weather34
> - Station: Oregon WMR200
>
> Le mardi 19 novembre 2019 16:36:37 UTC+11, Teva MERVIN a écrit :
>>
>> Hello.
>> I have a problem that I can not identify.
>> It happens at least once a day, and I have to restart weewx.
>> Do you have ideas?
>>
>> root@Nas:~# service weewx status
>> ● weewx.service - LSB: weewx weather system 
>>   Loaded: loaded (/etc/init.d/weewx; generated) 
>>   Active: active (exited) since Sun 2019-11-17 19:09:21 +11; 1 day 21h 
>> ago 
>> Docs: man:systemd-sysv-generator(8) 
>>  Process: 2094 ExecStart=/etc/init.d/weewx start (code=exited, 
>> status=0/SUCCESS) 
>>
>> nov. 19 13:34:26 Nas weewx[2110]: File 
>> "/usr/share/weewx/weewx/engine.py", line 601, in new_archive_record 
>> nov. 19 13:34:26 Nas weewx[2110]:  
>>  dbmanager.addRecord(event.record, accumulator=self.old_accumulator) 
>> nov. 19 13:34:26 Nas weewx[2110]: File 
>> "/usr/share/weewx/weewx/manager.py", line 246, in addRecord 
>> nov. 19 13:34:26 Nas weewx[2110]:  
>>  self._addSingleRecord(record, cursor, log_level) 
>> nov. 19 13:34:26 Nas weewx[2110]: File 
>> "/usr/share/weewx/weewx/manager.py", line 1212, in _addSingleRecord 
>> nov. 19 13:34:26 Nas weewx[2110]:   _weight = 
>> self._calc_weight(record) 
>> nov. 19 13:34:26 Nas weewx[2110]: File 
>> "/usr/share/weewx/weewx/manager.py", line 1582, in _calc_weight 
>> nov. 19 13:34:26 Nas weewx[2110]:   raise 
>> ValueError("Non-positive value for record field 'interval': %s" % 
>> (record['interval'], )) 
>> nov. 19 13:34:26 Nas weewx[2110]:   ValueError: Non-positive 
>> value for record field 'interval': 0 
>> nov. 19 13:34:26 Nas weewx[2110]:   Exiting.
>>
>> Thank you.
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/03d04bfa-faf4-4878-82e0-4b24d21f138a%40googlegroups.com.

[weewx-user] Re: Weewx -> Homepage

[Andrew Milner]

configure the ftp section of standard reports in weewx.conf



On Saturday, 23 November 2019 11:49:59 UTC+2, Michael Stuhldreier wrote:
>
> Hello everyone :-) 
>
> my Weewx is running since 1 year without errors on my raspberry pi 3b+ in 
> my local network and i can open the weather data on http://IP/weewx. 
> Everything okay since here :-) 
>
> But now i want to go online with this Weewx weather station. I can not 
> find a user guide / instruction, how to configure weewx, that every 
> 30minutes a new index.hmtl? file will be uploaded to my webspace. 
>
> How can i do this / configure this in weewx?
>
> Many thanks and best regards from Germany :-) 
>
> Micha
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/81366d36-0155-4cb1-ac7d-67b819e7b8a1%40googlegroups.com.

[weewx-user] Re: bad rain data

[Andrew Milner]

I would suggest:

a) stop weewx
b) take a copy of database
c) sort out any bad data in archive table - not in archive_day_rain table.  
set any unwanted rain to 0

d) drop daily tables with database utility
e) rebuild daily tables with database utility

f) delete all noaa files (they will be rebuilt on first report cycle)
g) restart weewx


On Sunday, 24 November 2019 13:55:56 UTC+2, Chris Thompstone wrote:
>
> just trying something:
> echo "SELECT * FROM archive_day_rain WHERE (sum > 4);" | sqlite3 
> weewx.sdb.old2
> if I do this, it brings up the rows with big sums.
> can I just do this:
>
> echo "UPDATE archive_day_rain SET sum=NULL WHERE (sum > 4);" | sqlite3 
> weewx.sdb.old2
>
> or will that not work? maybe sum=0 is better?
>
> Thanks
> Chris
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/64d812e7-4f2a-416d-ba61-155fcd696061%40googlegroups.com.

[weewx-user] Re: MrNonoss/WeewX-Docker problems

[Andrew Milner]

what is your archive interval set to?
what does the log say from startup of weewx up to the second archive 
interval has passed?


On Sunday, 24 November 2019 17:41:46 UTC+2, Colfin22 wrote:
>
> Ok, I've got somewhere. i need to run the containers detached.
>
> I've now got as far as i'm now getting weather data from my weather 
> station, the interceptor is working, I can see a continuous stream of data 
> in the weewx-core logs but it doesn't look like weewx is doing anything 
> with it as it's not archiving or creating a report in html
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1dfb01cc-9c54-4d2c-ad84-a397f40ccaae%40googlegroups.com.

[weewx-user] Re: Datenbank zusammen legen.

[Andrew Milner]

I would merge only the archive table and then use the database utility to 
drop the daily summary and rebuild the summaries for the combined database.



On Tuesday, 26 November 2019 06:33:06 UTC+2, J D wrote:
>
> Hi,
>
> Yes you can merge two databases I have done it a number of times. You need 
> to use SQLite commands. At a high level you attached to the two databases 
> and then use the update command. If you google merge sqlite databases you 
> can find a number of ways to do it.
> Jerry 
>
> On Sunday, November 24, 2019 at 2:52:27 AM UTC-7, Günther Wrana wrote:
>>
>> Hallo
>>
>> ich möchte Versuchen zwei Datenbanken von weewx.sdb zusammen zu fügen.
>>
>> Ich habe einen Rechner mit Ubuntu und kann die Datenbank mit DB Browser 
>> for SQLite öffnen.
>>
>> Die beiden Datenbanken beginnen und enden zu folgenden Zeiten.
>>
>> 1573144800 07.11.2019 17:40:00
>> 1573149300 07.11.2019 18:55:00
>>
>> 1573249500 08.11.2019 22:45:00
>> 1574009700 17.11.2019 17:55:00
>>
>> Nun habe ich noch nicht herausgefunden wie ich das mit DB Browser for 
>> SQLite mache.
>> Ich weis auch nicht ob das das Richtige Programm für mein Vorhaben ist.
>>
>> Darum hoffe ich das Ihr mir sagen könnt wie oder mit welchem Programm ich 
>> das tun soll.
>> Das ganze ist einmal ein Versuch danach würde ich dann gerne meine alten 
>> Wetterdaten die ich seit November 2014 aufgezeichnet habe auch noch 
>> einfügen.
>>
>> Für alle Tipps bin ich dankbar also dann
>>
>> Grüße Günther
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1b5dac3d-704e-4f8c-a76d-9729cb145bbb%40googlegroups.com.

[weewx-user] Re: Need to zero out rainRate and rain from time range

[Andrew Milner]

select * from archive where (dateTime >= 1574765820) and (dateTime <= 
1574766845);

will tell you what is in the table between those values and if it is the 
correct range then set rainRate and rain to 0 with
update archive set rainRate = 0, rain = 0  where (dateTime >= 1574765820) 
and (dateTime <= 1574766845);
 
On Tuesday, 26 November 2019 21:44:11 UTC+2, Chad Hutchins wrote:
>
> Hello!
>
> Using sqlite3 db for a Davis Vantage Vue station on a Raspberry Pi 3. 
>
> I need to zero (0.00) the rain rate and rain between two time ranges. I 
> think the data is between the following unix timestamps (1574765820 
> 1574766845) but that might not be what is exactly in the archive table.
>
> How do I go about finding that data so that I can run the commands listed 
> here for changing the data (except I would set to 0 instead of null) 
> https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data
>
> Thanks,
> Chad 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a002685f-9474-4ab2-b323-1f228b0e6cf9%40googlegroups.com.

[weewx-user] Re: bootstrap history page

[Andrew Milner]

from memory I tried to just change the two files, and it did not work.  
Seems there are other changes in the latest version and so my configuration 
was not compatible - I kept on getting an error to do with colors and fonts 
not being equal for noaa files so gave up.  The latest version allows you 
to set background color and font color for the history - which is useful.  
However I use highly customised colors and did not want to lose my current 
color settings so I stopped trying to work out why the noaa selection 
fonts/colors were failing.  I am sure it is something simple though.  The 
files are inside the zip which I pointed to on github before.



On Friday, 29 November 2019 23:44:49 UTC+2, Mikael Fredriksson wrote:
>
> Hi Andrew! Did you manage to get this to work? I don't know how to update 
> bootstrap. When I look at my skin.conf it says:
> $Revision: 737 $
> #$Author: tkeffer $
> #$Date: 2012-11-04 09:05:51 -0800 (Sun, 04 Nov 2012) $
>
> Where can I find the historygenerator.py file? 
>
> Thanks!
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/283aaec7-8daf-45d8-a361-1640f133a409%40googlegroups.com.

[weewx-user] Re: bootstrap history page

[Andrew Milner]

history generator.py lives in weewx/bin/user

On Saturday, 30 November 2019 05:08:16 UTC+2, Andrew Milner wrote:
>
> from memory I tried to just change the two files, and it did not work.  
> Seems there are other changes in the latest version and so my configuration 
> was not compatible - I kept on getting an error to do with colors and fonts 
> not being equal for noaa files so gave up.  The latest version allows you 
> to set background color and font color for the history - which is useful.  
> However I use highly customised colors and did not want to lose my current 
> color settings so I stopped trying to work out why the noaa selection 
> fonts/colors were failing.  I am sure it is something simple though.  The 
> files are inside the zip which I pointed to on github before.
>
>
>
> On Friday, 29 November 2019 23:44:49 UTC+2, Mikael Fredriksson wrote:
>>
>> Hi Andrew! Did you manage to get this to work? I don't know how to update 
>> bootstrap. When I look at my skin.conf it says:
>> $Revision: 737 $
>> #$Author: tkeffer $
>> #$Date: 2012-11-04 09:05:51 -0800 (Sun, 04 Nov 2012) $
>>
>> Where can I find the historygenerator.py file? 
>>
>> Thanks!
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/fb5071ec-80dd-4394-986a-7d03772cd56d%40googlegroups.com.

[weewx-user] Re: bootstrap history page

[Andrew Milner]

i only copied the files a week or so ago.  The only problem I am having is 
with the noaa table which is giving me an error - i have got the summary 
columns for the min, max, rain tables working as expected.



On Sunday, 1 December 2019 23:43:50 UTC+2, Mikael Fredriksson wrote:
>
> Ok, thanks Andrew!
>
> I did also try to update and use the new files but nothing changed so I 
> guess this has been removed in the latest update.
>
> Mikael
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c4491f79-5f50-49a5-9a75-3398c42be6e1%40googlegroups.com.

[weewx-user] Re: weewx - weewx-influx - grafana

[Andrew Milner]

On Wednesday, 4 December 2019 05:22:55 UTC+2, Xant wrote:
>
> (update)
>
> At this point, I pretty much reproduced original Christian Dashboard. Once 
> you get the hand-of-it, things are much quicker to setup sensors.
>
> Dashboard at this point is "static", and not real-time updated and 
> graphical response. Searching for MQTT solutions, or similar. InfluxDB has 
> a plugin called Telegraf, and Qnap also has its own IoT package. Will 
> investigate.
>
> Important to note that Grafana may develop source link direct to SQlite DB 
> (although, this promise is more than 2yo). If so, would be no need for 
> InfluxDB and direct reading direct WeeWX DB.
>
> X
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5113756e-0c73-42c8-b431-73906d6ed1db%40googlegroups.com.

[weewx-user] Re: How to test if lowBattery alarm notifications work?

[Andrew Milner]

a silly question - but have you actually got example, mypassword in your 
config - or have you replaced these with a real host, a real user and a 
real password??



On Wednesday, 4 December 2019 08:02:26 UTC+2, Michi Kaa wrote:
>
> my Config looks like this:
>
> time_wait = 3600
> count_threshold = 1
> smtp_host = mail.example.com
> smtp_user = not...@example.com
> smtp_password = myPassword
> from = not...@example.com
> mailto = m...@example.com
> subject = Weewx Battery low!
>
> I have log entries like that:
> Dec  3 06:55:28 weewxPi weewx[1365]: lowBattery: Low battery status 
> sounded at 2019-12-03 06:55:15 CET (1575352515): {'inTempBatteryStatus': 1}
> Dec  3 11:07:53 weewxPi weewx[1365]: lowBattery: Low battery status 
> sounded at 2019-12-03 11:07:53 CET (1575367673): {'inTempBatteryStatus': 1}
> Dec  3 13:26:02 weewxPi weewx[1365]: lowBattery: Low battery status 
> sounded at 2019-12-03 13:25:54 CET (1575375954): {'inTempBatteryStatus': 1}
> Dec  3 14:26:12 weewxPi weewx[1365]: lowBattery: Low battery status 
> sounded at 2019-12-03 14:26:09 CET (1575379569): {'inTempBatteryStatus': 1}
> Dec  3 16:26:14 weewxPi weewx[1365]: lowBattery: Low battery status 
> sounded at 2019-12-03 16:26:11 CET (1575386771): {'inTempBatteryStatus': 1}
> Dec  3 19:47:49 weewxPi weewx[1365]: lowBattery: Low battery status 
> sounded at 2019-12-03 19:47:49 CET (1575398869): {'outTempBatteryStatus': 1}
> Dec  3 20:48:03 weewxPi weewx[1365]: lowBattery: Low battery status 
> sounded at 2019-12-03 20:47:55 CET (1575402475): {'outTempBatteryStatus': 
> 1, 'inTempBatteryStatus': 1}
> Dec  3 21:48:23 weewxPi weewx[1365]: lowBattery: Low battery status 
> sounded at 2019-12-03 21:48:22 CET (1575406102): {'outTempBatteryStatus': 1}
> Dec  3 22:48:40 weewxPi weewx[1365]: lowBattery: Low battery status 
> sounded at 2019-12-03 22:48:19 CET (1575409699): {'outTempBatteryStatus': 1}
> Dec  3 23:48:57 weewxPi weewx[1365]: lowBattery: Low battery status 
> sounded at 2019-12-03 23:48:51 CET (1575413331): {'outTempBatteryStatus': 1}
> Dec  4 00:51:51 weewxPi weewx[1365]: lowBattery: Low battery status 
> sounded at 2019-12-04 00:51:32 CET (1575417092): {'outTempBatteryStatus': 1}
> Dec  4 01:52:35 weewxPi weewx[1365]: lowBattery: Low battery status 
> sounded at 2019-12-04 01:52:34 CET (1575420754): {'outTempBatteryStatus': 1}
> Dec  4 02:54:08 weewxPi weewx[1365]: lowBattery: Low battery status 
> sounded at 2019-12-04 02:54:03 CET (1575424443): {'outTempBatteryStatus': 1}
> Dec  4 04:02:38 weewxPi weewx[1365]: lowBattery: Low battery status 
> sounded at 2019-12-04 04:02:33 CET (1575428553): {'outTempBatteryStatus': 
> 1, 'inTempBatteryStatus': 1}
>
> But didn't receive a notification. No error entries.
>
> How can I test if mailing in weewx context works? I've changed some 
> syslog.LOG_DEBUG lines in lowBattery.py to syslog.LOG_INFO so i can omit 
> all the other debug stuff in the log, but with fresh batteries next chance 
> to have a real alarm is probably in a year or so.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3c4e11bb-e52b-40de-a8be-e461e6e9794e%40googlegroups.com.

[weewx-user] Re: How to test if lowBattery alarm notifications work?

[Andrew Milner]

a suggestion - reverse the test so you get the mail if battery is ok



On Wednesday, 4 December 2019 10:01:41 UTC+2, Michi Kaa wrote:
>
> It's never too silly to ask that kind of stuff. Yes, i did :). Bad 
> credentials should lead to an error-entry in the log, as far as I remember 
> the code.
>
> What I could probably do is modifying lowBattery.py in a way that it will 
> send warnings, when the battery is not empty and do more logging.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/72d8fb84-5709-411d-bfbf-dac968c08e1f%40googlegroups.com.

Re: [weewx-user] Re: Cloud services (wunderground etc.) worthwhile?

[Andrew Milner]

i have never seen the justification for rapidfire wrt 'standard' weather 
readings - nothing changes fast enough in a meaningful manner to justify 
the computing overheads imho.



On Wednesday, 4 December 2019 18:53:13 UTC+2, Xant wrote:
>
> I finally did it... not total WU unplug, but "half-unplug". As I also 
> serving data to other services, I just disabled "rapid fire" to WU, saving 
> resources as to deal with other stuff. 
>
> X
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2fef29b3-dbaa-4b17-86a9-cc790f1ca51f%40googlegroups.com.

[weewx-user] Re: bootstrap history page

[Andrew Milner]

does the log offer any clues??  worked for me just changing history 
generator.py and the skin.conf.  I suspect noaa does not work for me 
because i have changed my noaa files to html instead of txt and also 
altered the header lines so suspect i have upset something!!  I've also 
emailed him and also not heard anything back (yet).

On Sunday, 8 December 2019 00:26:31 UTC+2, Mikael Fredriksson wrote:
>
> Andrew,
>
> I've tried to copy these files and even changed them line by line in 
> place, but the summary columns just won't apear. 
> Don't know what to try more, I left a comment on his github. Hope to get 
> some answer to this.
>
> /Micael
>
>
>
>
> Den måndag 2 december 2019 kl. 04:17:46 UTC+1 skrev Andrew Milner:
>>
>> i only copied the files a week or so ago.  The only problem I am having 
>> is with the noaa table which is giving me an error - i have got the summary 
>> columns for the min, max, rain tables working as expected.
>>
>>
>>
>> On Sunday, 1 December 2019 23:43:50 UTC+2, Mikael Fredriksson wrote:
>>>
>>> Ok, thanks Andrew!
>>>
>>> I did also try to update and use the new files but nothing changed so I 
>>> guess this has been removed in the latest update.
>>>
>>> Mikael
>>>
>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7dc92d87-0098-49f4-8724-ecb9a5f621c1%40googlegroups.com.

[weewx-user] Re: bootstrap history page

[Andrew Milner]

that is, I think, what I am using.  The history tables are generated 
correctly for max, min, average, rain, raindays - but the noaa table does 
not generate for some raeson - historygenerator seems to think it is a 
normal table rather than the noaa table of buttons and i cannot find what 
is wrong.




On Monday, 9 December 2019 06:52:21 UTC+2, Michi Kaa wrote:
>
> For the Bootstrap skin to run correctly, you have to install the latest 
> commit of 
> https://github.com/brewster76/fuzzy-archer/blob/master/bin/user/historygenerator.py
>   
> , which is *NOT* included in the latest release!
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e109ebbe-c0e9-446a-b957-113f97ac3d97%40googlegroups.com.

[weewx-user] Re: bootstrap history page

[Andrew Milner]

here is my bootstrap skin which generates temperature and rain tables 
correctly but fails to create the NOAA button select table and instead 
gives a spurious error saying min values, max values and colours must have 
same number of elements. Whilst this is correct for normal history tables 
it does not apply to the NOAA table.  I assume that the NOAA section is not 
being identified as a NOAA table - why not??



On Monday, 9 December 2019 18:08:46 UTC+2, Michi Kaa wrote:
>
> I think I was the one who gave the answer on github. Did you post how you 
> solved it?
>
> Am Sonntag, 8. Dezember 2019 08:59:18 UTC+1 schrieb Mikael Fredriksson:
>>
>> Andrew,
>>
>> Finally got it to work
>> !
>> Got an answer on my comment on github, and followed the proceduer. 
>> I must have made some misstake before because it looks like this was what 
>> you told me to do.
>> My NOAA works also but I haven't made any changes on that.
>>
>> Hope you get some answer to your issue with this now!
>>
>> And thanks for your answers on this!
>>
>> /Mikael
>>
>> Den söndag 8 december 2019 kl. 00:49:39 UTC+1 skrev Andrew Milner:
>>>
>>> does the log offer any clues??  worked for me just changing history 
>>> generator.py and the skin.conf.  I suspect noaa does not work for me 
>>> because i have changed my noaa files to html instead of txt and also 
>>> altered the header lines so suspect i have upset something!!  I've also 
>>> emailed him and also not heard anything back (yet).
>>>
>>> On Sunday, 8 December 2019 00:26:31 UTC+2, Mikael Fredriksson wrote:
>>>>
>>>> Andrew,
>>>>
>>>> I've tried to copy these files and even changed them line by line in 
>>>> place, but the summary columns just won't apear. 
>>>> Don't know what to try more, I left a comment on his github. Hope to 
>>>> get some answer to this.
>>>>
>>>> /Micael
>>>>
>>>>
>>>>
>>>>
>>>> Den måndag 2 december 2019 kl. 04:17:46 UTC+1 skrev Andrew Milner:
>>>>>
>>>>> i only copied the files a week or so ago.  The only problem I am 
>>>>> having is with the noaa table which is giving me an error - i have got 
>>>>> the 
>>>>> summary columns for the min, max, rain tables working as expected.
>>>>>
>>>>>
>>>>>
>>>>> On Sunday, 1 December 2019 23:43:50 UTC+2, Mikael Fredriksson wrote:
>>>>>>
>>>>>> Ok, thanks Andrew!
>>>>>>
>>>>>> I did also try to update and use the new files but nothing changed so 
>>>>>> I guess this has been removed in the latest update.
>>>>>>
>>>>>> Mikael
>>>>>>
>>>>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9247f5ce-9150-4e0d-8ab1-d710602eb662%40googlegroups.com.



#   
   #
#   
   #
#  STANDARD SKIN CONFIGURATION FILE 
   #
#   
   #
#   
   #

#   
   #
#Copyright (c) 2010 Tom Keffer   
   #
#   
   #
#  See the file LICENSE.txt for your full rights.   
   #
#   
   #

#
#$Revision: 737 $
#$Author: tkeffer $
#$Date: 2012-11-04 09:05:51 -0800

[weewx-user] Re: bootstrap history page

[Andrew Milner]

The power of many eyes - that was it  It now works as expected.  Many 
thanks to everyone - especially Michi.  I never saw it either because I 
never really thought about the default values as they are not used.  Many 
many thanks - I can sleep peacefully again now!!
All working at 
http://andrewmilner.online/Bootstrap/history.html

Many many thanks


On Monday, 9 December 2019 21:55:38 UTC+2, Michi Kaa wrote:
>
> Haha! There it is. And now I know why I didn't find it: I have the same 
> error in my config but the line was commented out, because I use different 
> colours (sic!). But doing a DIFF on my config and yours didn't highlight 
> it, because the lines where the same except for the "#". I don't know where 
> I got this commented out line from, I guess from an older release?
>
> I hope the issue is solved by now and there is no other error...
>
> Am Montag, 9. Dezember 2019 19:34:45 UTC+1 schrieb J D:
>>
>> Here is the line for easy find
>>
>>  colours =   "#0029E5", "#0186E7", "#02E3EA", "#04EC97", *"#05EF3D2,* 
>> "#2BF207", 
>>
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f34f706c-2944-4a08-8c2d-fde201a69f7d%40googlegroups.com.

[weewx-user] force generation of yearly plot

[Andrew Milner]

A stupid question - but is there a way to force generation of yearly 
plots??  It is my understanding that the yealy plots are only generated 
perhaps only once per day.  I have modified the format of a yearly plot and 
want to see the result - but not wait until tomorrow!!  Does deleting the 
plot force it to be generated on the next report cycle, or only when the 
yearly's are next due to be generated?

confuzzed


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/47e7cf3e-5511-4e57-b8c9-7c87491af949%40googlegroups.com.

[weewx-user] Re: force generation of yearly plot

[Andrew Milner]

thanks  gary.  Just got an oddity with my local server now ... my public 
server shows the big images of the plots just fine, but for some reason my 
local server has an old big image cached and keeps delivering the cached 
version rather than the new.  fine for small image.  how can i clear or 
reload the big image delivered when i click on a plot (using bootstrap 
skin)??  Tried shift/reload - did not work.  Not too bothered as I assume 
it will correct itself at some stage but am curious!!

Andrew


On Sunday, 15 December 2019 09:27:47 UTC+2, gjr80 wrote:
>
> > Does deleting the plot force it to be generated on the next report cycle
>
> Yes
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1b4a267d-9b55-4ad3-871c-12c7d92c04d4%40googlegroups.com.

[weewx-user] Re: force generation of yearly plot

[Andrew Milner]

Gary - the images are generated ok by weewx - big and small.  The problem 
was the serving of the images by the webserver.  Whilst looking around for 
a solution Edge has magically decided to refresh its cache so now I do not 
have a problem anyway.  This looks like an issue with the caching that Edge 
does locally rather than the server.  In fact, using explorer worked just 
fine for big and small - but anyway, as i say, now even Edge is working 
fine for big and small.

Oh well, such is life - this just goes into the "life's mysteries" category 
for now!!!

Andrew


On Sunday, 15 December 2019 10:52:10 UTC+2, gjr80 wrote:
>
> Not real flash on bootstrap, but I seem to remember it generated big and 
> little images using the WeeWX image generator so nothing peculiar there, 
> the behaviour should be exactly the same. Deleting all images doesn’t work? 
> Standard WeeWX operation for all reports and images is to regenerate if the 
> report/image file does not exist, irrespective of any other settings. 
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d7870c8a-4856-408f-82b1-f677671c23c9%40googlegroups.com.

[weewx-user] Re: force generation of yearly plot

[Andrew Milner]

my problem was that ctrl/f5 gave an updated small image - but not the large 
image.  how/when edge decided to update the large image remains a mystery!!



On Monday, 16 December 2019 08:35:34 UTC+2, Michi Kaa wrote:
>
> Well, I encountered the exactly same behaviour using Firefox, Ctrl+F5 
> fixed it. I've never seen this in Edge (most porbably, because I never used 
> Edge :D )
>
> Am Sonntag, 15. Dezember 2019 21:38:23 UTC+1 schrieb gjr80:
>>
>> So the real source of the problem is revealed - Edge - ditched that and 
>> any Microsoft based browser years ago.
>>
>> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c19e5152-5001-482b-9eeb-cc560dd942aa%40googlegroups.com.

[weewx-user] Re: Include old NOAA reports to the archive page

[Andrew Milner]

have you tried just putting the reports into the NOAA directory and naming 
them in the same way as the weewx NOAA files??  It should work I would have 
thought - the drop down is populated by cheetah when the archive.html page 
is generated I think.

On Wednesday, 18 December 2019 07:20:12 UTC+2, peter wrote:
>
> I have NOAA reports from other software I was using before switching to 
> weewx. Database contains only “fresh” data and not the data from previous 
> software. 
> Is it possible to include the links to ma old NOAA reports into the 
> “archive.html.tmpl” page automatically? I’m using neowx skin. A workaround 
> is to manually put the links into the template file. 
> Thanks.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/466e010b-77dc-44ab-9f01-80031910a769%40googlegroups.com.

Re: [weewx-user] Re: Include old NOAA reports to the archive page

[Andrew Milner]

if the files are named in the same way as standard NOAA files the surely 
cheetah will think that it 'might have generated' them and so include them 
in the drop down??



On Wednesday, 18 December 2019 13:11:09 UTC+2, Thomas Keffer wrote:
>
> That's correct, except that the WeeWX Cheetah code knows only of the files 
> it has either generated, or might have generated. It has no way of knowing 
> about new files that have been dropped into the directory. You'd have to 
> write some custom Javascript code to do that. 
>
> -tk
>
> On Tue, Dec 17, 2019 at 11:15 PM Andrew Milner  > wrote:
>
>> have you tried just putting the reports into the NOAA directory and 
>> naming them in the same way as the weewx NOAA files??  It should work I 
>> would have thought - the drop down is populated by cheetah when the 
>> archive.html page is generated I think.
>>
>> On Wednesday, 18 December 2019 07:20:12 UTC+2, peter wrote:
>>>
>>> I have NOAA reports from other software I was using before switching to 
>>> weewx. Database contains only “fresh” data and not the data from previous 
>>> software. 
>>> Is it possible to include the links to ma old NOAA reports into the 
>>> “archive.html.tmpl” page automatically? I’m using neowx skin. A workaround 
>>> is to manually put the links into the template file. 
>>> Thanks.
>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/466e010b-77dc-44ab-9f01-80031910a769%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/466e010b-77dc-44ab-9f01-80031910a769%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8e5bd1ec-1a38-4a45-ae62-66ece80674ab%40googlegroups.com.

Re: [weewx-user] Re: Include old NOAA reports to the archive page

[Andrew Milner]

the OP said he already had the reports, and implied he just wanted to be 
able to view them.

I was thinking along the lines of naming the files ...txt just as they are 
now in the NOAA dorectory.  Unless weewx has changed the way to view these 
NOAA reports was via a selector control on the html page and the selector 
control was populated by cheetah.  I assumed it was using a directory 
listing to generate the linkages in the control to the actual .txt files 
and o just adding more .txt files cheetah would be none the wiser as to who 
had created the .txt files in that the naming convention would match those 
created by weewx.  No need to browse the directory - just use the selection 
control to view the selected file.

have we got our wires crossed perhaps??

Andrew


On Wednesday, 18 December 2019 14:14:55 UTC+2, Thomas Keffer wrote:
>
> It doesn't work that way, at least, not now. The problem is that if you 
> drop the files into the HTML directory, WeeWX has no way of knowing they 
> exist, and, due to security reasons, browsers are not allowed to, well, 
> browse webserver directories. There are ways around that using PHP or 
> Javascript code running on the webserver, but you'd have to write that.
>
> The only other option I can think of is to create a special subdirectory 
> in the skins subdirectory that holds old files that are to be copied over 
> to the HTML directory by the CopyGenerator. Then WeeWX could detect them.
>
> As always, PRs are welcome. :-)
>
> -tk
>
> On Wed, Dec 18, 2019 at 5:06 AM Andrew Milner  > wrote:
>
>> if the files are named in the same way as standard NOAA files the surely 
>> cheetah will think that it 'might have generated' them and so include them 
>> in the drop down??
>>
>>
>>
>> On Wednesday, 18 December 2019 13:11:09 UTC+2, Thomas Keffer wrote:
>>>
>>> That's correct, except that the WeeWX Cheetah code knows only of the 
>>> files it has either generated, or might have generated. It has no way of 
>>> knowing about new files that have been dropped into the directory. You'd 
>>> have to write some custom Javascript code to do that. 
>>>
>>> -tk
>>>
>>> On Tue, Dec 17, 2019 at 11:15 PM Andrew Milner  
>>> wrote:
>>>
>>>> have you tried just putting the reports into the NOAA directory and 
>>>> naming them in the same way as the weewx NOAA files??  It should work I 
>>>> would have thought - the drop down is populated by cheetah when the 
>>>> archive.html page is generated I think.
>>>>
>>>> On Wednesday, 18 December 2019 07:20:12 UTC+2, peter wrote:
>>>>>
>>>>> I have NOAA reports from other software I was using before switching 
>>>>> to weewx. Database contains only “fresh” data and not the data from 
>>>>> previous software. 
>>>>> Is it possible to include the links to ma old NOAA reports into the 
>>>>> “archive.html.tmpl” page automatically? I’m using neowx skin. A 
>>>>> workaround 
>>>>> is to manually put the links into the template file. 
>>>>> Thanks.
>>>>
>>>> -- 
>>>> 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...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/466e010b-77dc-44ab-9f01-80031910a769%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/466e010b-77dc-44ab-9f01-80031910a769%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/8e5bd1ec-1a38-4a45-ae62-66ece80674ab%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/8e5bd1ec-1a38-4a45-ae62-66ece80674ab%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d4d23608-c9e6-4b33-955e-1105d7564342%40googlegroups.com.

Re: [weewx-user] Re: Belchertown skin 1.0 released!

[Andrew Milner]

Can you use the correct names for skins rather than your own abbreviations 
as it makes it appear that there is another skin available!



On Friday, 20 December 2019 05:17:14 UTC+2, Xant wrote:
>
>
> Tom previously mentioned that Bskin may not be ready for W4 yet, but now 
> clarified.
>
> Will investigate further.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a6a10667-19de-48c9-b9cc-0cd228c04a9a%40googlegroups.com.

[weewx-user] Re: Best accurate 5 in 1 alternative

[Andrew Milner]

what is the archive interval set to in weewx.conf?  data is only written to 
the database every archive interval.  your last log ended just after the 
main packet loop commenced, so the first data would be written 5 - 30 
minutes after that point, and until then the database will remain empty.



On Friday, 13 December 2019 20:42:32 UTC+2, Sean Jahnig wrote:
>
> I built a weather station using an accurate 5 in 1! a raspberry pi and 
> weewx. 
>
> It works well but it the acurite side of things is temperamental. The usb 
> enabled display sometimes needs to be reset and a usb hub is required to 
> make sure it always has power. Not ideal when the station is installed in a 
> remote location. 
>
> Are there any better suggestions for a weather station that is more 
> reliable than the acurite? I plan to build another one but I’d like 
> something more reliable than acurite. The station must have anemometer and 
> windvane.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c0e1b023-90ff-411a-bde3-18fcf9bfc72e%40googlegroups.com.

Re: [weewx-user] Re: Best accurate 5 in 1 alternative

[Andrew Milner]

try this youtube

https://www.youtube.com/watch?v=OVsqGX0iBOM

it should help you



On Sunday, 29 December 2019 09:20:53 UTC+2, Sean Jahnig wrote:
>
> Thanks for the reply.
>
> It is 300. You are right, if i wait 10min it has started reporting so it 
> is working.
>
> I am having intermittent issues though and i think it is because i am 
> using the wrong antenna on the dongle. If i move the station more than 5m 
> away from the dongle, it loses the signal. And there's no way of knowing i 
> am losing signal because the 'Signal Quality' field in 
> http://192.168.1.150/weewx/ just says N/A. Is there no way to parse the 
> signal quality from rtl_144 to weewx ? I was hoping this would do it, but 
> it doesn't *rxCheckPercent = status.013E.Acurite5n1Packet*
>
> Also, can anyone tell me what length of antenna i should be using on the 
> SDR dongle? The sensor is transmitting at 433Mhz. At the moment the antenna 
> i have is about 12cm long (the type that you find on a wifi access point) 
> and it loses signal with the sensor when i go 5m+ away.
>
> thanks
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1f1f9563-be6b-40c4-9a5a-c10a83f902dc%40googlegroups.com.

[weewx-user] Re: StdReport thread has been terminated every day at 00:20 (1927, 'Connection was killed')

[Andrew Milner]

or you could stop weewx for the hyperbackup period and resume when it is 
complete.  weewx will then do 'catchup' from loggers and all should be 
tickety-boo .



On Wednesday, 1 January 2020 10:21:16 UTC+2, Geni wrote:
>
> Hi, Thomas.
> The hint that the error code 1927 comes from MariaDB, I knew immediately 
> where to look for it!
> Now at this time a hyperbackup job is running on my synologe which also 
> contained the application MariaDB, I have removed it and this night no 
> error messages.
>
> Summary:
> The backup stops the database service for a short moment and if that's 
> exactly when Weewx wants to access it, it won't work.
> My suggestion would be if weewx doesn't get a database connection it will 
> wait for the next interval but without killing the process.
> In my case this would be 1 or 2 intervals and then the missing records 
> would be read in and nobody would notice anything.
>
> Regards
> Geni
>
> PS: This error occurred very rarely with the Raspberry PI2?
>
>
> Am Dienstag, 31. Dezember 2019 11:01:10 UTC+1 schrieb Geni:
>>
>> Hello, 
>> Since I replaced the Raspberry PI 2 with a Raspberry PI 3+ this problem 
>> occurs every night, before only sporadically.
>> In use:
>> Raspberry 3+ mit Raspbian Buster Lite
>> Externe SqlDB (MariaDB 10) 
>> David Vantage Pro2 Version: 3.83
>> Weewx 3.9.2-1
>>
>> Every night at exactly 00:20, it stops. The report at 00:10 is still made
>> debug-log:
>> Dec 31 00:10:55 Wetter-Raspi weewx[889]: reportengine: Report 'RSYNC' not 
>> enabled. Skipping.
>> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Requesting 200 LOOP 
>> packets.
>> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Gentle wake up of 
>> console successful
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: StdReport thread has 
>> been terminated
>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: engine: Debug is 1
>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: engine: Initializing engine
>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Driver version is 3.1.1
>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Opened up serial port 
>> /dev/ttyUSB0; baud 19200; timeout 4.00
>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Gentle wake up of 
>> console successful
>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Hardware type is 16
>> Dec 31 07:44:11 Wetter-Raspi weewx[3001]: vantage: ISS ID is 1
>> Dec 31 07:44:11 Wetter-Raspi weewx[3001]: vantage: Hardware name: Vantage 
>> Pro2
>>  
>> syslog:
>> Dec 31 00:17:01 Wetter-Raspi CRON[1919]: (root) CMD (   cd / && run-parts 
>> --report /etc/cron.hourly)
>> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Requesting 200 LOOP 
>> packets.
>> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Gentle wake up of 
>> console successful
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Main loop exiting. 
>> Shutting engine down.
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Shutting down StdReport 
>> thread
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: StdReport thread has 
>> been terminated
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Caught unrecoverable 
>> exception in engine:
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   (1927, 'Connection was 
>> killed')
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   Traceback (most recent 
>> call last):
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>> "/usr/share/weewx/weewx/engine.py", line 894, in main
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   engine.run()
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>> "/usr/share/weewx/weewx/engine.py", line 191, in run
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   
>> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>> "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   callback(event)
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>> "/usr/share/weewx/weewx/wxservices.py", line 45, in new_loop_packet
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   
>> self.calc.do_calculations(event.packet, 'loop')
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>> "/usr/share/weewx/weewx/wxservices.py", line 191, in do_calculations
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   getattr(self, 
>> 'calc_' + obs)(data_us, data_type)
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>> "/usr/share/weewx/weewx/wxservices.py", line 228, in calc_pressure
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   data['dateTime'], 
>> interval)
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>> "/usr/share/weewx/weewx/wxservices.py", line 404, in _get_temperature_12h
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   record = 
>> dbmanager.getRecord(ts12, max_delta=self.max_delta_12h)
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: F

[weewx-user] Re: New html page

[Andrew Milner]

have you actually inlcuded the reference to the css in your new file?  
Without knowing what skin you are using, what you actually changed and what 
you are actually seeing it is very hard for us to imagine or speculate on 
what your specific problem may be caused by!!



On Sunday, 12 January 2020 13:22:45 UTC+2, Mikael Fredriksson wrote:
>
> Hi!
>
>
> When creating new web page I copied a template from my running page and 
> renamed it and made som smaller changes to it. 
> Added it to the skin.conf under [CheetahGenerator]
> When running a report cycle the new page is generated but it dont have the 
> same look, not the background and so on..
> I added the new template in same skin folder as the file I copied and 
> changed the name. 
> Must I change or add something somewhere else to get the same look of the 
> new page? In main.css I didn't find anything that had to do with the pages 
> specific.
>
> Help appreciated!
>
> /Mikael
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6c0a9f55-2973-4f7f-a021-8717c43d83a4%40googlegroups.com.

Re: [weewx-user] Re: Build/install Error on Raspberry PI 3B

[Andrew Milner]

or even better - read the documentation BEFOrE downloading any files!!  The 
install documentation for debian, mint and raspbian can be found at
http://weewx.com/docs/debian.htm

with weewx the documentation should be read, digested and understood to 
appreciate the power of weewx.

very little information is duplicated between the different documents, so 
one should at least try and appreciate the topics contained in each.  
Especially useful is the utilities documentation.




On Saturday, 18 January 2020 06:17:17 UTC+2, Xerxes Shelley wrote:
>
> So after much futzing around. Learning how to use the GREP command, (which 
> btw is a damn cool command, let's you search inside a file inside a 
> directory.) I finally went into the "docs" directory inside of the 
> weewx-v.e.rsion directory there is an insall.html. I opened it up in 
> the raspbian desktop, and followed the directions in it. SOLVED my setup 
> problems!
>
> i'm going to post this on this group hoping that it shows up in google 
> searches. Hope current users of this board don't mind. For future users-
> this is straight from from the above mentioned document.
>
> WeeWX: Installation using apt-get   
> This is the fastest way to install WeeWX on Debian-based systems, 
> including Ubuntu, Mint, and Raspbian.
>
> Configure apt
> Tell apt where to find the WeeWX releases. This only has to be done once - 
> the first time you install.
>
> wget -qO - http://weewx.com/keys.html | sudo apt-key add -
> wget -qO - http://weewx.com/apt/weewx.list | sudo tee 
> /etc/apt/sources.list.d/weewx.list
>
> Install
> Use apt-get to install WeeWX. When you are done, WeeWX will be running in 
> the background as a daemon.
>
> sudo apt-get update
> sudo apt-get install weewx
>
> Verify
> After 5 to 30 minutes, open the station web page in a web browser. You 
> should see your station information and data.
>
> file:///var/www/html/weewx/index.html
>
> Uninstall
> This will remove WeeWX, leaving any data intact.
>
> sudo apt-get remove weewx
>
> Where to go from here...
> User's Guide - configuration options, integrating with a web server, and 
> troubleshooting
> Customization Guide - instructions for modifying reports and adding 
> extensions
> Hardware Guide - details about weather station capabilities and quirks
> Utilities Guide - reference for the command-line options and actions
> wiki - HOWTOs, extensions, and drivers
> User Group
>
>
> On Friday, January 17, 2020 at 8:22:31 AM UTC-8, Thomas Keffer wrote:
>>
>> With WeeWX version 2.5 (released 2013), the name of the WMR section was 
>> changed from WMR-USB to WMR100. Normally, setup.py takes care of the name 
>> change, but in your case, you already have a WMR100 section, so setup.py 
>> doesn't know which one is correct and aborted.
>>
>> Go into weewx.conf and figure one which one is correct. My guess is the 
>> WMR100 section is correct. Then delete (or comment out) the other section 
>> (probably WMR-USB). This means you start with something like this:
>>
>> .
>> .
>> .
>> [WMR-USB]
>>   option1 = value
>>   option2 = value
>>
>> [WMR100]
>>   some_other_option = value
>> .
>> .
>> .
>>
>> and end up with
>>
>> .
>> .
>> .
>> # [WMR-USB]
>> #option1 = value
>> #option2 = value
>>
>> [WMR100]
>>   some_other_option = value
>> .
>> .
>> .
>>
>> I don't remember what actual options are used in these sections. That's 
>> why I've used the generic names "option1", "option2", etc.
>>
>> If this is all too much for you, you can email me your weewx.conf file 
>> and I'll do the corrections. After draining your bank account, of course. 
>> :-)
>>
>> -tk
>>
>> On Fri, Jan 17, 2020 at 8:01 AM Xerxes Shelley  wrote:
>>
>>> morning world!
>>>
>>> wondering if anyone knows why i get the error in the picture? again any 
>>> help would be appreciated. 
>>>
>>> On Wednesday, January 15, 2020 at 1:49:20 PM UTC-8, Xerxes Shelley wrote:

 Hi, i'm doing this as a hobby. Not super familiar with Linux. But i can 
 google the shit out something as needed. 

 I get the error

 *** Configuration file has both a 'WMR-USB' section and a 'WMR100' 
 section. Aborting  


 this is a fresh install i'm following the directions at 
 http://weewx.com/docs/setup.htm at the install WeeWX section. any help 
 here would be appreicated. I'm on the last step.  

 Thanks!

>>> -- 
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/a497e042-025d-448d-b9b8-606746811e6d%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed t

[weewx-user] Re: WeeWX v4 I Need an Extension Verified/Checked

[Andrew Milner]

I do not think v4 has officially been released yet - so I would recommend 
installing the new hardware with 3.9 and do the upgrade when v4 is finally 
released.  That way you do not change the whole shebang - hardware and 
software - in one giant leap. Regarding 'how do you know' - the answer is 
that you don't!!  The original writer may update wike or download with 
additional information, or another user may post a comment, but there is no 
automatic verification process of all extensions written by other people.




On Sunday, 19 January 2020 04:46:16 UTC+2, G Hammer wrote:
>
> I'd like to run v4 when I upgrade hardware this week.
> Seems to be doing fine for the devices and skin I use.
> With one exception, a RainMachine extension.
> There is one that was written by someone at RainMachine, but I think he 
> has moved on.
> I've asked there and raised an issue on the github page for the extension 
> with no response.
>
> How, besides installing v4 and the extension, can I determine if it will 
> run under v4?
>
> The extension is located at https://github.com/sprinkler/rainmachine-weewx 
> and 
> referenced at https://github.com/weewx/weewx/wiki/RainMachine
>
> With this functionality confirmed, I can make the change, without it I'll 
> need to stay with v3
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e95133ce-4a77-43db-930f-facf0e73e5e8%40googlegroups.com.

Re: [weewx-user] Re: WeeWX v4 I Need an Extension Verified/Checked

[Andrew Milner]

why not ask the author of the extension then - if it is important to you to 
have the answer.  After all, the author is the person who should have the 
answer.  As to whether the author  has tested against the beta version 
depends very much upon the time available to the author of the extension I 
suspect.  I know the bootstrap skin and mesowx took some iterations after 
the introduction of I think weewx v3 before there were useable versions 
available - and the changes were actually made by another weewx user rather 
than the original author.  

On Sunday, 19 January 2020 06:39:25 UTC+2, G Hammer wrote:
>
> Seems that there should be a way to determine this as the change to Python 
> 3 isn't just a WeeWX thing.
>
> As for whether or not to run the beta, it's beta 8 and what I use seems to 
> be ok as far as reports go. Is it not what beta are for after all?
>
> Anyway, not what I asked, so let's see what else comes.
>
> On Sat, Jan 18, 2020, 11:14 PM Andrew Milner  > wrote:
>
>> I do not think v4 has officially been released yet - so I would recommend 
>> installing the new hardware with 3.9 and do the upgrade when v4 is finally 
>> released.  That way you do not change the whole shebang - hardware and 
>> software - in one giant leap. Regarding 'how do you know' - the answer is 
>> that you don't!!  The original writer may update wike or download with 
>> additional information, or another user may post a comment, but there is no 
>> automatic verification process of all extensions written by other people.
>>
>>
>>
>>
>> On Sunday, 19 January 2020 04:46:16 UTC+2, G Hammer wrote:
>>>
>>> I'd like to run v4 when I upgrade hardware this week.
>>> Seems to be doing fine for the devices and skin I use.
>>> With one exception, a RainMachine extension.
>>> There is one that was written by someone at RainMachine, but I think he 
>>> has moved on.
>>> I've asked there and raised an issue on the github page for the 
>>> extension with no response.
>>>
>>> How, besides installing v4 and the extension, can I determine if it will 
>>> run under v4?
>>>
>>> The extension is located at 
>>> https://github.com/sprinkler/rainmachine-weewx and referenced at 
>>> https://github.com/weewx/weewx/wiki/RainMachine
>>>
>>> With this functionality confirmed, I can make the change, without it 
>>> I'll need to stay with v3
>>>
>>>
>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/wlufg8AdT0E/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/e95133ce-4a77-43db-930f-facf0e73e5e8%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/e95133ce-4a77-43db-930f-facf0e73e5e8%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2c3c86a5-147b-482e-a0ab-72786453f2d2%40googlegroups.com.

[weewx-user] Re: WH1080 barometer calibration surprise

[Andrew Milner]

what units is your database in ??  default corrections use the unit of the 
database.

2.9 inHg = 98.20 mbar



On Sunday, 19 January 2020 20:56:11 UTC+2, PJO wrote:
>
> I tried yesterday, using WeeWX v.3.9.2, to calibrate my WH1080 barometer 
> by adding
>
> pressure = pressure - 2.9
>
> under
>
> [StdCalibrate]
>
> [[Corrections]]
>
> in weewx.conf. The result, shown in the image below, is not what I 
> expected -- a drop of almost 100 mbar. The spike is because I rescinded the 
> edit. Is this a bug or have I missed something?
>
>
> [image: Selection_040.png]
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/860d0596-a84b-4249-bdd2-47df3e17e000%40googlegroups.com.

[weewx-user] Re: How can the ftp transfer be influenced?

[Andrew Milner]

what error messages are in the log for the times when ftp appears to be 
failing??

On Monday, 20 January 2020 14:38:29 UTC+2, Geni wrote:
>
> A cronjob fetches every 10 min a status.jpg of an external website and 
> stores it in the HTML_ROOT/meteo.
> Target the file in this folder should always be copied with the ftp to the 
> configured server and its path.
> This almost always works now but sometimes nothing is copied for 1 or 2 
> hours and suddenly it works again.
>
> Can or must I make an entry in the weewx.conf to make this work more 
> reliable?
>
> Geni
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5df449e5-5f86-42a1-939b-cd48f8d7fcf2%40googlegroups.com.

[weewx-user] Re: How can the ftp transfer be influenced?

[Andrew Milner]

have you run with debug turned on?

the 'fault' could be something happening at the other end - ie weewx may be 
transferring correctly and your ISP may be doing something odd.



On Monday, 20 January 2020 16:05:45 UTC+2, Geni wrote:
>
> No error is entered in syslog
>
> Am Montag, 20. Januar 2020 14:22:01 UTC+1 schrieb Andrew Milner:
>>
>> what error messages are in the log for the times when ftp appears to be 
>> failing??
>>
>> On Monday, 20 January 2020 14:38:29 UTC+2, Geni wrote:
>>>
>>> A cronjob fetches every 10 min a status.jpg of an external website and 
>>> stores it in the HTML_ROOT/meteo.
>>> Target the file in this folder should always be copied with the ftp to 
>>> the configured server and its path.
>>> This almost always works now but sometimes nothing is copied for 1 or 2 
>>> hours and suddenly it works again.
>>>
>>> Can or must I make an entry in the weewx.conf to make this work more 
>>> reliable?
>>>
>>> Geni
>>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/da9e82f1-ed5a-4b7d-907c-83e2b7648f20%40googlegroups.com.

[weewx-user] Re: Need help installing WeeWX. IPv4 address problem?

[Andrew Milner]

Well that is your choice - but I suspect your problems are more to do with 
using Linux instead of windows rather than having anything whatsoever to do 
with weewx.  Weewx is fantastic software - all that you had to do was tell 
weewx the ip address of your weather station - but that seemed to be beyond 
your abilities for some reason.  Linix is not windows - you do not go 
around rebooting linux just in order to restart a program for example.

Well I think not using weewx will be your loss - maybe you should have made 
sure you understood linux basics before going down the weewx route!!

when you got your last error the chances are it was because you did not 
specify the full path to weewx.conf, and at the time you were in your home 
directory rather than in the weewx home directory.  As I said before, 
knowing Linux basics would have helped you a lot!!

Never mind - you have made your decision.  Should you decide to try again 
remember to go one step at a time and follow instructions exactly.  The 
weewx documenttion is really good and all the users are always willing to 
help - but go one step at a time.

As I said before I suspect your issues were nothing whatsoever to do with 
weewx but were connected with your lack of knowledge of linux basics.




On Sunday, 26 January 2020 06:46:03 UTC+2, Bill Butler wrote:
>
> I fixed that fairly early in the game, but there were other problems. At 
> this point I've given up on trying to run weewx. I've delete every file on 
> my computer that contains the letters weewx and won't be reinstalling the 
> package again.
>
>
> On Saturday, January 25, 2020 at 8:46:18 PM UTC-7, Greg from Oz wrote:
>>
>> On your first picture you have the linux machine being blocked by UFW the 
>> firewall
>>
>>
>> https://www.digitalocean.com/community/tutorials/ufw-essentials-common-firewall-rules-and-commands
>>
>> Don't know if you have fixed that or not.
>>
>> On Friday, 24 January 2020 11:47:51 UTC+11, Bill Butler wrote:
>>>
>>> I recently tried to install WeeWX on my new Linux (Cinnamon Mint 18) 
>>> computer in an attempt to transfer Davis Vantage Vue (with WeatherLinkIP) 
>>> display/control from my old Windows 7 computer to my new Linux computer. I 
>>> copied the instructions at http://www.weewx.com/docs/debian.htm to the 
>>> terminal, but the installation failed – presumably due to the different 
>>> addresses of the two computers on my home network. Please see the large 
>>> picture of the log at 
>>> http://durangobill.com/TempPictures/WeewxErrors.jpg – especially the 
>>> last 4 lines. (or the attached file)
>>>
>>> I originally set up the Vantage Vue on my old Windows 7 computer several 
>>> years ago.
>>> Its IPv4 Address is displayed as: 192.168.0.219
>>> There is also an IPv4 Default Gateway at: 192.168.0.1
>>>
>>> The IPv4 Address on my new Linux computer is: 192.168.0.143
>>> (And so much easier to find)
>>>
>>> Both computers have Ethernet (wired) connections to a CenturyLink 
>>> PK5001Z router. (GUI address 192.168.0.1)
>>>
>>> Can anyone tell me what I should do to get WeeWX up and running on my 
>>> new Linux Computer?
>>> After WeeWX is up and running, is there any way I can move the 
>>> historical Vantage Vue weather data from my old Windows 7 computer to my 
>>> new Linux computer?
>>> (Note, I can write a “quickie” “C” program to input the old data and 
>>> write it out in whatever format is needed for WeeWX. Physical transfer of 
>>> files is not a problem.) 
>>>
>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c1d35767-bd72-4d0c-a7bb-d7d4b69f548b%40googlegroups.com.

Re: [weewx-user] AcuRite 5-in-1 daytime dropout

[Andrew Milner]

well u could check by just changing the batteries for alkaline and see if 
the issue goes away again!!



On Tuesday, 28 January 2020 06:13:28 UTC+2, Drew Latta wrote:
>
> I am getting a lot of no data error messages in the log, like:
>
> Jan 27 01:56:00 raspberrypi weewx[565]: acurite: R1: ignoring stale data 
> (rssi indicates no communication from sensors): 01 c8 7c 71 00 00 00 03 00 
> 00
> Jan 27 01:56:18 raspberrypi weewx[565]: acurite: R1: ignoring stale data 
> (rssi indicates no communication from sensors): 01 c8 7c 71 00 00 00 03 00 
> 00
>  
>
> Yes, I agree that the barometric pressure bit is weird.
>
> However, the AcuRite display unit is also "searching for a signal" when it 
> isn't working correctly as there is a signal icon on the display that is 
> flashing rather than showing bars. So that seems to suggest to me that it 
> is a true signal issue. 
>
> Based on the Energizer datasheet, the lithium primary batteries are 
> supposed to have an nominal voltage of 1.5 V. At 100 mA drain they have a 
> pretty flat discharge curve at 1.4 V for a long time. I don't think it is 
> undervoltage from the batteries.
>
> One thought is that the extra metal (Li) in there is causing some signal 
> propagation issue, but it doesn't seem to explain the day/night difference. 
> Seems like a stretch.
>
> Drew
>
> On Monday, January 27, 2020 at 2:10:30 PM UTC-6, p q wrote:
>>
>>I have a similar setup.  
>>
>> Here's what's weird. The barometric pressure is also from the display 
>> unit (I'm pretty sure) and it's dropping out too.
>>
>> Can you check to see what's in your database? Is the problem in the 
>> display or in recording the data? Are you getting any error messages in the 
>> log?
>>
>> I don't think switching settings is going to help, but I don't know.
>>
>> Lithium batteries used to be 1.3 volts vs 1.5 volts for alkaline. I don't 
>> know if yours are that way. It might even be worse than nominal voltage 
>> when it's cold.
>>
>> On Mon, Jan 27, 2020 at 10:34 AM Drew Latta  wrote:
>>
>>> Hi WeeWx users,
>>>
>>> I have a working WeeWx install on a Pi Zero W connected to an AcuRite 
>>> 01036 via USB.
>>>
>>> I have been having some issues with data dropout during the daytime. 
>>> Which you can see here: http://173.29.136.66/weewx/
>>>
>>> My assumption is that because the data for inside temperature are being 
>>> shown that this is a communication issue between the AcuRite display and 
>>> the 5-in-1 station rather than the AcuRite display and the Pi.
>>>
>>> The interesting twist here is that the data drop-outs are now worse 
>>> since I put in 4 new lithium AA batteries in the 5-in-1 to replace 4 new 
>>> alkaline AA's I had in it. I generally use lithium AA's in the 5-in-1 since 
>>> we often get winter lows < -20C (-5F). 
>>>
>>> Any thought on why lithium batteries would degrade the signal quality 
>>> during the daytime worse than alkaline batteries? 
>>>
>>> Does switching channels from A to B or C ever help this problem?
>>>
>>> Thanks for your thoughts,
>>>
>>> Drew
>>>
>>> -- 
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/b7612e87-62b8-4f66-bd31-66bddae7d79b%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>
>>
>> -- 
>> Peter Quinn
>> (415)794-2264
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/bb148808-1c78-4a8d-8dfc-42446f787964%40googlegroups.com.

[weewx-user] Re: XML: windspeed in m/sec as well as km/h

[Andrew Milner]

$current.windSpeed.formatted.km_per_hour

I think



On Tuesday, 28 January 2020 16:04:32 UTC+2, Keimpe Bleeker wrote:
>
> Hi all,
>
> For a local news-website I kneed to build an XML- feed with windspeed in 
> km/h, while my WeeWX is (consiously) configured for m/sec. Cheetah is 
> picking the value for windspeed with this variable: 
> $current.windSpeed.formatted. Is there a solution to get/create/... a 
> second variable with windspeed in km/h?
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9481d291-2619-4d78-9589-550b57805ff1%40googlegroups.com.

[weewx-user] Re: Confusion with need for WeatherLinkIP

[Andrew Milner]

the belfryboy logger works well for a fraction the price of the davis 
...



On Thursday, 30 January 2020 21:28:41 UTC+2, vince wrote:
>
> On Thursday, January 30, 2020 at 9:31:50 AM UTC-8, Kevin Davis wrote:
>
>> While I'm twiddling my thumbs waiting for my Davis station to show up, I 
>> realize I might be confused about the WeatherLinkIP accessory.  That is a 
>> required part to interface with the Pi/WeeWx or not?
>>
>
>
> You need 'something' to connect the Davis to the Pi.Easiest path is to 
> buy the Davis datalogger.
>
> What Greg said re: alternatives such as 3rd-party loggers or talking to 
> Davis servers the hard way etc. etc. :-)
>
> For me, just buying the Davis logger was the lowest blood pressure path 
> (although the darn thing should be $25 max not $110+ for what it does).
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7a0d56c9-0a7a-480a-a238-ffafa1746e82%40googlegroups.com.

[weewx-user] Re: users guide for python3 installation

[Andrew Milner]

None of my 5 RPis - of different models - has ever exhibited freezing at 2 
monthly intervals so I suspect you had something else causing your 
problem(s).



On Sunday, 2 February 2020 18:37:40 UTC+2, Rich Altmaier wrote:
>
> Hi David, perhaps noone will agree with me but I suggest swapping the RPI 
> for an Intel NUC.  You can get a used one on ebay very reasonably.   The 
> reliability is much greater. I got tired of my RPI freezing every 2 months. 
> And need I say the NUC is 20 to 50 times faster?  Loading multiple years 
> of weewx database transfer on RPI, 2 minutes. On NUC, 2 seconds.  Do you 
> believe me?
>
> Good luck!
> Rich
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/557ed271-0c46-48c9-8f67-f4d906377b46%40googlegroups.com.

[weewx-user] Re: set average readings to use different unit group than instantaneous readings

[Andrew Milner]

the simple way is to change the formatting in the template(s) where 
appropriate.  You are not changing units per se eg from m/s to kph to mph 
etc but merely the displayed fprmat - the underlying unit remains the same.



On Saturday, 8 February 2020 06:17:06 UTC+2, Thomas Carlin wrote:
>
> Good evening again, 
>
> The title pretty well says it all, I would like to set the average wind 
> speeds to use a different unit groups.  My vantage Pro2 reads wind speed in 
> 1mph increments, so there is no need to output decimal points on those 
> values, but I would like to be able to display more accurate average 
> values.  
>
> Is there a way to do this in the weewx report engine?
>
> Thank you in advance, as always!
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/13135f1b-831a-4b67-a3db-d57fb6c21e36%40googlegroups.com.

[weewx-user] Re: set average readings to use different unit group than instantaneous readings

[Andrew Milner]

see here in customisation guide
http://weewx.com/docs/customizing.htm#Formatting_examples



On Saturday, 8 February 2020 08:08:05 UTC+2, Andrew Milner wrote:
>
> the simple way is to change the formatting in the template(s) where 
> appropriate.  You are not changing units per se eg from m/s to kph to mph 
> etc but merely the displayed fprmat - the underlying unit remains the same.
>
>
>
> On Saturday, 8 February 2020 06:17:06 UTC+2, Thomas Carlin wrote:
>>
>> Good evening again, 
>>
>> The title pretty well says it all, I would like to set the average wind 
>> speeds to use a different unit groups.  My vantage Pro2 reads wind speed in 
>> 1mph increments, so there is no need to output decimal points on those 
>> values, but I would like to be able to display more accurate average 
>> values.  
>>
>> Is there a way to do this in the weewx report engine?
>>
>> Thank you in advance, as always!
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0fbd62a6-be10-46aa-8396-54b1655e024e%40googlegroups.com.

[weewx-user] Re: Wind gust speed differences.

[Andrew Milner]

is your windgust weewx generated or provided by the vantage vue?  ie do you 
have sw record generation or hardware?



On Monday, 10 February 2020 15:42:33 UTC+2, Ton Karsten wrote:
>
> yes, everything as standard Weewx
> Weather station: Davis Vantage Vue Wireless
> Yes, use of WU rapid fire
> Website: http://weerstationnibbixwoud.nl/
> WU: https://www.wunderground.com/dashboard/pws/INOORDHO191
> WOW: https://wow.metoffice.gov.uk/observations/details/?site_id=942006001
> It is not exciting or, I was wondering how this is possible?
>
> Ton
>
> Op maandag 10 februari 2020 10:10:56 UTC+1 schreef Ton Karsten:
>>
>> I note that there is a difference between the speed generated on the 
>> Weewx website and the speed specified on the WU website and the WOW website 
>> data. 
>> Is there an explanation for how this is possible and how to solve it?
>>
>> Regards,
>> Ton
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/31094165-d229-465c-ae0a-9ea981f26162%40googlegroups.com.

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

[Andrew Milner]

check that the absolute pressure is correct - I have had a FO station which 
had a dodgy pressure sensor before now.  Calibrating pressure in weewx 
solved it.

On Wednesday, 12 February 2020 03:51:29 UTC+2, gjr80 wrote:
>
> sudo /etc/init.d/weewx stop will stop the current running service but if 
> you have other instances running, for example WeeWX directly, sudo 
> /etc/init.d/weewx 
> stop will have no effect as WeeWX is not running as a service. When 
> running WeeWX directly you need to stop the execution using a control key 
> sequence (CTL-C) or list the running WeeWX processes with ps -aux|grep 
> weewx and then use the Linux kill command to kill the process.
>
> Whenever you do a lot of stop-starting, running services/running directly 
> and odd things (apart from odd pressure values :) ) are happening it can be 
> because there is more than one instance of WeeWX running. If you look at 
> the log you can usually see it by there being more than one process ID 
> number against WeeWX at any one time.
>
> Well if your relative pressure is set correctly I am out of ideas on how 
> to fix this. I am not convinced the driver is wrong but I guess it is 
> possible. Really need someone who understands the driver operation and the 
> 2813 to take that further.
>
> Gary
>
> On Wednesday, 12 February 2020 11:41:16 UTC+10, Dan Blanchard wrote:
>>
>> The further I go, the more complex it is getting.  First, yes I have a 
>> WS-2813U-IT and yes, I did set the relative pressure to match the local 
>> weather service.
>>
>> I don't want to muddy the waters any more, but how is it that I stopped 
>> the wewx service but it is still reporting?  I'm still trying to understand 
>> this thing.
>>
>> On Tuesday, February 11, 2020 at 5:04:02 PM UTC-8, gjr80 wrote:
>>>
>>> On Wednesday, 12 February 2020 10:16:47 UTC+10, Dan Blanchard wrote:

 OK, I shut down via sudo /etc/init.d/weewx stop then I ran sudo weewxd 
 /etc/weewx/weewx.conf and it is continuing to produce data.  I see 
 that the barometer and altimeter are both the 32.xx readings while 
 pressure 
 is the same as what is reading on my station 29.9x.

 Hang on, let's go through this a bit more carefully. So you have run 
>>> WeeWX directly and are seeing all three WeeWX pressure fields. WeeWX field 
>>> pressure is matching what is on your console exactly. Fields altitude 
>>> and barometer are 'in the 32s'. By my rough calculations an absolute 
>>> pressure of 29.9inHg at 2300ft gives a barometer value of about 32.5. So on 
>>> the face of it it would appear that the driver is providing data (whether 
>>> it is right or wrong) in field pressure and WeeWX is calculating fields 
>>> barometer and altimeter as expected.
>>>
>>> Can I ge weewx to read the pressure reading in lieu of the barometer 
 altimeter reading that it is presumably doing?

>>>
>>> Now I don't understand. The 28xx driver takes the pressure value 
>>> displayed on the station hardware and feeds that to WeeWX as the WeeWX 
>>> field named pressure (after which WeeWX calculates fields barometer and 
>>> altitude). Do you want the driver to instead take that pressure value 
>>> displayed on the station hardware and feed that to WeeWX as the WeeWX field 
>>> named barometer (after which WeeWX calculates fields pressure and 
>>> altitude)? That can be done but it requires modification of the driver 
>>> code, I would not being doing that lightly, someone did not roll a dice and 
>>> randomly decide to put the pressure value from the 2813 in field 
>>> pressure, it was done for a reason.
>>>
>>> I was looking for a 2813 manual and the only manual I could find was for 
>>> a WS-2813U-IT weather station. On page 14 it talks about setting a 
>>> 'Relative value pressure reference setting' based on a value from a weather 
>>> service, airport etc. Is that your station and have you set that correctly 
>>> or if not your station is there a similar setting?
>>>
>>> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/aa1cfede-c5aa-4971-851d-bcc33c144725%40googlegroups.com.

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

[Andrew Milner]

1. use stdcalibrate section of weewx.conf
http://weewx.com/docs/usersguide.htm#StdCalibrate
2. FO station = Fine Offset weather station



On Wednesday, 12 February 2020 22:15:48 UTC+2, Dan Blanchard wrote:
>
> Andrew, how do I calibrate the pressure in weewx? Also, what's a FO 
> station?
>
> On Tuesday, February 11, 2020 at 8:01:08 PM UTC-8, Andrew Milner wrote:
>>
>> check that the absolute pressure is correct - I have had a FO station 
>> which had a dodgy pressure sensor before now.  Calibrating pressure in 
>> weewx solved it.
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6093a602-7996-4aad-ad9f-81083adb6f80%40googlegroups.com.

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

[Andrew Milner]

If you have a LaCrosse WS28xx station then according to the hardware guide 
the station outputs PRESSURE in weewx terminology - regardless of what 
LaCrosse call it - and weewx should calculate barometer and altimeter 
settings.

If pressure is incorrect then it can be adjusted as you specified - by 
adjusting pressure (not barometer or altimeter)

Make sure pressure is set to use hardware and barometer and altimeter are 
set to use software.

I am surprised barometer and altimeter are the same values - have you set 
the station's altitude in weewx.conf, and have you specified software 
generation for the values?



On Thursday, 13 February 2020 09:23:27 UTC+2, Dan Blanchard wrote:
>
> Andrew, are you suggesting that I make a 'correction' entry under 
> [StdCalibrate] such as barometer = barometer -2.8  assuming that I am 
> getting a pressure reading of 30.13  and Barometer and ALtitude readings of 
> 32.93?
>
> (see attached screenshot)
>
> On Wednesday, February 12, 2020 at 7:42:08 PM UTC-8, Andrew Milner wrote:
>>
>> 1. use stdcalibrate section of weewx.conf
>> http://weewx.com/docs/usersguide.htm#StdCalibrate
>> 2. FO station = Fine Offset weather station
>>
>>
>>
>> On Wednesday, 12 February 2020 22:15:48 UTC+2, Dan Blanchard wrote:
>>>
>>> Andrew, how do I calibrate the pressure in weewx? Also, what's a FO 
>>> station?
>>>
>>> On Tuesday, February 11, 2020 at 8:01:08 PM UTC-8, Andrew Milner wrote:
>>>>
>>>> check that the absolute pressure is correct - I have had a FO station 
>>>> which had a dodgy pressure sensor before now.  Calibrating pressure in 
>>>> weewx solved it.
>>>>
>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/059b0489-70a3-4d05-9dae-f5ddd4b3767a%40googlegroups.com.

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

[Andrew Milner]

I give up - looks correct to me.

have you run from the command line and seen the LOOP and REC data weewx is 
receiving?

what altitude is your station, and what values are you currently getting 
for pressure, barometer and altimeter?  

On Thursday, 13 February 2020 22:10:08 UTC+2, Dan Blanchard wrote:
>
> I don't know, but that makes sense so I did it.  I'm still not getting 
> desired results though.
>
> On Thursday, February 13, 2020 at 9:38:55 AM UTC-8, Kevin Davis wrote:
>>
>> Do you need a space between your minus sign and the adjustment value? 
>>
>> On Thu, Feb 13, 2020 at 9:32 AM Dan Blanchard  wrote:
>>
>>> Hey Andrew, will you please look at the attached screen shots and let me 
>>> know if this looks correct?
>>>
>>> Do I need to restart (sudo /etc/init.d/weewx restart) after I make 
>>> these changes?  I have and the changes don't seem to be taking effect.  Is 
>>> there something else I need to do?
>>>
>>> With regard to the barometer and altimeter having the same settings; I 
>>> have probably misled.  They are not exactly the same but they were 
>>> relatively close to each other compared to the pressure value.  Here are 
>>> the current readings as of now when I run sudo weewxd 
>>> /etc/weewx/weewx.conf.
>>>
>>> pressure: 29.98
>>> altimeter: 32.57
>>> barometer: 32.74
>>>
>>>
>>>
>>> On Thursday, February 13, 2020 at 12:07:50 AM UTC-8, Andrew Milner wrote:
>>>>
>>>> If you have a LaCrosse WS28xx station then according to the hardware 
>>>> guide the station outputs PRESSURE in weewx terminology - regardless of 
>>>> what LaCrosse call it - and weewx should calculate barometer and altimeter 
>>>> settings.
>>>>
>>>> If pressure is incorrect then it can be adjusted as you specified - by 
>>>> adjusting pressure (not barometer or altimeter)
>>>>
>>>> Make sure pressure is set to use hardware and barometer and altimeter 
>>>> are set to use software.
>>>>
>>>> I am surprised barometer and altimeter are the same values - have you 
>>>> set the station's altitude in weewx.conf, and have you specified software 
>>>> generation for the values?
>>>>
>>>>
>>>>
>>>> On Thursday, 13 February 2020 09:23:27 UTC+2, Dan Blanchard wrote:
>>>>>
>>>>> Andrew, are you suggesting that I make a 'correction' entry under 
>>>>> [StdCalibrate] such as barometer = barometer -2.8  assuming that I am 
>>>>> getting a pressure reading of 30.13  and Barometer and ALtitude readings 
>>>>> of 
>>>>> 32.93?
>>>>>
>>>>> (see attached screenshot)
>>>>>
>>>>> On Wednesday, February 12, 2020 at 7:42:08 PM UTC-8, Andrew Milner 
>>>>> wrote:
>>>>>>
>>>>>> 1. use stdcalibrate section of weewx.conf
>>>>>> http://weewx.com/docs/usersguide.htm#StdCalibrate
>>>>>> 2. FO station = Fine Offset weather station
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wednesday, 12 February 2020 22:15:48 UTC+2, Dan Blanchard wrote:
>>>>>>>
>>>>>>> Andrew, how do I calibrate the pressure in weewx? Also, what's a FO 
>>>>>>> station?
>>>>>>>
>>>>>>> On Tuesday, February 11, 2020 at 8:01:08 PM UTC-8, Andrew Milner 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> check that the absolute pressure is correct - I have had a FO 
>>>>>>>> station which had a dodgy pressure sensor before now.  Calibrating 
>>>>>>>> pressure 
>>>>>>>> in weewx solved it.
>>>>>>>>
>>>>>>> -- 
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/08c79655-b1af-4134-9a2b-82a4f52f051f%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/08c79655-b1af-4134-9a2b-82a4f52f051f%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/617c3831-cd98-4f19-8ac8-5d5106bd5b44%40googlegroups.com.

Re: [weewx-user] Re: Using Belchertown skin, Want to drop some database fields

[Andrew Milner]

I cant resist chipping in here - I started with PDP-8 50 yrs ago with 4K 
memory and although I love cheap disk space I still cannot stand the (IMHO) 
profligate use of memory and the grossly inefficient use of processor power 
in modern systems.



On Friday, 14 February 2020 04:31:42 UTC+2, Thomas Keffer wrote:
>
> You're getting the error because you're still asking for a plot of 
> radiation. Remove the reference in skin.conf and the error should go away.
>
> I started on an IBM 1130 with 8k of memory, 50+ years ago.  But, I've 
> learned to be enjoy that cheap memory and not sweat it. 
>
>
>
> On Thu, Feb 13, 2020 at 6:12 PM ed100  > wrote:
>
>> Perhaps a bit of background, I started coding Fortran on state of the art 
>> IBM1620, I whole total 16k of memory.  It filled a large room.  That 
>> teaches you to conserve assets. I am retired so time is not something I 
>> worry about.
>> I wrote my first shopping cart in mid-90's and had a bunch of emails from 
>> Widenius and  Lerdorf about mysql and php,I was able  break them pretty 
>> regularly for couple of years.
>>
>> When I looked at archive table in phpmyadmin it shows index is small.  
>> When I look at the actually db files on server --right now each day archive 
>> used almost 100k, so removing say 25 columns is a bunch and also makes 
>> everything run faster.   
>>
>> Anyway still don't understand why I would get errors if weewx truely just 
>> looks at the column list.
>>
>> This is a lot better than sitting in  front of a tv eating chips.
>>
>> On Thursday, February 13, 2020 at 4:54:46 PM UTC-6, ed100 wrote:
>>>
>>> I have the Belchertown skin with MQTT running nicely after some serious 
>>> help from folks here.
>>> There are a bunch of fields in the weewx mariadb database that I will 
>>> never use.  I did some searching to how to do this but didn't find out how. 
>>> I don't want to damage things, just clean up unnecessary fields. (old 
>>> habits...)
>>> I did grab the extraTemp1 and use it to show the cpu temp on the weewx 
>>> raspberry.
>>>
>>> Thanks
>>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/d054fa06-772f-4a24-ac60-1d8dc16309e2%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/280e142c-4308-4fc6-af88-91836d8277eb%40googlegroups.com.

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

[Andrew Milner]

I am  not sure I understand what you think is wrong with the readings of
Pressure 29.89
Barometer 32.609
Altimeter 32.40
and why you believe something is wrong


On Friday, 14 February 2020 05:57:36 UTC+2, Dan Blanchard wrote:
>
> Altitude is 2,320 ft. and the values are in the screen shot on the 
> previous post.  Did you see that?
>
> On Thursday, February 13, 2020 at 7:16:11 PM UTC-8, Andrew Milner wrote:
>>
>> I give up - looks correct to me.
>>
>> have you run from the command line and seen the LOOP and REC data weewx 
>> is receiving?
>>
>> what altitude is your station, and what values are you currently getting 
>> for pressure, barometer and altimeter?  
>>
>> On Thursday, 13 February 2020 22:10:08 UTC+2, Dan Blanchard wrote:
>>>
>>> I don't know, but that makes sense so I did it.  I'm still not getting 
>>> desired results though.
>>>
>>> On Thursday, February 13, 2020 at 9:38:55 AM UTC-8, Kevin Davis wrote:
>>>>
>>>> Do you need a space between your minus sign and the adjustment value? 
>>>>
>>>> On Thu, Feb 13, 2020 at 9:32 AM Dan Blanchard  
>>>> wrote:
>>>>
>>>>> Hey Andrew, will you please look at the attached screen shots and let 
>>>>> me know if this looks correct?
>>>>>
>>>>> Do I need to restart (sudo /etc/init.d/weewx restart) after I make 
>>>>> these changes?  I have and the changes don't seem to be taking effect.  
>>>>> Is 
>>>>> there something else I need to do?
>>>>>
>>>>> With regard to the barometer and altimeter having the same settings; I 
>>>>> have probably misled.  They are not exactly the same but they were 
>>>>> relatively close to each other compared to the pressure value.  Here are 
>>>>> the current readings as of now when I run sudo weewxd 
>>>>> /etc/weewx/weewx.conf.
>>>>>
>>>>> pressure: 29.98
>>>>> altimeter: 32.57
>>>>> barometer: 32.74
>>>>>
>>>>>
>>>>>
>>>>> On Thursday, February 13, 2020 at 12:07:50 AM UTC-8, Andrew Milner 
>>>>> wrote:
>>>>>>
>>>>>> If you have a LaCrosse WS28xx station then according to the hardware 
>>>>>> guide the station outputs PRESSURE in weewx terminology - regardless of 
>>>>>> what LaCrosse call it - and weewx should calculate barometer and 
>>>>>> altimeter 
>>>>>> settings.
>>>>>>
>>>>>> If pressure is incorrect then it can be adjusted as you specified - 
>>>>>> by adjusting pressure (not barometer or altimeter)
>>>>>>
>>>>>> Make sure pressure is set to use hardware and barometer and altimeter 
>>>>>> are set to use software.
>>>>>>
>>>>>> I am surprised barometer and altimeter are the same values - have you 
>>>>>> set the station's altitude in weewx.conf, and have you specified 
>>>>>> software 
>>>>>> generation for the values?
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thursday, 13 February 2020 09:23:27 UTC+2, Dan Blanchard wrote:
>>>>>>>
>>>>>>> Andrew, are you suggesting that I make a 'correction' entry under 
>>>>>>> [StdCalibrate] such as barometer = barometer -2.8  assuming that I am 
>>>>>>> getting a pressure reading of 30.13  and Barometer and ALtitude 
>>>>>>> readings of 
>>>>>>> 32.93?
>>>>>>>
>>>>>>> (see attached screenshot)
>>>>>>>
>>>>>>> On Wednesday, February 12, 2020 at 7:42:08 PM UTC-8, Andrew Milner 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> 1. use stdcalibrate section of weewx.conf
>>>>>>>> http://weewx.com/docs/usersguide.htm#StdCalibrate
>>>>>>>> 2. FO station = Fine Offset weather station
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wednesday, 12 February 2020 22:15:48 UTC+2, Dan Blanchard wrote:
>>>>>>>>>
>>>>>>>>> Andrew, how do I calibrate the pressure in weewx? Also, what's a 
>>>>>>>>> FO station?
>>>>>>>>>
>>>>>>>>> On Tuesday, February 11, 2020 at 8:01:08 PM UTC-8, Andrew Milner 
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> check that the absolute pressure is correct - I have had a FO 
>>>>>>>>>> station which had a dodgy pressure sensor before now.  Calibrating 
>>>>>>>>>> pressure 
>>>>>>>>>> in weewx solved it.
>>>>>>>>>>
>>>>>>>>> -- 
>>>>> 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...@googlegroups.com.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/weewx-user/08c79655-b1af-4134-9a2b-82a4f52f051f%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/weewx-user/08c79655-b1af-4134-9a2b-82a4f52f051f%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9a0d6cfa-8346-4bc6-95c8-89c6a70e3365%40googlegroups.com.

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

[Andrew Milner]

I would expet you to be reporting barometer = sea level pressure which is 
pressure adjusted for temperature and altitudebecause weather stations 
always report sea level pressures.

Is what you call 'correct' pressure the raw pressure of the instrument or a 
pressure which you have set.  Does the station output the raw pressure or 
the manually adjusted pressure in the loop records?



On Friday, 14 February 2020 18:07:15 UTC+2, Dan Blanchard wrote:
>
> Andrew, that's a good questions; let me clarify.  
>
> This issue started when Weather Underground (WU) stopped showing my 
> station on the maps. I found out that was because I was reporting an 
> incorrect barometric 'pressure.'  As I dug into the details I found that my 
> *station 
> *was displaying the correct pressure (29.xx) but by the time it got to 
> WU, it was displaying the barometer reading (32.xx) from weewx.  This can 
> also be demonstrated by looking at the data displayed at 
> /var/www/html/weewx/index.html 
> (see attachment) so I assume that weewx is taking the pressure from my 
> station and somehow converting it or exchanging it for barometric pressure 
> before it gets uploaded to WU.  I just want the pressure from my unit to be 
> what is reported to WU.
>
> Side note: I've been running this station for many years on a Windows 
> based system and it has been working fine.  So I know the hardware side is 
> working; just something different about how weewx reports pressure (or 
> barometer, or altimiter).
>
> Does that help clarify my issue?
>
> On Friday, February 14, 2020 at 2:24:31 AM UTC-8, Andrew Milner wrote:
>>
>> I am  not sure I understand what you think is wrong with the readings of
>> Pressure 29.89
>> Barometer 32.609
>> Altimeter 32.40
>> and why you believe something is wrong
>>
>>
>> On Friday, 14 February 2020 05:57:36 UTC+2, Dan Blanchard wrote:
>>>
>>> Altitude is 2,320 ft. and the values are in the screen shot on the 
>>> previous post.  Did you see that?
>>>
>>> On Thursday, February 13, 2020 at 7:16:11 PM UTC-8, Andrew Milner wrote:
>>>>
>>>> I give up - looks correct to me.
>>>>
>>>> have you run from the command line and seen the LOOP and REC data weewx 
>>>> is receiving?
>>>>
>>>> what altitude is your station, and what values are you currently 
>>>> getting for pressure, barometer and altimeter?  
>>>>
>>>> On Thursday, 13 February 2020 22:10:08 UTC+2, Dan Blanchard wrote:
>>>>>
>>>>> I don't know, but that makes sense so I did it.  I'm still not getting 
>>>>> desired results though.
>>>>>
>>>>> On Thursday, February 13, 2020 at 9:38:55 AM UTC-8, Kevin Davis wrote:
>>>>>>
>>>>>> Do you need a space between your minus sign and the adjustment value? 
>>>>>>
>>>>>> On Thu, Feb 13, 2020 at 9:32 AM Dan Blanchard  
>>>>>> wrote:
>>>>>>
>>>>>>> Hey Andrew, will you please look at the attached screen shots and 
>>>>>>> let me know if this looks correct?
>>>>>>>
>>>>>>> Do I need to restart (sudo /etc/init.d/weewx restart) after I make 
>>>>>>> these changes?  I have and the changes don't seem to be taking effect.  
>>>>>>> Is 
>>>>>>> there something else I need to do?
>>>>>>>
>>>>>>> With regard to the barometer and altimeter having the same settings; 
>>>>>>> I have probably misled.  They are not exactly the same but they were 
>>>>>>> relatively close to each other compared to the pressure value.  Here 
>>>>>>> are 
>>>>>>> the current readings as of now when I run sudo weewxd 
>>>>>>> /etc/weewx/weewx.conf.
>>>>>>>
>>>>>>> pressure: 29.98
>>>>>>> altimeter: 32.57
>>>>>>> barometer: 32.74
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thursday, February 13, 2020 at 12:07:50 AM UTC-8, Andrew Milner 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> If you have a LaCrosse WS28xx station then according to the 
>>>>>>>> hardware guide the station outputs PRESSURE in weewx terminology - 
>>>>>>>> regardless of what LaCrosse call it - and weewx should calculate 

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

[Andrew Milner]

if indeed, and i now tend to agree, the station displays and outputs a 
manually adjusted barometer which is set to a sea level reading from local 
weather stations and not pressure then barometer should be set to hardware 
and pressure and altimeter set to software, and not as i previously 
suggested.

On Saturday, 15 February 2020 06:22:07 UTC+2, ln77 wrote:
>
> OK… The “pressure” that your station is displaying is what it should be 
> displaying: the ambient air pressure, correct for your altitude.  In weewx, 
> this is called “barometer” because that is what weather stations report for 
> barometric pressure.  “Altimeter” is basically the same thing; there are 
> differences in exactly how it is corrected, but those differences are minor 
> and can be ignored for now.  The distinction between what weewx calls 
> “barometer” and “pressure” is important, though, for anyone more than a few 
> hundred feet above sea level.  
>
> From the manual, it appears that the WS-2813 uses a simple method for 
> correcting to sea level, by allowing the user to adjust a correction factor 
> that is applied to the actual measured pressure until the reading matches 
> some local reference barometric pressure report.  This automatically also 
> corrects for any errors in the pressure sensor itself, a handy bonus. 
> There’s not reference in the manual to any other kind of pressure being 
> reported, so it only makes sense that what it transmits via the USB 
> interface is also this corrected pressure, i.e., “barometer.”  But the 
> WS28XX driver documentation, and as far as I can tell the code also, assume 
> that the pressure reading fro the hardware is what weewx calls “pressure,” 
> that is, the actual ambient pressure before correction for altitude.  As 
> far as I can tell, all of the WS28XX LaCrosse stations work the same way as 
> yours and actually send the corrected barometer reading. Maybe because the 
> LaCrosse documentation calls it “pressure,” it was mistakenly interpreted 
> as raw pressure reading in the driver. 
>
> The bottom line is, I’m pretty sure the issue is that the driver is wrong. 
>  I’m not familiar enough with that part of the weewx code to offer a fix, 
> but it should be pretty simple for someone who is familiar with that code.  
>
>   -Les
>
>
>
> On 14 Feb 2020, at 19:44, Dan Blanchard > 
> wrote:
>
> It is likely that I am mis-using the terms altimeter, barometer, and 
> pressure.  I'll clarify what I mean here.  
>
> What I previously defined as 'correct' pressure is that the pressure 
> reported by my station (LaCrosse WS-2813U-IT) matches the National Weather 
> Service barometer reading (
> https://forecast.weather.gov/MapClick.php?lat=47.7151345&lon=-116.946676#.XkdkXDFKiUk).
>  
> For example, *right now* my station is reading 30.06 pressure and the NWS 
> site is reporting 30.0 barometer.  Ultimately I just want my WS-2813 
> pressure reading to match the WU pressure reading (
> https://www.wunderground.com/dashboard/pws/KIDPOSTF43).  Right now it 
> appears that WU is reading the weewx barometer reading.  Is there a way to 
> have weewx report the pressure reading to WU?
>
> My WS-2813 outputs the manually adjusted pressure in the Loop records (see 
> attachment).  I don't see a way to change that.  Here is a link to the 
> manual (
> https://www.lacrossetechnology.com/media/catalog/product/w/s/ws-2813u-it.pdf
> ).
>
> On Friday, February 14, 2020 at 9:22:17 AM UTC-8, Andrew Milner wrote:
>>
>> I would expect you to be reporting barometer = sea level pressure which 
>> is pressure adjusted for temperature and altitude because weather stations 
>> always report sea level pressures.
>>
>> Is what you call 'correct' pressure the raw pressure of the instrument or 
>> a pressure which you have set.  Does the station output the raw pressure or 
>> the manually adjusted pressure in the loop records?
>>
>>
>>
>> On Friday, 14 February 2020 18:07:15 UTC+2, Dan Blanchard wrote:
>>>
>>> Andrew, that's a good questions; let me clarify.  
>>>
>>> This issue started when Weather Underground (WU) stopped showing my 
>>> station on the maps. I found out that was because I was reporting an 
>>> incorrect barometric 'pressure.'  As I dug into the details I found that my 
>>> *station 
>>> *was displaying the correct pressure (29.xx) but by the time it got to 
>>> WU, it was displaying the barometer reading (32.xx) from weewx.  This can 
>>> also be demonstrated by looking at the data displayed at 
>>> /var/www/html/weewx/index.html 
>>> (see attachment) so I assume that weew

[weewx-user] Re: problem with wee extension

[Andrew Milner]

did you try specifying the full path to your specific weewx.conf

eg
sudo /home/weewx/bin/wee_extension  --config=/home/weewx/bin/weewx.conf 
--list  or something like that anyway

On Saturday, 15 February 2020 20:31:45 UTC+2, angry tux wrote:
>
> Hi,
>
> thanks for taking care. 
> I have a dual installation done for SMA and WH1080, therefore the wee_conf 
> is under /home/weewx/bin/ same directory as the wee_extension
>
> I did install some other extensions a year ago, but do not remember if I 
> did anything different. Or could the last two updates of Weewx be 
> responsible?
>
> Best regards
>
>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c73cae4a-4d89-4262-81aa-c171c9aee88d%40googlegroups.com.

Re: [weewx-user] Re: WS3080 Lockup - FineOffsetUsb workaround not working.

[Andrew Milner]

I think lost connection:64 indicates a lost connection beteen base station 
and external transmitter - probably caused by a low battery - have you 
tried changing the batteries in the external transmitter??

On Saturday, 15 February 2020 23:50:05 UTC+2, Dave, G1OGY wrote:
>
> I believe I have identified a hitherto unreported "lockup" situation with 
> a Fine Offset system.
> The USB lockup suffered by certain systems is known and work-arounds have 
> been published 
> (not least by me); this problem is manifest by Wind, Rain, Temp/Humidity 
> being absent while Solar
> data continues to be reported on the console.
> The weewx log prints the following report:
>weewx[]: fousb: station status {'unknown': 0, 
> 'lost_connection': 64, 'rain_overflow': 0} (64)
>
> Note that this print is ~similar~ to that printed after startup and 
> catch-up of EEPROM data:
> weewx[]: engine: Starting main packet loop.
> weewx[]: fousb: station status {'unknown': 
> 0, 'lost_connection': 0, 'rain_overflow': 0} (0)
>
> The difference being the `'lost_connection': 64,` inclusion and the final 
> characters: `(64)`.
> This is the (new) lockup condition. There is no "Errno" print.
>
> Because the majority of the log text is printed while the system is in a 
> benign state and not 
> being sufficiently clever to grep out either/or of the error condition 
> prints - the quoted long text within the 
> string defeated me - I have modified my lockup-detector script to capture 
> the unique `(64)` and fire off the 
> USB power cycler script. 
> It is sufficient.
>
>
>
> #!/bin/bash
> # monitorlockup
> # watch the weewx log file for lockup condition and use USB power 
> recycling to clear the lockup
> # 20190622+20200110
>
>
> LOGfile=/home/weewx/weather/logs/weewx.log
> tail -Fn0 $LOGfile |
> while read line ; do
> echo "$line" | grep -qe 'Errno 110' -e '(64)'
> if [ $? = 0 ]
> then
> logger -t monitorlockup Error No 110 or lost connection 64 
> Observed in weewx.log
> /home/weewx/powercycleusb
> fi
> done
> READY=1
>
>
>
>
> and the power-cycler (requires acquisition and build of `uhubctl`)
>
>
>
> #!/bin/bash
> /home/weewx/uhubctl -d 15 -a cycle -p 2
>
>
> logger -t powercycleusb USB port 2 power cycled
>
> READY=0
>
>
> YMMV!
> [RPi2B, Raspian 10.2, Weewx 3.9.2: http://g1ogy.com/wx ]
>
> -- 
> Dave, G1OGY
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/137043ea-109e-49ab-a8dd-87f83bf37ddb%40googlegroups.com.

Re: [weewx-user] png images for index.html not updating but the data is being updated and the /smartphone images are being updated

[Andrew Milner]

what browser are you using??  I have found recently that microsoft edge 
seems to have entered a world of its own and now appears to require 
frequent forced refresh of pages to get the png's to update (Using shift/ 
refresh)  This has been happening for the past 2-3 weeks and was never 
needed before.



On Sunday, 16 February 2020 02:05:37 UTC+2, Troy Lass wrote:
>
> Ok, let me start over.  It's working properly now and it worked properly 
> for 2 days then froze, the page was stuck with on the previous day and 
> time.  The images were being written but the data was not updating.
>
> I did the following
> weewx stop
> wee_device --info
> wee_device --start
> weewx start
>
> After this the data was pulled from the data logger as expected but for 
> something like 2 hours the png files were not updated for the base 
> index.html file, even though the images for the /mobilephone were being 
> updated.  after some time,  over an hour, the images started to be updated 
> with no further action from me.  If it just takes a while for it to get 
> caught up I'm good, however I don't understand why I keep getting the page 
> frozen on a day/time.  This is what started the whole debugging process 
> before and caused me to think the data logger was bad.
>
> When I ran on the console bypassing the datalogger with the following in 
> the weewx.conf it ran without freezing but that was only while I was 
> waiting for the new datalogger so only a couple days.
>
> record_generation = software
> no_catchup = True
>
> When I opened this post the png images were not updating, but now they are 
> and have been for a day.
>
> What could cause the base page to keep from updating and it seems that a 
> wee_device --start fixes?  I'm wondering if there may be an issue with the 
> envoy I'm using now that could cause it to stop updating that would need a 
> --start?
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e978b9e2-f903-44c7-80a3-c86e0119b72f%40googlegroups.com.

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

[Andrew Milner]

pressure, barometer and altimeter look reasonable to me.  why are they 
wrong?




On Monday, 17 February 2020 03:09:28 UTC+2, Dan Blanchard wrote:
>
> Andrew, I've set barometer = hardware and altimeter = software and 
> pressure = software.  I've restarted weewx, but nothing has changed in the 
> Loop.
>
> On Friday, February 14, 2020 at 9:30:06 PM UTC-8, Andrew Milner wrote:
>>
>> if indeed, and i now tend to agree, the station displays and outputs a 
>> manually adjusted barometer which is set to a sea level reading from local 
>> weather stations and not pressure then barometer should be set to hardware 
>> and pressure and altimeter set to software, and not as i previously 
>> suggested.
>>
>> On Saturday, 15 February 2020 06:22:07 UTC+2, ln77 wrote:
>>>
>>> OK… The “pressure” that your station is displaying is what it should be 
>>> displaying: the ambient air pressure, correct for your altitude.  In weewx, 
>>> this is called “barometer” because that is what weather stations report for 
>>> barometric pressure.  “Altimeter” is basically the same thing; there are 
>>> differences in exactly how it is corrected, but those differences are minor 
>>> and can be ignored for now.  The distinction between what weewx calls 
>>> “barometer” and “pressure” is important, though, for anyone more than a few 
>>> hundred feet above sea level.  
>>>
>>> From the manual, it appears that the WS-2813 uses a simple method for 
>>> correcting to sea level, by allowing the user to adjust a correction factor 
>>> that is applied to the actual measured pressure until the reading matches 
>>> some local reference barometric pressure report.  This automatically also 
>>> corrects for any errors in the pressure sensor itself, a handy bonus. 
>>> There’s not reference in the manual to any other kind of pressure being 
>>> reported, so it only makes sense that what it transmits via the USB 
>>> interface is also this corrected pressure, i.e., “barometer.”  But the 
>>> WS28XX driver documentation, and as far as I can tell the code also, assume 
>>> that the pressure reading fro the hardware is what weewx calls “pressure,” 
>>> that is, the actual ambient pressure before correction for altitude.  As 
>>> far as I can tell, all of the WS28XX LaCrosse stations work the same way as 
>>> yours and actually send the corrected barometer reading. Maybe because the 
>>> LaCrosse documentation calls it “pressure,” it was mistakenly interpreted 
>>> as raw pressure reading in the driver. 
>>>
>>> The bottom line is, I’m pretty sure the issue is that the driver is 
>>> wrong.  I’m not familiar enough with that part of the weewx code to offer a 
>>> fix, but it should be pretty simple for someone who is familiar with that 
>>> code.  
>>>
>>>   -Les
>>>
>>>
>>>
>>> On 14 Feb 2020, at 19:44, Dan Blanchard  wrote:
>>>
>>> It is likely that I am mis-using the terms altimeter, barometer, and 
>>> pressure.  I'll clarify what I mean here.  
>>>
>>> What I previously defined as 'correct' pressure is that the pressure 
>>> reported by my station (LaCrosse WS-2813U-IT) matches the National Weather 
>>> Service barometer reading (
>>> https://forecast.weather.gov/MapClick.php?lat=47.7151345&lon=-116.946676#.XkdkXDFKiUk).
>>>  
>>> For example, *right now* my station is reading 30.06 pressure and the 
>>> NWS site is reporting 30.0 barometer.  Ultimately I just want my WS-2813 
>>> pressure reading to match the WU pressure reading (
>>> https://www.wunderground.com/dashboard/pws/KIDPOSTF43).  Right now it 
>>> appears that WU is reading the weewx barometer reading.  Is there a way to 
>>> have weewx report the pressure reading to WU?
>>>
>>> My WS-2813 outputs the manually adjusted pressure in the Loop records 
>>> (see attachment).  I don't see a way to change that.  Here is a link to the 
>>> manual (
>>> https://www.lacrossetechnology.com/media/catalog/product/w/s/ws-2813u-it.pdf
>>> ).
>>>
>>> On Friday, February 14, 2020 at 9:22:17 AM UTC-8, Andrew Milner wrote:
>>>>
>>>> I would expect you to be reporting barometer = sea level pressure which 
>>>> is pressure adjusted for temperature and altitude because weather stations 
>>>> always report sea level pressures.
>>>>
>>>> Is what you call 'correct' pressure the raw pressur

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

[Andrew Milner]

well if it is hard coded for pressure then the station adjustment made by 
the OP should be to set his station to a known sea level pressure and 
subtract a correction for altitude (2.6 for 2300 ft I think) and all should 
then be ok

On Monday, 17 February 2020 07:09:35 UTC+2, ln77 wrote:
>
> Setting those that way won’t fix the problem.  Those settings are hints to 
> weewx about what to use when the weather station hardware provides multiple 
> values.  The WS28XX driver is hard-coded to interpret the data from the 
> station as weewx “pressure,” and that is the only pressure-related datum 
> sent by the WS28XX stations.  
>
>   -Les
>
>
>
> On 16 Feb 2020, at 17:09, Dan Blanchard > 
> wrote:
>
> Andrew, I've set barometer = hardware and altimeter = software and 
> pressure = software.  I've restarted weewx, but nothing has changed in the 
> Loop.
>
> On Friday, February 14, 2020 at 9:30:06 PM UTC-8, Andrew Milner wrote:
>>
>> if indeed, and i now tend to agree, the station displays and outputs a 
>> manually adjusted barometer which is set to a sea level reading from local 
>> weather stations and not pressure then barometer should be set to hardware 
>> and pressure and altimeter set to software, and not as i previously 
>> suggested.
>>
>> On Saturday, 15 February 2020 06:22:07 UTC+2, ln77 wrote:
>>>
>>> OK… The “pressure” that your station is displaying is what it should be 
>>> displaying: the ambient air pressure, correct for your altitude.  In weewx, 
>>> this is called “barometer” because that is what weather stations report for 
>>> barometric pressure.  “Altimeter” is basically the same thing; there are 
>>> differences in exactly how it is corrected, but those differences are minor 
>>> and can be ignored for now.  The distinction between what weewx calls 
>>> “barometer” and “pressure” is important, though, for anyone more than a few 
>>> hundred feet above sea level.  
>>>
>>> From the manual, it appears that the WS-2813 uses a simple method for 
>>> correcting to sea level, by allowing the user to adjust a correction factor 
>>> that is applied to the actual measured pressure until the reading matches 
>>> some local reference barometric pressure report.  This automatically also 
>>> corrects for any errors in the pressure sensor itself, a handy bonus. 
>>> There’s not reference in the manual to any other kind of pressure being 
>>> reported, so it only makes sense that what it transmits via the USB 
>>> interface is also this corrected pressure, i.e., “barometer.”  But the 
>>> WS28XX driver documentation, and as far as I can tell the code also, assume 
>>> that the pressure reading fro the hardware is what weewx calls “pressure,” 
>>> that is, the actual ambient pressure before correction for altitude.  As 
>>> far as I can tell, all of the WS28XX LaCrosse stations work the same way as 
>>> yours and actually send the corrected barometer reading. Maybe because the 
>>> LaCrosse documentation calls it “pressure,” it was mistakenly interpreted 
>>> as raw pressure reading in the driver. 
>>>
>>> The bottom line is, I’m pretty sure the issue is that the driver is 
>>> wrong.  I’m not familiar enough with that part of the weewx code to offer a 
>>> fix, but it should be pretty simple for someone who is familiar with that 
>>> code.  
>>>
>>>   -Les
>>>
>>>
>>>
>>> On 14 Feb 2020, at 19:44, Dan Blanchard  wrote:
>>>
>>> It is likely that I am mis-using the terms altimeter, barometer, and 
>>> pressure.  I'll clarify what I mean here.  
>>>
>>> What I previously defined as 'correct' pressure is that the pressure 
>>> reported by my station (LaCrosse WS-2813U-IT) matches the National Weather 
>>> Service barometer reading (
>>> https://forecast.weather.gov/MapClick.php?lat=47.7151345&lon=-116.946676#.XkdkXDFKiUk).
>>>  
>>> For example, *right now* my station is reading 30.06 pressure and the 
>>> NWS site is reporting 30.0 barometer.  Ultimately I just want my WS-2813 
>>> pressure reading to match the WU pressure reading (
>>> https://www.wunderground.com/dashboard/pws/KIDPOSTF43).  Right now it 
>>> appears that WU is reading the weewx barometer reading.  Is there a way to 
>>> have weewx report the pressure reading to WU?
>>>
>>> My WS-2813 outputs the manually adjusted pressure in the Loop records 
>>> (see attachment).  I don't see a way to change that. 

[weewx-user] Re: Fixing my database

[Andrew Milner]

depends how completely you want to backfill!!
in the archive table there are columns for rain and rainrate which is a) 
the rain fall in the arhive period and b) the rainrate in the archive 
period.  For stations which do not provide rainrate this may well be a 
rainrate which decays over a period .

If you can fill in all the archive periods with the rainfall data the 
summary data could be recreated from the archive using drop daily and 
rebuild daily options of weewx_database utility.

alternatively you could fill in the columns in the rain daily summary table 
and the rainrate daily summary table for all the days you are missing




On Monday, 17 February 2020 17:00:58 UTC+2, Auchtermuchty Weather wrote:
>
> I've finally sorted out my rain gauge, but now I need to backfill the 
> rainfall data.  There is a station near enough to me to use their data, but 
> I could do with some guidance about what needs updating in my database, and 
> if I need to run anything afterwards.  I used SQL for years in the day job 
> so no problems there.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4ac07263-e72b-438f-9f43-2079fc72088e%40googlegroups.com.

[weewx-user] Re: Belchertown skin works, MQTT not updating real time

[Andrew Milner]

the LOOP data is not written to the weewx database, and the REC data is the 
AVERAGE of the LOOP data during the archive period - so you are most 
unlikely to have corresponding values for LOOP and REC wind data

On Monday, 17 February 2020 19:01:58 UTC+2, Fabio wrote:
>
> thank you for your reply, I started weewx by hand and the values of data 
> are different between database and the data showing on browser.  
> for example these are the data that come to me from the log and the data 
> that 's correctly written to the database archive:
>
> LOOP:windDir: 225.0, windGust: 4.9174525, windGustDir: 225.0, 
> windrun: 0.16093481, windSpeed: 2.6822468, windSpeed10: 
> 2.6822468, yearET: 0.0, yearRain: 396.60099
>
> while I received via browser for example for windspeed: 6.2 knots 
> almost double for the real value.
>
> my configuration for mqtt is this one: 
>[[MQTT]]
> server_url = mqtt://admin:admin23@localhost:1883/
> topic = "weather"
> unit_system = METRIC
> binding = archive, loop
> aggregation = aggregate
>
>
> [[[Extras]]]
> .
> mqtt_websockets_enabled = 1
> mqtt_websockets_port = 9001
> mqtt_websockets_topic = "weather/loop"
>
> I can't understand where is the issue.
> thanks in advance for your support
>
> Il giorno lunedì 17 febbraio 2020 17:06:50 UTC+1, ed100 ha scritto:
>>
>> fabio:
>>
>> The way I understand, MQTT updates the homepage when there is a loop.  
>> The charts below  are updated when the archive is run.  If you mouse over 
>> the wind you can see the difference in time between the chart and the time 
>> at the top of the page.  Don't know if this helps at all, I am just 
>> learning this stuff.
>>
>> You can also look at the values is in the database to see if they are 
>> right.  If you start weewx by hand without a daemon you can watch the loop 
>> values scroll by. they start with loop, the lines that start rec are the 
>> archive ones.
>>
>> On Friday, February 7, 2020 at 4:15:46 PM UTC-6, ed100 wrote:
>>>
>>> Belchertown skin is great and serves the data on website 192.168.1.200 
>>> just fine.  I just can't get MQTT to update the loops - it connects and 
>>> waits.
>>> I have read and tried several of the things mentioned on the net but no 
>>> joy yet.
>>> There are no error msgs that I have found.  What am I missing?
>>>
>>> from http://192.168.1.200/weewx/belchertown/index.html
>>> Connected. Waiting for data. Last Updated February 7, 2020, 3:22:00 PM
>>>
>>> belchertown: version 1.1b8
>>> restx: MQTT: service version is 0.19
>>> Initializing weewx version 4.0.0b11
>>> Using Python 3.7.3 (default, Apr  3 2019, 05:39:12) #012[GCC 8.2.0]
>>> Platform Linux-4.19.93-v7l+-armv7l-with-debian-10.2
>>> Raspberry rpi4
>>> Weewx is running on 192.168.1.190 (dedicated for weather things)
>>> webserver is running on 192.168.1.200
>>> pi is user on both.
>>>
>>> 192.168.1.200 is NAS for all my boxes, 5 raspberrys, two ubuntu boxes, 
>>> two Arduino boxes.
>>> 192.168.1.190 is setup and running out in our yard where the windspeed, 
>>> winddir, rain, temp etc are measured.
>>> Data is stored in an mariadb and served by ngnix running on 
>>> 192.168.1.200.
>>>
>>> from /etc/mosquitto/conf.d/myconfig.conf on 192.168.1.200:
>>>
>>> persistence false
>>>
>>> # mqtt
>>> listener 1883
>>> protocol mqtt
>>>
>>> # websockets
>>> listener 9001
>>> protocol websockets
>>>
>>> allow_anonymous true
>>>
>>> acl_file /etc/mosquitto/acl
>>>
>>> log_type all
>>> ===
>>> from  /etc/mosquitto/acl  on 192.168.1.200:
>>> # Allow anonymous access to the sys
>>> topic read $SYS/#
>>>
>>> # Allow anonymous to read weather
>>> topic weather/#
>>>
>>> # weewx readwrite to the loop
>>> user pi
>>> topic weather/#
>>>
>>> ==
>>>
>>> from weewx.conf:
>>>
>>> station_type = BCRobotics
>>> station_url = http://192.168.1.200
>>>
>>> [[MQTT]]
>>> server_url =  mqtt://192.168.1.200:1883/
>>> topic = weather/loop
>>> unit_system = US
>>> binding = archive, loop
>>> aggregation = aggregate
>>>
>>> [[Belchertown]]
>>> skin = Belchertown
>>> enable = true 
>>> HTML_ROOT = /var/www/html/weewx/belchertown
>>> [[[Extras]]]
>>>belchertown_root_url = "http://192.168.1.200";
>>>theme = auto
>>>theme_toggle_enabled = 1
>>>site_title = "Banjo's Wx Home" (Banjo is our dog, a lab 
>>> -- He checks the weather on his Ipaw.)
>>>home_page_header = "Banjo's Wx Conditions"
>>>mqtt_websockets_enabled = 1
>>>mqtt_websockets_host = "192.168.1.200"
>>>mqtt_websockets_port = 9001
>>>mqtt_websockets_topic = "weather/loop"
>>>mqtt_websockets_ssl = 0
>>>disconnect_live_website_visitor = 90
>>>log_failure = true
>>> 

[weewx-user] Re: Belchertown skin works, MQTT not updating real time

[Andrew Milner]

yes, you are correct - the REC is written to the archive table, but the 
data in the REC is the average of the LOOP data over the archive period.(if 
software generation is used).



On Monday, 17 February 2020 22:54:30 UTC+2, ed100 wrote:
>
> Andrew:  Isn't the data in the REC what is written to the archive table?
>
> I have MQTT updating my homepage every 10 sec. archive table gets new data 
> every 5 minutes.
>
>
>
> On Friday, February 7, 2020 at 4:15:46 PM UTC-6, ed100 wrote:
>>
>> Belchertown skin is great and serves the data on website 192.168.1.200 
>> just fine.  I just can't get MQTT to update the loops - it connects and 
>> waits.
>> I have read and tried several of the things mentioned on the net but no 
>> joy yet.
>> There are no error msgs that I have found.  What am I missing?
>>
>> from http://192.168.1.200/weewx/belchertown/index.html
>> Connected. Waiting for data. Last Updated February 7, 2020, 3:22:00 PM
>>
>> belchertown: version 1.1b8
>> restx: MQTT: service version is 0.19
>> Initializing weewx version 4.0.0b11
>> Using Python 3.7.3 (default, Apr  3 2019, 05:39:12) #012[GCC 8.2.0]
>> Platform Linux-4.19.93-v7l+-armv7l-with-debian-10.2
>> Raspberry rpi4
>> Weewx is running on 192.168.1.190 (dedicated for weather things)
>> webserver is running on 192.168.1.200
>> pi is user on both.
>>
>> 192.168.1.200 is NAS for all my boxes, 5 raspberrys, two ubuntu boxes, 
>> two Arduino boxes.
>> 192.168.1.190 is setup and running out in our yard where the windspeed, 
>> winddir, rain, temp etc are measured.
>> Data is stored in an mariadb and served by ngnix running on 192.168.1.200.
>>
>> from /etc/mosquitto/conf.d/myconfig.conf on 192.168.1.200:
>>
>> persistence false
>>
>> # mqtt
>> listener 1883
>> protocol mqtt
>>
>> # websockets
>> listener 9001
>> protocol websockets
>>
>> allow_anonymous true
>>
>> acl_file /etc/mosquitto/acl
>>
>> log_type all
>> ===
>> from  /etc/mosquitto/acl  on 192.168.1.200:
>> # Allow anonymous access to the sys
>> topic read $SYS/#
>>
>> # Allow anonymous to read weather
>> topic weather/#
>>
>> # weewx readwrite to the loop
>> user pi
>> topic weather/#
>>
>> ==
>>
>> from weewx.conf:
>>
>> station_type = BCRobotics
>> station_url = http://192.168.1.200
>>
>> [[MQTT]]
>> server_url =  mqtt://192.168.1.200:1883/
>> topic = weather/loop
>> unit_system = US
>> binding = archive, loop
>> aggregation = aggregate
>>
>> [[Belchertown]]
>> skin = Belchertown
>> enable = true 
>> HTML_ROOT = /var/www/html/weewx/belchertown
>> [[[Extras]]]
>>belchertown_root_url = "http://192.168.1.200";
>>theme = auto
>>theme_toggle_enabled = 1
>>site_title = "Banjo's Wx Home" (Banjo is our dog, a lab -- 
>> He checks the weather on his Ipaw.)
>>home_page_header = "Banjo's Wx Conditions"
>>mqtt_websockets_enabled = 1
>>mqtt_websockets_host = "192.168.1.200"
>>mqtt_websockets_port = 9001
>>mqtt_websockets_topic = "weather/loop"
>>mqtt_websockets_ssl = 0
>>disconnect_live_website_visitor = 90
>>log_failure = true
>>log_success = true
>>
>>
>> ==
>> sudo tail -25 /var/log/mosquitto/mosquitto.logon 192.168.1.200
>> 1581110894: New connection from 192.168.1.190 on port 1883.
>> 1581110894: New client connected from 192.168.1.190 as weewx_c7c0a139 
>> (c1, k60).
>> 1581110894: No will message specified.
>> 1581110894: Sending CONNACK to weewx_c7c0a139 (0, 0)
>> 1581110894: Received PUBLISH from weewx_c7c0a139 (d0, q0, r0, m0, 
>> 'weather/loop/loop', ... (824 bytes))
>> 1581110894: Received DISCONNECT from weewx_c7c0a139
>> 1581110894: Client weewx_c7c0a139 disconnected.
>>
>> =
>> from mosquitto_sub -v -t '#' (on 192.168.1.200)
>> weather/loop/loop {"dateTime": "1581110268.0", "usUnits": "1.0", 
>> "windSpeed_mph": "23.5736", "windDir": "225.0", "outTemp_F": 
>> "48.44069175713479", "rainRate_inch_per_hour": "0.0", "pressure_inHg": 
>> "29.537724517082214", "inTemp_F": "48.44069175713479", "inHumidity": 
>> "40.10936680311917", "outHumidity": "40.10936680311917", "extraTemp1_F": 
>> "29.0", "altimeter_inHg": "30.025126837815904", "appTemp_F": 
>> "30.718254859246187", "barometer_inHg": "30.032273523343694", 
>> "beaufort_count": "5.0", "cloudbase_foot": "5707.996577917219", 
>> "dewpoint_F": "25.30550681429903", "heatindex_F": "48.44069175713479", 
>> "humidex_F": "48.4406917571348", "inDewpoint_F": "25.30550681429903", 
>> "maxSolarRad_Wpm2": "337.7856265409849", "windchill_F": 
>> "40.906702199301414", "hourRain_in": "0.02794", "rain24_in": 
>> "0.447040005", "dayRain_in": "0.167

[weewx-user] Re: WeePOST Extension

[Andrew Milner]

http://weewx.com/docs/usersguide.htm#[StdRESTful]


On Tuesday, 18 February 2020 19:39:57 UTC+2, Walter Smith wrote:
>
> Andrew, this is great!  I am working my way through it all.  I have the 
> data being posted, but I get an entry in syslog for every post:
>
> Feb 18 10:45:59 raspberrypi2 weewx[30469]: restx: WeePOST: Published 
> record 2020-02-18 10:45:59 CST (1582044359)
> Feb 18 10:46:01 raspberrypi2 weewx[30469]: restx: WeePOST: Published 
> record 2020-02-18 10:46:02 CST (1582044362)
> Feb 18 10:46:03 raspberrypi2 weewx[30469]: restx: WeePOST: Published 
> record 2020-02-18 10:46:04 CST (1582044364)
> Feb 18 10:46:05 raspberrypi2 weewx[30469]: restx: WeePOST: Published 
> record 2020-02-18 10:46:06 CST (1582044366)
> Feb 18 10:46:07 raspberrypi2 weewx[30469]: restx: WeePOST: Published 
> record 2020-02-18 10:46:08 CST (1582044368)
> Feb 18 10:46:09 raspberrypi2 weewx[30469]: restx: WeePOST: Published 
> record 2020-02-18 10:46:10 CST (1582044370)
>
> Is there a way to turn (most) of those off?
>
> more complete log attached.
>
> Thanks, 
>
> Walt
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6cbfea35-4c3f-4c04-83d1-7fa618a92dee%40googlegroups.com.

[weewx-user] Re: Fixing my database

[Andrew Milner]

you can put all the rain in one archive interval or you can spred it over 
many as long as the total for the day is correct - the choice is yours.



On Wednesday, 19 February 2020 10:59:05 UTC+2, Auchtermuchty Weather wrote:
>
> Ah I think I understand now.  
>
> After a poke around looking at the .py files, I think I need to update 
> archive.rain for one row for that date, then run wee_database 
> --rebuild_daily for the date range I've altered.
>
> And I need to make sure I update just one row in Archive for the date, not 
> all of them!  I have a row every 5 minutes, so the one for 12:00:00 seems 
> appropriate.  I can check before I try the update to make sure they all 
> exists.  Still like the idea of using the Excel with the data from the 
> other site to build the correct SQL.
>
>
> On Monday, 17 February 2020 16:42:29 UTC, Auchtermuchty Weather wrote:
>>
>> Thanks.
>>
>> I need to go back to late November.  
>>
>> I've found out how to get the date & time from the dateTime column.  :)
>>
>> But is it just archive_day_rain.sum I need to update?
>>
>> The weather station is one of the FineOffset ones, does this do rain 
>> rate?  I always assumed it was calculated.  But if fixing the rain & 
>> running weewx_database will fix it that will be great.
>>
>> Looks like I need to read up weewx_database.  I can pick up the external 
>> data and put it in Excel which will let me build the SQL statements.  And 
>> yes, I will stop weewx and take a copy of weewx.sdb before I start changing 
>> data!
>>
>>
>> On Monday, 17 February 2020 15:18:49 UTC, Andrew Milner wrote:
>>>
>>> depends how completely you want to backfill!!
>>> in the archive table there are columns for rain and rainrate which is a) 
>>> the rain fall in the arhive period and b) the rainrate in the archive 
>>> period.  For stations which do not provide rainrate this may well be a 
>>> rainrate which decays over a period .
>>>
>>> If you can fill in all the archive periods with the rainfall data the 
>>> summary data could be recreated from the archive using drop daily and 
>>> rebuild daily options of weewx_database utility.
>>>
>>> alternatively you could fill in the columns in the rain daily summary 
>>> table and the rainrate daily summary table for all the days you are missing
>>>
>>>
>>>
>>>
>>> On Monday, 17 February 2020 17:00:58 UTC+2, Auchtermuchty Weather wrote:
>>>>
>>>> I've finally sorted out my rain gauge, but now I need to backfill the 
>>>> rainfall data.  There is a station near enough to me to use their data, 
>>>> but 
>>>> I could do with some guidance about what needs updating in my database, 
>>>> and 
>>>> if I need to run anything afterwards.  I used SQL for years in the day job 
>>>> so no problems there.
>>>>
>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1aa1fac2-e694-43e7-a2f6-307ecc8af427%40googlegroups.com.

Re: [weewx-user] Non supported weather station

[Andrew Milner]

I doubt if you will find wunderground to be reliable if you try and access 
it to get your data every 60 seconds  Wunderground is just not designed 
for such usage.





On Thursday, 20 February 2020 10:43:05 UTC+2, Ivan Schrooyen wrote:
>
> Hello Thomas,
>
> Thanks for your answer.
> The model that I have is the following. I did not see any possibility to 
> export the data to something else than wunderground.
>
> https://www.bresser.de/fr/Temps/BRESSER-Station-meteo-couleur-WIFI-avec-capteur-exterieur-5-en-1.html
>  
> Please let me know if I am wrong, this would help.
>
> Also, what I intend to do (even if not super clean), is to run a python 
> script from my NAS every 60s.
> This script would check on wunderground if there is new data online 
> compared to the text file stored on the NAS.
> Then it would update the text file on the NAS. Then use this text file to 
> update a graph available on a website/app.
> Not sure yet whether this is simple or not...
>
> Is there any easy app that you suggest to use?
>
> Thanks in advance,
> Ivan
>
> *Ivan Schrooyen*
>
> *M: **+33 6 98 38 72 56*
> *M: **+47 950 41 710*
> *E**: **ivan.s...@gmail.com *
> *A: 8 Sakkastadvika**, 5538 Haugesund, Norway*
>
>
>
>
> Le mer. 19 févr. 2020 à 15:47, Thomas Keffer  > a écrit :
>
>> Which Bresser model? Some are Fine Offset clones. 
>>
>> It is possible to "import" data from the Weather Underground, but it is a 
>> single-time, batch process, not intended for continuous use.
>>
>> -tk
>>
>> On Wed, Feb 19, 2020 at 5:51 AM Ivan Schrooyen > > wrote:
>>
>>> Hello,
>>> I would like to use Weewx to process the waeather data from my personal 
>>> weather station.
>>> This station (Bresser) is not supported by Weewx, but the data is 
>>> transferred to Wunderground (table).
>>> So, I am wondering whether it is possible to get the data from there, 
>>> process it and send it to another form of website/app?
>>> Thanks in advance,
>>> Ivan
>>>
>>> -- 
>>> 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...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/1ed76a9a-0b2a-4c74-b023-c70b080e193c%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEBRM_N_83SCjakky%2BEf8fr-SLU%3DVAnXGxO0oxWTHtZpLw%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b64dd53c-def0-4378-8067-5b7ba24e93d7%40googlegroups.com.

Re: [weewx-user] Non supported weather station

[Andrew Milner]

Interceptor perhaps so that weewx intercepts the data on its way from the 
station to wunderground .



On Thursday, 20 February 2020 14:00:26 UTC+2, Ivan Schrooyen wrote:
>
> Hello Andrew,
>
> Is there a cleaner way to get my data out of my weather station then?
> I am open to any suggestions...
>
> Ivan
>
> *Ivan Schrooyen*
>
> *M: **+33 6 98 38 72 56*
> *M: **+47 950 41 710*
> *E**: **ivan.s...@gmail.com *
> *A: 8 Sakkastadvika**, 5538 Haugesund, Norway*
>
>
>
>
> Le jeu. 20 févr. 2020 à 10:07, Andrew Milner  > a écrit :
>
>> I doubt if you will find wunderground to be reliable if you try and 
>> access it to get your data every 60 seconds  Wunderground is just not 
>> designed for such usage.
>>
>>
>>
>>
>>
>> On Thursday, 20 February 2020 10:43:05 UTC+2, Ivan Schrooyen wrote:
>>>
>>> Hello Thomas,
>>>
>>> Thanks for your answer.
>>> The model that I have is the following. I did not see any possibility to 
>>> export the data to something else than wunderground.
>>>
>>> https://www.bresser.de/fr/Temps/BRESSER-Station-meteo-couleur-WIFI-avec-capteur-exterieur-5-en-1.html
>>>  
>>> Please let me know if I am wrong, this would help.
>>>
>>> Also, what I intend to do (even if not super clean), is to run a python 
>>> script from my NAS every 60s.
>>> This script would check on wunderground if there is new data online 
>>> compared to the text file stored on the NAS.
>>> Then it would update the text file on the NAS. Then use this text file 
>>> to update a graph available on a website/app.
>>> Not sure yet whether this is simple or not...
>>>
>>> Is there any easy app that you suggest to use?
>>>
>>> Thanks in advance,
>>> Ivan
>>>
>>> *Ivan Schrooyen*
>>>
>>> *M: **+33 6 98 38 72 56*
>>> *M: **+47 950 41 710*
>>> *E**: **ivan.s...@gmail.com*
>>> *A: 8 Sakkastadvika**, 5538 Haugesund, Norway*
>>>
>>>
>>>
>>>
>>> Le mer. 19 févr. 2020 à 15:47, Thomas Keffer  a 
>>> écrit :
>>>
>>>> Which Bresser model? Some are Fine Offset clones. 
>>>>
>>>> It is possible to "import" data from the Weather Underground, but it is 
>>>> a single-time, batch process, not intended for continuous use.
>>>>
>>>> -tk
>>>>
>>>> On Wed, Feb 19, 2020 at 5:51 AM Ivan Schrooyen  
>>>> wrote:
>>>>
>>>>> Hello,
>>>>> I would like to use Weewx to process the waeather data from my 
>>>>> personal weather station.
>>>>> This station (Bresser) is not supported by Weewx, but the data is 
>>>>> transferred to Wunderground (table).
>>>>> So, I am wondering whether it is possible to get the data from there, 
>>>>> process it and send it to another form of website/app?
>>>>> Thanks in advance,
>>>>> Ivan
>>>>>
>>>>> -- 
>>>>> 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...@googlegroups.com.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/weewx-user/1ed76a9a-0b2a-4c74-b023-c70b080e193c%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/weewx-user/1ed76a9a-0b2a-4c74-b023-c70b080e193c%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>> -- 
>>>> 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...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEBRM_N_83SCjakky%2BEf8fr-SLU%3DVAnXGxO0oxWTHtZpLw%40mail.gmail.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEBRM_N_83SCjakky%2BEf8fr-SLU%3DVAnXGxO0oxWTHtZpLw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/b64dd53c-def0-4378-8067-5b7ba24e93d7%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/b64dd53c-def0-4378-8067-5b7ba24e93d7%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0b5d1edc-344f-40ca-9328-2795e9b43c6d%40googlegroups.com.