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

Thanks for the reply. I changed the archive interval back to 300 and rebooted. The system has been online for 3 hours now and it's still now posting. Any other ideas? On Sun, 12 Jan 2020, 09:59 gjr80, wrote: > Hi, > > The lack of posting to external services (at present) has nothing to do >

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

Hi I have missed something. Updated Interceptor to version 0.50 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:

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

Hi, The lack of posting to external services (at present) has nothing to do with connectivity. If you look at the log your system is not generating any archive records, the windy uploader is bound to the NEW_ARCHIVE_RECORD event so uploads are only triggered when a new archive record is

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

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

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

Hi, This is a different station that i setup about a month ago. This is using an Acurite 5-in-1 with and SDR dongle - no displays involved. The station has been online for the last 1 month with no problems. Today i woke up and the despite everything being online, the data is not being uploaded

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

Doing a strace running weewxd I am getting this stat64("/usr/share/weewx/swig_runtime_data4", 0x7e9d9ba8) = -1 ENOENT (No such file or directory) open("/usr/share/weewx/swig_runtime_data4.arm-linux-gnueabihf.so", O_RDONLY| O_LARGEFILE) = -1 ENOENT (No such file or directory)

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

pycap starts to run but then exits causes weewx to fail again. interceptor: ServerThread: start sniff server engine: Loading service w interceptor: MainThread: shutting down server thread interceptor: MainThread: stop sniff server interceptor: MainThread: unable to shut down server thread

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

On Saturday, January 11, 2020 at 4:51:30 PM UTC-5, Scott Grayban wrote: > > I tried pycap and that did run for a few seconds. > > Jan 11 00:39:13 weewx-pi weewx[3942]: engine: Loading station type > Interceptor (user.interceptor) > Jan 11 00:39:13 weewx-pi weewx[3942]: interceptor: MainThread:

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

I was getting that error BEFORE I did the upgrade though. On Saturday, January 11, 2020 at 4:54:18 PM UTC-8, mwall wrote: > > > > On Saturday, January 11, 2020 at 7:45:59 PM UTC-5, Scott Grayban wrote: >> >> Honestly I don't remember what version of Interceptor I was running >> before. I did a

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

For the record I was using the gw1000 ecowitt protocol On Saturday, January 11, 2020 at 5:33:39 PM UTC-7, mwall wrote: > > when you post the output from interceptor, please indicate whether the > capture is from a gw1000 using wu protocol or a gw1000 using ecowitt > protocol > -- You received

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

On Saturday, January 11, 2020 at 7:45:59 PM UTC-5, Scott Grayban wrote: > > Honestly I don't remember what version of Interceptor I was running > before. I did a update because like I said I hadn't messed with it since > last June so it could have been .46 > > I did a apt upgrade after I

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

Actually your driver I used was around Mar 8, 2019 because that's when I wrote the Hostapd doc. https://github.com/weewx/weewx/wiki/hostapd-WiFi-setup-for-Interceptor-driver On Saturday, January 11, 2020 at 4:42:13 PM UTC-8, mwall wrote: > > > > On Saturday, January 11, 2020 at 12:25:35 AM

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

Honestly I don't remember what version of Interceptor I was running before. I did a update because like I said I hadn't messed with it since last June so it could have been .46 I did a apt upgrade after I couldn't get weewx running but non of those packages involved python. On Saturday,

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

On Saturday, January 11, 2020 at 12:25:35 AM UTC-5, Scott Grayban wrote: > > I did a restart tonight and weewx wouldn't start. Saw this in the logs and > cannot figure out why this is happening. I checked all my configs and they > are right, haven't touched then since last June. > >

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

when you post the output from interceptor, please indicate whether the capture is from a gw1000 using wu protocol or a gw1000 using ecowitt protocol -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop

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

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,

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

I just disabled that skin also and used a different skin and same error. On Saturday, January 11, 2020 at 4:19:58 PM UTC-8, mwall wrote: > > On Saturday, January 11, 2020 at 12:25:35 AM UTC-5, Scott Grayban wrote: >> >> I did a restart tonight and weewx wouldn't start. Saw this in the logs >>

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

I added a custom page to my skin and that was it. I removed the changes and attempted a restart and it still wouldn't run. On Saturday, January 11, 2020 at 4:19:58 PM UTC-8, mwall wrote: > > On Saturday, January 11, 2020 at 12:25:35 AM UTC-5, Scott Grayban wrote: >> >> I did a restart tonight

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

On Saturday, January 11, 2020 at 12:25:35 AM UTC-5, Scott Grayban wrote: > > I did a restart tonight and weewx wouldn't start. Saw this in the logs and > cannot figure out why this is happening. I checked all my configs and they > are right, haven't touched then since last June. > > weewx[5862]:

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

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

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

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

[weewx-user] Re: VP 2 archive interval vs database vs Wunderground update

Great. Thanks for the help! On Saturday, January 11, 2020 at 12:09:04 PM UTC-8, vince wrote: > > On Saturday, January 11, 2020 at 11:45:22 AM UTC-8, brisguy foo wrote: >> >> so apparently, I am using SQLite even though I did not do anything other >> than the normal weewx install. >> > > Yes -

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

I tried pycap and that did run for a few seconds. Jan 11 00:39:13 weewx-pi weewx[3942]: engine: Loading station type Interceptor (user.interceptor) Jan 11 00:39:13 weewx-pi weewx[3942]: interceptor: MainThread: driver version is 0.49 Jan 11 00:39:13 weewx-pi weewx[3942]: interceptor:

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

