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

[Michael Waldor]

I, too, have the same problem.

My guess is that due to heavy rain the radio signal is attenuated too much. 
I use a raspberry to log the data, 10cm next to the weather station. 2 
weeks ago I've switched from wifi to LAN connection thus reducing radio 
interference somehow. Till now I did not loose the outdoor sensors even 
during rain.

But I suffer under two other problems:
1. UV sensor has died after 6months - its data degraded end of July over 
some days till it was zero continuously.
2. I sometimes have USB connection problems being solved by rebooting my 
raspberry - I use a watchdog now to reboot automatically.

Am Donnerstag, 13. Dezember 2018 20:11:04 UTC+1 schrieb Kalli:
>
>  Bei mir ist das auch so.
> nur die ID vom UV sensor bleibt.
>

-- 
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] Changing the start and finish of the "day"

[Colin Larsen]

Hi all

I haven't managed to find the simple answer to this, in some ways I hope it 
isn't too simple and I skimmed over it!

Here in NZ (and Australia I believe) the "meteorological day" is from 0900 
in the morning until 0900 the next morning. So rainfall totals for instance 
are taken from the amount between those times. My weather station can be 
set to use those times without any problem, what I am unsure of is the 
affect (if any) on Weewx? I assume that tags such as $day.rain.sum (hope I 
got that example right) would still take the data from midnight, not 0900? 
And that the NOAA reports generated and any daily records would also be 
within that midnight to midnight  time span?

Hopefully I've phrased this question properly and there is a fairly 
straight forward answer.

Many thanks
Colin

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

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

[G Hammer]

Pat,

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

[image: Alert.png]



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

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

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

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

[weewx-user] Re: AcuRite 01036M failed to get LOOP data

[Scott Grayban]

Hmm I wonder if I should do this. I haven't seen my Acurite fail so I 
wonder if that's a PI 3B you are using.

On Thursday, December 27, 2018 at 5:20:42 PM UTC-8, Dallas Epperson wrote:
>
> I have fixed the issue, but leaving the thread here in case someone 
> googles the issue and it helps them.
>
> The issue was with the pi and how it handles USB. I followed this advice 
> from Jim Easterbrook 
> to 
> keep that USB port from flipping between host and peripheral. 
>
> sudo vi /boot/config.txt
> add this line to the bottom:
> dtoverlay=dwc2,dr_mode=host
> and then reboot the pi.
>
> Cheers.
>
> On Thursday, December 27, 2018 at 7:42:24 PM UTC-5, Dallas Epperson wrote:
>>
>> I just installed weewx on a raspberry pi 3b+ running raspbian using apt. 
>> I have an AcuRite 01036M and the console connected to the pi via USB. On 
>> the AcuRite console, I have set USB mode to 3. 
>>
>> I'm not certain the console is being properly recognized by the pi. When 
>> I issue a lsusb command, I see this:
>> Bus 001 Device 004: ID 24c0:0003
>> Typically, I would expect to see the vendor and model number after that. 
>>
>> Also, when I tail /var/log/syslog, I see these error messages:
>> weewx[421]: acurite: Failed attempt 10 of 10 to get LOOP data: [Errno 
>> 110] Operation timed out
>>
>> Occasionally, Errno110 is replaced with
>> [Errno 32] Pipe error
>>
>> Any ideas?
>>
>

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

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

[Pat]

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

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

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

[Pat]

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

[Pat]

I agree. I've pushed these changes to GitHub 

. 

Feel free to grab the latest skins/Belchertown/index.html.tmpl and 
skin.conf, as well as bin/user/belchertown.py. 

The forecast_alert_length option is now deleted (not needed)

Restart weewx. 

On Thursday, December 27, 2018 at 8:35:21 PM UTC-5, G Hammer wrote:
>
> That gives the alert and enough info to decide if you want to see the 
> whole alert. 
> I like it. 
>
> On Thu, Dec 27, 2018 at 8:33 PM Pat > 
> wrote:
>
>> Perhaps something like this?
>>
>> On Thursday, December 27, 2018 at 8:27:23 PM UTC-5, G Hammer wrote:
>>>
>>> If you could just link the alert and no additional text you could fit 
>>> several on one line. 
>>> If I see an alert, I’m going to click for more info anyway. 
>>>
>>> On Thu, Dec 27, 2018 at 8:19 PM Pat  wrote:
>>>
 I feel like the attachment is too busy, but it's an option. Otherwise I 
 could try to pare it down to something like the NWS has with something 
 simple: High Wind Watch in effect until December 30, 08:00 AM MST


 On Thursday, December 27, 2018 at 7:56:42 PM UTC-5, Pat wrote:
>
> Yeah I was afraid of that. I was thinking on my drive home today how 
> best to show them without flooding the screen. 
>
>
> On Thursday, December 27, 2018 at 7:55:35 PM UTC-5, rich T wrote:
>>
>> Pat
>>
>> If an area has multiple alerts, the skin only displays the first 
>> Alert.
>>
>>
>> https://forecast.weather.gov/MapClick.php?site=tfx&zmx=&zmy=&map_x=168&map_y=146&x=168&y=146#.XCVn1WaWy70
>>
>>
>>
>>
>>> -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups "weewx-user" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/weewx-user/sEd4sVkjpZw/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 weewx-user+...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/sEd4sVkjpZw/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@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

[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

[weewx-user] Re: AcuRite 01036M failed to get LOOP data

[Dallas Epperson]

I have fixed the issue, but leaving the thread here in case someone googles 
the issue and it helps them.

The issue was with the pi and how it handles USB. I followed this advice 
from Jim Easterbrook 
to 
keep that USB port from flipping between host and peripheral. 

sudo vi /boot/config.txt
add this line to the bottom:
dtoverlay=dwc2,dr_mode=host
and then reboot the pi.

Cheers.

On Thursday, December 27, 2018 at 7:42:24 PM UTC-5, Dallas Epperson wrote:
>
> I just installed weewx on a raspberry pi 3b+ running raspbian using apt. 
> I have an AcuRite 01036M and the console connected to the pi via USB. On 
> the AcuRite console, I have set USB mode to 3. 
>
> I'm not certain the console is being properly recognized by the pi. When I 
> issue a lsusb command, I see this:
> Bus 001 Device 004: ID 24c0:0003
> Typically, I would expect to see the vendor and model number after that. 
>
> Also, when I tail /var/log/syslog, I see these error messages:
> weewx[421]: acurite: Failed attempt 10 of 10 to get LOOP data: [Errno 110] 
> Operation timed out
>
> Occasionally, Errno110 is replaced with
> [Errno 32] Pipe error
>
> Any ideas?
>

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

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

[G Hammer]

That gives the alert and enough info to decide if you want to see the whole
alert.
I like it.

On Thu, Dec 27, 2018 at 8:33 PM Pat  wrote:

> Perhaps something like this?
>
> On Thursday, December 27, 2018 at 8:27:23 PM UTC-5, G Hammer wrote:
>>
>> If you could just link the alert and no additional text you could fit
>> several on one line.
>> If I see an alert, I’m going to click for more info anyway.
>>
>> On Thu, Dec 27, 2018 at 8:19 PM Pat  wrote:
>>
>>> I feel like the attachment is too busy, but it's an option. Otherwise I
>>> could try to pare it down to something like the NWS has with something
>>> simple: High Wind Watch in effect until December 30, 08:00 AM MST
>>>
>>>
>>> On Thursday, December 27, 2018 at 7:56:42 PM UTC-5, Pat wrote:

 Yeah I was afraid of that. I was thinking on my drive home today how
 best to show them without flooding the screen.


 On Thursday, December 27, 2018 at 7:55:35 PM UTC-5, rich T wrote:
>
> Pat
>
> If an area has multiple alerts, the skin only displays the first Alert.
>
>
> https://forecast.weather.gov/MapClick.php?site=tfx&zmx=&zmy=&map_x=168&map_y=146&x=168&y=146#.XCVn1WaWy70
>
>
>
>
>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/weewx-user/sEd4sVkjpZw/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> weewx-user+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/sEd4sVkjpZw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

[Pat]

Perhaps something like this?

On Thursday, December 27, 2018 at 8:27:23 PM UTC-5, G Hammer wrote:
>
> If you could just link the alert and no additional text you could fit 
> several on one line. 
> If I see an alert, I’m going to click for more info anyway. 
>
> On Thu, Dec 27, 2018 at 8:19 PM Pat > 
> wrote:
>
>> I feel like the attachment is too busy, but it's an option. Otherwise I 
>> could try to pare it down to something like the NWS has with something 
>> simple: High Wind Watch in effect until December 30, 08:00 AM MST
>>
>>
>> On Thursday, December 27, 2018 at 7:56:42 PM UTC-5, Pat wrote:
>>>
>>> Yeah I was afraid of that. I was thinking on my drive home today how 
>>> best to show them without flooding the screen. 
>>>
>>>
>>> On Thursday, December 27, 2018 at 7:55:35 PM UTC-5, rich T wrote:

 Pat

 If an area has multiple alerts, the skin only displays the first Alert.


 https://forecast.weather.gov/MapClick.php?site=tfx&zmx=&zmy=&map_x=168&map_y=146&x=168&y=146#.XCVn1WaWy70




> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/sEd4sVkjpZw/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@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]

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

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

