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] 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]

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:
>
> Looks good
>
> On Thursday, December 27, 2018 at 7:50:49 PM UTC-5, Scott 
> Grayban wrote:
>>
>> Is my /etc/mosquitto/acl correct ? Or do I need to change 
>> those values ?
>>
>> # Allow anonymous access to the sys
>> topic read $SYS/#
>> # Allow anonymous to read weather
>> topic read 

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

[kutzenco]

I just checked your website and it's working for me. Congratulations!
phil

On Thursday, December 27, 2018 at 8:50:25 PM UTC-5, 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:

 Looks good

 On Thursday, December 27, 2018 at 7:50:49 PM UTC-5, Scott 
 Grayban wrote:
>
> Is my /etc/mosquitto/acl correct ? Or do I need to change 
> those values ?
>
> # Allow anonymous access to the sys
> topic read $SYS/#
> # Allow anonymous to read weather
> topic read weather/#
> # weewx readwrite to the loop
> user weewx
> topic weather/#
>
>
> On Thursday, December 27, 2018 at 4:43:02 PM UTC-8, Pat wrote:
>>
>> Ok, there's a few more things not quite right. 
>>
>> 1. MQTT is very picky about it's config file. Change your 
>> myconfig.conf so that there is no space between listener 1883 
>> and protocol 
>> mqtt. See 

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

[Colin Larsen]

He sure does - you can buy him a coffee :) Links are on the Github pages

On Fri, Dec 28, 2018 at 3:41 PM Scott Grayban  wrote:

> Thank you Pat for all your help... Do you take donations ?
>
> On Thursday, December 27, 2018 at 6:07:14 PM UTC-8, Pat wrote:
>>
>> Looks good!
>>
>>
>> On Thursday, December 27, 2018 at 8:50:25 PM UTC-5, 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:
>>
>> Looks good
>>
>> On Thursday, December 27, 2018 at 7:50:49 PM UTC-5, Scott
>> Grayban wrote:
>>>
>>> Is my /etc/mosquitto/acl correct ? Or do I need to change
>>> those values ?
>>>
>>> # Allow anonymous access to the sys
>>> topic read $SYS/#
>>> # Allow anonymous to read weather
>>> topic read weather/#
>>> # weewx readwrite to the loop
>>> user weewx

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

[Scott Grayban]

Thank you Pat for all your help... Do you take donations ?

On Thursday, December 27, 2018 at 6:07:14 PM UTC-8, Pat wrote:
>
> Looks good!
>
>
> On Thursday, December 27, 2018 at 8:50:25 PM UTC-5, 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:
>
> Looks good
>
> On Thursday, December 27, 2018 at 7:50:49 PM UTC-5, Scott 
> Grayban wrote:
>>
>> Is my /etc/mosquitto/acl correct ? Or do I need to change 
>> those values ?
>>
>> # Allow anonymous access to the sys
>> topic read $SYS/#
>> # Allow anonymous to read weather
>> topic read weather/#
>> # weewx readwrite to the loop
>> user weewx
>> topic weather/#
>>
>>
>> On Thursday, December 27, 2018 at 4:43:02 PM UTC-8, Pat wrote:
>>>
>>> Ok, there's a few more things not quite right. 
>>>

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

[Pat]

Looks good!


On Thursday, December 27, 2018 at 8:50:25 PM UTC-5, 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:

 Looks good

 On Thursday, December 27, 2018 at 7:50:49 PM UTC-5, Scott 
 Grayban wrote:
>
> Is my /etc/mosquitto/acl correct ? Or do I need to change 
> those values ?
>
> # Allow anonymous access to the sys
> topic read $SYS/#
> # Allow anonymous to read weather
> topic read weather/#
> # weewx readwrite to the loop
> user weewx
> topic weather/#
>
>
> On Thursday, December 27, 2018 at 4:43:02 PM UTC-8, Pat wrote:
>>
>> Ok, there's a few more things not quite right. 
>>
>> 1. MQTT is very picky about it's config file. Change your 
>> myconfig.conf so that there is no space between listener 1883 
>> and protocol 
>> mqtt. See my post from last night above a few. 
>>

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

[Colin Larsen]

Yep bingo. Well done. Mine works from inside and outside, not sure what you
have different though

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

> I guess I could move the MQTT to a public side server in my house so data
> is collected in-house also Wouldn't be hard to do seeing that Pat get
> me all sorted out. Just transfer all my settings.
>
> On Thursday, December 27, 2018 at 5:50:25 PM UTC-8, 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:
>
> Looks good
>
> On Thursday, December 27, 2018 at 7:50:49 PM UTC-5, Scott
> Grayban wrote:
>>
>> Is my /etc/mosquitto/acl correct ? Or do I need to change
>> those values ?
>>
>> # Allow anonymous access to the sys
>> topic read $SYS/#
>> # Allow anonymous to read weather
>> topic read weather/#
>> # weewx readwrite to the loop
>> user weewx
>> topic weather/#
>>

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

[Scott Grayban]

I guess I could move the MQTT to a public side server in my house so data 
is collected in-house also Wouldn't be hard to do seeing that Pat get 
me all sorted out. Just transfer all my settings.

On Thursday, December 27, 2018 at 5:50:25 PM UTC-8, 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:

 Looks good

 On Thursday, December 27, 2018 at 7:50:49 PM UTC-5, Scott 
 Grayban wrote:
>
> Is my /etc/mosquitto/acl correct ? Or do I need to change 
> those values ?
>
> # Allow anonymous access to the sys
> topic read $SYS/#
> # Allow anonymous to read weather
> topic read weather/#
> # weewx readwrite to the loop
> user weewx
> topic weather/#
>
>
> On Thursday, December 27, 2018 at 4:43:02 PM UTC-8, Pat wrote:
>>
>> Ok, there's a few more things not quite right. 
>>
>> 1. MQTT is very picky about it's config file. Change your 

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

[Scott Grayban]

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:
>>>
>>> Looks good
>>>
>>> On Thursday, December 27, 2018 at 7:50:49 PM UTC-5, Scott 
>>> Grayban wrote:

 Is my /etc/mosquitto/acl correct ? Or do I need to change those 
 values ?

 # Allow anonymous access to the sys
 topic read $SYS/#
 # Allow anonymous to read weather
 topic read weather/#
 # weewx readwrite to the loop
 user weewx
 topic weather/#


 On Thursday, December 27, 2018 at 4:43:02 PM UTC-8, Pat wrote:
>
> Ok, there's a few more things not quite right. 
>
> 1. MQTT is very picky about it's config file. Change your 
> myconfig.conf so that there is no space between listener 1883 and 
> protocol 
> mqtt. See my post from last night above a few. 
>
> listener 1883
> protocol mqtt
>
> Restart your mosquitto - or to be safe, restart your MQTT 
> server. 
>
> 2. Once it's back up and weewx says it's posting, can 

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