No system update. Still running Raspbian 9 on it. weeWX 3.9.2 Python 2.7.13 DRIVER_NAME = 'Interceptor' DRIVER_VERSION = '0.49' [Interceptor] driver = user.interceptor device_type = observer mode = sniff iface = wlan0 pcap_filter = src 10.3.141.62 and dst port 80

[weewx-user] Problems with generating history tables.

Hi! trying to add the html historic data tables in a nice colour scheme. Added these lines to [CheetahGenerator] in skin.conf: user.historygenerator.MyXSearch, user.stats.MyStats Added stats.py from /usr/share/doc/weewx/examples to my /usr/share/weewx/user folder This is the output from log

[weewx-user] Re: VP 2 archive interval vs database vs Wunderground update

On Saturday, January 11, 2020 at 11:45:22 AM UTC-8, brisguy foo wrote: > > so apparently, I am using SQLite even though I did not do anything other > than the normal weewx install. > Yes - sqlite3 is the default Will this db have all the data from my data logger or just the new records > that

[weewx-user] VP 2 archive interval vs database vs Wunderground update

Hi All, Just got weewx running last week on a RP zero and have it successfully uploading to Wunderground. I did not opt for the Rapidfire mode since the user info seemed to indicate this was risky and/or unnecessary. As a result, my PWS page only updates once every 30 minutes since that is

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

Here is a link to check out: *https://github.com/poblabs/weewx-belchertown/wiki/Adding-a-new-observation-type-to-the-WeeWX-database* On Saturday, January 11, 2020 at 1:05:15 PM UTC-5, Paul

[weewx-user] Re: MQTT for remote site and min data transfer - MQTT Driver as input to weewx

Time to revisit this old post as I finally spent some time with morrowwm's wxMesh driver to make slight modifications required for this use case. It has been working well for the last week and I am making it available in case it may be useful for someone else. If there is sufficient interest

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

I just changed over from a Lacross Gateway to an Ambient WS-2000 and an ECOWITT GW1000BU. I loaded the updated interceptor, everything working pretty well with a couple of issues. 1. I had to change the mapping in the driver for solarradiation. the driver mapped solarradiation to

Re: [weewx-user] Adding alternative source for a sensor data

Rich, Thanks a lot for your suggestion. The new sensor arrived earlier this week and I was able to install it to day. Fortunately, the replacement was easy. Even though my unit is listed as compatible, it does have a socketed sensor inside, so it was an easy plug and play. See image below

Re: [weewx-user] Delete data between two time points

Bingo! Thank you for your help. Neil On Saturday, 11 January 2020 14:46:36 UTC, Thomas Keffer wrote: > > It's actually much simpler. The field 'dateTime' is already in unix epoch > time. So, you want > > * delete from archive where dateTime>1578739140 and dateTime<1578741360;* > > Then

Re: [weewx-user] Delete data between two time points

It's actually much simpler. The field 'dateTime' is already in unix epoch time. So, you want * delete from archive where dateTime>1578739140 and dateTime<1578741360;* Then rebuild the daily summaries. -tk On Sat, Jan 11, 2020 at 7:29 AM Neil S wrote: > I am trying to delete data between two

[weewx-user] Delete data between two time points

I am trying to delete data between two time points as it is erroneous (I updated and for a short period the station type was reset to simulate). The time points are 11/1/20 at 10:39:00 and 11:16:00 (so I think I have the right unixepoch timestamps) I have worked out how to delete data that is

Re: [weewx-user] Re: anti_alias shrinks plot letters

The anti-alias scheme increases the image size, does the drawing, then shrinks it back down. The font size will fail if the plotting routine is forced to use a default font, which does not have an ability to scale it. Try specifying fonts that you know are available on your machine. -tk On

[weewx-user] Re: anti_alias shrinks plot letters

Thanks to gjr80, now I finally see in color :) So, this second part of my post is now solved. Answer was: I was using HTML color RGB codes and colors must be BGR. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group

Re: [weewx-user] Re: US - Metric problem

Ye! Thank you! Since I did not see any particular explanation, I entered HTML colour codes :) Figuring, it is going to HMTL page. This sentence of yours certanly should find its way to docs :)) -- You received this message because you are subscribed to the Google Groups "weewx-user"

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

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,

[weewx-user] Re: Image backup vs database

Hi all, Thank you for your advice. I now only backup an image after a major change and create a log for the smaller changes. With a logbook and the daily backup of the files specified by Weewx, things have to go well. Regards, Keimpe Op vrijdag 10 januari 2020 19:23:31 UTC+1 schreef Keimpe

[weewx-user] anti_alias shrinks plot letters

[image: daySmarttemp alias1.png] If I change Smartphone skin.conf anti_alias from 1 to 2, plots clean up nicely but all letters shrink to illegible size, as evidenced by attached plots. Why would anti_alias affect letters at all? What is a solution? To change all plot letter sizes

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

Jan 11 00:06:14 weewx-pi weewx[1417]: engine: Loading station type Interceptor (user.interceptor) Jan 11 00:06:14 weewx-pi weewx[1417]: interceptor: MainThread: driver version is 0.49 Jan 11 00:06:14 weewx-pi weewx[1417]: interceptor: MainThread: device type: observer Jan 11 00:06:14

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

On Saturday, January 11, 2020 at 12:36:15 AM UTC-5, Scott Grayban wrote: > > Running the Interceptor manuall works just fine so I know it's not that > did you do a system update? what version of weewx is this, what version of python, and what version of the weewx-interceptor? also,