Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Jamie Stephens]

FYI no issues  with Tom’s driver.  Just not registered

On Fri, Feb 23, 2024 at 9:29 PM Jamie Stephens 
wrote:

> I'm not code savvy but I seem to recall I personally was running this fork
> from tkeffer that he ported to python 3
> https://github.com/tkeffer/weatherflow-udp/tree/master
> I might roll back tot hat and see if the issue go away, I don't think it
> was ever committed to the main
>
> On Friday, February 23, 2024 at 8:29:23 PM UTC-5 vince wrote:
>
>> Source is at
>> https://github.com/captain-coredump/weatherflow-udp/blob/master/bin/user/weatherflowudp.py
>>  if
>> some driver experts wanted to suggest fixes. This one is beyond me other
>> than to suggest that since weewx v5 does not support python2 anymore that
>> perhaps the try/except block needs something tweaked to deal with what I'm
>> guessing (like totally guessing) is garbage-in a little more gracefully
>> (anybody ?)
>>
>> if timeouterr == 0:
>> try:
>> m0 = str(m[0],'utf-8').replace(",null",",None")#
>> Python 3
>> except:
>>
>> m0 = m[0].replace(",null",",None") #
>> Python 2
>> m1=''
>> try:
>> m1=eval(m0)
>> except SyntaxError:
>> logerr('Packet parse error: %s' % m0)
>> if self._log_raw_packets:
>> loginf('raw packet: %s' % m1)
>> m2=parseUDPPacket(m1)
>> m3=sendMyLoopPacket(m2, self._sensor_map)
>> if len(m3) > 2:
>> yield m3
>>
>> On Friday, February 23, 2024 at 12:10:54 PM UTC-8 Jamie Stephens wrote:
>>
>> i went ahead and opened up a issue with the driver, had another crash
>> today
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/JWTsu4s3TvY/unsubscribe.
> To unsubscribe from this group and all its topics, 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/8b15753c-088a-449b-87af-d7b37de9a15en%40googlegroups.com
> 
> .
>

-- 
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/CABWMpWRZrKJp_0Yv281FiPtscnEOY3FeaMUc6ubrbJtrZe5S3Q%40mail.gmail.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Jamie Stephens]

I'm not code savvy but I seem to recall I personally was running this fork 
from tkeffer that he ported to python 3 
https://github.com/tkeffer/weatherflow-udp/tree/master
I might roll back tot hat and see if the issue go away, I don't think it 
was ever committed to the main

On Friday, February 23, 2024 at 8:29:23 PM UTC-5 vince wrote:

> Source is at 
> https://github.com/captain-coredump/weatherflow-udp/blob/master/bin/user/weatherflowudp.py
>  if 
> some driver experts wanted to suggest fixes. This one is beyond me other 
> than to suggest that since weewx v5 does not support python2 anymore that 
> perhaps the try/except block needs something tweaked to deal with what I'm 
> guessing (like totally guessing) is garbage-in a little more gracefully 
> (anybody ?)
>
> if timeouterr == 0:
> try:
> m0 = str(m[0],'utf-8').replace(",null",",None")# 
> Python 3
> except:
>
> m0 = m[0].replace(",null",",None") # 
> Python 2
> m1=''
> try:
> m1=eval(m0)
> except SyntaxError:
> logerr('Packet parse error: %s' % m0)
> if self._log_raw_packets:
> loginf('raw packet: %s' % m1)
> m2=parseUDPPacket(m1)
> m3=sendMyLoopPacket(m2, self._sensor_map)
> if len(m3) > 2:
> yield m3
>
> On Friday, February 23, 2024 at 12:10:54 PM UTC-8 Jamie Stephens wrote:
>
> i went ahead and opened up a issue with the driver, had another crash today
>
>

-- 
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/8b15753c-088a-449b-87af-d7b37de9a15en%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[vince]

Source is at 
https://github.com/captain-coredump/weatherflow-udp/blob/master/bin/user/weatherflowudp.py
 if 
some driver experts wanted to suggest fixes. This one is beyond me other 
than to suggest that since weewx v5 does not support python2 anymore that 
perhaps the try/except block needs something tweaked to deal with what I'm 
guessing (like totally guessing) is garbage-in a little more gracefully 
(anybody ?)

if timeouterr == 0:
try:
m0 = str(m[0],'utf-8').replace(",null",",None")# 
Python 3
except:
m0 = m[0].replace(",null",",None") # 
Python 2
m1=''
try:
m1=eval(m0)
except SyntaxError:
logerr('Packet parse error: %s' % m0)
if self._log_raw_packets:
loginf('raw packet: %s' % m1)
m2=parseUDPPacket(m1)
m3=sendMyLoopPacket(m2, self._sensor_map)
if len(m3) > 2:
yield m3

On Friday, February 23, 2024 at 12:10:54 PM UTC-8 Jamie Stephens wrote:

i went ahead and opened up a issue with the driver, had another crash today

-- 
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/091809f3-9964-4bc5-a5fd-8b407425eb52n%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Jamie Stephens]

i went ahead and opened up a issue with the driver, had another crash today

On Thursday, February 22, 2024 at 1:20:16 PM UTC-5 vince wrote:

