[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

Thank you for your assistance. Support is great here. bell...@gmail.com schrieb am Mittwoch, 10. Februar 2021 um 22:45:36 UTC+1: > Unfortunately the message format doesn’t matter. The data is arriving > after the interval has been processed. From a MQTTSubscribe perspective, > the only thing

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

Unfortunately the message format doesn’t matter. The data is arriving after the interval has been processed. From a MQTTSubscribe perspective, the only thing I can think to do is, increase the interval... On Wednesday, 10 February 2021 at 13:49:45 UTC-5 kk44...@gmail.com wrote: > Ok, so it's

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

Ok, so it's no bug, but desired behavior. I was not aware of a thing called "archive_delay". There is no such option in my weewx.conf, and I did not know that it exists. In fact, the data received by MQTT are for the passed interval, but they come later, sometimes up to 1.5 minutes after.

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

Thanks for the log and configuration information. After working through it and WeeWX, I believe that everything is working as designed. >From the log, I will assume your archive_interval is 300 and archive_delay is 15. During this time of the log, MQTTSubscribe is chugging along, but nothing

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

I saved the requested data to the issue on github. bell...@gmail.com schrieb am Freitag, 5. Februar 2021 um 16:04:55 UTC+1: > And your MQTTSubscribe config settings, with any sensitive information > removed. > > On Friday, 5 February 2021 at 10:02:20 UTC-5 bell...@gmail.com wrote: > >>

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

And your MQTTSubscribe config settings, with any sensitive information removed. On Friday, 5 February 2021 at 10:02:20 UTC-5 bell...@gmail.com wrote: > Interesting. I might have to give you a version with extra logging. In > the meantime, could you attach the log. > Thanks. -rich > > On

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

Interesting. I might have to give you a version with extra logging. In the meantime, could you attach the log. Thanks. -rich On Friday, 5 February 2021 at 09:25:20 UTC-5 kk44...@gmail.com wrote: > There is an issue I observed: > > If the MQTT message is received some little seconds after the

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

There is an issue I observed: If the MQTT message is received some little seconds after the archive interval ends, then the loop record shows the new received value, but the archive record shows the old value from the previous interval. example: archive interval ends at 15:00:00. MQTT message

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

On Thursday, February 4, 2021 at 11:50:29 AM UTC-8 kk44...@gmail.com wrote: > As I did not really know how to update an extension, > Just install the new one. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

I am looking for the thumb-up smiley. As I did not really know how to update an extension, I uninstalled the old version first. After that I installed the version 2.0.0-rc04. That process removed part of the configuration data, but no problem, there was a backup. Now I see values every archive

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

Karen, Without doing a deep analysis on your log, I can't explain what you are seeing. I am pretty sure that the problem is a mismatch of the cache key, resulting in nothing being cached. I have created a release with an update that should fix this. It can be found here,

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

I looked at it again, and I think, I found something. This is a list of the archive records, and whether the MQTT data are included or not: 15:15:14 included 15:10 missing 15:05:16 included 15:00:14 included 14:55 missing 14:50:16 included 15:45:14 included 15:40 missing

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

I looked for all messages that contain self.cached_fields. /var/log/syslog.2.gz:Jan 30 16:51:45 LokalWiki weewx[1003818] DEBUG user.MQTTSubscribe: (Service) TopicManager self.cached_fields is {} /var/log/syslog.2.gz:Jan 30 17:07:40 LokalWiki weewx[1004756] DEBUG user.MQTTSubscribe: (Service)

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

Karen, I think a couple of things are going on. In your log snippet I see: Jan 30 17:32:18 LokalWiki weewx[1005876] DEBUG user.MQTTSubscribe: (Service) TopicManager *self.cached_fields is {}* Is this set in your second run? If so, what are the values? I’d expect it is now set, but but the key is

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

The use_topic_as_fieldname option worked. (Nevertheless, I find it confusing to set the option to "true" to _not_ using the topic as field name in WeeWX.) Unfortunately it does not cache. If I see the value for one archive interval, it is gone for the next. It shows the parameter name enclosed

[weewx-user] Re: MQTTSubscribe and topics, that are seldom sent

The subscription to the ‘wind’ topic is just some code that needs to be cleaned up. Tracking via #119 . You also need the ‘use_topic_as_fieldname = True’ option. Additional information is here