Re: [weewx-user] Re: steelseries-gauge dont works on path ../weewx/skins/seasons WHY ?

[Graham Eddy]

symlinks might be more manageable

> On 13 Dec 2020, at 10:32 am, gjr80  wrote:
> 
> The trick in your case, since you are using one copy of gauges.js to support 
> the Seasons skin and ss skin, will be to add path info that works for both 
> your Seasons and ss skins. You will need to find a suitable absolute path 
> that works for both,

-- 
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/7C0FC471-6F65-4FBC-AD41-F914256213E4%40gmail.com.

Re: [weewx-user] GW1000 - solar radiation data lost while switching from Interceptor to API driver

[Graham Eddy]

syslog shows you have mapped 'UV’ from ‘uv’ and ‘radiation’ from 
‘solar_radiation’.
my working config has ‘UV’ mapped from ‘uvi’ and ‘radiation’ from ‘uv'

> On 17 Dec 2020, at 10:41 am, 'Rainer Lang' via weewx-user 
>  wrote:
> 
> I was running Weewx with the GW1000 interceptor and everything ran smoothly. 
> After downloading and installing the GW1000 API driver v. 0.1.012b and 
> meticulously following the readme instructions, I got the system running - 
> with ONE issue - the solar radiation data had disappeared and would no longer 
> be displayed. 
> 
> (they are there and sent to Ecowitt.net, WU etc. and are captured by 
> CumulusMX and Meteobridge => it's not a GW1000 console issue, it's obviously 
> a weewx (configuration ?) issue. I have 4 GW1000 type consoles and switched 
> between them to make sure it's not due to the console [with weewxd]. 
> 
> Since midnight the solar radiation picture/graph has completely disappeared.
> So I'm wondering what went wrong here ...
> Anyone can advise ?
> attached the syslog of the driver switch time window and some debug=1 output 
> at the end, the weewx.conf, a screencopy of the missing or mutilated graph 
> and the output of weexd as screencopy and text.
> 
> -- 
> 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/712d3a95-4fd7-4bbc-9b07-62477f1b2774n%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/979F765D-AA53-4533-BEF7-245A3D4A714D%40gmail.com.

[weewx-user] [[Calculations]] on archive record not loop packet?

[Graham Eddy]

my reading of the 4.3.0 source is that [[Calculations]] calculates the 
specified xtypes on each loop packet. is there a simple way now, or is it in 
plan, to be able to have them calculated for archive records only?

i do not want to calculate AQI from averaged pollutant values except when the 
averages are updated, which for me is at the end of each archive interval. i 
have written a data service to call the xtypes each archive record, but i would 
prefer StdWXCalculate handled it for me with ‘= software’ declarations

-- 
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/D43D0E70-13A6-4B6B-905C-F7597C97DE0A%40gmail.com.

Re: [weewx-user] Has Anyone Reached out to Ecowitt about an API or Some other Connectivity with Weewx?

[Graham Eddy]

via wifi, see https://github.com/gjr80/weewx-gw1000 


> On 20 Dec 2020, at 12:37 am, ch...@chrismaness.com wrote:
> 
> an API for weewx to poll or receive broadcasts directly from their GW-1000?

-- 
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/D48DA951-E007-4AE8-AC1A-8962B52E88E6%40gmail.com.

Re: [weewx-user] [[Calculations]] on archive record not loop packet?

[Graham Eddy]

good idea. i'll code & submit that

On Tue, 22 Dec 2020, 11:06 am Tom Keffer,  wrote:

> Hi, Graham
>
> Seems like a reasonable thing to do but, no, there is no way at this
> point. Perhaps the [[Calculations]] section should be expanded to:
>
> [StdWXCalculate]
>   [[Calculations]]
> aqi = software, record
>
> That is, it takes an optional second positional parameter that can be one
> of 'loop', 'record', or 'both'. The default would be 'both'.
>
>
>
> On Fri, Dec 18, 2020 at 7:10 AM Graham Eddy  wrote:
>
>> my reading of the 4.3.0 source is that [[Calculations]] calculates the
>> specified xtypes on each loop packet. is there a simple way now, or is it
>> in plan, to be able to have them calculated for archive records only?
>>
>> i do not want to calculate AQI from averaged pollutant values except when
>> the averages are updated, which for me is at the end of each archive
>> interval. i have written a data service to call the xtypes each archive
>> record, but i would prefer StdWXCalculate handled it for me with ‘=
>> software’ declarations
>>
>> --
>> 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/D43D0E70-13A6-4B6B-905C-F7597C97DE0A%40gmail.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/CAPq0zEARNBu0cB18MDYiVc0101vw4W9PEcutpJ3ZFvGmYvt8GQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEARNBu0cB18MDYiVc0101vw4W9PEcutpJ3ZFvGmYvt8GQ%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-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAKwQt_ptTtJBJdHAdSZpL6ayy9OF23mcrORcS%3DdO965nq5NE%2Bg%40mail.gmail.com.

[weewx-user] 4.2.0 simulator - bug & fix for configuring list of observations

[Graham Eddy]

hello tom,
hopefully a simple fix that can make it into 4.3.0...

problem:
weewx 4.2.0 simulator crashes when i specify the list of observations to include

weewx.conf extract:
(note: ‘observations = ‘ line is one line. the line break is an artifact of 
copy&paste)
[GeSimulator]
# This section is for the weewx weather station simulator

# The time (in seconds) between LOOP packets.
loop_interval = 2.5

# The simulator mode can be either 'simulator' or 'generator'.
# Real-time simulator. Sleep between each LOOP packet.
mode = simulator
# Generator.  Emit LOOP packets as fast as possible (useful for testing).
#mode = generator

# The start time. Format is -mm-ddTHH:MM. If not specified, the default 
# is to use the present time.
#start = 2011-01-01T00:00

# list of variables for simulator to generate.
# note: if this is specified, only these will be produced
# remove PM2.5 and AQI variables
observations = 
inTemp,barometer,pressure,windSpeed,windDir,windGust,windGustDir,outHumidity,inHumidity,radiation,UV,rain,txBatteryStatus,windBatteryStatus,rainBatteryStatus,outTempBatteryStatus,inTempBatteryStatus,consBatteryVoltage,heatingVoltage,supplyVoltage,referenceVoltage,rxCheckPercent,altOutTemp,altInTemp,altPressure,altWindSpeed,altWindDir,altWindGust,altWindGustDir,altOutHumidity,altInHumidity,altRain,luminosity,solarEnergy,soilMoist1,soilMoist2,riverLevel,extraTemp1,wh40_batt,wh41_ch1_batt,wh41_ch2_batt,wh51_ch1_batt,wh51_ch2_batt,wh57_batt,ws80_batt

# The driver to use:
driver = user.gesimulator

log extract:
Dec 26 14:01:36 dizzy weewx-test[332] CRITICAL weewx.engine: File 
"/opt/weewx-4.2.0-test/bin/weewx/drivers/simulator.py", line 139, in __init__
Dec 26 14:01:36 dizzy weewx-test[332] CRITICAL weewx.engine:   
self.trim_observations(stn_dict)
Dec 26 14:01:36 dizzy weewx-test[332] CRITICAL weewx.engine: File 
"/opt/weewx-4.2.0-test/bin/weewx/drivers/simulator.py", line 144, in 
trim_observations
Dec 26 14:01:36 dizzy weewx-test[332] CRITICAL weewx.engine:   
desired = [x.strip() for x in stn_dict['observations'].split(',')]
Dec 26 14:01:36 dizzy weewx-test[332] CRITICAL weewx.engine:   
AttributeError: 'list' object has no attribute 'split'
Dec 26 14:01:36 dizzy weewx-test[332] CRITICAL __main__: Unable to load driver: 
'list' object has no attribute 'split'

rationale:
clearly the ‘observations =‘ line has been parsed as a list not as a string so 
split() fails

suggested fix:
weewx.drivers.simulator replace line 144 from
desired = [x.strip() for x in stn_dict['observations'].split(',')]
to
desired = stn_dict['observations']
if isinstance(desired, str):
# convert comma-separated string to list
desired = [x.strip() for x in desired.split(',')]

cheers

-- 
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/419112CF-BA4B-4B03-B7E3-E07B95F04DEA%40gmail.com.

Re: [weewx-user] Is it after sunset?

[Graham Eddy]

put a test into script to see if celestial time is in interval between now and 
now+5mins.
then either (a) generate the script, embedding the celestial time inside the 
script, or; (b) generate a file with the celestial timestamp, and your script 
reads the value from this generated file

> On 26 Dec 2020, at 5:10 pm, Robin  wrote:
> 
> I have a script that runs every five minutes, grabs an image from my webcam 
> and adds some text before it is uploaded to my website. I would like to test 
> if it is the first grab after sunset so that I can do some extra 'stuff' with 
> the image.
> 
> I am getting more and more frustrated by my lack of skill, knowledge and 
> diminishing brain power (not sure if it is advanced years or ouzo).
> 
> Please can somebody help.
> 
> 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/95f868c7-1080-4d27-8faf-9640ba580750n%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/9CE9CB37-675A-4C11-9599-D27D8487E8A1%40gmail.com.

Re: [weewx-user] [[Calculations]] on archive record not loop packet?

[Graham Eddy]

‘push request’ created (i think… github said something about deprecated) for 
‘loop’ and/or ‘archive’
i.e. aqi=software (defaults to both bindings) or aqi=software,loop or 
aqi=software,archive or aqi=software,loop,archive

> On 22 Dec 2020, at 11:47 am, Graham Eddy  wrote:
> 
> good idea. i'll code & submit that
> 
> On Tue, 22 Dec 2020, 11:06 am Tom Keffer,  <mailto:tkef...@gmail.com>> wrote:
> Hi, Graham
> 
> Seems like a reasonable thing to do but, no, there is no way at this point. 
> Perhaps the [[Calculations]] section should be expanded to:
> 
> [StdWXCalculate]
>   [[Calculations]]
> aqi = software, record
> 
> That is, it takes an optional second positional parameter that can be one of 
> 'loop', 'record', or 'both'. The default would be 'both'.
> 

-- 
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/8DA0EB9C-18B0-4F15-9384-6F3E0BA5C595%40gmail.com.

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[Graham Eddy]

sounds like some files might not be generating. are the timestamps on the 
generated files current? errors in log?

> On 26 Dec 2020, at 9:56 pm, Joe  wrote:
> 
> Looks like its all working and accessing the davis OK.
> 
> Only problem Im having now is the dates and times on the generated HTML are 
> all over the place.  Some of it is from a couple days ago, some of it is last 
> night and the mobile and smartphone HTML is not current.
> 
> On Friday, December 25, 2020 at 8:35:05 PM UTC-6 Joe wrote:
> Reimaged it finally and got the database conf file and such transferred over. 
>  
> 
> Now its catching up with all the data its been storing the past few days in 
> the Davis and publishing the records for last few days.
> 
> I guess it has been a few years since I have done this so its not too bad I 
> guess.
> 
> Hopefully I dont loose much data.  I'm still miffed why I lost 6mo of data 
> when I restored a backup from 6 months ago but I probably just dont 
> understand how the database is written is all.  
> 
> Such is life! I Do appreciate, as I always do the responses from the group.  
> 
> On Friday, December 25, 2020 at 7:31:09 PM UTC-6 vince wrote:
> You can get old versions of weewx .deb packages at 
> http://weewx.com/downloads/released_versions/ 
>  if you know what version you 
> used to use.   Check your weewx.conf file for the version identifier near the 
> top.You could alternately use the 'setup.py' method to install current 
> weewx on your ancient os, likely using python2 that your old os probably has 
> as its default.
> 
> But your preferred path is reflash to a current os and install current weewx 
> and then you're good for a long time.   You're talking 15 minutes of work to 
> do that.
> 
> I would suggest not bothering trying a dist-upgrade from debian-7 to 
> debian-10, as it's going to take forever and likely will not work anyway.   
> Just reimage clean to current RaspiOS which is based on current debian and 
> get caught up once and for all.
> 
> On Friday, December 25, 2020 at 4:53:02 PM UTC-8 Joe wrote:
> Really sucks I gotta completely re-image and re-set my whole PI board for 
> this.  I get used to set-forget .  I downloaded the files it needs. Database. 
> conf files etc as the online site says.
> 
> I was hoping this program would be more backward compatible with the RPI OS.
> 
> On Friday, December 25, 2020 at 1:06:21 PM UTC-6 vince wrote:
> Yup - your os is far too ancient for the libraries the weewx dpkg is built 
> against.   That version went end-of-life in May-2018.
> 
> I'd suggest you reimage with the current RaspiOS from  
> https://www.raspberrypi.org/software/operating-systems 
>  and then you'll be 
> up to date and supportable.  The weewx package works just fine in the current 
> os.
> 
> On Friday, December 25, 2020 at 2:35:04 AM UTC-8 Joe wrote:
> That worked.  7.8
> 
> 
> PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)"
> NAME="Raspbian GNU/Linux"
> VERSION_ID="7"
> VERSION="7 (wheezy)"
> ID=raspbian
> ID_LIKE=debian
> ANSI_COLOR="1;31"
> HOME_URL="http://www.raspbian.org/ "
> SUPPORT_URL="http://www.raspbian.org/RaspbianForums 
> "
> BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs 
> "
> root@raspberrypi:/etc# 
> 
> On Thursday, December 24, 2020 at 11:44:26 PM UTC-6 vince wrote:
> The current kernel version is 5.4.79 according to the release notes at 
> https://www.raspberrypi.org/software/operating-systems 
> 
> 
> My suspicion is that you are running an ancient os version that is too old 
> for the current packaged version of weewx.
> 
> Again, please run the following commands and provide the results.
> cat /etc/debian_version
> cat /etc/os-release
> 
> On Thursday, December 24, 2020 at 6:26:16 PM UTC-8 Joe wrote:
> Neither of those directories exist.
> 
> Its raspberrypi 3.18.7
> 
> On Thursday, December 24, 2020 at 9:53:49 AM UTC-6 vince wrote:
> On Thursday, December 24, 2020 at 4:33:57 AM UTC-8 Joe wrote:
> You mean to say running on the SD-CARD is bad idea?
> 
> Not bad, but not great if the card and power aren't quality.  But yes I 
> misstyped my original reply.
> 
> Re: your previous message containing " dpkg-deb: error: archive 
> '/var/cache/apt/archives/weewx_4.2.0-1_all.deb' contains not understood data 
> member control.tar.xz, giving up", that's an unusual message.
> 
> What version of raspi os are you running ?
> Can we see the contents of /etc/os-release and /etc/debian_version please ?
> 
> 
> 
> -- 
> 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 
> 

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[Graham Eddy]

to reduce the problem space, maybe ignore FTP for now - just look at the 
generated files locally. if timestamps are all over the place, either new ones 
are not being attempted (skin config error) or they are failing (template 
content failure)

watching tail, sometimes many screenfulls of log are generated at once and you 
can miss big chunks. i suggest using an editor to look at the log, line by 
line, to confirm (a) it has found the report definition; (b) it is enabled and 
will attempt generating all its files; (c) any errors; (d) completion of report 
generation

> On 26 Dec 2020, at 10:13 pm, Joe  wrote:
> 
> I''m watching with TAIL and I dont see any errors. It's making the images and 
> using FTP to send as needed but the dates and times on the published HTML is 
> all over. Some says 2am, some says last night at 830pm.
> 
> The FTP files date/time are mostly Dec 26 now, but some are 25th.
> 

-- 
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/CCD3CB62-0971-4CAD-9C4D-C81E3962232D%40gmail.com.

Re: [weewx-user] 4.2.0 simulator - bug & fix for configuring list of observations

[Graham Eddy]

i tried sending a pull request for [[calculations]] change - did that arrive?
i also then tried re-sending the simulator fix as a pull request but following 
the same procedure in github didn’t find a change to send - did that get 
gobbled into the other pull request somehow?
github is all strange to me...

> On 26 Dec 2020, at 11:42 pm, Tom Keffer  wrote:
> 
> Fixed in commit d9a4daa 
> 

-- 
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/948AA868-A869-437D-ADBE-4377F7BB6870%40gmail.com.

Re: [weewx-user] Re: gw1000 driver fail on wifi loss

[Graham Eddy]

suggestion: gw1000 install set loop_on_init to true by default. we will always 
have this kind of problem when the wifi (re)starts and weewx races ahead of it

> On 28 Dec 2020, at 8:12 am, gjr80  wrote:
> 
> That would explain the behaviour then, if loop_on_init is not set the loss of 
> connectivity with the station (for whatever reason) will cause WeeWX to exit 
> as it does with any other driver. I will make a point of pulling the network 
> on my GW1000 and confirming the driver and loop_on_init work as expected.

-- 
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/5BC374A7-1FB4-47B2-859B-B47A6F030715%40gmail.com.

Re: [weewx-user] Re: weewx-cmon doesn't read cpu_temp of Raspberri PI

[Graham Eddy]