> Jamie - I didn't change anything related to how the driver actually works. 
>  I just added one line to hopefully get it to register vs. v5 weewx.  The 
> map shows a few v5 sites using that driver now, so that part seems to be 
> working.
>
> On Thursday, February 22, 2024 at 7:24:23 AM UTC-8 Jamie Stephens wrote:
>
>> Thanks Tom, this is the new updated driver that Vince got pushed on this 
>> thread. maybe it was a one off 
>>
>> On Thursday, February 22, 2024 at 10:07:45 AM UTC-5 Tom Keffer wrote:
>>
>>> It looks like the author of the driver is trying to insert a string into 
>>> a byte array. You should file an issue on the repository's issue list.
>>>
>>> On Thu, Feb 22, 2024 at 6:00 AM Jamie Stephens  
>>> wrote:
>>>
 i manually restarted it and it's running right now just the registry 
 push error but not exited 
 Feb 22 08:50:19 weewx weewxd[68909]: ERROR weewx.restx: 
 StationRegistry: Failed to publish record 2024-02-22 08:50:00 EST 
 (17086098>

 will report back if weewx crashes again

 On Monday, February 19, 2024 at 7:09:16 PM UTC-5 Jamie Stephens wrote:

> Thanks for the fix, I didn't;t even noticed it was not working
>
> On Monday, February 19, 2024 at 4:25:28 AM UTC-5 Ton Karsten wrote:
>
>> Thank you for resolving the error message.
>>
>> Op ma 19 feb 2024 om 01:36 schreef bell...@gmail.com <
>> bell...@gmail.com>:
>>
>>> Thanks for pushing it over the goal line. Always the hardest part.
>>>
>>> On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:
>>>
 Update - the upstream author was nice enough to merge my PR for 
 this problem, so you can simply upgrade your driver to the latest 
 version 
 and your station registration should work again with weewx v5.

 weectl extension install 
 https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
 sudo systemctl restart weewx

 After upgrading your driver you should see the following output 
 from 'weectl extension list':

 Extension NameVersion   Description
 weatherflowudp1.10.2Capture data from WeatherFlow Bridge 
 via UDP broadcast packets

 Thanks again Rich for the nudge(s) !!!

 -- 
>>> 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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>> -- 
 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+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/2f38f991-b58b-4a9c-ad95-21a63311bb90n%40googlegroups.com
  
 
 .

>>>

-- 
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/a4287633-30a6-490a-9621-c2ee3c6a5323n%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[vince]

Jamie - I didn't change anything related to how the driver actually works. 
 I just added one line to hopefully get it to register vs. v5 weewx.  The 
map shows a few v5 sites using that driver now, so that part seems to be 
working.

On Thursday, February 22, 2024 at 7:24:23 AM UTC-8 Jamie Stephens wrote:

> Thanks Tom, this is the new updated driver that Vince got pushed on this 
> thread. maybe it was a one off 
>
> On Thursday, February 22, 2024 at 10:07:45 AM UTC-5 Tom Keffer wrote:
>
>> It looks like the author of the driver is trying to insert a string into 
>> a byte array. You should file an issue on the repository's issue list.
>>
>> On Thu, Feb 22, 2024 at 6:00 AM Jamie Stephens  
>> wrote:
>>
>>> i manually restarted it and it's running right now just the registry 
>>> push error but not exited 
>>> Feb 22 08:50:19 weewx weewxd[68909]: ERROR weewx.restx: StationRegistry: 
>>> Failed to publish record 2024-02-22 08:50:00 EST (17086098>
>>>
>>> will report back if weewx crashes again
>>>
>>> On Monday, February 19, 2024 at 7:09:16 PM UTC-5 Jamie Stephens wrote:
>>>
 Thanks for the fix, I didn't;t even noticed it was not working

 On Monday, February 19, 2024 at 4:25:28 AM UTC-5 Ton Karsten wrote:

> Thank you for resolving the error message.
>
> Op ma 19 feb 2024 om 01:36 schreef bell...@gmail.com <
> bell...@gmail.com>:
>
>> Thanks for pushing it over the goal line. Always the hardest part.
>>
>> On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:
>>
>>> Update - the upstream author was nice enough to merge my PR for this 
>>> problem, so you can simply upgrade your driver to the latest version 
>>> and 
>>> your station registration should work again with weewx v5.
>>>
>>> weectl extension install 
>>> https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
>>> sudo systemctl restart weewx
>>>
>>> After upgrading your driver you should see the following output from 
>>> 'weectl extension list':
>>>
>>> Extension NameVersion   Description
>>> weatherflowudp1.10.2Capture data from WeatherFlow Bridge via 
>>> UDP broadcast packets
>>>
>>> Thanks again Rich for the nudge(s) !!!
>>>
>>> -- 
>> 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
>>> 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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/2f38f991-b58b-4a9c-ad95-21a63311bb90n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
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/cb6767a8-1305-4acf-a440-88ba583b39afn%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Jamie Stephens]

Thanks Tom, this is the new updated driver that Vince got pushed on this 
thread. maybe it was a one off 

On Thursday, February 22, 2024 at 10:07:45 AM UTC-5 Tom Keffer wrote:

> It looks like the author of the driver is trying to insert a string into a 
> byte array. You should file an issue on the repository's issue list.
>
> On Thu, Feb 22, 2024 at 6:00 AM Jamie Stephens  
> wrote:
>
>> i manually restarted it and it's running right now just the registry push 
>> error but not exited 
>> Feb 22 08:50:19 weewx weewxd[68909]: ERROR weewx.restx: StationRegistry: 
>> Failed to publish record 2024-02-22 08:50:00 EST (17086098>
>>
>> will report back if weewx crashes again
>>
>> On Monday, February 19, 2024 at 7:09:16 PM UTC-5 Jamie Stephens wrote:
>>
>>> Thanks for the fix, I didn't;t even noticed it was not working
>>>
>>> On Monday, February 19, 2024 at 4:25:28 AM UTC-5 Ton Karsten wrote:
>>>
 Thank you for resolving the error message.

 Op ma 19 feb 2024 om 01:36 schreef bell...@gmail.com >>> >:

> Thanks for pushing it over the goal line. Always the hardest part.
>
> On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:
>
>> Update - the upstream author was nice enough to merge my PR for this 
>> problem, so you can simply upgrade your driver to the latest version and 
>> your station registration should work again with weewx v5.
>>
>> weectl extension install 
>> https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
>> sudo systemctl restart weewx
>>
>> After upgrading your driver you should see the following output from 
>> 'weectl extension list':
>>
>> Extension NameVersion   Description
>> weatherflowudp1.10.2Capture data from WeatherFlow Bridge via 
>> UDP broadcast packets
>>
>> Thanks again Rich for the nudge(s) !!!
>>
>> -- 
> 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+...@googlegroups.com.
>
 To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%40googlegroups.com
>  
> 
> .
>
 -- 
>> 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/2f38f991-b58b-4a9c-ad95-21a63311bb90n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/79ece3db-b456-4744-b354-301c7e75023cn%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Tom Keffer]

It looks like the author of the driver is trying to insert a string into a
byte array. You should file an issue on the repository's issue list.

On Thu, Feb 22, 2024 at 6:00 AM Jamie Stephens 
wrote:

> i manually restarted it and it's running right now just the registry push
> error but not exited
> Feb 22 08:50:19 weewx weewxd[68909]: ERROR weewx.restx: StationRegistry:
> Failed to publish record 2024-02-22 08:50:00 EST (17086098>
>
> will report back if weewx crashes again
>
> On Monday, February 19, 2024 at 7:09:16 PM UTC-5 Jamie Stephens wrote:
>
>> Thanks for the fix, I didn't;t even noticed it was not working
>>
>> On Monday, February 19, 2024 at 4:25:28 AM UTC-5 Ton Karsten wrote:
>>
>>> Thank you for resolving the error message.
>>>
>>> Op ma 19 feb 2024 om 01:36 schreef bell...@gmail.com >> >:
>>>
 Thanks for pushing it over the goal line. Always the hardest part.

 On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:

> Update - the upstream author was nice enough to merge my PR for this
> problem, so you can simply upgrade your driver to the latest version and
> your station registration should work again with weewx v5.
>
> weectl extension install
> https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
> sudo systemctl restart weewx
>
> After upgrading your driver you should see the following output from
> 'weectl extension list':
>
> Extension NameVersion   Description
> weatherflowudp1.10.2Capture data from WeatherFlow Bridge via
> UDP broadcast packets
>
> Thanks again Rich for the nudge(s) !!!
>
> --
 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+...@googlegroups.com.

>>> To view this discussion on the web visit
 https://groups.google.com/d/msgid/weewx-user/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%40googlegroups.com
 
 .

>>> --
> 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/2f38f991-b58b-4a9c-ad95-21a63311bb90n%40googlegroups.com
> 
> .
>

-- 
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/CAPq0zEBgm3xQsYh%2BFH0T-XyHVK6DmxE64Ha2Xq1VZzhh-Z1ROg%40mail.gmail.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Jamie Stephens]

i manually restarted it and it's running right now just the registry push 
error but not exited 
Feb 22 08:50:19 weewx weewxd[68909]: ERROR weewx.restx: StationRegistry: 
Failed to publish record 2024-02-22 08:50:00 EST (17086098>

will report back if weewx crashes again

On Monday, February 19, 2024 at 7:09:16 PM UTC-5 Jamie Stephens wrote:

> Thanks for the fix, I didn't;t even noticed it was not working
>
> On Monday, February 19, 2024 at 4:25:28 AM UTC-5 Ton Karsten wrote:
>
>> Thank you for resolving the error message.
>>
>> Op ma 19 feb 2024 om 01:36 schreef bell...@gmail.com :
>>
>>> Thanks for pushing it over the goal line. Always the hardest part.
>>>
>>> On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:
>>>
 Update - the upstream author was nice enough to merge my PR for this 
 problem, so you can simply upgrade your driver to the latest version and 
 your station registration should work again with weewx v5.

 weectl extension install 
 https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
 sudo systemctl restart weewx

 After upgrading your driver you should see the following output from 
 'weectl extension list':

 Extension NameVersion   Description
 weatherflowudp1.10.2Capture data from WeatherFlow Bridge via 
 UDP broadcast packets

 Thanks again Rich for the nudge(s) !!!

 -- 
>>> 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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
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/2f38f991-b58b-4a9c-ad95-21a63311bb90n%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Jamie Stephens]

 thread exited last night and won't restart
Feb 21 17:08:31 weewx weewxd[763]:   File "/usr/share/weewx/weewxd.py", 
line 166, in main
Feb 21 17:08:31 weewx weewxd[763]: engine.run()
Feb 21 17:08:31 weewx weewxd[763]:   File 
"/usr/share/weewx/weewx/engine.py", line 204, in run
Feb 21 17:08:31 weewx weewxd[763]: for packet in 
self.console.genLoopPackets():
Feb 21 17:08:31 weewx weewxd[763]:   File 
"/etc/weewx/bin/user/weatherflowudp.py", line 313, in genLoopPackets
Feb 21 17:08:31 weewx weewxd[763]: m0 = m[0].replace(",null",",None")   
  # Python 2
Feb 21 17:08:31 weewx weewxd[763]: TypeError: a bytes-like object is 
required, not 'str'
Feb 21 17:08:31 weewx systemd[1]: weewx.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 21 17:08:31 weewx systemd[1]: weewx.service: Failed with result 
'exit-code'.
Feb 21 17:08:31 weewx systemd[1]: weewx.service: Consumed 39min 16.609s CPU 
time.

On Monday, February 19, 2024 at 7:09:16 PM UTC-5 Jamie Stephens wrote:

> Thanks for the fix, I didn't;t even noticed it was not working
>
> On Monday, February 19, 2024 at 4:25:28 AM UTC-5 Ton Karsten wrote:
>
>> Thank you for resolving the error message.
>>
>> Op ma 19 feb 2024 om 01:36 schreef bell...@gmail.com :
>>
>>> Thanks for pushing it over the goal line. Always the hardest part.
>>>
>>> On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:
>>>
 Update - the upstream author was nice enough to merge my PR for this 
 problem, so you can simply upgrade your driver to the latest version and 
 your station registration should work again with weewx v5.

 weectl extension install 
 https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
 sudo systemctl restart weewx

 After upgrading your driver you should see the following output from 
 'weectl extension list':

 Extension NameVersion   Description
 weatherflowudp1.10.2Capture data from WeatherFlow Bridge via 
 UDP broadcast packets

 Thanks again Rich for the nudge(s) !!!

 -- 
>>> 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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
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/a18f61c4-9bbd-4f03-b868-95f954cfacaan%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Jamie Stephens]

Thanks for the fix, I didn't;t even noticed it was not working

On Monday, February 19, 2024 at 4:25:28 AM UTC-5 Ton Karsten wrote:

> Thank you for resolving the error message.
>
> Op ma 19 feb 2024 om 01:36 schreef bell...@gmail.com :
>
>> Thanks for pushing it over the goal line. Always the hardest part.
>>
>> On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:
>>
>>> Update - the upstream author was nice enough to merge my PR for this 
>>> problem, so you can simply upgrade your driver to the latest version and 
>>> your station registration should work again with weewx v5.
>>>
>>> weectl extension install 
>>> https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
>>> sudo systemctl restart weewx
>>>
>>> After upgrading your driver you should see the following output from 
>>> 'weectl extension list':
>>>
>>> Extension NameVersion   Description
>>> weatherflowudp1.10.2Capture data from WeatherFlow Bridge via UDP 
>>> broadcast packets
>>>
>>> Thanks again Rich for the nudge(s) !!!
>>>
>>> -- 
>> 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/edf92d87-9fee-4bf9-be24-9deee5139737n%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Ton Karsten]

Thank you for resolving the error message.

Op ma 19 feb 2024 om 01:36 schreef bell...@gmail.com :

> Thanks for pushing it over the goal line. Always the hardest part.
>
> On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:
>
>> Update - the upstream author was nice enough to merge my PR for this
>> problem, so you can simply upgrade your driver to the latest version and
>> your station registration should work again with weewx v5.
>>
>> weectl extension install
>> https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
>> sudo systemctl restart weewx
>>
>> After upgrading your driver you should see the following output from
>> 'weectl extension list':
>>
>> Extension NameVersion   Description
>> weatherflowudp1.10.2Capture data from WeatherFlow Bridge via UDP
>> broadcast packets
>>
>> Thanks again Rich for the nudge(s) !!!
>>
>> --
> 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/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%40googlegroups.com
> 
> .
>

-- 
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/CACngpzYZOxacpDBTmS5kvEHD1azbeOrOJjRQhfOE37M4Y3bPbw%40mail.gmail.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[bell...@gmail.com]

Thanks for pushing it over the goal line. Always the hardest part.

On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:

> Update - the upstream author was nice enough to merge my PR for this 
> problem, so you can simply upgrade your driver to the latest version and 
> your station registration should work again with weewx v5.
>
> weectl extension install 
> https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
> sudo systemctl restart weewx
>
> After upgrading your driver you should see the following output from 
> 'weectl extension list':
>
> Extension NameVersion   Description
> weatherflowudp1.10.2Capture data from WeatherFlow Bridge via UDP 
> broadcast packets
>
> Thanks again Rich for the nudge(s) !!!
>
>

-- 
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/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[vince]

Update - the upstream author was nice enough to merge my PR for this 
problem, so you can simply upgrade your driver to the latest version and 
your station registration should work again with weewx v5.

weectl extension install 
https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
sudo systemctl restart weewx

After upgrading your driver you should see the following output from 
'weectl extension list':

Extension NameVersion   Description
weatherflowudp1.10.2Capture data from WeatherFlow Bridge via UDP 
broadcast packets

Thanks again Rich for the nudge(s) !!!

-- 
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/c25ba1fb-2944-46bb-9649-9fdca59605bcn%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[vince]

Not at all obvious to my eyes, nor do I know how to lint to find that 
stuff, but you're better at this than I am :-)

FWIW - I have a fork of this driver that I added this workaround to...

   - wget 
   
https://github.com/vinceskahan/weatherflow-udp/archive/install_example_sensor_map.zip
 
   -O /var/tmp/weatherflow-udp-1.10.2.zip
   - weectl extension install /var/tmp/weatherflow-udp-1.10.2.zip

Changes from the upstream 1.10 version that's been stable for years...

   - added this @property line so v5 registration works vs. this driver
   - I also add a full Tempest sensor map on a clean installation so you 
   don't need to do any cut+paste (other than editing your sensor ID in)
   - added v5 installation note re: weectl
   - and bumped the version string and changelog of course

I'll ask the upstream author again to merge my PR these changes are on but 
last I checked he was kinda busy with having a life too. 

Hope this helps.

On Sunday, February 18, 2024 at 12:41:37 PM UTC-8 bell...@gmail.com wrote:

>
> Good to here. Work around or bug fix, I guess that is in the eye of the 
> beholder….
> While the docs may need some ‘sprucing up’, if one performs static code 
> analysis; the error is pretty obvious. Here is the lint error I got when I 
> removed it
> ‘bin/user/MQTTSubscribe.py:2155:4: W0236: Method 'hardware_name' was 
> expected to be 'property', found it instead as 'method' 
> (invalid-overridden-method)‘
> rich
> On Sunday 18 February 2024 at 15:07:53 UTC-5 vince wrote:
>
>> I can confirm that adding @property in the driver and restarting weewx 
>> 'does' work as a workaround, assuming you didn't use example.com as your 
>> host (sigh - another undocumented thing).
>>
>> # add the next line here around line 289 in the driver or so...
>> @property
>> def hardware_name(self):
>> return HARDWARE_NAME
>>
>> So there's at least one WeatherFlowUDP v5 system registered now.  Cool.
>>
>> Thanks Rich !
>>
>> On Sunday, February 18, 2024 at 11:03:07 AM UTC-8 bell...@gmail.com 
>> wrote:
>>
>>> Quick look of the code and it looks like  ‘example.com’ is rejected. 
>>> Seems the error logging could be improved. I’ll poke around and see if I 
>>> can create a decent pull request. But, I may have to defer to the experts.
>>>
>>> On Sunday 18 February 2024 at 13:30:44 UTC-5 vince wrote:
>>>
 I tried to do so but am still getting BAD REQUEST trying to register a 
 test pi.  Of course now it'll wait a day til trying again.  Sigh.

 I opened https://github.com/weewx/weewx/issues/936 on this one rather 
 than get multiple conversations all cross-intermingled here.


 On Sunday, February 18, 2024 at 7:16:17 AM UTC-8 bell...@gmail.com 
 wrote:

>
> I’d try adding the missing @property decorator. All signs point to 
> that being the problem. It can’t hurt and it fixes a bug.
> On Sunday 18 February 2024 at 01:01:05 UTC-5 vince wrote:
>
>> Meaning what for users or devs ?
>>
>>
>> On Saturday, February 17, 2024 at 3:45:38 PM UTC-8 Tom Keffer wrote:
>>
>>> The difference is that to upload to the station registry, V5 uses an 
>>> HTTP POST with a serialized JSON payload, while V4 uses an HTTP GET.  
>>> The 
>>> GET sent an "unbound method" to the registry as a query parameter. We 
>>> get a 
>>> lot of those, so I included a bit of code to salvage the hardware type 
>>> from 
>>> the "unbound method" parameter. Hence, no one noticed.
>>>
>>>
>>>
>>> On Sat, Feb 17, 2024 at 2:24 PM vince  wrote:
>>>
 There are 75 currently registered sites using this driver but 'all' 
 are showing as running 4.x so I'm guessing something changed in v5 
 weewx..

 On Saturday, February 17, 2024 at 1:44:38 PM UTC-8 
 bell...@gmail.com wrote:

> Theory:
> Drivers are suppose to implement hardware_name as a property. The 
> driver is missing the @property for hardware_name. When WeeWX 
> accesses it 
> as property, for example, instance.hardware_name it returns the 
> function 
> definition.
> Try adding the @property decorator to hardware_name in the driver. 
> (I did some minor testing by removing it in my driver)
> If this is it, I am stumped why it ever worked….
> rich
>
> On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:
>
>> Tom - I can duplicate this here with 5.0.2 running vs. my 
>> wfudpsimulator tool since I don't have actual hardware any more
>>
>> If registering is enabled, you get that error when the archive 
>> period rolls around.
>>
>> I added some debugging to restx that might help. 
>>
>> # Delay the registration by a random amount so all 
>> stations don't hit the server
>> # at the 

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[bell...@gmail.com]

Good to here. Work around or bug fix, I guess that is in the eye of the 
beholder….
While the docs may need some ‘sprucing up’, if one performs static code 
analysis; the error is pretty obvious. Here is the lint error I got when I 
removed it
‘bin/user/MQTTSubscribe.py:2155:4: W0236: Method 'hardware_name' was 
expected to be 'property', found it instead as 'method' 
(invalid-overridden-method)‘
rich
On Sunday 18 February 2024 at 15:07:53 UTC-5 vince wrote:

> I can confirm that adding @property in the driver and restarting weewx 
> 'does' work as a workaround, assuming you didn't use example.com as your 
> host (sigh - another undocumented thing).
>
> # add the next line here around line 289 in the driver or so...
> @property
> def hardware_name(self):
> return HARDWARE_NAME
>
> So there's at least one WeatherFlowUDP v5 system registered now.  Cool.
>
> Thanks Rich !
>
> On Sunday, February 18, 2024 at 11:03:07 AM UTC-8 bell...@gmail.com wrote:
>
>> Quick look of the code and it looks like  ‘example.com’ is rejected. 
>> Seems the error logging could be improved. I’ll poke around and see if I 
>> can create a decent pull request. But, I may have to defer to the experts.
>>
>> On Sunday 18 February 2024 at 13:30:44 UTC-5 vince wrote:
>>
>>> I tried to do so but am still getting BAD REQUEST trying to register a 
>>> test pi.  Of course now it'll wait a day til trying again.  Sigh.
>>>
>>> I opened https://github.com/weewx/weewx/issues/936 on this one rather 
>>> than get multiple conversations all cross-intermingled here.
>>>
>>>
>>> On Sunday, February 18, 2024 at 7:16:17 AM UTC-8 bell...@gmail.com 
>>> wrote:
>>>

 I’d try adding the missing @property decorator. All signs point to that 
 being the problem. It can’t hurt and it fixes a bug.
 On Sunday 18 February 2024 at 01:01:05 UTC-5 vince wrote:

> Meaning what for users or devs ?
>
>
> On Saturday, February 17, 2024 at 3:45:38 PM UTC-8 Tom Keffer wrote:
>
>> The difference is that to upload to the station registry, V5 uses an 
>> HTTP POST with a serialized JSON payload, while V4 uses an HTTP GET.  
>> The 
>> GET sent an "unbound method" to the registry as a query parameter. We 
>> get a 
>> lot of those, so I included a bit of code to salvage the hardware type 
>> from 
>> the "unbound method" parameter. Hence, no one noticed.
>>
>>
>>
>> On Sat, Feb 17, 2024 at 2:24 PM vince  wrote:
>>
>>> There are 75 currently registered sites using this driver but 'all' 
>>> are showing as running 4.x so I'm guessing something changed in v5 
>>> weewx..
>>>
>>> On Saturday, February 17, 2024 at 1:44:38 PM UTC-8 bell...@gmail.com 
>>> wrote:
>>>
 Theory:
 Drivers are suppose to implement hardware_name as a property. The 
 driver is missing the @property for hardware_name. When WeeWX accesses 
 it 
 as property, for example, instance.hardware_name it returns the 
 function 
 definition.
 Try adding the @property decorator to hardware_name in the driver. 
 (I did some minor testing by removing it in my driver)
 If this is it, I am stumped why it ever worked….
 rich

 On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:

> Tom - I can duplicate this here with 5.0.2 running vs. my 
> wfudpsimulator tool since I don't have actual hardware any more
>
> If registering is enabled, you get that error when the archive 
> period rolls around.
>
> I added some debugging to restx that might help. 
>
> # Delay the registration by a random amount so all 
> stations don't hit the server
> # at the same time.
> _registry_dict.setdefault('delay_post', random.randint(0, 
> 45))
>
> log.info("StationRegistry _registry_dict: %s", 
> _registry_dict)
>
> Which outputs
>
> 2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO 
> weewx.restx: StationRegistry _registry_dict: {'log_success': True, 
> 'log_failure': True, 'station_url': '
> https://www.example.com/no-station-here', 'station_type': 
> 'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test 
> station', 
> 'latitude': 47.31, 'longitude': -122.36, 'station_model':  method 
> WeatherFlowUDPDriver.hardware_name of 
> >, 
> 'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path': 
> '/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 
> 'delay_post': 
> 39}
>
>  Notice the station_model value.  Looks a little odd
>
> The driver sets the following
>
> # Default settings...
> 

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[vince]

I can confirm that adding @property in the driver and restarting weewx 
'does' work as a workaround, assuming you didn't use example.com as your 
host (sigh - another undocumented thing).

# add the next line here around line 289 in the driver or so...
@property
def hardware_name(self):
return HARDWARE_NAME

So there's at least one WeatherFlowUDP v5 system registered now.  Cool.

Thanks Rich !

On Sunday, February 18, 2024 at 11:03:07 AM UTC-8 bell...@gmail.com wrote:

> Quick look of the code and it looks like  ‘example.com’ is rejected. 
> Seems the error logging could be improved. I’ll poke around and see if I 
> can create a decent pull request. But, I may have to defer to the experts.
>
> On Sunday 18 February 2024 at 13:30:44 UTC-5 vince wrote:
>
>> I tried to do so but am still getting BAD REQUEST trying to register a 
>> test pi.  Of course now it'll wait a day til trying again.  Sigh.
>>
>> I opened https://github.com/weewx/weewx/issues/936 on this one rather 
>> than get multiple conversations all cross-intermingled here.
>>
>>
>> On Sunday, February 18, 2024 at 7:16:17 AM UTC-8 bell...@gmail.com wrote:
>>
>>>
>>> I’d try adding the missing @property decorator. All signs point to that 
>>> being the problem. It can’t hurt and it fixes a bug.
>>> On Sunday 18 February 2024 at 01:01:05 UTC-5 vince wrote:
>>>
 Meaning what for users or devs ?


 On Saturday, February 17, 2024 at 3:45:38 PM UTC-8 Tom Keffer wrote:

> The difference is that to upload to the station registry, V5 uses an 
> HTTP POST with a serialized JSON payload, while V4 uses an HTTP GET.  The 
> GET sent an "unbound method" to the registry as a query parameter. We get 
> a 
> lot of those, so I included a bit of code to salvage the hardware type 
> from 
> the "unbound method" parameter. Hence, no one noticed.
>
>
>
> On Sat, Feb 17, 2024 at 2:24 PM vince  wrote:
>
>> There are 75 currently registered sites using this driver but 'all' 
>> are showing as running 4.x so I'm guessing something changed in v5 
>> weewx..
>>
>> On Saturday, February 17, 2024 at 1:44:38 PM UTC-8 bell...@gmail.com 
>> wrote:
>>
>>> Theory:
>>> Drivers are suppose to implement hardware_name as a property. The 
>>> driver is missing the @property for hardware_name. When WeeWX accesses 
>>> it 
>>> as property, for example, instance.hardware_name it returns the 
>>> function 
>>> definition.
>>> Try adding the @property decorator to hardware_name in the driver. 
>>> (I did some minor testing by removing it in my driver)
>>> If this is it, I am stumped why it ever worked….
>>> rich
>>>
>>> On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:
>>>
 Tom - I can duplicate this here with 5.0.2 running vs. my 
 wfudpsimulator tool since I don't have actual hardware any more

 If registering is enabled, you get that error when the archive 
 period rolls around.

 I added some debugging to restx that might help. 

 # Delay the registration by a random amount so all stations 
 don't hit the server
 # at the same time.
 _registry_dict.setdefault('delay_post', random.randint(0, 
 45))

 log.info("StationRegistry _registry_dict: %s", 
 _registry_dict)

 Which outputs

 2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO 
 weewx.restx: StationRegistry _registry_dict: {'log_success': True, 
 'log_failure': True, 'station_url': '
 https://www.example.com/no-station-here', 'station_type': 
 'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test 
 station', 
 'latitude': 47.31, 'longitude': -122.36, 'station_model': >>> method 
 WeatherFlowUDPDriver.hardware_name of 
 >, 
 'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path': 
 '/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 
 'delay_post': 
 39}

  Notice the station_model value.  Looks a little odd

 The driver sets the following

 # Default settings...
 DRIVER_VERSION = "1.10"
 HARDWARE_NAME = "WeatherFlow"
 DRIVER_NAME = 'WeatherFlowUDP'

 Notice the single quotes around DRIVER_NAME there ?
 Perhaps some obscure single vs. double quote thing going on ?


 -- 
>> 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> 

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[bell...@gmail.com]

Quick look of the code and it looks like  ‘example.com’ is rejected. Seems 
the error logging could be improved. I’ll poke around and see if I can 
create a decent pull request. But, I may have to defer to the experts.

On Sunday 18 February 2024 at 13:30:44 UTC-5 vince wrote:

> I tried to do so but am still getting BAD REQUEST trying to register a 
> test pi.  Of course now it'll wait a day til trying again.  Sigh.
>
> I opened https://github.com/weewx/weewx/issues/936 on this one rather 
> than get multiple conversations all cross-intermingled here.
>
>
> On Sunday, February 18, 2024 at 7:16:17 AM UTC-8 bell...@gmail.com wrote:
>
>>
>> I’d try adding the missing @property decorator. All signs point to that 
>> being the problem. It can’t hurt and it fixes a bug.
>> On Sunday 18 February 2024 at 01:01:05 UTC-5 vince wrote:
>>
>>> Meaning what for users or devs ?
>>>
>>>
>>> On Saturday, February 17, 2024 at 3:45:38 PM UTC-8 Tom Keffer wrote:
>>>
 The difference is that to upload to the station registry, V5 uses an 
 HTTP POST with a serialized JSON payload, while V4 uses an HTTP GET.  The 
 GET sent an "unbound method" to the registry as a query parameter. We get 
 a 
 lot of those, so I included a bit of code to salvage the hardware type 
 from 
 the "unbound method" parameter. Hence, no one noticed.



 On Sat, Feb 17, 2024 at 2:24 PM vince  wrote:

> There are 75 currently registered sites using this driver but 'all' 
> are showing as running 4.x so I'm guessing something changed in v5 
> weewx..
>
> On Saturday, February 17, 2024 at 1:44:38 PM UTC-8 bell...@gmail.com 
> wrote:
>
>> Theory:
>> Drivers are suppose to implement hardware_name as a property. The 
>> driver is missing the @property for hardware_name. When WeeWX accesses 
>> it 
>> as property, for example, instance.hardware_name it returns the function 
>> definition.
>> Try adding the @property decorator to hardware_name in the driver. (I 
>> did some minor testing by removing it in my driver)
>> If this is it, I am stumped why it ever worked….
>> rich
>>
>> On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:
>>
>>> Tom - I can duplicate this here with 5.0.2 running vs. my 
>>> wfudpsimulator tool since I don't have actual hardware any more
>>>
>>> If registering is enabled, you get that error when the archive 
>>> period rolls around.
>>>
>>> I added some debugging to restx that might help. 
>>>
>>> # Delay the registration by a random amount so all stations 
>>> don't hit the server
>>> # at the same time.
>>> _registry_dict.setdefault('delay_post', random.randint(0, 
>>> 45))
>>>
>>> log.info("StationRegistry _registry_dict: %s", 
>>> _registry_dict)
>>>
>>> Which outputs
>>>
>>> 2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO 
>>> weewx.restx: StationRegistry _registry_dict: {'log_success': True, 
>>> 'log_failure': True, 'station_url': '
>>> https://www.example.com/no-station-here', 'station_type': 
>>> 'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test 
>>> station', 
>>> 'latitude': 47.31, 'longitude': -122.36, 'station_model': >> WeatherFlowUDPDriver.hardware_name of 
>>> >, 
>>> 'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path': 
>>> '/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 
>>> 'delay_post': 
>>> 39}
>>>
>>>  Notice the station_model value.  Looks a little odd
>>>
>>> The driver sets the following
>>>
>>> # Default settings...
>>> DRIVER_VERSION = "1.10"
>>> HARDWARE_NAME = "WeatherFlow"
>>> DRIVER_NAME = 'WeatherFlowUDP'
>>>
>>> Notice the single quotes around DRIVER_NAME there ?
>>> Perhaps some obscure single vs. double quote thing going on ?
>>>
>>>
>>> -- 
> 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+...@googlegroups.com.
>
 To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/742f4e63-77e3-41bc-b24d-ed98a37ab343n%40googlegroups.com
>  
> 
> .
>


-- 
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/693161d6-7c8d-48cf-af04-7c60e34850a6n%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[vince]

I tried to do so but am still getting BAD REQUEST trying to register a test 
pi.  Of course now it'll wait a day til trying again.  Sigh.

I opened https://github.com/weewx/weewx/issues/936 on this one rather than 
get multiple conversations all cross-intermingled here.


On Sunday, February 18, 2024 at 7:16:17 AM UTC-8 bell...@gmail.com wrote:

>
> I’d try adding the missing @property decorator. All signs point to that 
> being the problem. It can’t hurt and it fixes a bug.
> On Sunday 18 February 2024 at 01:01:05 UTC-5 vince wrote:
>
>> Meaning what for users or devs ?
>>
>>
>> On Saturday, February 17, 2024 at 3:45:38 PM UTC-8 Tom Keffer wrote:
>>
>>> The difference is that to upload to the station registry, V5 uses an 
>>> HTTP POST with a serialized JSON payload, while V4 uses an HTTP GET.  The 
>>> GET sent an "unbound method" to the registry as a query parameter. We get a 
>>> lot of those, so I included a bit of code to salvage the hardware type from 
>>> the "unbound method" parameter. Hence, no one noticed.
>>>
>>>
>>>
>>> On Sat, Feb 17, 2024 at 2:24 PM vince  wrote:
>>>
 There are 75 currently registered sites using this driver but 'all' are 
 showing as running 4.x so I'm guessing something changed in v5 weewx..

 On Saturday, February 17, 2024 at 1:44:38 PM UTC-8 bell...@gmail.com 
 wrote:

> Theory:
> Drivers are suppose to implement hardware_name as a property. The 
> driver is missing the @property for hardware_name. When WeeWX accesses it 
> as property, for example, instance.hardware_name it returns the function 
> definition.
> Try adding the @property decorator to hardware_name in the driver. (I 
> did some minor testing by removing it in my driver)
> If this is it, I am stumped why it ever worked….
> rich
>
> On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:
>
>> Tom - I can duplicate this here with 5.0.2 running vs. my 
>> wfudpsimulator tool since I don't have actual hardware any more
>>
>> If registering is enabled, you get that error when the archive period 
>> rolls around.
>>
>> I added some debugging to restx that might help. 
>>
>> # Delay the registration by a random amount so all stations 
>> don't hit the server
>> # at the same time.
>> _registry_dict.setdefault('delay_post', random.randint(0, 45))
>>
>> log.info("StationRegistry _registry_dict: %s", 
>> _registry_dict)
>>
>> Which outputs
>>
>> 2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO 
>> weewx.restx: StationRegistry _registry_dict: {'log_success': True, 
>> 'log_failure': True, 'station_url': '
>> https://www.example.com/no-station-here', 'station_type': 
>> 'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test 
>> station', 
>> 'latitude': 47.31, 'longitude': -122.36, 'station_model': > WeatherFlowUDPDriver.hardware_name of 
>> >, 
>> 'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path': 
>> '/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 
>> 'delay_post': 
>> 39}
>>
>>  Notice the station_model value.  Looks a little odd
>>
>> The driver sets the following
>>
>> # Default settings...
>> DRIVER_VERSION = "1.10"
>> HARDWARE_NAME = "WeatherFlow"
>> DRIVER_NAME = 'WeatherFlowUDP'
>>
>> Notice the single quotes around DRIVER_NAME there ?
>> Perhaps some obscure single vs. double quote thing going on ?
>>
>>
>> -- 
 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+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/742f4e63-77e3-41bc-b24d-ed98a37ab343n%40googlegroups.com
  
 
 .

>>>

-- 
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/d3b8b816-2651-4205-85f0-5ebd0f4191f4n%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[bell...@gmail.com]

I’d try adding the missing @property decorator. All signs point to that 
being the problem. It can’t hurt and it fixes a bug.
On Sunday 18 February 2024 at 01:01:05 UTC-5 vince wrote:

> Meaning what for users or devs ?
>
>
> On Saturday, February 17, 2024 at 3:45:38 PM UTC-8 Tom Keffer wrote:
>
>> The difference is that to upload to the station registry, V5 uses an HTTP 
>> POST with a serialized JSON payload, while V4 uses an HTTP GET.  The GET 
>> sent an "unbound method" to the registry as a query parameter. We get a lot 
>> of those, so I included a bit of code to salvage the hardware type from the 
>> "unbound method" parameter. Hence, no one noticed.
>>
>>
>>
>> On Sat, Feb 17, 2024 at 2:24 PM vince  wrote:
>>
>>> There are 75 currently registered sites using this driver but 'all' are 
>>> showing as running 4.x so I'm guessing something changed in v5 weewx..
>>>
>>> On Saturday, February 17, 2024 at 1:44:38 PM UTC-8 bell...@gmail.com 
>>> wrote:
>>>
 Theory:
 Drivers are suppose to implement hardware_name as a property. The 
 driver is missing the @property for hardware_name. When WeeWX accesses it 
 as property, for example, instance.hardware_name it returns the function 
 definition.
 Try adding the @property decorator to hardware_name in the driver. (I 
 did some minor testing by removing it in my driver)
 If this is it, I am stumped why it ever worked….
 rich

 On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:

> Tom - I can duplicate this here with 5.0.2 running vs. my 
> wfudpsimulator tool since I don't have actual hardware any more
>
> If registering is enabled, you get that error when the archive period 
> rolls around.
>
> I added some debugging to restx that might help. 
>
> # Delay the registration by a random amount so all stations 
> don't hit the server
> # at the same time.
> _registry_dict.setdefault('delay_post', random.randint(0, 45))
>
> log.info("StationRegistry _registry_dict: %s", _registry_dict)
>
> Which outputs
>
> 2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO 
> weewx.restx: StationRegistry _registry_dict: {'log_success': True, 
> 'log_failure': True, 'station_url': '
> https://www.example.com/no-station-here', 'station_type': 
> 'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test station', 
> 'latitude': 47.31, 'longitude': -122.36, 'station_model':  WeatherFlowUDPDriver.hardware_name of 
> >, 
> 'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path': 
> '/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 
> 'delay_post': 
> 39}
>
>  Notice the station_model value.  Looks a little odd
>
> The driver sets the following
>
> # Default settings...
> DRIVER_VERSION = "1.10"
> HARDWARE_NAME = "WeatherFlow"
> DRIVER_NAME = 'WeatherFlowUDP'
>
> Notice the single quotes around DRIVER_NAME there ?
> Perhaps some obscure single vs. double quote thing going on ?
>
>
> -- 
>>> 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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/742f4e63-77e3-41bc-b24d-ed98a37ab343n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
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/6673b855-b660-492f-ad35-c32910baacd9n%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[bell...@gmail.com]

Ah, I see that now. Thanks.

On Saturday 17 February 2024 at 18:45:38 UTC-5 Tom Keffer wrote:

> The difference is that to upload to the station registry, V5 uses an HTTP 
> POST with a serialized JSON payload, while V4 uses an HTTP GET.  The GET 
> sent an "unbound method" to the registry as a query parameter. We get a lot 
> of those, so I included a bit of code to salvage the hardware type from the 
> "unbound method" parameter. Hence, no one noticed.
>
>
>
> On Sat, Feb 17, 2024 at 2:24 PM vince  wrote:
>
>> There are 75 currently registered sites using this driver but 'all' are 
>> showing as running 4.x so I'm guessing something changed in v5 weewx..
>>
>> On Saturday, February 17, 2024 at 1:44:38 PM UTC-8 bell...@gmail.com 
>> wrote:
>>
>>> Theory:
>>> Drivers are suppose to implement hardware_name as a property. The driver 
>>> is missing the @property for hardware_name. When WeeWX accesses it as 
>>> property, for example, instance.hardware_name it returns the function 
>>> definition.
>>> Try adding the @property decorator to hardware_name in the driver. (I 
>>> did some minor testing by removing it in my driver)
>>> If this is it, I am stumped why it ever worked….
>>> rich
>>>
>>> On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:
>>>
 Tom - I can duplicate this here with 5.0.2 running vs. my 
 wfudpsimulator tool since I don't have actual hardware any more

 If registering is enabled, you get that error when the archive period 
 rolls around.

 I added some debugging to restx that might help. 

 # Delay the registration by a random amount so all stations 
 don't hit the server
 # at the same time.
 _registry_dict.setdefault('delay_post', random.randint(0, 45))

 log.info("StationRegistry _registry_dict: %s", _registry_dict)

 Which outputs

 2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO 
 weewx.restx: StationRegistry _registry_dict: {'log_success': True, 
 'log_failure': True, 'station_url': '
 https://www.example.com/no-station-here', 'station_type': 
 'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test station', 
 'latitude': 47.31, 'longitude': -122.36, 'station_model': >>> WeatherFlowUDPDriver.hardware_name of 
 >, 
 'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path': 
 '/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 
 'delay_post': 
 39}

  Notice the station_model value.  Looks a little odd

 The driver sets the following

 # Default settings...
 DRIVER_VERSION = "1.10"
 HARDWARE_NAME = "WeatherFlow"
 DRIVER_NAME = 'WeatherFlowUDP'

 Notice the single quotes around DRIVER_NAME there ?
 Perhaps some obscure single vs. double quote thing going on ?


 -- 
>> 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/742f4e63-77e3-41bc-b24d-ed98a37ab343n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/08933ecf-f6c1-4cda-a213-2c1812469bdcn%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[vince]

Meaning what for users or devs ?


On Saturday, February 17, 2024 at 3:45:38 PM UTC-8 Tom Keffer wrote:

> The difference is that to upload to the station registry, V5 uses an HTTP 
> POST with a serialized JSON payload, while V4 uses an HTTP GET.  The GET 
> sent an "unbound method" to the registry as a query parameter. We get a lot 
> of those, so I included a bit of code to salvage the hardware type from the 
> "unbound method" parameter. Hence, no one noticed.
>
>
>
> On Sat, Feb 17, 2024 at 2:24 PM vince  wrote:
>
>> There are 75 currently registered sites using this driver but 'all' are 
>> showing as running 4.x so I'm guessing something changed in v5 weewx..
>>
>> On Saturday, February 17, 2024 at 1:44:38 PM UTC-8 bell...@gmail.com 
>> wrote:
>>
>>> Theory:
>>> Drivers are suppose to implement hardware_name as a property. The driver 
>>> is missing the @property for hardware_name. When WeeWX accesses it as 
>>> property, for example, instance.hardware_name it returns the function 
>>> definition.
>>> Try adding the @property decorator to hardware_name in the driver. (I 
>>> did some minor testing by removing it in my driver)
>>> If this is it, I am stumped why it ever worked….
>>> rich
>>>
>>> On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:
>>>
 Tom - I can duplicate this here with 5.0.2 running vs. my 
 wfudpsimulator tool since I don't have actual hardware any more

 If registering is enabled, you get that error when the archive period 
 rolls around.

 I added some debugging to restx that might help. 

 # Delay the registration by a random amount so all stations 
 don't hit the server
 # at the same time.
 _registry_dict.setdefault('delay_post', random.randint(0, 45))

 log.info("StationRegistry _registry_dict: %s", _registry_dict)

 Which outputs

 2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO 
 weewx.restx: StationRegistry _registry_dict: {'log_success': True, 
 'log_failure': True, 'station_url': '
 https://www.example.com/no-station-here', 'station_type': 
 'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test station', 
 'latitude': 47.31, 'longitude': -122.36, 'station_model': >>> WeatherFlowUDPDriver.hardware_name of 
 >, 
 'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path': 
 '/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 
 'delay_post': 
 39}

  Notice the station_model value.  Looks a little odd

 The driver sets the following

 # Default settings...
 DRIVER_VERSION = "1.10"
 HARDWARE_NAME = "WeatherFlow"
 DRIVER_NAME = 'WeatherFlowUDP'

 Notice the single quotes around DRIVER_NAME there ?
 Perhaps some obscure single vs. double quote thing going on ?


 -- 
>> 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/742f4e63-77e3-41bc-b24d-ed98a37ab343n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/8b2c0921-b99f-477f-a77d-65e6e4cd178an%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Tom Keffer]

The difference is that to upload to the station registry, V5 uses an HTTP
POST with a serialized JSON payload, while V4 uses an HTTP GET.  The GET
sent an "unbound method" to the registry as a query parameter. We get a lot
of those, so I included a bit of code to salvage the hardware type from the
"unbound method" parameter. Hence, no one noticed.



On Sat, Feb 17, 2024 at 2:24 PM vince  wrote:

> There are 75 currently registered sites using this driver but 'all' are
> showing as running 4.x so I'm guessing something changed in v5 weewx..
>
> On Saturday, February 17, 2024 at 1:44:38 PM UTC-8 bell...@gmail.com
> wrote:
>
>> Theory:
>> Drivers are suppose to implement hardware_name as a property. The driver
>> is missing the @property for hardware_name. When WeeWX accesses it as
>> property, for example, instance.hardware_name it returns the function
>> definition.
>> Try adding the @property decorator to hardware_name in the driver. (I did
>> some minor testing by removing it in my driver)
>> If this is it, I am stumped why it ever worked….
>> rich
>>
>> On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:
>>
>>> Tom - I can duplicate this here with 5.0.2 running vs. my wfudpsimulator
>>> tool since I don't have actual hardware any more
>>>
>>> If registering is enabled, you get that error when the archive period
>>> rolls around.
>>>
>>> I added some debugging to restx that might help.
>>>
>>> # Delay the registration by a random amount so all stations
>>> don't hit the server
>>> # at the same time.
>>> _registry_dict.setdefault('delay_post', random.randint(0, 45))
>>>
>>> log.info("StationRegistry _registry_dict: %s", _registry_dict)
>>>
>>> Which outputs
>>>
>>> 2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO
>>> weewx.restx: StationRegistry _registry_dict: {'log_success': True,
>>> 'log_failure': True, 'station_url': '
>>> https://www.example.com/no-station-here', 'station_type':
>>> 'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test station',
>>> 'latitude': 47.31, 'longitude': -122.36, 'station_model': >> WeatherFlowUDPDriver.hardware_name of
>>> >,
>>> 'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path':
>>> '/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 'delay_post':
>>> 39}
>>>
>>>  Notice the station_model value.  Looks a little odd
>>>
>>> The driver sets the following
>>>
>>> # Default settings...
>>> DRIVER_VERSION = "1.10"
>>> HARDWARE_NAME = "WeatherFlow"
>>> DRIVER_NAME = 'WeatherFlowUDP'
>>>
>>> Notice the single quotes around DRIVER_NAME there ?
>>> Perhaps some obscure single vs. double quote thing going on ?
>>>
>>>
>>> --
> 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/742f4e63-77e3-41bc-b24d-ed98a37ab343n%40googlegroups.com
> 
> .
>

-- 
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/CAPq0zEA4WJfBRNFvGLf5sQFFYd740qb9ERvM9cyjAaHcnFcGsA%40mail.gmail.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[vince]

There are 75 currently registered sites using this driver but 'all' are 
showing as running 4.x so I'm guessing something changed in v5 weewx..

On Saturday, February 17, 2024 at 1:44:38 PM UTC-8 bell...@gmail.com wrote:

> Theory:
> Drivers are suppose to implement hardware_name as a property. The driver 
> is missing the @property for hardware_name. When WeeWX accesses it as 
> property, for example, instance.hardware_name it returns the function 
> definition.
> Try adding the @property decorator to hardware_name in the driver. (I did 
> some minor testing by removing it in my driver)
> If this is it, I am stumped why it ever worked….
> rich
>
> On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:
>
>> Tom - I can duplicate this here with 5.0.2 running vs. my wfudpsimulator 
>> tool since I don't have actual hardware any more
>>
>> If registering is enabled, you get that error when the archive period 
>> rolls around.
>>
>> I added some debugging to restx that might help. 
>>
>> # Delay the registration by a random amount so all stations don't 
>> hit the server
>> # at the same time.
>> _registry_dict.setdefault('delay_post', random.randint(0, 45))
>>
>> log.info("StationRegistry _registry_dict: %s", _registry_dict)
>>
>> Which outputs
>>
>> 2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO 
>> weewx.restx: StationRegistry _registry_dict: {'log_success': True, 
>> 'log_failure': True, 'station_url': '
>> https://www.example.com/no-station-here', 'station_type': 
>> 'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test station', 
>> 'latitude': 47.31, 'longitude': -122.36, 'station_model': > WeatherFlowUDPDriver.hardware_name of 
>> >, 
>> 'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path': 
>> '/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 'delay_post': 
>> 39}
>>
>>  Notice the station_model value.  Looks a little odd
>>
>> The driver sets the following
>>
>> # Default settings...
>> DRIVER_VERSION = "1.10"
>> HARDWARE_NAME = "WeatherFlow"
>> DRIVER_NAME = 'WeatherFlowUDP'
>>
>> Notice the single quotes around DRIVER_NAME there ?
>> Perhaps some obscure single vs. double quote thing going on ?
>>
>>
>>