[G Hammer]

If you could just link the alert and no additional text you could fit
several on one line.
If I see an alert, I’m going to click for more info anyway.

On Thu, Dec 27, 2018 at 8:19 PM Pat  wrote:

> I feel like the attachment is too busy, but it's an option. Otherwise I
> could try to pare it down to something like the NWS has with something
> simple: High Wind Watch in effect until December 30, 08:00 AM MST
>
>
> On Thursday, December 27, 2018 at 7:56:42 PM UTC-5, Pat wrote:
>>
>> Yeah I was afraid of that. I was thinking on my drive home today how best
>> to show them without flooding the screen.
>>
>>
>> On Thursday, December 27, 2018 at 7:55:35 PM UTC-5, rich T wrote:
>>>
>>> Pat
>>>
>>> If an area has multiple alerts, the skin only displays the first Alert.
>>>
>>>
>>> https://forecast.weather.gov/MapClick.php?site=tfx&zmx=&zmy=&map_x=168&map_y=146&x=168&y=146#.XCVn1WaWy70
>>>
>>>
>>>
>>>
 --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/sEd4sVkjpZw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[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 DarkSky Alerts

[Pat]

I feel like the attachment is too busy, but it's an option. Otherwise I 
could try to pare it down to something like the NWS has with something 
simple: High Wind Watch in effect until December 30, 08:00 AM MST


On Thursday, December 27, 2018 at 7:56:42 PM UTC-5, Pat wrote:
>
> Yeah I was afraid of that. I was thinking on my drive home today how best 
> to show them without flooding the screen. 
>
>
> On Thursday, December 27, 2018 at 7:55:35 PM UTC-5, rich T wrote:
>>
>> Pat
>>
>> If an area has multiple alerts, the skin only displays the first Alert.
>>
>>
>> https://forecast.weather.gov/MapClick.php?site=tfx&zmx=&zmy=&map_x=168&map_y=146&x=168&y=146#.XCVn1WaWy70
>>
>>
>>
>>
>>>

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

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] AcuRite 01036M failed to get LOOP data

[Dallas Epperson]

I just installed weewx on a raspberry pi 3b+ running raspbian using apt. 
I have an AcuRite 01036M and the console connected to the pi via USB. On 
the AcuRite console, I have set USB mode to 3. 

I'm not certain the console is being properly recognized by the pi. When I 
issue a lsusb command, I see this:
Bus 001 Device 004: ID 24c0:0003
Typically, I would expect to see the vendor and model number after that. 

Also, when I tail /var/log/syslog, I see these error messages:
weewx[421]: acurite: Failed attempt 10 of 10 to get LOOP data: [Errno 110] 
Operation timed out

Occasionally, Errno110 is replaced with
[Errno 32] Pipe error

Any ideas?

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

[Pat]

Yeah I was afraid of that. I was thinking on my drive home today how best 
to show them without flooding the screen. 


On Thursday, December 27, 2018 at 7:55:35 PM UTC-5, rich T wrote:
>
> Pat
>
> If an area has multiple alerts, the skin only displays the first Alert.
>
>
> https://forecast.weather.gov/MapClick.php?site=tfx&zmx=&zmy=&map_x=168&map_y=146&x=168&y=146#.XCVn1WaWy70
>
>
>
>
>>

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

[rich T]

Pat

If an area has multiple alerts, the skin only displays the first Alert.

https://forecast.weather.gov/MapClick.php?site=tfx&zmx=&zmy=&map_x=168&map_y=146&x=168&y=146#.XCVn1WaWy70




>

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

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: Looking to replace my old Acurite 0203C weather station

[Scott Grayban]

Thanks for the info !!! I'll work on doing this and post back on my results.

On Thursday, December 27, 2018 at 7:09:57 AM UTC-8, Dj Merrill wrote:
>
> On 12/27/2018 2:44 AM, Scott Grayban wrote: 
>
> I like this one http://a.co/d/1Lsy6fJ but it doesn't work with weewx. 
>
>
>
> The Ambient Weather WS-2902A works fine with WeeWX, using the Interceptor 
> driver and a Raspberry Pi 3B in my case. 
>
> There seem to be a few ways to make this work.  I went with the RPi using 
> the hard wired ethernet port attached to my local network, and setup the 
> wireless on the RPi to act as an Access Point.  The WS-2902A connects to 
> the RPis wireless network, and WeeWx with the Interceptor software runs on 
> the Rpi. 
>
> There seem to be other ways to make this work based on other posts on the 
> mailing list, such as redirecting traffic from your wireless router to your 
> WeeWx machine. 
>
>
>
> -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.

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

[G Hammer]

Hi Pat,

I have the Winter Weather Advisory. Nothing broken.
Thanks!

On Thursday, December 27, 2018 at 3:15:38 PM UTC-5, Pat wrote:
>
> I just received a weather alert on https://belchertownweather.com/ - so 
> far so good.
>
> Keep me posted on any alerts you guys get to make sure there's no bugs
>
> On Thursday, December 27, 2018 at 12:11:59 PM UTC-5, rich T wrote:
>>
>> Updated the files and all is running well. thanks Pat
>>
>> On Wednesday, December 26, 2018 at 7:53:57 PM UTC-5, Pat wrote:
>>>
>>> I've made more changes to this. Now you have to opt in for the alerts. 
>>> Erring on the side that alerts may not appeal or be available to everyone 
>>> in every region, it's opt-in. Simply add forecast_alert_enabled = 1 to 
>>> your skin options in weewx.conf. 
>>>
>>> The alert description has a default truncate at 75 characters. You can 
>>> override that with skin option forecast_alert_length
>>>
>>> Also non-MQTT sites now have alerts available to them. 
>>>
>>> Changes made to skin.conf, index.html.tmpl and user/bin/belchertown.py. 
>>> You can find the latest files in the repository and in the list of 
>>> recent commits 
>>> . 
>>>
>>> Please test it out. 
>>>
>>> On Wednesday, December 26, 2018 at 4:09:00 PM UTC-5, Colin Larsen wrote:

 Does that mean that I'll see alerts even though I only use the Darksky 
 current conditions? Did you pop in the option to disable the alerts?

 On Thu, 27 Dec 2018, 09:49 Pat >>>
> Sounds good! 
>
> I should add another disclaimer that the showing and hiding of the 
> alert bar automatically without reloading the website is only 
> accomplished 
> if you have the MQTT feature enabled. 
>
> Which reminds me I need to add an option to show that bar if MQTT is 
> disabled. I'll have to make another update later today. 
>
> On Wednesday, December 26, 2018 at 1:45:49 PM UTC-5, rich T wrote:
>>
>> Thanks Pat...Downloaded and installed both files and restarted 
>> weewx. No alerts in the area at this time; mostly likely some alerts 
>> towards end of week when the icy weather comes through.  We'll keep you 
>> informed.
>>
>> Rich
>>
>> On Wednesday, December 26, 2018 at 11:47:44 AM UTC-5, Pat wrote:
>>
>>> Oops - forgot to hide the alert bar 
>>> 
>>>  when 
>>> an alert clears. Try this updated version attached. Same rules apply as 
>>> above. 
>>>
>>>
>>> On Wednesday, December 26, 2018 at 11:39:24 AM UTC-5, Pat wrote:

 I just committed an initial attempt 
 .
  
 You can download the files from GitHub or from the attachments here. 

 As usual, have a backup of your setup just in case. To test it out, 
 copy the attached files to skins/Belchertown and restart weewx. 
 Wait for an archive period and if you have a weather alert, it should 
 appear like in the screenshot. Clicking the link will take you to the 
 source of the alert. 

 The alert area should update automatically in the background (no 
 page refresh needed). So if an alert goes active, it'll pop up the 
 alert 
 area. When it's gone it'll disappear. At least it should in theory :)

 Will need some testing and ironing out over the next few days for 
 sure... Let me know how it goes. 



 On Wednesday, December 26, 2018 at 9:54:46 AM UTC-5, Pat wrote:
>
> Agreed. Let me work on a concept
>
> On Wednesday, December 26, 2018 at 9:47:56 AM UTC-5, rich T wrote:
>>
>> I think underneath the timestamp with the Icon would look fine.  
>> Same text size as the timestamp but bold.  Maybe make the Alerts 
>> optional 
>> feature, so the users has a choice to display the Alerts.
>>
>> On Wednesday, December 26, 2018 at 9:29:16 AM UTC-5, Pat wrote:
>>>
>>> Ok cool. That GitHub repo just confirmed that I am doing what 
>>> they're doing. I'm not using JavaScript though, I'm just grabbing 
>>> the raw 
>>> JSON from DarkSky. I guess I've never seen the alerts array in my 
>>> output 
>>> when I initially created it, so out of sight out of mind?
>>>
>>> I just grabbed a forecast for an area in South Dakota that was 
>>> under weather advisory , 
>>> and I see in DarkSky's forecast it has the alert data. So I can use 
>>> this 
>>> sample data to include it in the skin. 
>>>
>>> Where and how should the alert be shown? I'd

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

[Pat]

I just received a weather alert on https://belchertownweather.com/ - so far 
so good.

Keep me posted on any alerts you guys get to make sure there's no bugs

On Thursday, December 27, 2018 at 12:11:59 PM UTC-5, rich T wrote:
>
> Updated the files and all is running well. thanks Pat
>
> On Wednesday, December 26, 2018 at 7:53:57 PM UTC-5, Pat wrote:
>>
>> I've made more changes to this. Now you have to opt in for the alerts. 
>> Erring on the side that alerts may not appeal or be available to everyone 
>> in every region, it's opt-in. Simply add forecast_alert_enabled = 1 to 
>> your skin options in weewx.conf. 
>>
>> The alert description has a default truncate at 75 characters. You can 
>> override that with skin option forecast_alert_length
>>
>> Also non-MQTT sites now have alerts available to them. 
>>
>> Changes made to skin.conf, index.html.tmpl and user/bin/belchertown.py. 
>> You can find the latest files in the repository and in the list of 
>> recent commits 
>> . 
>>
>> Please test it out. 
>>
>> On Wednesday, December 26, 2018 at 4:09:00 PM UTC-5, Colin Larsen wrote:
>>>
>>> Does that mean that I'll see alerts even though I only use the Darksky 
>>> current conditions? Did you pop in the option to disable the alerts?
>>>
>>> On Thu, 27 Dec 2018, 09:49 Pat >>
 Sounds good! 

 I should add another disclaimer that the showing and hiding of the 
 alert bar automatically without reloading the website is only accomplished 
 if you have the MQTT feature enabled. 

 Which reminds me I need to add an option to show that bar if MQTT is 
 disabled. I'll have to make another update later today. 

 On Wednesday, December 26, 2018 at 1:45:49 PM UTC-5, rich T wrote:
>
> Thanks Pat...Downloaded and installed both files and restarted 
> weewx. No alerts in the area at this time; mostly likely some alerts 
> towards end of week when the icy weather comes through.  We'll keep you 
> informed.
>
> Rich
>
> On Wednesday, December 26, 2018 at 11:47:44 AM UTC-5, Pat wrote:
>
>> Oops - forgot to hide the alert bar 
>> 
>>  when 
>> an alert clears. Try this updated version attached. Same rules apply as 
>> above. 
>>
>>
>> On Wednesday, December 26, 2018 at 11:39:24 AM UTC-5, Pat wrote:
>>>
>>> I just committed an initial attempt 
>>> .
>>>  
>>> You can download the files from GitHub or from the attachments here. 
>>>
>>> As usual, have a backup of your setup just in case. To test it out, 
>>> copy the attached files to skins/Belchertown and restart weewx. 
>>> Wait for an archive period and if you have a weather alert, it should 
>>> appear like in the screenshot. Clicking the link will take you to the 
>>> source of the alert. 
>>>
>>> The alert area should update automatically in the background (no 
>>> page refresh needed). So if an alert goes active, it'll pop up the 
>>> alert 
>>> area. When it's gone it'll disappear. At least it should in theory :)
>>>
>>> Will need some testing and ironing out over the next few days for 
>>> sure... Let me know how it goes. 
>>>
>>>
>>>
>>> On Wednesday, December 26, 2018 at 9:54:46 AM UTC-5, Pat wrote:

 Agreed. Let me work on a concept

 On Wednesday, December 26, 2018 at 9:47:56 AM UTC-5, rich T wrote:
>
> I think underneath the timestamp with the Icon would look fine.  
> Same text size as the timestamp but bold.  Maybe make the Alerts 
> optional 
> feature, so the users has a choice to display the Alerts.
>
> On Wednesday, December 26, 2018 at 9:29:16 AM UTC-5, Pat wrote:
>>
>> Ok cool. That GitHub repo just confirmed that I am doing what 
>> they're doing. I'm not using JavaScript though, I'm just grabbing 
>> the raw 
>> JSON from DarkSky. I guess I've never seen the alerts array in my 
>> output 
>> when I initially created it, so out of sight out of mind?
>>
>> I just grabbed a forecast for an area in South Dakota that was 
>> under weather advisory , 
>> and I see in DarkSky's forecast it has the alert data. So I can use 
>> this 
>> sample data to include it in the skin. 
>>
>> Where and how should the alert be shown? I'd like to keep it in 
>> line with the clean look of the skin. 
>>
>> I think I'll show the alert at the top of the page beneath the 
>> timestamp. An alert icon (maybe something like this? 
>> 

Re: [weewx-user] Re: rtl_433 and Weewxd config problems!!

[gjr80]

Someone else's config will be great but at the end of the day it will be 
different to what you will need to use. Have you worked through steps 4 and 5 
of the sdr readme as well as the How to run the driver directly and 
Configuration sections?You need to work through these to identify what sensors 
you wish to intercept with sdr and how you want their data mapped to weeWX 
fields.

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: rtl_433 and Weewxd config problems!!

[Charlie Thompson]

Thanks Mike,

When it’s convenient I’d love to see your weewx.conf file. 

-Charlie

Sent from my iPhone8
(Please excuse any typos or brevity)
 

> On Dec 27, 2018, at 10:59 AM, Mike Hawkins  wrote:
> 
> I’m have used it without problems.  I’m not close to mine today, so I can’t 
> send you a config file.  But I did not see any sensor_map section in your 
> conf file. You need to have that to convert what you are getting to weewx 
> sensors.
> 
> See:
> 
> https://github.com/matthewwall/weewx-sdr
> 
> 
> Mike
> 
> -- 
> 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: rtl_433 and Weewxd config problems!!

[Mike Hawkins]

I’m have used it without problems.  I’m not close to mine today, so I can’t 
send you a config file.  But I did not see any sensor_map section in your conf 
file. You need to have that to convert what you are getting to weewx sensors.

See:

https://github.com/matthewwall/weewx-sdr


Mike

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

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

[rich T]

Updated the files and all is running well. thanks Pat

On Wednesday, December 26, 2018 at 7:53:57 PM UTC-5, Pat wrote:
>
> I've made more changes to this. Now you have to opt in for the alerts. 
> Erring on the side that alerts may not appeal or be available to everyone 
> in every region, it's opt-in. Simply add forecast_alert_enabled = 1 to 
> your skin options in weewx.conf. 
>
> The alert description has a default truncate at 75 characters. You can 
> override that with skin option forecast_alert_length
>
> Also non-MQTT sites now have alerts available to them. 
>
> Changes made to skin.conf, index.html.tmpl and user/bin/belchertown.py. 
> You can find the latest files in the repository and in the list of recent 
> commits . 
>
> Please test it out. 
>
> On Wednesday, December 26, 2018 at 4:09:00 PM UTC-5, Colin Larsen wrote:
>>
>> Does that mean that I'll see alerts even though I only use the Darksky 
>> current conditions? Did you pop in the option to disable the alerts?
>>
>> On Thu, 27 Dec 2018, 09:49 Pat >
>>> Sounds good! 
>>>
>>> I should add another disclaimer that the showing and hiding of the alert 
>>> bar automatically without reloading the website is only accomplished if you 
>>> have the MQTT feature enabled. 
>>>
>>> Which reminds me I need to add an option to show that bar if MQTT is 
>>> disabled. I'll have to make another update later today. 
>>>
>>> On Wednesday, December 26, 2018 at 1:45:49 PM UTC-5, rich T wrote:

 Thanks Pat...Downloaded and installed both files and restarted 
 weewx. No alerts in the area at this time; mostly likely some alerts 
 towards end of week when the icy weather comes through.  We'll keep you 
 informed.

 Rich

 On Wednesday, December 26, 2018 at 11:47:44 AM UTC-5, Pat wrote:

> Oops - forgot to hide the alert bar 
> 
>  when 
> an alert clears. Try this updated version attached. Same rules apply as 
> above. 
>
>
> On Wednesday, December 26, 2018 at 11:39:24 AM UTC-5, Pat wrote:
>>
>> I just committed an initial attempt 
>> .
>>  
>> You can download the files from GitHub or from the attachments here. 
>>
>> As usual, have a backup of your setup just in case. To test it out, 
>> copy the attached files to skins/Belchertown and restart weewx. Wait 
>> for an archive period and if you have a weather alert, it should appear 
>> like in the screenshot. Clicking the link will take you to the source of 
>> the alert. 
>>
>> The alert area should update automatically in the background (no page 
>> refresh needed). So if an alert goes active, it'll pop up the alert 
>> area. 
>> When it's gone it'll disappear. At least it should in theory :)
>>
>> Will need some testing and ironing out over the next few days for 
>> sure... Let me know how it goes. 
>>
>>
>>
>> On Wednesday, December 26, 2018 at 9:54:46 AM UTC-5, Pat wrote:
>>>
>>> Agreed. Let me work on a concept
>>>
>>> On Wednesday, December 26, 2018 at 9:47:56 AM UTC-5, rich T wrote:

 I think underneath the timestamp with the Icon would look fine.  
 Same text size as the timestamp but bold.  Maybe make the Alerts 
 optional 
 feature, so the users has a choice to display the Alerts.

 On Wednesday, December 26, 2018 at 9:29:16 AM UTC-5, Pat wrote:
>
> Ok cool. That GitHub repo just confirmed that I am doing what 
> they're doing. I'm not using JavaScript though, I'm just grabbing the 
> raw 
> JSON from DarkSky. I guess I've never seen the alerts array in my 
> output 
> when I initially created it, so out of sight out of mind?
>
> I just grabbed a forecast for an area in South Dakota that was 
> under weather advisory , 
> and I see in DarkSky's forecast it has the alert data. So I can use 
> this 
> sample data to include it in the skin. 
>
> Where and how should the alert be shown? I'd like to keep it in 
> line with the clean look of the skin. 
>
> I think I'll show the alert at the top of the page beneath the 
> timestamp. An alert icon (maybe something like this? 
> ) and a brief text of the 
> alert next to it. Then you can click the alert to see the full 
> details. 
>
>
>
>
> On Tuesday, December 25, 2018 at 9:57:56 PM UTC-5, rich T wrote:
>>
>> Could this work with in your code:
>>
>> DarkSkyApi.loa

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

Ok thanks...

i will try factory reset...

thanks.

El jueves, 27 de diciembre de 2018, 16:27:37 (UTC+1), Cameron D escribió:
>
> Thanks, it is even odder than I expected.
> The USB block has speeds zero, however at the end there is a section weewx 
> does not use, which I think is maximum gust today, followed by max gust 
> this month.
> The max gust today (2018-12-27 at 00:00 was zero) but max for month was 
> 1.1 m/s at 2018-12-26 18:44. 
>
> This seems a tiny value, but the fact that is it not zero suggests it 
> might be a scaling error.
>
> I think you should connect the Windows software, save the history, and see 
> what it reports as wind speeds.
>
> A factory reset might help.
>
> Cameron.
>
> On Thursday, 27 December 2018 23:57:17 UTC+10, Juan Antonio Mosquera wrote:
>>
>> ok sorry... my data portion
>>
>>
>>
>>
>> Dec 27 14:56:20 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918981, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
>> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
>> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
>> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>> 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918983, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
>> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
>> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
>> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>> 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918983, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
>> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
>> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
>> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>> 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918985, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
>> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
>> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
>> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>> 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: raw packet: 
>> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
>> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: converted packet: 
>> {'windchill': None, 'dateTime': 1545918986, 'windDir': 206.0, 'windSpeed': 
>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
>> Dec 27 14:56:27 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
>> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
>> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
>> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
>> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
>> 157.0, 'channel': 1, 'windchill': None}
>> Dec 27 14:56:27 meteomontaos weewx[17954]: wmr300: raw

[weewx-user] Re: problem with wind in WMR300

[Cameron D]

Thanks, it is even odder than I expected.
The USB block has speeds zero, however at the end there is a section weewx 
does not use, which I think is maximum gust today, followed by max gust 
this month.
The max gust today (2018-12-27 at 00:00 was zero) but max for month was 1.1 
m/s at 2018-12-26 18:44. 

This seems a tiny value, but the fact that is it not zero suggests it might 
be a scaling error.

I think you should connect the Windows software, save the history, and see 
what it reports as wind speeds.

A factory reset might help.

Cameron.

