This is what is in my weewx.conf, seems a little different to yours.
[Interceptor]
# This section is for the network traffic interceptor driver.
# The driver to use:
driver = user.interceptor
# 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
device_type = fineoffset-bridge
port = 8000
[[sensor_map_extensions]]
windBatteryStatus = wh68_battery
txBatteryStatus = wh26_battery
supplyVoltage = wh40_battery
On Tuesday, April 28, 2020 at 2:08:55 PM UTC-4, Max Gutberlet wrote:
>
> LOL - literally the first thing I checked :-) Yep, the packets (in
> wireshark) are still comming in on eth0.
>
> I did some more investigation, this is starting to look like a python3.8
> with interceptor problem. My station actually talks ecowitt as well, so I
> configured
> it to send ecowitt to my server and started interceptor in listen mode für
> ecowitt as a standalone using
>
> PYTHONPATH=bin python3 bin/user/interceptor.py --device=ecowitt-client
> --mode=listen --port=9988
>
> same "no data received" behaviour and you have to actually kill the
> process, a control-c does not stop it which also hints at something
> "hanging".
>
> I am currently playing with an alternative ecowitt implementation
> https://github.com/iz0qwm/ecowitt_http_gateway but that also gives me a
> lot of
> python errors on identation :-(
>
> Any help greatly appreciated ! I still hope I am "just" misconfiguring
> something.....
> Thx
> Max
>
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/0d459179-d459-46d0-887a-b0f9c840c9ae%40googlegroups.com.
