[weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-13 Thread Karen K
Yes, it works. So the problem was not within MQTTSubscribe service, but in the configuration of the accumulator service. And it was no software issue, but a knowledge issue of the user. :-) Karen K schrieb am Donnerstag, 11. Februar 2021 um 10:11:48 UTC+1: > That's new to me. Thank you very muc

[weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-11 Thread Karen K
That's new to me. Thank you very much for that information. I will try it. bell...@gmail.com schrieb am Mittwoch, 10. Februar 2021 um 19:56:29 UTC+1: > Yes, it would be something like > [Accumulator] > [[W567470c]] > accumulator = firstlast > extractor = last > > See, https://

[weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-10 Thread bell...@gmail.com
Yes, it would be something like [Accumulator] [[W567470c]] accumulator = firstlast extractor = last See, https://github.com/weewx/weewx/wiki/Accumulators for additional information On Wednesday, 10 February 2021 at 13:51:08 UTC-5 kk44...@gmail.com wrote: > There is no such s

[weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-10 Thread Karen K
There is no such section. Should I have one? bell...@gmail.com schrieb am Mittwoch, 10. Februar 2021 um 19:44:55 UTC+1: > Looks like a bug when running as a service, I'll take a look. > What does your [Accumulator] section look like? > > On Wednesday, 10 February 2021 at 13:41:47 UTC-5 kk44...@gm

[weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-10 Thread bell...@gmail.com
Looks like a bug when running as a service, I'll take a look. What does your [Accumulator] section look like? On Wednesday, 10 February 2021 at 13:41:47 UTC-5 kk44...@gmail.com wrote: > For me it still does not work. > > The configuration is: > [[[pegel/567470/alarmcolor]]] > name = W567470c

[weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-10 Thread Karen K
For me it still does not work. The configuration is: [[[pegel/567470/alarmcolor]]] name = W567470c conversion_type = None expires_after = 4000 And the log is: Feb 10 19:32:47 LokalWiki weewx[378692] CRITICAL __main__: Caught unrecoverable exception: Feb 10 19:32:47 LokalWiki wee

[weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-08 Thread Tarmo
"If you get this working, I’d like to ‘steal’ the details/steps for a wiki page. -rich" you own this. this is your work and people around the world are thankful for this. On Monday, February 8, 2021 at 3:19:36 AM UTC+2 bell...@gmail.com wrote: > It should be doable. I do something similar wit

Re: [weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-08 Thread Tarmo
Thank you very much! The last one works like a charm. The string is accessible by $current.phenomenon.raw On Monday, February 8, 2021 at 9:30:58 PM UTC+2 bell...@gmail.com wrote: > Try adding a name = > > [[[emhi/26038/phenomenon]]] > *name = phenomenon* > conve

Re: [weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-08 Thread bell...@gmail.com
Try adding a name = [[[emhi/26038/phenomenon]]] *name = phenomenon* conversion_type = None Yeah, I know configuring payloads of type ‘individual’ needs to be reworked... rich On Monday, 8 February 2021 at 13:47:52 UTC-5 bell...@gmail.com wrote: > Thanks for the

Re: [weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-08 Thread bell...@gmail.com
Thanks for the log. Definitely a MQTTSubscribe bug with the name. I’ll look into it. Feb 8 20:28:53 pi3 weewx[3513] DEBUG user.MQTTSubscribe: (Driver) data-> final loop packet is emhi/26038/phenomenon 2021-02-08 20:28:52 EET (1612808932): dateTime: 1612808932.5151372, *emhi/26038/phenomenon*: C

Re: [weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-08 Thread Tarmo
debug = 1 log attached Feb 8 20:28:51 pi3 systemd[1]: Starting LSB: weewx weather system... Feb 8 20:28:52 pi3 weewx[3508] INFO __main__: Initializing weewx version 4.4.0 Feb 8 20:28:52 pi3 weewx[3508] INFO __main__: Using Python 3.5.3 (default, Nov 18 2020, 21:09:16) #012[GCC 6.3.0 20170516]

Re: [weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-08 Thread bell...@gmail.com
The other possibility is that the field/type in the packet generated by MQTTSubscribe is not phenomenon. From the config, it looks like it should be. If you set debug = 1, we can see what MQTTSubscribe is putting in the packet. For what's worth, I got a small testcase working and see string data

Re: [weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-08 Thread Tom Keffer
The error you are getting is coming from the ScalarStats accumulator, not the FirstLast accumulator. For some reason, the latter is not getting used, despite your configuration information (which looks correct). Is there another type besides phenomenon which has a string in it? -tk On Mon, Feb 8

[weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-08 Thread Karen K
I had the same problem. It seems to me that weewx does not know string values. I tried to send an alarm color value that way, to no success. Tarmo schrieb am Montag, 8. Februar 2021 um 10:46:40 UTC+1: > Thank you! > > It seems that the attempt to convert string to float still happens. I will >

[weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-08 Thread Tarmo
Thank you! It seems that the attempt to convert string to float still happens. I will attach snippets from log and config here. The field name which is causing trouble is "phenomenon". [MQTTSubscribeDriver] # This section is for the MQTTSubscribe driver. # The driver to use: driver

[weewx-user] Re: MQTTSubscribe - Presenting a field-name without storing it in the database

2021-02-07 Thread bell...@gmail.com
It should be doable. I do something similar with a few temperature sensors/fields. The fact that you are dealing with string data does add some complexity. First, for the field configuration you will need to set the conversion_type = None. Although it is not documented on the wiki, see https://