On Thursday, 27 December 2018 23:57:17 UTC+10, Juan Antonio Mosquera wrote:
>
> ok sorry... my data portion
>
>
>
>
> Dec 27 14:56:20 meteomontaos weewx[17954]: wmr300: converted packet: 
> {'windchill': None, 'dateTime': 1545918981, 'windDir': 206.0, 'windSpeed': 
> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
> 157.0, 'channel': 1, 'windchill': None}
> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: raw packet: 
> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
> Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: converted packet: 
> {'windchill': None, 'dateTime': 1545918983, 'windDir': 206.0, 'windSpeed': 
> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
> 157.0, 'channel': 1, 'windchill': None}
> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: raw packet: 
> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
> Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: converted packet: 
> {'windchill': None, 'dateTime': 1545918983, 'windDir': 206.0, 'windSpeed': 
> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
> 157.0, 'channel': 1, 'windchill': None}
> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: raw packet: 
> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: converted packet: 
> {'windchill': None, 'dateTime': 1545918985, 'windDir': 206.0, 'windSpeed': 
> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
> 157.0, 'channel': 1, 'windchill': None}
> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: raw packet: 
> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
> Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: converted packet: 
> {'windchill': None, 'dateTime': 1545918986, 'windDir': 206.0, 'windSpeed': 
> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
> Dec 27 14:56:27 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
> 0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
> 0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
> 00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
> 'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
> 157.0, 'channel': 1, 'windchill': None}
> Dec 27 14:56:27 meteomontaos weewx[17954]: wmr300: raw packet: 
> {'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
> 'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
> Dec 27 14:56:27 meteomontaos weewx[17954]: wmr300: con

Re: [weewx-user] Re: rtl_433 and Weewxd config problems!!

[Charlie Thompson]

Thanks for the reply.  That *did* fix the error message...but still no data 
sharing between rtl_433 and weewxd.
Is anyone else out there successfully using rtl_433 with WeeWx?

Thanks,
-Charlie

> On Dec 26, 2018, at 11:49 PM, gjr80  wrote:
> 
> Hi,
> 
> Probably one for Matthew to look into, though I believe he has not had much 
> time lately for things weeWX. In any case it would appear the SDR driver is 
> not seeing an expected rain_counter value. You can work around the issue by 
> editing sdr.py and changing line 487 from: 
> 
>  if 'rain_counter' in pkt:
> 
> to
>  
> if 'rain_counter' in pkt and pkt['rain_counter'] is not None:
> 
> Save sdr.py and restart weeWX. Note that this will handle the case I pointed 
> out above though it could be an indicator there are other issues with your 
> station/SDR, I would keep a close eye on things to ensure that all is working 
> as it should.
> 
> Gary
> 
>> On Thursday, 27 December 2018 13:31:27 UTC+10, Charlie T wrote:
>> I'm trying to get rtl_433 and weewxd to communicate.  I'm receiving data OK 
>> from my Acurite 5n1 sensor.
>> The problem is I can't get the data into weewxd.  I've attached my 
>> weewx.conf file as well as the error message I'm getting.
>> I know this must be a "duh" problem but I can't figure it out!
>> 
>> Any help appreciated.
>> Thanks!
>> 
>> -Charlie
>> 
>> 
>> 
>> 
>> 
>> 
>> 
> 
> -- 
> 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: Looking to replace my old Acurite 0203C weather station

[Dj Merrill]

On 12/27/2018 2:44 AM, Scott Grayban wrote: 

I like this one http://a.co/d/1Lsy6fJ but it doesn't work with weewx. 



The Ambient Weather WS-2902A works fine with WeeWX, using the Interceptor 
driver and a Raspberry Pi 3B in my case. 

There seem to be a few ways to make this work.  I went with the RPi using 
the hard wired ethernet port attached to my local network, and setup the 
wireless on the RPi to act as an Access Point.  The WS-2902A connects to 
the RPis wireless network, and WeeWx with the Interceptor software runs on 
the Rpi. 

There seem to be other ways to make this work based on other posts on the 
mailing list, such as redirecting traffic from your wireless router to your 
WeeWx machine. 



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

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

[G Hammer]

The changes didn't break anything here when there are no alerts, and 
perhaps tomorrow morning I'll be able to see the alert in action.

Thanks

On Wednesday, December 26, 2018 at 7:53:57 PM UTC-5, Pat wrote:
>
> I've made more changes to this. Now you have to opt in for the alerts. 
> Erring on the side that alerts may not appeal or be available to everyone 
> in every region, it's opt-in. Simply add forecast_alert_enabled = 1 to 
> your skin options in weewx.conf. 
>
> The alert description has a default truncate at 75 characters. You can 
> override that with skin option forecast_alert_length
>
> Also non-MQTT sites now have alerts available to them. 
>
> Changes made to skin.conf, index.html.tmpl and user/bin/belchertown.py. 
> You can find the latest files in the repository and in the list of recent 
> commits . 
>
> Please test it out. 
>
> On Wednesday, December 26, 2018 at 4:09:00 PM UTC-5, Colin Larsen wrote:
>>
>> Does that mean that I'll see alerts even though I only use the Darksky 
>> current conditions? Did you pop in the option to disable the alerts?
>>
>> On Thu, 27 Dec 2018, 09:49 Pat >
>>> Sounds good! 
>>>
>>> I should add another disclaimer that the showing and hiding of the alert 
>>> bar automatically without reloading the website is only accomplished if you 
>>> have the MQTT feature enabled. 
>>>
>>> Which reminds me I need to add an option to show that bar if MQTT is 
>>> disabled. I'll have to make another update later today. 
>>>
>>> On Wednesday, December 26, 2018 at 1:45:49 PM UTC-5, rich T wrote:

 Thanks Pat...Downloaded and installed both files and restarted 
 weewx. No alerts in the area at this time; mostly likely some alerts 
 towards end of week when the icy weather comes through.  We'll keep you 
 informed.

 Rich

 On Wednesday, December 26, 2018 at 11:47:44 AM UTC-5, Pat wrote:

> Oops - forgot to hide the alert bar 
> 
>  when 
> an alert clears. Try this updated version attached. Same rules apply as 
> above. 
>
>
> On Wednesday, December 26, 2018 at 11:39:24 AM UTC-5, Pat wrote:
>>
>> I just committed an initial attempt 
>> .
>>  
>> You can download the files from GitHub or from the attachments here. 
>>
>> As usual, have a backup of your setup just in case. To test it out, 
>> copy the attached files to skins/Belchertown and restart weewx. Wait 
>> for an archive period and if you have a weather alert, it should appear 
>> like in the screenshot. Clicking the link will take you to the source of 
>> the alert. 
>>
>> The alert area should update automatically in the background (no page 
>> refresh needed). So if an alert goes active, it'll pop up the alert 
>> area. 
>> When it's gone it'll disappear. At least it should in theory :)
>>
>> Will need some testing and ironing out over the next few days for 
>> sure... Let me know how it goes. 
>>
>>
>>
>> On Wednesday, December 26, 2018 at 9:54:46 AM UTC-5, Pat wrote:
>>>
>>> Agreed. Let me work on a concept
>>>
>>> On Wednesday, December 26, 2018 at 9:47:56 AM UTC-5, rich T wrote:

 I think underneath the timestamp with the Icon would look fine.  
 Same text size as the timestamp but bold.  Maybe make the Alerts 
 optional 
 feature, so the users has a choice to display the Alerts.

 On Wednesday, December 26, 2018 at 9:29:16 AM UTC-5, Pat wrote:
>
> Ok cool. That GitHub repo just confirmed that I am doing what 
> they're doing. I'm not using JavaScript though, I'm just grabbing the 
> raw 
> JSON from DarkSky. I guess I've never seen the alerts array in my 
> output 
> when I initially created it, so out of sight out of mind?
>
> I just grabbed a forecast for an area in South Dakota that was 
> under weather advisory , 
> and I see in DarkSky's forecast it has the alert data. So I can use 
> this 
> sample data to include it in the skin. 
>
> Where and how should the alert be shown? I'd like to keep it in 
> line with the clean look of the skin. 
>
> I think I'll show the alert at the top of the page beneath the 
> timestamp. An alert icon (maybe something like this? 
> ) and a brief text of the 
> alert next to it. Then you can click the alert to see the full 
> details. 
>
>
>
>
> On Tuesday, December 25, 2018 at 9:57:56 PM UTC-5, rich T wrote:
>>>

[weewx-user] Re: problem with wind in WMR300

[Juan Antonio Mosquera]

ok sorry... my data portion




Dec 27 14:56:20 meteomontaos weewx[17954]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545918981, 'windDir': 206.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:22 meteomontaos weewx[17954]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545918983, 'windDir': 206.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:23 meteomontaos weewx[17954]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545918983, 'windDir': 206.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545918985, 'windDir': 206.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:25 meteomontaos weewx[17954]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545918986, 'windDir': 206.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
Dec 27 14:56:27 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:27 meteomontaos weewx[17954]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:27 meteomontaos weewx[17954]: wmr300: converted packet: 
{'windchill': None, 'dateTime': 1545918988, 'windDir': 206.0, 'windSpeed': 
0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 157.0}
Dec 27 14:56:28 meteomontaos weewx[17954]: wmr300: decode: d4 36 12 0c 1b 
0f 1f 01 00 00 00 9d 00 00 00 ce 03 a0 7f fd 12 0c 1b 00 00 00 00 00 eb 12 
0c 1a 12 2c 00 0b 00 8b 12 0c 1b 00 00 7f ff 00 00 00 00 00 7f ff 0a 61 00 
00 00 00 00 00 00 00 00 00 {'wind_gust': 0.0, 'ts': 1545921060.0, 
'wind_avg': 0.0, 'packet_type': 212, 'wind_dir': 206.0, 'wind_gust_dir': 
157.0, 'channel': 1, 'windchill': None}
Dec 27 14:56:28 meteomontaos weewx[17954]: wmr300: raw packet: 
{'wind_gust': 0.0, 'ts': 1545921060.0, 'wind_avg': 0.0, 'packet_type': 212, 
'wind_dir': 206.0, 'wind_gust_dir': 157.0, 'channel': 1, 'w

[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: problem with wind in WMR300

[Cameron D]

Not exactly - you have only enabled debug_packet.
You need to add the line debug_decode=1, which includes the data fairly 
directly from the USB buffer, with less processing in the driver.

If the decode also shows zero values for wind in the usb input buffer then 
your next step should be to plug in a windows PC and run the Oregon Weather 
OS software to see if it shows correct wind speeds.  This is clutching at 
straws now, but I suppose the console might possibly have a corrupted 
calibration factor in what it sends over the USB.

Cameron.

On Thursday, 27 December 2018 22:28:51 UTC+10, Juan Antonio Mosquera wrote:
>
> yes... in raw packets windSpeed is Zero... i dont understand... console 
> show wind speed.
>
> El jueves, 27 de diciembre de 2018, 13:16:51 (UTC+1), Andrew Milner 
> escribió:
>>
>> Have you done what Cameron suggested a few posts ago and set 
>> debug_decode = 1 and 
>> debug_packet = 1 
>> in the wmr300 section of weewx.conf?
>>
>>
>>

-- 
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: Looking to replace my old Acurite 0203C weather station

[Pat]

If you find an Ambient station that has the ObserverIP module, I believe 
it'll work with the weewx-interceptor driver. Do some research here on the 
group though to make sure you're making an informed decision. 

On Thursday, December 27, 2018 at 2:44:06 AM UTC-5, Scott Grayban wrote:
>
> I'm in the US I like Davis but those are super expensive.
>
> I like Ambient but haven't found any that I can buy that work with weeWX.
>
> I like this one http://a.co/d/1Lsy6fJ but it doesn't work with weewx.
>
> On Wednesday, December 26, 2018 at 6:58:55 AM UTC-8, Pat wrote:
>>
>> Not sure where you're located but check into some of the FineOffset 
>> stations. If you're in the US, AmbientWeather.com has some rebranded ones 
>> for their brand. I don't have one, so other's here who have a FineOffset 
>> station may be able to offer their feedback. 
>>
>> On Wednesday, December 26, 2018 at 2:27:02 AM UTC-5, Scott Grayban wrote:
>>>
>>> I want to update to something with a bit more information like solar, UV 
>>> and lightning detection and works with weeWX for around the $250 price. 
>>> Anyone have suggestions ?
>>>
>>

-- 
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: ignore_zero_wind = False --> doesn't work

[gjr80]

In my experience station/weeWX issues that disappear for no apparent reason 
are not actually fixed, rather some set of conditions/circumstances have 
transpired that mask the previously seen symptoms. 

The ignore_zero_wind setting is very simple in its operations. if set to 
True windDirection and windGustDir are forced to None if windSpeed and 
windGust are zero respectively. This is the default action. If windSpeed 
and windGust are None then windDir and windGustDir are untouched (note that 
None and zero are two different values). If ignore_zero_wind is set to 
False then windDir and windGustDir are untouched irrespective of windSpeed 
and windGust. 

At the end of the day there are a number of scenarios that could explain 
what you initially observed; it could be that weeWX received no windDir 
data and left untouched windDir displayed as N/A, there could be a 
peculiarity to how your station provides data or there could be some other 
issue. Without knowing the station type and seeing the loop and archive 
data from the driver/weeWX (and possibly digging further) it is impossible 
to narrow down the issue.

I guess we will wait and see if the issue presents itself again in the 
future.

Gary

On Thursday, 27 December 2018 20:46:55 UTC+10, Christian Nimmervoll wrote:
>
>
> No idea why. But now it works. :)
>
> Maybe it just needed time.
> THX for the help!
> Chris
>
>

-- 
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: Weather-Data in a LOG File (in one line)

[Andrew Milner]

no problem.  I think there are other threads in the forum connected to 
creating csv files.



On Thursday, 27 December 2018 14:52:18 UTC+2, Christian Nimmervoll wrote:
>
> Thank you - this will help. :)
> Sorry!!
> My english isn't so good but you helped me!
>
> The next time, i'll try to write clearer and better.
>
> Best regards,
> Chris
>
> The next time
>
> Am Donnerstag, 27. Dezember 2018 13:32:46 UTC+1 schrieb Andrew Milner:
>>
>> You are not being very helpful in describing what you need.
>> You say "all the weather data in one line".  Do you mean the contents of 
>> the whole database, the most recent loop record, the most recent archive 
>> record or something else entirely?
>> Wunderground submissions are not via a file of any kind.  WU submissions 
>> utilise the HTTP get protocol - restful service. I do not know but assume 
>> awekas is similar
>>
>> If you want weewx to create a text file every archive period then just 
>> create a template for the file contents and weewx will oblige.
>>
>> eg
>> if there is a a template called textdata.csv.tmpl
>>
>> add a report to the skin called textdata
>>
>> put the data you want inside the template using whatever tags you want, 
>> separated by whatever characters you want
>>
>> when the reports are created it will create a file called textdata.csv as 
>> specified in the template.
>>
>>
>>
>>
>> On Thursday, 27 December 2018 12:50:52 UTC+2, Christian Nimmervoll wrote:
>>>
>>>
>>> As a additional Info: Until now - i had "Virtual Weather Station" in use 
>>> and I got such a LOG file. This would be great, when there is also a 
>>> possibility with Weewx.
>>>
>>> Greetings,
>>> Chris
>>>
>>

