date:20210612

Re: [weewx-user] Display both metric and imperial values

2021-06-12 Thread steeple ian

I am busy maintaining the support for my own template at the moment.
However, the WeeWX community is very, very supportive so I am absolutely
sure there will be somebody who is willing to tackle this for you. I am
happy to share code, but as I principally work in PHP, it is probably not
very appropriate for the Belchertown template.

On Sat, 12 Jun 2021 at 18:54, weather list 
wrote:

> Sounds good but also well above my pay grade I fear! Thank you.
>
> On 12 Jun, 2021, at 03:04, steeple ian  wrote:
>
> It should be quite straight forward. My approach would be a to use a unit
> system conversion calculation which could be toggled via an additional
> button in the skin.
>
>
>
> On Fri, 11 Jun 2021 at 23:56, weather list 
> wrote:
>
>> Yes, those Weather34 version have always done that. I’m interested in
>> whether it’s possible to do that in the Belchertown skin.
>>
>> On 11 Jun, 2021, at 17:57, Ian Millard  wrote:
>>
>> Look here: -
>>
>> https://claydonsweather.org.uk
>>
>> Various unit systems can be toggled from the menu (hamburger button top
>> left)
>>
>> Ian
>>
>> On 11 Jun 2021, at 22:53, weather list 
>> wrote:
>>
>> Original thread on this is here.
>> 
>>
>> "My system uses US units but I’ve been looking to see if I can somehow
>> display the temp in both systems:
>>
>> e.g.: 74 °F / 23 °C"
>>
>> That was answered helpfully in the original thread.
>>
>> New questions:
>>
>> In the Belchertown skin:
>>
>> Is it possible  to set a combined °F /°C group temperature or some way to
>> have both w/o customizing each temp display?
>>
>> Is it possible to have a JS switch like the Light/Dark one to allow
>> viewers to set display to metric or imperial?
>>
>>
>>
>>
>>
>> --
>>
>>
>> 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/28CB833D-EDD4-437C-8E87-711A2082E81C%40gmail.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/DB941153-3107-4E03-AC09-225075A85C1C%40gmail.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/3F799E56-546A-44A0-8811-533D601FD7DF%40gmail.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/CADASSaRgjq6bFXdEJ5awQP5P%3DD_kBorH_6sF9T5R9THPoRBiJA%40mail.gmail.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/0CB835AF-37F5-47EF-9BF6-6FE26A2EB1F0%40gmail.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/CADASSaSVH%2Bwzw3O4qwOL_MsZJLdD-Gkzy4ffF0ihU6RykqeBvA%40mail.gmail.com.

[weewx-user] Re: weewx stopped for no apparent reason

2021-06-12 Thread Jay Jaeger

FYI, since I made the change (using my own code, and only on the 
WllPollHost related call, it has stayed up.  HOWEVER, it also has not 
issued any error message, and it has not yet been, say, 3 days, so that 
might be a coincidence.  After, say, Tuesday, I'll give your new dev 
release a whirl (or sooner if the one that is running now locks up.)

(I have no idea if the request class honors any global timeout default, or 
not - no clue there.)

You are more than welcome - I actually enjoy debugging.  ;)

JRJ

On Saturday, June 12, 2021 at 1:50:39 PM UTC-5 michael.s...@gmail.com wrote:

> Hi JRJ,
> thank you for the extensive debugging.
> I've just pushed a new dev release 
> 
> .
>
> Yeah, you're right with the missing timeout. I had assumed the requests 
> library honors the socket timeout configured globally, but apparently not. 
> The standard WeeWX timeout option is now also used for the HTTP requests.
> Additionally, for good measures, I've also added a watchdog for when no 
> packets are received. It has an option to configure the iterations allowed 
> without data. See the changelog for details.
>
> - Michael
>
> cub...@gmail.com schrieb am Freitag, 11. Juni 2021 um 18:13:15 UTC+2:
>
>> I noticed that there is no timeout keyword on the request call 
>> davis_http.request_current.  I will add one to see if it helps.  (I also 
>> note that there is no timeout on the call in start_broadcast either.
>>
>> JRJ
>>
>> On Friday, June 11, 2021 at 10:58:48 AM UTC-5 Jay Jaeger wrote:
>>
>>> I just noticed that the call to _poll_callback()  [to WllPollHost.poll] 
>>> is indeed apparently not returning - noticed in the above logs that there 
>>> is NO message "Polled current conditions".  Working theory: if it receives 
>>> a UDP (broadcast) packet while it is doing the HTTP poll request, the 
>>> driver gets confused.
>>>
>>> On Friday, June 11, 2021 at 10:35:39 AM UTC-5 Jay Jaeger wrote:
>>>

 Happened again while I was looking at logs.  Just for grins, I fired 
 off an HTTP request from my PC, and it woke back up.

 So:  for some reason the WLL driver scheduler _do_tick method call to 
 _poll_callback() never returns, so that _do_tick never returns to 
 _scheduler_tick and thus it goes off to sleepy-land.   QUERY:  Is there 
 some reason it is calling _do_tick() before scheduling the next tick by 
 calling enterabs?  (And no, there is no exception being caught, as far as 
 I 
 can tell.)

 Adding a log.debug call after the _poll_callback() call - but I have no 
 doubt that under these conditions it will not be triggered.

 On Friday, June 11, 2021 at 10:06:10 AM UTC-5 Jay Jaeger wrote:

> Here are some more datapoints from the log that confirm that the 
> needed HTTP request to the WLL box is not occurring:
>
> Jun 10 22:37:01 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: 13scheduler ticks until next push refresh
> Jun 10 22:37:01 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: Next scheduler tick at 2021-06-11 
> 03:37:11 
> Z
> Jun 10 22:37:11 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: Scheduler tick
> Jun 10 22:37:11 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: Notifying poll callback
> Jun 10 22:37:12 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: 12scheduler ticks until next push refresh
> Jun 10 22:37:12 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: Next scheduler tick at 2021-06-11 
> 03:37:22 
> Z
> Jun 10 22:37:22 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: Scheduler tick
> Jun 10 22:37:22 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: Notifying poll callback
> Jun 10 22:37:23 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: 11scheduler ticks until next push refresh
> Jun 10 22:37:23 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: Next scheduler tick at 2021-06-11 
> 03:37:33 
> Z
> Jun 10 22:37:33 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: Scheduler tick
> Jun 10 22:37:33 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: Notifying poll callback
> Jun 10 22:37:34 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: 10scheduler ticks until next push refresh
> Jun 10 22:37:34 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: Next scheduler tick at 2021-06-11 
> 03:37:44 
> Z
> Jun 10 22:37:44 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: Scheduler tick
> Jun 10 22:37:44 mythtv2 weewx[239040] DEBUG 
> user.weatherlink_live.scheduler: Notifying poll callback
>
> *** That was the last log message including scheduler
>

[weewx-user] Re: weewx stopped for no apparent reason

2021-06-12 Thread Michael Schantl

Hi JRJ,
thank you for the extensive debugging.
I've just pushed a new dev release 

.

Yeah, you're right with the missing timeout. I had assumed the requests 
library honors the socket timeout configured globally, but apparently not. 
The standard WeeWX timeout option is now also used for the HTTP requests.
Additionally, for good measures, I've also added a watchdog for when no 
packets are received. It has an option to configure the iterations allowed 
without data. See the changelog for details.

- Michael

cub...@gmail.com schrieb am Freitag, 11. Juni 2021 um 18:13:15 UTC+2:

> I noticed that there is no timeout keyword on the request call 
> davis_http.request_current.  I will add one to see if it helps.  (I also 
> note that there is no timeout on the call in start_broadcast either.
>
> JRJ
>
> On Friday, June 11, 2021 at 10:58:48 AM UTC-5 Jay Jaeger wrote:
>
>> I just noticed that the call to _poll_callback()  [to WllPollHost.poll] 
>> is indeed apparently not returning - noticed in the above logs that there 
>> is NO message "Polled current conditions".  Working theory: if it receives 
>> a UDP (broadcast) packet while it is doing the HTTP poll request, the 
>> driver gets confused.
>>
>> On Friday, June 11, 2021 at 10:35:39 AM UTC-5 Jay Jaeger wrote:
>>
>>>
>>> Happened again while I was looking at logs.  Just for grins, I fired off 
>>> an HTTP request from my PC, and it woke back up.
>>>
>>> So:  for some reason the WLL driver scheduler _do_tick method call to 
>>> _poll_callback() never returns, so that _do_tick never returns to 
>>> _scheduler_tick and thus it goes off to sleepy-land.   QUERY:  Is there 
>>> some reason it is calling _do_tick() before scheduling the next tick by 
>>> calling enterabs?  (And no, there is no exception being caught, as far as I 
>>> can tell.)
>>>
>>> Adding a log.debug call after the _poll_callback() call - but I have no 
>>> doubt that under these conditions it will not be triggered.
>>>
>>> On Friday, June 11, 2021 at 10:06:10 AM UTC-5 Jay Jaeger wrote:
>>>
 Here are some more datapoints from the log that confirm that the needed 
 HTTP request to the WLL box is not occurring:

 Jun 10 22:37:01 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: 13scheduler ticks until next push refresh
 Jun 10 22:37:01 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: Next scheduler tick at 2021-06-11 
 03:37:11 
 Z
 Jun 10 22:37:11 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: Scheduler tick
 Jun 10 22:37:11 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: Notifying poll callback
 Jun 10 22:37:12 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: 12scheduler ticks until next push refresh
 Jun 10 22:37:12 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: Next scheduler tick at 2021-06-11 
 03:37:22 
 Z
 Jun 10 22:37:22 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: Scheduler tick
 Jun 10 22:37:22 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: Notifying poll callback
 Jun 10 22:37:23 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: 11scheduler ticks until next push refresh
 Jun 10 22:37:23 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: Next scheduler tick at 2021-06-11 
 03:37:33 
 Z
 Jun 10 22:37:33 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: Scheduler tick
 Jun 10 22:37:33 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: Notifying poll callback
 Jun 10 22:37:34 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: 10scheduler ticks until next push refresh
 Jun 10 22:37:34 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: Next scheduler tick at 2021-06-11 
 03:37:44 
 Z
 Jun 10 22:37:44 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: Scheduler tick
 Jun 10 22:37:44 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.scheduler: Notifying poll callback

 *** That was the last log message including scheduler

 After that we see (excluding most of the .mappers log entries)

 Jun 10 22:37:44 mythtv2 weewx[239040] DEBUG urllib3.connectionpool: 
 Starting new HTTP connection (1): vantagevieww.lan:80
 Jun 10 22:37:45 mythtv2 weewx[239040] DEBUG urllib3.connectionpool: 
 http://vantagevieww.lan:80 "GET /v1/current_conditions HTTP/1.1" 200 
 None
 Jun 10 22:37:46 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.davis_broadcast: Received 394 bytes from 
 ('192.168.42.75', 25447)
 Jun 10 22:37:46 mythtv2 weewx[239040] DEBUG 
 user.weatherlink_live.packets: Trying to create UDP conditions packet
 Jun 10 22:37:46 mythtv2 weewx[239040] DEBUG

Re: [weewx-user] Display both metric and imperial values

2021-06-12 Thread weather list

Sounds good but also well above my pay grade I fear! Thank you.

> On 12 Jun, 2021, at 03:04, steeple ian  wrote:
> 
> It should be quite straight forward. My approach would be a to use a unit 
> system conversion calculation which could be toggled via an additional button 
> in the skin.
> 
> 
> 
> On Fri, 11 Jun 2021 at 23:56, weather list  > wrote:
> Yes, those Weather34 version have always done that. I’m interested in whether 
> it’s possible to do that in the Belchertown skin.
> 
> 
>> On 11 Jun, 2021, at 17:57, Ian Millard > > wrote:
>> 
> 
> 
>> Look here: -
>> 
>> https://claydonsweather.org.uk 
>> 
>> Various unit systems can be toggled from the menu (hamburger button top left)
>> 
>> Ian
>> 
>>> On 11 Jun 2021, at 22:53, weather list >> > wrote:
>>> 
>>> Original thread on this is here. 
>>> 
>>> 
>>> "My system uses US units but I’ve been looking to see if I can somehow 
>>> display the temp in both systems:
>>> 
>>> e.g.: 74 °F / 23 °C"
>>> 
>>> That was answered helpfully in the original thread.
>>> 
>>> New questions:
>>> 
>>> In the Belchertown skin:
>>> 
>>> Is it possible  to set a combined °F /°C group temperature or some way to 
>>> have both w/o customizing each temp display?
>>> 
>>> Is it possible to have a JS switch like the Light/Dark one to allow viewers 
>>> to set display to metric or imperial?
>>> 
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> 
>>> 
>>> 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/28CB833D-EDD4-437C-8E87-711A2082E81C%40gmail.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/DB941153-3107-4E03-AC09-225075A85C1C%40gmail.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/3F799E56-546A-44A0-8811-533D601FD7DF%40gmail.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/CADASSaRgjq6bFXdEJ5awQP5P%3DD_kBorH_6sF9T5R9THPoRBiJA%40mail.gmail.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/0CB835AF-37F5-47EF-9BF6-6FE26A2EB1F0%40gmail.com.

Re: [weewx-user] Display both metric and imperial values

2021-06-12 Thread steeple ian

It should be quite straight forward. My approach would be a to use a unit
system conversion calculation which could be toggled via an additional
button in the skin.



On Fri, 11 Jun 2021 at 23:56, weather list 
wrote:

> Yes, those Weather34 version have always done that. I’m interested in
> whether it’s possible to do that in the Belchertown skin.
>
> On 11 Jun, 2021, at 17:57, Ian Millard  wrote:
>
> Look here: -
>
> https://claydonsweather.org.uk
>
> Various unit systems can be toggled from the menu (hamburger button top
> left)
>
> Ian
>
> On 11 Jun 2021, at 22:53, weather list  wrote:
>
> Original thread on this is here.
> 
>
> "My system uses US units but I’ve been looking to see if I can somehow
> display the temp in both systems:
>
> e.g.: 74 °F / 23 °C"
>
> That was answered helpfully in the original thread.
>
> New questions:
>
> In the Belchertown skin:
>
> Is it possible  to set a combined °F /°C group temperature or some way to
> have both w/o customizing each temp display?
>
> Is it possible to have a JS switch like the Light/Dark one to allow
> viewers to set display to metric or imperial?
>
>
>
>
>
> --
>
>
> 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/28CB833D-EDD4-437C-8E87-711A2082E81C%40gmail.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/DB941153-3107-4E03-AC09-225075A85C1C%40gmail.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/3F799E56-546A-44A0-8811-533D601FD7DF%40gmail.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/CADASSaRgjq6bFXdEJ5awQP5P%3DD_kBorH_6sF9T5R9THPoRBiJA%40mail.gmail.com.

Re: [weewx-user] Display both metric and imperial values

[weewx-user] Re: weewx stopped for no apparent reason

[weewx-user] Re: weewx stopped for no apparent reason

Re: [weewx-user] Display both metric and imperial values

Re: [weewx-user] Display both metric and imperial values

5 matches

Site Navigation

Mail list logo

Footer information