[weewx-user] Re: LW301 Support

[Anthony Fisher]

Hello Julz,

I only just got LW301 working with weewx myself (again). In my case the 
interceptor driver is used in listen mode, not sniff mode, and I have an 
OpenWRT router/mini server running it.

My first experiment with it stopped working when Oregon Scientific pulled 
down the Anywhere Weather server designed to work with the LW301. This had 
the effect of the LW301 continually looking up DNS for the server and 
getting no-where, so it stopped sending any type of data that the 
interceptor driver could capture for weewx.

I've since added a host record to my OpenWRT router so the LW301 sends its 
data to my local box instead of out on the internet, my router rewrites the 
request via firewall rules to port 8080, where the interceptor driver is 
set to listen to and can thus read the data in the http POST and use it for 
weewx. If you haven't done something like this yourself in answering the 
LW301's sad request for a server that no longer exists, the LW301 is 
unlikely to be sending anything useful at all ... it will just forlornly be 
looking for the Oregon server it is designed to send its data to.

Note that you only need to fool the LW301 into thinking it has a 
destination to send the data to - gateway.weather.oregonscientific.com is 
the hostname it wants ... you don't actually have to handle the http POST 
it sends after it finds the appropriately named server.

Hope this helps in some small way.

Cheers,
Anthony

On Sunday, December 23, 2018 at 9:12:14 AM UTC+11, julz wrote:
>
> Can any one help with this..
>
>
> Dec 22 22:01:49 localhost weewx[12802]: interceptor: MainThread: driver 
> version is 0.42rc2
> Dec 22 22:01:49 localhost weewx[12802]: interceptor: MainThread: device 
> type: lw30x
> Dec 22 22:01:49 localhost weewx[12802]: interceptor: MainThread: sensor 
> map: {'inTemp': 'ot.2:*.*', 'outTemp': 'ot.1:*.*'}
> Dec 22 22:01:49 localhost weewx[12802]: interceptor: MainThread: mode is 
> sniff
> Dec 22 22:01:49 localhost weewx[12802]: interceptor: MainThread: sniff 
> iface=eno1 promiscuous=0
> Dec 22 22:01:49 localhost weewx[12802]: interceptor: MainThread: sniff 
> filter 'src 192.168.1.158 and dst port 80'
> Dec 22 22:01:49 localhost weewx[12802]: import of driver failed: 
> Activateing packet capture failed. Error returned by packet capture library 
> was SIOCGIFHWADDR: No such device ()
> Dec 22 22:01:49 localhost weewx[12802]: engine: Unable to load driver: 
> Activateing packet capture failed. Error returned by packet capture library 
> was SIOCGIFHWADDR: No such device
> Dec 22 22:01:49 localhost weewx[12802]:  Exiting...
> Dec 22 22:05:31 localhost chronyd[2545]: Selected source 193.150.34.2
>
> cannot solve this error any body got any ideas?
> Kind regards
> Julz
>
>
>
> On Thursday, 20 December 2018 20:27:48 UTC, julz wrote:
>>
>> The compatibility chart suggests that oregon scientific LW301 & LW302 are 
>> compatible with this software but I cannot find any details on how to setup 
>> as LW301 is network connected.
>> Has anyone got the LW301 working?
>> Guess there will be more questions from other interested users as oregon 
>> has now killed the server for good!
>> Thanks in advance 
>>
>> Julz
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

Am I missing something ???

No data is getting pulled for *Highest Daily Wind Run* records.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

Created a new issue #33 


On Friday, December 28, 2018 at 5:21:40 AM UTC-8, Pat wrote:
>
> Thanks for the support. I'm due for another coffee!
>
> On Friday, December 28, 2018 at 8:17:26 AM UTC-5, Scott Grayban wrote:
>>
>> Donated also...
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Option -y of wee_device --dump or --clear-memory does not work

[Thomas Keffer]

Right you are. I've created issue #361
 to track.

Thanks for the report!

-tk

On Fri, Dec 28, 2018 at 5:31 PM  wrote:

> I'm actually try use the option -y for confirmed the question in the
> prompt for the commands wee_device --dump and wee_device --clear-memory but
> does not work, and when I use the command wee_device --dump -y ask again at
> the prompt
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Scott Grayban]

Wasn't the tabbing editing in nano... seems my ssh environment was the 
issue. I fixed that and is working correctly.

On Friday, December 28, 2018 at 1:03:46 PM UTC-8, Scott Grayban wrote:
>
> friggiin tab spacing so used to doing that i forget css hates it
>
> On Friday, December 28, 2018 at 12:56:51 PM UTC-8, Pat wrote:
>>
>> The errors are still there. I'd even say they're worse. You have some 
>> ascii characters in there. 
>>
>> Top part of screenshot is Chrome developer tools, bottom part is your 
>> styles.css. 
>>
>> Try to delete and re-enter the diff. Something is very sideways. See 
>> attached screenshot. 
>>
>>
>> On Friday, December 28, 2018 at 3:50:55 PM UTC-5, Scott Grayban wrote:
>>>
>>> I just checked again and the icon is still black I didn't see any 
>>> errors in my chrome console either.
>>>
>>> On Friday, December 28, 2018 at 6:24:44 AM UTC-8, Pat wrote:

 Double check your diff for typos and extra characters. Chrome is 
 showing an error in your styles.css at line 1628 for .wx-stn-alert

 On Friday, December 28, 2018 at 9:16:16 AM UTC-5, Scott Grayban wrote:
>
> Well shit... I updated the styles and index.html.tmpl and the icon is 
> STILL black...
>
> On Friday, December 28, 2018 at 5:44:31 AM UTC-8, Pat wrote:
>>
>> I see. I've made 2 changes to the styles.css 
>> 
>>  
>> file in the last couple of days. 
>>
>> You can see those specific commits here 
>> 
>>  
>> and here 
>> 
>>
>> On Friday, December 28, 2018 at 8:41:53 AM UTC-5, Scott Grayban wrote:
>>>
>>> Yup missed that commit !
>>>
>>> I can't overwrite the file because I have modified it for my tastes. 
>>> So I use diff's
>>>
>>> On Friday, December 28, 2018 at 5:35:36 AM UTC-8, Pat wrote:

 It doesn't look like you have the latest styles.css 
 .
  
 Viewing your source shows the section missing where I set the icon 
 red. 

 Grab an updated copy, place in skins/Belchertown then restart 
 weewx. It should update on the next archive interval

 .wx-stn-alert i {
 color: red;
 }


 On Friday, December 28, 2018 at 8:32:36 AM UTC-5, Scott Grayban 
 wrote:
>
> Why is my alert icon black though ? I did replace my index with 
> yours and modified my styles by hand because I made some font 
> color/text 
> changes.
>
> On Friday, December 28, 2018 at 5:01:05 AM UTC-8, Pat wrote:
>>
>> Looks like you still have a bit of an older index.html.tmpl based 
>> on the alert source code I can see on your site. I'm not sure why 
>> you have 
>> 2 icons, but replace your index.html.tmpl with this one 
>> 
>>  
>> and then restart weewx. 
>>
>>
>>
>> On Thursday, December 27, 2018 at 11:34:16 PM UTC-5, G Hammer 
>> wrote:
>>>
>>> Pat,
>>>
>>> A bit late on getting the files, but while it didn't break 
>>> anything, I now have two alert symbols displayed.
>>> I replaced /index.html.tmpl skin.conf styles.css and 
>>> bin/user/belchertown.py with the latest github versions.
>>>
>>> [image: Alert.png]
>>>
>>>
>>>
>>> On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:

 I've also just updates the styles.css to have the correct 
 spacing for the alert area. Be sure to grab a copy of that and 
 restart weewx

>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Option -y of wee_device --dump or --clear-memory does not work

[h . ochoa]

I'm actually try use the option -y for confirmed the question in the prompt 
for the commands wee_device --dump and wee_device --clear-memory but does 
not work, and when I use the command wee_device --dump -y ask again at the 
prompt

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[kutzenco]

Pat,
Yes, the alerts update automatically! I have a few that disappeared and new 
ones were added without my doing a refresh. I now have *7 *alerts showing! 
We've gotten a huge amount of rain and I'm showing flood alerts for several 
nearby rivers as well as alerts for the county. So, alerts are working 
great for me.

