[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

`outTempBatteryStatus` REAL, `inTempBatteryStatus` REAL, `appTemp` REAL, 
`windRun` REAL, `cloudbase` REAL);

Yup it's there.

On Saturday, December 29, 2018 at 6:52:30 AM UTC-8, Pat wrote:
>
> Verify your database has the windrun column
>
> On Saturday, December 29, 2018 at 1:09:14 AM UTC-5, Scott Grayban wrote:
>>
>> Am I missing something ???
>>
>> No data is getting pulled for *Highest Daily Wind Run* records.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

shit its windrun not windRun

On Saturday, December 29, 2018 at 6:52:30 AM UTC-8, Pat wrote:
>
> Verify your database has the windrun column
>
> On Saturday, December 29, 2018 at 1:09:14 AM UTC-5, Scott Grayban wrote:
>>
>> Am I missing something ???
>>
>> No data is getting pulled for *Highest Daily Wind Run* records.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

Verify your database has the windrun column

On Saturday, December 29, 2018 at 1:09:14 AM UTC-5, Scott Grayban wrote:
>
> Am I missing something ???
>
> No data is getting pulled for *Highest Daily Wind Run* records.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

Am I missing something ???

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

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Scott Grayban]

Created a new issue #33 


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

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

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

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

, ('cloudbase', 'REAL')

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



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

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Pat]

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Scott Grayban]

Donated also...

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

 Can everyone else check again please ?

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

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

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

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

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

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

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

What would the format be ?

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

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Pat]

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

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

 Ahh so use my router IP instead and port forward 

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

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

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

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

 Is your broker or weewx available to the public?


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

Re: [weewx-user] Re: Belchertown 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

[G Hammer]

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

