Re: [weewx-user] Re: getting weewx[12196]: cheetahgenerator: Skipping template index.html.tmpl: cannot find start time

[Ted Frohling]

I have a single ISS, single console and wired envoy.  That is, there is a 
cable from the ISS to the envoy.  The data logger inserted in the envoy is 
connected to the Pi via a serial cable.  The console is listening to the 
ISS wirelessly.  I assumed, incorrectly, that the ISS was listening to the 
envoy since the envoy also has an antenna.  I took the logger out of the 
envoy with all the power supplies connected, waited around 30 seconds, and 
plugged it back in to the Envoy, closed the case up and inserted the 
batteries, and got a beep, then about two minutes later, plugged the Envoy 
into the DC wall transformer.   Restarted the weewx software normally (in 
daemon mode). No pages got updated and got CRC16 errors, so restarted weewx 
in software mode, and ordered a new data logger, as I'm pretty sure it's 
the problem.  If not I have a spare...

Sorry for the confusion.

ted


On Sunday, January 12, 2020 at 5:18:05 AM UTC-7, Thomas Keffer wrote:
>
> Ted, it's not clear what you are doing, nor what setup you have. Slow down 
> and describe your setup carefully.
>
> Do you have a single ISS (the gadget with the wind vane and rain bucket), 
> a single console, and a single Envoy? Which ones are wired to the ISS? You 
> say the Envoy has a wired connection to the ISS. What about the console?
>
> Just to be clear: there is no connection between consoles and Envoys. They 
> listen to the ISS independently, either through a wire, or wirelessly, 
> never to each other.
>
> Finally, you said you removed the logger from the Envoy, but you didn't 
> say whether you put it back in.
>
> -tk
>
> On Sat, Jan 11, 2020 at 4:04 PM Ted Frohling  > wrote:
>
>> I removed the data logger from the Envoy and am now getting:
>>
>> Jan 11 17:01:32 weewx weewx[23496]: vantage: Retrieving 513 page(s); 
>> starting index= 3
>> Jan 11 17:01:36 weewx weewx[23496]: vantage: get_data_with_crc16; try #1 
>> failed: Expected to read 267 chars; got 191 inst
>> ead
>> Jan 11 17:01:36 weewx weewx[23496]: vantage: Timeout in 
>> get_data_with_crc16
>> Jan 11 17:01:36 weewx weewx[23496]: vantage: Getting archive packets 
>> since 2020-01-11 16:40:00 MST (1578786000)
>> Jan 11 17:01:40 weewx weewx[23496]: vantage: Retry  #0 failed
>>
>> I would assume this indicates either a communications problem or very 
>> corrupted memory in the logger.  With the other problems, I suspect bad 
>> memory.  Am I right?
>>
>> ted
>>
>> On Saturday, January 11, 2020 at 4:39:29 PM UTC-7, Ted Frohling wrote:
>>>
>>> Missed he reference to taking the logger out and reseating.  Will do 
>>> that.  The console seems to be working well.  The system is a wired system 
>>> that connects to the envoy.  I'm assuming the console receives it's data 
>>> from the envoy via radio.
>>>
>>> ted
>>>
>>>
>>> On Saturday, January 11, 2020 at 4:20:28 AM UTC-7, Thomas Keffer wrote:

 Did you try reseating the logger?

 On Fri, Jan 10, 2020 at 6:36 PM Ted Frohling  
 wrote:

>
>
> On Friday, January 10, 2020 at 6:09:38 PM UTC-7, Ted Frohling wrote:
>>
>>
>>
>> On Friday, January 10, 2020 at 3:41:10 PM UTC-7, gjr80 wrote:
>>>
>>>
>>> On Saturday, 11 January 2020 08:15:14 UTC+10, Ted Frohling wrote:

 Reset the Vantage Pro 2 console and the Weather Envoy for good 
 measure.  Dumped the database and cleared the memory. Still have the 
 problem. The Vantage Pro 2 console is old, and the firmware is stuck 
 at 
 1.90.  Wondering if I should pitch it and get a new console.  

>>>  
>>> No need for anything drastic like that. My console is v1.90 and 
>>> works fine. I don't have an envoy though I don't believe that changes 
>>> the 
>>> process for clearing the station memory. Just checking the obvious, but 
>>> you 
>>> did stop WeeWX before running wee_device to clear the station 
>>> memory? Were there any errors returns anywhere during the process?
>>>
>>
>> No errors for either the dump or the clear command. However after 
>> doing the dump, followed by the clear, and restarting weewx, waiting, no 
>> records are being put into the database. 
>>
>>>
>>> Wondering if the following log messages are indicitive of the 
 problem:

 weewx weewx[16819]: cheetahgenerator: Skipping template 
 wind.html.tmpl: cannot find start time
 Jan 10 15:10:26 weewx weewx[16819]: cheetahgenerator: Skipping 
 template barometer.html.tmpl: cannot find start time
 Jan 10 15:10:26 weewx weewx[16819]: cheetahgenerator: Skipping 
 template index.html.tmpl: cannot find start time

>>>
>>> These are indicative of there being no data in your database. Since 
>>> you purged and reinstalled earlier your database will have been cleared 
>>> and 
>>> since WeeWX cannot get archvie records from the station no archive 
>>> records 
>>> are

[weewx-user] Re: trying to figure out sqlite data

[gjr80]

OK, let's see if we can clear up a few things here.

just and FYI, so my level of knowledge is understood: I am not a 
> programmer, just a network engineer, with a fair amount of experience with 
> linux and internet systems, so I am fumbling thru the sqlite syntax, and 
> trying to look at the python code with a very basic knowledge of where 
> things are being called.
>

That's OK, I am just an electronics engineer and an outdated one at that, 
when I started using WeeWX I wondered 'is that python with an ie or a y', 
so you will be fine.

My graphs being generated have gaps, and I think it is because of the long 
> data?
>

To understand why you see gaps in plots you need to understand a little of 
how the WeeWX plot engine works. Assume we are plotting an observation on a 
'line' type plot. When WeeWX starts plotting points for the line the 
current point is joined to the last point with a line. However, to provide 
a realistic plot when there is say a large gap in time for the observation 
concerned (say your sensor was offline for some time) rather than join two 
points quite some time apart with a straight line, WeeWX will leave out the 
joining line if the gap in time is sufficiently long. The gaps are 
controlled by the line_gap_fraction setting in skin.conf under 
[ImageGenerator]. A gap is considered to be *the time period covered by the 
entire plot* * line_gap_fraction. Any gaps in data greater than this value 
will be considered a gap and the connecting line omitted. So for a standard 
WeeWX day plot (nominally covering 27 hours) and the default 
line_gap_fraction value of 0.01 this value is about 16 minutes (it will 
actually vary as it is calculated based on the timestamps of the earliest 
point in the plot and the most recent point in the plot). So I would expect 
that you will be seeing gaps if you have successive points that are > 16 
minutes apart. Remember that whilst you may have archive records every 5 or 
so minutes if the observation concerned is None/NULL that point/timestamp 
is omitted from the plot series so it is quite possible to have continuous 
archive records every 5 minutes but still have gaps if data is missing. A 
common source of 'gaps in plots' is Davis station users who initially use 
the default 30 minute archive period, they only have data points in the 
plots every 30 minutes so the plots end up being a series of sparsely 
spaced dots.

Not sure what you mean by long data, type LONG or long as in 'this one has 
more digits than that one'? Either way it doesn't matter, if the data is in 
the archive and is not None/NULL it will be plotted without detriment.

Is some of this cause by the missing_calc=True switch
>

All the calc-missing option does is calculate any derived observations that 
are missing from imported data. So for example if dewpoint is missing from 
an imported record and calc-missing is True then WeeWX will calculate 
dewpoint for that record. As usual there are a couple of provisos; firstly 
WeeWX can only calculate those derived obs that it knows about, these are 
specified in the [StdWXCalculate] [[Calculations]] stanza in weewx.conf. So 
for a default install that would be pressure, barometer, altimeter, 
windchill, heatindex, dewpoint, inDewpoint and rainRate. Secondly, WeeWX 
can only calculate the derived obs if the required pre-requisites exist, 
for example dewpoint is a function of outTemp and outHumidity, if 
outHumidity does not exist dewpoint cannot be calculated and it will be 
left as is. The one to watch out here is WeeWX field pressure (aka station 
pressure), if the station provides WeeWX with barometer and WeeWX is to 
calculate pressure the outTemp value from 12 hours previous is required, if 
that historical data is not available then pressure will not be calculated. 
This is why you sometimes see no pressure data for the first 12 hours of an 
import (and this is the main cause for the reworking of wee_import in v4)

