[weewx-user] Redundant and self synchronizing database between two systems - which approach (MQTT ?) ?

[Markus]

Hello,

i am building up a Raspberry Pi based home made weather station at my 
garden house.
The data collecting script will be self written (more to this script here: 
https://www.wxforum.net/index.php?topic=22428.0 )
For a stable system the RasPi will run with a industrial grade microSD 
(Transcend High Endurance) and a UPS.

The weather data will be collected locally on the RasPi but should also be 
stored on my Linux server - both are connected via LAN.
The Linux server is also responsible for visualizing the weather data.

When the Linux server or the RasPi were down, they should synchronize to 
the latest available data automatically when they up again.

My question:
Which approach may be a good solution (and easy maintainable) for this 
requirements?
May be a mqtt with two servers be used?
I am happy for every proposal.

Regards
Markus


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Original Vantage Pro, connected via serial-ethernet converter?

['loonsailor' via weewx-user]

I forgot to mention - running under Ubunto 17.10.

On Tuesday, December 26, 2017 at 9:57:39 PM UTC-8, loonsailor wrote:
>
> My old computer, on which I've been running view for many years, has died. 
>  I'd like to switch over to weewx, but I'm not sure if it will support my 
> hardware.  I'm running an original vantage pro.  The console has a serial 
> port, which I've connected to my LAN with a Lantronix serial-ethernet 
> interface, an older version of this 
>  one.  I can't move 
> the console near my computer, because the wireless won't handle the walls 
> and the distance.  So, I have uncertainty on two levels - the old Vantage 
> Pro (not the newer + version), and the connection via a serial-ethernet 
> interface.  Can I make this work, or do I need to rethink the whole thing?
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Original Vantage Pro, connected via serial-ethernet converter?

['loonsailor' via weewx-user]

My old computer, on which I've been running view for many years, has died. 
 I'd like to switch over to weewx, but I'm not sure if it will support my 
hardware.  I'm running an original vantage pro.  The console has a serial 
port, which I've connected to my LAN with a Lantronix serial-ethernet 
interface, an older version of this 
 one.  I can't move 
the console near my computer, because the wireless won't handle the walls 
and the distance.  So, I have uncertainty on two levels - the old Vantage 
Pro (not the newer + version), and the connection via a serial-ethernet 
interface.  Can I make this work, or do I need to rethink the whole thing?

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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Some possible helps for anyone running an old Davis Vantage Pro2 console

[Doug Bo]

I'm running an older Vantage Pro2 console, vintage 2007, firmware 1.90  
(can't update firmware due to console hardware changes)
My WeatherlinkIP is running current firmware but console seems to be very 
slow to respond.  I disabled the upload to weatherlink.

I had to tweak the conf file to get it to run more than 24 hours.  The 
parameter adjustments below are based on threads I found in this forum.  
Hopefully my discoveries will help someone.  Although I doubt anyone (other 
than me) is running old consoles.  LOL

Any other tips are appreciated.  Thanks.

I'm currently discussing my options with Davis on updating my consoles.  
Maybe newer hardware.  :)

Doug B.



loop_on_init = True

  
# TCP send delay (when using the WeatherLinkIP):
tcp_send_delay = 0.5



*# experimentcommand_delay = 1.0*
# The id of your ISS station (usually 1). If you use a wind meter 
connected
# to a anemometer transmitter kit, use its id
iss_id = 2

# How long to wait for a response from the station before giving up (in
# seconds; must be greater than 2)
# timeout = 4

*timeout = 8*
# How long to wait before trying again (in seconds)
# wait_before_retry = 1.2

*wait_before_retry = 3.5*
# How many times to try before giving up:
max_tries = 4

# Vantage model Type: 1 = Vantage Pro; 2 = Vantage Pro2
model_type = 2

# The driver to use:
driver = weewx.drivers.vantage

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Best way to add WebDAV to weewx?

[Doug Bo]

Uploading files to a remote web server using FTP is not working due to 
multiple levels of NAT on my local network (wireless ISP) & my web server 
provider setup.  My web server provider prefers WebDAV over FTP when 
uploading files from a device buried behind multiple levels of NAT.

Currently I'm using cadaver in a cron job to upload the images & files 
generated by the StandardReport.

It appears that Python has webdavclient which should do the same job as 
cadaver.

I would like to remove the cron job and use either cadaver or webdavclient 
in place of FTP to upload the files & images created by StandardReport.  
How should I proceed?  Feature request?  Change code?

I'm running weewx 3.8.0 on Raspberry Pi 3 using Vantage Pro2 hardware.

Thanks,
Doug B.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weewx generating reports two days head

[Mike Dame]

So it will not restart, I copied back the backup database. I tried with and
without the sql drop, now the database will not start... :(

pi@raspberrypi:~ $ sudo cp -p /var/tmp/weewx.sdb.backup
/var/lib/weewx/weewx.sdb

pi@raspberrypi:~ $ sudo sqlite3 /var/lib/weewx/weewx.sdb
SQLite version 3.8.7.1 2014-10-29 13:59:56
Enter ".help" for usage hints.
sqlite>
sqlite> DELETE FROM archive WHERE dateTime > 1514181600;
sqlite> .quit

pi@raspberrypi:~ $ sudo wee_database --drop-daily
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database
'archive_sqlite'
Proceeding will delete all your daily summaries from database 'weewx.sdb'
Are you sure you want to proceed (y/n)? y
Dropping daily summary tables from 'weewx.sdb' ...
Daily summary tables dropped from database 'weewx.sdb' in 2.58 seconds

pi@raspberrypi:~ $ sudo wee_database --rebuild-daily
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database
'archive_sqlite'
All daily summaries will be rebuilt.
Proceed (y/n)? y
Rebuilding daily summaries in database 'weewx.sdb' ...
Records processed: 738000; Last date: 2017-12-21 11:30:00 CST (1513877400)
Processed 738994 records to rebuild 2585 day summaries in 698.76
seconds
Rebuild of daily summaries in database 'weewx.sdb' complete

pi@raspberrypi:~ $ sudo systemctl start weewx;tail -f /var/log/messages
Dec 26 21:04:06 raspberrypi wee_database[18640]: manager: Processed 738994
records to backfill 2585 day summaries in 698.48 seconds
Dec 26 21:04:06 raspberrypi wee_database[18640]: Rebuild of daily summaries
in database 'weewx.sdb' complete
Dec 26 21:13:36 raspberrypi wee_database[18824]: manager: Dropping daily
summary tables from 'weewx.sdb' ...
Dec 26 21:13:38 raspberrypi wee_database[18824]: manager: Dropped daily
summary tables from database 'weewx.sdb'
Dec 26 21:13:45 raspberrypi wee_database[18832]: All daily summaries will
be rebuilt.
Dec 26 21:13:47 raspberrypi wee_database[18832]: manager: Created daily
summary tables
Dec 26 21:13:47 raspberrypi wee_database[18832]: Rebuilding daily summaries
in database 'weewx.sdb' ...
Dec 26 21:13:47 raspberrypi wee_database[18832]: manager: Starting backfill
of daily summaries
Dec 26 21:25:21 raspberrypi wee_database[18832]: manager: Processed 739683
records to backfill 2588 day summaries in 694.00 seconds
Dec 26 21:25:22 raspberrypi wee_database[18832]: Rebuild of daily summaries
in database 'weewx.sdb' complete
^C
pi@raspberrypi:~ $ ps -ef | grep weewx
pi   18967  1332  0 21:26 pts/000:00:00 grep --color=auto weewx
pi@raspberrypi:~ $


pi@raspberrypi:~ $ sudo systemctl -l status weewx
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx)
   Active: active (exited) since Tue 2017-12-26 09:11:01 CST; 11h ago
  Process: 12968 ExecStop=/etc/init.d/weewx stop (code=exited,
status=0/SUCCESS)
  Process: 13199 ExecStart=/etc/init.d/weewx start (code=exited,
status=0/SUCCESS)

Dec 26 09:11:02 raspberrypi weewx[13213]: File
"/usr/share/weewx/weewx/engine.py", line 604, in setup_database
Dec 26 09:11:02 raspberrypi weewx[13213]:   _nrecs, _ndays =
dbmanager.backfill_day_summary() # @UnusedVariable
Dec 26 09:11:02 raspberrypi weewx[13213]: File
"/usr/share/weewx/weewx/manager.py", line 1428, in backfill_day_summary
Dec 26 09:11:02 raspberrypi weewx[13213]: 
timestamp_to_string(lastRecord)))
Dec 26 09:11:02 raspberrypi weewx[13213]:   ViolatedPrecondition:
lastUpdate(2017-12-26 08:55:00 CST (1514300100)) > lastRecord(2017-12-25
00:00:00 CST (1514181600))
Dec 26 09:11:02 raspberrypi weewx[13213]:   Exiting.
Dec 26 20:44:30 raspberrypi systemd[1]: Started LSB: weewx weather system.
Dec 26 20:45:47 raspberrypi systemd[1]: Started LSB: weewx weather system.
Dec 26 20:47:02 raspberrypi systemd[1]: Started LSB: weewx weather system.
Dec 26 21:05:26 raspberrypi systemd[1]: Started LSB: weewx weather system.
pi@raspberrypi:~ $