[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

[Colin Larsen]

Yes indeed, that should do it. You can just put your domain name in the
same as I have. And port forward external port 9001 to 192.168.0.4 port 9001

On Fri, Dec 28, 2018 at 2:40 PM 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 you
> verify from your computer that MQTT is wokring

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

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

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 have

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

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 
>> .
>>  
>> At a minimum you need mqtt_enabled, which you have, but also 
>> mqtt_host 
>> and mqtt_topic.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

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 
> .
>  
> At a minimum you need mqtt_enabled, which you have, but also 
> mqtt_host 
> and mqtt_topic.
>
> As mentioned previously, weewx is posting to your MQTT broker 
> using [[MQTT]], the skin also needs to know where the broker is so it 
> can 
> get that data too and that's done in [[Belchertown]] [[[Extras]]]. 
>
> On Thursday, 

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

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 
 .
  
 At a minimum you need mqtt_enabled, which you have, but also mqtt_host 
 and mqtt_topic.

 As mentioned previously, weewx is posting to your MQTT broker using 
 [[MQTT]], the skin also needs to know where the broker is so it can 
 get 
 that data too and that's done in [[Belchertown]] [[[Extras]]]. 

 On Thursday, December 27, 2018 at 7:21:33 PM UTC-5, Scott Grayban 
 wrote:
>
> [[Belchertown]]
> HTML_ROOT = /home/weewx/public_html/Nettleton
> skin = Nettleton
> [[[Extras]]]
> belchertown_root_url = http://
> www.nettletondistrict.com/Nettleton
> logo_image = http://
> www.nettleto

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

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 
>>> .
>>>  
>>> At a minimum you need mqtt_enabled, which you have, but also mqtt_host 
>>> and mqtt_topic.
>>>
>>> As mentioned previously, weewx is posting to your MQTT broker using 
>>> [[MQTT]], the skin also needs to know where the broker is so it can get 
>>> that data too and that's done in [[Belchertown]] [[[Extras]]]. 
>>>
>>> On Thursday, December 27, 2018 at 7:21:33 PM UTC-5, Scott Grayban 
>>> wrote:

 [[Belchertown]]
 HTML_ROOT = /home/weewx/public_html/Nettleton
 skin = Nettleton
 [[[Extras]]]
 belchertown_root_url = http://
 www.nettletondistrict.com/Nettleton
 logo_image = http://
 www.nettletondistrict.com/Nettleton/images/map_of_spokane_wa.jpg
 site_title = Nettleton District Weather Station
 footer_copyright_text = "Nettleton District Weather 
 Station, Spokane, Washington"
 radar_html = ""
 mqtt_enabled = 1
 show_apptemp = 1
 show_windrun = 1
 highcharts_show_apptemp = 1
 forecast_enabled = 1
 darksky_secret_

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

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 
>> .
>>  
>> At a minimum you need mqtt_enabled, which you have, but also mqtt_host 
>> and mqtt_topic.
>>
>> As mentioned previously, weewx is posting to your MQTT broker using 
>> [[MQTT]], the skin also needs to know where the broker is so it can get 
>> that data too and that's done in [[Belchertown]] [[[Extras]]]. 
>>
>> On Thursday, December 27, 2018 at 7:21:33 PM UTC-5, Scott Grayban 
>> wrote:
>>>
>>> [[Belchertown]]
>>> HTML_ROOT = /home/weewx/public_html/Nettleton
>>> skin = Nettleton
>>> [[[Extras]]]
>>> belchertown_root_url = http://
>>> www.nettletondistrict.com/Nettleton
>>> logo_image = http://
>>> www.nettletondistrict.com/Nettleton/images/map_of_spokane_wa.jpg
>>> site_title = Nettleton District Weather Station
>>> footer_copyright_text = "Nettleton District Weather 
>>> Station, Spokane, Washington"
>>> radar_html = ""
>>> mqtt_enabled = 1
>>> show_apptemp = 1
>>> show_windrun = 1
>>> highcharts_show_apptemp = 1
>>> forecast_enabled = 1
>>> darksky_secret_key = XX
>>> earthquake_enabled = 1
>>> facebook_enabled = 1
>>> twitter_enabled = 1
>>> graphs_page_header = "Weather Observation Graphs"
>>> records_page_header = "Weather Observation Records"
>>> reports_page_header = "Weather Observation Reports"
>>> about_page_header = "About This Weather Station"
>>>
>>>
>>>
>>>
>>> On Thursday, December 27, 2018 at 4:15:22 PM UTC-8, Pat wrote:
>>>

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

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 
> .
>  
> At a minimum you need mqtt_enabled, which you have, but also mqtt_host 
> and mqtt_topic.
>
> As mentioned previously, weewx is posting to your MQTT broker using 
> [[MQTT]], the skin also needs to know where the broker is so it can get 
> that data too and that's done in [[Belchertown]] [[[Extras]]]. 
>
> On Thursday, December 27, 2018 at 7:21:33 PM UTC-5, Scott Grayban 
> wrote:
>>
>> [[Belchertown]]
>> HTML_ROOT = /home/weewx/public_html/Nettleton
>> skin = Nettleton
>> [[[Extras]]]
>> belchertown_root_url = http://
>> www.nettletondistrict.com/Nettleton
>> logo_image = http://
>> www.nettletondistrict.com/Nettleton/images/map_of_spokane_wa.jpg
>> site_title = Nettleton District Weather Station
>> footer_copyright_text = "Nettleton District Weather 
>> Station, Spokane, Washington"
>> radar_html = ""
>> mqtt_enabled = 1
>> show_apptemp = 1
>> show_windrun = 1
>> highcharts_show_apptemp = 1
>> forecast_enabled = 1
>> darksky_secret_key = XX
>> earthquake_enabled = 1
>> facebook_enabled = 1
>> twitter_enabled = 1
>> graphs_page_header = "Weather Observation Graphs"
>> records_page_header = "Weather Observation Records"
>> reports_page_header = "Weather Observation Reports"
>> about_page_header = "About This Weather Station"
>>
>>
>>
>>
>> On Thursday, December 27, 2018 at 4:15:22 PM UTC-8, Pat wrote:
>>>
>>> Please post your Belchertown skin settings.
>>>
>>> On Thursday, December 27, 2018 at 7:00:21 PM UTC-5, Scott Grayban 
>>> wrote:

 Ok so my weewx.conf looks like this now
 [[MQTT]]
 server_url = mqtt://weewx:passwordX@192.168.0.4:1883/
 topic = weather/#
 unit_system = US
 binding = archive, loop
 aggregation = aggregate



 My /etc

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

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 
 .
  
 At a minimum you need mqtt_enabled, which you have, but also mqtt_host and 
 mqtt_topic.

 As mentioned previously, weewx is posting to your MQTT broker using 
 [[MQTT]], the skin also needs to know where the broker is so it can get 
 that data too and that's done in [[Belchertown]] [[[Extras]]]. 

 On Thursday, December 27, 2018 at 7:21:33 PM UTC-5, Scott Grayban wrote:
>
> [[Belchertown]]
> HTML_ROOT = /home/weewx/public_html/Nettleton
> skin = Nettleton
> [[[Extras]]]
> belchertown_root_url = http://
> www.nettletondistrict.com/Nettleton
> logo_image = http://
> www.nettletondistrict.com/Nettleton/images/map_of_spokane_wa.jpg
> site_title = Nettleton District Weather Station
> footer_copyright_text = "Nettleton District Weather 
> Station, Spokane, Washington"
> radar_html = ""
> mqtt_enabled = 1
> show_apptemp = 1
> show_windrun = 1
> highcharts_show_apptemp = 1
> forecast_enabled = 1
> darksky_secret_key = XX
> earthquake_enabled = 1
> facebook_enabled = 1
> twitter_enabled = 1
> graphs_page_header = "Weather Observation Graphs"
> records_page_header = "Weather Observation Records"
> reports_page_header = "Weather Observation Reports"
> about_page_header = "About This Weather Station"
>
>
>
>
> On Thursday, December 27, 2018 at 4:15:22 PM UTC-8, Pat wrote:
>>
>> Please post your Belchertown skin settings.
>>
>> On Thursday, December 27, 2018 at 7:00:21 PM UTC-5, Scott Grayban 
>> wrote:
>>>
>>> Ok so my weewx.conf looks like this now
>>> [[MQTT]]
>>> server_url = mqtt://weewx:passwordX@192.168.0.4:1883/
>>> topic = weather/#
>>> unit_system = US
>>> binding = archive, loop
>>> aggregation = aggregate
>>>
>>>
>>>
>>> My /etc/mosquitto/conf.d/myconfig.conf looks like this
>>> persistence false
>>> allow_anonymous true
>>> password_file /etc/mosquitto/passwd
>>> acl_file /etc/mosquitto/acl
>>>
>>> listener 1883
>>> protocol mqtt
>>>
>>> # websockets
>>> listener 9001
>>> protocol websockets
>>>
>>> Still not connecting. I wonder if thats do to the reverse proxy 
>>> with apache ?
>>>
>>>
>>> On Thursday, December 27, 2018 at 5:31:22 AM UTC-8, Pat wrote:

 This is because your MQTT is isolated to localhost only. Local host 
 in this case would be your weewx server, which you must have installed 
 MQTT 
>>>

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

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 
>>> .
>>>  
>>> At a minimum you need mqtt_enabled, which you have, but also mqtt_host and 
>>> mqtt_topic.
>>>
>>> As mentioned previously, weewx is posting to your MQTT broker using 
>>> [[MQTT]], the skin also needs to know where the broker is so it can get 
>>> that data too and that's done in [[Belchertown]] [[[Extras]]]. 
>>>
>>> On Thursday, December 27, 2018 at 7:21:33 PM UTC-5, Scott Grayban wrote:

 [[Belchertown]]
 HTML_ROOT = /home/weewx/public_html/Nettleton
 skin = Nettleton
 [[[Extras]]]
 belchertown_root_url = http://
 www.nettletondistrict.com/Nettleton
 logo_image = http://
 www.nettletondistrict.com/Nettleton/images/map_of_spokane_wa.jpg
 site_title = Nettleton District Weather Station
 footer_copyright_text = "Nettleton District Weather 
 Station, Spokane, Washington"
 radar_html = ""
 mqtt_enabled = 1
 show_apptemp = 1
 show_windrun = 1
 highcharts_show_apptemp = 1
 forecast_enabled = 1
 darksky_secret_key = XX
 earthquake_enabled = 1
 facebook_enabled = 1
 twitter_enabled = 1
 graphs_page_header = "Weather Observation Graphs"
 records_page_header = "Weather Observation Records"
 reports_page_header = "Weather Observation Reports"
 about_page_header = "About This Weather Station"




 On Thursday, December 27, 2018 at 4:15:22 PM UTC-8, Pat wrote:
>
> Please post your Belchertown skin settings.
>
> On Thursday, December 27, 2018 at 7:00:21 PM UTC-5, Scott Grayban 
> wrote:
>>
>> Ok so my weewx.conf looks like this now
>> [[MQTT]]
>> server_url = mqtt://weewx:passwordX@192.168.0.4:1883/
>> topic = weather/#
>> unit_system = US
>> binding = archive, loop
>> aggregation = aggregate
>>
>>
>>
>> My /etc/mosquitto/conf.d/myconfig.conf looks like this
>> persistence false
>> allow_anonymous true
>> password_file /etc/mosquitto/passwd
>> acl_file /etc/mosquitto/acl
>>
>> listener 1883
>> protocol mqtt
>>
>> # websockets
>> listener 9001
>> protocol websockets
>>
>> Still not connecting. I wonder if thats do to the reverse proxy 
>> with apache ?
>>
>>
>> On Thursday, December 27, 2018 at 5:31:22 AM UTC-8, Pat wrote:
>>>
>>> This is because your MQTT is isolated to localhost only. Local host 
>>> in this case would be your weewx server, which you must have installed 
>>> MQTT 
>>> on as well. Which works for weewx ==> MQTT since they are on the same 
>>> system, but nothing else
>>>
>>> First, change your MQTT to listen on 1883 for external connections. 
>>> Since you're not using SSL, you can remove th

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

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 
>> .
>>  
>> At a minimum you need mqtt_enabled, which you have, but also mqtt_host and 
>> mqtt_topic.
>>
>> As mentioned previously, weewx is posting to your MQTT broker using 
>> [[MQTT]], the skin also needs to know where the broker is so it can get 
>> that data too and that's done in [[Belchertown]] [[[Extras]]]. 
>>
>> On Thursday, December 27, 2018 at 7:21:33 PM UTC-5, Scott Grayban wrote:
>>>
>>> [[Belchertown]]
>>> HTML_ROOT = /home/weewx/public_html/Nettleton
>>> skin = Nettleton
>>> [[[Extras]]]
>>> belchertown_root_url = http://
>>> www.nettletondistrict.com/Nettleton
>>> logo_image = http://
>>> www.nettletondistrict.com/Nettleton/images/map_of_spokane_wa.jpg
>>> site_title = Nettleton District Weather Station
>>> footer_copyright_text = "Nettleton District Weather 
>>> Station, Spokane, Washington"
>>> radar_html = ""
>>> mqtt_enabled = 1
>>> show_apptemp = 1
>>> show_windrun = 1
>>> highcharts_show_apptemp = 1
>>> forecast_enabled = 1
>>> darksky_secret_key = XX
>>> earthquake_enabled = 1
>>> facebook_enabled = 1
>>> twitter_enabled = 1
>>> graphs_page_header = "Weather Observation Graphs"
>>> records_page_header = "Weather Observation Records"
>>> reports_page_header = "Weather Observation Reports"
>>> about_page_header = "About This Weather Station"
>>>
>>>
>>>
>>>
>>> On Thursday, December 27, 2018 at 4:15:22 PM UTC-8, Pat wrote:

 Please post your Belchertown skin settings.

 On Thursday, December 27, 2018 at 7:00:21 PM UTC-5, Scott Grayban wrote:
>
> Ok so my weewx.conf looks like this now
> [[MQTT]]
> server_url = mqtt://weewx:passwordX@192.168.0.4:1883/
> topic = weather/#
> unit_system = US
> binding = archive, loop
> aggregation = aggregate
>
>
>
> My /etc/mosquitto/conf.d/myconfig.conf looks like this
> persistence false
> allow_anonymous true
> password_file /etc/mosquitto/passwd
> acl_file /etc/mosquitto/acl
>
> listener 1883
> protocol mqtt
>
> # websockets
> listener 9001
> protocol websockets
>
> Still not connecting. I wonder if thats do to the reverse proxy 
> with apache ?
>
>
> On Thursday, December 27, 2018 at 5:31:22 AM UTC-8, Pat wrote:
>>
>> This is because your MQTT is isolated to localhost only. Local host 
>> in this case would be your weewx server, which you must have installed 
>> MQTT 
>> on as well. Which works for weewx ==> MQTT since they are on the same 
>> system, but nothing else
>>
>> First, change your MQTT to listen on 1883 for external connections. 
>> Since you're not using SSL, you can remove the 8883, update your 
>> myconfig.conf with this. 
>>
>> listener 1883
>> protocol mqtt
>>
>> With this change it'll open port 1883 to external connections like 
>> your laptop. 
>>
>> You can leave your weewx.conf [[MQTT]] config alone since they are 
>> on the same machine, localhost will work here like it already is. 
>>
>> I don't see your skin options so I think you haven't done that. 
>> You're posting to MQTT

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

# netstat -tulpn | grep mosquitto
tcp0  0 0.0.0.0:90010.0.0.0:*   LISTEN 
 15091/mosquitto 
tcp0  0 0.0.0.0:18830.0.0.0:*   LISTEN 
 15091/mosquitto 
tcp6   0  0 :::1883 :::*LISTEN 
 15091/mosquitto 


On Thursday, December 27, 2018 at 4:36:18 PM UTC-8, 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 
>> .
>>  
>> At a minimum you need mqtt_enabled, which you have, but also mqtt_host and 
>> mqtt_topic.
>>
>> As mentioned previously, weewx is posting to your MQTT broker using 
>> [[MQTT]], the skin also needs to know where the broker is so it can get 
>> that data too and that's done in [[Belchertown]] [[[Extras]]]. 
>>
>> On Thursday, December 27, 2018 at 7:21:33 PM UTC-5, Scott Grayban wrote:
>>>
>>> [[Belchertown]]
>>> HTML_ROOT = /home/weewx/public_html/Nettleton
>>> skin = Nettleton
>>> [[[Extras]]]
>>> belchertown_root_url = http://
>>> www.nettletondistrict.com/Nettleton
>>> logo_image = http://
>>> www.nettletondistrict.com/Nettleton/images/map_of_spokane_wa.jpg
>>> site_title = Nettleton District Weather Station
>>> footer_copyright_text = "Nettleton District Weather 
>>> Station, Spokane, Washington"
>>> radar_html = ""
>>> mqtt_enabled = 1
>>> show_apptemp = 1
>>> show_windrun = 1
>>> highcharts_show_apptemp = 1
>>> forecast_enabled = 1
>>> darksky_secret_key = XX
>>> earthquake_enabled = 1
>>> facebook_enabled = 1
>>> twitter_enabled = 1
>>> graphs_page_header = "Weather Observation Graphs"
>>> records_page_header = "Weather Observation Records"
>>> reports_page_header = "Weather Observation Reports"
>>> about_page_header = "About This Weather Station"
>>>
>>>
>>>
>>>
>>> On Thursday, December 27, 2018 at 4:15:22 PM UTC-8, Pat wrote:

 Please post your Belchertown skin settings.

 On Thursday, December 27, 2018 at 7:00:21 PM UTC-5, Scott Grayban wrote:
>
> Ok so my weewx.conf looks like this now
> [[MQTT]]
> server_url = mqtt://weewx:passwordX@192.168.0.4:1883/
> topic = weather/#
> unit_system = US
> binding = archive, loop
> aggregation = aggregate
>
>
>
> My /etc/mosquitto/conf.d/myconfig.conf looks like this
> persistence false
> allow_anonymous true
> password_file /etc/mosquitto/passwd
> acl_file /etc/mosquitto/acl
>
> listener 1883
> protocol mqtt
>
> # websockets
> listener 9001
> protocol websockets
>
> Still not connecting. I wonder if thats do to the reverse proxy 
> with apache ?
>
>
> On Thursday, December 27, 2018 at 5:31:22 AM UTC-8, Pat wrote:
>>
>> This is because your MQTT is isolated to localhost only. Local host 
>> in this case would be your weewx server, which you must have installed 
>> MQTT 
>> on as well. Which works for weewx ==> MQTT since they are on the same 
>> system, but nothing else
>>
>> First, change your MQTT to listen on 1883 for external connections. 
>> Since you're not using SSL, you can remove the 8883, update your 
>> myconfig.conf with this. 
>>
>> listener 1883
>> protocol mqtt
>>
>> With this change it'll open port 1883 to external connections like 
>> your laptop. 
>>
>> You can leave your weewx.conf [[MQTT]] config alone since they are 
>> on the same machine, localhost will work here like it already is. 
>>
>> I don't see your skin options so I think you haven't done that. 
>> You're posting to MQTT with [[MQTT]], but now you need to retrieve - 
>> that's 
>> what the skin does. 
>>
>> In weewx.conf you need to specify the Belchertown skin options for 
>> MQTT such as enabling it, hostname, topic, etc. 
>> 
>>  You 
>> cannot use localhost here for mqtt_host, you need to specify the IP 
>> of the server hosting your MQTT. By saying 127.0.0.1 or localhost that 
>> means Chrome is g

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

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 
> .
>  
> At a minimum you need mqtt_enabled, which you have, but also mqtt_host and 
> mqtt_topic.
>
> As mentioned previously, weewx is posting to your MQTT broker using 
> [[MQTT]], the skin also needs to know where the broker is so it can get 
> that data too and that's done in [[Belchertown]] [[[Extras]]]. 
>
> On Thursday, December 27, 2018 at 7:21:33 PM UTC-5, Scott Grayban wrote:
>>
>> [[Belchertown]]
>> HTML_ROOT = /home/weewx/public_html/Nettleton
>> skin = Nettleton
>> [[[Extras]]]
>> belchertown_root_url = http://
>> www.nettletondistrict.com/Nettleton
>> logo_image = http://
>> www.nettletondistrict.com/Nettleton/images/map_of_spokane_wa.jpg
>> site_title = Nettleton District Weather Station
>> footer_copyright_text = "Nettleton District Weather Station, 
>> Spokane, Washington"
>> radar_html = ""
>> mqtt_enabled = 1
>> show_apptemp = 1
>> show_windrun = 1
>> highcharts_show_apptemp = 1
>> forecast_enabled = 1
>> darksky_secret_key = XX
>> earthquake_enabled = 1
>> facebook_enabled = 1
>> twitter_enabled = 1
>> graphs_page_header = "Weather Observation Graphs"
>> records_page_header = "Weather Observation Records"
>> reports_page_header = "Weather Observation Reports"
>> about_page_header = "About This Weather Station"
>>
>>
>>
>>
>> On Thursday, December 27, 2018 at 4:15:22 PM UTC-8, Pat wrote:
>>>
>>> Please post your Belchertown skin settings.
>>>
>>> On Thursday, December 27, 2018 at 7:00:21 PM UTC-5, Scott Grayban wrote:

 Ok so my weewx.conf looks like this now
 [[MQTT]]
 server_url = mqtt://weewx:passwordX@192.168.0.4:1883/
 topic = weather/#
 unit_system = US
 binding = archive, loop
 aggregation = aggregate



 My /etc/mosquitto/conf.d/myconfig.conf looks like this
 persistence false
 allow_anonymous true
 password_file /etc/mosquitto/passwd
 acl_file /etc/mosquitto/acl

 listener 1883
 protocol mqtt

 # websockets
 listener 9001
 protocol websockets

 Still not connecting. I wonder if thats do to the reverse proxy 
 with apache ?


 On Thursday, December 27, 2018 at 5:31:22 AM UTC-8, Pat wrote:
>
> This is because your MQTT is isolated to localhost only. Local host in 
> this case would be your weewx server, which you must have installed MQTT 
> on 
> as well. Which works for weewx ==> MQTT since they are on the same 
> system, 
> but nothing else
>
> First, change your MQTT to listen on 1883 for external connections. 
> Since you're not using SSL, you can remove the 8883, update your 
> myconfig.conf with this. 
>
> listener 1883
> protocol mqtt
>
> With this change it'll open port 1883 to external connections like 
> your laptop. 
>
> You can leave your weewx.conf [[MQTT]] config alone since they are on 
> the same machine, localhost will work here like it already is. 
>
> I don't see your skin options so I think you haven't done that. You're 
> posting to MQTT with [[MQTT]], but now you need to retrieve - that's what 
> the skin does. 
>
> In weewx.conf you need to specify the Belchertown skin options for 
> MQTT such as enabling it, hostname, topic, etc. 
> 
>  You 
> cannot use localhost here for mqtt_host, you need to specify the IP 
> of the server hosting your MQTT. By saying 127.0.0.1 or localhost that 
> means Chrome is going to try to connect to YOUR PC for MQTT data which 
> probably doesn't exist. You need to specify the IP of the MQTT broker, 
> like 
> 192.168.1.100 or whatever. This is where having a static IP or a DHCP 
> reservation is important so the IP of your internal broker doesn't change.
>
>
> On Thursday, December 27, 2018 at 2:38:06 AM UTC-5, Scott Grayban 
> wrote:
>>
>> Pat
>>
>> I seem to have missed something in setting up MQTT for the skin... I 
>> followed https://obrienlabs.net/how-to-setup-

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

Under [[[Extras]]] you don't have any of the skin specific MQTT settings 
.
 
At a minimum you need mqtt_enabled, which you have, but also mqtt_host and 
mqtt_topic.

As mentioned previously, weewx is posting to your MQTT broker using 
[[MQTT]], the skin also needs to know where the broker is so it can get 
that data too and that's done in [[Belchertown]] [[[Extras]]]. 

On Thursday, December 27, 2018 at 7:21:33 PM UTC-5, Scott Grayban wrote:
>
> [[Belchertown]]
> HTML_ROOT = /home/weewx/public_html/Nettleton
> skin = Nettleton
> [[[Extras]]]
> belchertown_root_url = http://
> www.nettletondistrict.com/Nettleton
> logo_image = http://
> www.nettletondistrict.com/Nettleton/images/map_of_spokane_wa.jpg
> site_title = Nettleton District Weather Station
> footer_copyright_text = "Nettleton District Weather Station, 
> Spokane, Washington"
> radar_html = ""
> mqtt_enabled = 1
> show_apptemp = 1
> show_windrun = 1
> highcharts_show_apptemp = 1
> forecast_enabled = 1
> darksky_secret_key = XX
> earthquake_enabled = 1
> facebook_enabled = 1
> twitter_enabled = 1
> graphs_page_header = "Weather Observation Graphs"
> records_page_header = "Weather Observation Records"
> reports_page_header = "Weather Observation Reports"
> about_page_header = "About This Weather Station"
>
>
>
>
> On Thursday, December 27, 2018 at 4:15:22 PM UTC-8, Pat wrote:
>>
>> Please post your Belchertown skin settings.
>>
>> On Thursday, December 27, 2018 at 7:00:21 PM UTC-5, Scott Grayban wrote:
>>>
>>> Ok so my weewx.conf looks like this now
>>> [[MQTT]]
>>> server_url = mqtt://weewx:passwordX@192.168.0.4:1883/
>>> topic = weather/#
>>> unit_system = US
>>> binding = archive, loop
>>> aggregation = aggregate
>>>
>>>
>>>
>>> My /etc/mosquitto/conf.d/myconfig.conf looks like this
>>> persistence false
>>> allow_anonymous true
>>> password_file /etc/mosquitto/passwd
>>> acl_file /etc/mosquitto/acl
>>>
>>> listener 1883
>>> protocol mqtt
>>>
>>> # websockets
>>> listener 9001
>>> protocol websockets
>>>
>>> Still not connecting. I wonder if thats do to the reverse proxy with 
>>> apache ?
>>>
>>>
>>> On Thursday, December 27, 2018 at 5:31:22 AM UTC-8, Pat wrote:

 This is because your MQTT is isolated to localhost only. Local host in 
 this case would be your weewx server, which you must have installed MQTT 
 on 
 as well. Which works for weewx ==> MQTT since they are on the same system, 
 but nothing else

 First, change your MQTT to listen on 1883 for external connections. 
 Since you're not using SSL, you can remove the 8883, update your 
 myconfig.conf with this. 

 listener 1883
 protocol mqtt

 With this change it'll open port 1883 to external connections like your 
 laptop. 

 You can leave your weewx.conf [[MQTT]] config alone since they are on 
 the same machine, localhost will work here like it already is. 

 I don't see your skin options so I think you haven't done that. You're 
 posting to MQTT with [[MQTT]], but now you need to retrieve - that's what 
 the skin does. 

 In weewx.conf you need to specify the Belchertown skin options for 
 MQTT such as enabling it, hostname, topic, etc. 
 
  You 
 cannot use localhost here for mqtt_host, you need to specify the IP of 
 the server hosting your MQTT. By saying 127.0.0.1 or localhost that means 
 Chrome is going to try to connect to YOUR PC for MQTT data which probably 
 doesn't exist. You need to specify the IP of the MQTT broker, like 
 192.168.1.100 or whatever. This is where having a static IP or a DHCP 
 reservation is important so the IP of your internal broker doesn't change.


 On Thursday, December 27, 2018 at 2:38:06 AM UTC-5, Scott Grayban wrote:
>
> Pat
>
> I seem to have missed something in setting up MQTT for the skin... I 
> followed https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/ 
> except the SLL stuff since I wouldn't need it.
>
> weewx.conf
>
>
> [[MQTT]]
> server_url = mqtt://weewx:xx@127.0.0.1:1883/
> topic = weather/#
> unit_system = US
> binding = archive, loop
> aggregation = aggregate
>
> and
>
> # cat /etc/mosquitto/conf.d/myconfig.conf
> persistence false
>  
> allow_anonymous true
> password_file /etc/mosquitto/passwd
>  
> acl_file /etc/mosquitto/acl
>
>
> listener 1883 localhost
>>

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

[[Belchertown]]
HTML_ROOT = /home/weewx/public_html/Nettleton
skin = Nettleton
[[[Extras]]]
belchertown_root_url = http:
//www.nettletondistrict.com/Nettleton
logo_image = http:
//www.nettletondistrict.com/Nettleton/images/map_of_spokane_wa.jpg
site_title = Nettleton District Weather Station
footer_copyright_text = "Nettleton District Weather Station, 
Spokane, Washington"
radar_html = ""
mqtt_enabled = 1
show_apptemp = 1
show_windrun = 1
highcharts_show_apptemp = 1
forecast_enabled = 1
darksky_secret_key = XX
earthquake_enabled = 1
facebook_enabled = 1
twitter_enabled = 1
graphs_page_header = "Weather Observation Graphs"
records_page_header = "Weather Observation Records"
reports_page_header = "Weather Observation Reports"
about_page_header = "About This Weather Station"




On Thursday, December 27, 2018 at 4:15:22 PM UTC-8, Pat wrote:
>
> Please post your Belchertown skin settings.
>
> On Thursday, December 27, 2018 at 7:00:21 PM UTC-5, Scott Grayban wrote:
>>
>> Ok so my weewx.conf looks like this now
>> [[MQTT]]
>> server_url = mqtt://weewx:passwordX@192.168.0.4:1883/
>> topic = weather/#
>> unit_system = US
>> binding = archive, loop
>> aggregation = aggregate
>>
>>
>>
>> My /etc/mosquitto/conf.d/myconfig.conf looks like this
>> persistence false
>> allow_anonymous true
>> password_file /etc/mosquitto/passwd
>> acl_file /etc/mosquitto/acl
>>
>> listener 1883
>> protocol mqtt
>>
>> # websockets
>> listener 9001
>> protocol websockets
>>
>> Still not connecting. I wonder if thats do to the reverse proxy with 
>> apache ?
>>
>>
>> On Thursday, December 27, 2018 at 5:31:22 AM UTC-8, Pat wrote:
>>>
>>> This is because your MQTT is isolated to localhost only. Local host in 
>>> this case would be your weewx server, which you must have installed MQTT on 
>>> as well. Which works for weewx ==> MQTT since they are on the same system, 
>>> but nothing else
>>>
>>> First, change your MQTT to listen on 1883 for external connections. 
>>> Since you're not using SSL, you can remove the 8883, update your 
>>> myconfig.conf with this. 
>>>
>>> listener 1883
>>> protocol mqtt
>>>
>>> With this change it'll open port 1883 to external connections like your 
>>> laptop. 
>>>
>>> You can leave your weewx.conf [[MQTT]] config alone since they are on 
>>> the same machine, localhost will work here like it already is. 
>>>
>>> I don't see your skin options so I think you haven't done that. You're 
>>> posting to MQTT with [[MQTT]], but now you need to retrieve - that's what 
>>> the skin does. 
>>>
>>> In weewx.conf you need to specify the Belchertown skin options for MQTT 
>>> such as enabling it, hostname, topic, etc. 
>>> 
>>>  You 
>>> cannot use localhost here for mqtt_host, you need to specify the IP of 
>>> the server hosting your MQTT. By saying 127.0.0.1 or localhost that means 
>>> Chrome is going to try to connect to YOUR PC for MQTT data which probably 
>>> doesn't exist. You need to specify the IP of the MQTT broker, like 
>>> 192.168.1.100 or whatever. This is where having a static IP or a DHCP 
>>> reservation is important so the IP of your internal broker doesn't change.
>>>
>>>
>>> On Thursday, December 27, 2018 at 2:38:06 AM UTC-5, Scott Grayban wrote:

 Pat

 I seem to have missed something in setting up MQTT for the skin... I 
 followed https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/ 
 except the SLL stuff since I wouldn't need it.

 weewx.conf


 [[MQTT]]
 server_url = mqtt://weewx:xx@127.0.0.1:1883/
 topic = weather/#
 unit_system = US
 binding = archive, loop
 aggregation = aggregate

 and

 # cat /etc/mosquitto/conf.d/myconfig.conf
 persistence false
  
 allow_anonymous true
 password_file /etc/mosquitto/passwd
  
 acl_file /etc/mosquitto/acl


 listener 1883 localhost
 listener 8883
 protocol mqtt
  
 # websockets
 listener 9001
 protocol websockets

 # cat /etc/mosquitto/acl
 # 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/#

 This test line works

 mosquitto_pub -h localhost -t "weather/test" -m "hello world. this is 
 to the weather topic with authentication" -u weewx -P xx

 But index page is showing *Connecting to weather station real time 
 data.*

 MQTT is posting.

 Dec 26 23:19:39 raspberrypi 

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

Please post your Belchertown skin settings.

On Thursday, December 27, 2018 at 7:00:21 PM UTC-5, Scott Grayban wrote:
>
> Ok so my weewx.conf looks like this now
> [[MQTT]]
> server_url = mqtt://weewx:passwordX@192.168.0.4:1883/
> topic = weather/#
> unit_system = US
> binding = archive, loop
> aggregation = aggregate
>
>
>
> My /etc/mosquitto/conf.d/myconfig.conf looks like this
> persistence false
> allow_anonymous true
> password_file /etc/mosquitto/passwd
> acl_file /etc/mosquitto/acl
>
> listener 1883
> protocol mqtt
>
> # websockets
> listener 9001
> protocol websockets
>
> Still not connecting. I wonder if thats do to the reverse proxy with 
> apache ?
>
>
> On Thursday, December 27, 2018 at 5:31:22 AM UTC-8, Pat wrote:
>>
>> This is because your MQTT is isolated to localhost only. Local host in 
>> this case would be your weewx server, which you must have installed MQTT on 
>> as well. Which works for weewx ==> MQTT since they are on the same system, 
>> but nothing else
>>
>> First, change your MQTT to listen on 1883 for external connections. Since 
>> you're not using SSL, you can remove the 8883, update your myconfig.conf 
>> with this. 
>>
>> listener 1883
>> protocol mqtt
>>
>> With this change it'll open port 1883 to external connections like your 
>> laptop. 
>>
>> You can leave your weewx.conf [[MQTT]] config alone since they are on 
>> the same machine, localhost will work here like it already is. 
>>
>> I don't see your skin options so I think you haven't done that. You're 
>> posting to MQTT with [[MQTT]], but now you need to retrieve - that's what 
>> the skin does. 
>>
>> In weewx.conf you need to specify the Belchertown skin options for MQTT 
>> such as enabling it, hostname, topic, etc. 
>> 
>>  You 
>> cannot use localhost here for mqtt_host, you need to specify the IP of 
>> the server hosting your MQTT. By saying 127.0.0.1 or localhost that means 
>> Chrome is going to try to connect to YOUR PC for MQTT data which probably 
>> doesn't exist. You need to specify the IP of the MQTT broker, like 
>> 192.168.1.100 or whatever. This is where having a static IP or a DHCP 
>> reservation is important so the IP of your internal broker doesn't change.
>>
>>
>> On Thursday, December 27, 2018 at 2:38:06 AM UTC-5, Scott Grayban wrote:
>>>
>>> Pat
>>>
>>> I seem to have missed something in setting up MQTT for the skin... I 
>>> followed https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/ 
>>> except the SLL stuff since I wouldn't need it.
>>>
>>> weewx.conf
>>>
>>>
>>> [[MQTT]]
>>> server_url = mqtt://weewx:xx@127.0.0.1:1883/
>>> topic = weather/#
>>> unit_system = US
>>> binding = archive, loop
>>> aggregation = aggregate
>>>
>>> and
>>>
>>> # cat /etc/mosquitto/conf.d/myconfig.conf
>>> persistence false
>>>  
>>> allow_anonymous true
>>> password_file /etc/mosquitto/passwd
>>>  
>>> acl_file /etc/mosquitto/acl
>>>
>>>
>>> listener 1883 localhost
>>> listener 8883
>>> protocol mqtt
>>>  
>>> # websockets
>>> listener 9001
>>> protocol websockets
>>>
>>> # cat /etc/mosquitto/acl
>>> # 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/#
>>>
>>> This test line works
>>>
>>> mosquitto_pub -h localhost -t "weather/test" -m "hello world. this is 
>>> to the weather topic with authentication" -u weewx -P xx
>>>
>>> But index page is showing *Connecting to weather station real time 
>>> data.*
>>>
>>> MQTT is posting.
>>>
>>> Dec 26 23:19:39 raspberrypi weewx[6544]: restx: MQTT: Published record 
>>> 2018-12-26 23:19:39 PST (1545895179)
>>> Dec 26 23:19:45 raspberrypi weewx[6544]: restx: MQTT: Published record 
>>> 2018-12-26 23:19:45 PST (1545895185)
>>>
>>> So I don't know what I did worng. I restraced all steps and I did it 
>>> correctly.
>>>
>>> On Friday, December 7, 2018 at 2:12:23 PM UTC-8, Pat wrote:

 The last thread was getting a bit long. So I've started a new one. 

 Belchertown Skin 0.8.1 has been released which fixes a couple of bugs. 
 See the release notes, and install instructions here:

 https://github.com/poblabs/weewx-belchertown/releases




-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[rich T]

Try 

server_url = http://weewx:password@192.168.0.4:1883/


Rich

On Thursday, December 27, 2018 at 7:00:21 PM UTC-5, Scott Grayban wrote:
>
> Ok so my weewx.conf looks like this now
> [[MQTT]]
> server_url = mqtt://weewx:passwordX@192.168.0.4:1883/
> topic = weather/#
> unit_system = US
> binding = archive, loop
> aggregation = aggregate
>
>
>
> My /etc/mosquitto/conf.d/myconfig.conf looks like this
> persistence false
> allow_anonymous true
> password_file /etc/mosquitto/passwd
> acl_file /etc/mosquitto/acl
>
> listener 1883
> protocol mqtt
>
> # websockets
> listener 9001
> protocol websockets
>
> Still not connecting. I wonder if thats do to the reverse proxy with 
> apache ?
>
>
> On Thursday, December 27, 2018 at 5:31:22 AM UTC-8, Pat wrote:
>>
>> This is because your MQTT is isolated to localhost only. Local host in 
>> this case would be your weewx server, which you must have installed MQTT on 
>> as well. Which works for weewx ==> MQTT since they are on the same system, 
>> but nothing else
>>
>> First, change your MQTT to listen on 1883 for external connections. Since 
>> you're not using SSL, you can remove the 8883, update your myconfig.conf 
>> with this. 
>>
>> listener 1883
>> protocol mqtt
>>
>> With this change it'll open port 1883 to external connections like your 
>> laptop. 
>>
>> You can leave your weewx.conf [[MQTT]] config alone since they are on 
>> the same machine, localhost will work here like it already is. 
>>
>> I don't see your skin options so I think you haven't done that. You're 
>> posting to MQTT with [[MQTT]], but now you need to retrieve - that's what 
>> the skin does. 
>>
>> In weewx.conf you need to specify the Belchertown skin options for MQTT 
>> such as enabling it, hostname, topic, etc. 
>> 
>>  You 
>> cannot use localhost here for mqtt_host, you need to specify the IP of 
>> the server hosting your MQTT. By saying 127.0.0.1 or localhost that means 
>> Chrome is going to try to connect to YOUR PC for MQTT data which probably 
>> doesn't exist. You need to specify the IP of the MQTT broker, like 
>> 192.168.1.100 or whatever. This is where having a static IP or a DHCP 
>> reservation is important so the IP of your internal broker doesn't change.
>>
>>
>> On Thursday, December 27, 2018 at 2:38:06 AM UTC-5, Scott Grayban wrote:
>>>
>>> Pat
>>>
>>> I seem to have missed something in setting up MQTT for the skin... I 
>>> followed https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/ 
>>> except the SLL stuff since I wouldn't need it.
>>>
>>> weewx.conf
>>>
>>>
>>> [[MQTT]]
>>> server_url = mqtt://weewx:xx@127.0.0.1:1883/
>>> topic = weather/#
>>> unit_system = US
>>> binding = archive, loop
>>> aggregation = aggregate
>>>
>>> and
>>>
>>> # cat /etc/mosquitto/conf.d/myconfig.conf
>>> persistence false
>>>  
>>> allow_anonymous true
>>> password_file /etc/mosquitto/passwd
>>>  
>>> acl_file /etc/mosquitto/acl
>>>
>>>
>>> listener 1883 localhost
>>> listener 8883
>>> protocol mqtt
>>>  
>>> # websockets
>>> listener 9001
>>> protocol websockets
>>>
>>> # cat /etc/mosquitto/acl
>>> # 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/#
>>>
>>> This test line works
>>>
>>> mosquitto_pub -h localhost -t "weather/test" -m "hello world. this is 
>>> to the weather topic with authentication" -u weewx -P xx
>>>
>>> But index page is showing *Connecting to weather station real time 
>>> data.*
>>>
>>> MQTT is posting.
>>>
>>> Dec 26 23:19:39 raspberrypi weewx[6544]: restx: MQTT: Published record 
>>> 2018-12-26 23:19:39 PST (1545895179)
>>> Dec 26 23:19:45 raspberrypi weewx[6544]: restx: MQTT: Published record 
>>> 2018-12-26 23:19:45 PST (1545895185)
>>>
>>> So I don't know what I did worng. I restraced all steps and I did it 
>>> correctly.
>>>
>>> On Friday, December 7, 2018 at 2:12:23 PM UTC-8, Pat wrote:

 The last thread was getting a bit long. So I've started a new one. 

 Belchertown Skin 0.8.1 has been released which fixes a couple of bugs. 
 See the release notes, and install instructions here:

 https://github.com/poblabs/weewx-belchertown/releases




-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

Ok so my weewx.conf looks like this now
[[MQTT]]
server_url = mqtt://weewx:passwordX@192.168.0.4:1883/
topic = weather/#
unit_system = US
binding = archive, loop
aggregation = aggregate



My /etc/mosquitto/conf.d/myconfig.conf looks like this
persistence false
allow_anonymous true
password_file /etc/mosquitto/passwd
acl_file /etc/mosquitto/acl

listener 1883
protocol mqtt

# websockets
listener 9001
protocol websockets

Still not connecting. I wonder if thats do to the reverse proxy with 
apache ?


On Thursday, December 27, 2018 at 5:31:22 AM UTC-8, Pat wrote:
>
> This is because your MQTT is isolated to localhost only. Local host in 
> this case would be your weewx server, which you must have installed MQTT on 
> as well. Which works for weewx ==> MQTT since they are on the same system, 
> but nothing else
>
> First, change your MQTT to listen on 1883 for external connections. Since 
> you're not using SSL, you can remove the 8883, update your myconfig.conf 
> with this. 
>
> listener 1883
> protocol mqtt
>
> With this change it'll open port 1883 to external connections like your 
> laptop. 
>
> You can leave your weewx.conf [[MQTT]] config alone since they are on the 
> same machine, localhost will work here like it already is. 
>
> I don't see your skin options so I think you haven't done that. You're 
> posting to MQTT with [[MQTT]], but now you need to retrieve - that's what 
> the skin does. 
>
> In weewx.conf you need to specify the Belchertown skin options for MQTT 
> such as enabling it, hostname, topic, etc. 
> 
>  You 
> cannot use localhost here for mqtt_host, you need to specify the IP of 
> the server hosting your MQTT. By saying 127.0.0.1 or localhost that means 
> Chrome is going to try to connect to YOUR PC for MQTT data which probably 
> doesn't exist. You need to specify the IP of the MQTT broker, like 
> 192.168.1.100 or whatever. This is where having a static IP or a DHCP 
> reservation is important so the IP of your internal broker doesn't change.
>
>
> On Thursday, December 27, 2018 at 2:38:06 AM UTC-5, Scott Grayban wrote:
>>
>> Pat
>>
>> I seem to have missed something in setting up MQTT for the skin... I 
>> followed https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/ 
>> except the SLL stuff since I wouldn't need it.
>>
>> weewx.conf
>>
>>
>> [[MQTT]]
>> server_url = mqtt://weewx:xx@127.0.0.1:1883/
>> topic = weather/#
>> unit_system = US
>> binding = archive, loop
>> aggregation = aggregate
>>
>> and
>>
>> # cat /etc/mosquitto/conf.d/myconfig.conf
>> persistence false
>>  
>> allow_anonymous true
>> password_file /etc/mosquitto/passwd
>>  
>> acl_file /etc/mosquitto/acl
>>
>>
>> listener 1883 localhost
>> listener 8883
>> protocol mqtt
>>  
>> # websockets
>> listener 9001
>> protocol websockets
>>
>> # cat /etc/mosquitto/acl
>> # 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/#
>>
>> This test line works
>>
>> mosquitto_pub -h localhost -t "weather/test" -m "hello world. this is to 
>> the weather topic with authentication" -u weewx -P xx
>>
>> But index page is showing *Connecting to weather station real time data.*
>>
>> MQTT is posting.
>>
>> Dec 26 23:19:39 raspberrypi weewx[6544]: restx: MQTT: Published record 
>> 2018-12-26 23:19:39 PST (1545895179)
>> Dec 26 23:19:45 raspberrypi weewx[6544]: restx: MQTT: Published record 
>> 2018-12-26 23:19:45 PST (1545895185)
>>
>> So I don't know what I did worng. I restraced all steps and I did it 
>> correctly.
>>
>> On Friday, December 7, 2018 at 2:12:23 PM UTC-8, Pat wrote:
>>>
>>> The last thread was getting a bit long. So I've started a new one. 
>>>
>>> Belchertown Skin 0.8.1 has been released which fixes a couple of bugs. 
>>> See the release notes, and install instructions here:
>>>
>>> https://github.com/poblabs/weewx-belchertown/releases
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

This is because your MQTT is isolated to localhost only. Local host in this 
case would be your weewx server, which you must have installed MQTT on as 
well. Which works for weewx ==> MQTT since they are on the same system, but 
nothing else

First, change your MQTT to listen on 1883 for external connections. Since 
you're not using SSL, you can remove the 8883, update your myconfig.conf 
with this. 

listener 1883
protocol mqtt

With this change it'll open port 1883 to external connections like your 
laptop. 

You can leave your weewx.conf [[MQTT]] config alone since they are on the 
same machine, localhost will work here like it already is. 

I don't see your skin options so I think you haven't done that. You're 
posting to MQTT with [[MQTT]], but now you need to retrieve - that's what 
the skin does. 

In weewx.conf you need to specify the Belchertown skin options for MQTT 
such as enabling it, hostname, topic, etc. 

 You 
cannot use localhost here for mqtt_host, you need to specify the IP of the 
server hosting your MQTT. By saying 127.0.0.1 or localhost that means 
Chrome is going to try to connect to YOUR PC for MQTT data which probably 
doesn't exist. You need to specify the IP of the MQTT broker, like 
192.168.1.100 or whatever. This is where having a static IP or a DHCP 
reservation is important so the IP of your internal broker doesn't change.


On Thursday, December 27, 2018 at 2:38:06 AM UTC-5, Scott Grayban wrote:
>
> Pat
>
> I seem to have missed something in setting up MQTT for the skin... I 
> followed https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/ except 
> the SLL stuff since I wouldn't need it.
>
> weewx.conf
>
>
> [[MQTT]]
> server_url = mqtt://weewx:xx@127.0.0.1:1883/
> topic = weather/#
> unit_system = US
> binding = archive, loop
> aggregation = aggregate
>
> and
>
> # cat /etc/mosquitto/conf.d/myconfig.conf
> persistence false
>  
> allow_anonymous true
> password_file /etc/mosquitto/passwd
>  
> acl_file /etc/mosquitto/acl
>
>
> listener 1883 localhost
> listener 8883
> protocol mqtt
>  
> # websockets
> listener 9001
> protocol websockets
>
> # cat /etc/mosquitto/acl
> # 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/#
>
> This test line works
>
> mosquitto_pub -h localhost -t "weather/test" -m "hello world. this is to 
> the weather topic with authentication" -u weewx -P xx
>
> But index page is showing *Connecting to weather station real time data.*
>
> MQTT is posting.
>
> Dec 26 23:19:39 raspberrypi weewx[6544]: restx: MQTT: Published record 
> 2018-12-26 23:19:39 PST (1545895179)
> Dec 26 23:19:45 raspberrypi weewx[6544]: restx: MQTT: Published record 
> 2018-12-26 23:19:45 PST (1545895185)
>
> So I don't know what I did worng. I restraced all steps and I did it 
> correctly.
>
> On Friday, December 7, 2018 at 2:12:23 PM UTC-8, Pat wrote:
>>
>> The last thread was getting a bit long. So I've started a new one. 
>>
>> Belchertown Skin 0.8.1 has been released which fixes a couple of bugs. 
>> See the release notes, and install instructions here:
>>
>> https://github.com/poblabs/weewx-belchertown/releases
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

Pat

I seem to have missed something in setting up MQTT for the skin... I 
followed https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/ except 
the SLL stuff since I wouldn't need it.

weewx.conf


[[MQTT]]
server_url = mqtt://weewx:xx@127.0.0.1:1883/
topic = weather/#
unit_system = US
binding = archive, loop
aggregation = aggregate

and

# cat /etc/mosquitto/conf.d/myconfig.conf
persistence false
 
allow_anonymous true
password_file /etc/mosquitto/passwd
 
acl_file /etc/mosquitto/acl


listener 1883 localhost
listener 8883
protocol mqtt
 
# websockets
listener 9001
protocol websockets

# cat /etc/mosquitto/acl
# 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/#

This test line works

mosquitto_pub -h localhost -t "weather/test" -m "hello world. this is to 
the weather topic with authentication" -u weewx -P xx

But index page is showing *Connecting to weather station real time data.*

MQTT is posting.

Dec 26 23:19:39 raspberrypi weewx[6544]: restx: MQTT: Published record 2018-
12-26 23:19:39 PST (1545895179)
Dec 26 23:19:45 raspberrypi weewx[6544]: restx: MQTT: Published record 2018-
12-26 23:19:45 PST (1545895185)

So I don't know what I did worng. I restraced all steps and I did it 
correctly.

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

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

# sqlite3 weewx.sdb_new
SQLite version 3.16.2 2017-01-06 16:32:41
Enter ".help" for usage hints.
sqlite> .schema archive
CREATE TABLE archive (`dateTime` INTEGER NOT NULL UNIQUE PRIMARY KEY, 
`usUnits` INTEGER NOT NULL, `interval` INTEGER NOT NULL, `barometer` REAL, 
`pressure` REAL, `altimeter` REAL, `inTemp` REAL, `outTemp` REAL, 
`inHumidity` REAL, `outHumidity` REAL, `windSpeed` REAL, `windDir` REAL, 
`windGust` REAL, `windGustDir` REAL, `rainRate` REAL, `rain` REAL, 
`dewpoint` REAL, `windchill` REAL, `heatindex` REAL, `ET` REAL, `radiation` 
REAL, `UV` REAL, `extraTemp1` REAL, `extraTemp2` REAL, `extraTemp3` REAL, 
`soilTemp1` REAL, `soilTemp2` REAL, `soilTemp3` REAL, `soilTemp4` REAL, 
`leafTemp1` REAL, `leafTemp2` REAL, `extraHumid1` REAL, `extraHumid2` REAL, 
`soilMoist1` REAL, `soilMoist2` REAL, `soilMoist3` REAL, `soilMoist4` REAL, 
`leafWet1` REAL, `leafWet2` REAL, `rxCheckPercent` REAL, `txBatteryStatus` 
REAL, `consBatteryVoltage` REAL, `hail` REAL, `hailRate` REAL, `heatingTemp` 
REAL, `heatingVoltage` REAL, `supplyVoltage` REAL, `referenceVoltage` REAL, 
`windBatteryStatus` REAL, `rainBatteryStatus` REAL, `outTempBatteryStatus` 
REAL, `inTempBatteryStatus` REAL, `appTemp` REAL, `windRun` REAL);
sqlite> .exit



Last line shows both in the db now...


On Wednesday, December 26, 2018 at 6:46:21 PM UTC-8, Scott Grayban wrote:
>
> AHHH I got it It didn't dawn on me that this
>
> *schema = schemas.wview.schema + [('appTemp',   'REAL'), ('windRun',   
> 'REAL')]*
>
> should be this
>
> *schema_apptemp = schemas.wview.schema + [('appTemp',   'REAL'), 
> ('windRun',   'REAL')]*
>
> S stupid me...
>
>
> On Wednesday, December 26, 2018 at 6:40:41 PM UTC-8, gjr80 wrote:
>>
>> Simple, delete the line:
>>
>> schema = user.extensions.schema_windrun
>>
>> We now put everything in schema_apptemp. Please post user/extensions.py
>>
>> Gary
>>
>>
>> On Thursday, 27 December 2018 12:32:23 UTC+10, Scott Grayban wrote:
>>>
>>> The error is in the weewx.conf
>>>
>>>
>>> [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*
>>> *schema = user.extensions.schema_windrun*
>>>
>>> This is where it's saying *Duplicate keyword name at line 403*
>>>
>>> And I can't figure out how to combine that into 1 line.
>>>
>>> I have this in */usr/share/weewx/user/extensions.py*
>>>
>>> *schema = schemas.wview.schema + [('appTemp',   'REAL'), ('windRun',   
>>> 'REAL')]*
>>>
>>>
>>> On Wednesday, December 26, 2018 at 5:19:35 PM UTC-8, gjr80 wrote:

 Hi Scott,

 On Thursday, 27 December 2018 09:19:11 UTC+10, 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 ?
>

 Do you mean adding more than one field to your schema or more than one 
 schema 
 = entry under [[wx_binding]]. I presume you mean the former, as the 
 latter is not allowed, configobj (which handles parsing of the weeWX 
 .conf files) only allows unique config option entries in a given 
 stanza. So you can't have two schema = entries under [[wx_binding]]. 
 You can certainly add more than one field at a time with a custom schema 
 defined in a file.

 So we can work what is going wrong I suggest you give us the complete 
 picture by posting:

 1. the contents of weewx.conf with any sensitive info (eg passwords, 
 user names etc) removed
 2. the contents of the file (it should be 
 /home/weewx/bin/user/extensions.py or 
 /usr/share/weewx/user/extensions.py depending on your weeWX install 
 type) containing the custom schema you are specifying at the schema = 
 entry under [[wx_binding]] in weewx.conf
 3. a screen capture showing the exact commands you issue and the exact 
 responses received

 Please don't remove anything other than sensitive info, often a user 
 may post what they think is the critical piece of info from a command or 
 config file only to find that there is some other piece of critical info 
 in 
 the command output or config file that we need to work out exactly what is 
 happening. Saves a lot of to'ing and fro'ing

 Gary

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and 

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

AHHH I got it It didn't dawn on me that this

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

should be this

*schema_apptemp = schemas.wview.schema + [('appTemp',   'REAL'), 
('windRun',   'REAL')]*

S stupid me...


On Wednesday, December 26, 2018 at 6:40:41 PM UTC-8, gjr80 wrote:
>
> Simple, delete the line:
>
> schema = user.extensions.schema_windrun
>
> We now put everything in schema_apptemp. Please post user/extensions.py
>
> Gary
>
>
> On Thursday, 27 December 2018 12:32:23 UTC+10, Scott Grayban wrote:
>>
>> The error is in the weewx.conf
>>
>>
>> [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*
>> *schema = user.extensions.schema_windrun*
>>
>> This is where it's saying *Duplicate keyword name at line 403*
>>
>> And I can't figure out how to combine that into 1 line.
>>
>> I have this in */usr/share/weewx/user/extensions.py*
>>
>> *schema = schemas.wview.schema + [('appTemp',   'REAL'), ('windRun',   
>> 'REAL')]*
>>
>>
>> On Wednesday, December 26, 2018 at 5:19:35 PM UTC-8, gjr80 wrote:
>>>
>>> Hi Scott,
>>>
>>> On Thursday, 27 December 2018 09:19:11 UTC+10, 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 ?

>>>
>>> Do you mean adding more than one field to your schema or more than one 
>>> schema 
>>> = entry under [[wx_binding]]. I presume you mean the former, as the 
>>> latter is not allowed, configobj (which handles parsing of the weeWX 
>>> .conf files) only allows unique config option entries in a given 
>>> stanza. So you can't have two schema = entries under [[wx_binding]]. 
>>> You can certainly add more than one field at a time with a custom schema 
>>> defined in a file.
>>>
>>> So we can work what is going wrong I suggest you give us the complete 
>>> picture by posting:
>>>
>>> 1. the contents of weewx.conf with any sensitive info (eg passwords, 
>>> user names etc) removed
>>> 2. the contents of the file (it should be 
>>> /home/weewx/bin/user/extensions.py or 
>>> /usr/share/weewx/user/extensions.py depending on your weeWX install 
>>> type) containing the custom schema you are specifying at the schema = 
>>> entry under [[wx_binding]] in weewx.conf
>>> 3. a screen capture showing the exact commands you issue and the exact 
>>> responses received
>>>
>>> Please don't remove anything other than sensitive info, often a user may 
>>> post what they think is the critical piece of info from a command or config 
>>> file only to find that there is some other piece of critical info in the 
>>> command output or config file that we need to work out exactly what is 
>>> happening. Saves a lot of to'ing and fro'ing
>>>
>>> Gary
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[gjr80]

Simple, delete the line:

schema = user.extensions.schema_windrun

We now put everything in schema_apptemp. Please post user/extensions.py

Gary


On Thursday, 27 December 2018 12:32:23 UTC+10, Scott Grayban wrote:
>
> The error is in the weewx.conf
>
>
> [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*
> *schema = user.extensions.schema_windrun*
>
> This is where it's saying *Duplicate keyword name at line 403*
>
> And I can't figure out how to combine that into 1 line.
>
> I have this in */usr/share/weewx/user/extensions.py*
>
> *schema = schemas.wview.schema + [('appTemp',   'REAL'), ('windRun',   
> 'REAL')]*
>
>
> On Wednesday, December 26, 2018 at 5:19:35 PM UTC-8, gjr80 wrote:
>>
>> Hi Scott,
>>
>> On Thursday, 27 December 2018 09:19:11 UTC+10, 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 ?
>>>
>>
>> Do you mean adding more than one field to your schema or more than one 
>> schema 
>> = entry under [[wx_binding]]. I presume you mean the former, as the 
>> latter is not allowed, configobj (which handles parsing of the weeWX 
>> .conf files) only allows unique config option entries in a given stanza. 
>> So you can't have two schema = entries under [[wx_binding]]. You can 
>> certainly add more than one field at a time with a custom schema defined in 
>> a file.
>>
>> So we can work what is going wrong I suggest you give us the complete 
>> picture by posting:
>>
>> 1. the contents of weewx.conf with any sensitive info (eg passwords, 
>> user names etc) removed
>> 2. the contents of the file (it should be 
>> /home/weewx/bin/user/extensions.py or /usr/share/weewx/user/extensions.py 
>> depending on your weeWX install type) containing the custom schema you are 
>> specifying at the schema = entry under [[wx_binding]] in weewx.conf
>> 3. a screen capture showing the exact commands you issue and the exact 
>> responses received
>>
>> Please don't remove anything other than sensitive info, often a user may 
>> post what they think is the critical piece of info from a command or config 
>> file only to find that there is some other piece of critical info in the 
>> command output or config file that we need to work out exactly what is 
>> happening. Saves a lot of to'ing and fro'ing
>>
>> Gary
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

On Wednesday, December 26, 2018 at 5:19:35 PM UTC-8, gjr80 wrote:
>
> Hi Scott,
>
> On Thursday, 27 December 2018 09:19:11 UTC+10, 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 ?
>>
>
> Do you mean adding more than one field to your schema or more than one schema 
> = entry under [[wx_binding]]. I presume you mean the former, as the 
> latter is not allowed, configobj (which handles parsing of the weeWX .conf 
> files) only allows unique config option entries in a given stanza. So you 
> can't have two schema = entries under [[wx_binding]]. You can certainly 
> add more than one field at a time with a custom schema defined in a file.
>
> So we can work what is going wrong I suggest you give us the complete 
> picture by posting:
>
> 1. the contents of weewx.conf with any sensitive info (eg passwords, user 
> names etc) removed
> 2. the contents of the file (it should be 
> /home/weewx/bin/user/extensions.py or /usr/share/weewx/user/extensions.py 
> depending on your weeWX install type) containing the custom schema you are 
> specifying at the schema = entry under [[wx_binding]] in weewx.conf
> 3. a screen capture showing the exact commands you issue and the exact 
> responses received
>
> Please don't remove anything other than sensitive info, often a user may 
> post what they think is the critical piece of info from a command or config 
> file only to find that there is some other piece of critical info in the 
> command output or config file that we need to work out exactly what is 
> happening. Saves a lot of to'ing and fro'ing
>
> Gary
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

The error is in the weewx.conf


[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*
*schema = user.extensions.schema_windrun*

This is where it's saying *Duplicate keyword name at line 403*

And I can't figure out how to combine that into 1 line.

I have this in */usr/share/weewx/user/extensions.py*

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


On Wednesday, December 26, 2018 at 5:19:35 PM UTC-8, gjr80 wrote:
>
> Hi Scott,
>
> On Thursday, 27 December 2018 09:19:11 UTC+10, 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 ?
>>
>
> Do you mean adding more than one field to your schema or more than one schema 
> = entry under [[wx_binding]]. I presume you mean the former, as the 
> latter is not allowed, configobj (which handles parsing of the weeWX .conf 
> files) only allows unique config option entries in a given stanza. So you 
> can't have two schema = entries under [[wx_binding]]. You can certainly 
> add more than one field at a time with a custom schema defined in a file.
>
> So we can work what is going wrong I suggest you give us the complete 
> picture by posting:
>
> 1. the contents of weewx.conf with any sensitive info (eg passwords, user 
> names etc) removed
> 2. the contents of the file (it should be 
> /home/weewx/bin/user/extensions.py or /usr/share/weewx/user/extensions.py 
> depending on your weeWX install type) containing the custom schema you are 
> specifying at the schema = entry under [[wx_binding]] in weewx.conf
> 3. a screen capture showing the exact commands you issue and the exact 
> responses received
>
> Please don't remove anything other than sensitive info, often a user may 
> post what they think is the critical piece of info from a command or config 
> file only to find that there is some other piece of critical info in the 
> command output or config file that we need to work out exactly what is 
> happening. Saves a lot of to'ing and fro'ing
>
> Gary
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[gjr80]

Hi Scott,

On Thursday, 27 December 2018 09:19:11 UTC+10, 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 ?
>

Do you mean adding more than one field to your schema or more than one schema 
= entry under [[wx_binding]]. I presume you mean the former, as the latter 
is not allowed, configobj (which handles parsing of the weeWX .conf files) 
only allows unique config option entries in a given stanza. So you can't 
have two schema = entries under [[wx_binding]]. You can certainly add more 
than one field at a time with a custom schema defined in a file.

So we can work what is going wrong I suggest you give us the complete 
picture by posting:

1. the contents of weewx.conf with any sensitive info (eg passwords, user 
names etc) removed
2. the contents of the file (it should be /home/weewx/bin/user/extensions.py 
or /usr/share/weewx/user/extensions.py depending on your weeWX install 
type) containing the custom schema you are specifying at the schema = entry 
under [[wx_binding]] in weewx.conf
3. a screen capture showing the exact commands you issue and the exact 
responses received

Please don't remove anything other than sensitive info, often a user may 
post what they think is the critical piece of info from a command or config 
file only to find that there is some other piece of critical info in the 
command output or config file that we need to work out exactly what is 
happening. Saves a lot of to'ing and fro'ing

Gary

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

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.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Andrew Milner]

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.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

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.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

When I run

wee_database weewx.conf --reconfigure

I am getting python errors

Traceback (most recent call last):
  File "/usr/bin/wee_database", line 793, in 
main()
  File "/usr/bin/wee_database", line 133, in main
config_path, config_dict = weecfg.read_config(options.config_path, args)
  File "/usr/share/weewx/weecfg/__init__.py", line 223, in read_config
config_dict = configobj.ConfigObj(config_path, file_error=True)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
__init__
self._load(infile, configspec)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
raise error
configobj.DuplicateError: Duplicate keyword name at line 401.



On Sunday, December 9, 2018 at 1:51:15 PM UTC-8, Philip Kutzenco wrote:
>
> Dj,
>
> (I deleted the first version of this post as I left out a trailing "]" in 
> step 1).
>
> This is from instructions Pat gave me in the past to extend the schema:
>
> 1) Extend the database
>
> nano /usr/share/weewx/user/extensions.py
>
> then add the following:
>
>
> *import schemas.wviewschema_apptemp = schemas.wview.schema + 
> [('appTemp',   'REAL')]*
>
>
>
> 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.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Scott Grayban]

I love the skin... tweaked it a bit for my taste, added location, server 
and weeWX stats to the about page... 
http://www.nettletondistrict.com/Nettleton/ It's being served from my local 
IP via a reverse proxy.

Next task is to get MQTT working !!

Thanks for all your work !!

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

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

Haven't seen this before, my initial guess is that this is something to do 
with Cheetah I think, and not my skin necessarily. 

Does your configuration or database have some sort of ascii character in it 
like the degrees symbol or something like that?

Seems to be something with your setup. Check your configs and database?

On Friday, December 21, 2018 at 6:53:47 PM UTC-5, da...@friscoweather.com 
wrote:
>
> Hi Pat,
>
> I've installed the latest version and have followed all of your 
> instructions, however, I keep getting the following errors when weeex tries 
> to generate the actual index.html files:
>
> Dec 21 16:40:22 debian weewx[6732]: reportengine: Running report 
> Belchertown
> Dec 21 16:40:22 debian weewx[6732]: reportengine: Found configuration file 
> /etc/weewx/skins/Belchertown/skin.conf for report Belchertown
> Dec 21 16:40:22 debian weewx[6732]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
> 'user.belchertown.getData']
> Dec 21 16:40:22 debian weewx[6732]: manager: Daily summary version is 2.0
> Dec 21 16:40:22 debian weewx[6732]: Belchertown Extension: version 0.8
> Dec 21 16:40:26 debian weewx[6732]: cheetahgenerator: Generate failed with 
> exception ''
> Dec 21 16:40:26 debian weewx[6732]: cheetahgenerator:  Ignoring 
> template /etc/weewx/skins/Belchertown/about/index.html.tmpl
> Dec 21 16:40:26 debian weewx[6732]: cheetahgenerator:  Reason: 'ascii' 
> codec can't decode byte 0xef in position 0: ordinal not in range(128)
> Dec 21 16:40:26 debian weewx[6732]:   Traceback (most recent call 
> last):
> Dec 21 16:40:26 debian weewx[6732]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 328, in generate
> Dec 21 16:40:26 debian weewx[6732]:   
> filtersLib=weewx.cheetahgenerator)
> Dec 21 16:40:26 debian weewx[6732]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1259, in 
> __init__
> Dec 21 16:40:26 debian weewx[6732]:   self._compile(source, file, 
> compilerSettings=compilerSettings)
> Dec 21 16:40:26 debian weewx[6732]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1553, in 
> _compile
> Dec 21 16:40:26 debian weewx[6732]:   keepRefToGeneratedCode=True)
> Dec 21 16:40:26 debian weewx[6732]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 740, in compile
> Dec 21 16:40:26 debian weewx[6732]:   settings=(compilerSettings 
> or {}))
> Dec 21 16:40:26 debian weewx[6732]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Compiler.py", line 1579, in 
> __init__
> Dec 21 16:40:26 debian weewx[6732]:   source = unicode(source)
> Dec 21 16:40:26 debian weewx[6732]:   UnicodeDecodeError: 'ascii' 
> codec can't decode byte 0xef in position 0: ordinal not in range(128)
> Dec 21 16:40:27 debian weewx[6732]: cheetahgenerator: Generate failed with 
> exception ''
> Dec 21 16:40:27 debian weewx[6732]: cheetahgenerator:  Ignoring 
> template /etc/weewx/skins/Belchertown/index.html.tmpl
> Dec 21 16:40:27 debian weewx[6732]: cheetahgenerator:  Reason: 'ascii' 
> codec can't decode byte 0xef in position 0: ordinal not in range(128)
> Dec 21 16:40:27 debian weewx[6732]:   Traceback (most recent call 
> last):
> Dec 21 16:40:27 debian weewx[6732]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 328, in generate
> Dec 21 16:40:27 debian weewx[6732]:   
> filtersLib=weewx.cheetahgenerator)
> Dec 21 16:40:27 debian weewx[6732]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1259, in 
> __init__
> Dec 21 16:40:27 debian weewx[6732]:   self._compile(source, file, 
> compilerSettings=compilerSettings)
> Dec 21 16:40:27 debian weewx[6732]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1553, in 
> _compile
> Dec 21 16:40:27 debian weewx[6732]:   keepRefToGeneratedCode=True)
> Dec 21 16:40:27 debian weewx[6732]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 740, in compile
> Dec 21 16:40:27 debian weewx[6732]:   settings=(compilerSettings 
> or {}))
> Dec 21 16:40:27 debian weewx[6732]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Compiler.py", line 1579, in 
> __init__
> Dec 21 16:40:27 debian weewx[6732]:   source = unicode(source)
> Dec 21 16:40:27 debian weewx[6732]:   UnicodeDecodeError: 'ascii' 
> codec can't decode byte 0xef in position 0: ordinal not in range(128)
> Dec 21 16:40:27 debian weewx[6732]: cheetahgenerator: Generate failed with 
> exception ''
> Dec 21 16:40:27 debian weewx[6732]: cheetahgenerator:  Ignoring 
> template /etc/weewx/skins/Belchertown/pi/index.html.tmpl
> Dec 21 16:40:27 debian weewx[6732]: cheetahgenerator:  Reason: 'ascii' 