[Scott Grayban]

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:
>>
>> Looks good
>>
>> On Thursday, December 27, 2018 at 7:50:49 PM UTC-5, Scott Grayban 
>> wrote:
>>>
>>> Is my /etc/mosquitto/acl correct ? Or do I need to change those 
>>> values ?
>>>
>>> # Allow anonymous access to the sys
>>> topic read $SYS/#
>>> # Allow anonymous to read weather
>>> topic read weather/#
>>> # weewx readwrite to the loop
>>> user weewx
>>> topic weather/#
>>>
>>>
>>> On Thursday, December 27, 2018 at 4:43:02 PM UTC-8, Pat wrote:

 Ok, there's a few more things not quite right. 

 1. MQTT is very picky about it's config file. Change your 
 myconfig.conf so that there is no space between listener 1883 and 
 protocol 
 mqtt. See my post from last night above a few. 

 listener 1883
 protocol mqtt

 Restart your mosquitto - or to be safe, restart your MQTT 
 server. 

 2. Once it's back up and weewx says it's posting, can you 
 verify from your computer that MQTT is wokring? You can use a 
 program like MQTT 
 Spy 
 
  on 
 Windows if you have Java installed. 

 3. In MQTT, the # is only used for debugging. 

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

[Colin Larsen]

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:
>
> Looks good
>
> On Thursday, December 27, 2018 at 7:50:49 PM UTC-5, Scott Grayban
> wrote:
>>
>> Is my /etc/mosquitto/acl correct ? Or do I need to change those
>> values ?
>>
>> # Allow anonymous access to the sys
>> topic read $SYS/#
>> # Allow anonymous to read weather
>> topic read weather/#
>> # weewx readwrite to the loop
>> user weewx
>> topic weather/#
>>
>>
>> On Thursday, December 27, 2018 at 4:43:02 PM UTC-8, Pat wrote:
>>>
>>> Ok, there's a few more things not quite right.
>>>
>>> 1. MQTT is very picky about it's config file. Change your
>>> myconfig.conf so that there is no space between listener 1883 and 
>>> protocol
>>> mqtt. See my post from last night above a few.
>>>
>>> listener 1883
>>> protocol mqtt
>>>
>>> Restart your mosquitto - or to be safe, restart your MQTT
>>> server.
>>>
>>> 2. Once it's back up and weewx says it's posting, can you verify
>>> from your computer that MQTT is wokring? You can use a program like 
>>> MQTT
>>> Spy
>>> 
>>>  on
>>> Windows if you have Java installed.
>>>
>>> 3. In MQTT, the # is only used for debugging. You really don't
>>> want to publish or subscribe to this special topic.
>>>
>>> Under [[MQTT]] change
>>>
>>> topic = weather/weewx
>>>
>>> Under Belchertown [[[Extras]]] change
>>>
>>> mqtt_topic = weather/weewx/loop
>>>
>>> 

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

[Colin Larsen]

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:

 Looks good

 On Thursday, December 27, 2018 at 7:50:49 PM UTC-5, Scott Grayban
 wrote:
>
> Is my /etc/mosquitto/acl correct ? Or do I need to change those
> values ?
>
> # Allow anonymous access to the sys
> topic read $SYS/#
> # Allow anonymous to read weather
> topic read weather/#
> # weewx readwrite to the loop
> user weewx
> topic weather/#
>
>
> On Thursday, December 27, 2018 at 4:43:02 PM UTC-8, Pat wrote:
>>
>> Ok, there's a few more things not quite right.
>>
>> 1. MQTT is very picky about it's config file. Change your
>> myconfig.conf so that there is no space between listener 1883 and 
>> protocol
>> mqtt. See my post from last night above a few.
>>
>> listener 1883
>> protocol mqtt
>>
>> Restart your mosquitto - or to be safe, restart your MQTT server.
>>
>> 2. Once it's back up and weewx says it's posting, can you verify
>> from your computer that MQTT is wokring? You can use a program like 
>> MQTT
>> Spy
>> 
>>  on
>> Windows if you have Java installed.
>>
>> 3. In MQTT, the # is only used for debugging. You really don't
>> want to publish or subscribe to this special topic.
>>
>> Under [[MQTT]] change
>>
>> topic = weather/weewx
>>
>> Under Belchertown [[[Extras]]] change
>>
>> mqtt_topic = weather/weewx/loop
>>
>> Restart weewx
>>
>>
>> On Thursday, December 27, 2018 at 7:36:18 PM UTC-5, Scott Grayban
>> wrote:
>>
>>> Ok getting close.
>>>
>>> in EXTRAS I have
>>>
>>> mqtt_enabled = 1
>>> mqtt_host = 192.168.0.4
>>> mqtt_topic = weather/#
>>> mqtt_port = 1883
>>> mqtt_ssl = 0
>>> 

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

[Colin Larsen]

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:
>>>
>>> Looks good
>>>
>>> On Thursday, December 27, 2018 at 7:50:49 PM UTC-5, Scott Grayban
>>> wrote:

 Is my /etc/mosquitto/acl correct ? Or do I need to change those
 values ?

 # Allow anonymous access to the sys
 topic read $SYS/#
 # Allow anonymous to read weather
 topic read weather/#
 # weewx readwrite to the loop
 user weewx
 topic weather/#


 On Thursday, December 27, 2018 at 4:43:02 PM UTC-8, Pat wrote:
>
> Ok, there's a few more things not quite right.
>
> 1. MQTT is very picky about it's config file. Change your
> myconfig.conf so that there is no space between listener 1883 and 
> protocol
> mqtt. See my post from last night above a few.
>
> listener 1883
> protocol mqtt
>
> Restart your mosquitto - or to be safe, restart your MQTT server.
>
> 2. Once it's back up and weewx says it's posting, can you verify
> from your computer that MQTT is wokring? You can use a program like 
> MQTT
> Spy
> 
>  on
> Windows if you have Java installed.
>
> 3. In MQTT, the # is only used for debugging. You really don't
> want to publish or subscribe to this special topic.
>
> Under [[MQTT]] change
>
> topic = weather/weewx
>
> Under Belchertown [[[Extras]]] change
>
> mqtt_topic = weather/weewx/loop
>
> Restart weewx
>
>
> On Thursday, December 27, 2018 at 7:36:18 PM UTC-5, Scott Grayban
> wrote:
>
>> Ok getting close.
>>
>> in EXTRAS I have
>>
>> mqtt_enabled = 1
>> mqtt_host = 192.168.0.4
>> mqtt_topic = weather/#
>> mqtt_port = 1883
>> mqtt_ssl = 0
>> disconnect_live_website_visitor = 180
>>
>>
>> which now is giving *Failed connecting to the weather station.
>> Please try again later!*
>>
>> I am pretty sure I 

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

[G Hammer]

I get connecting for about a minute then failed try again later.