an alternative to repurposing an existing data_type is to define an xtype (e.g. 
see https://github.com/g-eddy/weewx-vitalstats)

> On 28 Dec 2020, at 9:05 am, Kevin Chapman  wrote:
> 
> Thank you.  I will check it out.  
> 
> On Sun, Dec 27, 2020 at 6:00 AM Mike Revitt  > wrote:
> Sorry it has taken so long to respond to this, but I have just finished 
> documenting how I added the CPU Temperature to my website, this is all 
> documented here 
> 
>  
> https://www.cougar.eu.com/useful-guides/weewx-guides/rasberry-pi/read-cpu-temp.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/6B658B72-0127-4CA6-BC85-60A52CB0A9E7%40gmail.com.

Re: [weewx-user] weewx-cmon doesn't read cpu_temp of Raspberri PI

[Graham Eddy]

hmm, the ‘novelty’ i think is having an xtype calculated with values from 
outside weewx (eg cpu temperature), and the expense of the calculation is not 
really at issue - though normally they would be light-weight in case they are 
used often (eg barometer)

architecturally anything external is supposed to brought into weewx via a 
service and made available via weewx packet. (the *providing* of an xtype is 
now positioned as a service, but the xtypes themselves are not.)

okay, i’ll recast my vitalstats from xtypes_service to data_service and not 
bypass the packets...

> On 28 Dec 2020, at 11:40 am, Tom Keffer  wrote:
> 
> That's a novel use of xtypes, but I'm not sure it's always a good idea. In 
> this case, I think you'd be better off simply adding the type to the LOOP 
> packet or archive record. 
> 
> The intended purpose of xtypes is to calculate derived variables. It's 
> entirely possible it could be called many times during a reporting cycle, 
> depending on the template used. Something involving I/O could be very 
> expensive.
> 
> Having said that, xtypes also do database accesses, which can also be very 
> expensive, so my advice is inconsistent. So, not saying never do it, but 
> think it through.

-- 
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/29A71619-51B9-41B6-A4AB-14E54482FB56%40gmail.com.

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[Graham Eddy]

the .html timestamps are all current (assuming Dec 27 19:50 is current).
the .png timestamps are current until middle of the month images, then all old 
→ stopping part way through image generation.
some of the .png timestamps are very late in the 5 minute reporting period → 
maybe not finishing one report before starting the next.
you will need to look at (post here) the detailed log showing from before the 
start of report generation until past the end of completion of report 
generation to see if there is overlap.
or maybe the image generator is crashing part-way → ditto for need to see 
detailed logs

> On 28 Dec 2020, at 12:54 pm, Joe  wrote:
> 
> -rw-r--r-- 1 root root  7357 Dec 27 19:51  daywind.png
> -rw-r--r-- 1 root root  6148 Dec 27 19:51  daywindvec.png
> -rw-r--r-- 1 root root  1150 Dec 27 19:46  favicon.ico
> drwxr-xr-x 2 root root  4096 Dec 25 20:53  font
> -rw-r--r-- 1 root root  7315 Dec 27 19:51 '#FTP.last'
> -rw-r--r-- 1 root root 25919 Dec 27 19:50  index.html
> -rw-r--r-- 1 root root   564 Dec 27 19:46  mobile.css
> -rw-r--r-- 1 root root  2413 Dec 27 19:50  mobile.html
> -rw-r--r-- 1 root root  7606 Dec 25 20:48  monthbarometer.png
> -rw-r--r-- 1 root root 11985 Dec 27 19:50  month.html
> -rw-r--r-- 1 root root  7135 Dec 25 20:48  monthhumidity.png
> -rw-r--r-- 1 root root  6519 Dec 25 20:53  monthhum.png
> -rw-r--r-- 1 root root  8204 Dec 25 20:51  monthinside.png
> -rw-r--r-- 1 root root  5436 Dec 25 20:51  monthpond.png
> -rw-r--r-- 1 root root  7674 Dec 25 20:51  monthradiation.png
> -rw-r--r-- 1 root root  6976 Dec 25 20:48  monthrain.png
> -rw-r--r-- 1 root root  7324 Dec 25 20:51  monthrx.png
> -rw-r--r-- 1 root root  9045 Dec 25 20:48  monthtempchill.png
> -rw-r--r-- 1 root root  9280 Dec 25 20:48  monthtempdew.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/A6FC2CCE-2EE4-45B2-A27E-21CA535665D0%40gmail.com.

Re: [weewx-user] weewx-cmon doesn't read cpu_temp of Raspberri PI

[Graham Eddy]

i forgot to acknowledge the design consideration you raised that by calculating 
value once and storing it in the packet, unlike an xtype it is not 
re-calculated each time it is referenced

> On 28 Dec 2020, at 12:54 pm, Graham Eddy  wrote:
> 
> hmm, the ‘novelty’ i think is having an xtype calculated with values from 
> outside weewx (eg cpu temperature), and the expense of the calculation is not 
> really at issue - though normally they would be light-weight in case they are 
> used often (eg barometer)
> 
> architecturally anything external is supposed to brought into weewx via a 
> service and made available via weewx packet. (the *providing* of an xtype is 
> now positioned as a service, but the xtypes themselves are not.)
> 
> okay, i’ll recast my vitalstats from xtypes_service to data_service and not 
> bypass the packets...
> 
>> On 28 Dec 2020, at 11:40 am, Tom Keffer > <mailto:tkef...@gmail.com>> wrote:
>> 
>> That's a novel use of xtypes, but I'm not sure it's always a good idea. In 
>> this case, I think you'd be better off simply adding the type to the LOOP 
>> packet or archive record. 
>> 
>> The intended purpose of xtypes is to calculate derived variables. It's 
>> entirely possible it could be called many times during a reporting cycle, 
>> depending on the template used. Something involving I/O could be very 
>> expensive.
>> 
>> Having said that, xtypes also do database accesses, which can also be very 
>> expensive, so my advice is inconsistent. So, not saying never do it, but 
>> think it through.
> 

-- 
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/929A756F-DAE7-495C-9368-C85D2479E4F7%40gmail.com.

Re: [weewx-user] Independent weewx backup script

[Graham Eddy]

looking at https://sqlite.org/backup.html  
(extract below; my emphasis), the Backup API restarts the backup if an update 
(not a read) occurs during the backup → might silently never complete if backup 
takes longer than archive interval.
this could be dealt with by aborting the backup if it runs into end of archive 
interval → tell user to use some other backup method

did a couple of simple timing tests.
RPi 4B (SD card), weewx.sdb 104.5MB (381k records, dunno how many ‘pages'), no 
progress reporting:
  1 page at a time, default 25 msec delays: backup took 10.5 secs elapsed
  10 pages ditto: 7.9 secs elapsed
  100 pages ditto: 7.0 secs elapsed
  1000 pages ditto: 6.7 secs elapsed
conclusion: only seriously under-powered boxes would be unable to complete 
within typical 300 sec archive interval.
would be good if someone with such a box gave it a try


File and Database Connection Locking

During the 250 ms sleep in step 3 above, no read-lock is held on the database 
file and the mutex associated with pDb is not held. This allows other threads 
to use database connection  pDb and 
other connections to write to the underlying database file.

If another thread or process writes to the source database while this function 
is sleeping, then SQLite detects this and usually restarts the backup process 
when sqlite3_backup_step() is next called. There is one exception to this rule: 
If the source database is not an in-memory database, and the write is performed 
from within the same process as the backup operation and uses the same database 
handle (pDb), then the destination database (the one opened using connection 
pFile) is automatically updated along with the source. The backup process may 
then be continued after the sqlite3_sleep() call returns as if nothing had 
happened.

Whether or not the backup process is restarted as a result of writes to the 
source database mid-backup, the user can be sure that when the backup operation 
is completed the backup database contains a consistent and up-to-date snapshot 
of the original. However:

Writes to an in-memory source database, or writes to a file-based source 
database by an external process or thread using a database connection other 
than pDb are significantly more expensive than writes made to a file-based 
source database using pDb (as the entire backup operation must be restarted in 
the former two cases).
If the backup process is restarted frequently enough it may never run to 
completion and the backupDb() function may never return.




> On 11 Jan 2021, at 2:22 am, Tom Keffer  wrote:
> 
> If the backup takes long enough, it could interfere with writing a record to 
> the database. Eventually, the write will time out, causing weewxd to restart 
> from the top. It won't crash weewxd (that is, cause it to exit), nor corrupt 
> the database, but the record would be lost. 
> 
> That's the advantage of the incremental backup approach. The backup process 
> never holds a lock on the database for very long. Just a second or two.
> 
> BTW, the backup API 
>  is 
> now included in Python starting with V3.7. If you have a modern version of 
> Python, you don't have to write a C program to access the API.
> 
> I'm hoping to inspire someone to write a simple script that would run once a 
> day using the backup API.
> 
> -tk

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/E7A3C0BE-A408-464E-B43F-87E0DEEA6E0C%40gmail.com.

Re: [weewx-user] Independent weewx backup script

[Graham Eddy]

as a once-off i did nothing fancy, even hard-coding the number of pages and 
filename of database (trivial to fiddle), using shell time to measure elapsed 
time

import sqlite3

con = sqlite3.connect('/opt/weewx-4.2.0-test/archive/weewx.sdb')
bck = sqlite3.connect('backup.db')
with bck:
con.backup(bck, pages=1)
bck.close()
con.close()


> On 12 Jan 2021, at 4:24 am, vince  wrote:
> 
> On Monday, January 11, 2021 at 5:03:14 AM UTC-8 graha...@gmail.com wrote:
> conclusion: only seriously under-powered boxes would be unable to complete 
> within typical 300 sec archive interval.
> would be good if someone with such a box gave it a try
> 
> 
> If you can point us at the exact script you used, I can run it versus a test 
> db on a litany of seriousy under-powered boxes :-)
> 
> I have everything from a Seagate Dockstar (128MB RAM, laptop drive, always on 
> the edge of swapping) to pi using SD (model-B, zero, zeroW, pi3, pi3+, pi4)

-- 
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/1EBCD01F-B1C8-48AC-8D5A-DFAF8B0E20D5%40gmail.com.

Re: [weewx-user] Independent weewx backup script

[Graham Eddy]

i use ‘cp’. heck, i use ‘scp’…
i just make sure i work in the window from 2 mins after archive interval (long 
after my archive updates are completed) to a few secs before next archive 
interval.
could make BACKUP a new built-in report like FTP and RSYNC - unless want to 
make backup independent of weewx (e.g. scenario where restore is required 
because weewx is screwed up and stuffs up reports)

> On 12 Jan 2021, at 12:25 pm, Tom Keffer  wrote:
> 
> I actually think 'cp' is pretty safe. When WeeWX writes a record to the 
> database, it has to update the main archive, as well as many daily summaries. 
> To make sure this is all done atomicallly, it does it as one big transaction.
> 
> So, unless your 'cp' has the unfortunate timing of happening at the exact 
> moment when the transaction is being committed, you should be fine. I don't 
> know how big a time window that is. Maybe a couple hundred milliseconds?
> 

-- 
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/6045AACC-4BB1-4B6C-97A8-65F02F1DA0B0%40gmail.com.

[weewx-user] ecowitt ws80

[Graham Eddy]

the top of my ecowitt ws80 (the light sensor) has partly filled with 
condensation and stopped working. the rest of the ws80 is still working. is 
this ‘expected’ of an exposed ws80 (how else to get UV?) or is it a fault 
(demand a replacement)?

Graham Eddy

-- 
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/A823A248-BDBF-4DA2-ABF3-6FAB4EB33F0F%40gmail.com.

Re: [weewx-user] ecowitt ws80

[Graham Eddy]

summer here so 30 C during day (forecast 40 C in a few days). will be well 
above 0 C for 6 months…

i tipped unit on its side to drain condensation away from electrical innards. 
it is already sitting in the warmest place, out in the sun, a lot warmer than 
inside the house :-)  it stopped transmitting 48 hours ago. i’ll give it 
another day in the sun to see if it comes good

> On 21 Jan 2021, at 9:24 pm, Rainer Lang  wrote:
> 
> That's definitely not a feature.
> However, did you have below 0°C/32°F temperatures ?
> And do you have the inbuilt heater connected and powered ?
> 
> What works with others who had the phenomenon - and no heater activated - 
> was, taking it down, drying it inside/indoors and it worked again.
> Mine has its heater activated since recently and went through a minus 
> centigrade degree period followed by temperatures up to 10°C.
> and - no issues.
> Once activated by the inbuilt thermostat starts the heating when the 
> temperature drops below 0°C and keeps on running until the temperature goes 
> above 10°C/50°F.
> That seems to avoid not only the freezing but also the condensation water 
> inside.
> 
> I guess a replacement you can only ask for, if you have the heating 
> implemented (what quite some people don't seem to do, wanting to save on the 
> rather expensive power supply for it
> [a decicated power supply unit]).
> On 21.01.2021 03:59, Graham Eddy wrote:
>> the top of my ecowitt ws80 (the light sensor) has partly filled with 
>> condensation and stopped working. the rest of the ws80 is still working. is 
>> this ‘expected’ of an exposed ws80 (how else to get UV?) or is it a fault 
>> (demand a replacement)?
>> 
>> Graham Eddy
>> 
>> -- 
>> 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 
>> <mailto:weewx-user+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/A823A248-BDBF-4DA2-ABF3-6FAB4EB33F0F%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/A823A248-BDBF-4DA2-ABF3-6FAB4EB33F0F%40gmail.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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/18eef889-d0fa-3bf0-024f-e912de256998%40gmail.com
>  
> <https://groups.google.com/d/msgid/weewx-user/18eef889-d0fa-3bf0-024f-e912de256998%40gmail.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/71489C08-9405-4BF8-AC73-37FF11EF8FE4%40gmail.com.

Re: [weewx-user] Re: Weewx 4.3.0 and weewx multi on a fresh install

[Graham Eddy]

this sounds like the posting i made about 12 months ago where ‘stop’ does not 
work because the options on start-stop-daemon changed and you had to add an 
extra argument - without the new arg the ‘stop’ silently fails

> On 23 Jan 2021, at 9:02 am, vince  wrote:
> 
> Gary - I would agree that 'stop' does not work on a debian10 system but 
> 'start' works fine.   Same problem exists regardless of whether you use the 
> init.d file directly or if you use systemctl to let systemd control the 
> processes.  Start works.  Stop silently does nothing.  Nothing I could see in 
> the logs to indicate that it even tried to shut the processes down. 

-- 
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/C799F1FB-9DED-4EE9-9F90-9C6CDE1F7CE1%40gmail.com.

Re: [weewx-user] Weewx 4.3.0 and weewx multi on a fresh install

[Graham Eddy]

hmm just recalled that was only for weewx process owned by non-root user - 
presumably not relevant

> On 23 Jan 2021, at 1:18 pm, Graham Eddy  wrote:
> 
> this sounds like the posting i made about 12 months ago where ‘stop’ does not 
> work because the options on start-stop-daemon changed and you had to add an 
> extra argument - without the new arg the ‘stop’ silently fails
> 
>> On 23 Jan 2021, at 9:02 am, vince > <mailto:vinceska...@gmail.com>> wrote:
>> 
>> Gary - I would agree that 'stop' does not work on a debian10 system but 
>> 'start' works fine.   Same problem exists regardless of whether you use the 
>> init.d file directly or if you use systemctl to let systemd control the 
>> processes.  Start works.  Stop silently does nothing.  Nothing I could see 
>> in the logs to indicate that it even tried to shut the processes down. 
> 

-- 
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/EFDA3390-1B0B-49F5-B5D9-DECD95544A2F%40gmail.com.

[weewx-user] PM10 in ecowitt WH41 sensor?

[Graham Eddy]

fiddling with SDR trying to find some other sensor, i notice the following from 
rtl_433:
time  : 2021-01-24 00:02:08
model : Fineoffset-WH0290  ID: 4
2.5um Fine Particulate Matter: 8 ug/m3 10um Coarse Particulate 
Matter: 9 ug/m3
Integrity : CRC
which clearly says the ecowitt WH41 is transmitting PM10 value as well as PM2.5

i don't see the PM10 value appearing in WH41 ‘manual’, nor in gary’s gw1000 
driver. is there some way to extract this PM10 value other than via SDR?



-- 
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/75A1DDCC-3F98-4CD6-95BE-3C9A55A2E720%40gmail.com.

Re: [weewx-user] Unable to wake up Vantage console

[Graham Eddy]

you need to post your syslog from the time *before weewx first starts* until 
after its says EXITING.
pay particular attention to anything said about the serial port


> On 25 Jan 2021, at 4:56 pm, Txo  wrote:
> 
> Bonjour,
> I have recently buy a Vantage station with a meteo-pi 
> (https://wifilogger.net/meteopi.html) in a rasperry pi3. Weewx worked well 
> with Simulator but since I connected the station and chose the Vantage driver 
> I have nothing. Weewx don't start with this message :
> weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx; generated)
>Active: active (exited) since Sun 2021-01-24 18:24:35 CET; 12h ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 607 ExecStart=/etc/init.d/weewx start (code=exited, 
> status=0/SUCCESS)
> 
> janv. 24 18:25:02 raspledeuix python3[740]: weewx[740] CRITICAL weewx.engine: 
>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
> janv. 24 18:25:02 raspledeuix python3[740]: weewx[740] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in 
> __init__
> janv. 24 18:25:02 raspledeuix python3[740]: weewx[740] CRITICAL weewx.engine: 
>   self._setup()
> janv. 24 18:25:02 raspledeuix python3[740]: weewx[740] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1317, in 
> _setup
> janv. 24 18:25:02 raspledeuix python3[740]: weewx[740] CRITICAL weewx.engine: 
>   self.port.wakeup_console(max_tries=self.max_tries)
> janv. 24 18:25:02 raspledeuix python3[740]: weewx[740] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 118, in 
> wakeup_console
> janv. 24 18:25:02 raspledeuix python3[740]: weewx[740] CRITICAL weewx.engine: 
>   raise weewx.WakeupError("Unable to wake up Vantage console")
> janv. 24 18:25:02 raspledeuix python3[740]: weewx[740] CRITICAL weewx.engine: 
>   weewx.WakeupError: Unable to wake up Vantage console
> janv. 24 18:25:02 raspledeuix python3[740]: weewx[740] CRITICAL __main__: 
> Unable to load driver: Unable to wake up Vantage console
> janv. 24 18:25:02 raspledeuix python3[740]: weewx[740] CRITICAL __main__: 
>   Exiting...
> 
> I didn’t find anything to solve this problem, but I may have looked for it 
> wrong.
> As you can see my English is minimum  and don’t be offended by my problems of 
> understanding.
> 
> Merci.
> 
> -- 
> 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/97cd2a0b-61e3-464b-bc51-e0f007912088n%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/9BB9F1F7-12B4-415F-BC10-C63D9AAEB0CD%40gmail.com.