[weewx-user] Re: Belchertown Skin 0.8.1 released

[dave]

Hi Pat,

I've installed the latest version and have followed all of your 
instructions, however, I keep getting the following errors when weeex tries 
to generate the actual index.html files:

Dec 21 16:40:22 debian weewx[6732]: reportengine: Running report Belchertown
Dec 21 16:40:22 debian weewx[6732]: reportengine: Found configuration file 
/etc/weewx/skins/Belchertown/skin.conf for report Belchertown
Dec 21 16:40:22 debian weewx[6732]: cheetahgenerator: using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'user.belchertown.getData']
Dec 21 16:40:22 debian weewx[6732]: manager: Daily summary version is 2.0
Dec 21 16:40:22 debian weewx[6732]: Belchertown Extension: version 0.8
Dec 21 16:40:26 debian weewx[6732]: cheetahgenerator: Generate failed with 
exception ''
Dec 21 16:40:26 debian weewx[6732]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Belchertown/about/index.html.tmpl
Dec 21 16:40:26 debian weewx[6732]: cheetahgenerator:  Reason: 'ascii' 
codec can't decode byte 0xef in position 0: ordinal not in range(128)
Dec 21 16:40:26 debian weewx[6732]:   Traceback (most recent call last):
Dec 21 16:40:26 debian weewx[6732]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 328, in generate
Dec 21 16:40:26 debian weewx[6732]:   
filtersLib=weewx.cheetahgenerator)
Dec 21 16:40:26 debian weewx[6732]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1259, in 
__init__
Dec 21 16:40:26 debian weewx[6732]:   self._compile(source, file, 
compilerSettings=compilerSettings)
Dec 21 16:40:26 debian weewx[6732]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1553, in 
_compile
Dec 21 16:40:26 debian weewx[6732]:   keepRefToGeneratedCode=True)
Dec 21 16:40:26 debian weewx[6732]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 740, in compile
Dec 21 16:40:26 debian weewx[6732]:   settings=(compilerSettings or 
{}))
Dec 21 16:40:26 debian weewx[6732]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Compiler.py", line 1579, in 
__init__
Dec 21 16:40:26 debian weewx[6732]:   source = unicode(source)
Dec 21 16:40:26 debian weewx[6732]:   UnicodeDecodeError: 'ascii' codec 
can't decode byte 0xef in position 0: ordinal not in range(128)
Dec 21 16:40:27 debian weewx[6732]: cheetahgenerator: Generate failed with 
exception ''
Dec 21 16:40:27 debian weewx[6732]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Belchertown/index.html.tmpl
Dec 21 16:40:27 debian weewx[6732]: cheetahgenerator:  Reason: 'ascii' 
codec can't decode byte 0xef in position 0: ordinal not in range(128)
Dec 21 16:40:27 debian weewx[6732]:   Traceback (most recent call last):
Dec 21 16:40:27 debian weewx[6732]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 328, in generate
Dec 21 16:40:27 debian weewx[6732]:   
filtersLib=weewx.cheetahgenerator)
Dec 21 16:40:27 debian weewx[6732]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1259, in 
__init__
Dec 21 16:40:27 debian weewx[6732]:   self._compile(source, file, 
compilerSettings=compilerSettings)
Dec 21 16:40:27 debian weewx[6732]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1553, in 
_compile
Dec 21 16:40:27 debian weewx[6732]:   keepRefToGeneratedCode=True)
Dec 21 16:40:27 debian weewx[6732]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 740, in compile
Dec 21 16:40:27 debian weewx[6732]:   settings=(compilerSettings or 
{}))
Dec 21 16:40:27 debian weewx[6732]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Compiler.py", line 1579, in 
__init__
Dec 21 16:40:27 debian weewx[6732]:   source = unicode(source)
Dec 21 16:40:27 debian weewx[6732]:   UnicodeDecodeError: 'ascii' codec 
can't decode byte 0xef in position 0: ordinal not in range(128)
Dec 21 16:40:27 debian weewx[6732]: cheetahgenerator: Generate failed with 
exception ''
Dec 21 16:40:27 debian weewx[6732]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Belchertown/pi/index.html.tmpl
Dec 21 16:40:27 debian weewx[6732]: cheetahgenerator:  Reason: 'ascii' 
codec can't decode byte 0xef in position 0: ordinal not in range(128)
Dec 21 16:40:27 debian weewx[6732]:   Traceback (most recent call last):
Dec 21 16:40:27 debian weewx[6732]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 328, in generate
Dec 21 16:40:27 debian weewx[6732]:   
filtersLib=weewx.cheetahgenerator)
Dec 21 16:40:27 debian weewx[6732]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1259, in 
__init__
Dec 21 16:40:27 debian weewx[6732]:   self._compile(source, file, 
compilerSettings=compilerSet

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.

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

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

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

[Pat]

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.

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

[Pat]

The skin actually uses HighStock 

 
but has the timeline disabled. Feel free to enable it in your setup :)

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.

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