On Thu, Dec 27, 2018 at 8: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:
>>>
>>> Looks good
>>>
>>> On Thursday, December 27, 2018 at 7:50:49 PM UTC-5, Scott Grayban
>>> wrote:

 Is my /etc/mosquitto/acl correct ? Or do I need to change those
 values ?

 # Allow anonymous access to the sys
 topic read $SYS/#
 # Allow anonymous to read weather
 topic read weather/#
 # weewx readwrite to the loop
 user weewx
 topic weather/#


 On Thursday, December 27, 2018 at 4:43:02 PM UTC-8, Pat wrote:
>
> Ok, there's a few more things not quite right.
>
> 1. MQTT is very picky about it's config file. Change your
> myconfig.conf so that there is no space between listener 1883 and 
> protocol
> mqtt. See my post from last night above a few.
>
> listener 1883
> protocol mqtt
>
> Restart your mosquitto - or to be safe, restart your MQTT server.
>
> 2. Once it's back up and weewx says it's posting, can you verify
> from your computer that MQTT is wokring? You can use a program like 
> MQTT
> Spy
> 
>  on
> Windows if you have Java installed.
>
> 3. In MQTT, the # is only used for debugging. You really don't
> want to publish or subscribe to this special topic.
>
> Under [[MQTT]] change
>
> topic = weather/weewx
>
> Under Belchertown [[[Extras]]] change
>
> mqtt_topic = weather/weewx/loop
>
> Restart weewx
>
>
> On Thursday, December 27, 2018 at 7:36:18 PM UTC-5, Scott Grayban
> wrote:
>
>> Ok getting close.
>>
>> in EXTRAS I have
>>
>> mqtt_enabled = 1
>> mqtt_host = 192.168.0.4
>> mqtt_topic = weather/#
>> mqtt_port = 1883
>> mqtt_ssl = 0
>> disconnect_live_website_visitor = 180
>>
>>
>> which now is giving *Failed connecting to the weather station.
>> Please try again later!*
>>
>> I am pretty sure I have MQTT right
>>
>> On Thursday, December 27, 2018 at 4:24:08 PM UTC-8, Pat wrote:
>>>
>>> Under [[[Extras]]] you don't have any of the skin specific MQTT
>>> settings

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

[Scott Grayban]

I tried that but I still get the error.

On Wednesday, December 26, 2018 at 5:15:50 PM UTC-8, Pat wrote:
>
> You need to make them an array. Something like: 
>
> schema = schemas.wview.schema + [('appTemp',   'REAL'), ('windrun',  
>  'REAL')]
>
>
> On Wednesday, December 26, 2018 at 6:27:53 PM UTC-5, Colin Larsen wrote:
>>
>> Maybe I did it wrong - but all I did was add the 2 new fields in the 
>> original wview schema, which for me was hiding in /var/lib/weewx/schemas 
>> from memory and then did the --rebuild which ran perfectly. 
>>
>> There may be a good reason for not doing that :) so I may not be giving 
>> you the best advice but it did work fine.
>>
>> Colin
>>
>> On Thu, Dec 27, 2018 at 12:19 PM Scott Grayban  wrote:
>>
>>> I tried adding 1 at a time but it deletes the previous one. Certainly 
>>> you should be able to add more then just 1 right ?
>>>
>>> On Wednesday, December 26, 2018 at 6:54:40 AM UTC-8, Andrew Milner wrote:

 I think You should probably only have one new schema specified - not 
 two - when you do the reconfigure



 On Wednesday, 26 December 2018 14:19:27 UTC+2, Scott Grayban wrote:
>
> Step 2 is not working at all for me...
>
> If I have
> *schema = user.extensions.schema_apptemp*
> *schema = user.extensions.schema_windrun*
>
> added in the 
>
> *[DataBindings]*
> *[[wx_binding]]*
>
>
> *wee_database weewx.conf --reconfigure*
>
> Gives this error
>
> *configobj.DuplicateError: Duplicate keyword name at line 402.*
>
>
> On Sunday, December 9, 2018 at 1:51:15 PM UTC-8, Philip Kutzenco wrote:
>
> 2) Stop weewx and edit weewx.conf to tell it to use this new schema 
>> extension by adding the *schema = line* below to the [DataBindings] 
>> stanza:
>>
>>
>>
>>
>> *[DataBindings][[wx_binding]]...schema = 
>> user.extensions.schema_apptemp*
>>
>>
>>
>> 3) Create a new copy of the database with the extended schema
>>
>> *wee_database weewx.conf --reconfigure*
>> and then rename the databases
>>
>>
>>
>> 4) Rebuild the database with new daily values
>>
>> *Sudo wee_database --rebuild-daily*
>>
>>
>>
>> 5) restart weewx
>>
>> phil
>>
>> On Sunday, December 9, 2018 at 4:27:23 PM UTC-5, Dj Merrill wrote:
>>>
>>> Please forgive my ignorance.  It is not clear after reading the 
>>> instructions on extending the database precisely what I should do in 
>>> this 
>>> case.  Obviously we don't have an "user/electricity.py" file, but we do 
>>> have a "user/belchertown.py" file.
>>>
>>> Should I modify the "belchertown.py" file with something like:
>>>
>>> import schemas.wview
>>> schema_with_apptemp = schemas.wview.schema + [('appTemp', 'REAL')]
>>>
>>>
>>> Then modify weewx.conf to have:
>>>
>>> [DataBindings]
>>> [[wx_binding]]
>>> database = archive_sqlite
>>> table_name = archive
>>> manager = weewx.wxmanager.WXDaySummaryManager
>>> schema = user.belchertown.schema_with_apptemp
>>>
>>>
>>> I am using SQLlite so I believe I can skip step 3.
>>>
>>> Then, "wee_database weewx.conf --reconfigure" and rename the 
>>> databases?
>>>
>>> Thanks,
>>>
>>> -Dj
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> 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 Skin 0.8.1 released

[Pat]

You need to make them an array. Something like: 

schema = schemas.wview.schema + [('appTemp',   'REAL'), ('windrun',  
 'REAL')]


On Wednesday, December 26, 2018 at 6:27:53 PM UTC-5, Colin Larsen wrote:
>
> Maybe I did it wrong - but all I did was add the 2 new fields in the 
> original wview schema, which for me was hiding in /var/lib/weewx/schemas 
> from memory and then did the --rebuild which ran perfectly. 
>
> There may be a good reason for not doing that :) so I may not be giving 
> you the best advice but it did work fine.
>
> Colin
>
> On Thu, Dec 27, 2018 at 12:19 PM Scott Grayban  > wrote:
>
>> I tried adding 1 at a time but it deletes the previous one. Certainly you 
>> should be able to add more then just 1 right ?
>>
>> On Wednesday, December 26, 2018 at 6:54:40 AM UTC-8, Andrew Milner wrote:
>>>
>>> I think You should probably only have one new schema specified - not two 
>>> - when you do the reconfigure
>>>
>>>
>>>
>>> On Wednesday, 26 December 2018 14:19:27 UTC+2, Scott Grayban wrote:

 Step 2 is not working at all for me...

 If I have
 *schema = user.extensions.schema_apptemp*
 *schema = user.extensions.schema_windrun*

 added in the 

 *[DataBindings]*
 *[[wx_binding]]*


 *wee_database weewx.conf --reconfigure*

 Gives this error

 *configobj.DuplicateError: Duplicate keyword name at line 402.*


 On Sunday, December 9, 2018 at 1:51:15 PM UTC-8, Philip Kutzenco wrote:

 2) Stop weewx and edit weewx.conf to tell it to use this new schema 
