I'm not sure you should have pressure and barometer and altimeter all 
coming from barometer.  The accurite should only be providing one pof the 
three values - and let weews derive the other two if necessary by 
specifying 'software'. The three values should be different values in the 
archive.

On Saturday, 3 November 2018 08:56:05 UTC+2, Kevin Key wrote:
>
> I got it to work!  
>
> For anyone else searching for an answer and reading this, here's what I 
> did:
>
> Install the Interceptor plugin (as mentioned earlier).
>
> Connected the Acurite Access via a bridged connection on the Raspberry Pi.
>
> Specified the "Observer" hardware.
>
> In weewx.conf:
>
> Scroll down to the "" section and make sure it looks like this:
>
> [Interceptor]
>     # This section is for the network traffic interceptor driver.
>
>     # The driver to use:
>     driver = user.interceptor
>     device_type = observer
>     mode = sniff
>     iface = eth0
>     port = 80
>     pcap_filter = src net 192.168.6.0/24 && dst port 80
>     # NOTE: You'll need to change the above pcap_filter IP address range 
> to match that of the one you assigned to the ethernet port on your own 
> Raspberry Pi. 
>
>     # Specify the hardware device to capture.  Options include:
>     #   acurite-bridge - acurite internet bridge
>     #   observer - fine offset WH2600/HP1000/HP1003, aka 'observer'
>     #   lw30x - oregon scientific LW301/LW302
>     #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
>     [[sensor_map]]
>         pressure = barometer
>         barometer = barometer
>         altimeter = barometer
>         outHumidity = humidity_out
>         outTemp = temperature_out
>         windSpeed = wind_speed
>         windGust = wind_gust
>         windDir = wind_dir
>         dewpoint = dewpoint
>         rain = rain_total
>
>
> On Thu, Nov 1, 2018 at 10:42 AM vince <[email protected] <javascript:>> 
> wrote:
>
>> On Thursday, November 1, 2018 at 9:00:22 AM UTC-7, Andrew Milner wrote:
>>>
>>> This post referred to the bridge rather than the sensors - and Matthew's 
>>> post implies it is only encrypted from bridge to servers so SDR should 
>>> still work with the sensors I believe (don't think they are new) - however 
>>> there is no way of knowing if new sensors will be plain or encrypted in the 
>>> future!!
>>>
>>> On Thursday, 1 November 2018 16:51:37 UTC+2, Andy wrote:
>>>>
>>>> Can we still use the SDR driver? Is Acurite encrypting the traffic from 
>>>> the sensors to the console on new hardware?
>>>>
>>>
>> A little googling led me to a bunch of threads seeming to say that some 
>> folks had gotten a SDR type solution working at least notionally.  Try a 
>> google search for "acurite access with weewx" and look at the threads there 
>> especially the ones on wxforum.net
>>
>> Shorter answer is 'some work will probably be required, as it's always 
>> more work to go first (or close to first)'
>>
>> There's a lot of chatter on wxforum.net and other sites about Acurite 
>> doing things like actually turning off their customer support forums (I 
>> didn't check to verify this), but FWIW that company sure doesn't have the 
>> best of reputations these days.....
>>  
>>
>> -- 
>> 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 [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

Reply via email to