[WILWetter25]

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.

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

[Andrew Milner]

Which part of the highcharts demo page do you think should be incorporated 
into the Belchertown skin, and instead of what??

On Tuesday, 11 December 2018 22:38:34 UTC+2, WILWetter25 wrote:
>
> Thank you for your hard work. I am looking around for a alternative to 
> Highcharts and I found this:
> https://www.highcharts.com/stock/demo/basic-line
> It would be cool if this could be integrated in the skin :) Just a 
> suggestion 
> Am Freitag, 7. Dezember 2018 23:12:23 UTC+1 schrieb Pat:
>>
>> The last thread was getting a bit long. So I've started a new one. 
>>
>> Belchertown Skin 0.8.1 has been released which fixes a couple of bugs. 
>> See the release notes, and install instructions here:
>>
>> https://github.com/poblabs/weewx-belchertown/releases
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

[rich T]

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.

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

[WILWetter25]

Thank you for your hard work. I am looking around for a alternative to 
Highcharts and I found this:
https://www.highcharts.com/stock/demo/basic-line
It would be cool if this could be integrated in the skin :) Just a 
suggestion 
Am Freitag, 7. Dezember 2018 23:12:23 UTC+1 schrieb Pat:
>
> The last thread was getting a bit long. So I've started a new one. 
>
> Belchertown Skin 0.8.1 has been released which fixes a couple of bugs. See 
> the release notes, and install instructions here:
>
> https://github.com/poblabs/weewx-belchertown/releases
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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

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

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.

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

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 emails