-- 
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: problem with wind in WMR300

[Andrew Milner]

you need another wmr300 user to help you here I think.  Is it possible 
there is a wmr300 firmware update needed??



On Thursday, 27 December 2018 14:28:51 UTC+2, Juan Antonio Mosquera wrote:
>
> yes... in raw packets windSpeed is Zero... i dont understand... console 
> show wind speed.
>
> El jueves, 27 de diciembre de 2018, 13:16:51 (UTC+1), Andrew Milner 
> escribió:
>>
>> Have you done what Cameron suggested a few posts ago and set 
>> debug_decode = 1 and 
>> debug_packet = 1 
>> in the wmr300 section of weewx.conf?
>>
>>
>>
>> On Thursday, 27 December 2018 09:13:48 UTC+2, Juan Antonio Mosquera wrote:
>>>
>>> Yes, there are speed values in the console. This before changing the 
>>> template did not happen. I have activated the flag that you indicate to 
>>> have the address at least. What can happen so that weewx does not receive 
>>> those values? (I have rebooted the console).
>>>
>>> Greetings and thanks.
>>>
>>>
>>> El jueves, 27 de diciembre de 2018, 3:45:21 (UTC+1), Andrew Milner 
>>> escribió:

 From your logs it looks as though windspeed is not being received 
 although wind direction IS being received.

 It looks as though your anemometer which is reading windspeed is not 
 providing any output.

 Does your console show a windspeed??

 Weewx will ignore wind direction if windspeed is zero or null

 If you want to see wind direction when windspeed is zero or not 
 asvailable then you must set:
 [StdWXCalculate]
 ...
 ignore_zero_wind = False

 in weewx.conf

 and the wind direction will be preserved by weewx even when windspeed 
 is zero or not available.







 On Wednesday, 26 December 2018 18:34:35 UTC+2, Juan Antonio Mosquera 
 wrote:
>
> Better info...
>
>
> sudo journalctl -f | grep wind
> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: raw packet: 
> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
> 212, 
> 'wind_dir': 131.0, 'wind_gust_dir': 121.0, 'channel': 1, 'windchill': 
> None}
> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: converted packet: 
> {'windchill': None, 'dateTime': 1545842019, 'windDir': 131.0, 
> 'windSpeed': 
> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 121.0}
> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: raw packet: 
> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
> 212, 
> 'wind_dir': 131.0, 'wind_gust_dir': 135.0, 'channel': 1, 'windchill': 
> None}
> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: converted packet: 
> {'windchill': None, 'dateTime': 1545842020, 'windDir': 131.0, 
> 'windSpeed': 
> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 135.0}
> Dec 26 17:33:41 meteomontaos weewx[13518]: wmr300: raw packet: 
> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
> 212, 
> 'wind_dir': 131.0, 'wind_gust_dir': 135.0, 'channel': 1, 'windchill': 
> None}
> Dec 26 17:33:41 meteomontaos weewx[13518]: wmr300: converted packet: 
> {'windchill': None, 'dateTime': 1545842022, 'windDir': 131.0, 
> 'windSpeed': 
> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 135.0}
> Dec 26 17:33:42 meteomontaos weewx[13518]: wmr300: raw packet: 
> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
> 212, 
> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': 
> None}
> Dec 26 17:33:42 meteomontaos weewx[13518]: wmr300: converted packet: 
> {'windchill': None, 'dateTime': 1545842022, 'windDir': 131.0, 
> 'windSpeed': 
> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
> Dec 26 17:33:45 meteomontaos weewx[13518]: wmr300: raw packet: 
> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
> 212, 
> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': 
> None}
> Dec 26 17:33:45 meteomontaos weewx[13518]: wmr300: converted packet: 
> {'windchill': None, 'dateTime': 1545842025, 'windDir': 131.0, 
> 'windSpeed': 
> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
> Dec 26 17:33:47 meteomontaos weewx[13518]: wmr300: raw packet: 
> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
> 212, 
> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': 
> None}
> Dec 26 17:33:47 meteomontaos weewx[13518]: wmr300: converted packet: 
> {'windchill': None, 'dateTime': 1545842027, 'windDir': 131.0, 
> 'windSpeed': 
> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
> Dec 26 17:33:49 meteomontaos weewx[13518]: wmr300: raw packet: 
> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
> 212, 
> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': 
>>

[weewx-user] Re: Weather-Data in a LOG File (in one line)

[Christian Nimmervoll]

Thank you - this will help. :)
Sorry!!
My english isn't so good but you helped me!

The next time, i'll try to write clearer and better.

Best regards,
Chris

The next time

Am Donnerstag, 27. Dezember 2018 13:32:46 UTC+1 schrieb Andrew Milner:
>
> You are not being very helpful in describing what you need.
> You say "all the weather data in one line".  Do you mean the contents of 
> the whole database, the most recent loop record, the most recent archive 
> record or something else entirely?
> Wunderground submissions are not via a file of any kind.  WU submissions 
> utilise the HTTP get protocol - restful service. I do not know but assume 
> awekas is similar
>
> If you want weewx to create a text file every archive period then just 
> create a template for the file contents and weewx will oblige.
>
> eg
> if there is a a template called textdata.csv.tmpl
>
> add a report to the skin called textdata
>
> put the data you want inside the template using whatever tags you want, 
> separated by whatever characters you want
>
> when the reports are created it will create a file called textdata.csv as 
> specified in the template.
>
>
>
>
> On Thursday, 27 December 2018 12:50:52 UTC+2, Christian Nimmervoll wrote:
>>
>>
>> As a additional Info: Until now - i had "Virtual Weather Station" in use 
>> and I got such a LOG file. This would be great, when there is also a 
>> possibility with Weewx.
>>
>> Greetings,
>> Chris
>>
>