We've had a total of 3.3 inches of rain since the storm started yesterday - 
2.6 inches of that has been since midnight 🌧☔. Hopefully it's over for now 
(radar looks clear). But there is some more rain forecast for Monday night.
phil

On Friday, December 28, 2018 at 11:38:49 AM UTC-5, Pat wrote:
>
> It should clear on archive intervals. Keep an eye on it and let me know
>
> On Friday, December 28, 2018 at 10:56:58 AM UTC-5, kutz...@gmail.com 
> wrote:
>>
>> Pat,
>>
>> Do the alerts update automatically on archive refresh like the graphs? Or 
>> do you need to manually refresh the page. I disabled timeout for my page as 
>> I want people to be able to leave it up always on a tablet, if they like. 
>> It would be nice if the alerts went away when withdrawn or update if 
>> changed. If they don't update automatically, could that feature be added?
>>
>> phil
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: use Weewx on raspberry

[vk3anz]

You need to make sure that the weewx bin directory is in the PYTHONPATH.

I've just run weewx from python, but something like 

$ PYTHONPATH=/home/weewx/bin thonny..

- Use whatever the location of weewx is and whatever command you use to 
invoke thonny.

Susan

On Friday, December 21, 2018 at 6:03:05 AM UTC+11, Patrick Tranchant wrote:
>
> hello Pat,
>
> I try to run the script with Thonny, and I have an error on line" import 
> weedb" => ImportError : No Module named "weedb"
> problem with the path !!!
>
> Patrick
>
> On Saturday, December 8, 2018 at 3:40:43 PM UTC+1, Patrick Tranchant wrote:
>>
>> hello I am a newbie from France ( sorry for my english )
>>
>> I want to use weewx on a raspberry with a weather station built by myself 
>> (view on Magpi)
>> I don't see my station on your website to configure :
>>
>> Weather Station Hardware Comparison: I don't found my weather station.
>> Do you have a solution or how to configure Weewx
>>
>> thank you for your help
>>
>> Patrick
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Pat]

The errors are still there. I'd even say they're worse. You have some ascii 
characters in there. 

Top part of screenshot is Chrome developer tools, bottom part is your 
styles.css. 

Try to delete and re-enter the diff. Something is very sideways. See 
attached screenshot. 


On Friday, December 28, 2018 at 3:50:55 PM UTC-5, Scott Grayban wrote:
>
> I just checked again and the icon is still black I didn't see any 
> errors in my chrome console either.
>
> On Friday, December 28, 2018 at 6:24:44 AM UTC-8, Pat wrote:
>>
>> Double check your diff for typos and extra characters. Chrome is showing 
>> an error in your styles.css at line 1628 for .wx-stn-alert
>>
>> On Friday, December 28, 2018 at 9:16:16 AM UTC-5, Scott Grayban wrote:
>>>
>>> Well shit... I updated the styles and index.html.tmpl and the icon is 
>>> STILL black...
>>>
>>> On Friday, December 28, 2018 at 5:44:31 AM UTC-8, Pat wrote:

 I see. I've made 2 changes to the styles.css 
 
  
 file in the last couple of days. 

 You can see those specific commits here 
 
  
 and here 
 

 On Friday, December 28, 2018 at 8:41:53 AM UTC-5, Scott Grayban wrote:
>
> Yup missed that commit !
>
> I can't overwrite the file because I have modified it for my tastes. 
> So I use diff's
>
> On Friday, December 28, 2018 at 5:35:36 AM UTC-8, Pat wrote:
>>
>> It doesn't look like you have the latest styles.css 
>> .
>>  
>> Viewing your source shows the section missing where I set the icon red. 
>>
>> Grab an updated copy, place in skins/Belchertown then restart weewx. 
>> It should update on the next archive interval
>>
>> .wx-stn-alert i {
>> color: red;
>> }
>>
>>
>> On Friday, December 28, 2018 at 8:32:36 AM UTC-5, Scott Grayban wrote:
>>>
>>> Why is my alert icon black though ? I did replace my index with 
>>> yours and modified my styles by hand because I made some font 
>>> color/text 
>>> changes.
>>>
>>> On Friday, December 28, 2018 at 5:01:05 AM UTC-8, Pat wrote:

 Looks like you still have a bit of an older index.html.tmpl based 
 on the alert source code I can see on your site. I'm not sure why you 
 have 
 2 icons, but replace your index.html.tmpl with this one 
 
  
 and then restart weewx. 



 On Thursday, December 27, 2018 at 11:34:16 PM UTC-5, G Hammer wrote:
>
> Pat,
>
> A bit late on getting the files, but while it didn't break 
> anything, I now have two alert symbols displayed.
> I replaced /index.html.tmpl skin.conf styles.css and 
> bin/user/belchertown.py with the latest github versions.
>
> [image: Alert.png]
>
>
>
> On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:
>>
>> I've also just updates the styles.css to have the correct spacing 
>> for the alert area. Be sure to grab a copy of that and restart weewx
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Scott Grayban]

friggiin tab spacing so used to doing that i forget css hates it

On Friday, December 28, 2018 at 12:56:51 PM UTC-8, Pat wrote:
>
> The errors are still there. I'd even say they're worse. You have some 
> ascii characters in there. 
>
> Top part of screenshot is Chrome developer tools, bottom part is your 
> styles.css. 
>
> Try to delete and re-enter the diff. Something is very sideways. See 
> attached screenshot. 
>
>
> On Friday, December 28, 2018 at 3:50:55 PM UTC-5, Scott Grayban wrote:
>>
>> I just checked again and the icon is still black I didn't see any 
>> errors in my chrome console either.
>>
>> On Friday, December 28, 2018 at 6:24:44 AM UTC-8, Pat wrote:
>>>
>>> Double check your diff for typos and extra characters. Chrome is showing 
>>> an error in your styles.css at line 1628 for .wx-stn-alert
>>>
>>> On Friday, December 28, 2018 at 9:16:16 AM UTC-5, Scott Grayban wrote:

 Well shit... I updated the styles and index.html.tmpl and the icon is 
 STILL black...

 On Friday, December 28, 2018 at 5:44:31 AM UTC-8, Pat wrote:
>
> I see. I've made 2 changes to the styles.css 
> 
>  
> file in the last couple of days. 
>
> You can see those specific commits here 
> 
>  
> and here 
> 
>
> On Friday, December 28, 2018 at 8:41:53 AM UTC-5, Scott Grayban wrote:
>>
>> Yup missed that commit !
>>
>> I can't overwrite the file because I have modified it for my tastes. 
>> So I use diff's
>>
>> On Friday, December 28, 2018 at 5:35:36 AM UTC-8, Pat wrote:
>>>
>>> It doesn't look like you have the latest styles.css 
>>> .
>>>  
>>> Viewing your source shows the section missing where I set the icon red. 
>>>
>>> Grab an updated copy, place in skins/Belchertown then restart weewx. 
>>> It should update on the next archive interval
>>>
>>> .wx-stn-alert i {
>>> color: red;
>>> }
>>>
>>>
>>> On Friday, December 28, 2018 at 8:32:36 AM UTC-5, Scott Grayban 
>>> wrote:

 Why is my alert icon black though ? I did replace my index with 
 yours and modified my styles by hand because I made some font 
 color/text 
 changes.

 On Friday, December 28, 2018 at 5:01:05 AM UTC-8, Pat wrote:
>
> Looks like you still have a bit of an older index.html.tmpl based 
> on the alert source code I can see on your site. I'm not sure why you 
> have 
> 2 icons, but replace your index.html.tmpl with this one 
> 
>  
> and then restart weewx. 
>
>
>
> On Thursday, December 27, 2018 at 11:34:16 PM UTC-5, G Hammer 
> wrote:
>>
>> Pat,
>>
>> A bit late on getting the files, but while it didn't break 
>> anything, I now have two alert symbols displayed.
>> I replaced /index.html.tmpl skin.conf styles.css and 
>> bin/user/belchertown.py with the latest github versions.
>>
>> [image: Alert.png]
>>
>>
>>
>> On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:
>>>
>>> I've also just updates the styles.css to have the correct 
>>> spacing for the alert area. Be sure to grab a copy of that and 
>>> restart weewx
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Scott Grayban]

I just checked again and the icon is still black I didn't see any 
errors in my chrome console either.