[weewx-user] Re: Belchertown Skin 0.8.1 released

[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:55https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Wes Witt]

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:55https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Philip Kutzenco]

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:55https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[G Hammer]

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:50 ftp weewx[13683]: File 
"/home/weewx/bin/weedb/sqlite.py", line 41, in guarded_fn
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 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.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[G Hammer]

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:55https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[rich T]

https://www.davisinstruments.com/product_documents/weather/app_notes/AN_28-derived-weather-variables.pdf

On Sunday, December 9, 2018 at 8:07:28 PM UTC-5, Philip Kutzenco wrote:
>
> First, let me apologize for hijacking this Belchertown thread to get 
> educated on Apparent Temperature.
>
> Second, thanks Gary, your explanation clarifies it for me. It seems I was 
> fixed on a simplistic definition of Apparent Temperature sometimes used in 
> the US which yields the same value as either Wind Chill, Temperature, or 
> Heat Index depending upon the value of "actual temperature". In contrast, 
> the weewx calculation relies on the more sophisticated model developed by 
> Steadman.
>
> I actually like that the weewx calculated value is different than what I 
> thought it should be. The simplistic definition doesn't add any new 
> information as you could just look at Wind Chill, Heat Index and 
> Temperature to get the same information the simple definition provides. In 
> addition, I don't actually know what formula Vantage uses to calculate Wind 
> Chill and Heat Index (I'll look it up), which my station hardware 
> calculates and provides. 
>
> The Steadman model gives a more nuanced value probably closer to what is 
> intended - that is, what the human body perceives the temperature to be.
>
> I'll move any further questions I have on this to a separate topic.
> phil
>
> On Sunday, December 9, 2018 at 6:05:08 PM UTC-5, gjr80 wrote:
>>
>> As you point out weeWX windchill and heatindex values track outTemp below 
>> certain minimums and above certain maximums respectively. The weeWX 
>> calculated appTemp uses the formulas mentioned in the post you linked and 
>> is quite different to a composite heatindex and windchill (by composite I 
>> mean windchill below 50F and heatindex above 81F). The key difference 
>> (other than the formula) is that appTemp is valid across all temperatures. 
>> appTemp is certainly affected by wind speed (just look at the formula), I 
>> often notice appTemp moving in time (and quite markedly) with wind speed 
>> changes on my realtime gauges.
>>
>> I like to think of 'feels like' as being a term that means different 
>> things to different people and without an agreed understanding can be a 
>> source of confusion. It really is just a general term that tries to better 
>> approximate the effect of current weather conditions on the body, it could 
>> be based on a measure of heatindex, windchill, humidex, wet bulb globe 
>> temperature or apparent temperature. For me in Australia I think of 
>> apparent temperature, I expect in Canada humidex may be a more accepted 
>> measurement.
>>
>> The use of the term 'apparent temperature' can also be confusing at 
>> times; does it refer to the accepted formula for Apparent Temperature (as 
>> you linked or as used by weeWX) or is it the more literal meaining. For 
>> this reason I prefer to refer to something like the 'weeWX appTemp field' 
>> or 'Apparent Temperature' to make it clear I am referring to the calculated 
>> value.
>>
>> Gary
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Dj Merrill]