So unless you have some very weird intermittent data I suspect that 
calc-missing will have nothing to do with your gaps.

Any thoughts?
>

Yes, for any meaningful diagnosis you need to provide the plot you believe 
to have issues and details of the underlying data. You have provided 
details of the data (I think) but without knowing when or what was plotted 
it is impossible to say anything more.


Just a few words on wee_import. wee_import was never designed with the 
intent of using it as a cron job for importing WU data. In fact, there was 
some trepidation on Tom's behalf when a WU module was proposed for 
wee_import, WU is just to , well, all over the place and full of quirks to 
be a reliable and consistent data source. Take for example the current 
(new) WU API. During testing of the v4 wee_import it was found that 
successive API queries for the current days data for a given station would 
only return part of the day's data. The first query on the current day 
would return all records up until the current 

[weewx-user] Re: Import of driver failed [Interceptor]

[Scott Grayban]

>
> i still have no idea what changes you are making between runs


It's pretty simple when you read...

python-libpcap is a debian package installed via apt. and python-pypcap is 
the other package. I posted both outputs from each different ways to 
supposedly run you driver and neither work anymore. Plain and simple. I 
tested on a virgin install of debian 9 for a raspberry pi 3B+ with only 
hostapd installed and weewx. I changed the station_type to Interceptor and 
added the wlan0 info. I then started weewx and same problem... I don't what 
to give you when just this simple test didnt work either. 

-- 
You received this message because you are subscribed to the Google 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/61828d82-0e76-4663-92a9-956dfe232605%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[Scott Grayban]

never mind I have trashed weewx and will go on with something else. It 
worked for almost 3 years without a hitch.

On Sunday, January 12, 2020 at 5:15:06 PM UTC-8, mwall wrote:
>
>
>
> On Sunday, January 12, 2020 at 7:45:31 PM UTC-5, Scott Grayban wrote:
>>
>> Just to make sure that this isn't a error caused by me I installed a 
>> fresh raspian and weewx with your driver and my Ambient connected to 
>> hostapd and the same error popped up for both libpcap and pypcap installed. 
>> All virgin here... the only change in that weewx.conf I made was changing 
>> the station type and adding hostpad to raspbian.
>>
>
> scott,
>
> i still have no idea what changes you are making between runs, and which 
> log output is associated with each change.  it sounds like you are 
> modifying the libpcap layer and the python pcap layer - i've seen at least 
> two different pypcap versions in the log output (1.1 and 1.2.2). 
>
> m
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/156ff298-da52-49b1-96d4-c215a5560de3%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[mwall]

On Sunday, January 12, 2020 at 7:45:31 PM UTC-5, Scott Grayban wrote:
>
> Just to make sure that this isn't a error caused by me I installed a fresh 
> raspian and weewx with your driver and my Ambient connected to hostapd and 
> the same error popped up for both libpcap and pypcap installed. All virgin 
> here... the only change in that weewx.conf I made was changing the station 
> type and adding hostpad to raspbian.
>

scott,

i still have no idea what changes you are making between runs, and which 
log output is associated with each change.  it sounds like you are 
modifying the libpcap layer and the python pcap layer - i've seen at least 
two different pypcap versions in the log output (1.1 and 1.2.2). 

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/625b7846-16b0-4f60-adfe-be288128d774%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[Scott Grayban]

Just to make sure that this isn't a error caused by me I installed a fresh 
raspian and weewx with your driver and my Ambient connected to hostapd and 
the same error popped up for both libpcap and pypcap installed. All virgin 
here... the only change in that weewx.conf I made was changing the station 
type and adding hostpad to raspbian.

On Sunday, January 12, 2020 at 3:05:53 PM UTC-8, mwall wrote:
>
> On Sunday, January 12, 2020 at 5:47:18 PM UTC-5, Scott Grayban wrote:
>>
>>
>> [StdWXCalculate]
>> 
>> [[Calculations]]
>> # Derived quantities are calculated by this service. Possible 
>> values are:
>> #  hardware- use the value provided by hardware
>> #  software- use the value calculated by weewx
>> #  prefer_hardware - use value provide by hardware if available,
>> #  otherwise use value calculated by weewx
>> 
>> pressure = prefer_hardware
>> barometer = prefer_hardware
>> altimeter = prefer_hardware
>> windchill = prefer_hardware
>> heatindex = prefer_hardware
>> dewpoint = prefer_hardware
>> inDewpoint = prefer_hardware
>> rainRate = prefer_hardware
>> inHumidity = Inside Humidity
>>
>
> probably not relevant to the interceptor, but 'Inside Humidity' is not a 
> valid parameter for the 'Calculations' stanza.
>
> now with debug=1, start up weewx and post the log from startup until 
> failure.
>  
>

-- 
You received this message because you are subscribed to the Google 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/2efb2eaa-fd99-4684-9c57-099078dda170%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[Scott Grayban]