On Friday, December 28, 2018 at 6:24:44 AM UTC-8, Pat wrote:
>
> Double check your diff for typos and extra characters. Chrome is showing 
> an error in your styles.css at line 1628 for .wx-stn-alert
>
> On Friday, December 28, 2018 at 9:16:16 AM UTC-5, Scott Grayban wrote:
>>
>> Well shit... I updated the styles and index.html.tmpl and the icon is 
>> STILL black...
>>
>> On Friday, December 28, 2018 at 5:44:31 AM UTC-8, Pat wrote:
>>>
>>> I see. I've made 2 changes to the styles.css 
>>> 
>>>  
>>> file in the last couple of days. 
>>>
>>> You can see those specific commits here 
>>> 
>>>  
>>> and here 
>>> 
>>>
>>> On Friday, December 28, 2018 at 8:41:53 AM UTC-5, Scott Grayban wrote:

 Yup missed that commit !

 I can't overwrite the file because I have modified it for my tastes. So 
 I use diff's

 On Friday, December 28, 2018 at 5:35:36 AM UTC-8, Pat wrote:
>
> It doesn't look like you have the latest styles.css 
> .
>  
> Viewing your source shows the section missing where I set the icon red. 
>
> Grab an updated copy, place in skins/Belchertown then restart weewx. 
> It should update on the next archive interval
>
> .wx-stn-alert i {
> color: red;
> }
>
>
> On Friday, December 28, 2018 at 8:32:36 AM UTC-5, Scott Grayban wrote:
>>
>> Why is my alert icon black though ? I did replace my index with yours 
>> and modified my styles by hand because I made some font color/text 
>> changes.
>>
>> On Friday, December 28, 2018 at 5:01:05 AM UTC-8, Pat wrote:
>>>
>>> Looks like you still have a bit of an older index.html.tmpl based on 
>>> the alert source code I can see on your site. I'm not sure why you have 
>>> 2 
>>> icons, but replace your index.html.tmpl with this one 
>>> 
>>>  
>>> and then restart weewx. 
>>>
>>>
>>>
>>> On Thursday, December 27, 2018 at 11:34:16 PM UTC-5, G Hammer wrote:

 Pat,

 A bit late on getting the files, but while it didn't break 
 anything, I now have two alert symbols displayed.
 I replaced /index.html.tmpl skin.conf styles.css and 
 bin/user/belchertown.py with the latest github versions.

 [image: Alert.png]



 On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:
>
> I've also just updates the styles.css to have the correct spacing 
> for the alert area. Be sure to grab a copy of that and restart weewx
>


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Changing the start and finish of the "day"

[Colin Larsen]

Thanks Thomas

Glad I got the question right, even if the answer isn't simple. I'll stick
will midnight to midnight on my station and see if the extension mentioned
in issue #91 can help.

Cheers (and Merry Xmas, Happy New Year's)
Colin


On Sat, 29 Dec 2018, 01:27 Thomas Keffer  Very well phrased!
>
> And asked before. Issue #91 
> addresses the same problem. Unfortunately, it's a tough problem to solve.
> The issue has been languishing around for nearly 3 years! No plans to
> implement anything.
>
> -tk
>
> On Thu, Dec 27, 2018 at 10:03 PM Colin Larsen 
> wrote:
>
>> Hi all
>>
>> I haven't managed to find the simple answer to this, in some ways I hope
>> it isn't too simple and I skimmed over it!
>>
>> Here in NZ (and Australia I believe) the "meteorological day" is from
>> 0900 in the morning until 0900 the next morning. So rainfall totals for
>> instance are taken from the amount between those times. My weather station
>> can be set to use those times without any problem, what I am unsure of is
>> the affect (if any) on Weewx? I assume that tags such as $day.rain.sum
>> (hope I got that example right) would still take the data from midnight,
>> not 0900? And that the NOAA reports generated and any daily records would
>> also be within that midnight to midnight  time span?
>>
>> Hopefully I've phrased this question properly and there is a fairly
>> straight forward answer.
>>
>> Many thanks
>> Colin
>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

RE: [weewx-user] Re: Belchertown DarkSky Alerts

[kutzenco]

Done. Issue #31.

 

phil

 

From: weewx-user@googlegroups.com  On Behalf Of Pat
Sent: Friday, December 28, 2018 1:08 PM
To: weewx-user 
Subject: Re: [weewx-user] Re: Belchertown DarkSky Alerts

 

I could have sworn I looked at this. Can you put in a quick issue for me on the 
GitHub page so I don't forget it again?

On Friday, December 28, 2018 at 11:52:28 AM UTC-5, kutz...@gmail.com 
  wrote:

Sounds great Pat! I'll watch it and let you know.

 

Speaking of updates, I notice that the "Current Day" under "Weather Record 
Snapshots" on the main page (see attached screenshot) doesn't update 
automatically on archive intervals. The data in that block does update on 
archive intervals, but you need to refresh the page to get the day to change if 
you leave the website up overnight.

 

Can that be changed?

 

phil


On Friday, December 28, 2018 at 11:38:49 AM UTC-5, Pat wrote:

It should clear on archive intervals. Keep an eye on it and let me know

On Friday, December 28, 2018 at 10:56:58 AM UTC-5, kutz...@gmail.com 
  wrote:

Pat,

 

Do the alerts update automatically on archive refresh like the graphs? Or do 
you need to manually refresh the page. I disabled timeout for my page as I want 
people to be able to leave it up always on a tablet, if they like. It would be 
nice if the alerts went away when withdrawn or update if changed. If they don't 
update automatically, could that feature be added?

 

phil


On Friday, December 28, 2018 at 9:03:04 AM UTC-5, Pat wrote:

Wow that is a lot of alerts!


On Friday, December 28, 2018 at 8:59:30 AM UTC-5, kutz...@gmail.com 
  wrote:

Pat, Nice addition!!

 

It seems to be working great for me. We're in the middle of a major rainstorm - 
we currently have an embarrassment of alerts! See the attached jpg.

 

phil

-- 
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/sEd4sVkjpZw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com 
 .
For more options, visit https://groups.google.com/d/optout.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Pat]

I could have sworn I looked at this. Can you put in a quick issue for me on 
the GitHub page so I don't forget it again?

On Friday, December 28, 2018 at 11:52:28 AM UTC-5, kutz...@gmail.com wrote:
>
> Sounds great Pat! I'll watch it and let you know.
>
> Speaking of updates, I notice that the "Current Day" under "Weather Record 
> Snapshots" on the main page (see attached screenshot) doesn't update 
> automatically on archive intervals. The data in that block does update on 
> archive intervals, but you need to refresh the page to get the day to 
> change if you leave the website up overnight.
>
> Can that be changed?
>
> phil
>
> On Friday, December 28, 2018 at 11:38:49 AM UTC-5, Pat wrote:
>>
>> It should clear on archive intervals. Keep an eye on it and let me know
>>
>> On Friday, December 28, 2018 at 10:56:58 AM UTC-5, kutz...@gmail.com 
>> wrote:
>>>
>>> Pat,
>>>
>>> Do the alerts update automatically on archive refresh like the graphs? 
>>> Or do you need to manually refresh the page. I disabled timeout for my page 
>>> as I want people to be able to leave it up always on a tablet, if they 
>>> like. It would be nice if the alerts went away when withdrawn or update if 
>>> changed. If they don't update automatically, could that feature be added?
>>>
>>> phil
>>>
>>> On Friday, December 28, 2018 at 9:03:04 AM UTC-5, Pat wrote:

 Wow that is a lot of alerts!

 On Friday, December 28, 2018 at 8:59:30 AM UTC-5, kutz...@gmail.com 
 wrote:
>
> Pat, Nice addition!!
>
> It seems to be working great for me. We're in the middle of a major 
> rainstorm - we currently have an embarrassment of alerts! See the 
> attached 
> jpg.
>
> phil
>


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[kutzenco]

Sounds great Pat! I'll watch it and let you know.

Speaking of updates, I notice that the "Current Day" under "Weather Record 
Snapshots" on the main page (see attached screenshot) doesn't update 
automatically on archive intervals. The data in that block does update on 
archive intervals, but you need to refresh the page to get the day to 
change if you leave the website up overnight.

Can that be changed?

phil

On Friday, December 28, 2018 at 11:38:49 AM UTC-5, Pat wrote:
>
> It should clear on archive intervals. Keep an eye on it and let me know
>
> On Friday, December 28, 2018 at 10:56:58 AM UTC-5, kutz...@gmail.com 
> wrote:
>>
>> Pat,
>>
>> Do the alerts update automatically on archive refresh like the graphs? Or 
>> do you need to manually refresh the page. I disabled timeout for my page as 
>> I want people to be able to leave it up always on a tablet, if they like. 
>> It would be nice if the alerts went away when withdrawn or update if 
>> changed. If they don't update automatically, could that feature be added?
>>
>> phil
>>
>> On Friday, December 28, 2018 at 9:03:04 AM UTC-5, Pat wrote:
>>>
>>> Wow that is a lot of alerts!
>>>
>>> On Friday, December 28, 2018 at 8:59:30 AM UTC-5, kutz...@gmail.com 
>>> wrote:

 Pat, Nice addition!!

 It seems to be working great for me. We're in the middle of a major 
 rainstorm - we currently have an embarrassment of alerts! See the attached 
 jpg.

 phil

>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Pat]