On Tue, Dec 26, 2017 at 1:49 PM, gjr80  wrote:

> Hi,
>
> Try dropping the daily summaries before rebuilding:
>
> sudo wee_database --drop-daily
> sudo wee_database --rebuild-daily
>
> Since 3.7.0 (I think) you can usually, but not always, rebuild without
> first dropping. I think this is one of those exceptions.
>
> Gary
>
> --
> 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/RezDiRbbCks/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit 

Re: [weewx-user] Re: Windchill generated wrong.

[Thomas Keffer]

​That suggests a bug in the driver.

Looking through the code and comparing it to Bashewa's reverse engineered
protocol , it looks like the
driver might be decoding the wrong byte.​

I don't have access to an WMR200, so I'll have to ask the original author.

-tk


On Tue, Dec 26, 2017 at 1:50 PM, Mark Jenks  wrote:

> 20 miles NW from Green Bay, WI.  Frozen Tundra!
>
>
> On Tuesday, December 26, 2017 at 3:21:28 PM UTC-6, vince wrote:
>>
>> On Monday, December 25, 2017 at 10:24:36 PM UTC-8, Mark Jenks wrote:
>>>
>>> Yes, I live somewhere where the air hurts my face..  But that being
>>> said, when windchill hits -25, it calculates it wrong.
>>>
>>> Outside Temperature -9.4°F
>>> Wind Chill -24.6°F
>>> Heat Index -9.4°F
>>> Dewpoint -34.2°F
>>> Humidity 27%
>>>
>>>
>> ok - I have to ask.where are 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Windchill generated wrong.