-- 
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/742f4e63-77e3-41bc-b24d-ed98a37ab343n%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[bell...@gmail.com]

Theory:
Drivers are suppose to implement hardware_name as a property. The driver is 
missing the @property for hardware_name. When WeeWX accesses it as 
property, for example, instance.hardware_name it returns the function 
definition.
Try adding the @property decorator to hardware_name in the driver. (I did 
some minor testing by removing it in my driver)
If this is it, I am stumped why it ever worked….
rich

On Saturday 17 February 2024 at 13:49:06 UTC-5 vince wrote:

> Tom - I can duplicate this here with 5.0.2 running vs. my wfudpsimulator 
> tool since I don't have actual hardware any more
>
> If registering is enabled, you get that error when the archive period 
> rolls around.
>
> I added some debugging to restx that might help. 
>
> # Delay the registration by a random amount so all stations don't 
> hit the server
> # at the same time.
> _registry_dict.setdefault('delay_post', random.randint(0, 45))
>
> log.info("StationRegistry _registry_dict: %s", _registry_dict)
>
> Which outputs
>
> 2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO 
> weewx.restx: StationRegistry _registry_dict: {'log_success': True, 
> 'log_failure': True, 'station_url': '
> https://www.example.com/no-station-here', 'station_type': 
> 'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test station', 
> 'latitude': 47.31, 'longitude': -122.36, 'station_model':  WeatherFlowUDPDriver.hardware_name of 
> >, 
> 'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path': 
> '/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 'delay_post': 
> 39}
>
>  Notice the station_model value.  Looks a little odd
>
> The driver sets the following
>
> # Default settings...
> DRIVER_VERSION = "1.10"
> HARDWARE_NAME = "WeatherFlow"
> DRIVER_NAME = 'WeatherFlowUDP'
>
> Notice the single quotes around DRIVER_NAME there ?
> Perhaps some obscure single vs. double quote thing going on ?
>
>
>

-- 
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/648b2312-d50b-44d7-8d12-ef76a92e55ffn%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[vince]

Tom - I can duplicate this here with 5.0.2 running vs. my wfudpsimulator 
tool since I don't have actual hardware any more

If registering is enabled, you get that error when the archive period rolls 
around.

I added some debugging to restx that might help. 

# Delay the registration by a random amount so all stations don't 
hit the server
# at the same time.
_registry_dict.setdefault('delay_post', random.randint(0, 45))

log.info("StationRegistry _registry_dict: %s", _registry_dict)

Which outputs

2024-02-17T10:36:57.489015-08:00 raspberrypi weewxd[1902]: INFO 
weewx.restx: StationRegistry _registry_dict: {'log_success': True, 
'log_failure': True, 'station_url': 
'https://www.example.com/no-station-here', 'station_type': 
'WeatherFlowUDP', 'description': 'WeatherflowUDP Simulator test station', 
'latitude': 47.31, 'longitude': -122.36, 'station_model': >, 
'config_path': '/home/pi/weewx-data/weewx.conf', 'entry_path': 
'/home/pi/weewx-venv/lib/python3.11/site-packages/weewxd.py', 'delay_post': 
39}

 Notice the station_model value.  Looks a little odd

The driver sets the following

# Default settings...
DRIVER_VERSION = "1.10"
HARDWARE_NAME = "WeatherFlow"
DRIVER_NAME = 'WeatherFlowUDP'

Notice the single quotes around DRIVER_NAME there ?
Perhaps some obscure single vs. double quote thing going on ?


-- 
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/182ff702-ec25-462f-a070-e75e9869b94en%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[pmcg...@gmail.com]

I am seeing the same issue.  Here is my startup through a reporting cycle 
log with debug=1

Feb 17 06:07:18 Garagepi weewxd-weatherflow[1999]: INFO weewx.engine: Using 
binding 'wx_binding' to database 'weatherflow.sdb'
Feb 17 06:07:18 Garagepi weewxd-weatherflow[1999]: INFO weewx.manager: 
Starting backfill of daily summaries
Feb 17 06:07:18 Garagepi weewxd-weatherflow[1999]: INFO weewx.manager: 
Daily summaries up to date
Feb 17 06:07:18 Garagepi weewxd-weatherflow[1999]: INFO weewx.engine: 
Starting main packet loop.
Feb 17 06:07:18 Garagepi weewxd-weatherflow[1999]: INFO 
user.weatherflowudp: Listening for UDP broadcasts to IP address  
on port 50222, with timeout 90 and share_socket True...
Feb 17 06:07:28 Garagepi weewxd-weatherflow[1999]: INFO weewx.wxxtypes: 
Type beaufort has been deprecated. Use unit beaufort instead.
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: INFO __main__: Received 
signal TERM (15).
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: INFO weewx.engine: Main 
loop exiting. Shutting engine down.
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG weewx.restx: Shut 
down StationRegistry thread.
Feb 17 06:07:57 Garagepi systemd[1]: Stopping WeeWX weatherflow...
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: INFO __main__: 
Terminating weewx version 5.0.2
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
 Traceback (most recent call last):
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
   File "/usr/share/weewx/weewxd.py", line 166, in main
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
 engine.run()
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
   File "/usr/share/weewx/weewx/engine.py", line 204, in run
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
 for packet in self.console.genLoopPackets():
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
   File "/etc/weewx/bin/user/weatherflowudp.py", line 290, in genLoopPackets
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
 for udp_packet in self.gen_udp_packets():
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
   File "/etc/weewx/bin/user/weatherflowudp.py", line 310, in 
gen_udp_packets
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
 m0, host_info = sock.recvfrom(1024)
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
   File "/usr/share/weewx/weewxd.py", line 260, in sigTERMhandler
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
 raise Terminate
Feb 17 06:07:57 Garagepi weewxd-weatherflow[1999]: DEBUG __main__:  
 Terminate
Feb 17 06:07:57 Garagepi systemd[1]: weewx@weatherflow.service: Main 
process exited, code=killed, status=15/TERM
Feb 17 06:07:57 Garagepi systemd[1]: weewx@weatherflow.service: Succeeded.
Feb 17 06:07:57 Garagepi systemd[1]: Stopped WeeWX weatherflow.
Feb 17 06:07:57 Garagepi systemd[1]: Started WeeWX weatherflow.
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: 
Initializing weewxd version 5.0.2
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: Command 
line: /usr/share/weewx/weewxd.py --log-label weewxd-weatherflow 
/etc/weewx/weatherflow.conf
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: Using 
Python 3.7.3 (default, Oct 11 2023, 09:51:27) #012[GCC 8.3.0]
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: Located 
at /usr/bin/python3
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: Platform 
Linux-5.10.103-v7+-armv7l-with-debian-10.13
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: Locale: 
'en_US.UTF-8'
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: Entry 
path: /usr/share/weewx/weewxd.py
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: 
WEEWX_ROOT: /etc/weewx
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: 
Configuration file: /etc/weewx/weatherflow.conf
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: User 
module: /etc/weewx/bin/user
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO __main__: Debug: 1
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: DEBUG __main__: 
Initializing engine
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO weewx.engine: 
Loading station type WeatherFlowUDP (user.weatherflowudp)
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO 
user.weatherflowudp: driver version is 1.11
Feb 17 06:07:58 Garagepi weewxd-weatherflow[2016]: INFO 
user.weatherflowudp: sensor map is {'outTemp': 
'air_temperature.ST-0353.obs_st', 'outHumidity': 
'relative_humidity.ST-0353.obs_st', 'pressure': 
'station_pressure.ST-0353.obs_st', 'lightning_strike_count': 
'lightning_strike_count.ST-0353.obs_st', 'lightning_distance': 

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Tom Keffer]

Potentially. The station registry is being passed some bad information.
It's possible that information is needed elsewhere in the program.

Set debug=1, then restart weewxd. Post the log from startup through the
first reporting cycle.

Also, please note which version of the driver you ended up using.

-tk


On Thu, Feb 15, 2024 at 7:55 AM Ton Karsten  wrote:

> When I restart weexw with the WeatherFlowUDP driver in use, I get the
> following error messages once:
> feb 15 16:00:17 raspberrypi weewxd.py[8060]: weatherflowudp: MainThread:
> Listening for UDP broadcasts to IP address  on port 50222, with
> timeout 90 and share_socket False...
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: *** Traceback
> (most recent call last):
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   File
> "/usr/share/weewx/weewx/restx.py", line 384, in run_loop
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***
> self.process_record(_record, dbmanager)
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   File
> "/usr/share/weewx/weewx/restx.py", line 438, in process_record
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***
> _payload = self.get_post_body(_full_record)
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***
>  
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   File
> "/usr/share/weewx/weewx/restx.py", line 1560, in get_post_body
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***
> json_body = json.dumps(body)
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***
>   
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   File
> "/usr/lib/python3.11/json/__init__.py", line 231, in dumps
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***
> return _default_encoder.encode(obj)
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***
>  
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   File
> "/usr/lib/python3.11/json/encoder.py", line 200, in encode
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***
> chunks = self.iterencode(o, _one_shot=True)
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***
>^^
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   File
> "/usr/lib/python3.11/json/encoder.py", line 258, in iterencode
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***
> return _iterencode(o, 0)
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***
>  ^
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   File
> "/usr/lib/python3.11/json/encoder.py", line 180, in default
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: *** raise
> TypeError(f'Object of type {o.__class__.__name__} '
> feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***
> TypeError: Object of type method is not JSON serializable
> feb 15 16:00:17 raspberrypi weewxd[8060]: CRITICAL weewx.restx:
> StationRegistry: Thread terminating. Reason: Object of type method is not
> JSON serializable
> feb 15 16:00:17 raspberrypi weewxd[8060]: Exception in thread
> StationRegistry:
> feb 15 16:00:17 raspberrypi weewxd[8060]: Traceback (most recent call
> last):
> feb 15 16:00:17 raspberrypi weewxd[8060]:   File
> "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
> feb 15 16:00:17 raspberrypi weewxd[8060]: self.run()
> feb 15 16:00:17 raspberrypi weewxd[8060]:   File
> "/usr/share/weewx/weewx/restx.py", line 359, in run
> feb 15 16:00:17 raspberrypi weewxd[8060]: self.run_loop()
> feb 15 16:00:17 raspberrypi weewxd[8060]:   File
> "/usr/share/weewx/weewx/restx.py", line 384, in run_loop
> feb 15 16:00:17 raspberrypi weewxd[8060]: self.process_record(_record,
> dbmanager)
> feb 15 16:00:17 raspberrypi weewxd[8060]:   File
> "/usr/share/weewx/weewx/restx.py", line 438, in process_record
> feb 15 16:00:17 raspberrypi weewxd[8060]: _payload =
> self.get_post_body(_full_record)
> feb 15 16:00:17 raspberrypi weewxd[8060]:
>  
> feb 15 16:00:17 raspberrypi weewxd[8060]:   File
> "/usr/share/weewx/weewx/restx.py", line 1560, in get_post_body
> feb 15 16:00:17 raspberrypi weewxd[8060]: json_body = json.dumps(body)
> feb 15 16:00:17 raspberrypi weewxd[8060]: 
> feb 15 16:00:17 raspberrypi weewxd[8060]:   File
> "/usr/lib/python3.11/json/__init__.py", line 231, in dumps
> feb 15 16:00:17 raspberrypi weewxd[8060]: return
> _default_encoder.encode(obj)
> feb 15 16:00:17 raspberrypi weewxd[8060]:
>  
> feb 15 16:00:17 raspberrypi weewxd[8060]:   File
> "/usr/lib/python3.11/json/encoder.py", line 200, in encode
> feb 15 16:00:17 raspberrypi weewxd[8060]: chunks = self.iterencode(o,
> 

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Ton Karsten]

When I restart weexw with the WeatherFlowUDP driver in use, I get the 
following error messages once:
feb 15 16:00:17 raspberrypi weewxd.py[8060]: weatherflowudp: MainThread: 
Listening for UDP broadcasts to IP address  on port 50222, with 
timeout 90 and share_socket False...
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: *** Traceback 
(most recent call last):
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   File 
"/usr/share/weewx/weewx/restx.py", line 384, in run_loop
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: *** 
self.process_record(_record, dbmanager)
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   File 
"/usr/share/weewx/weewx/restx.py", line 438, in process_record
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: *** 
_payload = self.get_post_body(_full_record)
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   
 
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   File 
"/usr/share/weewx/weewx/restx.py", line 1560, in get_post_body
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: *** 
json_body = json.dumps(body)
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   
  
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   File 
"/usr/lib/python3.11/json/__init__.py", line 231, in dumps
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: *** return 
_default_encoder.encode(obj)
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   
 
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   File 
"/usr/lib/python3.11/json/encoder.py", line 200, in encode
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: *** chunks 
= self.iterencode(o, _one_shot=True)
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   
   ^^
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   File 
"/usr/lib/python3.11/json/encoder.py", line 258, in iterencode
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: *** return 
_iterencode(o, 0)
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   
 ^
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: ***   File 
"/usr/lib/python3.11/json/encoder.py", line 180, in default
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: *** raise 
TypeError(f'Object of type {o.__class__.__name__} '
feb 15 16:00:17 raspberrypi weewxd[8060]: ERROR weewx.restx: *** TypeError: 
Object of type method is not JSON serializable
feb 15 16:00:17 raspberrypi weewxd[8060]: CRITICAL weewx.restx: 
StationRegistry: Thread terminating. Reason: Object of type method is not 
JSON serializable
feb 15 16:00:17 raspberrypi weewxd[8060]: Exception in thread 
StationRegistry:
feb 15 16:00:17 raspberrypi weewxd[8060]: Traceback (most recent call last):
feb 15 16:00:17 raspberrypi weewxd[8060]:   File 
"/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
feb 15 16:00:17 raspberrypi weewxd[8060]: self.run()
feb 15 16:00:17 raspberrypi weewxd[8060]:   File 
"/usr/share/weewx/weewx/restx.py", line 359, in run
feb 15 16:00:17 raspberrypi weewxd[8060]: self.run_loop()
feb 15 16:00:17 raspberrypi weewxd[8060]:   File 
"/usr/share/weewx/weewx/restx.py", line 384, in run_loop
feb 15 16:00:17 raspberrypi weewxd[8060]: self.process_record(_record, 
dbmanager)
feb 15 16:00:17 raspberrypi weewxd[8060]:   File 
"/usr/share/weewx/weewx/restx.py", line 438, in process_record
feb 15 16:00:17 raspberrypi weewxd[8060]: _payload = 
self.get_post_body(_full_record)
feb 15 16:00:17 raspberrypi weewxd[8060]:   
 
feb 15 16:00:17 raspberrypi weewxd[8060]:   File 
"/usr/share/weewx/weewx/restx.py", line 1560, in get_post_body
feb 15 16:00:17 raspberrypi weewxd[8060]: json_body = json.dumps(body)
feb 15 16:00:17 raspberrypi weewxd[8060]: 
feb 15 16:00:17 raspberrypi weewxd[8060]:   File 
"/usr/lib/python3.11/json/__init__.py", line 231, in dumps
feb 15 16:00:17 raspberrypi weewxd[8060]: return 
_default_encoder.encode(obj)
feb 15 16:00:17 raspberrypi weewxd[8060]:   
 
feb 15 16:00:17 raspberrypi weewxd[8060]:   File 
"/usr/lib/python3.11/json/encoder.py", line 200, in encode
feb 15 16:00:17 raspberrypi weewxd[8060]: chunks = self.iterencode(o, 
_one_shot=True)
feb 15 16:00:17 raspberrypi weewxd[8060]: 
 ^^
feb 15 16:00:17 raspberrypi weewxd[8060]:   File 
"/usr/lib/python3.11/json/encoder.py", line 258, in iterencode
feb 15 16:00:17 raspberrypi weewxd[8060]: return _iterencode(o, 0)
feb 15 16:00:17 raspberrypi weewxd[8060]:^
feb 15 16:00:17 raspberrypi 

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Ton Karsten]

Okay thanks.

Op wo 14 feb 2024 om 18:12 schreef vince :

> The weatherflow-udp driver works just fine on v5.
>
> On Wednesday, February 14, 2024 at 7:47:17 AM UTC-8 Ton Karsten wrote:
>
>> Thanks for sharing.
>> Which version are you using?
>> This: https://github.com/captain-coredump/weatherflow-udp
>> Or this one: https://github.com/rongrimes/weewx-tempest-pi
>>
>> Op woensdag 14 februari 2024 om 16:26:59 UTC+1 schreef Tom Hogland:
>>
>>> I'm currently using WeatherflowUDP with weewx 5.0.2 and it's working
>>> fine.
>>>
>>> On Wednesday, February 14, 2024 at 5:31:50 AM UTC-9 Ton Karsten wrote:
>>>
 I use the WeatherFlow Tempest for my weather station.
 I have equipped my weather station with the latest version of weewx.
 Is the WeatherFlowUDP driver suitable for weewx 5.x and has this been
 tested?
 I'm not sure if the installation will go without errors.
>>>
>>> --
> 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/50f83928-617b-447c-98a1-daff5f80964bn%40googlegroups.com
> 
> .
>

-- 
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/CACngpza6bGxpWfbBVjhBPcd8UBsprq8CehG2GF3dauVQLpHvgw%40mail.gmail.com.