It should clear on archive intervals. Keep an eye on it and let me know

On Friday, December 28, 2018 at 10:56:58 AM UTC-5, kutz...@gmail.com wrote:
>
> Pat,
>
> Do the alerts update automatically on archive refresh like the graphs? Or 
> do you need to manually refresh the page. I disabled timeout for my page as 
> I want people to be able to leave it up always on a tablet, if they like. 
> It would be nice if the alerts went away when withdrawn or update if 
> changed. If they don't update automatically, could that feature be added?
>
> phil
>
> On Friday, December 28, 2018 at 9:03:04 AM UTC-5, Pat wrote:
>>
>> Wow that is a lot of alerts!
>>
>> On Friday, December 28, 2018 at 8:59:30 AM UTC-5, kutz...@gmail.com 
>> wrote:
>>>
>>> Pat, Nice addition!!
>>>
>>> It seems to be working great for me. We're in the middle of a major 
>>> rainstorm - we currently have an embarrassment of alerts! See the attached 
>>> jpg.
>>>
>>> phil
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[kutzenco]

Pat,

Do the alerts update automatically on archive refresh like the graphs? Or 
do you need to manually refresh the page. I disabled timeout for my page as 
I want people to be able to leave it up always on a tablet, if they like. 
It would be nice if the alerts went away when withdrawn or update if 
changed. If they don't update automatically, could that feature be added?

phil

On Friday, December 28, 2018 at 9:03:04 AM UTC-5, Pat wrote:
>
> Wow that is a lot of alerts!
>
> On Friday, December 28, 2018 at 8:59:30 AM UTC-5, kutz...@gmail.com wrote:
>>
>> Pat, Nice addition!!
>>
>> It seems to be working great for me. We're in the middle of a major 
>> rainstorm - we currently have an embarrassment of alerts! See the attached 
>> jpg.
>>
>> phil
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Scott Grayban]

Fixed that and went through everything 3 times no more errors but still 
black icon... odd

On Friday, December 28, 2018 at 6:24:44 AM UTC-8, Pat wrote:
>
> Double check your diff for typos and extra characters. Chrome is showing 
> an error in your styles.css at line 1628 for .wx-stn-alert
>
> On Friday, December 28, 2018 at 9:16:16 AM UTC-5, Scott Grayban wrote:
>>
>> Well shit... I updated the styles and index.html.tmpl and the icon is 
>> STILL black...
>>
>> On Friday, December 28, 2018 at 5:44:31 AM UTC-8, Pat wrote:
>>>
>>> I see. I've made 2 changes to the styles.css 
>>> 
>>>  
>>> file in the last couple of days. 
>>>
>>> You can see those specific commits here 
>>> 
>>>  
>>> and here 
>>> 
>>>
>>> On Friday, December 28, 2018 at 8:41:53 AM UTC-5, Scott Grayban wrote:

 Yup missed that commit !

 I can't overwrite the file because I have modified it for my tastes. So 
 I use diff's

 On Friday, December 28, 2018 at 5:35:36 AM UTC-8, Pat wrote:
>
> It doesn't look like you have the latest styles.css 
> .
>  
> Viewing your source shows the section missing where I set the icon red. 
>
> Grab an updated copy, place in skins/Belchertown then restart weewx. 
> It should update on the next archive interval
>
> .wx-stn-alert i {
> color: red;
> }
>
>
> On Friday, December 28, 2018 at 8:32:36 AM UTC-5, Scott Grayban wrote:
>>
>> Why is my alert icon black though ? I did replace my index with yours 
>> and modified my styles by hand because I made some font color/text 
>> changes.
>>
>> On Friday, December 28, 2018 at 5:01:05 AM UTC-8, Pat wrote:
>>>
>>> Looks like you still have a bit of an older index.html.tmpl based on 
>>> the alert source code I can see on your site. I'm not sure why you have 
>>> 2 
>>> icons, but replace your index.html.tmpl with this one 
>>> 
>>>  
>>> and then restart weewx. 
>>>
>>>
>>>
>>> On Thursday, December 27, 2018 at 11:34:16 PM UTC-5, G Hammer wrote:

 Pat,

 A bit late on getting the files, but while it didn't break 
 anything, I now have two alert symbols displayed.
 I replaced /index.html.tmpl skin.conf styles.css and 
 bin/user/belchertown.py with the latest github versions.

 [image: Alert.png]



 On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:
>
> I've also just updates the styles.css to have the correct spacing 
> for the alert area. Be sure to grab a copy of that and restart weewx
>


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Pat]

Double check your diff for typos and extra characters. Chrome is showing an 
error in your styles.css at line 1628 for .wx-stn-alert

On Friday, December 28, 2018 at 9:16:16 AM UTC-5, Scott Grayban wrote:
>
> Well shit... I updated the styles and index.html.tmpl and the icon is 
> STILL black...
>
> On Friday, December 28, 2018 at 5:44:31 AM UTC-8, Pat wrote:
>>
>> I see. I've made 2 changes to the styles.css 
>> 
>>  
>> file in the last couple of days. 
>>
>> You can see those specific commits here 
>> 
>>  
>> and here 
>> 
>>
>> On Friday, December 28, 2018 at 8:41:53 AM UTC-5, Scott Grayban wrote:
>>>
>>> Yup missed that commit !
>>>
>>> I can't overwrite the file because I have modified it for my tastes. So 
>>> I use diff's
>>>
>>> On Friday, December 28, 2018 at 5:35:36 AM UTC-8, Pat wrote:

 It doesn't look like you have the latest styles.css 
 .
  
 Viewing your source shows the section missing where I set the icon red. 

 Grab an updated copy, place in skins/Belchertown then restart weewx. It 
 should update on the next archive interval

 .wx-stn-alert i {
 color: red;
 }


 On Friday, December 28, 2018 at 8:32:36 AM UTC-5, Scott Grayban wrote:
>
> Why is my alert icon black though ? I did replace my index with yours 
> and modified my styles by hand because I made some font color/text 
> changes.
>
> On Friday, December 28, 2018 at 5:01:05 AM UTC-8, Pat wrote:
>>
>> Looks like you still have a bit of an older index.html.tmpl based on 
>> the alert source code I can see on your site. I'm not sure why you have 
>> 2 
>> icons, but replace your index.html.tmpl with this one 
>> 
>>  
>> and then restart weewx. 
>>
>>
>>
>> On Thursday, December 27, 2018 at 11:34:16 PM UTC-5, G Hammer wrote:
>>>
>>> Pat,
>>>
>>> A bit late on getting the files, but while it didn't break anything, 
>>> I now have two alert symbols displayed.
>>> I replaced /index.html.tmpl skin.conf styles.css and 
>>> bin/user/belchertown.py with the latest github versions.
>>>
>>> [image: Alert.png]
>>>
>>>
>>>
>>> On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:

 I've also just updates the styles.css to have the correct spacing 
 for the alert area. Be sure to grab a copy of that and restart weewx

>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Scott Grayban]

Well shit... I updated the styles and index.html.tmpl and the icon is STILL 
black...