> extension by adding the *schema = line* below to the [DataBindings] 
> stanza:
>
>
>
>
> *[DataBindings][[wx_binding]]...schema = 
> user.extensions.schema_apptemp*
>
>
>
> 3) Create a new copy of the database with the extended schema
>
> *wee_database weewx.conf --reconfigure*
> and then rename the databases
>
>
>
> 4) Rebuild the database with new daily values
>
> *Sudo wee_database --rebuild-daily*
>
>
>
> 5) restart weewx
>
> phil
>
> On Sunday, December 9, 2018 at 4:27:23 PM UTC-5, Dj Merrill wrote:
>>
>> Please forgive my ignorance.  It is not clear after reading the 
>> instructions on extending the database precisely what I should do in 
>> this 
>> case.  Obviously we don't have an "user/electricity.py" file, but we do 
>> have a "user/belchertown.py" file.
>>
>> Should I modify the "belchertown.py" file with something like:
>>
>> import schemas.wview
>> schema_with_apptemp = schemas.wview.schema + [('appTemp', 'REAL')]
>>
>>
>> Then modify weewx.conf to have:
>>
>> [DataBindings]
>> [[wx_binding]]
>> database = archive_sqlite
>> table_name = archive
>> manager = weewx.wxmanager.WXDaySummaryManager
>> schema = user.belchertown.schema_with_apptemp
>>
>>
>> I am using SQLlite so I believe I can skip step 3.
>>
>> Then, "wee_database weewx.conf --reconfigure" and rename the 
>> databases?
>>
>> Thanks,
>>
>> -Dj
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com .
>> 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 Skin 0.8.1 released

[Colin Larsen]

Maybe I did it wrong - but all I did was add the 2 new fields in the
original wview schema, which for me was hiding in /var/lib/weewx/schemas
from memory and then did the --rebuild which ran perfectly.

There may be a good reason for not doing that :) so I may not be giving you
the best advice but it did work fine.

Colin

On Thu, Dec 27, 2018 at 12:19 PM Scott Grayban  wrote:

> I tried adding 1 at a time but it deletes the previous one. Certainly you
> should be able to add more then just 1 right ?
>
> On Wednesday, December 26, 2018 at 6:54:40 AM UTC-8, Andrew Milner wrote:
>>
>> I think You should probably only have one new schema specified - not two
>> - when you do the reconfigure
>>
>>
>>
>> On Wednesday, 26 December 2018 14:19:27 UTC+2, Scott Grayban wrote:
>>>
>>> Step 2 is not working at all for me...
>>>
>>> If I have
>>> *schema = user.extensions.schema_apptemp*
>>> *schema = user.extensions.schema_windrun*
>>>
>>> added in the
>>>
>>> *[DataBindings]*
>>> *[[wx_binding]]*
>>>
>>>
>>> *wee_database weewx.conf --reconfigure*
>>>
>>> Gives this error
>>>
>>> *configobj.DuplicateError: Duplicate keyword name at line 402.*
>>>
>>>
>>> On Sunday, December 9, 2018 at 1:51:15 PM UTC-8, Philip Kutzenco wrote:
>>>
>>> 2) Stop weewx and edit weewx.conf to tell it to use this new schema
 extension by adding the *schema = line* below to the [DataBindings]
 stanza:




 *[DataBindings][[wx_binding]]...schema =
 user.extensions.schema_apptemp*



 3) Create a new copy of the database with the extended schema

 *wee_database weewx.conf --reconfigure*
 and then rename the databases



 4) Rebuild the database with new daily values

 *Sudo wee_database --rebuild-daily*



 5) restart weewx

 phil

 On Sunday, December 9, 2018 at 4:27:23 PM UTC-5, Dj Merrill wrote:
>
> Please forgive my ignorance.  It is not clear after reading the
> instructions on extending the database precisely what I should do in this
> case.  Obviously we don't have an "user/electricity.py" file, but we do
> have a "user/belchertown.py" file.
>
> Should I modify the "belchertown.py" file with something like:
>
> import schemas.wview
> schema_with_apptemp = schemas.wview.schema + [('appTemp', 'REAL')]
>
>
> Then modify weewx.conf to have:
>
> [DataBindings]
> [[wx_binding]]
> database = archive_sqlite
> table_name = archive
> manager = weewx.wxmanager.WXDaySummaryManager
> schema = user.belchertown.schema_with_apptemp
>
>
> I am using SQLlite so I believe I can skip step 3.
>
> Then, "wee_database weewx.conf --reconfigure" and rename the databases?
>
> Thanks,
>
> -Dj
>
> --
> 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 Skin 0.8.1 released

[Colin Larsen]

Yes, unfortunately that is taken from the Darksky current conditions so it
breaks. I was considering raising a request with Pat to use that
independent of using the forecast display

On Fri, 14 Dec 2018, 05:25 G Hammer  Did that change affect the current condition graphic next to the current
> temp?
>
>
> On Tuesday, December 11, 2018 at 8:33:57 PM UTC-5, Colin Larsen wrote:
>>
>> I came across the Darksky widgets today and they do include alerts
>>
>> https://darksky.net/widgets
>>
>> I've just replaced the whole Darksky forecast section with a 'hook' page
>> to place the week widget there instead. Apparently it does include alerts.
>> I have found the downloaded forecast data to be way off in temp - as much
>> as 3 deg celsius low, even compared to their own widget which is both
>> confusing and surprising. It appears that for me the widget forecast is
>> much better than the api download data
>>
>> On Wed, Dec 12, 2018 at 2:26 PM rich T  wrote:
>>
>>> Is there a way to include alerts from Darksky?
>>>
>>> On Friday, December 7, 2018 at 5:12:23 PM UTC-5, 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+...@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 Skin 0.8.1 released

[G Hammer]

Did that change affect the current condition graphic next to the current 
temp?


On Tuesday, December 11, 2018 at 8:33:57 PM UTC-5, Colin Larsen wrote:
>
> I came across the Darksky widgets today and they do include alerts
>
> https://darksky.net/widgets
>
> I've just replaced the whole Darksky forecast section with a 'hook' page 
> to place the week widget there instead. Apparently it does include alerts. 
> I have found the downloaded forecast data to be way off in temp - as much 
> as 3 deg celsius low, even compared to their own widget which is both 
> confusing and surprising. It appears that for me the widget forecast is 
> much better than the api download data
>
> On Wed, Dec 12, 2018 at 2:26 PM rich T > 
> wrote:
>
>> Is there a way to include alerts from Darksky?
>>
>> On Friday, December 7, 2018 at 5:12:23 PM UTC-5, 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+...@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 Skin 0.8.1 released - Suggestion

