INFO user.interceptor: unrecognized parameter

[Brian Watson]

Hi,

I've been running weewx for a while, but new to the group.  I have an Ambient Weather WS-2902D and my only reason for running weewx is to have my data stored locally and not depend on ambientweather.net.  It's been working exactly as I had hoped, but I just moved my station and an external sensor and needed to rename some things and I seem to have confused the interceptor driver.  I've done some debugging and have some questions.

I'm running the "matthewwall/weewx-interceptor" driver.  This hasn't been touched in 5 years.  I've seen reference to other forks, but have not been able to find them.  Is this the recommended version, or is there another?

Prior to the relocation I didn't care about the data from the 2nd sensor as it was in the wrong place anyway.  Now that it's in the correct place I want to start collecting the data.  Ambient Weather calls the data from this sensor "temp2f" and "humidity2".  These are not in the default, extended, schema so I added:

[[sensor_map]]
       extraHumid1 = humidity2  
       extraTemp1 = temp2f

to the [Interceptor] section of my config file.  I can see in the logs that the map is being used.

I'm not getting data for these sensors in the database and I have:

Mar 18 13:05:15 slug weewxd[2983454]: INFO user.interceptor: unrecognized parameter temp2f=60.6
Mar 18 13:05:15 slug weewxd[2983454]: INFO user.interceptor: unrecognized parameter humidity2=37

in my logs.  I've tried swapping the order of the map elements in the config file with no change.

Should this work?  What am I missing?

Thanks,

Brian

[Vince Skahan]

What does the [Interceptor] section in weewx.conf look like ?

Quick look at the code of 'unrecognized parameter' shows that in 4 sections of the driver.  Three of them know of those items.  The AcuriteBridge section does not seem to know of them.

Assuming you're set to acurite-bridge take a look around line 980-1035 in interceptor.py and where you might try adding those elements.  Sorry - the code/comments/readme info are too skeletal for me to suggest a patch.

[Brian Watson]

Not a great start to my group membership - I solved this myself not long after posting.

Turns out I had been running the wrong interceptor configuration all along - I had interceptor configured to accept "observer" data, but I was sending it "wu". Enough fields match that I didn't notice until I tried to use the extra sensor.

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 visit https://groups.google.com/d/msgid/weewx-user/dfce1e4a-e8ca-40eb-9145-f38f0f68e240n%40googlegroups.com.