Re: [weewx-user] Unable to wake up Vantage console

[Graham Eddy]

sorry, i should also have said: set debug to 1 (near top of weewx.conf).
that will tell us more about the dialogue between vantage and weewx

> On 25 Jan 2021, at 9:05 pm, Txo  wrote:
> 
> Jan 25 10:54:31 raspledeuix systemd[1]: Starting LSB: weewx weather system...
> Jan 25 10:54:32 raspledeuix weewx[8154] INFO __main__: Initializing weewx 
> version 4.3.0
> Jan 25 10:54:32 raspledeuix weewx[8154] INFO __main__: Using Python 3.7.3 
> (default, Jul 25 2020, 13:03:44) #012[GCC 8.3.0]
> Jan 25 10:54:32 raspledeuix weewx[8154] INFO __main__: Platform 
> Linux-4.19.66-v7+-armv7l-with-debian-10.7
> Jan 25 10:54:32 raspledeuix weewx[8154] INFO __main__: Locale is 'fr_FR.UTF-8'
> Jan 25 10:54:32 raspledeuix weewx[8154] INFO __main__: PID file is 
> /var/run/weewx.pid
> Jan 25 10:54:32 raspledeuix weewx[8159] INFO __main__: Using configuration 
> file /etc/weewx/weewx.conf
> Jan 25 10:54:32 raspledeuix weewx[8159] INFO __main__: Debug is 0
> Jan 25 10:54:32 raspledeuix weewx[8159] INFO weewx.engine: Loading station 
> type Vantage (weewx.drivers.vantage)
> Jan 25 10:54:32 raspledeuix weewx[8141]: Starting weewx weather system: weewx.
> Jan 25 10:54:32 raspledeuix systemd[1]: Started LSB: weewx weather system.
> Jan 25 10:54:48 raspledeuix weewx[8159] ERROR weewx.drivers.vantage: Unable 
> to wake up console
> Jan 25 10:54:48 raspledeuix weewx[8159] ERROR weewx.engine: Import of driver 
> failed: Unable to wake up Vantage console ()
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL weewx.engine:   
> Traceback (most recent call last):
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL weewx.engine:   
> self.console = loader_function(config_dict, self)
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL weewx.engine:   
> return VantageService(engine, config_dict)
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL weewx.engine:   
> Vantage.__init__(self, **config_dict[DRIVER_NAME])
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL weewx.engine:   
> self._setup()
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1317, in _setup
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL weewx.engine:   
> self.port.wakeup_console(max_tries=self.max_tries)
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 118, in wakeup_console
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL weewx.engine:   
> raise weewx.WakeupError("Unable to wake up Vantage console")
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL weewx.engine:   
> weewx.WakeupError: Unable to wake up Vantage console
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL __main__: Unable to load 
> driver: Unable to wake up Vantage console
> Jan 25 10:54:48 raspledeuix weewx[8159] CRITICAL __main__:   
> Exiting...
> 
> $ sudo cat /var/log/syslog | grep serial
> Jan 25 08:54:11 raspledeuix kernel: [1.075547] uart-pl011 
> 3f201000.serial: cts_event_workaround enabled
> Jan 25 08:54:11 raspledeuix kernel: [1.083381] 3f201000.serial: ttyAMA0 
> at MMIO 0x3f201000 (irq = 81, base_baud = 0) is a PL011 rev2
> Jan 25 08:54:11 raspledeuix kernel: [1.093016] 3f215040.serial: ttyS0 at 
> MMIO 0x0 (irq = 53, base_baud = 5000) is a 16550
> 
> My Vantage section in weewx.conf :
>   
> [Vantage]
> # This section is for the Davis Vantage series of weather stations.
> 
> # Connection type: serial or ethernet 
> #  serial (the classic VantagePro)
> #  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
>type = serial
> 
> # If the connection type is serial, a port must be specified:
> #   Debian, Ubuntu, Redhat, Fedora, and SuSE:
> # /dev/ttyUSB0 is a common USB port name
> # /dev/ttyS0   is a common serial port name
> #   BSD:
> # /dev/cuaU0   is a common serial port name
>port = /dev/ttyS0
> 
> # If the connection type is ethernet, an IP Address/hostname is required:
> host = 1.2.3.4
> 
> ##
> # The rest of this section rarely needs any attention. 
> # You can safely leave it "as is."
> ##
> 
> #

Re: [weewx-user] Unable to wake up Vantage console

[Graham Eddy]

the syslog says it is successfully opening the serial device file, but not 
getting a sensible response (probably no response at all), in other words a 
communication problem between port and vantage pro

this forum contains many cases where people have had to check their serial port 
communicating with vantage pro.
there are many possible causes so i suggest searching the forum for the steps 
required

> On 26 Jan 2021, at 1:39 am, Txo  wrote:
> 
> Jan 25 15:29:39 raspledeuix weewx[18327] DEBUG weewx.drivers.vantage: Opened 
> up serial port /dev/ttyS0; baud 19200; timeout 4.00
> Jan 25 15:29:43 raspledeuix weewx[18327] DEBUG weewx.drivers.vantage: Retry 
> #0 failed
> Jan 25 15:29:47 raspledeuix weewx[18327] DEBUG weewx.drivers.vantage: Retry 
> #1 failed
> Jan 25 15:29:51 raspledeuix weewx[18327] DEBUG weewx.drivers.vantage: Retry 
> #2 failed
> Jan 25 15:29:55 raspledeuix weewx[18327] DEBUG weewx.drivers.vantage: Retry 
> #3 failed
> Jan 25 15:29:55 raspledeuix weewx[18327] ERROR weewx.drivers.vantage: Unable 
> to wake up console
> 

-- 
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/C16CAA0E-847F-446E-A55C-172AA5DB8E16%40gmail.com.

Re: [weewx-user] Re: Graph not update

[Graham Eddy]

is this the correct target ftp location?

> On 5 Feb 2021, at 5:24 pm, ginfo...@gmail.com  wrote:
> 
> Feb  5 05:55:32 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: Connected to 
> it31.siteground.eu 
> Feb  5 05:55:32 raspberrypi weewx[7414] DEBUG weeutil.ftpupload: Uploaded 
> file /home/weewx/public_html/favicon.ico to 
> /public_html/www.meteomestre.it/favicon.ico 
> 

-- 
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/38B1C430-4128-4CE9-8080-DE96FB9D97F5%40gmail.com.

Re: [weewx-user] Having trouble installing on Mac

[Graham Eddy]

did you run bin/weewxd as root, to have needed permissions for creating 
/var/log/weewx.log?

as an aside, you are thinking of moving weewx from mac to rpi. do it. macos 
continues to diverge from its linux roots into strange lands opaque to mere 
mortals e.g. i found daemons via launchd becoming impossible through successive 
macos releases without arcane knowledge, and abandoned macos 6 months ago. my 
mac mini now runs ubuntu in a DMZ and weewx runs wonderfully on an rpi 4B using 
raspian os. and i got a gw1000 to run as a service in parallel with my vp2 on 
same weewx instance
(my macos laptops are still great - i just recommend against macos for server)