Thanks for all of the help, and the explanation of how appTemp is 
calculated.  I am much less confused about it now, and think I will put a 
blurb on the "about" page as an explanation to others.

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Philip Kutzenco]

First, let me apologize for hijacking this Belchertown thread to get 
educated on Apparent Temperature.

Second, thanks Gary, your explanation clarifies it for me. It seems I was 
fixed on a simplistic definition of Apparent Temperature sometimes used in 
the US which yields the same value as either Wind Chill, Temperature, or 
Heat Index depending upon the value of "actual temperature". In contrast, 
the weewx calculation relies on the more sophisticated model developed by 
Steadman.

I actually like that the weewx calculated value is different than what I 
thought it should be. The simplistic definition doesn't add any new 
information as you could just look at Wind Chill, Heat Index and 
Temperature to get the same information the simple definition provides. In 
addition, I don't actually know what formula Vantage uses to calculate Wind 
Chill and Heat Index (I'll look it up), which my station hardware 
calculates and provides. 

The Steadman model gives a more nuanced value probably closer to what is 
intended - that is, what the human body perceives the temperature to be.

I'll move any further questions I have on this to a separate topic.
phil

On Sunday, December 9, 2018 at 6:05:08 PM UTC-5, gjr80 wrote:
>
> As you point out weeWX windchill and heatindex values track outTemp below 
> certain minimums and above certain maximums respectively. The weeWX 
> calculated appTemp uses the formulas mentioned in the post you linked and 
> is quite different to a composite heatindex and windchill (by composite I 
> mean windchill below 50F and heatindex above 81F). The key difference 
> (other than the formula) is that appTemp is valid across all temperatures. 
> appTemp is certainly affected by wind speed (just look at the formula), I 
> often notice appTemp moving in time (and quite markedly) with wind speed 
> changes on my realtime gauges.
>
> I like to think of 'feels like' as being a term that means different 
> things to different people and without an agreed understanding can be a 
> source of confusion. It really is just a general term that tries to better 
> approximate the effect of current weather conditions on the body, it could 
> be based on a measure of heatindex, windchill, humidex, wet bulb globe 
> temperature or apparent temperature. For me in Australia I think of 
> apparent temperature, I expect in Canada humidex may be a more accepted 
> measurement.
>
> The use of the term 'apparent temperature' can also be confusing at times; 
> does it refer to the accepted formula for Apparent Temperature (as you 
> linked or as used by weeWX) or is it the more literal meaining. For this 
> reason I prefer to refer to something like the 'weeWX appTemp field' or 
> 'Apparent Temperature' to make it clear I am referring to the calculated 
> value.
>
> Gary
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[gjr80]

As you point out weeWX windchill and heatindex values track outTemp below 
certain minimums and above certain maximums respectively. The weeWX calculated 
appTemp uses the formulas mentioned in the post you linked and is quite 
different to a composite heatindex and windchill (by composite I mean windchill 
below 50F and heatindex above 81F). The key difference (other than the formula) 
is that appTemp is valid across all temperatures. appTemp is certainly affected 
by wind speed (just look at the formula), I often notice appTemp moving in time 
(and quite markedly) with wind speed changes on my realtime gauges.

I like to think of 'feels like' as being a term that means different things to 
different people and without an agreed understanding can be a source of 
confusion. It really is just a general term that tries to better approximate 
the effect of current weather conditions on the body, it could be based on a 
measure of heatindex, windchill, humidex, wet bulb globe temperature or 
apparent temperature. For me in Australia I think of apparent temperature, I 
expect in Canada humidex may be a more accepted measurement.

The use of the term 'apparent temperature' can also be confusing at times; does 
it refer to the accepted formula for Apparent Temperature (as you linked or as 
used by weeWX) or is it the more literal meaining. For this reason I prefer to 
refer to something like the 'weeWX appTemp field' or 'Apparent Temperature' to 
make it clear I am referring to the calculated value.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Philip Kutzenco]