[Pat]

haha, nope, maybe an early bed time

On Wednesday, December 12, 2018 at 8:00:05 PM UTC-5, Colin Larsen wrote:
>
> Quick, more coffee!  :D
>
> On Thu, 13 Dec 2018, 13:56 Pat  wrote:
>
>> Wow, I'm having a hard time replying clearly tonight. 
>>
>> Find this. It should say "false". 
>>
>> navigator: {
>>  enabled: false
>>  },
>>
>>
>> and set it to true :)
>>
>>
>> On Wednesday, December 12, 2018 at 7:54:51 PM UTC-5, Pat wrote:
>>>
>>> The skin actually uses HighStock 
>>> 
>>>  but 
>>> has the timeline disabled. Feel free to enable it in your setup :)
>>>
>>> To do so, edit the skins/Belchertown/js/highcharts-dayplots.js and 
>>> weekplot, monthplot and yearplot.js files. 
>>>
>>> Then search for 
>>>
>>>
>>> navigator: {
>>> enabled: true
>>> },
>>>
>>> and set to true for the plots you want it enabled for. You may have to 
>>> do this for multiple plots depending on how you want to customize it.
>>>
>>> Save and restart weewx. Wait for an archive interval and refresh the 
>>> page. 
>>>
>>> See attached image for an example. 
>>>
>>> On Tuesday, December 11, 2018 at 11:38:07 PM UTC-5, WILWetter25 wrote:

 The Akin use Highcharts currently.
 In the link I posted you will See a example for HighStock. The 
 difference between Highcharts and HighStock: In HighStock you can choose a 
 Date, time. 
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com .
>> 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 Skin 0.8.1 released - Suggestion

[Colin Larsen]

Quick, more coffee!  :D

On Thu, 13 Dec 2018, 13:56 Pat  Wow, I'm having a hard time replying clearly tonight.
>
> Find this. It should say "false".
>
> navigator: {
>  enabled: false
>  },
>
>
> and set it to true :)
>
>
> On Wednesday, December 12, 2018 at 7:54:51 PM UTC-5, Pat wrote:
>>
>> The skin actually uses HighStock
>> 
>>  but
>> has the timeline disabled. Feel free to enable it in your setup :)
>>
>> To do so, edit the skins/Belchertown/js/highcharts-dayplots.js and
>> weekplot, monthplot and yearplot.js files.
>>
>> Then search for
>>
>>
>> navigator: {
>> enabled: true
>> },
>>
>> and set to true for the plots you want it enabled for. You may have to do
>> this for multiple plots depending on how you want to customize it.
>>
>> Save and restart weewx. Wait for an archive interval and refresh the
>> page.
>>
>> See attached image for an example.
>>
>> On Tuesday, December 11, 2018 at 11:38:07 PM UTC-5, WILWetter25 wrote:
>>>
>>> The Akin use Highcharts currently.
>>> In the link I posted you will See a example for HighStock. The
>>> difference between Highcharts and HighStock: In HighStock you can choose a
>>> Date, time.
>>
>> --
> 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 Skin 0.8.1 released

[Colin Larsen]

I came across the Darksky widgets today and they do include alerts

https://darksky.net/widgets

I've just replaced the whole Darksky forecast section with a 'hook' page to
place the week widget there instead. Apparently it does include alerts. I
have found the downloaded forecast data to be way off in temp - as much as
3 deg celsius low, even compared to their own widget which is both
confusing and surprising. It appears that for me the widget forecast is
much better than the api download data

On Wed, Dec 12, 2018 at 2:26 PM rich T  wrote:

> Is there a way to include alerts from Darksky?
>
> On Friday, December 7, 2018 at 5:12:23 PM UTC-5, 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.
>

-- 
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

[Colin Larsen]

Great news, glad to hear you sorted it.

Cheers
Colin

On Wed, 12 Dec 2018, 03:47 G Hammer  I did. The sqlite3 commands from Phil allowed me to see that whatever
> config I did was not actually active.
> I blame user error as I had edited files on one machine and ftp'd the
> files to the server.
> Performing the entire process on the server gave the expected result.
>
> Thanks for the education to all!
>
> On Monday, December 10, 2018 at 7:05:31 PM UTC-5, Colin Larsen wrote:
>>
>> Do you also see errors on your Records page where Highest App Temp and
>> Lowest App temp are?
>>
>> On Tue, Dec 11, 2018 at 12:03 PM  wrote:
>>
>>> That should do it.
>>>
>>> If you have sqlite3 installed, you can open the database with the
>>> command sqlite3 weewx.sdb and then issue the command:
>>>
>>>  .schema archive
>>>
>>> You should see `appTemp` REAL at the end of the list.
>>>
>>> The command:
>>>
>>>  .tables
>>>
>>> should show archive_day_appTemp somewhere in the list.
>>>
>>>  .exit
>>>
>>> will exit the program
>>>
>>> It's best to have weewx stopped prior to opening the database with
>>> sqlite3.
>>> phil
>>>
>>>
>>> On Monday, December 10, 2018 at 5:41:02 PM UTC-5, G Hammer wrote:
>>>
 Hmmm, well then I'm at a loss.
 I though the database had been extended.

 Here's what I did:

 Edit extensions.py to be:
 import schemas.wview
 schema_apptemp = schemas.wview.schema + [('appTemp',   'REAL')]
 Stop weewx
 Edit weewx.conf to have:
 [DataBindings]

 [[wx_binding]]
 # The database must match one of the sections in [Databases].
 # This is likely to be the only option you would want to
 change.
 database = archive_sqlite
 # The name of the table within the database
 table_name = archive
 # The manager handles aggregation of data for historical
 summaries
 manager = weewx.wxmanager.WXDaySummaryManager
 # The schema defines the structure of the database.
 # It is *only* used when the database is created.
 #schema = schemas.wview.schema
 schema = user.extensions.schema_apptemp
 Ran wee_database weewx.conf --reconfigure
 Renamed weewx.sdb to weewx.sdb.org
 Renamed the new file to weewx.sdb
 Ran wee_database --rebuild-daily

 Start weewx


 On Monday, December 10, 2018 at 1:30:05 PM UTC-5, Colin Larsen wrote:
>
> If you haven't extended the database as per the Weewx wiki you will
> get those errors. I haven't written a guide but it is reasonably
> straightforward
>
> On Tue, 11 Dec 2018, 07:05 G Hammer 
>> Yes, in fact followed your guide above.
>> The Feels like shows in the temp display, but when enabled in charts
>> you get the error.
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to weewx-user+...@googlegroups.com.
>> 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+...@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 Skin 0.8.1 released

[Colin Larsen]

Do you also see errors on your Records page where Highest App Temp and
Lowest App temp are?

On Tue, Dec 11, 2018 at 12:03 PM  wrote:

> That should do it.
>
> If you have sqlite3 installed, you can open the database with the command 
> sqlite3
> weewx.sdb and then issue the command:
>
>  .schema archive
>
> You should see `appTemp` REAL at the end of the list.
>
> The command:
>
>  .tables
>
> should show archive_day_appTemp somewhere in the list.
>
>  .exit
>
> will exit the program
>
> It's best to have weewx stopped prior to opening the database with sqlite3.
> phil
>
>
> On Monday, December 10, 2018 at 5:41:02 PM UTC-5, G Hammer wrote:
>
>> Hmmm, well then I'm at a loss.
>> I though the database had been extended.
>>
>> Here's what I did:
>>
>> Edit extensions.py to be:
>> import schemas.wview
>> schema_apptemp = schemas.wview.schema + [('appTemp',   'REAL')]
>> Stop weewx
>> Edit weewx.conf to have:
>> [DataBindings]
>>
>> [[wx_binding]]
>> # The database must match one of the sections in [Databases].
>> # This is likely to be the only option you would want to change.
>> database = archive_sqlite
>> # The name of the table within the database
>> table_name = archive
>> # The manager handles aggregation of data for historical
>> summaries
>> manager = weewx.wxmanager.WXDaySummaryManager
>> # The schema defines the structure of the database.
>> # It is *only* used when the database is created.
>> #schema = schemas.wview.schema
>> schema = user.extensions.schema_apptemp
>> Ran wee_database weewx.conf --reconfigure
>> Renamed weewx.sdb to weewx.sdb.org
>> Renamed the new file to weewx.sdb
>> Ran wee_database --rebuild-daily
>>
>> Start weewx
>>
>>
>> On Monday, December 10, 2018 at 1:30:05 PM UTC-5, Colin Larsen wrote:
>>>
>>> If you haven't extended the database as per the Weewx wiki you will get
>>> those errors. I haven't written a guide but it is reasonably straightforward
>>>
>>> On Tue, 11 Dec 2018, 07:05 G Hammer >>
 Yes, in fact followed your guide above.
 The Feels like shows in the temp display, but when enabled in charts
 you get the error.

 --
 You received this message because you are subscribed to the Google
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to weewx-user+...@googlegroups.com.
 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 Skin 0.8.1 released

[kutzenco]

That should do it.

If you have sqlite3 installed, you can open the database with the command 
sqlite3 
weewx.sdb and then issue the command:

 .schema archive

You should see `appTemp` REAL at the end of the list.

The command:

 .tables

should show archive_day_appTemp somewhere in the list.

 .exit

will exit the program

It's best to have weewx stopped prior to opening the database with sqlite3.
phil


On Monday, December 10, 2018 at 5:41:02 PM UTC-5, G Hammer wrote:

> Hmmm, well then I'm at a loss.
> I though the database had been extended.
>
> Here's what I did:
>
> Edit extensions.py to be:
> import schemas.wview
> schema_apptemp = schemas.wview.schema + [('appTemp',   'REAL')]
> Stop weewx
> Edit weewx.conf to have:
> [DataBindings]
> 
> [[wx_binding]]
> # The database must match one of the sections in [Databases].
> # This is likely to be the only option you would want to change.
> database = archive_sqlite
> # The name of the table within the database
> table_name = archive
> # The manager handles aggregation of data for historical summaries
> manager = weewx.wxmanager.WXDaySummaryManager
> # The schema defines the structure of the database.
> # It is *only* used when the database is created.
> #schema = schemas.wview.schema
> schema = user.extensions.schema_apptemp
> Ran wee_database weewx.conf --reconfigure
> Renamed weewx.sdb to weewx.sdb.org
> Renamed the new file to weewx.sdb
> Ran wee_database --rebuild-daily
>
> Start weewx
>
>
> On Monday, December 10, 2018 at 1:30:05 PM UTC-5, Colin Larsen wrote:
>>
>> If you haven't extended the database as per the Weewx wiki you will get 
>> those errors. I haven't written a guide but it is reasonably straightforward
>>
>> On Tue, 11 Dec 2018, 07:05 G Hammer >
>>> Yes, in fact followed your guide above. 
>>> The Feels like shows in the temp display, but when enabled in charts you 
>>> get the error. 
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> 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 Skin 0.8.1 released

[G Hammer]

Hmmm, well then I'm at a loss.
I though the database had been extended.

Here's what I did:

Edit extensions.py to be:
import schemas.wview
schema_apptemp = schemas.wview.schema + [('appTemp',   'REAL')]
Stop weewx
Edit weewx.conf to have:
[DataBindings]

[[wx_binding]]
# The database must match one of the sections in [Databases].
# This is likely to be the only option you would want to change.
database = archive_sqlite
# The name of the table within the database
table_name = archive
# The manager handles aggregation of data for historical summaries
manager = weewx.wxmanager.WXDaySummaryManager
# The schema defines the structure of the database.
# It is *only* used when the database is created.
#schema = schemas.wview.schema
schema = user.extensions.schema_apptemp
Ran wee_database weewx.conf --reconfigure
Renamed weewx.sdb to weewx.sdb.org
Renamed the new file to weewx.sdb
Ran wee_database --rebuild-daily

Start weewx


On Monday, December 10, 2018 at 1:30:05 PM UTC-5, Colin Larsen wrote:
>
> If you haven't extended the database as per the Weewx wiki you will get 
> those errors. I haven't written a guide but it is reasonably straightforward
>
> On Tue, 11 Dec 2018, 07:05 G Hammer  
> wrote:
>
>> Yes, in fact followed your guide above. 
>> The Feels like shows in the temp display, but when enabled in charts you 
>> get the error. 
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com .
>> 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 Skin 0.8.1 released

[Colin Larsen]

If you haven't extended the database as per the Weewx wiki you will get
those errors. I haven't written a guide but it is reasonably straightforward

On Tue, 11 Dec 2018, 07:05 G Hammer  Yes, in fact followed your guide above.
> The Feels like shows in the temp display, but when enabled in charts you
> get the error.
>
> --
> 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 Skin 0.8.1 released

[Colin Larsen]

You don't have the database extended for appTemp, it's an easy operation.
You will also have errors on the records page?

On Tue, 11 Dec 2018, 06:39 Philip Kutzenco  See my post above in this topic :
> https://groups.google.com/d/msg/weewx-user/ARBHWDXiDpQ/7cz4m-Q7BAAJ.
> 
>
> phil
>
>
> On Monday, December 10, 2018 at 11:22:58 AM UTC-5, Wes Witt wrote:
>>
>> following. i'm interested in using apptemp to but would like to know what
>> is necessary to get the archive table configured properly.
>>
>> On Monday, December 10, 2018 at 7:54:39 AM UTC-8, Philip Kutzenco wrote:
>>>
>>> This is likely a naive question on my part. But did you extend the
>>> schema on the archive table for your database to include appTemp? Assuming
>>> so, did you rebuild the daily value tables? Are the values in the archive
>>> table and the archive_day_appTemp table being populated? When I look at
>>> your website, your daily.json data shows appTemp with a value of "N/A".phil
>>>
>>>
>>> On Monday, December 10, 2018 at 10:09:52 AM UTC-5, G Hammer wrote:

 Here's the rest of the pertinent log entries that Groups cut off:
 Dec 10 09:55:50 ftp weewx[13683]:   raise weedb.
 NoColumnError(e)
 Dec 10 09:55:50 ftp weewx[13683]:   NoColumnError: no such
 column: appTemp
 Dec 10 09:55:50 ftp weewx[13683]:   Generator terminated
 Dec 10 09:55:50 ftp weewx[13683]: copygenerator: copied 0 files to /
 home/weewx/public_html/weather



 On Monday, December 10, 2018 at 10:07:01 AM UTC-5, G Hammer wrote:
>
> Pat,
>
> When I have show_apptemp=1 I do see the Feels like temp as I expect.
> If I set highcharts_show_apptemp = 1 I do not get an apptemp plot, the
> report generator errors out:
> Dec 10 09:55:50 ftp weewx[13683]: reportengine: Caught unrecoverable
> exception in generator weewx.cheetahgenerator.CheetahGenerator
> Dec 10 09:55:50 ftp weewx[13683]:   no such column:
> appTemp
> Dec 10 09:55:50 ftp weewx[13683]:   Traceback (most
> recent call last):
> Dec 10 09:55:50 ftp weewx[13683]: File
> "/home/weewx/bin/weewx/reportengine.py", line 239, in run
> Dec 10 09:55:50 ftp weewx[13683]:   obj.start()
> Dec 10 09:55:50 ftp weewx[13683]: File
> "/home/weewx/bin/weewx/reportengine.py", line 273, in start
> Dec 10 09:55:50 ftp weewx[13683]:   self.run()
> Dec 10 09:55:50 ftp weewx[13683]: File
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 158, in run
> Dec 10 09:55:50 ftp weewx[13683]:   ngen = self.
> generate(gen_dict[section_name], self.gen_ts)
> Dec 10 09:55:50 ftp weewx[13683]: File
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
> Dec 10 09:55:50 ftp weewx[13683]:   ngen += self.
> generate(section[subsection], gen_ts)
> Dec 10 09:55:50 ftp weewx[13683]: File
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
> Dec 10 09:55:50 ftp weewx[13683]:   ngen += self.
> generate(section[subsection], gen_ts)
> Dec 10 09:55:50 ftp weewx[13683]: File
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 320, in generate
> Dec 10 09:55:50 ftp weewx[13683]:   default_binding)
> Dec 10 09:55:50 ftp weewx[13683]: File
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 372, in
> _getSearchList
> Dec 10 09:55:50 ftp weewx[13683]:   searchList += obj.
> get_extension_list(timespan, db_lookup)
> Dec 10 09:55:50 ftp weewx[13683]: File
> "/home/weewx/bin/user/belchertown_highchartsSearchX.py", line 85, in
> get_extension_list
> Dec 10 09:55:50 ftp weewx[13683]:   (time_start_vt,
> time_stop_vt, appTemp_vt) = db_lookup().getSqlVectors(TimeSpan(
> _start_ts, _end_ts), 'appTemp')
> Dec 10 09:55:50 ftp weewx[13683]: File
> "/home/weewx/bin/weewx/manager.py", line 512, in getSqlVectors
> Dec 10 09:55:50 ftp weewx[13683]:   aggregate_type,
> aggregate_interval)
> Dec 10 09:55:50 ftp weewx[13683]: File
> "/home/weewx/bin/weewx/manager.py", line 775, in _getSqlVectors
> Dec 10 09:55:50 ftp weewx[13683]:   for _rec in
> _cursor.execute(sql_str, (startstamp, stopstamp)):
> Dec 10 09:55 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 

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

[John Clark]

Fair enough. I use Gimp to make them 60% transparent so it doesn't 
distract from the info. Wanted to try, and if I don't like it, I won't 
use it.


On 12/9/2018 9:43 AM, Pat wrote:
Hi John, I don't have plans right now to include that level of 
customization with the base theme because I'll never be able to keep 
everyone happy :)


You can make your own watermarks, or background changes if you want on 
your own install though! Edit the skins/Belchertown/style.css and on 
line 12 is for HTML, you can add your background there just like you 
did for your about page.


Restart weewx, and wait for the archive generation to copy the updated 
CSS to your site.


The problem is - as you'll see in the attached image example - is that 
the main container's background is all white because you want to be 
able to read text and see images on the site. Having a busy background 
can distract from the info. The container of the website is 1200px 
wide and gets smaller as your screen gets smaller (mobile screen, 
etc). So for example you could get fancy with a background that has a 
1200px center section "missing" then your sidebar areas could have the 
background you're looking for.


Hope this helps.

On Sunday, December 9, 2018 at 10:13:21 AM UTC-5, John Clark wrote:

BTW, if you look on my weather page ( weather.w0avq.org
<http://weather.w0avq.org> ) and click on "about" you can see what
I mean about a "watermark" for the site. Was just thinking out
loud that it would be nice to do if it weren't too much of a hassle.



 Forwarded Message ----
    Subject:    Re: [weewx-user] Re: Belchertown Skin 0.8.1 released
Date:   Sun, 9 Dec 2018 08:19:58 -0600
From:   John Clark  
To: weewx...@googlegroups.com 



Would be convenient to have it on the "front page" with the
"normal" temp.

On 12/9/2018 3:47 AM, Colin Larsen wrote:

Hi John

I see wind chill on your charts/graphs, were you looking to have
it someplace else?

73
Colin, ZL2ARL
41south.net.nz <http://41south.net.nz>

On Sun, 9 Dec 2018, 22:34 John Clark  wrote:

Just a query asking if it is a setting I missed, but I see no
wind chill display. Secondly, and this is just a thought from
a cosmetic standpoint, but the possible inclusion of a
background "watermark" for aesthetics. (snow for the winter,
etc) Thought I had it accomplished on my reports but every
ftp update wrote over my changes (sigh). Still and all,  I am
quite satisfied with how weather.w0avq.org
<http://weather.w0avq.org> looks.

On 12/8/2018 8:04 PM, Pat wrote:


Glad to hear all the positive feedback! All your sites look
great - but I could be biased :)

On Saturday, December 8, 2018 at 4:58:00 PM UTC-5, Alan
Bryant wrote:

Pat,

Just wanted to say thanks! I have mine up and running,
minus the logo and about page.
https://weather.bryantgeeks.com/
<https://weather.bryantgeeks.com/>.

Great skin and I am loving having such an easy and
beautiful view of my weather data.

Alan Bryant

On Friday, December 7, 2018 at 4:12:23 PM UTC-6, 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
<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+...@googlegroups.com
.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.


-- 
*/John Clark, WØAVQ

w0a...@gmail.com /*
-- 
*/John Clark, WØAVQ

w0a...@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 
<mailto:weewx-user+unsubscr...@googlegroups.com>.

For more options, visit https://groups.google.com/d/optout.

--
*/John Clark, WØAVQ
w0av...@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.
For more options, visit https://groups.google.com/d/optout.

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

[John Clark]