[Mark Jenks]

20 miles NW from Green Bay, WI.  Frozen Tundra!


On Tuesday, December 26, 2017 at 3:21:28 PM UTC-6, vince wrote:
>
> On Monday, December 25, 2017 at 10:24:36 PM UTC-8, Mark Jenks wrote:
>>
>> Yes, I live somewhere where the air hurts my face..  But that being said, 
>> when windchill hits -25, it calculates it wrong.
>>
>> Outside Temperature -9.4°F
>> Wind Chill -24.6°F
>> Heat Index -9.4°F
>> Dewpoint -34.2°F
>> Humidity 27%
>>
>>
> ok - I have to ask.where are 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Windchill generated wrong.

[vince]

On Monday, December 25, 2017 at 10:24:36 PM UTC-8, Mark Jenks wrote:
>
> Yes, I live somewhere where the air hurts my face..  But that being said, 
> when windchill hits -25, it calculates it wrong.
>
> Outside Temperature -9.4°F
> Wind Chill -24.6°F
> Heat Index -9.4°F
> Dewpoint -34.2°F
> Humidity 27%
>
>
ok - I have to ask.where are 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Windchill generated wrong.

[Mark Jenks]

Correct.


On Tuesday, December 26, 2017 at 1:44:41 PM UTC-6, gjr80 wrote:
>
> So when weeWX was displaying the nonsense windchill at the same time the 
> console was displaying the correct windchill?
>
> Gary
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx generating reports two days head

[gjr80]

Hi,

Try dropping the daily summaries before rebuilding:

sudo wee_database --drop-daily
sudo wee_database --rebuild-daily

Since 3.7.0 (I think) you can usually, but not always, rebuild without first 
dropping. I think this is one of those exceptions.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Windchill generated wrong.

[gjr80]

So when weeWX was displaying the nonsense windchill at the same time the 
console was displaying the correct windchill?

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Oregon scientific WMR300 issues

[Alberto Sánchez]

Thanks!!! I will test as soon as possible and I will inform here.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Oregon scientific WMR300 issues

[mwall]

On Tuesday, December 26, 2017 at 8:07:51 AM UTC-5, Alberto Sánchez wrote:
>
> I am testing new mwall driver 0.19RC1 (Thanks a lot mwall). But I have 
> problems with it:
>
>>
>>
fixed at commit e43e033 

it looks like we must ignore usb non-errors and usb timeouts for all reads 
and writes

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx generating reports two days head

[Mike Dame]

Got an error with trying to rebuild database.

pi@raspberrypi:~ $ sudo wee_database --rebuild-daily --from 2017-12-25
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_sqlite'
Daily summaries from 2017-12-25 through the end will be rebuilt.
Proceed (y/n)? y
Rebuilding daily summaries in database 'weewx.sdb' ...
Traceback (most recent call last):
  File "/usr/bin/wee_database", line 793, in 
main()
  File "/usr/bin/wee_database", line 153, in main
rebuildDaily(config_dict, db_binding, options)
  File "/usr/bin/wee_database", line 262, in rebuildDaily
trans_days=20)
  File "/usr/share/weewx/weewx/manager.py", line 1428, in 
backfill_day_summary
timestamp_to_string(lastRecord)))
weewx.ViolatedPrecondition: lastUpdate(2017-12-26 08:55:00 CST 
(1514300100)) > lastRecord(2017-12-25 00:00:00 CST (1514181600))