Dj,

Check out this link for details: 
https://groups.google.com/d/msg/weewx-user/bNz3ymPNHHc/caYi1nqlAgAJ

I must say that I have been a bit confused about the appTemp value weewx 
calculates. My understanding is that the Apparent Temperature is equal to 
the Wind Chill number when the temp is 50 degrees F or below. It is equal 
to the Heat Index with the temp is 81 degrees F or above. My Vantage Vue 
transmits Wind Chill and Heat Index values. But the weewx calculated 
appTemp value doesn't match my understanding of what it should equal (or at 
least closely equal).

I wonder if it has to do with Loop Values for wind speed (which drives Wind 
Chill) and humidity (which drives Heat Index) vs. archive values for for 
those measures (which are aggregates). I don't know. Maybe someone else  
knows?
phil

On Sunday, December 9, 2018 at 5:04:01 PM UTC-5, Dj Merrill wrote:
>
> That worked beautifully, thank you Philip!
>
> I don't believe the data it is showing is correct, though.  Outside temp 
> is 23.5 F currently, with no wind.  It is showing a "feels like" 
> temperature of 18.1 F.  Other sources  are showing the feels like temp in 
> my area being the same as the outside temp.
>
> How is it calculating the data?
>
> 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.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Dj Merrill]

That worked beautifully, thank you Philip!

