OK, starting to test the limits of my networking knowledge. One last thing 
to try, let's make sure the interceptor is listening to the correct IP 
address (and only the correct IP address). In weewx.conf under [Interceptor] 
can you add and the address = 192,168.2.41, ie:

[Interceptor]
    ....
    device_type = observer
    address = 192.168.2.41
    ....

Save and restart WeeWX. 

I see you have now disabled WeeWX posting to WU, that may well fix the 
issue of the multiple duplicate packets but of course you have now lost the 
ability of posting to WU. If disabling WU in WeeWX settles things down you 
might want to try the adding the address setting above and enabling WU (but 
lets leave RF aside for now).

Taking a log extract from startup for a couple of archive periods should 
soon show if we are on track or not.

Gary

On Saturday, 23 May 2020 09:33:14 UTC+10, Zsolt Máté wrote:
>
> Right now I've disabled MQTT in weewx.conf, cleaned the future records 
> from the database, dropped and rebuild the daily stats. Last HTML generated 
> is more than 30 minutes old.
>
> To paint a picture of my setup:
> I'm running this weather station -> 
> https://www.jaycar.co.nz/7-inch-colour-wireless-weather-station/p/XC0370 - 
> IP address 192.168.2.60 that sends data to WU (intercepted)
> weewx is running in a proxmox container with the IP's 192.168.2.40 and 
> 192.168.2.41, 41 being the interceptor.
> On my router (openwrt), I've set up a rule, that the traffic from my PWS 
> should be forwarded to 192.168.2.41.
> iptables -t nat -A PREROUTING -s 192.168.2.60 -p tcp --dport 80 -j DNAT 
> --to-destination 192.168.2.41:80
> iptables -t nat -A POSTROUTING -j MASQUERADE
> Weewx is forwarding the intercepted data to WU.
> MQTT is used for the Belchertown skin (right now uninstalled) and to 
> integrate my weather data into Home Assistant.
>
>
> On Saturday, May 23, 2020 at 10:57:43 AM UTC+12, gjr80 wrote:
>>
>> Thanks. I am trying to get my head around what is going on here. There 
>> seems to be a lot of double handling (posting) of records, for example the 
>> 22 May 19:50:20 record is published by the MQTT uploader six times:
>>
>> May 22 19:50:28 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
>> record 2020-05-22 19:50:20 NZST (1590133820)
>> ...
>> May 22 19:50:29 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
>> record 2020-05-22 19:50:20 NZST (1590133820)
>> ...
>> May 22 19:50:44 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
>> record 2020-05-22 19:50:20 NZST (1590133820)
>> ...
>> May 22 19:50:50 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
>> record 2020-05-22 19:50:20 NZST (1590133820)
>> ...
>> May 22 19:51:00 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
>> record 2020-05-22 19:50:20 NZST (1590133820)
>> ...
>> May 22 19:51:16 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
>> record 2020-05-22 19:50:20 NZST (1590133820)
>>
>> I also see the interceptor is picking up a lot of what appears to be 
>> duplicate records some of which are HTTP POST and others HTTP GET. Can you 
>> clarrify your configuration? From the wee_debug report you have WeeWX 
>> uploading to WU both normal (every archive record) updates and rapid fire 
>> and you have WeeWX uploading to a MQTT broker every archive record and loop 
>> packet. Do you have your weather station uploading to WU? I am thinking it 
>> might be time to pare back to a bare bones setup by turning off a few 
>> services.
>>
>> Gary
>>
>> On Friday, 22 May 2020 18:36:29 UTC+10, Zsolt Máté wrote:
>>>
>>> It stopped updating the html at local 08:00PM, and in the log I see an 
>>> MQTT message dated tomorrow.
>>> It's MQTT related: May 22 20:00:20 weewx weewx[5569] INFO weewx.restx: 
>>> MQTT: Published record 2020-05-23 07:00:00 NZST (1590174000)
>>>
>>> Log from 10 minutes before until 10 minutes after 8PM -> 
>>> https://pastebin.com/K7s8e60V
>>>
>>

-- 
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/b7541bae-0b2b-4218-9151-1bf9824b2824%40googlegroups.com.

Reply via email to