-- 
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: Weather-Data in a LOG File (in one line)

[Andrew Milner]

You are not being very helpful in describing what you need.
You say "all the weather data in one line".  Do you mean the contents of 
the whole database, the most recent loop record, the most recent archive 
record or something else entirely?
Wunderground submissions are not via a file of any kind.  WU submissions 
utilise the HTTP get protocol - restful service. I do not know but assume 
awekas is similar

If you want weewx to create a text file every archive period then just 
create a template for the file contents and weewx will oblige.

eg
if there is a a template called textdata.csv.tmpl

add a report to the skin called textdata

put the data you want inside the template using whatever tags you want, 
separated by whatever characters you want

when the reports are created it will create a file called textdata.csv as 
specified in the template.




On Thursday, 27 December 2018 12:50:52 UTC+2, Christian Nimmervoll wrote:
>
>
> As a additional Info: Until now - i had "Virtual Weather Station" in use 
> and I got such a LOG file. This would be great, when there is also a 
> possibility with Weewx.
>
> Greetings,
> Chris
>

-- 
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: problem with wind in WMR300

[Juan Antonio Mosquera]

yes... in raw packets windSpeed is Zero... i dont understand... console 
show wind speed.

El jueves, 27 de diciembre de 2018, 13:16:51 (UTC+1), Andrew Milner 
escribió:
>
> Have you done what Cameron suggested a few posts ago and set 
> debug_decode = 1 and 
> debug_packet = 1 
> in the wmr300 section of weewx.conf?
>
>
>
> On Thursday, 27 December 2018 09:13:48 UTC+2, Juan Antonio Mosquera wrote:
>>
>> Yes, there are speed values in the console. This before changing the 
>> template did not happen. I have activated the flag that you indicate to 
>> have the address at least. What can happen so that weewx does not receive 
>> those values? (I have rebooted the console).
>>
>> Greetings and thanks.
>>
>>
>> El jueves, 27 de diciembre de 2018, 3:45:21 (UTC+1), Andrew Milner 
>> escribió:
>>>
>>> From your logs it looks as though windspeed is not being received 
>>> although wind direction IS being received.
>>>
>>> It looks as though your anemometer which is reading windspeed is not 
>>> providing any output.
>>>
>>> Does your console show a windspeed??
>>>
>>> Weewx will ignore wind direction if windspeed is zero or null
>>>
>>> If you want to see wind direction when windspeed is zero or not 
>>> asvailable then you must set:
>>> [StdWXCalculate]
>>> ...
>>> ignore_zero_wind = False
>>>
>>> in weewx.conf
>>>
>>> and the wind direction will be preserved by weewx even when windspeed is 
>>> zero or not available.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Wednesday, 26 December 2018 18:34:35 UTC+2, Juan Antonio Mosquera 
>>> wrote:

 Better info...


 sudo journalctl -f | grep wind
 Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: raw packet: 
 {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
 212, 
 'wind_dir': 131.0, 'wind_gust_dir': 121.0, 'channel': 1, 'windchill': None}
 Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: converted packet: 
 {'windchill': None, 'dateTime': 1545842019, 'windDir': 131.0, 'windSpeed': 
 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 121.0}
 Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: raw packet: 
 {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
 212, 
 'wind_dir': 131.0, 'wind_gust_dir': 135.0, 'channel': 1, 'windchill': None}
 Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: converted packet: 
 {'windchill': None, 'dateTime': 1545842020, 'windDir': 131.0, 'windSpeed': 
 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 135.0}
 Dec 26 17:33:41 meteomontaos weewx[13518]: wmr300: raw packet: 
 {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
 212, 
 'wind_dir': 131.0, 'wind_gust_dir': 135.0, 'channel': 1, 'windchill': None}
 Dec 26 17:33:41 meteomontaos weewx[13518]: wmr300: converted packet: 
 {'windchill': None, 'dateTime': 1545842022, 'windDir': 131.0, 'windSpeed': 
 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 135.0}
 Dec 26 17:33:42 meteomontaos weewx[13518]: wmr300: raw packet: 
 {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
 212, 
 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
 Dec 26 17:33:42 meteomontaos weewx[13518]: wmr300: converted packet: 
 {'windchill': None, 'dateTime': 1545842022, 'windDir': 131.0, 'windSpeed': 
 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
 Dec 26 17:33:45 meteomontaos weewx[13518]: wmr300: raw packet: 
 {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
 212, 
 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
 Dec 26 17:33:45 meteomontaos weewx[13518]: wmr300: converted packet: 
 {'windchill': None, 'dateTime': 1545842025, 'windDir': 131.0, 'windSpeed': 
 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
 Dec 26 17:33:47 meteomontaos weewx[13518]: wmr300: raw packet: 
 {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
 212, 
 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
 Dec 26 17:33:47 meteomontaos weewx[13518]: wmr300: converted packet: 
 {'windchill': None, 'dateTime': 1545842027, 'windDir': 131.0, 'windSpeed': 
 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
 Dec 26 17:33:49 meteomontaos weewx[13518]: wmr300: raw packet: 
 {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
 212, 
 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
 Dec 26 17:33:49 meteomontaos weewx[13518]: wmr300: converted packet: 
 {'windchill': None, 'dateTime': 1545842029, 'windDir': 131.0, 'windSpeed': 
 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
 Dec 26 17:33:49 meteomontaos weewx[13518]: wmr300: raw packet: 
 {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 
 212, 
 'win

[weewx-user] Re: ignore_zero_wind = False --> doesn't work

[Juan Antonio Mosquera]

the problem was that the variable was not well located, now it works ok. 
Thanks and sorry.

El jueves, 27 de diciembre de 2018, 9:58:13 (UTC+1), Juan Antonio Mosquera 
escribió:
>
> Not work, me too.
>
> El jueves, 27 de diciembre de 2018, 9:53:38 (UTC+1), Christian Nimmervoll 
> escribió:
>>
>> Hi,
>>
>> I changed the "ignore_zero_wind" to False but this setting doesn't work.
>> I wanna see the Wind direction also, when the windspeed is zerro. Now i 
>> always see "N/A"
>>
>> In my config File - i have add it as listed below:
>>
>> #
>>
>> #   This section controls the origin of derived values.
>>
>> [StdWXCalculate]
>> 
>> *ignore_zero_wind = False*
>>
>> [[Calculations]]
>> # Derived quantities are calculated by this service. Possible 
>> values are:
>> #  hardware- use the value provided by hardware
>> #  software- use the value calculated by weewx
>> #  prefer_hardware - use value provide by hardware if available,
>> #  otherwise use value calculated by weewx
>> 
>> pressure = prefer_hardware
>> barometer = prefer_hardware
>> altimeter = prefer_hardware
>> windchill = prefer_hardware
>> heatindex = prefer_hardware
>> dewpoint = prefer_hardware
>> inDewpoint = prefer_hardware
>> rainRate = prefer_hardware
>>
>> #
>>
>>
>> What have i done wrong?
>> Thx,
>> Chris
>>
>>

-- 
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: problem with wind in WMR300

[Andrew Milner]

Have you done what Cameron suggested a few posts ago and set 
debug_decode = 1 and 
debug_packet = 1 
in the wmr300 section of weewx.conf?



On Thursday, 27 December 2018 09:13:48 UTC+2, Juan Antonio Mosquera wrote:
>
> Yes, there are speed values in the console. This before changing the 
> template did not happen. I have activated the flag that you indicate to 
> have the address at least. What can happen so that weewx does not receive 
> those values? (I have rebooted the console).
>
> Greetings and thanks.
>
>
> El jueves, 27 de diciembre de 2018, 3:45:21 (UTC+1), Andrew Milner 
> escribió:
>>
>> From your logs it looks as though windspeed is not being received 
>> although wind direction IS being received.
>>
>> It looks as though your anemometer which is reading windspeed is not 
>> providing any output.
>>
>> Does your console show a windspeed??
>>
>> Weewx will ignore wind direction if windspeed is zero or null
>>
>> If you want to see wind direction when windspeed is zero or not 
>> asvailable then you must set:
>> [StdWXCalculate]
>> ...
>> ignore_zero_wind = False
>>
>> in weewx.conf
>>
>> and the wind direction will be preserved by weewx even when windspeed is 
>> zero or not available.
>>
>>
>>
>>
>>
>>
>>
>> On Wednesday, 26 December 2018 18:34:35 UTC+2, Juan Antonio Mosquera 
>> wrote:
>>>
>>> Better info...
>>>
>>>
>>> sudo journalctl -f | grep wind
>>> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: raw packet: 
>>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>>> 'wind_dir': 131.0, 'wind_gust_dir': 121.0, 'channel': 1, 'windchill': None}
>>> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: converted packet: 
>>> {'windchill': None, 'dateTime': 1545842019, 'windDir': 131.0, 'windSpeed': 
>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 121.0}
>>> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: raw packet: 
>>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>>> 'wind_dir': 131.0, 'wind_gust_dir': 135.0, 'channel': 1, 'windchill': None}
>>> Dec 26 17:33:39 meteomontaos weewx[13518]: wmr300: converted packet: 
>>> {'windchill': None, 'dateTime': 1545842020, 'windDir': 131.0, 'windSpeed': 
>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 135.0}
>>> Dec 26 17:33:41 meteomontaos weewx[13518]: wmr300: raw packet: 
>>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>>> 'wind_dir': 131.0, 'wind_gust_dir': 135.0, 'channel': 1, 'windchill': None}
>>> Dec 26 17:33:41 meteomontaos weewx[13518]: wmr300: converted packet: 
>>> {'windchill': None, 'dateTime': 1545842022, 'windDir': 131.0, 'windSpeed': 
>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 135.0}
>>> Dec 26 17:33:42 meteomontaos weewx[13518]: wmr300: raw packet: 
>>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>>> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
>>> Dec 26 17:33:42 meteomontaos weewx[13518]: wmr300: converted packet: 
>>> {'windchill': None, 'dateTime': 1545842022, 'windDir': 131.0, 'windSpeed': 
>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
>>> Dec 26 17:33:45 meteomontaos weewx[13518]: wmr300: raw packet: 
>>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>>> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
>>> Dec 26 17:33:45 meteomontaos weewx[13518]: wmr300: converted packet: 
>>> {'windchill': None, 'dateTime': 1545842025, 'windDir': 131.0, 'windSpeed': 
>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
>>> Dec 26 17:33:47 meteomontaos weewx[13518]: wmr300: raw packet: 
>>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>>> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
>>> Dec 26 17:33:47 meteomontaos weewx[13518]: wmr300: converted packet: 
>>> {'windchill': None, 'dateTime': 1545842027, 'windDir': 131.0, 'windSpeed': 
>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
>>> Dec 26 17:33:49 meteomontaos weewx[13518]: wmr300: raw packet: 
>>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>>> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
>>> Dec 26 17:33:49 meteomontaos weewx[13518]: wmr300: converted packet: 
>>> {'windchill': None, 'dateTime': 1545842029, 'windDir': 131.0, 'windSpeed': 
>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
>>> Dec 26 17:33:49 meteomontaos weewx[13518]: wmr300: raw packet: 
>>> {'wind_gust': 0.0, 'ts': 1545844080.0, 'wind_avg': 0.0, 'packet_type': 212, 
>>> 'wind_dir': 131.0, 'wind_gust_dir': 137.0, 'channel': 1, 'windchill': None}
>>> Dec 26 17:33:49 meteomontaos weewx[13518]: wmr300: converted packet: 
>>> {'windchill': None, 'dateTime': 1545842030, 'windDir': 131.0, 'windSpeed': 
>>> 0.0, 'windGust': 0.0, 'usUnits': 17, 'windGustDir': 137.0}
>>> Dec 26 17:33:51 meteomontaos we

[weewx-user] Re: Weather-Data in a LOG File (in one line)

[Christian Nimmervoll]

As a additional Info: Until now - i had "Virtual Weather Station" in use 
and I got such a LOG file. This would be great, when there is also a 
possibility with Weewx.

Greetings,
Chris

-- 
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.
1.01,2018,12,27,11,49,0,0,2,263,43,97,75.0,37.5,30.4,32.1,0.0,0.0,4,0.0,0,0.0,0,0.0,0,0.0,0.0,105,37.5,75.2,44.2,36.7,0.000,0.9,0.9,-0.6,0.0,0.0,0.0,7.0,814.0

[weewx-user] Weather-Data in a LOG File (in one line)

[Christian Nimmervoll]

For further processing of data on my PHP website I need a log file with all 
Weather data in one line. I have not found a way to get this from Weewx. 
But I think the weather services like Wunderground or Awekas work exactly 
with such a file. Is there a way to get this file via FTP on my webserver? 
I haven't found help in the manual. Thanks for the help. Chris

-- 
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: ignore_zero_wind = False --> doesn't work

[Christian Nimmervoll]

No idea why. But now it works. :)

Maybe it just needed time.
THX for the help!
Chris

-- 
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: ignore_zero_wind = False --> doesn't work

[Christian Nimmervoll]

Hi;

Yes i've done a restart. (sudo /etc/init.d/weewx restart)

Here is the actually Output - now we have no wind and i can't see the 
direction of the (last) wind.
Please look at my attachment.


Am Donnerstag, 27. Dezember 2018 10:33:03 UTC+1 schrieb gjr80:
>
> Hi,
>
> It appears you have the setting correct. What makes you say it does not 
> work? What are you seeing/looking at? Did you restart weeWX after making 
> the change? Have you checkd the logs for errors - from startup? Did you run 
> weeWX directly (http://weewx.com/docs/usersguide.htm#Running_directly) 
> and observe the loop and archive records? If not I suggest you do that and 
> post the screen output here. Would probably be a good idea to post a copy 
> of weewx.conf (with passwords and other sensitive info removed) as well.
>
> 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] ignore_zero_wind = False --> doesn't work

[gjr80]

Hi,

It appears you have the setting correct. What makes you say it does not work? 
What are you seeing/looking at? Did you restart weeWX after making the change? 
Have you checkd the logs for errors - from startup? Did you run weeWX directly 
(http://weewx.com/docs/usersguide.htm#Running_directly) and observe the loop 
and archive records? If not I suggest you do that and post the screen output 
here. Would probably be a good idea to post a copy of weewx.conf (with 
passwords and other sensitive info removed) as well.

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: ignore_zero_wind = False --> doesn't work

[Juan Antonio Mosquera]

Not work, me too.

El jueves, 27 de diciembre de 2018, 9:53:38 (UTC+1), Christian Nimmervoll 
escribió:
>
> Hi,
>
> I changed the "ignore_zero_wind" to False but this setting doesn't work.
> I wanna see the Wind direction also, when the windspeed is zerro. Now i 
> always see "N/A"
>
> In my config File - i have add it as listed below:
>
> #
>
> #   This section controls the origin of derived values.
>
> [StdWXCalculate]
> 
> *ignore_zero_wind = False*
>
> [[Calculations]]
> # Derived quantities are calculated by this service. Possible 
> values are:
> #  hardware- use the value provided by hardware
> #  software- use the value calculated by weewx
> #  prefer_hardware - use value provide by hardware if available,
> #  otherwise use value calculated by weewx
> 
> pressure = prefer_hardware
> barometer = prefer_hardware
> altimeter = prefer_hardware
> windchill = prefer_hardware
> heatindex = prefer_hardware
> dewpoint = prefer_hardware
> inDewpoint = prefer_hardware
> rainRate = prefer_hardware
>
> #
>
>
> What have i done wrong?
> Thx,
> Chris
>
>

-- 
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] ignore_zero_wind = False --> doesn't work

[Christian Nimmervoll]

Hi,

I changed the "ignore_zero_wind" to False but this setting doesn't work.
I wanna see the Wind direction also, when the windspeed is zerro. Now i 
always see "N/A"

In my config File - i have add it as listed below:

#

#   This section controls the origin of derived values.

[StdWXCalculate]

*ignore_zero_wind = False*

[[Calculations]]
# Derived quantities are calculated by this service. Possible 
values are:
#  hardware- use the value provided by hardware
#  software- use the value calculated by weewx
#  prefer_hardware - use value provide by hardware if available,
#  otherwise use value calculated by weewx

pressure = prefer_hardware
barometer = prefer_hardware
altimeter = prefer_hardware
windchill = prefer_hardware
heatindex = prefer_hardware
dewpoint = prefer_hardware
inDewpoint = prefer_hardware
rainRate = prefer_hardware

#


What have i done wrong?
Thx,
Chris

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