On Monday, December 25, 2017 at 8:53:02 PM UTC-6, Mike Dame wrote:
>
> Last night I rebooted my raspberry running that is running "weewx 
> v3.8.0".  And the report are dated two days ahead, so today is the 25th of 
> Dec, reported that the temps are from 27th of Dec. I have double checked 
> the system clock is correct on the raspberry and the time on the "WMR200a" 
> is set correct, within minute of the raspberry.  notice the date stamp on 
> the database check below.
>
> The only error that I can see in the messages log is "wmr200: MainThread: 
> W Clock time unsynchronized", I did not really get any hits that would give 
> me a hint if this is the error or not.
>
> pi@raspberrypi:~ $ sudo  wee_database --check
> Using configuration file /etc/weewx/weewx.conf
> Using database binding 'wx_binding', which is bound to database 
> 'archive_sqlite'
> Checking daily summary tables version...
> Daily summary tables are at version 1.0
> Recommend running --update to recalculate interval weightings.
> Daily summary tables version check completed in 0.02 seconds.
> Preparing Null String Check, this may take awhile...
> *Checking record: 739537; Timestamp: 2017-12-27 04:31:37 CST (1514370697)*
> No null strings found.
> Completed Null String Check in 70.77 seconds.
> pi@raspberrypi:~ $ date
> *Mon 25 Dec 20:42:46 CST 2017*
> pi@raspberrypi:~ $ 
>
> Anybody got some ideas?
>
> Regards,
> Mike
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Windchill generated wrong.

[Mark Jenks]

Yes, software seems to be working fine now.

Outside Temperature -9.6°F
Wind Chill -26.9°F
Heat Index -9.6°F
Dewpoint -34.3°F
Humidity 27%
Barometer 30.599 inHg
Barometer Trend (3 hours) 0.057 inHg
Wind 9 mph from 270° (W)
Rain Rate 0.00 in/hr
Inside Temperature 62.1°F
Inside Humidity 25%


