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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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,

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

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

[weewx-user] Re: Belchertown DarkSky Alerts

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

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,

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

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

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

[weewx-user] Re: Belchertown DarkSky Alerts

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

[weewx-user] Re: Belchertown DarkSky Alerts

Pat If an area has multiple alerts, the skin only displays the first Alert. https://forecast.weather.gov/MapClick.php?site=tfx==_x=168_y=146=168=146#.XCVn1WaWy70 > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

# 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 :::*

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

[weewx-user] Re: Looking to replace my old Acurite 0203C weather station

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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,

[weewx-user] Re: Looking to replace my old Acurite 0203C weather station

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

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

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

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

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:

[weewx-user] Re: Belchertown Skin 0.8.1 released

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

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

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

[weewx-user] Re: Looking to replace my old Acurite 0203C weather station

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 >

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

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

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

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

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

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

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

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

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

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

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