I don't believe the data it is showing is correct, though.  Outside temp is 
23.5 F currently, with no wind.  It is showing a "feels like" temperature 
of 18.1 F.  Other sources  are showing the feels like temp in my area being 
the same as the outside temp.

How is it calculating the data?

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.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Philip Kutzenco]

One more thing:

extensions.py could be in /home/weewx/bin/user if you installed weewx with 
setup.py rather than with apt-get.
phil


On Sunday, December 9, 2018 at 4:51:15 PM UTC-5, Philip Kutzenco wrote:
>
> Dj,
>
> (I deleted the first version of this post as I left out a trailing "]" in 
> step 1).
>
> This is from instructions Pat gave me in the past to extend the schema:
>
> 1) Extend the database
>
> nano /usr/share/weewx/user/extensions.py
>
> then add the following:
>
>
> *import schemas.wviewschema_apptemp = schemas.wview.schema + 
> [('appTemp',   'REAL')]*
>
>
>
> 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
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Philip Kutzenco]

Dj,

(I deleted the first version of this post as I left out a trailing "]" in 
step 1).

This is from instructions Pat gave me in the past to extend the schema:

1) Extend the database

nano /usr/share/weewx/user/extensions.py

then add the following:


*import schemas.wviewschema_apptemp = schemas.wview.schema + [('appTemp',   
'REAL')]*



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.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Philip Kutzenco]

Dj,

This is from instructions Pat gave me in the past to extend the schema:

1) Extend the database

nano /usr/share/weewx/user/extensions.py

then add the following:


*import schemas.wviewschema_apptemp = schemas.wview.schema + [('appTemp',   
'REAL')*



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

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Dj Merrill]

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.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Philip Kutzenco]

Dj,

In addition to extending the schema for your database to include appTemp, 
as Pat notes (this is a requirement), I recommend you add the line 
mentioned by Rich

show apptemp = 1

in the [[[Extras]]] stanza of the [[Belchertown]] stanza in weewx.conf 
(instead of adding it to skin.conf). This will ensure that the change 
"sticks" after installs of new Belchertown skin versions.
phil

On Sunday, December 9, 2018 at 3:49:43 PM UTC-5, Pat wrote:
>
> Thanks Dj! As mentioned in the general options guide 
> , your 
> database will need to be extended for the appTemp 
>  observations. 
>
> On Sunday, December 9, 2018 at 3:44:00 PM UTC-5, rich T wrote:
>>
>> Dj
>>
>> In the skin.conf file located in the Belchertown folder, set 
>> "show_apptemp = 1". Restart weewx.
>>
>> Rich 
>>
>> On Sunday, December 9, 2018 at 3:27:35 PM UTC-5, Dj Merrill wrote:
>>
>>> Pat, what a beautiful piece of work!  Thank you for sharing this with us!
>>>
>>> I notice on your site there is a "Feels like" temperature shown under 
>>> the outside temperature and above the high/low temps on the top of the main 
>>> page.  I don't see that on my site, and am wondering how to enable that?
>>>
>>> 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.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Pat]

Thanks Dj! As mentioned in the general options guide 
, your 
database will need to be extended for the appTemp 
 observations. 

On Sunday, December 9, 2018 at 3:44:00 PM UTC-5, rich T wrote:
>
> Dj
>
> In the skin.conf file located in the Belchertown folder, set "show_apptemp 
> = 1". Restart weewx.
>
> Rich 
>
> On Sunday, December 9, 2018 at 3:27:35 PM UTC-5, Dj Merrill wrote:
>
>> Pat, what a beautiful piece of work!  Thank you for sharing this with us!
>>
>> I notice on your site there is a "Feels like" temperature shown under the 
>> outside temperature and above the high/low temps on the top of the main 
>> page.  I don't see that on my site, and am wondering how to enable that?
>>
>> 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.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[rich T]

Dj

In the skin.conf file located in the Belchertown folder, set "show_apptemp 
= 1". Restart weewx.

Rich 

On Sunday, December 9, 2018 at 3:27:35 PM UTC-5, Dj Merrill wrote:

> Pat, what a beautiful piece of work!  Thank you for sharing this with us!
>
> I notice on your site there is a "Feels like" temperature shown under the 
> outside temperature and above the high/low temps on the top of the main 
> page.  I don't see that on my site, and am wondering how to enable that?
>
> 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.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Dj Merrill]

Pat, what a beautiful piece of work!  Thank you for sharing this with us!

I notice on your site there is a "Feels like" temperature shown under the 
outside temperature and above the high/low temps on the top of the main 
page.  I don't see that on my site, and am wondering how to enable that?

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.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[rich T]

Got it to show...thanks Pat

On Sunday, December 9, 2018 at 2:07:20 PM UTC-5, Pat wrote:
>
> No tag, but the version number is in the view source at the bottom. 

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

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.