On Tuesday, December 26, 2017 at 7:45:12 AM UTC-6, Mark Jenks wrote:
>
> Yes, windchill is correct on the station.  Says -30F right now.
>
> I'm going to try switching it to software to see if it fixes it for now.
>
> I have a feeling that the driver isn't grabbing it correctly.
>
> -Mark
>
> On Tuesday, December 26, 2017 at 3:54:03 AM UTC-6, gjr80 wrote:
>>
>> Hmm, accoding to the Hardware Guide (
>> http://weewx.com/docs/hardware.htm#wmr200_notes) the WMR200 calculates 
>> and provides windchill to weeWX. So it's likely either the WMR200 driver is 
>> decoding windchill incorrectly or the station is outputting nonsense 
>> windchill now and then. Does windchill always display correctly on the 
>> station? Probably need a WMR200 expert I suspect.
>>
>> You could force weeWX to calculate windchill by setting 
>> windchill=software under StdWXCalculate in weewx.conf but this will only 
>> give you a windchill value when you have non-None values for outTemp AND 
>> windSpeed in the packet/record. Arguably this is only masking the issue 
>> rather than fixing it.
>>
>> Gary
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Windchill generated wrong.

[Mark Jenks]

Yes, windchill is correct on the station.  Says -30F right now.

I'm going to try switching it to software to see if it fixes it for now.

I have a feeling that the driver isn't grabbing it correctly.

-Mark

On Tuesday, December 26, 2017 at 3:54:03 AM UTC-6, gjr80 wrote:
>
> Hmm, accoding to the Hardware Guide (
> http://weewx.com/docs/hardware.htm#wmr200_notes) the WMR200 calculates 
> and provides windchill to weeWX. So it's likely either the WMR200 driver is 
> decoding windchill incorrectly or the station is outputting nonsense 
> windchill now and then. Does windchill always display correctly on the 
> station? Probably need a WMR200 expert I suspect.
>
> You could force weeWX to calculate windchill by setting windchill=software 
> under StdWXCalculate in weewx.conf but this will only give you a windchill 
> value when you have non-None values for outTemp AND windSpeed in the 
> packet/record. Arguably this is only masking the issue rather than fixing 
> it.
>
> Gary
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] wh1080 tendency

[Daniel Jerez]

---Detectar idiomaAfrikáansAlbanésAlemánAmáricoÁrabeArmenio
AzerbaiyanoBengalíBielorrusoBirmanoBosnioBúlgaroCanarésCatalánCebuanoChecoChino 
(Simplificado)Chino (Tradicional)CingalésCoreanoCorsoCriollo haitianoCroata
DanésEslovacoEslovenoEspañolEsperantoEstonioEuskeraFinésFrancésFrisón 
occidentalGaélico escocésGalésGallegoGeorgianoGriegoGuyaratíHausaHawaiano
HebreoHindiHmongHúngaroIgboIndonesioInglésIrlandésIslandésItalianoJaponés
JavanésJemerKazajoKirguísKurdoLaoLatínLetónLituanoLuxemburguésMacedonio
MalayalamMalayoMalgacheMaltésMaoríMaratíMongolNeerlandésNepalíNoruegoNyanja
PanyabíPastúnPersaPolacoPortuguésRumanoRusoSamoanoSerbioSesotho meridional
ShonaSindhiSomalíSuajiliSuecoSundanésTagaloTailandésTamilTayikoTeluguTurco
UcranianoUrduUzbekoVietnamitaXhosaYidisYorubaZulúEspañol

hello, I have a wh-1080 weather station connected to a raspberry and weewx by 
usb. In my panel of the station, is the drawing of tendency that is the one 
that has the forecast for the next hours that calculates the station, can I 
read that parameter from weewx? since I am using the WU forecast and it is not 
as accurate as the one my own station gives me. 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weewx generating reports two days head

[Thomas Keffer]

Somehow the clock on your weather station or your RPi got a couple days
ahead of reality, perhaps when you rebooted. Do you have a real-time clock?
To figure out what happened you would have to go through the historical RPi
system logs from back when you rebooted.

In any case, no matter what the cause, the fix is the same: delete the "in
the future" database records and rebuild the daily summaries. Here's the
steps (NOT TESTED):

1. Stop weewx

2. Make a backup copy of your database.

sudo cp /var/lib/weewx/weewx.sdb /var/tmp/weewx.sdb.backup


3. Figure out what the last good record is in your database. Let's say it
was 0100 on 25-Dec-2017 CST (UTC-6). That would be 1514181600 unix epoch
time. This website  can help.

4. Make sure the tool sqlite3 is on your system

apt-get install sqlite3


5. Use it to delete the future records

sudo sqlite /var/lib/weewx/weewx.sdb
sqlite> DELETE FROM archive WHERE dateTime > 1514181600;
sqlite> .quit


6. Rebuild the daily summaries

sudo wee_database --rebuild-daily --from 2017-12-25


7. Restart weewx.

Let us know how it goes.

-tk


On Tue, Dec 26, 2017 at 1:01 PM, Mike Dame  wrote:

> I have attached two cycles, the log looks normal to me (but not an expert).
> Without doing a sql query to look at the database, it weekly temp graph
> looks like it is adding data on the correct date, but the current graph is
> plotting data that was dated wrong
>
> Mike
>
>
> On Monday, December 25, 2017 at 8:53:02 PM UTC-6, Mike Dame wrote:
>>
>> Last night I rebooted my raspberry running that is running "weewx
>> v3.8.0".  And the report are dated two days ahead, so today is the 25th of
>> Dec, reported that the temps are from 27th of Dec. I have double checked
>> the system clock is correct on the raspberry and the time on the "WMR200a"
>> is set correct, within minute of the raspberry.  notice the date stamp on
>> the database check below.
>>
>> The only error that I can see in the messages log is "wmr200: MainThread:
>> W Clock time unsynchronized", I did not really get any hits that would give
>> me a hint if this is the error or not.
>>
>> pi@raspberrypi:~ $ sudo  wee_database --check
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'wx_binding', which is bound to database
>> 'archive_sqlite'
>> Checking daily summary tables version...
>> Daily summary tables are at version 1.0
>> Recommend running --update to recalculate interval weightings.
>> Daily summary tables version check completed in 0.02 seconds.
>> Preparing Null String Check, this may take awhile...
>> *Checking record: 739537; Timestamp: 2017-12-27 04:31:37 CST (1514370697)*
>> No null strings found.
>> Completed Null String Check in 70.77 seconds.
>> pi@raspberrypi:~ $ date
>> *Mon 25 Dec 20:42:46 CST 2017*
>> pi@raspberrypi:~ $
>>
>> Anybody got some ideas?
>>
>> Regards,
>> Mike
>>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Oregon scientific WMR300 issues

[Alberto Sánchez]

If I restart weewx It works well. 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Oregon scientific WMR300 issues

[Alberto Sánchez]

I am testing new mwall driver 0.19RC1 (Thanks a lot mwall). But I have 
problems with it:

Dec 26 14:01:28 raspberrypi weewx[2333]: File 
"/usr/share/weewx/weewx/drivers/wmr300.py", line 1230, in get_history
Dec 26 14:01:28 raspberrypi weewx[2333]:   self.finish_history()
Dec 26 14:01:28 raspberrypi weewx[2333]: File 
"/usr/share/weewx/weewx/drivers/wmr300.py", line 1129, in finish_history
Dec 26 14:01:28 raspberrypi weewx[2333]:   self.station.write(cmd)
Dec 26 14:01:28 raspberrypi weewx[2333]: File 
"/usr/share/weewx/weewx/drivers/wmr300.py", line 1465, in write
Dec 26 14:01:28 raspberrypi weewx[2333]:   return self._write(buf)
Dec 26 14:01:28 raspberrypi weewx[2333]: File 
"/usr/share/weewx/weewx/drivers/wmr300.py", line 1458, in _write
Dec 26 14:01:28 raspberrypi weewx[2333]:   sent = 
self.handle.interruptWrite(Station.EP_OUT, buf, self.timeout)
Dec 26 14:01:28 raspberrypi weewx[2333]:   USBError: could not detach 
kernel driver from interface 0: No data available
Dec 26 14:01:28 raspberrypi weewx[2333]:   Exiting.



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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx generating reports two days head

[Mike Dame]

I have attached two cycles, the log looks normal to me (but not an expert).
Without doing a sql query to look at the database, it weekly temp graph 
looks like it is adding data on the correct date, but the current graph is 
plotting data that was dated wrong

Mike

On Monday, December 25, 2017 at 8:53:02 PM UTC-6, Mike Dame wrote:
>
> Last night I rebooted my raspberry running that is running "weewx 
> v3.8.0".  And the report are dated two days ahead, so today is the 25th of 
> Dec, reported that the temps are from 27th of Dec. I have double checked 
> the system clock is correct on the raspberry and the time on the "WMR200a" 
> is set correct, within minute of the raspberry.  notice the date stamp on 
> the database check below.
>
> The only error that I can see in the messages log is "wmr200: MainThread: 
> W Clock time unsynchronized", I did not really get any hits that would give 
> me a hint if this is the error or not.
>
> pi@raspberrypi:~ $ sudo  wee_database --check
> Using configuration file /etc/weewx/weewx.conf
> Using database binding 'wx_binding', which is bound to database 
> 'archive_sqlite'
> Checking daily summary tables version...
> Daily summary tables are at version 1.0
> Recommend running --update to recalculate interval weightings.
> Daily summary tables version check completed in 0.02 seconds.
> Preparing Null String Check, this may take awhile...
> *Checking record: 739537; Timestamp: 2017-12-27 04:31:37 CST (1514370697)*
> No null strings found.
> Completed Null String Check in 70.77 seconds.
> pi@raspberrypi:~ $ date
> *Mon 25 Dec 20:42:46 CST 2017*
> pi@raspberrypi:~ $ 
>
> Anybody got some ideas?
>
> Regards,
> Mike
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Dec 26 06:36:48 raspberrypi weewx[786]: wmr200: Thread-6: I USB polling device 
thread exiting
Dec 26 06:36:48 raspberrypi weewx[786]: wmr200: MainThread: I USB polling 
thread expired
Dec 26 06:36:48 raspberrypi weewx[786]: wmr200: Thread-5: I Watchdog received 
shutdown
Dec 26 06:36:48 raspberrypi weewx[786]: wmr200: Thread-5: I Watchdog thread 
exiting
Dec 26 06:36:48 raspberrypi weewx[786]: wmr200: MainThread: I Watchdog thread 
expired
Dec 26 06:36:48 raspberrypi weewx[786]: wmr200: MainThread: I Received packet 
count live:17712 archive:12 control:1299
Dec 26 06:36:48 raspberrypi weewx[786]: wmr200: MainThread: I Received 
bytes:999864 sent bytes:14352
Dec 26 06:36:48 raspberrypi weewx[786]: wmr200: MainThread: I Packet archive 
queue len:3 live queue len:0
Dec 26 06:36:48 raspberrypi weewx[786]: wmr200: MainThread: W Exiting with 
packets still in archive queue cnt:3
Dec 26 06:36:48 raspberrypi weewx[786]: wmr200: MainThread: I Driver gracefully 
exiting
Dec 26 06:36:48 raspberrypi weewx[786]: engine: Terminating weewx version 3.8.0
Dec 26 06:37:11 raspberrypi pi: == Weewx Stopped 
=
Dec 26 06:37:29 raspberrypi weewx[11805]: engine: Initializing weewx version 
3.8.0
Dec 26 06:37:29 raspberrypi weewx[11805]: engine: Using Python 2.7.9 (default, 
Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
Dec 26 06:37:29 raspberrypi weewx[11805]: engine: Platform 
Linux-4.9.35-v7+-armv7l-with-debian-8.0
Dec 26 06:37:29 raspberrypi weewx[11805]: engine: Locale is 'en_GB.UTF-8'
Dec 26 06:37:29 raspberrypi weewx[11805]: engine: pid file is /var/run/weewx.pid
Dec 26 06:37:29 raspberrypi weewx[11809]: engine: Using configuration file 
/etc/weewx/weewx.conf
Dec 26 06:37:29 raspberrypi weewx[11809]: engine: Loading station type WMR200 
(weewx.drivers.wmr200)
Dec 26 06:37:29 raspberrypi weewx[11809]: wmr200: MainThread: I driver version 
is 3.3.4
Dec 26 06:37:29 raspberrypi weewx[11809]: wmr200: MainThread: I sensor map is 
{'outTempBatteryStatus': 'battery_status_out', 'outHumidity': 'humidity_1', 
'rainRate': 'rain_rate', 'heatindex4': 'heatindex_5', 'rainTotal': 
'rain_total', 'rainBatteryStatus': 'battery_status_rain', 'heatindex6': 
'heatindex_7', 'extraTemp5': 'temperature_6', 'uvFault': 'uv_fault', 
'extraTemp2': 'temperature_3', 'heatindex': 'heatindex_1', 'extraTemp3': 
'temperature_4', 'rain24': 'rain_24', 'inHeatindex': 'heatindex_0', 'inTemp': 
'temperature_0', 'extraTemp1': 'temperature_2', 'hourRain': 'rain_hour', 
'windFault': 'wind_fault', 'windchill': 'windchill', 'clockUnsynchronized': 
'clock_unsynchronized', 'extraTemp7': 'temperature_8', 'rain': 'rain', 
'forecastIcon': 'forecast_icon', 'pressure': 'pressure', 'extraHumid4': 
'humidity_5', 'extraHumid5': 'humidity_6', 'extraHumid2': 'humidity_3', 
'extraHumid3': 'humidity_4', 'extraHumid1': 'humidity_2', 'extraTemp6': 
'temperature_7', 'heatindex5': 'heatindex_6', 'extraTemp4': 'temperature_5', 
'heatindex7': 'heatindex_8', 'altimeter': 'altimeter', 'heatindex1': 
'heatindex_2', 'heatindex2': 

Re: [weewx-user] Re: rapidfire work on usb conected acurite display and 5-1 sensor?

[Thomas Keffer]

Warren: Matthew has come up with a fix. If you want to give it a try, you
can replace your copy of the file bin/weewx/wxservices.py with this one

.

Alternatively, if you're using git, you can just do a pull and run it out
of the git directory.

-tk

On Mon, Dec 25, 2017 at 5:02 PM, Warren Severin  wrote:

>
>
> On Sunday, December 24, 2017 at 6:05:31 PM UTC-7, Tom Keffer wrote:
>>
>>
>> I've posted issue #291  to
>> track the problem.
>>
>> Thanks! I'll be most happy to assist with additional debug info or trying
> experimental or diagnostic code, etc. Let me know.
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Myacurite

[John Jensen]

Is there any support for the myacurite website in weewx?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Windchill generated wrong.

[gjr80]

Hmm, accoding to the Hardware Guide 
(http://weewx.com/docs/hardware.htm#wmr200_notes) the WMR200 calculates and 
provides windchill to weeWX. So it's likely either the WMR200 driver is 
decoding windchill incorrectly or the station is outputting nonsense windchill 
now and then. Does windchill always display correctly on the station? Probably 
need a WMR200 expert I suspect.

You could force weeWX to calculate windchill by setting windchill=software 
under StdWXCalculate in weewx.conf but this will only give you a windchill 
value when you have non-None values for outTemp AND windSpeed in the 
packet/record. Arguably this is only masking the issue rather than fixing it.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Windchill generated wrong.

[Andrew Milner]

It looks to me as though the windchill came in from the station wrong 
(3302.8 in the log you posted).  Have you tried setting windchill = 
software rather than the default of hardware in stdwxcalculate / 
calculations section of weewx.conf to see if it makes any difference??



On Tuesday, 26 December 2017 11:21:30 UTC+2, Mark Jenks wrote:

> WMR200.   Weewx 3.8.0
>
>
> On Tuesday, December 26, 2017 at 12:35:44 AM UTC-6, gjr80 wrote:
>>
>> Also, what type of station?
>>
>> Gary
>>
>
>
> Dec 26 03:19:28 server weewxd: LOOP:   2017-12-26 03:19:03 CST 
> (1514279943) altimeter: None, appTemp: None, barometer: None, cloudbase: 
> None, dateTime: 1514279943, dewpoint: None, heatindex: None, humidex: None, 
> inDewpoint: 26.4423483272, inHeatindex: None, inHumidity: 25, inTemp: 
> 62.78, maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, 
> windchill: None, windDir: None, windGustDir: None
> Dec 26 03:19:28 server weewxd: LOOP:   2017-12-26 03:19:13 CST 
> (1514279953) altimeter: None, appTemp: None, barometer: None, cloudbase: 
> None, dateTime: 1514279953, dewpoint: None, heatindex: None, humidex: None, 
> inDewpoint: 26.4423483272, inHeatindex: None, inHumidity: 25, inTemp: 
> 62.78, maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, 
> windchill: None, windDir: None, windGustDir: None
> Dec 26 03:19:28 server weewxd: LOOP:   2017-12-26 03:19:14 CST 
> (1514279954) altimeter: None, appTemp: None, barometer: None, cloudbase: 
> None, dateTime: 1514279954, dewpoint: None, heatindex: None, humidex: None, 
> inDewpoint: None, maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 
> 1, windchill: 3302.8, windDir: 270.0, windGust: 8.05299066698, windSpeed: 
> 7.60560229659
> Dec 26 03:19:28 server weewxd: LOOP:   2017-12-26 03:19:23 CST 
> (1514279963) altimeter: None, appTemp: None, barometer: None, cloudbase: 
> None, dateTime: 1514279963, dewpoint: None, heatindex: None, humidex: None, 
> inDewpoint: 26.4423483272, inHeatindex: None, inHumidity: 25, inTemp: 
> 62.78, maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, 
> windchill: None, windDir: None, windGustDir: None
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Disabling Weewx Autostart

[Gary Roderick]

Hi,

*sudo rm /etc/init.d/weewx *

should what you want.

Gary

On Tue, 26 Dec 2017 at 19:12, Phil Green  wrote:

> Hi,
> I have just been updating my Pi hardware from a Pi2 to Pi3.
> I use to use a hardware RTC module to set the clock time on boot.
> However the new Pi3 case I have no longer suits the RTC module.
> Because Weewx is set to autostart and the clock is set using the fake
> clock method and is incorrect until the NTP service sets it, Weewx doesn't
> run properly due to incorrect time.  I have to stop the service on boot
> manually and restart manually once the time has been set via internet NTP
> service.
> My question is how do I disable the auto starting of Weewx, I presume then
> I can manually start and stop Weewx in the usual way using:-
>
> *sudo /etc/init.d/weewx start*
>
> *sudo /etc/init.d/weewx stop*
>
>
> I installed Weewx using the apt-get method and using the current version
> of Jessie if this affects the solution.
> I look forward to getting advice.
> Regards
> Phil.
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-- 

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] trouble getting a calculated max solar radiation written in archive table

[gjr80]

Good that fixed the problem. Granted the requirement for pyephem is not as 
clearly spelt out as it should, probably because pyephem was first used for 
planetary/Sun/star rise/set/transit calcs and maxSolarRad was added much later. 
I'll make a note to add a couple of lines to the docs. Thanks.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Windchill generated wrong.

[Mark Jenks]

WMR200.   Weewx 3.8.0


On Tuesday, December 26, 2017 at 12:35:44 AM UTC-6, gjr80 wrote:
>
> Also, what type of station?
>
> Gary
>


Dec 26 03:19:28 server weewxd: LOOP:   2017-12-26 03:19:03 CST (1514279943) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514279943, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
26.4423483272, inHeatindex: None, inHumidity: 25, inTemp: 62.78, 
maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, windchill: 
None, windDir: None, windGustDir: None
Dec 26 03:19:28 server weewxd: LOOP:   2017-12-26 03:19:13 CST (1514279953) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514279953, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
26.4423483272, inHeatindex: None, inHumidity: 25, inTemp: 62.78, 
maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, windchill: 
None, windDir: None, windGustDir: None
Dec 26 03:19:28 server weewxd: LOOP:   2017-12-26 03:19:14 CST (1514279954) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514279954, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
None, maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, 
windchill: 3302.8, windDir: 270.0, windGust: 8.05299066698, windSpeed: 
7.60560229659
Dec 26 03:19:28 server weewxd: LOOP:   2017-12-26 03:19:23 CST (1514279963) 
altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 
1514279963, dewpoint: None, heatindex: None, humidex: None, inDewpoint: 
26.4423483272, inHeatindex: None, inHumidity: 25, inTemp: 62.78, 
maxSolarRad: None, pressure: None, rainRate: 0, usUnits: 1, windchill: 
None, windDir: None, windGustDir: None
 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] trouble getting a calculated max solar radiation written in archive table

[Tom Van Dyck]

Your quick stab in the dark did the trick! Thanks! :-)

But its still guesswork if you don't know this. The docs (in the 
StdWXCalculate section) don't state you need this library if you add 
maxSolarRad calculation + the application doesn't crash if the library is 
missing.