BTW, if you look on my weather page ( weather.w0avq.org 
<http://weather.w0avq.org> ) and click on "about" you can see what I 
mean about a "watermark" for the site. Was just thinking out loud that 
it would be nice to do if it weren't too much of a hassle.




 Forwarded Message ----
Subject:    Re: [weewx-user] Re: Belchertown Skin 0.8.1 released
Date:   Sun, 9 Dec 2018 08:19:58 -0600
From:   John Clark 
To: weewx-user@googlegroups.com



Would be convenient to have it on the "front page" with the "normal" temp.

On 12/9/2018 3:47 AM, Colin Larsen wrote:

Hi John

I see wind chill on your charts/graphs, were you looking to have it 
someplace else?


73
Colin, ZL2ARL
41south.net.nz <http://41south.net.nz>

On Sun, 9 Dec 2018, 22:34 John Clark <mailto:w0av...@gmail.com> wrote:


Just a query asking if it is a setting I missed, but I see no wind
chill display. Secondly, and this is just a thought from a
cosmetic standpoint, but the possible inclusion of a background
"watermark" for aesthetics. (snow for the winter, etc) Thought I
had it accomplished on my reports but every ftp update wrote over
my changes (sigh). Still and all,  I am quite satisfied with how
weather.w0avq.org <http://weather.w0avq.org> looks.

On 12/8/2018 8:04 PM, Pat wrote:


Glad to hear all the positive feedback! All your sites look great
- but I could be biased :)

On Saturday, December 8, 2018 at 4:58:00 PM UTC-5, Alan Bryant
wrote:

Pat,

Just wanted to say thanks! I have mine up and running, minus
the logo and about page. https://weather.bryantgeeks.com/.

Great skin and I am loving having such an easy and beautiful
view of my weather data.

Alan Bryant

On Friday, December 7, 2018 at 4:12:23 PM UTC-6, 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
<mailto:weewx-user+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.



--
*/John Clark, WØAVQ
w0av...@gmail.com/*
--
*/John Clark, WØAVQ
w0av...@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.
For more options, visit https://groups.google.com/d/optout.

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

[John Clark]

Would be convenient to have it on the "front page" with the "normal" temp.

On 12/9/2018 3:47 AM, Colin Larsen wrote:

Hi John

I see wind chill on your charts/graphs, were you looking to have it 
someplace else?


73
Colin, ZL2ARL
41south.net.nz 

On Sun, 9 Dec 2018, 22:34 John Clark  wrote:


Just a query asking if it is a setting I missed, but I see no wind
chill display. Secondly, and this is just a thought from a
cosmetic standpoint, but the possible inclusion of a background
"watermark" for aesthetics. (snow for the winter, etc) Thought I
had it accomplished on my reports but every ftp update wrote over
my changes (sigh). Still and all,  I am quite satisfied with how
weather.w0avq.org  looks.

On 12/8/2018 8:04 PM, Pat wrote:


Glad to hear all the positive feedback! All your sites look great
- but I could be biased :)

On Saturday, December 8, 2018 at 4:58:00 PM UTC-5, Alan Bryant
wrote:

Pat,

Just wanted to say thanks! I have mine up and running, minus
the logo and about page. https://weather.bryantgeeks.com/.

Great skin and I am loving having such an easy and beautiful
view of my weather data.

Alan Bryant

On Friday, December 7, 2018 at 4:12:23 PM UTC-6, 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.



--
*/John Clark, WØAVQ
w0av...@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.
For more options, visit https://groups.google.com/d/optout.

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

[Colin Larsen]

Hi John

I see wind chill on your charts/graphs, were you looking to have it
someplace else?

73
Colin, ZL2ARL
41south.net.nz

On Sun, 9 Dec 2018, 22:34 John Clark  Just a query asking if it is a setting I missed, but I see no wind chill
> display. Secondly, and this is just a thought from a cosmetic standpoint,
> but the possible inclusion of a background "watermark" for aesthetics.
> (snow for the winter, etc) Thought I had it accomplished on my reports but
> every ftp update wrote over my changes (sigh). Still and all,  I am quite
> satisfied with how weather.w0avq.org looks.
>
> On 12/8/2018 8:04 PM, Pat wrote:
>
> Glad to hear all the positive feedback! All your sites look great - but I
> could be biased :)
>
> On Saturday, December 8, 2018 at 4:58:00 PM UTC-5, Alan Bryant wrote:
>>
>> Pat,
>>
>> Just wanted to say thanks! I have mine up and running, minus the logo and
>> about page. https://weather.bryantgeeks.com/.
>>
>> Great skin and I am loving having such an easy and beautiful view of my
>> weather data.
>>
>> Alan Bryant
>>
>> On Friday, December 7, 2018 at 4:12:23 PM UTC-6, 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.
>
> --
>
> *John Clark, WØAVQ w0av...@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.
> 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 Skin 0.8.1 released

[John Clark]

Just a query asking if it is a setting I missed, but I see no wind chill 
display. Secondly, and this is just a thought from a cosmetic 
standpoint, but the possible inclusion of a background "watermark" for 
aesthetics. (snow for the winter, etc) Thought I had it accomplished on 
my reports but every ftp update wrote over my changes (sigh). Still and 
all,  I am quite satisfied with how weather.w0avq.org looks.


On 12/8/2018 8:04 PM, Pat wrote:

Glad to hear all the positive feedback! All your sites look great - 
but I could be biased :)


On Saturday, December 8, 2018 at 4:58:00 PM UTC-5, Alan Bryant wrote:

Pat,

Just wanted to say thanks! I have mine up and running, minus the
logo and about page. https://weather.bryantgeeks.com/
.

Great skin and I am loving having such an easy and beautiful view
of my weather data.

Alan Bryant

On Friday, December 7, 2018 at 4:12:23 PM UTC-6, 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.

--
*/John Clark, WØAVQ
w0av...@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.
For more options, visit https://groups.google.com/d/optout.

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

[Philip Kutzenco]

Also upgraded and working great (wx.kutzenco.com).
phil

On Friday, December 7, 2018 at 9:46:05 PM UTC-5, Colin Larsen wrote:
>
> Upgraded 41south.net.nz 
> 
>  
> and working great. In my footer I've added the version and updated date 
> just for reference.
>
> Colin
>
> On Sat, 8 Dec 2018, 12:25 Hector Valenzuela   wrote:
>
>> I installed version 0.1.  I'll have to try another version
>>
>> El viernes, 7 de diciembre de 2018, 15:12:23 (UTC-7), Pat escribió:
>>>
>>> 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+...@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 Skin 0.8.1 released

[Colin Larsen]

Upgraded 41south.net.nz and working great. In my footer I've added the
version and updated date just for reference.

Colin

On Sat, 8 Dec 2018, 12:25 Hector Valenzuela  I installed version 0.1.  I'll have to try another version
>
> El viernes, 7 de diciembre de 2018, 15:12:23 (UTC-7), Pat escribió:
>>
>> 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.
>

-- 
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.