Seems like now weewx MQTT is emitting a message every time a LOOP packet 
arrives. Let me guess, you hardware is capable of measuring wind/gusts in a 
2.5s interval, maybe a Tempest?
I don't know why this has changed, does Belchertown let you set the 
interval? Usually you set this like described 
here: 
https://github.com/matthewwall/weewx-mqtt/blob/d1739f3d57f07f402ddd3c20ac10ad5f874be1e9/bin/user/mqtt.py#L33
Mario Wesolek schrieb am Freitag, 9. Februar 2024 um 12:07:05 UTC+1:

> After update to 5.0.1-4  the MQTT publish data every 2-5 seconds ... have 
> anyone an explanation or can tell me where i can setup the publish time?
>
> Feb  9 12:04:08 weewx chronyd[522]: Selected source 217.197.91.176 (
> de.pool.ntp.org)
> Feb  9 12:04:09 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:10 CET (1707476650)
> Feb  9 12:04:12 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:12 CET (1707476652)
> Feb  9 12:04:14 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:15 CET (1707476655)
> Feb  9 12:04:17 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:17 CET (1707476657)
> Feb  9 12:04:19 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:20 CET (1707476660)
> Feb  9 12:04:22 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:22 CET (1707476662)
> Feb  9 12:04:24 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:25 CET (1707476665)
> Feb  9 12:04:27 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:27 CET (1707476667)
> Feb  9 12:04:29 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:30 CET (1707476670)
> Feb  9 12:04:32 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:32 CET (1707476672)
> Feb  9 12:04:34 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:35 CET (1707476675)
> Feb  9 12:04:37 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:37 CET (1707476677)
> Feb  9 12:04:39 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:40 CET (1707476680)
> Feb  9 12:04:42 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:42 CET (1707476682)
> Feb  9 12:04:44 weewx weewxd[716]: INFO weewx.restx: MQTT: Published 
> record 2024-02-09 12:04:45 CET (1707476685)
>
> thank you very much!
> mario 
> dg1fi 
>
> Mario Wesolek schrieb am Dienstag, 6. Februar 2024 um 10:42:58 UTC+1:
>
>> hi there!
>>
>> i use weewx with belchertown skin and publish the data via mqtt. in 
>> versions < 5.0.1 mqtt publish the data to every full minute, like 10:01:00, 
>> 10:02:00 and so on... after upgrade the time is uneven, like:
>>
>> Feb  6 09:56:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published 
>> record 2024-02-06 09:56:50 CET (1707209810)
>> Feb  6 09:57:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published 
>> record 2024-02-06 09:57:50 CET (1707209870)
>> Feb  6 09:58:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published 
>> record 2024-02-06 09:58:51 CET (1707209931)
>> Feb  6 09:59:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published 
>> record 2024-02-06 09:59:51 CET (1707209991)
>> Feb  6 10:00:51 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published 
>> record 2024-02-06 10:00:00 CET (1707210000)
>> Feb  6 10:00:51 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published 
>> record 2024-02-06 10:00:52 CET (1707210052)
>>
>> this is not really a problem but i will understand the reason. have 
>> anybody a explanation? 
>>
>> thank you very much!
>> mario 
>>
>

-- 
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/5a259c50-9811-4c0a-a4ef-9fab88ca1361n%40googlegroups.com.

Reply via email to