Op maandag 25 december 2017 22:23:20 UTC+1 schreef gjr80:
>
> Pardon my typo, obviously 'macSolarRad' should be 'maxSolarRad'
>
> Gary
>
> On Tue, 26 Dec 2017 at 08:06, gjr80  
> wrote:
>
>> Hi,
>>
>> First off, a quick stab in the dark, have you installed pyephem(
>> http://weewx.com/docs/setup.htm)? Pyephem is required to calculate 
>> maxSolarRad otherwise it will always be None/null.
>>
>> No reason why calculated values can't be added, as long as (1) the 
>> calculated field actually appears in the weeWX produced archive record and 
>> (2) there is a field of that name in the archive. Might be worth checking 
>> what is in your archive records by running weeWX directly (
>> http://www.weewx.com/docs/usersguide.htm#Running_directly) and looking 
>> at the lines starting with REC (will appear once every archive period). Is 
>> there a macSolarRad field and does it have a value?
>>
>> As for wee_database, sure it is very simple to add a field using tools 
>> like myphpadmin, but it is equally easy to screw things right up. 
>> Wee_database helps avoid such issues.
>>
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
>
> Gary
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Disabling Weewx Autostart

[Phil Green]

Hi,
I have just been updating my Pi hardware from a Pi2 to Pi3.
I use to use a hardware RTC module to set the clock time on boot. 
However the new Pi3 case I have no longer suits the RTC module.
Because Weewx is set to autostart and the clock is set using the fake clock 
method and is incorrect until the NTP service sets it, Weewx doesn't run 
properly due to incorrect time.  I have to stop the service on boot 
manually and restart manually once the time has been set via internet NTP 
service.
My question is how do I disable the auto starting of Weewx, I presume then 
I can manually start and stop Weewx in the usual way using:-

*sudo /etc/init.d/weewx start*

*sudo /etc/init.d/weewx stop*


I installed Weewx using the apt-get method and using the current version of 
Jessie if this affects the solution. 
I look forward to getting advice.
Regards
Phil.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.