> On 5 Feb 2021, at 9:16 pm, PAK  wrote:
> 
> Hi all,
> 
> I am very new and am struggling with a lot of this but hopefully this makes 
> sense.
> 
> I have a Mac, with an Ecowitt HP2553. I am trying to get a handle on this 
> before I purchase the GW1000 and maybe a Raspberry Pi. 
> 
> The second time I tried to install Weewx it went really well until the last 
> command. Here's the log: -
> pak@Peters-iMac weewx % python3 ./bin/weewxd weewx.conf
> 
> Traceback (most recent call last):
> 
>   File 
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/config.py",
>  line 563, in configure
> 
> handler = self.configure_handler(handlers[name])
> 
>   File 
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/config.py",
>  line 744, in configure_handler
> 
> result = factory(**kwargs)
> 
>   File 
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/handlers.py",
>  line 148, in __init__
> 
> BaseRotatingHandler.__init__(self, filename, mode, encoding, delay)
> 
>   File 
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/handlers.py",
>  line 55, in __init__
> 
> logging.FileHandler.__init__(self, filename, mode, encoding, delay)
> 
>   File 
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/__init__.py",
>  line 1143, in __init__
> 
> StreamHandler.__init__(self, self._open())
> 
>   File 
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/__init__.py",
>  line 1172, in _open
> 
> return open(self.baseFilename, self.mode, encoding=self.encoding)
> 
> PermissionError: [Errno 13] Permission denied: '/var/log/weewx.log'
> 
> 
> 
> The above exception was the direct cause of the following exception:
> 
> 
> 
> Traceback (most recent call last):
> 
>   File "./bin/weewxd", line 264, in 
> 
> main()
> 
>   File "./bin/weewxd", line 81, in main
> 
> weeutil.logger.setup(options.log_label, {})
> 
>   File "/Users/Shared/weewx/bin/weeutil/logger.py", line 187, in setup
> 
> logging.config.dictConfig(log_dict)
> 
>   File 
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/config.py",
>  line 808, in dictConfig
> 
> dictConfigClass(config).configure()
> 
>   File 
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/logging/config.py",
>  line 570, in configure
> 
> raise ValueError('Unable to configure handler '
> 
> ValueError: Unable to configure handler 'rotate'
> 
> pak@Peters-iMac weewx % 
> 
> 
> I am wondering if the driver is the problem. I think I need to install an 
> interceptor somehow? It might all be too much for me and could be easier to 
> go back to Davis hehe. All I really want are daily, weekly and yearly reports 
> like I'm used to with WeatherLink.
> 
> Thanks for any help,
> Peter. 
> 
> -- 
> 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/62969bcb-fadf-4d05-8671-b164a0ed9390n%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/AA7A84C6-917C-4869-B4DC-9627616EA228%40gmail.com.

Re: [weewx-user] Pausible values for UV sensor?!

[Graham Eddy]

https://wiki.cancer.org.au/skincancerstats/UV_radiation 
:

The UV Index is a standardised measure used to express UV radiation intensity. 
It is equal to 40 times the erythemally effective power of the sun in W/m2. The 
UV Index at solar noon is generally in the range 0-12 and values above 11 are 
considered extreme.[1] 

 In Australia, peak daily values in summer are regularly in excess of 12-14, 
and can reach 16-17 at more northern latitudes.[2] 

 When the forecast UV Index is ≥3, sun protection is required.[14] 


Table 1: Australian capital city average daily maximum UV levels by month.[15] 

LocationJan Feb Mar Apr May JuneJulyAug 
SeptOct Nov Dec
Darwin  12  13  12  11  9   8   9   10  12  
13  12  12
Brisbane12  11  9   7   5   4   4   5   
7   9   11  11
Perth   12  11  9   6   4   3   3   4   6   
8   10  11
Sydney  11  10  8   5   3   2   3   4   5   
7   9   10
Canberra11  8   7   5   3   2   2   3   
5   7   9   11
Adelaide11  10  8   5   3   2   2   3   
5   7   9   11
Melbourne   10  9   7   4   2   2   2   3   
4   6   8   10
Hobart  8   7   4   3   1   1   1   2   3   
4   6   7
Values are rounded to the nearest whole number. Highlighted months have an 
average daily maximum UV less than 3 even where rounding has made it appear 
otherwise.


> On 8 Feb 2021, at 12:44 pm, Greg Troxel  wrote:
> 
> I am at 42ish North (Massachusetts, US), and with a Davis UV sensor, the
> highest values I see are about 7.

-- 
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/5053A2CD-A07C-4D5B-BBDB-E689C9F44B97%40gmail.com.

Re: [weewx-user] Failed install of Cheetah on Mac Catalina

[Graham Eddy]

mine are case sensitive

> On 10 Feb 2021, at 3:04 pm, Gary Strand  wrote:
> 
> related to Macs being case-insensitive

-- 
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/94DC0E66-60DB-463E-80C4-7818E18F2539%40gmail.com.

Re: [weewx-user] WOW data upload customisation

[Graham Eddy]

the ecowitt WH51 reports soil moisture as percent. i changed unit_group in 
user.extensions to reflect this.
(‘percent of what?’ is a good question → calibration for own soil type, which 
i’ve yet to do, but it gives me sensible ballpark numbers out of the box)

> On 14 Feb 2021, at 1:26 am, Tom Keffer  wrote:
> 
> The source code would have to be modified.
> 
> However, the reason that WeeWX does not upload soil moisture to WOW is that 
> they expect the number to be in percent, whereas the rest of WeeWX has soil 
> moisture in centibars. When I wrote the code (now 10 years ago?), it wasn't 
> obvious to me how to convert between the two. As I understand it, the 
> conversion is soil specific.
> 
> If you can figure the conversion out, I'm happy to modify the code to support 
> WOW.
> 
> -tk
> 
> On Sat, Feb 13, 2021 at 5:58 AM hedle...@gmail.com 
>   > wrote:
> I wish to  add soil temperature data to my UK met  WOW upload  - can anyone  
> pont  me  ot  the skin/conf file  that  I  need  to  edit please? 
> 
> 
> 
> -- 
> 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/e777a026-e7c6-4174-a7b3-09ce348f7456n%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/CAPq0zEDG0%2B35GwnpoktYOQU7%3DmqV7C_U2vtNtPXjtrDfpmemLQ%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/1EEE69C6-4DCB-48EB-A1C4-94F0998E2AF2%40gmail.com.

Re: [weewx-user] Re: Cheetah Generator Errors

[Graham Eddy]

dunno whether this is a config error but the indentation and number of ‘[’s are 
not consistent here

> On 16 Feb 2021, at 7:06 am, Parker Lohrenz  wrote:
> 
> [[Belchertown]]
> template = js/belchertown.js.tmpl
> 
> [[[home]]]
> template = index.html.tmpl
> 

-- 
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/9D8F6D1C-B735-4C37-ADF3-114E7E71FB70%40gmail.com.

Re: [weewx-user] Re: Cheetah Generator Errors

[Graham Eddy]

that was my point. i think it was a subtle config error, not yet picked up by 
the authour, that did not cause a syntax error, but would truncate his expected 
reports. but, not knowing belchertown, perhaps this strange configuration was 
correct for it...

> On 16 Feb 2021, at 4:31 pm, gjr80  wrote:
> 
> Unlike python, configobj has no specific indentation requirements, it's just 
> us humans that like indentation. Square brackets on the other hand are 
> important, in this case there would have been no error (the square brackets 
> were consistent/matched) but [[Belchertown]] and below would have been 
> ignored by CheetahGenerator.
> 
> Gary
> 
> On Tuesday, 16 February 2021 at 11:49:58 UTC+10 graha...@gmail.com wrote:
> dunno whether this is a config error but the indentation and number of ‘[’s 
> are not consistent here
> 
>> On 16 Feb 2021, at 7:06 am, Parker Lohrenz > > wrote:
>> 
>> [[Belchertown]]
>> template = js/belchertown.js.tmpl
>> 
>> [[[home]]]
>> template = index.html.tmpl
>> 
> 
> 
> -- 
> 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/a8d9aeb8-3af3-4523-afd2-0ce32559e760n%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/03A06CBF-672A-490E-9D74-EB57D517BE5A%40gmail.com.

Re: [weewx-user] Re: Reboot GW1000 using monit?

[Graham Eddy]

internet our here in the bush is flakey and goes down often.
i have UPS on internet connection so have not looked out for gw1000 rebooting 
every 20 mins while running on battery. i will look out for it next time. 
*very* unsatisfactory if lack of external internet interrupts my local data 
collection

i would appreciate a recipe on how to bypass it (masquerading IPs to local 
server and spoofing http request, and ntp request?) in the gw1000 wiki, and 
appreciate even more it being an installation option on the driver/service

yes, i will lodge a complaint with ecowitt too. i can’t see the manufacturer 
changing it, but they need to be aware of the line crossed. (has anyone checked 
to see if it conflicts with ecowitt's declared privacy policy?)

> On 17 Feb 2021, at 9:27 am, vince  wrote:
> 
> Multiple people including me asked for a simple on/off switch for the 
> watchdogs so we could run LAN-only and they said no.
> 
> At least it can be faked on the LAN if you have enough network-fu, but we 
> shouldn't have to do stuff like 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/4C879964-7B78-4C34-945F-59DCC7EC91B1%40gmail.com.

Re: [weewx-user] Request for assistance - GW2000/WS90

[Graham Eddy]

anyone in australia know how i can order a GW2000 from here at present?
i want the ethernet port and sane power supply

-- 
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/8AA48E8D-7863-4203-B56A-12CC43784064%40geddy.au.

Re: [weewx-user] Davis Data Logger - Issue

[Graham Eddy]

my vp2 (15yo) recently started throwing this error (causing weewx restart) 
every few hours. perhaps coincidence, but it started very soon after after id 
#2 (a davis temperature station - the ISS has id #1) stopped reporting after 
several days of low battery alert on and off (i was travelling), kept happening 
for a few days, then stopped almost immediately after id #2 started reporting 
again after i changed its battery (when i got back)

> On 9 May 2022, at 7:02 am, Tom Keffer  wrote:
> 
> Now that I think about it, there is an experiment I've been meaning to try. 
> Right now, the Vantage driver tries 3 times, then gives up and restarts the 
> program from the top.
> 
> The experiment would be to do something not quite so drastic. Rather than 
> restart the program, try a Vantage "wake up" sequence instead.
> 
> I've never tried this strategy because there hasn't been a logger regularly 
> showing this error that I could test. But it appears yours does. I'm tied up 
> with something else, but give me a few days to come up with a solution.
> 
> In the meantime, I've posted issue #772 
> .

-- 
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/C01F4424-57BD-4650-B92A-0C7AB70F8B0B%40geddy.au.

Re: [weewx-user] Davis Data Logger - Issue

[Graham Eddy]

i reported earlier that i got a burst of weewx restarts by vantage driver when 
my extra vp2 station (wireless temp) battery started reporting low (i hadn’t 
noticed until this thread started). tom’s new retry patch not applied. this 
happened a second time recently viz. burst of restart activity when extra 
station reported low battery. nothing to do with power supplies or reboots, i 
am more inclined to point to an envoy or data logger/usb firmware bug (they are 
more than 15yo).
(it is possible this firmware bug could lead to phantom battery low reports; i 
think more likely they were genuine battery low events driving the error)

sadly this extra wireless vp2 station has just been borked - it was under water 
for a week in 2010 floods (i mounted it higher after that :-) but a few days 
ago couldn’t survive 2-3 tonnes of tree branch crushing it on rocks. it will be 
replaced by a much much cheaper ecowitt remote temp probe (i run dual 
vp2/gw1000)

> On 19 May 2022, at 1:09 am, Paul Dunphy  wrote:
> 
> Whatever it is, it's related to RPis talking to a Davis Logger via USB. I 
> have a couple of powered USB hubs lying around. I can try putting one of them 
> on in the next day or so . . . now that you mention it, I never had any 
> trouble with an RPi 3. However, it did/does manifest itself on three 
> different RPi 4s. I'll report back when I have results using a powered hub.
> 
> - Paul VE1DX
> 
> On 2022-05-18 11:14 a.m., Tom Keffer wrote:
>> I don't know that it's a "timing issue," but it could certainly be a power 
>> issue. 
>> 
>> The USB power supplies for many RPis can be barely adequate. In particular, 
>> the RPi 4 uses a lot of power. It doesn't take much for the power to sag, 
>> resulting in errors.
>> 
> 
>   >snip<
> 
> -- 
> 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/9d5bf73c-2c97-fd8b-6a14-06dfbeb751d3%40gmail.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/C3966CBD-3617-43B9-9D9A-92FF650FC34F%40geddy.au.

[weewx-user] vp2 - how to disable ch2?

[Graham Eddy]

my old vantage pro2’s additional wireless temp station at ch2 (iss is at ch1) 
has carked it (crushed in tree fall). it exists no more; it is not 
transmitting. my vp2 data logger is faithfully reporting a phantom value of 
about 150 C (not bad for a river!) every few seconds, how do i disable this 
phantom?

i tried (with weewx not running) ‘wee_device --set-transmitter-type=2,10’ to 
set ch2 to none, but all i get is an error ‘No  received from Vantage 
console’, and it continues reporting the phantom when i start weewx again. how 
can i stop this phantom?
cheers

-- 
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/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au.

Re: [weewx-user] vp2 - how to disable ch2?

[Graham Eddy]

QC is filtering out the bad values, but weewx server is currently resetting 
after 4 failed retries on regular basis while the phantom station haunts the 
vp2. there is no radio signal being transmitted to provide the extraTemp1 
values, it is just a figment of data logger’s imagination. the phantom 
battery-low apparently from the ex-station stopped yesterday, but the data 
logger is still reporting the extraTemp1 despite my (failed) wee_device 
instruction just now to desist

i do ‘wee_device —set-transmitter-type=2,10’ and it gives ’no ’ error.
then i do ‘wee_device —info’ and it reports ch2 still enabled
so it is not just a case of resetting memory/power

weewx v4.5.1 using python3.7 on RPi 4B running buster with usb/serial
(vp2 firmware is from 2004. lately weewx has been resetting whenever the (now 
ex-) extra station reported low battery, so this bogus extraTemp1 value 
upsetting weewx is kinda understandable → i need to turn all vestiges of the 
(ex-) extra station off)

> On 25 May 2022, at 5:53 pm, Stephen Hocking  wrote:
> 
> Given such a whacko figure, perhaps under the [[Corrections]] section under 
> [StdCalibrate], or more suitably, something under [StdQC].
> 
> On Wed, 25 May 2022 at 17:45, Graham Eddy  <mailto:g...@geddy.au>> wrote:
> my old vantage pro2’s additional wireless temp station at ch2 (iss is at ch1) 
> has carked it (crushed in tree fall). it exists no more; it is not 
> transmitting. my vp2 data logger is faithfully reporting a phantom value of 
> about 150 C (not bad for a river!) every few seconds, how do i disable this 
> phantom?
> 
> i tried (with weewx not running) ‘wee_device --set-transmitter-type=2,10’ to 
> set ch2 to none, but all i get is an error ‘No  received from Vantage 
> console’, and it continues reporting the phantom when i start weewx again. 
> how can i stop this phantom?
> cheers
> 
> -- 
> 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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au
>  
> <https://groups.google.com/d/msgid/weewx-user/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au?utm_medium=email&utm_source=footer>.
> 
> 
> -- 
>   "I and the public know
>   what all schoolchildren learn
>   Those to whom evil is done
>   Do evil in return"  W.H. Auden, "September 1, 1939"
> 
> 
> -- 
> 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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/CA%2BxzKjDCR-xMeMrCDm7_Nq1XeJikmWSJ9N1TYcPezwLc0x7h%3Dw%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/weewx-user/CA%2BxzKjDCR-xMeMrCDm7_Nq1XeJikmWSJ9N1TYcPezwLc0x7h%3Dw%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-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/F4510CA0-CFDC-4855-A336-6A1FCED46B72%40geddy.au.

Re: [weewx-user] vp2 - how to disable ch2?

[Graham Eddy]

data logger is in an envoy

> On 25 May 2022, at 7:25 pm, gjr80  wrote:
> 
> Can't you set transmitter IDs manually via the console?
> 
> Gary
> 
> On Wednesday, 25 May 2022 at 18:18:36 UTC+10 Graham Eddy wrote:
> QC is filtering out the bad values, but weewx server is currently resetting 
> after 4 failed retries on regular basis while the phantom station haunts the 
> vp2. there is no radio signal being transmitted to provide the extraTemp1 
> values, it is just a figment of data logger’s imagination. the phantom 
> battery-low apparently from the ex-station stopped yesterday, but the data 
> logger is still reporting the extraTemp1 despite my (failed) wee_device 
> instruction just now to desist
> 
> i do ‘wee_device —set-transmitter-type=2,10’ and it gives ’no ’ error.
> then i do ‘wee_device —info’ and it reports ch2 still enabled
> so it is not just a case of resetting memory/power
> 
> weewx v4.5.1 using python3.7 on RPi 4B running buster with usb/serial
> (vp2 firmware is from 2004. lately weewx has been resetting whenever the (now 
> ex-) extra station reported low battery, so this bogus extraTemp1 value 
> upsetting weewx is kinda understandable → i need to turn all vestiges of the 
> (ex-) extra station off)
> 
> 
>> On 25 May 2022, at 5:53 pm, Stephen Hocking > > wrote:
>> 
> 
>> Given such a whacko figure, perhaps under the [[Corrections]] section under 
>> [StdCalibrate], or more suitably, something under [StdQC].
>> 
>> On Wed, 25 May 2022 at 17:45, Graham Eddy > > wrote:
>> my old vantage pro2’s additional wireless temp station at ch2 (iss is at 
>> ch1) has carked it (crushed in tree fall). it exists no more; it is not 
>> transmitting. my vp2 data logger is faithfully reporting a phantom value of 
>> about 150 C (not bad for a river!) every few seconds, how do i disable this 
>> phantom?
>> 
>> i tried (with weewx not running) ‘wee_device --set-transmitter-type=2,10’ to 
>> set ch2 to none, but all i get is an error ‘No  received from Vantage 
>> console’, and it continues reporting the phantom when i start weewx again. 
>> how can i stop this phantom?
>> cheers
>> 
>> -- 
>> 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 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au
>>  
>> <https://groups.google.com/d/msgid/weewx-user/70718B18-F8FE-49F8-8303-7BE22F28B8DC%40geddy.au?utm_medium=email&utm_source=footer>.
>> 
>> 
>> -- 
>>   "I and the public know
>>   what all schoolchildren learn
>>   Those to whom evil is done
>>   Do evil in return" W.H. Auden, "September 1, 1939"
>> 
>> 
>> -- 
>> 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 
>> .
> 
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/CA%2BxzKjDCR-xMeMrCDm7_Nq1XeJikmWSJ9N1TYcPezwLc0x7h%3Dw%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/CA%2BxzKjDCR-xMeMrCDm7_Nq1XeJikmWSJ9N1TYcPezwLc0x7h%3Dw%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-user+unsubscr...@googlegroups.com 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/3b764166-7458-4fd1-a0e7-4acbee17e7d4n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/3b764166-7458-4fd1-a0e7-4acbee17e7d4n%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/D38AF7A8-8AC0-4A50-8F49-F98A595EFEF3%40geddy.au.

Re: [weewx-user] vp2 - how to disable ch2?

[Graham Eddy]

i can power down, pull it apart, put the batteries in backwards. how do i reset 
it?
(and why would wee_device be failing to reconfigure ch2 but work successfully 
otherwise?)

> On 25 May 2022, at 8:13 pm, gjr80  wrote:
> 
> Doesn't leave many options. Can't power down/reset the envoy?
> 
> Gary
> 
> On Wednesday, 25 May 2022 at 19:53:32 UTC+10 Graham Eddy wrote:
> data logger is in an envoy
> 
> 
>> On 25 May 2022, at 7:25 pm, gjr80 > > wrote:
>> 
> 
>> Can't you set transmitter IDs manually via the console?
>> 
>> 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/C6DEC2F7-0B3B-4FD4-ACD7-661727422852%40geddy.au.

Re: [weewx-user] vp2 - how to disable ch2?

[Graham Eddy]

did that - envoy has now forgotten the old wireless station [RESOLVED] - thanks

it has been a lot of years since the envoy was last unpowered!

> On 27 May 2022, at 6:21 am, gjr80  wrote:
> 
> I don't have an Envoy but I understand it is a case of removing all power 
> sources, including batteries, waiting for 10-20 seconds for any capacitance 
> to discharge and then power up again. Don't know I would put the batteries in 
> reverse though.
> 
> Gary
> 
> On Wednesday, 25 May 2022 at 21:05:36 UTC+10 Graham Eddy wrote:
> i can power down, pull it apart, put the batteries in backwards. how do i 
> reset it?
> (and why would wee_device be failing to reconfigure ch2 but work successfully 
> otherwise?)
> 
> 
>> On 25 May 2022, at 8:13 pm, gjr80 > > wrote:
>> 
>> Doesn't leave many options. Can't power down/reset the envoy?
>> 
>> Gary
>> 
>> On Wednesday, 25 May 2022 at 19:53:32 UTC+10 Graham Eddy wrote:
>> data logger is in an envoy
>> 
>> 
>>> On 25 May 2022, at 7:25 pm, gjr80 > wrote:
>>> 
>> 
>>> Can't you set transmitter IDs manually via the console?
>>> 
>>> 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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/f5fd67c3-594c-45d3-9000-8f2b09a31e51n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/f5fd67c3-594c-45d3-9000-8f2b09a31e51n%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/13B27969-E764-4CDF-80C8-5B336B8B9EE6%40geddy.au.

Re: [weewx-user] LOOP try problem ...

[Graham Eddy]

not the reported problem, but config error needs to be fixed nonetheless

> On 18 Jun 2022, at 1:14 am, mup...@gmail.com  wrote:
> 
> Jun 17 08:09:38 weewx-RPi weewx[83743] ERROR weewx.engine: The archive 
> interval in the configuration file (300) does not match the station hardware 
> interval (1800).
> Jun 17 08:09:38 weewx-RPi weewx[83743] INFO weewx.engine: Using archive 
> interval of 1800 seconds (specified by hardware)

-- 
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/33ED3171-3EDD-45D1-82B6-722E0DD6C809%40geddy.au.

Re: [weewx-user] LOOP try problem ...

[Graham Eddy]

as tom noted, you need to configure the vp2 console device to 300 secs to get 
reports each 5 mins (or change weewx.conf file to 1800 secs if every 30 mins 
sufficient)

this would not cause the read errors on the vp2, so is off-topic, but worth 
pointing out.
cheers

> On 18 Jun 2022, at 2:23 pm, mup...@gmail.com  wrote:
> 
>> The archive interval in the configuration file (300) does not match the 
>> station hardware interval (1800)

-- 
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/DBC76C09-79A4-4E00-B5FC-E6B12D8685AB%40geddy.au.

Re: [weewx-user] howto fix weewx sqlite database

[Graham Eddy]

15 years of data, running happily on RPi 4B:
graham@paperbark:/home/weewx/archive $ ls -l weewx.sdb 
-rw-r--r-- 1 weewx weewx 175935488 Jul 11 00:55 weewx.sdb

> On 11 Jul 2022, at 12:43 am, Fische Namenlos  wrote:
> 
> my station is using sqlite database (weewx.sdb) for nearly 5 years, and now - 
> I suppose - is getting to big for my Raspi-server, it stops working/writting.

-- 
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/8C3EB25A-F4A3-4D14-B43C-16556831AF91%40geddy.au.

Re: [weewx-user] Only use wee_import without connecting a weather station

[Graham Eddy]

perhaps consider the provided ‘fileparse’ driver - see 
~weewx/examples/fileparse/readme.txt

> On 29 Aug 2022, at 7:43 pm, Stein Arne Storslett  wrote:
> 
> Is there a way to only run the weewx database with data through "wee_import" 
> without connecting a weather station?
> I.e. just producing the web pages / reports.
> 
> Re another thread I have issues getting weewx to connect to my weather 
> station console, the Cotech Weather Station sold by ClasOhlson in the 
> nordics, Europe.
> 
> However I've been able to produce data via the station's (somewhat arcane) 
> software WeatherHome so I want to create the reports based on 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/fc0712e7-326d-45ed-811b-3e4c6c3a94b0n%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/9FA4093A-41D4-4B19-928D-C762200257EB%40geddy.au.

Re: [weewx-user] Never thought it could happen

[Graham Eddy]

i was travelling when it flooded back home (se oz) 6 weeks ago. lots of folk 
watch my river depth graph so as the value unexpectedly went off the top of 
graph, i updated the y-scale to compensate a few times. someone asked me to 
stop increasing it because i was dragging the river level up :-)
⊣GE⊢

> On 1 Jan 2023, at 10:21 am, Gerard Cerchio  wrote:
> 
> When I set up my station  I 
> wrote in 2 rain gauges, a weekly and an annual. I had never seen more than 3 
> inches of rain in a week so I set a 4 rain inch high graphic for the week. In 
> this single past week we got more rain then we got all year. Who'd a thunk 
> 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/75e68c94-3b32-49a2-91ec-b10f91e295b8n%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/51E45CF8-8603-4BE6-8E76-28F8D194B96E%40geddy.au.

Re: [weewx-user] Davis VP2 reliability with Rasp Pi zero

[Graham Eddy]

It is much more likely your power supply being the problem. Get a ups to smooth the spikes (dunno if rpi hat does that)⊣ GE ⊢    phone➔brevityOn 6 Jan 2023 12:46 pm, "iams...@gmail.com"  wrote:"What happens if you 'pull the plug' on your VP2? Does it keep running? Perhaps the batteries are bad?Yes, it keeps running, that is why it seems to be a weewx issue to me. In other words, if the Pi Zero running weewx were not connected to the VP2, the data logger memory would not get corrupted. In fact, weewx is able to recover data that was gathered during the power outage (while the Pi is shut down). It is only when power is restored that the data logger corruption happens. At least I assume that is really the root of the issue, I really don't know. All I know is that almost every time the power goes out, I get the record time error and all data recording and uploading stops.I've looked into getting a UPS for the Pi, which really appears to be nothing more than a $15 ext phone battery, but it seems to me this is a weewx problem that should be addressed. Alternately, I can contact Davis to see what they say."On Thursday, January 5, 2023 at 3:34:40 PM UTC-8 tke...@gmail.com wrote:It should work.What happens if you 'pull the plug' on your VP2? Does it keep running? Perhaps the batteries are bad?Personally, I use a UPS for both the weewx server and the VP2 and haven't had a memory corruption problem in at least a decade. So, you could try that.On Thu, Jan 5, 2023 at 11:30 AM iams...@gmail.com  wrote:I've been using weewx running on a Pi Zero with no other tasks. Unfortunately, I live in a area that suffers power losses, often during a weather events, so I lose that data. What typically happens is that when the power comes back on, I get the dreaded "..page timestamp... less than final timestamp..." error. The only way I have been able to address it is to use the memory dump and clear. I don't understand why this happens since the VP2 is running with battery backup, yet the memory on the datalogger gets corrupted. Is this an issue with weewx that could be addressed?Failing that, can I address this issue by adding a backup supply to my Pi Zero?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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/c833a23b-2957-4311-882a-cda796d0c928n%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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/7bd3876d-96a1-4c3a-82fb-c4f406234066n%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/709fe62a-0bad-4448-9b1f-318c3e05bb72%40email.android.com.

[weewx-user] line gaps

[Graham Eddy]

i am getting a sequence of points plotted rather than a line showing.
line_type = solid
line_gap_fraction = 0.3
the points are 20 mins apart. 20min/24hrs = 0.013 so i expect the points to be 
joined.
i have tried line_gap_fraction 0.9 and - just to be thorough - 1.0 and (being 
silly) 10.0 - with no change.
any ideas how to ‘join the dots’?
google is my friend but he didn’t help this time.
cheers


⊣GE⊢

-- 
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/5E209B62-AD8B-4F6E-8219-EC2778D16E35%40geddy.au.

Re: [weewx-user] line gaps

[Graham Eddy]

this means line_gap_fraction relates only to interval gaps of whole records, 
not of column value gaps within successive records.
hmm, inserting interpolated values to cover interval gaps in a column can only 
be done to past records - nope, i don’t want to go there...
well, now i know - learn to love the ‘mark’ not the ‘line'.
thanks
⊣GE⊢

> On 19 Jan 2023, at 2:49 am, Tom Keffer  wrote:
> 
> You're not doing something dumb. None values always mark line breaks. 
> 
> On Wed, Jan 18, 2023 at 6:30 AM Graham Eddy  <mailto:g...@geddy.au>> wrote:
> 

-- 
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/D4BCD919-180F-45F4-AA01-845B49CB9A74%40geddy.au.

Re: [weewx-user] line gaps

[Graham Eddy]

fair request, but i don’t GitHub, so some code follows.
my old RPi test box is now my production LoRaWAN box, so i worked using my 
production weewx box, so testing is pretty minimal (seems to work on my two 
graphs)

see weeplot/utilities.py:520 on weewx 5.8.0:

line = []
last_x = None
for xy in zip(x, y):
#GE start new
# If the y coordinate is None, ignore it
if xy[1] is None:
continue
#GE end new 
dx = xy[0] - last_x if last_x is not None else 0
last_x = xy[0]
#GE start original
#GE# If the y coordinate is None or dx > maxdx, that marks a break
#GEif xy[1] is None or (maxdx is not None and dx > maxdx):
#GE end original
#GE start new
# If dx > maxdx, that marks a break
if (maxdx is not None and dx > maxdx):
#GE end new 
# If the length of the line is non-zero, yield it
if len(line):
yield line
line = [] if xy[1] is None else [xy]
else:   
line.append(xy)
if len(line):
yield line

cheers
⊣GE⊢

> On 19 Jan 2023, at 12:50 pm, Tom Keffer  wrote:
> 
> Speaking of dumb, in retrospect, this seems like a dumb choice. It should be 
> at least optional.
> 
> The code was written about 10 years ago. I simply cannot remember why I chose 
> to always honor None values, despite any value of line_gap_fraction.
> 
> A PR would be welcome, should you wish to write one.
> 
> On Wed, Jan 18, 2023 at 4:55 PM Graham Eddy  <mailto:g...@geddy.au>> wrote:
>> this means line_gap_fraction relates only to interval gaps of whole records, 
>> not of column value gaps within successive records.
>> hmm, inserting interpolated values to cover interval gaps in a column can 
>> only be done to past records - nope, i don’t want to go there...
>> well, now i know - learn to love the ‘mark’ not the ‘line'.
>> thanks
>> ⊣GE⊢
>> 
>>> On 19 Jan 2023, at 2:49 am, Tom Keffer >> <mailto:tkef...@gmail.com>> wrote:
>>> 
>>> You're not doing something dumb. None values always mark line breaks. 
>>> 
>>> On Wed, Jan 18, 2023 at 6:30 AM Graham Eddy >> <mailto:g...@geddy.au>> wrote:
>>> 
>> 
>> 
>> -- 
>> 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 
>> <mailto:weewx-user+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/D4BCD919-180F-45F4-AA01-845B49CB9A74%40geddy.au
>>  
>> <https://groups.google.com/d/msgid/weewx-user/D4BCD919-180F-45F4-AA01-845B49CB9A74%40geddy.au?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 
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEAoEWv3TdnHZ%2BJeWmbQV7t20-h2N9La3geer7eiLyavMA%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEAoEWv3TdnHZ%2BJeWmbQV7t20-h2N9La3geer7eiLyavMA%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-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6EF71977-00B3-465E-A252-2CC02F7B1C3E%40geddy.au.

[weewx-user] new river level monitor

[Graham Eddy]

i posted some time ago about my trusty old river level monitor. i am still 
receiving occasional enquiries about it - yes, unfortunately that product i 
used is no longer available. whilst it is still working for me, i have now 
deployed a new river level monitor in parallel, some details below

old river level monitor

Aquagauge provided a radio receiver with serial interface and a number of 
sensor types with radio transmitters. a receiver could support up to 8 
transmitters. the radio and serial protocols are proprietary

i wrote a weewx service that read the serial interface and inserted the data 
values into weewx packets. later i migrated this to a daemon that emitted the 
data as mqtt messages, and weewx reads the mqtt messages. this works fine; it 
is still in use

this river level sensor is pressure-based i.e. the probe sits on river bottom 
(in my case wrapped around a brick and tucked into a river bank nook) and 
measures the water pressure. there is a very inconvenient cable from the probe 
to the transmitter. the latter measures atmospheric pressure, the pressure 
difference is the weight of the water above the sensor thence deriving water 
depth. it proved to be quite accurate

the transmitter has suffered many travails, the latest being going for a swim 
during a flood when the bridge it was on was swept downstream. it is very 
robust but now failing more often and i fear one day soon not being able to 
rescusitate it → motivation for replacement. this product is no longer sold or 
supported

new river level sensor

i decided to try an ultrasound sensor i.e. the probe measures round-trip time 
for a signal reflected from river surface back to probe with known speed of 
signal. this means there is no cable needed to run into the river

my river level sensor must be a commercial off-the-shelf product, for which i 
am happy to write interface software. it also has to be wireless connection to 
RPi at least 50 meters away and be powered by long-life battery

i picked a Dragino LDDS75 Distance Detector 
(https://www.dragino.com/products/distance-level-sensor/item/161-ldds75.html). 
i mounted it under the sparkling new bridge i built over the river, higher than 
the old bridge. it sends quite large and complex messages via mqtt, so i wrote 
a daemon that plucks the salient data and re-publishes as simple message, 
imported into weewx. my daemon also configures a fix-point height for the 
sensor, so the simplified mqtt message includes a ‘level’ field as well as 
‘distance’ for easy digestion

this is a LoRaWAN device so provides the long distance and battery longevity i 
require

radio receiver server

the new river level sensor is the first of several sensors on my new open radio 
network, as opposed to the closed proprietary radio network per Aquagauge, so i 
need a radio transceiver to talk to them. i assume familiarity with LoRaWAN 
(https://www.thethingsnetwork.org/docs/lorawan/architecture/)

for the local LoWRaWAN gateway, i put a RAK 2245 LoRaWAN HAT 
(https://www.rakwireless.com/en-us/products/lpwan-gateways-and-concentrators/rak2245-pihat)
 on an RPi 4B and installed RAK’s gateway software from their GitHub

i tried using the chirpstack LoRaWAN stack running on local server but couldn’t 
get it to work reliably, it seemed to work only intermittently. i think i was 
having trouble with not picking up the radio packet preamble but, not being a 
radiohead, gave it up as too much like hard work. i tried The Things Network 
stack (https://www.thethingsindustries.com/docs/getting-started/ttn/) and, to 
paraphrase steve jobs, ‘it just worked’. i am using the ’community edition’, 
which is a subscribed but free service. the downside is that the network server 
and join server run on TTN’s hardware over the internet so i lose device 
connectivity when internet link is down. they provide the software to run your 
own copy of the stack, which i plan to do in future

so, the river level sensor emits radio packets, my RPi gateway receives the 
packets and sends to TTN stack, the TTN stack processes and emits them as 
complex mqtt messages, which my dameon picks up and simplifies, then weewx 
digests the simplified mqtt messages. (i have chosen to put LoRaWAN gateway on 
a separate RPi from the weewx RPi)

the TTN stack’s mqtt broker is on their remote server. i have chosen to bridge 
that mqtt broker to my RPi gateway so that, from my home network’s perspective, 
all that LoRaWAN stuff is happening on my RPi gateway. this fits my plan to 
move the TTN stack to the RPi gateway in future

the RAK 2245 includes an itty bitty antenna. i get a good signal and reliable 
connection at 100 meters, haven’t tested further distance. LoRa supports 10 km 
with a decent antenna

additional sensors

the LoRaWAN gateway supports a lot of LoRa devices simultaneously, it is just a 
case of joining them to the radio network and processing their dat

i have also deployed a river temperature sensor (replacing the VP2 wir

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Graham Eddy]

vnc makes no relevant difference.
command = ‘screen’ below shows program ‘screen’ has a ‘pi’ user process open on 
/dev/ttyUSB0 at the moment. not weewxd. probably left over from earlier 
troubleshooting.
kill it with “sudo killall screen”.
check if any weewxd’s or screen’s hanging around with “ps -ef | grep -e weewxd 
-e screen”. kill them if you find any.
you should now be back to a clean state with /devttyUSB0 ready for opening. do 
“sudo lsof /dev/ttyUSB0” to be sure

> On 25 Feb 2021, at 5:24 pm, gjr80  wrote:
> 
> I don't know, I'm a SSH only person, I am getting out of my depth now.
> 
> Gary
> 
> On Thursday, 25 February 2021 at 16:21:11 UTC+10 monmul wrote:
> I am using VNC Viewer (and always have) rather than SSHnot sure if that 
> makes any difference?
> 
> On Thursday, 25 February 2021 at 19:13:29 UTC+13 gjr80 wrote:
> Hmm, different to my Davis on my RPi which shows weewxd rather than screen. I 
> will have to defer to Tom or someone who knows about screen.
> 
> Gary
> 
> On Thursday, 25 February 2021 at 15:58:07 UTC+10 monmul wrote:
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
>   Output information may be incomplete.
> COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
> screen  16582   pi6u   CHR  188,0  0t0 20196 /dev/ttyUSB0
> pi@WeatherPi:~ $ 
> 

-- 
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/3FE5D7F5-535A-4DB7-94BD-9D3C11D6A47B%40gmail.com.

Re: [weewx-user] Tracking Rainfall 9 AM to 9 AM (Australia)

[Graham Eddy]

i have been using this for a while#evilbunny2008 attributed this in 2018 to Gary in australia



-- 
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/99B40A58-AFB4-4DB0-A217-4635896E0BF4%40gmail.com.
# since.py
#evilbunny2008 attributed this in 2018 to Gary in australia
# since 9am today: $since($hour=9).rain.sum.formatted
# since 9am yesterday: today $since($hour=9,$today=false).rain.sum.formatted
#
# A Search List Extension to provide aggregates since a given hour.
#
# python imports
import datetime
import syslog
import time

# weeWX imports
import weeutil.weeutil
import weewx.cheetahgenerator
import weewx.units

def logmsg(level, msg):
syslog.syslog(level, 'since: %s' % msg)

def logdbg(msg):
logmsg(syslog.LOG_DEBUG, msg)

def logdbg2(msg):
   if weewx.debug >= 2:
logmsg(syslog.LOG_DEBUG, msg)

def loginf(msg):
logmsg(syslog.LOG_INFO, msg)

def logerr(msg):
logmsg(syslog.LOG_ERR, msg)


class Since(weewx.cheetahgenerator.SearchList):
"""SLE to provide aggregates since a given time of day."""

def __init__(self, generator):
# call our parent's initialisation
super(Since, self).__init__(generator)

def get_extension_list(self, timespan, db_lookup):
"""Returns a NewBinder object that supports aggregates since a given
   time.

The NewBinder object implements the tag $since that allows
inclusion of aggregates since the last occurrence of a give time of
day, eg total rainfall since 9am, average temperature since midday.
The signature of the $since tag is:

$since([$hour=x]).obstype.aggregation[.optional_unit_conversion][.optional_formatting]

where

x is an integer from 0 to 23 inclusive representing the hour of the
day

obstype is a field in the archive table in use eg outTemp, inHumidiy
or rain

aggregation is an aggregate function supported by weewx (refer
Customization Guide appendices)

optional_unit_conversion and optional_formatting are optional weeWX
unit conversion and formatting codes respectively

Parameters:
timespan: An instance of weeutil.weeutil.TimeSpan. This will hold
  the start and stop times of the domain of valid times.

db_lookup: This is a function that, given a data binding as its
   only parameter, will return a database manager object.

Returns:
A NewBinder object with a timespan from "hour" o'clock to the
report time
  """

t1 = time.time()

class NewBinder(weewx.tags.TimeBinder):

def __init__(self, db_lookup, report_time,
 formatter=weewx.units.Formatter(),
 converter=weewx.units.Converter(), **option_dict):
# call our parents initialisation
super(NewBinder, self).__init__(db_lookup, report_time,
formatter=formatter,
converter=converter,
**option_dict)

def since(self, data_binding=None, hour=0, minute=0, today=True):
"""Return a TimeSpanBinder for the period since 'hour'."""

# get datetime obj for the time of our report
stop_dt = datetime.datetime.fromtimestamp(timespan.stop)
# the timespan we want may be wholly within today or may have
# started yesterday, it depends on the value of the hour
# parameter
# first, get time obj for "hour" o'clock
hour_t = datetime.time(hour, minute)
if stop_dt.hour >= hour and stop_dt.minute >= minute:
# our timespan is solely within today, the start ts is at
# "hour" o'clock
# get datetime obj for "hour" o'clock today
hour_dt = datetime.datetime.combine(stop_dt, hour_t)
else:
# our timespan starts yesterday and finishes today, so our
# start ts is "hour" o'clock yesterday
# first, get a datetime object for yesterday
yest_dt = stop_dt + datetime.timedelta(days=-1)
# get datetime obj for "hour" o'clock yesterday
hour_dt = datetime.datetime.combine(yest_dt, hour_t)
# now get a ts, that is our start ts
start_ts = time.mktime(hour_dt.timetuple())
# and put together our timespan as a TimeSpan object
 

Re: [weewx-user] Tracking Rainfall 9 AM to 9 AM (Australia)

[Graham Eddy]

put file in /home/weewx/bin/user/since.py (if /home/weewx is where weewx in 
installed) so python sees it as module user.since

add class user.since.Since to search_list_extensions in your skin.conf e.g.
[CheetahGenerator]

# Possible encodings are 'html_entities', 'utf8', or 'strict_ascii'
encoding = html_entities

# Search list extensions
search_list_extensions = user.since.Since, user.forecast.ForecastVariables

[[SummaryByMonth]]
# Reports that summarize "by month"
[[[NOAA_month]]]
encoding = utf8
template = NOAA/NOAA-%Y-%m.txt.tmpl
update your .html.tmpl to use the $since timespan e.g.
$since($hour=9).rain.sum.format(add_label=False)

> On 1 Mar 2021, at 3:59 pm, Robert D  wrote:
> 
> Thanks Graham - looking at it with a text editor...it looks like it has been 
> written to do what want. 
> But being a bit of a newby - I am not sure what to do with it..!!  My guess 
> is something similar to the BigTempPanel..???
> 
> "copy wfpiconsole.include.kv to the /home/pi/wfpiconsole directory copy 
> bigtempinclude.py to the /home/pi/wfpiconsole/lib directory
> 
> cp wfpiconsole.include.kv /home/pi/wfpiconsole/ cp bigtempinclude.py 
> /home/pi/wfpiconsole/lib/
> Change ownership on both files to pi
> 
> chown pi:pi /home/pi/wfpiconsole/lib/bigtempinclude.py chown pi:pi 
> /home/pi/wfpiconsole/wfpiconsole.include.kv
> Modify /home/pi/wfpiconsole/wfpiconsole.kv
> 
> Insert the following line on line 27: #:include wfpiconsole.include.kv
> 
> Modify /home/pi/wfpiconsole/main.py
> 
> Insert the following lines starting at line 226 from lib.bigtempinclude 
> import BigTempPanel from lib.bigtempinclude import BigTempButton
> 
> Modify /home/pi/wfpiconsole/wfpiconsole.ini Beginning around line 50, modify 
> the PrimaryPanel or SecondaryPanel section to enable the BigTemp panel in 
> whichever position you like."
> 
> 
> 
> Rob.
> 
> 
> 
> On Monday, 1 March 2021 at 15:08:47 UTC+10:30 graha...@gmail.com wrote:
> i have been using this for a while
> 
> #evilbunny2008 attributed this in 2018 to Gary in australia
> 
> -- 
> 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/38d1c2f1-3066-4918-860d-6fcd8c1de2een%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/90BBB476-F68C-407C-8809-975F5CB41903%40gmail.com.

Re: [weewx-user] Tracking Rainfall 9 AM to 9 AM (Australia)

[Graham Eddy]

after adding since.py file to bin/user/, and adding user.since.Since to 
skin.conf, you could just edit your .html.tmpl files to change ‘$day.rain.sum’ 
to ‘$since($hour=9).rain.sum’ (i.e. ‘$day’ → ‘$since($hour=9)’), so that all 
your daily rain is since 9am instead of since midnight. i think that is worth a 
go. just save copies of the files you are about to change if you want that 
backstop

> On 1 Mar 2021, at 6:39 pm, Robert D  wrote:
> 
> Thanks - that has given me lots to look at.
> Working out how to install a new skin will take some research & reading up...
> Everything in my setup is "standard" - I haven't learned enough to start 
> modifying things yet.
> I will have a look at the APP.
> What I am aiming for is  BOM style monthly Climate Stats report for my 
> location.
> 

-- 
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/9A96571C-7C4C-4BA1-ABB6-5454B9A44B8E%40gmail.com.

Re: [weewx-user] Weather station on Raspberry Pi with LTE/4G connect

[Graham Eddy]

do you really want to push the raw data form RPi to webserver, on which you 
will have to generate the reports (e.g. another instance of weewx), or generate 
the reports on RPi and push the reports to the webserver?

> On 1 Mar 2021, at 7:52 pm, Christian Radermacher 
>  wrote:
> 
> So the best way is to push the Data to an Webserver/Database offsite the Pi.  
> I don´t want to store the Date local on the Pi. The Website is available over 
> the Internet, so everyone can see it, the Pi isn't available from the 
> Internet.

-- 
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/B9D6A900-2745-41CB-AC33-06DF9FDDA34F%40gmail.com.

Re: [weewx-user] Weather station on Raspberry Pi with LTE/4G connect

[Graham Eddy]

i’ve implemented my own bidirectional gateway and i also parked this issue - 
next version’s problem, as i had no present need for it. but i am moving my 
system (of which weewx is a component) to mqtt backbone (e.g. my alarms weewx 
service moving to mqtt for more general use) so i would be very interested to 
discuss this issue with you as it impacts all my mqtt apps. i tracked the 
publish requests while they were in client-side queue but didn’t persist them, 
wondering about true need and performance cost

> On 3 Mar 2021, at 11:14 am, bell...@gmail.com  wrote:
> 
> In order to ensure data delivery, I’ve started investigating ‘persistent 
> sessions’ (clean_session = False) and a QOS = 2. I think on the subscribe 
> side it will be that easy - assuming the broker is configured correctly. On 
> the publish side, I’ll probably have to keep track of failed publishes and 
> have some type of retry - not sure I really want to deal with 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/BFEC0C32-54AD-4410-B22D-B0F599A0D1C5%40gmail.com.

Re: [weewx-user] Re: Skin not change

[Graham Eddy]

if you have any other skins enabled, and they point to the same directory, they 
would be overwriting the new specification

> On 3 Mar 2021, at 6:13 pm, gjr80  wrote:
> 
>  [[StandardReport]]
>  # This is the old "Standard" skin. By default, it is not enabled.
>  skin = neowx-material
>  enable = true

-- 
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/F89E3C9B-58EF-4970-A2A8-08F71164296E%40gmail.com.

Re: [weewx-user] Weather station on Raspberry Pi with LTE/4G connect

[Graham Eddy]

i’m headed to gitub discussions now...

> On 4 Mar 2021, at 9:03 am, bell...@gmail.com  wrote:
> 
> Graham,
> I am still very much in the ‘idea stage’, but would be happy to chat. In 
> order to not hijack this thread we should probably start another thread or 
> start a discussion over here, 
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/discussions 
> 
> - 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/E2A8EE7E-D78C-4093-8474-AE28EEA26204%40gmail.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Graham Eddy]

or just note which /dev/ttyUSB* comes and goes

once identified i like to put in a udev rule to create a known device file such 
as /dev/vp2

> On 5 Mar 2021, at 12:33 pm, vince  wrote:
> 
> One good way to identify a USB device is to unplug it, plug it back in, and 
> see what the 'dmesg' command reported.You'll tend to be able to figure 
> out which USB port it connected to that way.

-- 
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/00A833D2-4689-4DF1-916D-5B7A88CA5EF8%40gmail.com.

Re: [weewx-user] Weather station on Raspberry Pi with LTE/4G connect

[Graham Eddy]

a driver creates the original packet with a timestamp, a service changes 
(usually adds to) the existing packet.
some modules, like gw1000, can be configured to be in either mode (i.e. 
originate packets, or augment existing packets produced by some other driver). 
i do this, with vantage as driver and gw1000 in service mode

> On 5 Mar 2021, at 10:59 pm, Christian Radermacher 
>  wrote:
> 
> In which case I user Service, in which case I use driver?

-- 
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/67FACED2-7AA0-4BA3-854B-C31E8CE79F81%40gmail.com.

Re: [weewx-user] Re: Installing Weewx on a Raspberry Pi with a Weatherlink Live

[Graham Eddy]

macos puts users under /Users, linux puts them under /home. windoze has its 
convention for users too

> On 10 Mar 2021, at 3:51 pm, troutwitted  wrote:
> 
> To specify an install location different from the default /home/weewx, modify 
> the parameter home in the setup.cfg file. Mac users will want to change it to 
> /Users/Shared/weewx.
> 
> I'm a Mac user, largely a software idiot, but it's not clear to me why I will 
> want to change the setup.cfg file to change from the default /home/weewx. Can 
> I trouble one of you to explain to me why I should do it and perhaps the 
> easiest way to modify the file, if you don't mind. Thanks very much.

-- 
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/98433D18-5C80-47C0-99E9-ADF1CAA4B9DA%40gmail.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Graham Eddy]

how much is ‘new’ and much much ‘old’? i.e. with the new envoy, are you using 
the old known-working data logger and cable?

> On 11 Mar 2021, at 2:09 pm, monmul  wrote:
> 
> New Envoy shows no response to TEST or NVER...so that one is definately dead 
> I think!

-- 
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/A6B84107-4BA1-4304-9B61-244F700591E4%40gmail.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Graham Eddy]

i do recall that davis introduced an incompatability between old firmware and 
new datalogger but i don’t recall the details. i’m sure a search of the forum 
archive would see if that was relevant

> On 11 Mar 2021, at 2:17 pm, monmul  wrote:
> 
> Yes I am using the original data logger and cable that came with the old 
> EnvoyI take out the data logger from he old one and put it in the new 
> one...I suspect that the data logger may not be compatible with the new Envoy

-- 
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/A4FF1391-8844-4E16-8B1D-C2F6C6F06A3B%40gmail.com.

Re: [weewx-user] Re: Database merge?

[Graham Eddy]

no lines removed or added i.e. line 153 still in situ?

i seem to recall configobj has difficulties with empty stanza and more so with 
trailing comment lines. probably worth a try ensuring neither of those in the 
file e.g. leave enable=false uncommented

> On 18 Mar 2021, at 10:19 am, PJO  wrote:
> 
> This (attached) is the file with passwords, ids and coordinates removed.  
> 
> Here's what I did:
> 
> I stopped weewx on both RPis; copied the database to the new one, having 
> backed up the database there, and then swapped in a copy of my weewx.conf 
> with the uploads to wunderground etc. enabled. When that didn't work I went 
> through and disabled all those. I did check both the weewx.conf files 
> carefully using a split screen file comparison utility and didn't see 
> anything wrong. I then went through and disabled the uploads, as shown here. 
> I reverted to the original database and previous weewx.conf--and weewx ran 
> again, so I assumed the problem was something in the database/configuration. 
> 
> If you can see anything wrong at line 153 I'll be interested to know what it 
> is! And many thanks, of course, for looking.
> 
> On Wednesday, March 17, 2021 at 8:37:37 PM UTC tke...@gmail.com wrote:
> You likely have a typo in weewx.conf but without seeing yours it's impossible 
> to know where.   
> 
> In this case, we do know where: line 153 in weewx.conf.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/451deb4d-665a-40fc-ad2b-f1a801bdc7e7n%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/1AE2B36D-D53D-4C7D-9088-87627D11B3D1%40gmail.com.

Re: [weewx-user] MQTT for Belchertown skin

[Graham Eddy]

what’s not working?

> On 28 Mar 2021, at 12:33 am, Tom Hackett  wrote:
> 
> I just can't figure this out.

-- 
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/7A79B922-E098-48AE-A46C-3A128A3F9D90%40gmail.com.

Re: [weewx-user] Re: Vantage Pro data logger corruption - Daylight Saving Time?

[Graham Eddy]

i have never seen this problem viz having to clear logger memory to fix DST 
transition. heck, i have never had to clear logger memory

> On 29 Mar 2021, at 12:32 am, John Kline  wrote:
> 
> The issue being reported here sounds different.  Are you guys saying you 
> *always* have this problem going in and out of DST?  Do you have the correct 
> DST setting in the console?  Even when I encountered the issue above, I 
> didn’t have to clear memory in my logger.  Tom, do you see this issue?  Do 
> you have to clear memory in your logger every six months?

-- 
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/64199516-3F67-4EFF-BFF0-3C43122A8EBF%40gmail.com.

Re: [weewx-user] Re: Vantage Pro data logger corruption - Daylight Saving Time?

[Graham Eddy]

so *that* was what the upgrade was. they would only rent us that device (don’t 
recall how much but it was a lot) and couldn’t say what it did. as you would 
expect, i refused. glad i did: the change was not even relevant to my country. 
and the vp2 has ticked quite nicely since, without the update

> On 29 Mar 2021, at 3:19 am, wfs...@gmail.com  wrote:
> 
> I have an original Vantage Pro (VP1) with a serial to USB converter cable 
> attached to a RPi and Weewx does not crash at time changes.  To update the VP 
> firmware for the 2007 DST rule change, Davis had to loan you a special piece 
> of hardware to install the update, and it is indicated at VP console reboot 
> as REV B.  After you patched your firmware, you returned the device to Davis.

-- 
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/C05ED71B-B63B-4B20-9620-5617BF86464D%40gmail.com.

[weewx-user] 'systemctl stop' sends SIGKILL not SIGTERM on RPi

[Graham Eddy]

using the provided weewx.service on an RPi, ‘sudo systemctl stop weewx’ sends 
SIGKILL instantly (twice), which is a very unclean termination of weewx and 
causes me problems. has anyone encountered this and has a proper fix?

so far as i can tell from the manuals (particularly ‘systemd.kill' and 
‘systemd.service’), this is defective behaviour by systemd - it should send a 
SIGTERM followed by a SIGKILL (if necessary) 90 secs later by default. instead, 
i can only stop it sending SIGKILL by setting ‘FinalKillSignal=SIGTERM’ in 
weewx.service, where systemd sends SIGTERM twice instead. ‘KillSignal=SIGTERM’ 
is ignored

my workaround is ‘SendSIGKILL=no’ in weewx.service, which nicely sends SIGTERM 
for clean shutdown, but there is no followup SIGwhatever for contingent 
termination of rogue process(es)

weewx.service with workaround is:
# systemd configuration for weewx

[Unit]
Description=weewx weather system
Requires=time-sync.target
After=time-sync.target
RequiresMountsFor=/home

[Service]
ExecStart=/home/weewx/bin/weewxd --daemon --pidfile=/run/weewx/weewx.pid 
/home/weewx/weewx.conf
ExecReload=/bin/kill -HUP $MAINPID
Type=forking
PIDFile=/run/weewx/weewx.pid
User=weewx
Group=weewx
SendSIGKILL=no  # workaround to stop SIGKILL sent instantly (systemd bug)

[Install]
WantedBy=multi-user.target

-- 
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/57F87F51-50BC-4359-A437-F8CDEF455BB3%40gmail.com.

Re: [weewx-user] 'systemctl stop' sends SIGKILL not SIGTERM on RPi

[Graham Eddy]

some of my services do have state that i need to save on termination, so it is 
important to me

> On 3 Apr 2021, at 1:42 am, Tom Keffer  wrote:
> 
> SIGKILL is unclean behavior, but it should not cause any harm. The only state 
> worth worrying about is the database and, there, all writes are done as 
> transactions

-- 
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/27D58FC6-07A2-49A3-981D-CE55301D974C%40gmail.com.

Re: [weewx-user] Weewx-envoy driver

[Graham Eddy]

a quick peek at the code indicates it is python2-only (the exception handling 
is the giveaway)

> On 5 Apr 2021, at 7:53 am, weather list  wrote:
> 
> Does anyone have this  running? 
> Installed it on my WeeWx install and it appears in the wee_extension —list 
> results but does not show up if I do a wee_config —reconfigure, even when I 
> open a new terminal session.
> 
> Intel NUC
> Debian 10 (Raspian Desktop)
> WeeWx install Python3
> WeeWx 4.4.0

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/D0EDE5E8-9D22-4375-B73E-76F66FBA87D5%40gmail.com.

Re: [weewx-user] WeeWX-MQTTSubscribe - use of - sanity check

[Graham Eddy]

i am nearly finished doing something similar, except
  (1) i position weewx as the manager of the wx hardware via station-specific 
interface - weewx is the app that encapsulates the wx and provides its data as 
mqtt to the world (unless the wx is natively mqtt). e.g. the vantage driver is 
solid.
  (2) i also position weewx as manager of an abstract weather station that 
receives its observations from many sources - and i have chosen mqtt as the 
common messaging medium i.e. lots of little IoT devices provide data to weewx 
via mqtt. this is a different role from (1), and i know some weewx users stream 
to data consolidaters that can provide this abstraction instead.
  (3) i wrote my own bi-directional mqtt gateway, for use in all my mqtt apps 
(the paho client leaves a lot ’to the reader’ to implement in a production 
environment so needs a whole software layer above it). most of my former data 
services have been migrated to separate apps that talk to weewx via mqtt. (some 
of my weewx data services manipulate data within weewx so are not 
externalised.) i have a weewx data service built on the bi-directional gateway 
as the interface between weewx and mqtt world.

i expect there is a lot of overlap with the excellent MQTTSubscribe. but my 
requirement was for a generic gateway outside of weewx, and the weewx interface 
is just one of the apps built on it

> On 9 Apr 2021, at 5:47 am, Colin Larsen  wrote:
> 
> I'm thinking about rewriting my current weather station code to solely use 
> MQTT to deliver data to 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/8BAB1C3E-DE3C-4D57-84FA-6B6AFBD0326C%40gmail.com.

Re: [weewx-user] WH57(lighning detection) and GW1000 send daily summary on every records

[Graham Eddy]

post your gw1000 config especially map. suspect you are accumulating an 
already-accumulated count

> On 11 Apr 2021, at 7:12 am, Johann Destombes  wrote:
> 
> The GW1000 show 5 lightnings, this number is ok on the WS View apps and on 
> ecowitt.net  but it's now more than 1000 on weewx 
> database

-- 
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/18062C14-9FBE-428E-99F0-967814247E62%40gmail.com.

Re: [weewx-user] Version 4.5.0 released

[Graham Eddy]

4.5.1 updated cleanly here (from 4.4.0 using setup.py on current RPi OS)

i ran into the as_value_tuple() API change, as documented - minor fix to change 
my services (added ‘except KeyError’ to ‘vt[0] is None’ test)

-- 
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/8A079FD8-CC44-4489-B87E-31FDFBAC8CF3%40gmail.com.

[weewx-user] set 'group_time' to 'unix_epoch_ms' causes crash in weewx.almanac

[Graham Eddy]

my upgrade from 4.4.0 to 4.5.1 was not as clean as i indicated earlier. it 
crashed on test system every time it tried to generate reports but i fixed 
that, and production system update was clean. so, reporting the error:

cheetah crashed apparently inside weewx.almanac, so i inserted a print() - 
logging not being used in weewx.almanac - the line before the apparent error on 
line 370:

# Calculate and store the start-of-day in Dublin Julian Days. 
#self.sod_djd = 
timestamp_to_djd(weeutil.weeutil.startOfDay(self.time_ts))
print(f"self.time_ts={self.time_ts}")
(y,m,d) = time.localtime(self.time_ts)[0:3]
self.sod_djd = timestamp_to_djd(time.mktime((y,m,d,0,0,0,0,0,-1)))

i ran it in foreground to get output, it crashed as usual, see log extract:

Apr 11 23:05:17 stringybark weewx[15861] INFO weewx.manager: Added record 
2021-04-11 23:05:00 AEST (1618146300) to database 'weewx.sdb'
Apr 11 23:05:17 stringybark weewx[15861] INFO weewx.manager: Added record 
2021-04-11 23:05:00 AEST (1618146300) to daily summary in 'weewx.sdb'
Apr 11 23:05:17 stringybark weewx[15861] DEBUG user.forecast: MainThread: OWM: 
not yet time to do the forecast
Apr 11 23:05:17 stringybark weewx[15861] DEBUG weewx.reportengine: Running 
reports for latest time in the database.
Apr 11 23:05:17 stringybark weewx[15861] DEBUG weewx.reportengine: Running 
report 'GEReport'
Apr 11 23:05:17 stringybark weewx[15861] DEBUG weewx.reportengine: Found 
configuration file /home/weewx/skins/GE/skin.conf for report 'GEReport'
Apr 11 23:05:17 stringybark weewx[15861] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.JSONHelpers', 
'user.since.Since', 'user.forecast.ForecastVariables']
Apr 11 23:05:17 stringybark weewx[15861] DEBUG weewx.manager: Daily summary 
version is 4.0
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator: Generate 
failed with exception ''
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator:  
Ignoring template /home/weewx/skins/GE/forecast-frag.html.tmpl
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator:  
Reason: timestamp out of range for platform time_t
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator:   
Traceback (most recent call last):
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator: 
File "/home/weewx/bin/weewx/cheetahgenerator.py", line 326, in generate
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator:  
 unicode_string = compiled_template.respond()
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator: 
File "_home_weewx_skins_GE_forecast_frag_html_tmpl.py", line 94, in respond
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator: 
File "/usr/local/lib/python3.7/dist-packages/Cheetah/Template.py", line 1708, 
in _handleCheetahInclude
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator:  
 self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator: 
File "_home_weewx_skins_GE_forecast_strip_inc.py", line 952, in respond
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator: 
File "/home/weewx/bin/weewx/almanac.py", line 267, in sunrise
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator:  
 return self.sun.rise if self.hasExtras else self._sunrise
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator: 
File "/home/weewx/bin/weewx/almanac.py", line 343, in __getattr__
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator:  
 return AlmanacBinder(self, attr)
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator: 
File "/home/weewx/bin/weewx/almanac.py", line 371, in __init__
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator:  
 (y,m,d) = time.localtime(self.time_ts)[0:3]
Apr 11 23:05:29 stringybark weewx[15861] ERROR weewx.cheetahgenerator:   
OverflowError: timestamp out of range for platform time_t
Apr 11 23:05:30 stringybark weewx[15861] INFO weewx.cheetahgenerator: Generated 
12 files for report GEReport in 12.83 seconds

and here is stdout from running it 

self.time_ts=1618146328
LOOP:   2021-04-11 23:05:28 AEST (1618146328) altimeter: 32.04764416490144, 
altInHumidity: 29.99981453133538, altInTemp: 63.9273433231, altOutHumidity: 
79.99986089817905, altOutTemp: 32.74071750761992, altPressure: 
31.05363272637, altRain: 0, altWindDir: 359.9991653890743, altWindGust: 
11.7217963581, altWindGustDir: 359.9991653890743, altWindSpeed: 
9.76816363175, appTemp: 28.239945905002337, b

Re: [weewx-user] Re: set 'group_time' to 'unix_epoch_ms' causes crash in weewx.almanac

[Graham Eddy]

i am using https://github.com/chaunceygardiner/weewx-forecast v.b12, which, as 
you say, calls almanac

i think i understand. deep in weewx (call it weewx ‘kernel’), monotonic time is 
a fundamental always measured in time_t. in the upper levels of weewx, in the 
world of weewx units, time is an observable property with transformable units. 
almanac is really part of the ‘kernel’, which works in time_t only, so any time 
values from the units space must be converted to time_t before being presented 
to almanac i.e. it is actually a bug in forecast, in this case [and might imply 
some tweaking needed in the almanac interface within cheetah]

> On 13 Apr 2021, at 1:52 pm, gjr80  wrote:
> 
> To understand why you are seeing this behaviour you need to understand how 
> Almanac objects are created and how they are created within a Cheetah 
> template/WeeWX report. 
> 
> An Almanac object needs, among other things, a unix epoch timestamp when it 
> is created. If the Almanac constructor does not include a timestamp the 
> current system time is used. The key point here is that the timestamp is a 
> unix epoch timestamp, ie seconds since midnight GMT/UTC 1 January 1970. When 
> you use an $almanac.xxx tag in a CheetahGenerator template the 
> CheetahGenerator obtains an Almanac object (to provide all of the 
> $almanac.xxx tags) and uses the report generator timestamp (a unix epoch 
> timestamp) to initialise the underlying Almanac object. You have not shown us 
> the code in your GE skin, but for the purposes of the exercise I will assume 
> it is similar to some of the existing forecast extension and clones code. The 
> forecast variable available in the forecast skin has an almanac property 
> (which works just like the $almanac tag) that can be used to obtain various 
> tags, commonly sun/moon rise/set etc. The forecast extension also operates 
> across a number of days and almanac properties for each day are obtained by 
> initialising the almanac with a timestamp for each day (period), for example 
> (my indentation):
> 
> #for $period in $periods 
>#set $img = '' 
>#set $alm = $forecast.almanac(ts=$period.event_ts.raw+10) 
>#if $alm.hasExtras 
>  #set $moonrise_ts = $alm.moon.rise.raw #set $moonset_ts = 
> $alm.moon.set.raw
> 
> Here the almanac is initialised not with the current epoch timestamp or 
> generator timestamp but with a tag ($period.event_ts.raw) that is going to be 
> in the group_time units that apply to the skin. When group_time is set to 
> unix_epoch you get seconds since epoch, if you use unix_epoch_ms you get 
> milliseconds since unix epoch or 1000 time the former. This is what causes 
> the overflow and this is why changing group_time causes the error to 
> appear/disappear.
> 
> Is it a bug, maybe, but I don't think it is. class Almanac needs a timestamp, 
> the class says it needs to be initialised with a unix epoch timestamp but 
> that is not what it is being given. If you ask WeeWX to convert degree C to 
> hPa is it a bug if WeeWX throws an error?
> 
> Solutions? class Almanac could be made handle a timestamp in unix epoch 
> seconds or milliseconds as it is generally pretty easy to tell the 
> difference, though not for all date-times. Not sure on Tom's view on that 
> though, does feel a little hackish to me. Alternatively, templates/SLEs etc 
> could just force any timestamps being passed to $almanac() (or in this case 
> $forecast.almanac()) be be in unix_epoch seconds, just like we force units in 
> some formulae to degree C or m/s etc. So in this case something like 
> (untested):
> 
> #for $period in $periods 
>#set $img = '' 
>#set $alm = $forecast.almanac(ts=$period.event_ts.unix_epoch.raw+10) 
>#if $alm.hasExtras 
>  #set $moonrise_ts = $alm.moon.rise.raw #set $moonset_ts = 
> $alm.moon.set.raw
> 
> should work.
> 
> 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/8BCD6A36-D6CF-4B41-B41F-455CD75C7025%40gmail.com.

Re: [weewx-user] Re: weewx.cheetahgenerator debug

[Graham Eddy]

it would be really helpful if the temporary file created by cheetah was not 
deleted when an error occurred

> On 17 Apr 2021, at 2:32 pm, gjr80  wrote:
> 
> Unfortunately sometimes Cheetah gives only limited info and often the best 
> you can do is try to deduce from the error message where or what the error 
> is. As you have no doubt found you cannot use the line number referred to in 
> the error trace, that is a line number in temporary file created by Cheetah 
> and we don't have access to that file.

-- 
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/F90C894F-4EA5-49DD-B3A5-D5F091010060%40gmail.com.

Re: [weewx-user] Database Disk Image Is malformed

[Graham Eddy]

two RPi’s report db failure 10 mins apart. i assume they are SD-based. SD cards 
are notoriously susceptible to power spikes → must have USB/power conditioning. 
or you’ve been incredibly unlucky and near-simultaneous failure is coincidence

> On 17 Apr 2021, at 10:22 pm, Tom Keffer  wrote:
> 
> I have two RaspPi's  running weewx seperatly with there own console from the 
> same the weather station. 
> At 8.40 on one and 08.50 on the other they both failed with the same thing 
> Database Disk Image is malformed. Both have been running for a long time 
> without problems.

-- 
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/E14FE251-F936-4800-9CF3-E45FEF6F9AF1%40gmail.com.

Re: [weewx-user] Re: Wewx is not rebooted with the system

[Graham Eddy]

nothing relevant shown in the tiny extract of the very long syslog…
post a copy of your .service file and the systemctl commands you have used

> On 17 Apr 2021, at 10:52 pm, P C  wrote:
> 
> Sorry, I do not see how we can put this service on the way.
> Thank you for help
> 
> log after reboot «
> pi@pi:~ $ sudo tail -f /var/log/syslog | tee /var/tmp/SysLog
> Apr 17 14:12:33 pi dbus-daemon[352]: [system] Activating via systemd: service 

-- 
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/7624D4DA-FF83-446D-A3A1-3FF9C6F449A4%40gmail.com.

Re: [weewx-user] Re: Wewx is not rebooted with the system

[Graham Eddy]

see weewx util/systemd/weewx.service for an example config file. you will copy 
this to /etc/systemd/system/.
see online manual systemd.unit(5) to understand its content (you are unlikely 
to need to change the file)

see online manual systemctl(1) for the commands to start/stop weewx service, 
once configured as above.
the key command are
  # systemctl [start | stop | enable | status] weewx

(after copying file into /etc/systemd/…, you should run
  # systemctl daemon-reload
to ensure systemd realises it has been updated)

> On 17 Apr 2021, at 11:57 pm, P C  wrote:
> 
> This is that not know what to set as a parameter for the systemctl command. 

-- 
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/18E4A7FE-C7C9-45DD-A28B-30E770F2AF49%40gmail.com.

Re: [weewx-user] Re: Wewx is not rebooted with the system

[Graham Eddy]

change the weewx.service file to point to your weewxd executable.
when you use someone else’s configuartion file, you must always check that it 
matches your own system configuration and requirements

> On 18 Apr 2021, at 5:13 pm, P C  wrote:
> 
> /home/weewx/bin/weewxd: No such file or directory

-- 
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/A0577C96-BE0F-4125-8CF7-D8725C10961C%40gmail.com.

Re: [weewx-user] Adding a new type to an SQLite DB

[Graham Eddy]

and —config takes a weewx.conf (not a weewx.sdb) as its arg

> On 20 Apr 2021, at 5:57 am, vince  wrote:
> 
> Your weewx is too old.  You need to update to 4.5.0 or later according to the 
> release notes at https://github.com/weewx/weewx/releases 
> 
> 
> 
> On Monday, April 19, 2021 at 11:38:54 AM UTC-7 weatherl...@gmail.com 
>  wrote:
> I am asking just that but I can’t see how —binding might work
> 
> When I installed the Envoy drive, it still uses wx_binding when in creates 
> envoy.sdb
> 
> So I tried:
> 
> In /home/weewx:
> 
> sudo bin/wee_database --add-column=energy_total --config=archive/envoy.sdb
> 
> And it throws an error:
> 
> wee_database: error: no such option: --add-column

-- 
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/AC231192-0869-449D-9CE3-C6319BDB1659%40gmail.com.

[weewx-user] gw1000 - wh41 wh57 battery values

[Graham Eddy]

i have been tracking battery and signal values for 36 hours for my various 
sensors hanging off a gw1000.
for wh41 and wh57 i expected to see values 0-5, but i have see other values.
wh41 has shown 15 quite often. wh57 has shown 255 once.
15 and 255 look suspiciously like bit masks.

i should add that both my wh41s reset themselves often (irregularly) for no 
apparent reason, and have done so since their first day.
the 15 value might reflect a period of wh41 insanity. should they behave this 
way?
maybe the 255 value from wh57 was just a bloop to be filtered out by QA

can someone explain what i am seeing for wh41 and wh57 values?

-- 
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/4204E979-8B64-4D84-9F20-130E5356C9AA%40gmail.com.

Re: [weewx-user] Re: gw1000 - wh41 wh57 battery values

[Graham Eddy]

an extract from test system - RPi with gw1000 as driver

> On 21 Apr 2021, at 6:30 pm, gjr80  wrote:
> 
> Either way post the logged data here and I can decode what the driver was 
> receiving.

—logged config—
Apr 21 21:33:09 stringybark weewx-gw1000[341] DEBUG __main__: Initializing 
engine
Apr 21 21:33:09 stringybark weewx-gw1000[341] INFO weewx.engine: Loading 
station type GW1000 (user.gw1000)
Apr 21 21:33:09 stringybark weewx-gw1000[341] DEBUG user.gw1000: Sending packet 
'FF FF 26 03 29' to '192.168.37.53:45000'
Apr 21 21:33:09 stringybark weewx-gw1000[341] DEBUG user.gw1000: Received 
response 'FF FF 26 09 50 02 91 46 AE 7E 84'
Apr 21 21:33:09 stringybark weewx-gw1000[341] DEBUG user.gw1000: Sending packet 
'FF FF 30 03 33' to '192.168.37.53:45000'
Apr 21 21:33:09 stringybark weewx-gw1000[341] DEBUG user.gw1000: Received 
response 'FF FF 30 0B 00 01 60 80 9A 14 62 01 2D'
Apr 21 21:33:09 stringybark weewx-gw1000[341] INFO user.gw1000: field map is 
{'co2': 'co2', 'dateTime': 'datetime', 'daymaxwind': 'daymaxwind', 'dayRain': 
'rainday', 'dewpoint': 'dewpoint', 'extraHumid1': 'humid1', 'extraHumid2': 
'humid2', 'extraHumid3': 'humid3', 'extraHumid4': 'humid4', 'extraHumid5': 
'humid5', 'extraHumid6': 'humid6', 'extraHumid7': 'humid7', 'extraHumid8': 
'humid8', 'extraHumid17': 'humid17', 'extraTemp1': 'temp1', 'extraTemp2': 
'temp2', 'extraTemp3': 'temp3', 'extraTemp4': 'temp4', 'extraTemp5': 'temp5', 
'extraTemp6': 'temp6', 'extraTemp7': 'temp7', 'extraTemp8': 'temp8', 
'extraTemp9': 'temp9', 'extraTemp10': 'temp10', 'extraTemp11': 'temp11', 
'extraTemp12': 'temp12', 'extraTemp13': 'temp13', 'extraTemp14': 'temp14', 
'extraTemp15': 'temp15', 'extraTemp16': 'temp16', 'extraTemp17': 'temp17', 
'heatindex': 'heatindex', 'hourRain': 'rainhour', 'IGN_co2_24h_avg': 
'co2_24h_avg', 'IGN_pm2_51_24h_avg': 'pm251_24h_avg', 'IGN_pm2_52_24h_avg': 
'pm252_24h_avg', 'IGN_pm2_53_24h_avg': 'pm253_24h_avg', 'IGN_pm2_54_24h_avg': 
'pm254_24h_avg', 'IGN_pm2_55_24h_avg': 'pm255_24h_avg', 'IGN_pm10_24h_avg': 
'pm10_24h_avg', 'inHumidity': 'inhumid', 'inTemp': 'intemp', 'leafWet1': 
'leafwet1', 'leafWet2': 'leafwet2', 'leafWet3': 'leafwet3', 'leafWet4': 
'leafwet4', 'leafWet5': 'leafwet5', 'leafWet6': 'leafwet6', 'leafWet7': 
'leafwet7', 'leafWet8': 'leafwet8', 'leak1': 'leak1', 'leak2': 'leak2', 
'leak3': 'leak3', 'leak4': 'leak4', 'lightning_distance': 'lightningdist', 
'lightning_last_det_time': 'lightningdettime', 'lightning_strike_count': 
'lightning_strike_count', 'lightningcount': 'lightningcount', 'luminosity': 
'light', 'monthRain': 'rainmonth', 'outHumidity': 'outhumid', 'outTemp': 
'outtemp', 'pm2_5': 'pm251', 'pm2_52': 'pm252', 'pm2_53': 'pm253', 'pm2_54': 
'pm254', 'pm2_55': 'pm255', 'pm10': 'pm10', ‘pressure’truncated on screen
Apr 21 21:33:09 stringybark weewx-gw1000[341] INFO user.gw1000: driver version 
is 0.3.0
Apr 21 21:33:09 stringybark weewx-gw1000[341] INFO user.gw1000: GW1000 address 
is 192.168.37.53:45000
Apr 21 21:33:09 stringybark weewx-gw1000[341] INFO user.gw1000: poll interval 
is 20 seconds
Apr 21 21:33:09 stringybark weewx-gw1000[341] DEBUG user.gw1000: max tries is 
3, retry wait time is 10 seconds
Apr 21 21:33:09 stringybark weewx-gw1000[341] DEBUG user.gw1000: broadcast 
address is b'255.255.255.255':46000, socket timeout is 2 seconds


—logged packets——
Apr 21 22:01:45 stringybark weewx-gw1000[341] DEBUG user.gw1000: Received 
response 'FF FF 27 00 67 01 00 F6 06 23 08 26 8C 09 26 8C 02 00 34 07 63 0A 00 
AD 0B 00 00 0C 00 05 15 00 00 00 00 16 00 00 17 00 2A 00 1E 4D 00 1E 2C 32 2E 
17 4C 04 00 00 00 05 FF A0 FF F4 FF FF FF FF FF FF FF 62 00 00 00 00 61 FF FF 
FF FF 60 FF 19 00 0C 0E 00 00 10 00 02 11 00 9D 12 00 00 00 9D 13 00 00 09 B6 
0D 00 00 AD'
Apr 21 22:01:45 stringybark weewx-gw1000[341] DEBUG user.gw1000: sensor data is 
'01 00 F6 06 23 08 26 8C 09 26 8C 02 00 34 07 63 0A 00 AD 0B 00 00 0C 00 05 15 
00 00 00 00 16 00 00 17 00 2A 00 1E 4D 00 1E 2C 32 2E 17 4C 04 00 00 00 05 FF 
A0 FF F4 FF FF FF FF FF FF FF 62 00 00 00 00 61 FF FF FF FF 60 FF 19 00 0C 0E 
00 00 10 00 02 11 00 9D 12 00 00 00 9D 13 00 00 09 B6 0D 00 00'
Apr 21 22:01:45 stringybark weewx-gw1000[341] DEBUG user.gw1000: Parsed data: 
{'intemp': 24.6, 'inhumid': 35, 'absbarometer': 986.8, 'relbarometer': 986.8, 
'outtemp': 5.2, 'outhumid': 99, 'winddir': 173, 'windspeed': 0.0, 'gustspeed': 
0.5, 'light': 0.0, 'uv': 0.0, 'uvi': 0, 'pm251': 3.0, 'pm251_24h_avg': 3.0, 
'soilmoist1': 50, 'soilmoist2': 23, 'lightningcount': 0, 'lightningdettime': 
None, 'lightningdist': None, 'daymaxwind': 1.2, 'rainrate': 0.0, 'rainday': 
0.2, 'rainweek': 15.7, 'rainmonth': 15.7, 'rainyear': 248.6, 'rainevent': 0.0, 
'datetime': 1619006505}
Apr 21 22:01:45 stringybark weewx-gw1000[341] DEBUG user.gw1000: Sending packet 
'FF FF 3C 03 3F' to '192.168.37.53:45000’
Apr 21 22:01:45 stringybark weewx-gw1000[341] DEBUG user.gw1000: Received 
response 'FF FF 3C 01 15 00 FF FF FF FF 00 00 01 FF FF FF FF FF 00 02

Re: [weewx-user] Re: gw1000 - wh41 wh57 battery values

[Graham Eddy]

this reminds me strongly of windDir value when windSpeed==0

> On 22 Apr 2021, at 3:46 pm, gjr80  wrote:
> 
> Sensor signal level 0 is a valid signal level so we cannot just omit a sensor 
> entirely just because the GW1000 reports signal level = 0. At the same time 
> we know that the battery state data is at best unreliable, and in some cases 
> plain invalid, so I am happy for the driver to ignore battery state in such 
> cases.

-- 
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/18CB66F0-1B84-454A-97C8-5FCB27D1B993%40gmail.com.

Re: [weewx-user] gw1000 - wh41 wh57 battery values

[Graham Eddy]

even after only a few hours it is obvious that it has cleaned up the battery 
status data

the following graphs show before and after new gw1000.py at 12pm:





as to why the sensor packet loss is so high, that is something else for me to 
investigate (none are more than 10m from receiver). is this level of loss 
normal for gw1000?

> On 22 Apr 2021, at 5:55 pm, Graham Eddy  wrote:
> 
> this reminds me strongly of windDir value when windSpeed==0
> 
>> On 22 Apr 2021, at 3:46 pm, gjr80 > <mailto:gjroder...@gmail.com>> wrote:
>> 
>> Sensor signal level 0 is a valid signal level so we cannot just omit a 
>> sensor entirely just because the GW1000 reports signal level = 0. At the 
>> same time we know that the battery state data is at best unreliable, and in 
>> some cases plain invalid, so I am happy for the driver to ignore battery 
>> state in such cases.
> 

-- 
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/A95B179D-FBCC-4DEC-BF60-982AB19E9895%40gmail.com.

[weewx-user] data_binding in 'for' ?

[Graham Eddy]

where in the following should i place ‘($data_binding=vp2_binding)’ ?
note that other tags within the #for scope need to have a different data_binding

#for $day in $month.days
#if $day.outTemp.count.raw

-- 
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/2BBAD130-5F2A-46DB-BFD4-6A806B0BC153%40gmail.com.

Re: [weewx-user] Re: new weewx install not creating database or webpage

[Graham Eddy]

… and wait 5 minutes for the first report i.e. for index.html to be created. 
see whether logfile reports errors generating it

> On 27 Apr 2021, at 12:42 pm, p q  wrote:
> 
> Where does the log file say the files are being copied to?
> Where does weewx.conf have for  HTML_ROOT ?
> 
> On Mon, Apr 26, 2021 at 7:35 PM Eric Koester  > wrote:
> I removed the init.d related files and copied the systemd files as you 
> demonstrated.
> I can see the signs of it working:
> - the pid file '/var/run/weewx.pid' exists
> - after running this command 'sudo tail -f /var/log/syslog' I see weather 
> station data being recieved every 10 seconds
> - the database file /home/weewx/archive/weewx.sdb got accessed when I entered 
> 'sudo systemctl start weewx'
> 
> However, there is still no index.html file in the /home/weewx/public_html 
> directory.
> 
> What other files and processes should I be seeing?

-- 
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/76D0A4F1-E1A6-4BA3-8DD9-EE4DFDC5A1BF%40gmail.com.

Re: [weewx-user] Using weewx-vitalstats & graphing data from data-services

[Graham Eddy]

> Using this service as an example: https://github.com/g-eddy/weewx-vitalstats. 
> How can I get the data from that into something graphable by the Belchertown 
> skin?

you will be creating new data_types(s). i don’t know belchertown; use its 
method to add new items to template files

> Is it necessary to add a database column if I want these graphed over time?

yes, that is how weewx works: graphed over time → stored as column in database

> Can they be shown as current values somehow without needing to store them? 
> (and then I presume I would not be able to graph them)

again yes. $current refers to the current (archive) data packet, just as it is 
being put into the database (that is, the data_types in the packet that have 
columns get stored). if you put $current.outTemp in a template, that is taking 
from the packet, no column required

> Adding the graph like this results in a error "weewx.UnknownType: cpu_temp”

this is a new data_type so weewx as yet knows nothing about it. creating a 
column for it only persists it in database, it doesn’t tell weewx what it is 
(e.g. what units does it use)

> I've created my own services for a couple of raspberry pi sensors, but I just 
> store info in database names that already exist eg "event.packet['pressure'] 
> = 0.02953 * float(pressure)" and the data is then easily used in a 
> Belchertown graph..

quite valid thing to do - you are hijacking weewx’s knowledge of existing 
data_types to use for your own variables

the Customisation Manual goes into this in great detail; you will get your 
answer there.
a partial answer is to say you need to add a definition to your 
bin/user/extensions.py, such as
weewx.units.obs_group_dict['cpu_temp'] = 'group_temperature'
which tells weewx that ‘cpu_temp’ is a temperature thingy so degree_C and 
degree_F are the kind of units to use for 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/DE233099-3842-4A1F-9892-77AC9A0F697E%40gmail.com.

Re: [weewx-user] Extract station data for use in script...

[Graham Eddy]

you can easily create a template just like wview’s parameterlist.htm.
look at the NOAA templates as a related example.
weewx 4.5 has introduced json as generated values format (i haven’t tried them 
yet) which should suit you perfectly

> On 28 Apr 2021, at 5:33 pm, bus...@gmail.com  wrote:
> 
> 
> Hi,
> I wonder if weewx has some file or methods where I can easily read the last 
> weather station data from with php or perl.  The good ol' WeatherView had its 
> parameterlist.htm file where all raw data from the station were saved at each 
> poll.  
> 
> Does weewx have something like this too, or do I have to retrieve it from the 
> database?
> 
> Does it exist examples of this..?
> 
> best regards
> Tor
> 
> -- 
> 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/ed636472-eec0-45e1-bc8d-ac40e630e98cn%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/3340B97B-A081-4792-9A04-F3E5245233B8%40gmail.com.

[weewx-user] rebuild-daily fails

[Graham Eddy]

rebuilding daily summary on weewx database is not working, hopefully someone 
can help

in the leadup to this,
* i copied producton weewx.sdb to dev/test (different host) weewx-gw1000.sdb,
* in which i dropped lots of columns and renamed others (using wee_database 
—drop-columns and —rename-column respectively)
* then i dropped daily summaries (using wee_database —drop-daily).
* when i try to rebuild daily summaries (using wee_database —rebuild-daily), it 
reports a failure that a daily table already (still) exists - this table 
corresponds to a column that i did *not* alter

before doing —drop-daily i also deleted the content of a number of columns 
(obviously not the dropped ones) using sql clause of form ‘update table set 
altimeter = NULL, heatindex = NULL;’, preparatory to doing a —calc-missing 
after some new values were to be loaded into core columns such as outTemp and 
outHumidity

(presumably i can do an sql dump of archive table and reload to new db instance 
and go forward with that, but i should work through this in case there is an 
underlying weewx problem)

weewx-gw1000.conf points to weewx-gw1000.sdb

i am running another instance of weewx on the test system, from weewx-iwx.conf, 
which points to weewx-iwx.sdb, obviously doing other things

details of commands and log follow

weewx@stringybark:~ $ wee_database --config=weewx-gw1000.conf --drop-daily
Using configuration file weewx-gw1000.conf
Using database binding 'wx_binding', which is bound to database 'archive_sqlite'
Proceeding will delete all your daily summaries from database 'weewx-gw1000.sdb'
Are you sure you want to proceed (y/n)? y
Dropping daily summary tables from 'weewx-gw1000.sdb' ... 
No daily summaries found in database 'weewx-gw1000.sdb'. Nothing done.
weewx@stringybark:~ $ wee_database --config=weewx-gw1000.conf --rebuild-daily
Using configuration file weewx-gw1000.conf
Using database binding 'wx_binding', which is bound to database 'archive_sqlite'
All daily summaries will be rebuilt.
Proceed (y/n)? y
Traceback (most recent call last):
  File "/home/weewx/bin/weedb/sqlite.py", line 30, in guarded_fn
return fn(*args, **kwargs)
  File "/home/weewx/bin/weedb/sqlite.py", line 219, in execute
return sqlite3.Cursor.execute(self, *args, **kwargs)
sqlite3.OperationalError: table archive_day_lightning_strike_count already 
exists

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/weewx/bin/wee_database", line 1138, in 
main()
  File "/home/weewx/bin/wee_database", line 236, in main
rebuildDaily(config_dict, db_binding, options)
  File "/home/weewx/bin/wee_database", line 336, in rebuildDaily
db_binding, initialize=True) as dbmanager:
  File "/home/weewx/bin/weewx/manager.py", line 746, in open_manager_with_config
return open_manager(manager_dict, initialize)
  File "/home/weewx/bin/weewx/manager.py", line 734, in open_manager
manager_dict['schema'])
  File "/home/weewx/bin/weewx/manager.py", line 164, in open_with_create
dbmanager = cls(connection, table_name=table_name, schema=schema)
  File "/home/weewx/bin/weewx/manager.py", line 876, in __init__
self._initialize_day_tables(schema)
  File "/home/weewx/bin/weewx/manager.py", line 932, in _initialize_day_tables
self._initialize_day_table(obs[0], obs[1].lower(), cursor)
  File "/home/weewx/bin/weewx/manager.py", line 953, in _initialize_day_table
cursor.execute(sql_create_str)
  File "/home/weewx/bin/weedb/sqlite.py", line 40, in guarded_fn
raise weedb.TableExistsError(e)
weedb.TableExistsError: table archive_day_lightning_strike_count already exists
weewx@stringybark:~ $ sqlite3 archive/weewx-gw1000.sdb 
SQLite version 3.27.2 2019-02-25 16:06:06
Enter ".help" for usage hints.
sqlite> drop table archive_day_lightning_strike_count;
Error: no such table: archive_day_lightning_strike_count
sqlite> .tables
archive
sqlite> select * from sqlite_master;
table|archive|archive|2|CREATE TABLE archive (`dateTime` INTEGER NOT NULL 
UNIQUE PRIMARY KEY, `usUnits` INTEGER NOT NULL, `interval` INTEGER NOT NULL, 
`altimeter` REAL, `barometer` REAL, `cloudbase` REAL, `dewpoint` REAL, `ET` 
REAL, `heatindex` REAL, `lightning_distance` REAL, `lightning_strike_count` 
REAL, `lightning_last_det_time` REAL, `luminosity` REAL, `pm2_5` REAL, 
`radiation` REAL, `soilMoist1` REAL, `soilMoist2` REAL, `UV` REAL, `windchill` 
REAL, `inTemp` REAL, `outTemp` REAL, `inHumidity` REAL, `outHumidity` REAL, 
`pressure` REAL, `windDir` REAL, `windSpeed` REAL, `windGust` REAL, 
`windGustDir` REAL, `rain` REAL, `stormRain` REAL, `rainRate` REAL, `pm2_52` 
REAL, `wh40_batt` REAL, `wh41_ch1_batt` REAL, `wh41_ch2_batt` REAL, 
`wh51_ch1_batt` REAL, `wh51_ch2_batt` REAL, `wh57_batt` REAL, `ws80_batt` REAL, 
`wh40_sig` REAL, `wh41_ch1_sig` REAL, `wh41_ch2_sig` REAL, `wh51_ch1_sig` REAL, 
`wh51_ch2_sig` REAL, `wh57_sig` REAL, `ws80_sig` REAL)
index|sqlite_autoindex_archive_1|archive|4

Re: [weewx-user] Re: rebuild-daily fails

[Graham Eddy]

> You are changing so much

i am trying a different split of data between two drivers (one database into 
two), where both have data in columns in one database

> (why ?)

you don’t jump a gap in two hops

> in a seemingly random order

the sequence is logical to me: make a copy for second driver, drop the columns 
in it no longer required (belong to other driver), rename some of the remaining 
(eg altOutTemp to outTemp), recalc derived values from the new core columns 
(eg. dewpoint)

> If you just want to start over completely,

i indicated i can do so to progress, but i want to flag a potential problem in 
weewx viz. i drop-daily, demonstrate the summary tables do not exist, attempt 
rebuild-daily but it claims a summary table exists

this is using the —drop-tables and —rename-tables options new to 4.5. hopefully 
someone else has pushed them hard too and can compare results

-- 
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/76559C51-63DC-470E-9D9B-694817393CF2%40gmail.com.

Re: [weewx-user] Re: rebuild-daily fails

[Graham Eddy]

i don’t know how to reproduce it (so many changes, as vince pointed out). i was 
hoping someone had seen it before: maybe a default value going astray

it is worth a first-pass inspection, but no more than that if i can’t reproduce 
it or not seen elsewhere. summary of problem statement would be “—drop-daily 
succeeds on db but subsequent —rebuild-daily fails and reports a summary table 
already exists, but sqlite3 shows that table does not exist"

my weewx-gw1000.conf contains
[[wx_binding]]
schema = user.extensions.gw1000_schema
[[archive_sqlite]]
database_name = weewx-gw1000.sdb
obviously both schema and database have been changed → could contain errors. 
could an inconsistency between the two cause the problem?

and how could the second half of problem statement (—rebuild-daily fails and 
reports a summary table already exists, but sqlite3 shows that table does not 
exist) come about? going to the wrong database, or simply that error message 
itself is incorrect, spring to mind

> On 2 May 2021, at 10:58 am, Tom Keffer  wrote:
> 
> It's a new feature, so there may well be a problem. Unfortunately (or, maybe 
> fortunately!) I am unable to replicate it. I dropped a couple columns, 
> renamed a column, then dropped the daily summary. I then rebuilt it 
> uneventfully. 
> 
> If you can walk me through an example, maybe I can replicate your 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/13BA09CA-EEA3-44F1-927F-5C63BBF66D97%40gmail.com.

Re: [weewx-user] Re: rebuild-daily fails

[Graham Eddy]

found it: duplicate entry in user.extensions.gw1000_schema

i was under the impression that that schema was used only when the database is 
created, but that is incorrect: the schema is also used in —rebuild-daily

> On 2 May 2021, at 12:28 pm, Graham Eddy  wrote:
> 
> my weewx-gw1000.conf contains
>   [[wx_binding]]
>   schema = user.extensions.gw1000_schema
>   [[archive_sqlite]]
>   database_name = weewx-gw1000.sdb
> obviously both schema and database have been changed → could contain errors. 
> could an inconsistency between the two cause the problem?
> 
> and how could the second half of problem statement (—rebuild-daily fails and 
> reports a summary table already exists, but sqlite3 shows that table does not 
> exist) come about? going to the wrong database, or simply that error message 
> itself is incorrect, spring to mind

-- 
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/1F783EAB-63BB-4ADA-A893-E98DC2287084%40gmail.com.

Re: [weewx-user] Re: rebuild-daily fails

[Graham Eddy]

and the table ‘was not there’ because it was created within a transaction that 
was rolled back because of the error

> On 2 May 2021, at 2:23 pm, Graham Eddy  wrote:
> 
> found it: duplicate entry in user.extensions.gw1000_schema
> 
> i was under the impression that that schema was used only when the database 
> is created, but that is incorrect: the schema is also used in —rebuild-daily
> 
>> On 2 May 2021, at 12:28 pm, Graham Eddy > <mailto:graham.e...@gmail.com>> wrote:
>> 
>> my weewx-gw1000.conf contains
>>  [[wx_binding]]
>>  schema = user.extensions.gw1000_schema
>>  [[archive_sqlite]]
>>  database_name = weewx-gw1000.sdb
>> obviously both schema and database have been changed → could contain errors. 
>> could an inconsistency between the two cause the problem?
>> 
>> and how could the second half of problem statement (—rebuild-daily fails and 
>> reports a summary table already exists, but sqlite3 shows that table does 
>> not exist) come about? going to the wrong database, or simply that error 
>> message itself is incorrect, spring to mind
> 

-- 
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/82B5E6A0-DEAA-40D7-9D2D-07C3C7548540%40gmail.com.

[weewx-user] overloading gw1000?

[Graham Eddy]

every 24 hours or so recently my gw1000 has become unresponsive and required a 
power cycle.
i am not only polling it every 20 secs in production weewx instance, i am also 
polling it every 20 secs in two more test weewx instances → i think i am 
overloading it. just because the api is there doesn’t mean it can be hammered 
continuously...

-- 
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/338B7B2E-41CB-4C55-A1A2-776CFD21E57A%40gmail.com.

Re: [weewx-user] overloading gw1000?

[Graham Eddy]

i’m not sure what is being comparing to. in my case, it is one gw1000 being 
polled from three different locations independently each at 20 sec intervals

> On 9 May 2021, at 4:59 pm, Rainer Lang  wrote:
> 
> I don't think that that's a phenomenon to be generalized.
> My GW1000s (s !) are running with weewx (API) and Meteobridge (API) being 
> polled every 10 seconds without getting stuck.

-- 
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/A99D1862-D6DE-4E78-A576-F372C5F67227%40gmail.com.

Re: [weewx-user] Re: rtl_433 not found when run at boot or as service

[Graham Eddy]

you probably have, but it doesn’t hurt reminding: before even considering 
weewx, make sure you repeated *all* the installation steps for rtl433, not just 
dropped stuff in, and from a blank slate not from an earlier attempt. i have 
had to do this several times (migrating hosts), and i have made this mistake 
with rtl433 twice - leaving out a step, doesn’t work, continue build instead of 
wiping it, still won’t work

> On 12 May 2021, at 1:06 pm, 'dvdhns' via weewx-user 
>  wrote:
> 
> Not much luck.
> The symlinks sorta worked - but then I was getting errors that showed the RTL 
> was already being used, it was like it was calling it twice.
> I tried putting the full path in the command line in the SDR section of the 
> weewx.conf. That made weewx produce no errors, but nothing was being 
> collected. Yet, when I set debug in weewx.conf >0 it looked like it was 
> seeing data, but not writing it. 
> Totally confused, at this point. I started from scratch, installed weewx 
> using Python3 and had same results.
> I had this hardware setup working for 11 months - just burned out my microSD 
> card on the RPi. If only I realized it would be this hard to get things 
> working again. 

-- 
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/F49062E3-80CF-460C-91A8-CD0F6BA35508%40gmail.com.