This error is with python-libpcap installed

Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Initializing weewx version 
3.9.2
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Using Python 2.7.13 (default, 
Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Platform 
Linux-4.19.66-v7+-armv7l-with-debian-9.11
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Locale is 'en_US.UTF-8'
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Using configuration file 
/etc/weewx/weewx.conf.20200110210428
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Debug is 1
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Initializing engine
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Loading station type 
Interceptor (user.interceptor)
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: driver 
version is 0.49
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: device type: 
observer
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: sensor map: 
None
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: mode is sniff
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: sniff 
iface=wlan0 promiscuous=0
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: sniff filter 
'src 10.3.141.62 and dst port 80'
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Import of driver failed: in 
method 'pcapObject_open_live', argument 2 of type 'char *' ()
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Unable to load driver: in 
method 'pcapObject_open_live', argument 2 of type 'char *'
Jan 12 13:28:07 weewx-pi weewx[3792]:   Exiting...

On Sunday, January 12, 2020 at 3:05:53 PM UTC-8, mwall wrote:
>
> On Sunday, January 12, 2020 at 5:47:18 PM UTC-5, Scott Grayban wrote:
>>
>>
>> [StdWXCalculate]
>> 
>> [[Calculations]]
>> # Derived quantities are calculated by this service. Possible 
>> values are:
>> #  hardware- use the value provided by hardware
>> #  software- use the value calculated by weewx
>> #  prefer_hardware - use value provide by hardware if available,
>> #  otherwise use value calculated by weewx
>> 
>> pressure = prefer_hardware
>> barometer = prefer_hardware
>> altimeter = prefer_hardware
>> windchill = prefer_hardware
>> heatindex = prefer_hardware
>> dewpoint = prefer_hardware
>> inDewpoint = prefer_hardware
>> rainRate = prefer_hardware
>> inHumidity = Inside Humidity
>>
>
> probably not relevant to the interceptor, but 'Inside Humidity' is not a 
> valid parameter for the 'Calculations' stanza.
>
> now with debug=1, start up weewx and post the log from startup until 
> failure.
>  
>

-- 
You received this message because you are subscribed to the Google 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/7169d461-7b2c-41ea-b111-202834f47b9d%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[Scott Grayban]

Shit wont post right here...

Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Initializing weewx version 
3.9.2 
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Using Python 2.7.13 (default, 
Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516] 
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Platform 
Linux-4.19.66-v7+-armv7l-with-debian-9.11 
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Locale is 'en_US.UTF-8' 
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Using configuration file 
/etc/weewx/weewx.conf 
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Debug is 1 
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Initializing engine 
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Loading station type 
Interceptor (user.interceptor) 
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: driver 
version is 0.49 
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: device type: 
observer 
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: sensor map: 
None 
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: mode is 
sniff 
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: sniff 
iface=wlan0 promiscuous=0 
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: sniff filter 
'src 10.3.141.62 and dst port 80' 
Jan 12 16:23:50 weewx-pi weewx[8674]: interceptor: MainThread: pypcap (1.1) 
Jan 12 16:23:50 weewx-pi weewx[8674]: interceptor: ServerThread: start 
sniff server 
Jan 12 16:23:50 weewx-pi weewx[8674]: engine: Loading service w 
Jan 12 16:23:50 weewx-pi weewx[8674]: interceptor: MainThread: shutting 
down server thread 
Jan 12 16:23:50 weewx-pi weewx[8674]: interceptor: MainThread: stop sniff 
server 
Jan 12 16:24:07 weewx-pi weewx[8674]: engine: Caught unrecoverable 
exception in engine: 
Jan 12 16:24:07 weewx-pi weewx[8674]:   Empty module name 
Jan 12 16:24:07 weewx-pi weewx[8674]:   Traceback (most recent call 
last): 
Jan 12 16:24:07 weewx-pi weewx[8674]: File 
"/usr/share/weewx/weewx/engine.py", line 888, in main 
Jan 12 16:24:07 weewx-pi weewx[8674]:   engine = 
engine_class(config_dict) 
Jan 12 16:24:07 weewx-pi weewx[8674]: File 
"/usr/share/weewx/weewx/engine.py", line 78, in __init__ 
Jan 12 16:24:07 weewx-pi weewx[8674]:  
 self.loadServices(config_dict) 
Jan 12 16:24:07 weewx-pi weewx[8674]: File 
"/usr/share/weewx/weewx/engine.py", line 142, in loadServices 
Jan 12 16:24:07 weewx-pi weewx[8674]:  
 self.service_obj.append(weeutil.weeutil._get_object(svc)(self, 
config_dict)) 
Jan 12 16:24:07 weewx-pi weewx[8674]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1107, in _get_object 
Jan 12 16:24:07 weewx-pi weewx[8674]:   mod = 
__import__(module) 
Jan 12 16:24:07 weewx-pi weewx[8674]:   ValueError: Empty module 
name 
Jan 12 16:24:07 weewx-pi weewx[8674]:   Exiting.


On Sunday, January 12, 2020 at 3:05:53 PM UTC-8, mwall wrote:
>
> On Sunday, January 12, 2020 at 5:47:18 PM UTC-5, Scott Grayban wrote:
>>
>>
>> [StdWXCalculate]
>> 
>> [[Calculations]]
>> # Derived quantities are calculated by this service. Possible 
>> values are:
>> #  hardware- use the value provided by hardware
>> #  software- use the value calculated by weewx
>> #  prefer_hardware - use value provide by hardware if available,
>> #  otherwise use value calculated by weewx
>> 
>> pressure = prefer_hardware
>> barometer = prefer_hardware
>> altimeter = prefer_hardware
>> windchill = prefer_hardware
>> heatindex = prefer_hardware
>> dewpoint = prefer_hardware
>> inDewpoint = prefer_hardware
>> rainRate = prefer_hardware
>> inHumidity = Inside Humidity
>>
>
> probably not relevant to the interceptor, but 'Inside Humidity' is not a 
> valid parameter for the 'Calculations' stanza.
>
> now with debug=1, start up weewx and post the log from startup until 
> failure.
>  
>

-- 
You received this message because you are subscribed to the Google 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/c3be8419-8d5d-4aa1-8155-f2e624d4eca2%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[Scott Grayban]

Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Initializing weewx version 3.9
.2
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Using Python 2.7.13 (default, 
Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Platform Linux-4.19.66-v7+-
armv7l-with-debian-9.11
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Locale is 'en_US.UTF-8'
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Using configuration file /etc/
weewx/weewx.conf
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Debug is 1
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Initializing engine
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Loading station type 
Interceptor (user.interceptor)
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: driver 
version is 0.49
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: device type: 
observer
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: sensor map: 
None
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: mode is sniff
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: sniff 
iface=wlan0 
promiscuous=0
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: sniff filter 
'src 
10.3.141.62 and dst port 80'
Jan 12 16:23:50 weewx-pi weewx[8674]: interceptor: MainThread: pypcap (1.1)
Jan 12 16:23:50 weewx-pi weewx[8674]: interceptor: ServerThread: start 
sniff server
Jan 12 16:23:50 weewx-pi weewx[8674]: engine: Loading service w
Jan 12 16:23:50 weewx-pi weewx[8674]: interceptor: MainThread: shutting 
down server thread
Jan 12 16:23:50 weewx-pi weewx[8674]: interceptor: MainThread: stop sniff 
server
Jan 12 16:24:07 weewx-pi weewx[8674]: engine: Caught unrecoverable 
exception in engine:
Jan 12 16:24:07 weewx-pi weewx[8674]:   Empty module name
Jan 12 16:24:07 weewx-pi weewx[8674]:   Traceback (most recent call 
last):
Jan 12 16:24:07 weewx-pi weewx[8674]: File 
"/usr/share/weewx/weewx/engine.py", line 888, in main
Jan 12 16:24:07 weewx-pi weewx[8674]:   engine = engine_class(
config_dict)
Jan 12 16:24:07 weewx-pi weewx[8674]: File 
"/usr/share/weewx/weewx/engine.py", line 78, in __init__
Jan 12 16:24:07 weewx-pi weewx[8674]:   self.loadServices(
config_dict)
Jan 12 16:24:07 weewx-pi weewx[8674]: File 
"/usr/share/weewx/weewx/engine.py", line 142, in loadServices
Jan 12 16:24:07 weewx-pi weewx[8674]:   self.service_obj.append(
weeutil.weeutil._get_object(svc)(self, config_dict))
Jan 12 16:24:07 weewx-pi weewx[8674]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1107, in _get_object
Jan 12 16:24:07 weewx-pi weewx[8674]:   mod = __import__(module)
Jan 12 16:24:07 weewx-pi weewx[8674]:   ValueError: Empty module 
name
Jan 12 16:24:07 weewx-pi weewx[8674]:   Exiting.


And this is with python-libpcap
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Initializing weewx version 3.9
.2 
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Using Python 2.7.13 (default, 
Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516] 
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Platform Linux-4.19.66-v7+-
armv7l-with-debian-9.11 
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Locale is 'en_US.UTF-8' 
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Using configuration file /etc/
weewx/weewx.conf.20200110210428 
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Debug is 1 
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Initializing engine 
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Loading station type 
Interceptor (user.interceptor) 
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: driver 
version is 0.49 
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: device type: 
observer 
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: sensor map: 
None 
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: mode is 
sniff 
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: sniff 
iface=wlan0 
promiscuous=0 
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: sniff filter 
'src 
10.3.141.62 and dst port 80' 
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Import of driver failed: in 
method 'pcapObject_open_live', argument 2 of type 'char *' () 
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Unable to load driver: in 
method 'pcapObject_open_live', argument 2 of type 'char *' 
Jan 12 13:28:07 weewx-pi weewx[3792]:   Exiting...


I removed inHumidity too see if that made any difference and it doesn't.

-- 
You received this message because you are subscribed to the Google 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/8af750d6-05ec-444c-b003-dc037019449d%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[Scott Grayban]

Error with python-libpcap installed

Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Initializing weewx version 3.9
.2
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Using Python 2.7.13 (default, 
Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Platform Linux-4.19.66-v7+-
armv7l-with-debian-9.11
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Locale is 'en_US.UTF-8'
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Using configuration file /etc/
weewx/weewx.conf.20200110210428
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Debug is 1
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Initializing engine
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Loading station type 
Interceptor (user.interceptor)
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: driver 
version is 0.49
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: device type: 
observer
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: sensor map: 
None
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: mode is sniff
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: sniff 
iface=wlan0 
promiscuous=0
Jan 12 13:28:07 weewx-pi weewx[3792]: interceptor: MainThread: sniff filter 
'src 
10.3.141.62 and dst port 80'
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Import of driver failed: in 
method 'pcapObject_open_live', argument 2 of type 'char *' ()
Jan 12 13:28:07 weewx-pi weewx[3792]: engine: Unable to load driver: in 
method 'pcapObject_open_live', argument 2 of type 'char *'
Jan 12 13:28:07 weewx-pi weewx[3792]:   Exiting...


Error with python-pypcap

Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Initializing weewx version 3.9
.2 
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Using Python 2.7.13 (default, 
Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516] 
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Platform Linux-4.19.66-v7+-
armv7l-with-debian-9.11 
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Locale is 'en_US.UTF-8' 
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Using configuration file /etc/
weewx/weewx.conf 
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Debug is 1 
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Initializing engine 
Jan 12 16:23:49 weewx-pi weewx[8674]: engine: Loading station type 
Interceptor (user.interceptor) 
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: driver 
version is 0.49 
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: device type: 
observer 
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: sensor map: 
None 
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: mode is 
sniff 
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: sniff 
iface=wlan0 
promiscuous=0 
Jan 12 16:23:49 weewx-pi weewx[8674]: interceptor: MainThread: sniff filter 
'src 
10.3.141.62 and dst port 80' 
Jan 12 16:23:50 weewx-pi weewx[8674]: interceptor: MainThread: pypcap (1.1) 
Jan 12 16:23:50 weewx-pi weewx[8674]: interceptor: ServerThread: start 
sniff server 
Jan 12 16:23:50 weewx-pi weewx[8674]: engine: Loading service w 
Jan 12 16:23:50 weewx-pi weewx[8674]: interceptor: MainThread: shutting 
down server thread 
Jan 12 16:23:50 weewx-pi weewx[8674]: interceptor: MainThread: stop sniff 
server 
Jan 12 16:24:07 weewx-pi weewx[8674]: engine: Caught unrecoverable 
exception in engine: 
Jan 12 16:24:07 weewx-pi weewx[8674]:   Empty module name 
Jan 12 16:24:07 weewx-pi weewx[8674]:   Traceback (most recent call 
last): 
Jan 12 16:24:07 weewx-pi weewx[8674]: File 
"/usr/share/weewx/weewx/engine.py", line 888, in main 
Jan 12 16:24:07 weewx-pi weewx[8674]:   engine = engine_class(
config_dict) 
Jan 12 16:24:07 weewx-pi weewx[8674]: File 
"/usr/share/weewx/weewx/engine.py", line 78, in __init__ 
Jan 12 16:24:07 weewx-pi weewx[8674]:   self.loadServices(
config_dict) 
Jan 12 16:24:07 weewx-pi weewx[8674]: File 
"/usr/share/weewx/weewx/engine.py", line 142, in loadServices 
Jan 12 16:24:07 weewx-pi weewx[8674]:   self.service_obj.append(
weeutil.weeutil._get_object(svc)(self, config_dict)) 
Jan 12 16:24:07 weewx-pi weewx[8674]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1107, in _get_object 
Jan 12 16:24:07 weewx-pi weewx[8674]:   mod = __import__(module) 
Jan 12 16:24:07 weewx-pi weewx[8674]:   ValueError: Empty module 
name 
Jan 12 16:24:07 weewx-pi weewx[8674]:   Exiting.




On Sunday, January 12, 2020 at 3:05:53 PM UTC-8, mwall wrote:
>
> On Sunday, January 12, 2020 at 5:47:18 PM UTC-5, Scott Grayban wrote:
>>
>>
>> [StdWXCalculate]
>> 
>> [[Calculations]]
>> # Derived quantities are calculated by this service. Possible 
>> values are:
>> #  hardware- use the value provided by hardware
>> #  software- use the value calculated by weewx
>> #  prefer_hardware - use value provide by hardware if a

[weewx-user] Re: Weewx v4 beta install doesn't create an index.html file

[Ted Frohling]

Well, I thought that I had found the problem, my issue turned out that my 
data logger memory was failing and that was the reason I wasn't getting an 
index.html file created, since there was no data to be posted.  I went back 
to the 3.9 train to figure out what was really happening, only to find that 
the data logger was causing the issue.  I have a new one on order so after 
that gets installed and 3.9 is working correctly, I'll do the upgrade 
again.  

ted


On Wednesday, January 8, 2020 at 9:09:38 PM UTC-7, ted frohling wrote:
>
> I'm trying to install weewx-4.0.0b7 but after the install, there is no 
> index.html file in the /home/weewx/public_html directory.  Am I missing 
> something in the build or the docs?
>
> Thanks,
>
> ted
>
>

-- 
You received this message because you are subscribed to the Google 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/3a30f0d6-57d7-489a-8aaa-1f9b9c71662b%40googlegroups.com.

[weewx-user] Re: Weewx v4 beta install doesn't create an index.html file

[KnC Mc]

@ted can you share what you found?  I am seeing some weird issues with my 
wee_reports, and maybe what you found can help?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f0f9929d-f0fd-46f1-9243-6daee8160fb1%40googlegroups.com.

[weewx-user] Re: trying to figure out sqlite data

[KnC Mc]

Actually, now that I look again, there are NULL values and long values in 
the 'pressure' column and that is what I was seeing that raised a flag.  

I might mention that this box is running simulator driver, and I pull the 
data from WU with wee_importv4 / wee-reportsv3.8.0 to populate the graphs 
via cheetah and the Standard template.  I have been trying the beta v4 
wee_import, and cron a script that calls the utilities.  It was working for 
a day or so, but it started failing, so I changed the script to call 
wee_import every 12 hours, and now every 10 minutes, but it only seems to 
work from 1-2am everyday now, and I am trying too figure out why.  The logs 
show the imports, but the only discrepancy in the archive database I can 
see is the integer/long differences.  

If there is something else I can provide to troubleshoot this, let me know. 
 This is deeper than I have looked before, so I am still reading docs.  I 
change the trachea value from 250 to 50 thinking that had something to do 
with it, and I have played with the time frames that I call the script in 
cron, but don't see a difference.  The odd thing is that when I do a full 
days import I see some PRIMARY Key errors, but if I wait a couple hours the 
graphs update.  I do not understand why the graphs do not update 
immediately like they did before the api_key was required back in May?  

just and FYI, so my level of knowledge is understood: I am not a 
programmer, just a network engineer, with a fair amount of experience with 
linux and internet systems, so I am fumbling thru the sqlite syntax, and 
trying to look at the python code with a very basic knowledge of where 
things are being called.  

-- 
You received this message because you are subscribed to the Google 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/2927efc5-e930-4a0a-b03e-c11758ca4997%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[mwall]

On Sunday, January 12, 2020 at 5:47:18 PM UTC-5, Scott Grayban wrote:
>
>
> [StdWXCalculate]
> 
> [[Calculations]]
> # Derived quantities are calculated by this service. Possible 
> values are:
> #  hardware- use the value provided by hardware
> #  software- use the value calculated by weewx
> #  prefer_hardware - use value provide by hardware if available,
> #  otherwise use value calculated by weewx
> 
> pressure = prefer_hardware
> barometer = prefer_hardware
> altimeter = prefer_hardware
> windchill = prefer_hardware
> heatindex = prefer_hardware
> dewpoint = prefer_hardware
> inDewpoint = prefer_hardware
> rainRate = prefer_hardware
> inHumidity = Inside Humidity
>

probably not relevant to the interceptor, but 'Inside Humidity' is not a 
valid parameter for the 'Calculations' stanza.

now with debug=1, start up weewx and post the log from startup until 
failure.
 

-- 
You received this message because you are subscribed to the Google 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/e36caeab-5823-467f-abfb-1aa29ad7654c%40googlegroups.com.

[weewx-user] Re: trying to figure out sqlite data

[vince]

On Sunday, January 12, 2020 at 2:43:48 PM UTC-8, KnC Mc wrote:
>
> I have some weird reporting while executing wee_reports, and trying to 
> decipher sqlite archive data... I am running v3.8.0 and trying to generate 
> html with cheetah generate with the Standard Template using wee_reports; I 
> can see that the from logs that the data is being imported from WU, but the 
> data appears to have different data (float, and long?) being populated in 
> the database.  My graphs being generated have gaps, and I think it is 
> because of the long data?  Is this supposed to populate like this?  Is some 
> of this cause by the missing_calc=True switch?  It seems when the long data 
> is present the graphs do not generate?  Any thoughts?
>
>
The schema dictates the data type, which by default is REAL everywhere 
basically.  I'm guessing you're seeing 29.945 and thinking it's a different 
data type than 29.51324567 perhaps (?)

To see the schema, try:

echo ".schema" | sqlite3 /home/weewx/archive/weewx.sdb | grep "TABLE 
archive"


(or substitute in the path to your weewx.sdb if you used a pre-packaged 
weewx or if you put your db in an unusual place)
 
 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5540892e-cef3-4e28-9672-dd1f4245196b%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[Scott Grayban]

# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2015 Tom Keffer
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.9.2

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Nettleton District Weather Station, Spokane, Washington"

# Latitude and longitude in decimal degrees
latitude = 47.6677449
longitude = -117.447635

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 1922, foot

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be 
used.
#station_type = Simulator
station_type = Interceptor

# If you have a website, you may specify an URL
station_url = http://www.nettletondistrict.com/Nettleton/

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 6

##

[Simulator]
# 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

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

[Interceptor]

driver = user.interceptor
device_type = observer
mode = sniff
iface = wlan0
pcap_filter = src 10.3.141.62 and dst port 80

##

#   This section is for uploading data to Internet sites

[StdRESTful]

[[StationRegistry]]
# To register this weather station with weewx, set this to true
register_this_station = true

[[AWEKAS]]
# This section is for configuring posts to AWEKAS.

# If you wish to do this, set the option 'enable' to true,
# and specify a username and password.
# To guard against parsing errors, put the password in quotes.
enable = false
username = replace_me
password = replace_me

[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to do this, set the option 'enable' to true,
# and specify the station ID (e.g., CW1234).
enable = true
station = FW4353

# If this is an APRS (radio amateur) station, uncomment
# the following and replace with a passcode (e.g., 12345).
#passcode = replace_me (APRS stations only)

[[PWSweather]]
# This section is for configuring posts to PWSweather.com.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
# To guard against parsing errors, put the password in quotes.
enable = true
station = KWASPOKA85
password = xx

[[WOW]]
# This section is for configuring posts to WOW.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
# To guard against parsing errors, put the password in quotes.
enable = true
station = d2850c02-2199-e911-80e7-0003ff59883f
password = x
retry_login = 30

[[Wunderground]]
# This section is for configuring posts to the Weather Underground.

# If you wish to do this, set the option 'enable' to true,
# and specify a station (e.g., 'KORHOODR3') and password.
# To guard against parsing errors, put the password in quotes.
enable = false
station = KWASPOKA85
password = 

# Set the following to True to have weewx use the WU "Rapidfire"
   

[weewx-user] trying to figure out sqlite data

[KnC Mc]

I have some weird reporting while executing wee_reports, and trying to 
decipher sqlite archive data... I am running v3.8.0 and trying to generate 
html with cheetah generate with the Standard Template using wee_reports; I 
can see that the from logs that the data is being imported from WU, but the 
data appears to have different data (float, and long?) being populated in 
the database.  My graphs being generated have gaps, and I think it is 
because of the long data?  Is this supposed to populate like this?  Is some 
of this cause by the missing_calc=True switch?  It seems when the long data 
is present the graphs do not generate?  Any thoughts?



1578658795|1|5|29.985|29.8761096323624|||44.8||95.0|0.0|146.0|0.0||0.0|0.0|43.3|44.8|44.8|0.0|0.0|0.0||

1578659088|1|5|29.99|29.881088493416|||44.6||95.0|0.0|146.0|0.0||0.0|0.0|43.2|44.6|44.6|0.0|0.0|0.0||

1578659388|1|5|29.995|29.8860733174157|||44.8||95.0|0.1|146.0|1.1||0.0|0.0|43.3|44.8|44.8|0.0|0.0|0.0||

1578659691|1|5|29.995|29.8858513938269|||44.1||95.0|0.0|146.0|0.0||0.0|0.0|42.7|44.1|44.1|0.0|0.0|0.0||

1578659995|1|5|30.005|29.8958089206109|||43.6||95.3|0.3|146.0|1.1||0.0|0.0|42.3|43.6|43.6|0.0|0.0|0.0||

1578660288|1|5|30.01|29.9010209175344|||44.8||95.5|0.0|146.0|1.1||0.0|0.0|43.6|44.8|44.8|0.0|0.0|0.0||

1578660588|1|5|30.01|29.900801236113|||44.4||95.0|0.0|146.0|0.0||0.0|0.0|43.0|44.4|44.4|0.0|0.0|0.0||

1578660891|1|5|30.015|29.9057641779364|||43.1||95.0|0.0|146.0|0.0||0.0|0.0|41.6|43.1|43.1|0.0|0.0|0.0||

1578661195|1|5|30.015|29.9057603259206|||42.8||95.1|0.0|146.0|0.0||0.0|0.0|41.4|42.8|42.8|0.0|0.0|0.0||

1578661488|1|5|30.015|29.9055446491771|||42.5||95.4|0.1|146.0|1.1||0.0|0.0|41.3|42.5|42.5|0.0|0.0|0.0||

1578661788|1|5|30.015|29.905545537471|||42.4||96.0|0.0|146.0|1.1||0.0|0.0|41.5|42.4|42.4|0.0|0.0|0.0||

1578662091|1|5|30.015|29.9057623802369|||42.7||96.0|0.3|146.0|1.1||0.0|0.0|41.8|42.7|42.7|0.0|0.0|0.0||

1578662395|1|5|30.025|29.9157345674942|||43.3||96.0|0.3|146.0|1.1||0.0|0.0|42.4|43.3|43.3|0.0|0.0|0.0||

1578662688|1|5|30.025|29.915741851967|||43.8||96.0|0.0|146.0|1.1||0.0|0.0|42.9|43.8|43.8|0.0|0.0|0.0||

1578662988|1|5|30.025|29.9157403852974|||43.7||96.0|0.0|146.0|0.0||0.0|0.0|42.8|43.7|43.7|0.0|0.0|0.0||

1578663291|1|5|30.035|29.92569529528|||43.1||96.0|0.0|146.0|0.0||0.0|0.0|42.2|43.1|43.1|0.0|0.0|0.0||

1578663595|1|5|30.035|29.9256981760096|||43.3||96.0|0.2|146.0|1.1||0.0|0.0|42.4|43.3|43.3|0.0|0.0|0.0||

1578663888|1|5|30.045|29.9356632326362|||43.4||96.0|0.1|146.0|1.1||0.0|0.0|42.5|43.4|43.4|0.0|0.0|0.0||

1578664188|1|5|30.045|29.9356646856104|||43.5||96.0|0.1|146.0|1.1||0.0|0.0|42.6|43.5|43.5|0.0|0.0|0.0||

1578664491|1|5|30.045|29.9356632326362|||43.4||96.0|0.0|146.0|0.0||0.0|0.0|42.5|43.4|43.4|0.0|0.0|0.0||

1578664795|1|5|30.04|29.93067139438|||42.7||96.0|0.0|146.0|1.1||0.0|0.0|41.8|42.7|42.7|0.0|0.0|0.0||

1578665088|1|5|30.045|29.9354347320158|||42.3||96.0|0.0|146.0|1.1||0.0|0.0|41.4|42.3|42.3|0.0|0.0|0.0||

1578665388|1|5|30.04|29.9304529655435|||42.3||96.0|0.1|146.0|1.1||0.0|0.0|41.4|42.3|42.3|0.0|0.0|0.0||

1578665691|1|5|30.04|29.9304529655435|||42.3||96.0|0.0|146.0|0.0||0.0|0.0|41.4|42.3|42.3|0.0|0.0|0.0||

1578665995|1|5|30.045|29.9354347320158|||42.3||96.0|0.0|146.0|1.1||0.0|0.0|41.4|42.3|42.3|0.0|0.0|0.0||

1578666288|1|5|30.045|29.9354358730477|||42.3||96.3|0.0|146.0|0.0||0.0|0.0|41.5|42.3|42.3|0.0|0.0|0.0||

1578666588|1|5|30.055|29.9456196470376|||42.9||96.0|0.0|146.0|0.0||0.0|0.0|42.0|42.9|42.9|0.0|0.0|0.0||

1578666891|1|5|30.055|29.9456253930404|||43.3||96.0|0.0|146.0|0.0||0.0|0.0|42.4|43.3|43.3|0.0|0.0|0.0||

1578667195|1|5|30.055|29.945623949298|||43.2||96.0|0.0|146.0|0.0||0.0|0.0|42.3|43.2|43.2|0.0|0.0|0.0||

1578667488|1|5|30.055|29.9456268416336|||43.4||96.0|0.1|146.0|1.1||0.0|0.0|42.5|43.4|43.4|0.0|0.0|0.0||

1578667788|1|5|30.055|29.9456297534278|||43.6||96.0|0.1|146.0|1.1||0.0|0.0|42.7|43.6|43.6|0.0|0.0|0.0||

1578668091|1|5|30.055|29.9456344229049|||44.0||95.7|0.9|146.0|2.2||0.0|0.0|43.0|44.0|44.0|0.0|0.4|0.0||

1578668395|1|5|30.055|29.9458539312799|||44.7||95.0|0.8|146.0|2.2||0.0|0.0|43.2|44.7|44.7|0.0|2.6|0.

[weewx-user] Re: Import of driver failed [Interceptor]

[mwall]

On Sunday, January 12, 2020 at 3:29:40 PM UTC-5, Scott Grayban wrote:
>
> Well I can't find it. I have been through it a dozen times and just don't 
> see it.
>

no one can help you if you don't post it!  try posting your weewx 
configuration file (the one that resulted in the 'engine: Loading service 
w' and 'ValueError: Empty module name' exception).

diagnosing these things is MUCH easier if you post the log and config right 
from the start.

sometimes just the act of doing that will let you see things that you missed

-- 
You received this message because you are subscribed to the Google 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/f3f47822-e2ff-4dc9-b052-cd68cf4cf1e6%40googlegroups.com.

[weewx-user] Re: Netatmo extraTemp2

[mwall]

user sainton made a similar request:

> Hi,
> I'm using Weewx an Netatmo weather station. All works fine. But I have a 
second extramodule, but how my 

> I have this extramodule data in Weewx ?

> My I need to modify netatmo.py and add more field data ?


> 'extraTemp2': '
*.NAModule5.Temperature',> 'extraHumid2': '*.NAModule5.Humidity',
> 'extra_rf_status_2': '
*.NAModule5.rf_status',> 'extra_battery_vp_2': '*.NAModule5.battery_vp',
> 'extra2BatteryStatus': '*.NAModule5.battery_percent',

> My I rebuild my SQL database ?

> Thank's for your help.

> Gilles.


and here is the answer:


do not modify netatmo.py. do not modify your schema.


modify the [Netatmo] section of your weewx configuration file like this:


[Netatmo]
...
[[sensor_map]]
extraTemp2 = *.NAModule5.Temperature
extraHumid2 = *.NAModule5.Humidity
extra_rf_status_2 = *.NAModule5.rf_status
extra_battery_vp_2 = *.NAModule5.battery_vp
extra2BatteryStatus = *.NAModule5.battery_percent



-- 
You received this message because you are subscribed to the Google 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/b2928b80-48fc-4d83-876f-f595bcb2181a%40googlegroups.com.

[weewx-user] Re: wanted: users with ecowitt gw1000 wifi bridge

[mwall]

On Sunday, January 12, 2020 at 7:23:30 AM UTC-5, Vetti52 wrote:
>
> This will make things a bit easier. However, I must confess, that I am 
> sometimes a bit messy. So, when updating interceptor.py from your site, I 
> will have to remember, on which parts I mades my modifications. So, for me 
> it would be much easier, if all modifications could  reside in a separate 
> file. I am afraid, that realizing this would a hard job for now.
>

the only modifications you should make are to the weewx configuration file.

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b7d27feb-4733-4368-afc9-62405d1ceb42%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[Scott Grayban]

Well I can't find it. I have been through it a dozen times and just don't 
see it.

On Saturday, January 11, 2020 at 9:30:16 PM UTC-8, mwall wrote:
>
> On Saturday, January 11, 2020 at 9:37:44 PM UTC-5, Scott Grayban wrote:
>>
>>
>> All of this points to the weewx engine but non of it makes any sense 
>> because I can run interceptor standalone.
>>
>
> actually, it points to a problem in your weewx configuration 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/12d60f14-e363-4326-adb6-3a778a4d3259%40googlegroups.com.

[weewx-user] Netatmo extraTemp2

[ve2se]

Hi all  
adding  an extraTemp2 to my Netatmo station , i want to know how to add it 
to weewx datadump from dev.netatmo.com .
Looking at weewx.log  , i receive data for ;
NAMain  module , NAModule1 (exteriorTemp) , NAModule 2 (wind) , NAModule 3 
(rain) , NAModule 4 (extraTemp1) 
but nothing for extraTemp2 . extraTemp2  is present in my Netatmo app.
Tnx for help , Jean-Pierre

-- 
You received this message because you are subscribed to the Google 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/b376839a-27ce-48c8-8c6a-c17e6de8eab3%40googlegroups.com.

[weewx-user] Re: wanted: users with ecowitt gw1000 wifi bridge

[Gert Andersen]

Hi Matthew

Seems to work with the additional sensors now.

Thanks for your support.

Gert

On Sunday, January 12, 2020 at 9:21:35 AM UTC+1, mwall wrote:
>
>
>
> On Sunday, January 12, 2020 at 1:38:45 AM UTC-5, Gert Andersen wrote:
>>
>>
>> Out running directly:
>> pi@Desktop:~/weewx-interceptor/bin/user $ PYTHONPATH=/usr/share/weewx 
>> python /usr/share/weewx/user/interceptor.py --device=ecowitt-client --port 
>> 8000 --debug
>> raw data: 
>> PASSKEY=&stationtype=EasyWeatherV1.4.5&dateutc=2020-01-12+06:19:35&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.000&monthlyrainin=0.000&yearlyrainin=0.000&temp2f=43.7&humidity2=91&batt2=0&freq=868M&model=HP1000SE_Pro_V1.5.8
>> raw packet: {'temperature_2': 43.7, 'humidity_2': 91.0, 'rain_rate': 0.0, 
>> 'battery_2': 0.0, 'dateTime': 1578809975, 'usUnits': 1}
>> mapped packet: {'temperature_2': 43.7, 'humidity_2': 91.0, 'rain_rate': 
>> 0.0, 'battery_2': 0.0, 'dateTime': 1578809975, 'usUnits': 1}
>>
>> I have this in in weewx.conf:
>> [Interceptor]
>> driver = user.interceptor
>> device_type = ecowitt-client
>> port = 8000
>>[[sensor_map]]
>> outTemp = temperature_2
>> outHumidity = humidity_2
>>
>>
> i think you should use the sensor_map_extensions, not sensor_map.  so your 
> configuration would look like this:
>
> [Interceptor]
> driver = user.interceptor
> device_type = ecowitt-client
> port = 8000
> [[sensor_map_extensions]]
> outTemp = temperature_2
> outHumidity = humidity_2
>
> that way all of the normal mappings will remain, and you only override 
> outTemp and outHumidity to use the additional sensor.
>
> m 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b436649c-7a64-4bc5-8237-645415ce551b%40googlegroups.com.

[weewx-user] Re: wanted: users with ecowitt gw1000 wifi bridge

[Vetti52]

Thanks, Matthew!

This will make things a bit easier. However, I must confess, that I am 
sometimes a bit messy. So, when updating interceptor.py from your site, I 
will have to remember, on which parts I mades my modifications. So, for me 
it would be much easier, if all modifications could  reside in a separate 
file. I am afraid, that realizing this would a hard job for now.


On Sunday, 12. January 2020 at 01:31:13 UTC+1 mwall wrote:
>
> thank you paul, gert, vetti25, thomas gum, g hammer!  support for 
> additional sensors added as of commit 
> a37cd1a9741fccbade9496c40c5bd9d4905b8ad1
>
> i also added support for 'sensor_map_extensions' - you can define only 
> additional mappings instead of having to define the entire map
>
> for example, all you have to do to add sensors is this:
>
> [Interceptor]
> ...
> [[sensor_map_extensions]]
> extraTemp5 = temperature_5
> extraHumid5 = humidity_5
>
> any mappings in sensor_map_extensions will add to or replace those in 
> sensor_map
>
> of course, if you define sensor_map yourself that will replace the default 
> sensor_map
>
> m
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3c4e93a5-707f-4a61-b6f0-df1e32fc7fd4%40googlegroups.com.

Re: [weewx-user] Re: getting weewx[12196]: cheetahgenerator: Skipping template index.html.tmpl: cannot find start time

[Thomas Keffer]

Ted, it's not clear what you are doing, nor what setup you have. Slow down
and describe your setup carefully.

Do you have a single ISS (the gadget with the wind vane and rain bucket), a
single console, and a single Envoy? Which ones are wired to the ISS? You
say the Envoy has a wired connection to the ISS. What about the console?

Just to be clear: there is no connection between consoles and Envoys. They
listen to the ISS independently, either through a wire, or wirelessly,
never to each other.

Finally, you said you removed the logger from the Envoy, but you didn't say
whether you put it back in.

-tk

On Sat, Jan 11, 2020 at 4:04 PM Ted Frohling  wrote:

> I removed the data logger from the Envoy and am now getting:
>
> Jan 11 17:01:32 weewx weewx[23496]: vantage: Retrieving 513 page(s);
> starting index= 3
> Jan 11 17:01:36 weewx weewx[23496]: vantage: get_data_with_crc16; try #1
> failed: Expected to read 267 chars; got 191 inst
> ead
> Jan 11 17:01:36 weewx weewx[23496]: vantage: Timeout in get_data_with_crc16
> Jan 11 17:01:36 weewx weewx[23496]: vantage: Getting archive packets since
> 2020-01-11 16:40:00 MST (1578786000)
> Jan 11 17:01:40 weewx weewx[23496]: vantage: Retry  #0 failed
>
> I would assume this indicates either a communications problem or very
> corrupted memory in the logger.  With the other problems, I suspect bad
> memory.  Am I right?
>
> ted
>
> On Saturday, January 11, 2020 at 4:39:29 PM UTC-7, Ted Frohling wrote:
>>
>> Missed he reference to taking the logger out and reseating.  Will do
>> that.  The console seems to be working well.  The system is a wired system
>> that connects to the envoy.  I'm assuming the console receives it's data
>> from the envoy via radio.
>>
>> ted
>>
>>
>> On Saturday, January 11, 2020 at 4:20:28 AM UTC-7, Thomas Keffer wrote:
>>>
>>> Did you try reseating the logger?
>>>
>>> On Fri, Jan 10, 2020 at 6:36 PM Ted Frohling  wrote:
>>>


 On Friday, January 10, 2020 at 6:09:38 PM UTC-7, Ted Frohling wrote:
>
>
>
> On Friday, January 10, 2020 at 3:41:10 PM UTC-7, gjr80 wrote:
>>
>>
>> On Saturday, 11 January 2020 08:15:14 UTC+10, Ted Frohling wrote:
>>>
>>> Reset the Vantage Pro 2 console and the Weather Envoy for good
>>> measure.  Dumped the database and cleared the memory. Still have the
>>> problem. The Vantage Pro 2 console is old, and the firmware is stuck at
>>> 1.90.  Wondering if I should pitch it and get a new console.
>>>
>>
>> No need for anything drastic like that. My console is v1.90 and works
>> fine. I don't have an envoy though I don't believe that changes the 
>> process
>> for clearing the station memory. Just checking the obvious, but you did
>> stop WeeWX before running wee_device to clear the station memory?
>> Were there any errors returns anywhere during the process?
>>
>
> No errors for either the dump or the clear command. However after
> doing the dump, followed by the clear, and restarting weewx, waiting, no
> records are being put into the database.
>
>>
>> Wondering if the following log messages are indicitive of the problem:
>>>
>>> weewx weewx[16819]: cheetahgenerator: Skipping template
>>> wind.html.tmpl: cannot find start time
>>> Jan 10 15:10:26 weewx weewx[16819]: cheetahgenerator: Skipping
>>> template barometer.html.tmpl: cannot find start time
>>> Jan 10 15:10:26 weewx weewx[16819]: cheetahgenerator: Skipping
>>> template index.html.tmpl: cannot find start time
>>>
>>
>> These are indicative of there being no data in your database. Since
>> you purged and reinstalled earlier your database will have been cleared 
>> and
>> since WeeWX cannot get archvie records from the station no archive 
>> records
>> are being saved to archive. Once we get archive records those errors will
>> disappear. You could run with record_generation =  software but that
>> is only putting a bandaid on the problem not fixing it.
>>
>>
> I'll try that and see if I can get that working.  thanks.
>

 Setting  record_generation =  software allowed weewx to start updating
 the database and web pages are being generated.  Which is good news, but as
 you say a bandaid.



> ted
>
> Tom may have more advice.
>>
>> Gary
>>
>> --
 You received this message because you are subscribed to the Google
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to weewx...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/weewx-user/be6b96b0-ba79-4c0e-a8c9-be6394d312dc%40googlegroups.com
 
 .

>>> --
> You received this message because

[weewx-user] Re: New html page

[Mikael Fredriksson]

Andrew,

I made a simple misstake, pointed the web page to wrong folder 
(/var/www/html/weewx/Bjurdammen/tables.html) instead of 
(/var/www/html/weewx/tables.html).
Don't know thou why the table.html can be found in both of those folders? 

Thanks for your answer, and I'll try to be more specific next time I ask 
for help :)

/Mikael

Den söndag 12 januari 2020 kl. 12:34:57 UTC+1 skrev Andrew Milner:
>
> have you actually inlcuded the reference to the css in your new file?  
> Without knowing what skin you are using, what you actually changed and what 
> you are actually seeing it is very hard for us to imagine or speculate on 
> what your specific problem may be caused by!!
>
>
>
> On Sunday, 12 January 2020 13:22:45 UTC+2, Mikael Fredriksson wrote:
>>
>> Hi!
>>
>>
>> When creating new web page I copied a template from my running page and 
>> renamed it and made som smaller changes to it. 
>> Added it to the skin.conf under [CheetahGenerator]
>> When running a report cycle the new page is generated but it dont have 
>> the same look, not the background and so on..
>> I added the new template in same skin folder as the file I copied and 
>> changed the name. 
>> Must I change or add something somewhere else to get the same look of the 
>> new page? In main.css I didn't find anything that had to do with the pages 
>> specific.
>>
>> Help appreciated!
>>
>> /Mikael
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4b79a528-9b0e-4c55-911f-51cc5f361e15%40googlegroups.com.

[weewx-user] Re: New html page

[Andrew Milner]

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



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

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6c0a9f55-2973-4f7f-a021-8717c43d83a4%40googlegroups.com.

[weewx-user] New html page

[Mikael Fredriksson]

Hi!


When creating new web page I copied a template from my running page and 
renamed it and made som smaller changes to it. 
Added it to the skin.conf under [CheetahGenerator]
When running a report cycle the new page is generated but it dont have the 
same look, not the background and so on..
I added the new template in same skin folder as the file I copied and 
changed the name. 
Must I change or add something somewhere else to get the same look of the 
new page? In main.css I didn't find anything that had to do with the pages 
specific.

Help appreciated!

/Mikael

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/620131af-37c3-4f25-801d-6537c90894dc%40googlegroups.com.

Re: [weewx-user] Re: pi is online and weewx driver is working - but not posting

[Sean Jahnig]

Thanks for the reply Matthew.

We had a big storm last night so i guess the sensor must've power cycled
itself? It is mounted far out of reach so i'm quite certain no one touched
it.

Will keep an eye on it.

Thanks

On Sun, Jan 12, 2020 at 1:14 PM mwall  wrote:

> On Sunday, January 12, 2020 at 3:56:32 AM UTC-5, Sean Jahnig wrote:
>>
>>
>> Any ideas why that would've changed?
>>
>
> it depends on the sensor.  i know that some temperature/humidity sensors
> have a new, apparently random identifier each time you power cycle them.
> however, i have never seen the 5n1 sensor do that.
>
> m
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/rlau4OqQTtY/unsubscribe.
> To unsubscribe from this group and all its topics, 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/a4bbc408-2fec-44ee-a40a-0b1c355f6495%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/CALeSoZnX170TOt81tr1rK7PZRqWc%2BFjYOU9xZ8GUnnQ4RGdu1Q%40mail.gmail.com.

[weewx-user] Re: wanted: users with ecowitt gw1000 wifi bridge

[Gert Andersen]

Hi 

Thanks for your prompt answer.

I'll try later today and let you know.

Gert

On Sunday, January 12, 2020 at 9:21:35 AM UTC+1, mwall wrote:
>
>
>
> On Sunday, January 12, 2020 at 1:38:45 AM UTC-5, Gert Andersen wrote:
>>
>>
>> Out running directly:
>> pi@Desktop:~/weewx-interceptor/bin/user $ PYTHONPATH=/usr/share/weewx 
>> python /usr/share/weewx/user/interceptor.py --device=ecowitt-client --port 
>> 8000 --debug
>> raw data: 
>> PASSKEY=&stationtype=EasyWeatherV1.4.5&dateutc=2020-01-12+06:19:35&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.000&monthlyrainin=0.000&yearlyrainin=0.000&temp2f=43.7&humidity2=91&batt2=0&freq=868M&model=HP1000SE_Pro_V1.5.8
>> raw packet: {'temperature_2': 43.7, 'humidity_2': 91.0, 'rain_rate': 0.0, 
>> 'battery_2': 0.0, 'dateTime': 1578809975, 'usUnits': 1}
>> mapped packet: {'temperature_2': 43.7, 'humidity_2': 91.0, 'rain_rate': 
>> 0.0, 'battery_2': 0.0, 'dateTime': 1578809975, 'usUnits': 1}
>>
>> I have this in in weewx.conf:
>> [Interceptor]
>> driver = user.interceptor
>> device_type = ecowitt-client
>> port = 8000
>>[[sensor_map]]
>> outTemp = temperature_2
>> outHumidity = humidity_2
>>
>>
> i think you should use the sensor_map_extensions, not sensor_map.  so your 
> configuration would look like this:
>
> [Interceptor]
> driver = user.interceptor
> device_type = ecowitt-client
> port = 8000
> [[sensor_map_extensions]]
> outTemp = temperature_2
> outHumidity = humidity_2
>
> that way all of the normal mappings will remain, and you only override 
> outTemp and outHumidity to use the additional sensor.
>
> m 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9c14d6d9-3b52-4089-a804-5700c3e158d6%40googlegroups.com.

Re: [weewx-user] Re: pi is online and weewx driver is working - but not posting

[mwall]

On Sunday, January 12, 2020 at 3:56:32 AM UTC-5, Sean Jahnig wrote:
>
>
> Any ideas why that would've changed?
>

it depends on the sensor.  i know that some temperature/humidity sensors 
have a new, apparently random identifier each time you power cycle them.  
however, i have never seen the 5n1 sensor do that.

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a4bbc408-2fec-44ee-a40a-0b1c355f6495%40googlegroups.com.

Re: [weewx-user] Re: pi is online and weewx driver is working - but not posting

[gjr80]

No no idea, have not used SDR myself. Maybe Matthew or others have come across 
changing sensor ids.

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/0dbbfea5-66ae-4c7f-8e39-23ff3e9c0506%40googlegroups.com.

Re: [weewx-user] Re: pi is online and weewx driver is working - but not posting

[Sean Jahnig]

Hi Gary,


Thanks for helping me troubleshoot. I found the problem.


In the sensor map i originally specified which items to capture by using
the identifier '013E' which i obtained by running *rtl_433 -M utc -F json
-G* and that was working for the last month until 3am this morning. Below
is what i was using:


wind_speed.013E.Acurite5n1Packet


Now, upon a closer inspection of running *rtl_433 -M utc -F json -G* again
i notice the identifier has changed to '0A0A'. So i updated the sensor map
in /etc/weewx/weewx.conf to use the new identifier and it all started
working.

wind_speed.0A0A.Acurite5n1Packet

Any ideas why that would've changed?


On Sun, Jan 12, 2020 at 12:12 PM gjr80  wrote:

> OK, so no luck there. I would be looking at your sensor map next. In your
> sensor map I see wind_speed but in the log I see the sdr driver finds
> wind_speed_kph. I would work through the steps in the sdr driver
> installation instructions  (https://github.com/matthewwall/weewx-sdr)
> from step 4 onwards to verify your sensor map is correct. Specifically,
> what does step 4 capture and what sensor map did you implement at step 5
> based on that capture.
>
> Gary
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/rlau4OqQTtY/unsubscribe.
> To unsubscribe from this group and all its topics, 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/fe850799-6774-4458-9f7f-2fe94b208820%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/CALeSoZn-vX0HZZi0v2sEj61wpkW8Mm-iAFDJsJENYvoffURkbQ%40mail.gmail.com.

[weewx-user] Re: wanted: users with ecowitt gw1000 wifi bridge

[mwall]

On Sunday, January 12, 2020 at 1:38:45 AM UTC-5, Gert Andersen wrote:
>
>
> Out running directly:
> pi@Desktop:~/weewx-interceptor/bin/user $ PYTHONPATH=/usr/share/weewx 
> python /usr/share/weewx/user/interceptor.py --device=ecowitt-client --port 
> 8000 --debug
> raw data: 
> PASSKEY=&stationtype=EasyWeatherV1.4.5&dateutc=2020-01-12+06:19:35&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.000&monthlyrainin=0.000&yearlyrainin=0.000&temp2f=43.7&humidity2=91&batt2=0&freq=868M&model=HP1000SE_Pro_V1.5.8
> raw packet: {'temperature_2': 43.7, 'humidity_2': 91.0, 'rain_rate': 0.0, 
> 'battery_2': 0.0, 'dateTime': 1578809975, 'usUnits': 1}
> mapped packet: {'temperature_2': 43.7, 'humidity_2': 91.0, 'rain_rate': 
> 0.0, 'battery_2': 0.0, 'dateTime': 1578809975, 'usUnits': 1}
>
> I have this in in weewx.conf:
> [Interceptor]
> driver = user.interceptor
> device_type = ecowitt-client
> port = 8000
>[[sensor_map]]
> outTemp = temperature_2
> outHumidity = humidity_2
>
>
i think you should use the sensor_map_extensions, not sensor_map.  so your 
configuration would look like this:

[Interceptor]
driver = user.interceptor
device_type = ecowitt-client
port = 8000
[[sensor_map_extensions]]
outTemp = temperature_2
outHumidity = humidity_2

that way all of the normal mappings will remain, and you only override 
outTemp and outHumidity to use the additional sensor.

m 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a45fa7cc-7537-42cd-a848-957a4141466a%40googlegroups.com.

[weewx-user] Re: wanted: users with ecowitt gw1000 wifi bridge

[mwall]

On Sunday, January 12, 2020 at 1:38:45 AM UTC-5, Gert Andersen wrote:
>
> Updated Interceptor to version 0.50
>
> and I get this error:
> Jan 12 07:27:17 Desktop weewx[2501]: Starting weewx weather system: weewx.
> Jan 12 07:27:17 Desktop weewx[2516]: interceptor: MainThread: driver 
> version is 0.50
> Jan 12 07:27:17 Desktop weewx[2516]: interceptor: MainThread: device type: 
> ecowitt-client
> Jan 12 07:27:17 Desktop weewx[2516]: engine: Import of driver failed: 
> 'InterceptorDriver' object has no attribute 'default_sensor_map' ( 'exceptions.AttributeError'>)
> Jan 12 07:27:17 Desktop weewx[2516]: engine: Unable to load driver: 
> 'InterceptorDriver' object has no attribute 'default_sensor_map'
> Jan 12 07:27:17 Desktop weewx[2516]:   Exiting...
>
> Im using the Ecowiit protocol from the console(HP2551-C)
>
> Any ideas?
>

sorry, the initialization of sensor_map was incorrect.  fixed at commit 
7ecaad0

please update to latest interceptor.py

-- 
You received this message because you are subscribed to the Google 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/ad5e94ea-fea6-4561-b358-5022f71f1cdd%40googlegroups.com.

Re: [weewx-user] Re: pi is online and weewx driver is working - but not posting

[gjr80]

OK, so no luck there. I would be looking at your sensor map next. In your 
sensor map I see wind_speed but in the log I see the sdr driver finds 
wind_speed_kph. I would work through the steps in the sdr driver installation 
instructions  (https://github.com/matthewwall/weewx-sdr) from step 4 onwards to 
verify your sensor map is correct. Specifically, what does step 4 capture and 
what sensor map did you implement at step 5 based on that capture.

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/fe850799-6774-4458-9f7f-2fe94b208820%40googlegroups.com.