On Friday, December 28, 2018 at 5:44:31 AM UTC-8, Pat wrote:
>
> I see. I've made 2 changes to the styles.css 
> 
>  
> file in the last couple of days. 
>
> You can see those specific commits here 
> 
>  
> and here 
> 
>
> On Friday, December 28, 2018 at 8:41:53 AM UTC-5, Scott Grayban wrote:
>>
>> Yup missed that commit !
>>
>> I can't overwrite the file because I have modified it for my tastes. So I 
>> use diff's
>>
>> On Friday, December 28, 2018 at 5:35:36 AM UTC-8, Pat wrote:
>>>
>>> It doesn't look like you have the latest styles.css 
>>> .
>>>  
>>> Viewing your source shows the section missing where I set the icon red. 
>>>
>>> Grab an updated copy, place in skins/Belchertown then restart weewx. It 
>>> should update on the next archive interval
>>>
>>> .wx-stn-alert i {
>>> color: red;
>>> }
>>>
>>>
>>> On Friday, December 28, 2018 at 8:32:36 AM UTC-5, Scott Grayban wrote:

 Why is my alert icon black though ? I did replace my index with yours 
 and modified my styles by hand because I made some font color/text changes.

 On Friday, December 28, 2018 at 5:01:05 AM UTC-8, Pat wrote:
>
> Looks like you still have a bit of an older index.html.tmpl based on 
> the alert source code I can see on your site. I'm not sure why you have 2 
> icons, but replace your index.html.tmpl with this one 
> 
>  
> and then restart weewx. 
>
>
>
> On Thursday, December 27, 2018 at 11:34:16 PM UTC-5, G Hammer wrote:
>>
>> Pat,
>>
>> A bit late on getting the files, but while it didn't break anything, 
>> I now have two alert symbols displayed.
>> I replaced /index.html.tmpl skin.conf styles.css and 
>> bin/user/belchertown.py with the latest github versions.
>>
>> [image: Alert.png]
>>
>>
>>
>> On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:
>>>
>>> I've also just updates the styles.css to have the correct spacing 
>>> for the alert area. Be sure to grab a copy of that and restart weewx
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[G Hammer]

That was it. Thanks.

On Friday, December 28, 2018 at 8:01:05 AM UTC-5, Pat wrote:
>
> Looks like you still have a bit of an older index.html.tmpl based on the 
> alert source code I can see on your site. I'm not sure why you have 2 
> icons, but replace your index.html.tmpl with this one 
> 
>  
> and then restart weewx. 
>
>
>
> On Thursday, December 27, 2018 at 11:34:16 PM UTC-5, G Hammer wrote:
>>
>> Pat,
>>
>> A bit late on getting the files, but while it didn't break anything, I 
>> now have two alert symbols displayed.
>> I replaced /index.html.tmpl skin.conf styles.css and 
>> bin/user/belchertown.py with the latest github versions.
>>
>> [image: Alert.png]
>>
>>
>>
>> On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:
>>>
>>> I've also just updates the styles.css to have the correct spacing for 
>>> the alert area. Be sure to grab a copy of that and restart weewx
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Pat]

Wow that is a lot of alerts!

On Friday, December 28, 2018 at 8:59:30 AM UTC-5, kutz...@gmail.com wrote:
>
> Pat, Nice addition!!
>
> It seems to be working great for me. We're in the middle of a major 
> rainstorm - we currently have an embarrassment of alerts! See the attached 
> jpg.
>
> phil
>
> On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:
>>
>> I've also just updates the styles.css to have the correct spacing for the 
>> alert area. Be sure to grab a copy of that and restart weewx
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Scott Grayban]

Damn.. as if combining all alerts into 1 isn't good enough !!!

On Friday, December 28, 2018 at 5:59:30 AM UTC-8, kutz...@gmail.com wrote:
>
> Pat, Nice addition!!
>
> It seems to be working great for me. We're in the middle of a major 
> rainstorm - we currently have an embarrassment of alerts! See the attached 
> jpg.
>
> phil
>
> On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:
>>
>> I've also just updates the styles.css to have the correct spacing for the 
>> alert area. Be sure to grab a copy of that and restart weewx
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Scott Grayban]

Why is my alert icon black though ? I did replace my index with yours and 
modified my styles by hand because I made some font color/text changes.

On Friday, December 28, 2018 at 5:01:05 AM UTC-8, Pat wrote:
>
> Looks like you still have a bit of an older index.html.tmpl based on the 
> alert source code I can see on your site. I'm not sure why you have 2 
> icons, but replace your index.html.tmpl with this one 
> 
>  
> and then restart weewx. 
>
>
>
> On Thursday, December 27, 2018 at 11:34:16 PM UTC-5, G Hammer wrote:
>>
>> Pat,
>>
>> A bit late on getting the files, but while it didn't break anything, I 
>> now have two alert symbols displayed.
>> I replaced /index.html.tmpl skin.conf styles.css and 
>> bin/user/belchertown.py with the latest github versions.
>>
>> [image: Alert.png]
>>
>>
>>
>> On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:
>>>
>>> I've also just updates the styles.css to have the correct spacing for 
>>> the alert area. Be sure to grab a copy of that and restart weewx
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Scott Grayban]

I got your last commit but missed the previous one for the alert icon. I'm 
all good now !

On Friday, December 28, 2018 at 5:44:31 AM UTC-8, Pat wrote:
>
> I see. I've made 2 changes to the styles.css 
> 
>  
> file in the last couple of days. 
>
> You can see those specific commits here 
> 
>  
> and here 
> 
>
> On Friday, December 28, 2018 at 8:41:53 AM UTC-5, Scott Grayban wrote:
>>
>> Yup missed that commit !
>>
>> I can't overwrite the file because I have modified it for my tastes. So I 
>> use diff's
>>
>> On Friday, December 28, 2018 at 5:35:36 AM UTC-8, Pat wrote:
>>>
>>> It doesn't look like you have the latest styles.css 
>>> .
>>>  
>>> Viewing your source shows the section missing where I set the icon red. 
>>>
>>> Grab an updated copy, place in skins/Belchertown then restart weewx. It 
>>> should update on the next archive interval
>>>
>>> .wx-stn-alert i {
>>> color: red;
>>> }
>>>
>>>
>>> On Friday, December 28, 2018 at 8:32:36 AM UTC-5, Scott Grayban wrote:

 Why is my alert icon black though ? I did replace my index with yours 
 and modified my styles by hand because I made some font color/text changes.

 On Friday, December 28, 2018 at 5:01:05 AM UTC-8, Pat wrote:
>
> Looks like you still have a bit of an older index.html.tmpl based on 
> the alert source code I can see on your site. I'm not sure why you have 2 
> icons, but replace your index.html.tmpl with this one 
> 
>  
> and then restart weewx. 
>
>
>
> On Thursday, December 27, 2018 at 11:34:16 PM UTC-5, G Hammer wrote:
>>
>> Pat,
>>
>> A bit late on getting the files, but while it didn't break anything, 
>> I now have two alert symbols displayed.
>> I replaced /index.html.tmpl skin.conf styles.css and 
>> bin/user/belchertown.py with the latest github versions.
>>
>> [image: Alert.png]
>>
>>
>>
>> On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:
>>>
>>> I've also just updates the styles.css to have the correct spacing 
>>> for the alert area. Be sure to grab a copy of that and restart weewx
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Pat]

I see. I've made 2 changes to the styles.css 

 
file in the last couple of days. 

You can see those specific commits here 

 
and here 


On Friday, December 28, 2018 at 8:41:53 AM UTC-5, Scott Grayban wrote:
>
> Yup missed that commit !
>
> I can't overwrite the file because I have modified it for my tastes. So I 
> use diff's
>
> On Friday, December 28, 2018 at 5:35:36 AM UTC-8, Pat wrote:
>>
>> It doesn't look like you have the latest styles.css 
>> .
>>  
>> Viewing your source shows the section missing where I set the icon red. 
>>
>> Grab an updated copy, place in skins/Belchertown then restart weewx. It 
>> should update on the next archive interval
>>
>> .wx-stn-alert i {
>> color: red;
>> }
>>
>>
>> On Friday, December 28, 2018 at 8:32:36 AM UTC-5, Scott Grayban wrote:
>>>
>>> Why is my alert icon black though ? I did replace my index with yours 
>>> and modified my styles by hand because I made some font color/text changes.
>>>
>>> On Friday, December 28, 2018 at 5:01:05 AM UTC-8, Pat wrote:

 Looks like you still have a bit of an older index.html.tmpl based on 
 the alert source code I can see on your site. I'm not sure why you have 2 
 icons, but replace your index.html.tmpl with this one 
 
  
 and then restart weewx. 



 On Thursday, December 27, 2018 at 11:34:16 PM UTC-5, G Hammer wrote:
>
> Pat,
>
> A bit late on getting the files, but while it didn't break anything, I 
> now have two alert symbols displayed.
> I replaced /index.html.tmpl skin.conf styles.css and 
> bin/user/belchertown.py with the latest github versions.
>
> [image: Alert.png]
>
>
>
> On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:
>>
>> I've also just updates the styles.css to have the correct spacing for 
>> the alert area. Be sure to grab a copy of that and restart weewx
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Scott Grayban]

Yup missed that commit !

I can't overwrite the file because I have modified it for my tastes. So I 
use diff's

On Friday, December 28, 2018 at 5:35:36 AM UTC-8, Pat wrote:
>
> It doesn't look like you have the latest styles.css 
> .
>  
> Viewing your source shows the section missing where I set the icon red. 
>
> Grab an updated copy, place in skins/Belchertown then restart weewx. It 
> should update on the next archive interval
>
> .wx-stn-alert i {
> color: red;
> }
>
>
> On Friday, December 28, 2018 at 8:32:36 AM UTC-5, Scott Grayban wrote:
>>
>> Why is my alert icon black though ? I did replace my index with yours and 
>> modified my styles by hand because I made some font color/text changes.
>>
>> On Friday, December 28, 2018 at 5:01:05 AM UTC-8, Pat wrote:
>>>
>>> Looks like you still have a bit of an older index.html.tmpl based on the 
>>> alert source code I can see on your site. I'm not sure why you have 2 
>>> icons, but replace your index.html.tmpl with this one 
>>> 
>>>  
>>> and then restart weewx. 
>>>
>>>
>>>
>>> On Thursday, December 27, 2018 at 11:34:16 PM UTC-5, G Hammer wrote:

 Pat,

 A bit late on getting the files, but while it didn't break anything, I 
 now have two alert symbols displayed.
 I replaced /index.html.tmpl skin.conf styles.css and 
 bin/user/belchertown.py with the latest github versions.

 [image: Alert.png]



 On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:
>
> I've also just updates the styles.css to have the correct spacing for 
> the alert area. Be sure to grab a copy of that and restart weewx
>


-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

Yeah I haven't documented much of it yet since it's not officially 
released. 

But if you want to expand your database (again) to add cloudbase, update 
your extensions.py like you did the other day and add this inside the 
brackets where you have your appTemp and windrun 

, ('cloudbase', 'REAL')

Then do the database shuffle and rebuild your dailies. Setting Belchertown 
skin option show_cloudbase = 1 should enable it for you after a weewx 
restart. 



On Friday, December 28, 2018 at 8:11:26 AM UTC-5, Scott Grayban wrote:
>
> I know its a bit early but I noticed you added cloudbase and you need to 
> expand the db to use it. In the changelog you only mention to read wiki but 
> it's not there
>
> What would the format be ?
>
> On Friday, December 7, 2018 at 2:12:23 PM UTC-8, Pat wrote:
>>
>> The last thread was getting a bit long. So I've started a new one. 
>>
>> Belchertown Skin 0.8.1 has been released which fixes a couple of bugs. 
>> See the release notes, and install instructions here:
>>
>> https://github.com/poblabs/weewx-belchertown/releases
>>
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Pat]

It doesn't look like you have the latest styles.css 
.
 
Viewing your source shows the section missing where I set the icon red. 

Grab an updated copy, place in skins/Belchertown then restart weewx. It 
should update on the next archive interval

.wx-stn-alert i {
color: red;
}


On Friday, December 28, 2018 at 8:32:36 AM UTC-5, Scott Grayban wrote:
>
> Why is my alert icon black though ? I did replace my index with yours and 
> modified my styles by hand because I made some font color/text changes.
>
> On Friday, December 28, 2018 at 5:01:05 AM UTC-8, Pat wrote:
>>
>> Looks like you still have a bit of an older index.html.tmpl based on the 
>> alert source code I can see on your site. I'm not sure why you have 2 
>> icons, but replace your index.html.tmpl with this one 
>> 
>>  
>> and then restart weewx. 
>>
>>
>>
>> On Thursday, December 27, 2018 at 11:34:16 PM UTC-5, G Hammer wrote:
>>>
>>> Pat,
>>>
>>> A bit late on getting the files, but while it didn't break anything, I 
>>> now have two alert symbols displayed.
>>> I replaced /index.html.tmpl skin.conf styles.css and 
>>> bin/user/belchertown.py with the latest github versions.
>>>
>>> [image: Alert.png]
>>>
>>>
>>>
>>> On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:

 I've also just updates the styles.css to have the correct spacing for 
 the alert area. Be sure to grab a copy of that and restart weewx

>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

Thanks for the support. I'm due for another coffee!

On Friday, December 28, 2018 at 8:17:26 AM UTC-5, Scott Grayban wrote:
>
> Donated also...
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

Donated also...

On Friday, December 28, 2018 at 5:02:40 AM UTC-8, Pat wrote:
>
> You're welcome! MQTT can be confusing at first but once you get the 
> concept down that 1 client publishes, and MANY clients can subscribe and 
> get instant updates, it starts to make sense and open doors to other 
> projects :)
>
> On Thursday, December 27, 2018 at 10:16:20 PM UTC-5, Scott Grayban wrote:
>>
>> I did learn a lot. It's the first time in my 40 years of working on linux 
>> that I ever used MQTT and have to admit I can now use that knowledge on a 
>> few sites clients are complaining about.
>>
>> I want to thank each of those who helped because this was a little 
>> learning curve for me. And especially Pat. who was so patient with me.
>>
>> On Thursday, December 27, 2018 at 7:09:26 PM UTC-8, G Hammer wrote:
>>>
>>> Looking good!
>>> Look at all you learned and be proud of your new knowledge. 
>>>
>>> On Thu, Dec 27, 2018 at 8:50 PM Scott Grayban  wrote:
>>>
 ok I did a test from the outside seems to work but of course it 
 doesn't work in-house but I can live with that.

 Can everyone else check again please ?

 On Thursday, December 27, 2018 at 5:40:04 PM UTC-8, Scott Grayban wrote:
>
> Ahh so use my router IP instead and port forward 
>
> On Thursday, December 27, 2018 at 5:33:59 PM UTC-8, Colin Larsen wrote:
>>
>> My MQTT settings in skin.conf look like this - with my public web 
>> site name in there
>>
>> # MQTT Defaults
>>
>> mqtt_enabled = 1
>>
>> mqtt_host = "41south.net.nz"
>>
>> mqtt_port = 9001
>>
>> mqtt_ssl = 0
>>
>> mqtt_topic = "weather/41south/loop"
>>
>> disconnect_live_website_visitor = 180
>>
>> On Fri, Dec 28, 2018 at 2:31 PM Colin Larsen  
>> wrote:
>>
>>>
>>> On Fri, Dec 28, 2018 at 2:29 PM Colin Larsen  
>>> wrote:
>>>
 My browser won't connect to your data, which is due to the fact 
 that you need to port forward the 9001 in your router - otherwise 
 other 
 users outside your network can't access the MQTT data. You'll also 
 need to 
 provide your public ip address or use your FQDN in that setting

 On Fri, Dec 28, 2018 at 2:25 PM Scott Grayban  
 wrote:

> Got it !!!
>
> See if it works on your end 
> http://www.nettletondistrict.com/Nettleton/
>
> On Thursday, December 27, 2018 at 5:14:02 PM UTC-8, Pat wrote:
>>
>> Also, Belchertown uses websockets, so you should change your 
>> [[[Extras]]] mqtt_port to 9001 since that's what you have defined in 
>> myconfig.conf. I didn't catch that earlier. 
>>
>> On Thursday, December 27, 2018 at 8:13:12 PM UTC-5, Pat wrote:
>>>
>>> Ok, so thinking about this. I'm an outside person, and I cannot 
>>> reach your 192.168.0.4 from the outside world. This is a problem 
>>> because I 
>>> need to reach that in order to get MQTT data on your website. 
>>>
>>> You need to port forward 9001 to 192.168.0.4 so I can reach it 
>>> from the outside 
>>>
>>> On Thursday, December 27, 2018 at 8:11:12 PM UTC-5, Scott 
>>> Grayban wrote:

 192.168.0.4 is a local IP that has the weewx installed and data 
 pulled from the station but the website itself is served to the 
 public with 
 a outside IP 63.230.134.161 via a reverse proxy

 see http://www.nettletondistrict.com/Nettleton/ it works fine 
 doing a reverse proxy for everything but the MQTT so far.

 On Thursday, December 27, 2018 at 5:03:34 PM UTC-8, Pat wrote:
>
> I'm not sure what is causing that. Might be best to start from 
> the basics again. Check out my article to compare your settings, 
> read the 
> descriptions again, and also check out the skin options to make 
> sure you're 
> not missing something. 
>
> Is your broker or weewx available to the public?
>
>
> On Thursday, December 27, 2018 at 7:56:44 PM UTC-5, Scott 
> Grayban wrote:
>>
>> Shit.mosquitto.log is showing Socket error on client 
>> , disconnecting.
>>
>> 1545958518: New connection from 192.168.0.4 on port 1883.
>> 1545958518: New client connected from 192.168.0.4 as 
>> d413f626-b78b-4bca-8e99-43861d26dc6a (c1, k60, u'weewx').
>> 1545958518: Client d413f626-b78b-4bca-8e99-43861d26dc6a 
>> disconnected.
>> 1545958520: New connection from 63.230.134.161 on port 1883.
>> 1545958520: *Socket error on 

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

I know its a bit early but I noticed you added cloudbase and you need to 
expand the db to use it. In the changelog you only mention to read wiki but 
it's not there

What would the format be ?

On Friday, December 7, 2018 at 2:12:23 PM UTC-8, Pat wrote:
>
> The last thread was getting a bit long. So I've started a new one. 
>
> Belchertown Skin 0.8.1 has been released which fixes a couple of bugs. See 
> the release notes, and install instructions here:
>
> https://github.com/poblabs/weewx-belchertown/releases
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

You're welcome! MQTT can be confusing at first but once you get the concept 
down that 1 client publishes, and MANY clients can subscribe and get 
instant updates, it starts to make sense and open doors to other projects :)

On Thursday, December 27, 2018 at 10:16:20 PM UTC-5, Scott Grayban wrote:
>
> I did learn a lot. It's the first time in my 40 years of working on linux 
> that I ever used MQTT and have to admit I can now use that knowledge on a 
> few sites clients are complaining about.
>
> I want to thank each of those who helped because this was a little 
> learning curve for me. And especially Pat. who was so patient with me.
>
> On Thursday, December 27, 2018 at 7:09:26 PM UTC-8, G Hammer wrote:
>>
>> Looking good!
>> Look at all you learned and be proud of your new knowledge. 
>>
>> On Thu, Dec 27, 2018 at 8:50 PM Scott Grayban  wrote:
>>
>>> ok I did a test from the outside seems to work but of course it 
>>> doesn't work in-house but I can live with that.
>>>
>>> Can everyone else check again please ?
>>>
>>> On Thursday, December 27, 2018 at 5:40:04 PM UTC-8, Scott Grayban wrote:

 Ahh so use my router IP instead and port forward 

 On Thursday, December 27, 2018 at 5:33:59 PM UTC-8, Colin Larsen wrote:
>
> My MQTT settings in skin.conf look like this - with my public web site 
> name in there
>
> # MQTT Defaults
>
> mqtt_enabled = 1
>
> mqtt_host = "41south.net.nz"
>
> mqtt_port = 9001
>
> mqtt_ssl = 0
>
> mqtt_topic = "weather/41south/loop"
>
> disconnect_live_website_visitor = 180
>
> On Fri, Dec 28, 2018 at 2:31 PM Colin Larsen  
> wrote:
>
>>
>> On Fri, Dec 28, 2018 at 2:29 PM Colin Larsen  
>> wrote:
>>
>>> My browser won't connect to your data, which is due to the fact that 
>>> you need to port forward the 9001 in your router - otherwise other 
>>> users 
>>> outside your network can't access the MQTT data. You'll also need to 
>>> provide your public ip address or use your FQDN in that setting
>>>
>>> On Fri, Dec 28, 2018 at 2:25 PM Scott Grayban  
>>> wrote:
>>>
 Got it !!!

 See if it works on your end 
 http://www.nettletondistrict.com/Nettleton/

 On Thursday, December 27, 2018 at 5:14:02 PM UTC-8, Pat wrote:
>
> Also, Belchertown uses websockets, so you should change your 
> [[[Extras]]] mqtt_port to 9001 since that's what you have defined in 
> myconfig.conf. I didn't catch that earlier. 
>
> On Thursday, December 27, 2018 at 8:13:12 PM UTC-5, Pat wrote:
>>
>> Ok, so thinking about this. I'm an outside person, and I cannot 
>> reach your 192.168.0.4 from the outside world. This is a problem 
>> because I 
>> need to reach that in order to get MQTT data on your website. 
>>
>> You need to port forward 9001 to 192.168.0.4 so I can reach it 
>> from the outside 
>>
>> On Thursday, December 27, 2018 at 8:11:12 PM UTC-5, Scott Grayban 
>> wrote:
>>>
>>> 192.168.0.4 is a local IP that has the weewx installed and data 
>>> pulled from the station but the website itself is served to the 
>>> public with 
>>> a outside IP 63.230.134.161 via a reverse proxy
>>>
>>> see http://www.nettletondistrict.com/Nettleton/ it works fine 
>>> doing a reverse proxy for everything but the MQTT so far.
>>>
>>> On Thursday, December 27, 2018 at 5:03:34 PM UTC-8, Pat wrote:

 I'm not sure what is causing that. Might be best to start from 
 the basics again. Check out my article to compare your settings, 
 read the 
 descriptions again, and also check out the skin options to make 
 sure you're 
 not missing something. 

 Is your broker or weewx available to the public?


 On Thursday, December 27, 2018 at 7:56:44 PM UTC-5, Scott 
 Grayban wrote:
>
> Shit.mosquitto.log is showing Socket error on client 
> , disconnecting.
>
> 1545958518: New connection from 192.168.0.4 on port 1883.
> 1545958518: New client connected from 192.168.0.4 as 
> d413f626-b78b-4bca-8e99-43861d26dc6a (c1, k60, u'weewx').
> 1545958518: Client d413f626-b78b-4bca-8e99-43861d26dc6a 
> disconnected.
> 1545958520: New connection from 63.230.134.161 on port 1883.
> 1545958520: *Socket error on client , disconnecting.*
> 1545958533: New connection from 192.168.0.4 on port 1883.
>
>
> On Thursday, December 27, 2018 at 4:52:22 PM UTC-8, Pat wrote:
>>
>

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Scott Grayban]

Not for me but I did notice that my alert icon is black and not red

On Thursday, December 27, 2018 at 8:34:16 PM UTC-8, G Hammer wrote:
>
> Pat,
>
> A bit late on getting the files, but while it didn't break anything, I now 
> have two alert symbols displayed.
> I replaced /index.html.tmpl skin.conf styles.css and 
> bin/user/belchertown.py with the latest github versions.
>
> [image: Alert.png]
>
>
>
> On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:
>>
>> I've also just updates the styles.css to have the correct spacing for the 
>> alert area. Be sure to grab a copy of that and restart weewx
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown DarkSky Alerts

[Pat]

Looks like you still have a bit of an older index.html.tmpl based on the 
alert source code I can see on your site. I'm not sure why you have 2 
icons, but replace your index.html.tmpl with this one 

 
and then restart weewx. 



On Thursday, December 27, 2018 at 11:34:16 PM UTC-5, G Hammer wrote:
>
> Pat,
>
> A bit late on getting the files, but while it didn't break anything, I now 
> have two alert symbols displayed.
> I replaced /index.html.tmpl skin.conf styles.css and 
> bin/user/belchertown.py with the latest github versions.
>
> [image: Alert.png]
>
>
>
> On Thursday, December 27, 2018 at 9:11:04 PM UTC-5, Pat wrote:
>>
>> I've also just updates the styles.css to have the correct spacing for the 
>> alert area. Be sure to grab a copy of that and restart weewx
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Changing the start and finish of the "day"

[Thomas Keffer]

Very well phrased!

And asked before. Issue #91 
addresses the same problem. Unfortunately, it's a tough problem to solve.
The issue has been languishing around for nearly 3 years! No plans to
implement anything.

-tk

On Thu, Dec 27, 2018 at 10:03 PM Colin Larsen 
wrote:

> Hi all
>
> I haven't managed to find the simple answer to this, in some ways I hope
> it isn't too simple and I skimmed over it!
>
> Here in NZ (and Australia I believe) the "meteorological day" is from 0900
> in the morning until 0900 the next morning. So rainfall totals for instance
> are taken from the amount between those times. My weather station can be
> set to use those times without any problem, what I am unsure of is the
> affect (if any) on Weewx? I assume that tags such as $day.rain.sum (hope I
> got that example right) would still take the data from midnight, not 0900?
> And that the NOAA reports generated and any daily records would also be
> within that midnight to midnight  time span?
>
> Hopefully I've phrased this question properly and there is a fairly
> straight forward answer.
>
> Many thanks
> Colin
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WH4000 (WH3080) changes transmitter ID when it starts to Rain

[Kalli]

Hallo
bei mir ist jetzt auch die UV einheit tot, ich werde im Frühjar mal auf das 
Dach gehen und die UV einheit entfernen , und mal nachsehen was da los ist.

cu. Kalli

Am Montag, 3. September 2018 13:01:41 UTC+2 schrieb Bostjan Potocnik:
>
> I have issues with WH4000 (using SDR it's WH3080). When starts to rain 
> (almost every time) outside unit for temp, rain, ... changes transmitter ID 
> (restarts?).
> That causes that WH4000 console loses outside sensor and it sometimes 
> takes more than 3hours to connect to externla sensor with new ID again.
> I discovered that while troubleshooting wireless connectivity (due to lost 
> connectivity when raining) by using SDR. Logs below:
>
> *Jul 22 16:44:29* weewx-sdr weewx-weewx-sdr[578]: sdr: MainThread: 
> lines=['{"time" : "2018-07-22 14:44:26", "model" : "Fine Offset Electronics 
> WH1080/WH3080 Weather Station", "msg_type" : 0, 
> *"id" : 73*, "temperature_C" : 18.900, "humidity" : 86, "direction_str" : 
> "N", "direction_deg" : "0", "speed" : 3.672, "gust" : 4.896, *"rain" : 
> 14.700*, "battery" : "OK"}\n', 
> .
> .
> .
> *Jul 22 16:44:41* weewx-sdr weewx-weewx-sdr[578]: sdr: MainThread: 
> lines=['{"time" : "2018-07-22 14:44:38", "model" : "Fine Offset Electronics 
> WH1080/WH3080 Weather Station", "msg_type" : 0,
> * "id" : 151*, "temperature_C" : 18.900, "humidity" : 86, "direction_str" 
> : "N", "direction_deg" : "0", "speed" : 0.000, "gust" : 0.000, *"rain" : 
> 0.000*, "battery" : "OK"}\n']
>
>
> *Anyone with the same experiences and maybe solutions?*
>
> I have no problems with UV/Lux sensor, that one does not change 
> transmitter ID!
>
> Thanks,
>
> Bostjan
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: wlink error with weatherlink.com V2

[Ruben Navarro Huedo]

I have exactly the same problem with: LOOP data is not being downloaded 
into the database.
It is downloading only archive data each hour.

El viernes, 8 de junio de 2018, 17:57:39 (UTC+2), Philip Kutzenco escribió:
>
> m,
>
> As an addition, I noted an error in today's log file from wlink. After 
> WeeWX manager added a number of records to the database and before the 
> report images were created, I see the following three lines: I'm not sure 
> if this helps understand why LOOP data is not being read.
>
>
> Jun  8 11:46:16 raspberrypi weewx[554]: wlink: cannot make timestamp: 
> ds=65535 ts=65535
> Jun  8 11:46:16 raspberrypi weewx[554]: wlink: cannot make timestamp: 
> ds=65535 ts=65535
> Jun  8 11:46:16 raspberrypi weewx[554]: wlink: cannot make timestamp: 
> ds=65535 ts=65535
>
> Note that debugging at this time (unlike the file I uploaded in my 
> previous post) is set at 0.
>
> Best,
> phil
>
>
> On Thursday, June 7, 2018 at 8:03:52 PM UTC-4, Philip Kutzenco wrote:
>
>> m,
>>
>>  
>>
>> I called Davis. It turns out that because a single weatherlink.com v2 
>> account can now support multiple devices, to download data, you use the DID 
>> of the station as username, instead of the web account username - you use 
>> the same password you used before, though.
>>
>>  
>>
>> I tested this by downloading data from the website using the Davis 
>> Weatherlink software for Windows.
>>
>>  
>>
>> So, I updated weewx.conf entering my DID as username.
>>
>>  
>>
>> WeeWX with your wlink driver now works! Woo-hoo. But there still is an 
>> issue for me. According to the Caveat on your Github page for wlink
>>
>> This driver obtains LOOP data by polling the weatherlink.com site every 
>> 60 seconds. ARCHIVE data are retrieved from the weatherlink.com site 
>> using the API published by Davis.
>>
>>
>> http://www.davisnet.com/support/weather/download/VantageSerialProtocolDocs_v261.pdf
>>
>> According to the FAQ, LOOP data are uploaded once per minute, and 
>> weatherlink.com creates an archive record each hour:
>>
>> http://www.davisnet.com/support/weather/faq/index.asp?ProdFam=15
>>
>> Non-archive records downloaded from weatherlink.com contain only a 
>> subset of observations: windSpeed, windDir, barometer, outTemp, and rain.
>>
>> It appears that the archive data is downloaded once per hour after it is 
>> created by weatherlink.com and loaded into the sqlite database. However, 
>> the LOOP data is not downloaded into the database. The WeeWX report web 
>> pages are only updated once per hour. I see on the weatherlink.com web 
>> site, that my data logger is, indeed uploading data once per minute, (by 
>> the way inside temp and humidity seem included in that once-per-minute 
>> data) but the web reports from WeeWX are only updated hourly (with data in 
>> 5 minute increments).  With the Vantage driver, I do get 5 minute 
>> updates from WeeWX.
>>
>>  
>>
>> I restarted WeeWX with wlink and debugging = 1.
>>
>>  
>>
>> I've uploaded those log entries as log.txt.
>>
>>  
>>
>> I hope you can help me correct this. If you need access to 
>> weatherlink.com, I can give you my DID and password to log in with (and 
>> I’ll change it later).
>>
>>  
>>
>> Thanks again in advance for your great help.
>>
>>  
>>
>> Best,
>>
>> phil  
>>
>>
>> On Thursday, June 7, 2018 at 11:29:07 AM UTC-4, mwall wrote:
>>>
>>>
>>>
>>> On Thursday, June 7, 2018 at 9:50:35 AM UTC-4, Philip Kutzenco wrote:

 m,

 Thanks. I will call Davis. 

 But first, I have a question. How does wlink know whether to connect to 
 weatherlink.com V1 or weatherlink.com V2. If, indeed, it is connecting 
 to weatherlink.com V1, then those error messages make sense. Both 
 websites are live. I no longer have an account on V1, but I do have an 
 account on V2.

 To login to weatherlink.com 
 
  
 V1 you go to https://www.weatherlink.com/login.php
 To login to weatherlink.com V2 you go to 
 https://www.weatherlink.com/login

 I'll bet that wlink is trying to login to V1!

 Is that something I can change, or do you need to make that change?

>>>
>>>
>>> hi phil,
>>>
>>> the weewx-wlink uploader uses these URLs:
>>>
>>> http://www.weatherlink.com/user/USERNAME/index.php
>>> ?view=main&headers=0&type=2
>>>
>>> http://weatherlink.com/webdl.php
>>> ?timestamp=XXX&user=USERNAME&pass=PASSWORD&action=data
>>>
>>> http://weatherlink.com/webdl.php
>>> ?timestamp=0&user=USERNAME&pass=PASSWORD&action=headers
>>> where USERNAME is your username and PASSWORD is your password, and XXX 
>>> is a davis timestamp
>>>
>>> try entering those URLs directly using curl or wget (or a web browser) 
>>> to see what you get.
>>>
>>> there is no distinction made regarding V1 or V2
>>>
>>> the davis timestamp is derived from a unix epoch timestamp like this:
>>>
>>> def _epoch_to_timestamp(epoc

[weewx-user] Re: wlink error with weatherlink.com V2

[Ruben Navarro Huedo]

Last days i am getting: Dec 28 10:28:20 raspi weewx[441]: wlink: download 
failed attempt 5 of 5: HTTP Error 403: Forbidden
Dec 28 10:28:50 raspi weewx[441]: wlink: download failed after 5 tries




-- 
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.
For more options, visit https://groups.google.com/d/optout.