[weewx-user] Belchertown mobile PWA resume websocket (iOS)
Hey Pat - any chance you could merge https://github.com/poblabs/weewx-belchertown/pull/251? -- Brice Ruth, FCD Software Engineer, Madison WI -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW4R%2B3XsbbaVuONEtR0PbKa9fNtzGdmyDvcKCpVg%3DgKaQw%40mail.gmail.com.
[weewx-user] thank you
Recently upgraded to weewx 4.1.0 via apt-get upgrade on my Pi 4, and just now to Belchertown v1.1 - restarted the daemon and waited for all the assets to regenerate and just wanted to say: THANK YOU Well done to everyone that puts in their time to pull this stuff together. Cheers, Brice Ruth, FCD Software Engineer, Madison WI -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW7Dcoz4LdOKXsNtO9evGbkQ%3DC1Bg96njBQuH4RV4CF8pA%40mail.gmail.com.
Re: [weewx-user] Let's Encrypt certificate
Also, no harm in just running certbot renew with --force-renewal. No guess work, you'll get a new cert that is guaranteed not affected. Brice Ruth, FCD Software Engineer, Madison WI On Tue, Mar 3, 2020 at 5:50 PM John Kline wrote: > *Q: How do I know if I’m using an affected certificate?* > *A:* Here is an online tool that will show you: > https://checkhost.unboundtest.com/ 1.8k > <https://checkhost.unboundtest.com/> > > Or, on a Linux/BSD-like system, this command will show you example.com's > current certificate serial number: > > openssl s_client -connect example.com:443 -servername example.com > -showcerts /dev/null | openssl x509 -text -noout | grep -A 1 > Serial\ Number | tr -d : > > You can see the list of all affected serial numbers at: > https://letsencrypt.org/caaproblem/ <https://letsencrypt.org/caaproblem/> > > On Mar 3, 2020, at 3:26 PM, rich T wrote: > > > FYI about Let's Encrypt Certificate > > https://www.wxforum.net/index.php?topic=38915.msg400193;topicseen#msg400193 > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/3ae15136-379b-43b2-9c0e-074d7c814c5f%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/3ae15136-379b-43b2-9c0e-074d7c814c5f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/5FB4D501-B3AB-4F30-B5D0-A28694418F3E%40johnkline.com > <https://groups.google.com/d/msgid/weewx-user/5FB4D501-B3AB-4F30-B5D0-A28694418F3E%40johnkline.com?utm_medium=email&utm_source=footer> > . > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW60X-E1VWWrjpvfYhG4DR9rhFG5FHcv4cFs_uXv_-468Q%40mail.gmail.com.
Re: [weewx-user] Re: Belchertown - PWA re-connect for Websocket
I pushed up a different approach - lemme know what you think. Brice Ruth, FCD Software Engineer, Madison WI On Mon, Feb 17, 2020 at 2:39 PM Brice Ruth wrote: > https://github.com/poblabs/weewx-belchertown/pull/251 - now on development > > Brice Ruth, FCD > Software Engineer, Madison WI > > > On Mon, Feb 17, 2020 at 2:26 PM Brice Ruth wrote: > >> Pushed https://github.com/poblabs/weewx-belchertown/pull/250 >> >> Brice Ruth, FCD >> Software Engineer, Madison WI >> >> >> On Mon, Feb 17, 2020 at 2:13 PM Brice Ruth wrote: >> >>> Roger that. >>> >>> Brice Ruth, FCD >>> Software Engineer, Madison WI >>> >>> >>> On Mon, Feb 17, 2020 at 2:05 PM Pat wrote: >>> >>>> PR's are welcome on the Belchertown skin! Please pull against the >>>> development branch and I'll check it out >>>> >>>> On Monday, February 17, 2020 at 2:54:18 PM UTC-5, Brice Ruth wrote: >>>>> >>>>> Good afternoon - >>>>> >>>>> I've noticed that, on the iPhone, when I launch my PWS site from the >>>>> homescreen, using the previously created icon (thank you!) - the websocket >>>>> doesn't "reconnect" if you switch away and go back after a while. Doing >>>>> some research, it seems that at some point, Apple modified homescreen >>>>> launched apps to "save state" - which ... doesn't re-execute any JS >>>>> automatically, seemingly. I did find a pattern to work around this here >>>>> https://stackoverflow.com/a/56944455 and I've locally applied this on >>>>> the version I'm running (I don't think I'm on the beta?). I basically did >>>>> a >>>>> minor refactor of the code that's tied to click/restart-interval, and used >>>>> that to tie to the visibilitychanged event that seems to get triggered. >>>>> >>>>> Limited testing seems to indicate that this works. Any concerns with >>>>> me pushing up a PR for this? Anything else I should be aware of? >>>>> >>>>> Thanks! >>>>> >>>>> Brice Ruth, FCD >>>>> Software Engineer, Madison WI >>>>> >>>> -- >>>> 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. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/weewx-user/54c9bfde-cefc-4073-b741-003726ca9d5f%40googlegroups.com >>>> <https://groups.google.com/d/msgid/weewx-user/54c9bfde-cefc-4073-b741-003726ca9d5f%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW6HOZ0aZpVXE%3Dz0qiQP84QP-nhNkmp%2BLhGgXau2FX%2Bf3A%40mail.gmail.com.
Re: [weewx-user] Re: Belchertown - PWA re-connect for Websocket
https://github.com/poblabs/weewx-belchertown/pull/251 - now on development Brice Ruth, FCD Software Engineer, Madison WI On Mon, Feb 17, 2020 at 2:26 PM Brice Ruth wrote: > Pushed https://github.com/poblabs/weewx-belchertown/pull/250 > > Brice Ruth, FCD > Software Engineer, Madison WI > > > On Mon, Feb 17, 2020 at 2:13 PM Brice Ruth wrote: > >> Roger that. >> >> Brice Ruth, FCD >> Software Engineer, Madison WI >> >> >> On Mon, Feb 17, 2020 at 2:05 PM Pat wrote: >> >>> PR's are welcome on the Belchertown skin! Please pull against the >>> development branch and I'll check it out >>> >>> On Monday, February 17, 2020 at 2:54:18 PM UTC-5, Brice Ruth wrote: >>>> >>>> Good afternoon - >>>> >>>> I've noticed that, on the iPhone, when I launch my PWS site from the >>>> homescreen, using the previously created icon (thank you!) - the websocket >>>> doesn't "reconnect" if you switch away and go back after a while. Doing >>>> some research, it seems that at some point, Apple modified homescreen >>>> launched apps to "save state" - which ... doesn't re-execute any JS >>>> automatically, seemingly. I did find a pattern to work around this here >>>> https://stackoverflow.com/a/56944455 and I've locally applied this on >>>> the version I'm running (I don't think I'm on the beta?). I basically did a >>>> minor refactor of the code that's tied to click/restart-interval, and used >>>> that to tie to the visibilitychanged event that seems to get triggered. >>>> >>>> Limited testing seems to indicate that this works. Any concerns with me >>>> pushing up a PR for this? Anything else I should be aware of? >>>> >>>> Thanks! >>>> >>>> Brice Ruth, FCD >>>> Software Engineer, Madison WI >>>> >>> -- >>> 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. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/54c9bfde-cefc-4073-b741-003726ca9d5f%40googlegroups.com >>> <https://groups.google.com/d/msgid/weewx-user/54c9bfde-cefc-4073-b741-003726ca9d5f%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW6LOvonJoKYSyF_ah8eYCoRUYE-Vabi5dSin7zB72XVjA%40mail.gmail.com.
Re: [weewx-user] Re: Belchertown - PWA re-connect for Websocket
Pushed https://github.com/poblabs/weewx-belchertown/pull/250 Brice Ruth, FCD Software Engineer, Madison WI On Mon, Feb 17, 2020 at 2:13 PM Brice Ruth wrote: > Roger that. > > Brice Ruth, FCD > Software Engineer, Madison WI > > > On Mon, Feb 17, 2020 at 2:05 PM Pat wrote: > >> PR's are welcome on the Belchertown skin! Please pull against the >> development branch and I'll check it out >> >> On Monday, February 17, 2020 at 2:54:18 PM UTC-5, Brice Ruth wrote: >>> >>> Good afternoon - >>> >>> I've noticed that, on the iPhone, when I launch my PWS site from the >>> homescreen, using the previously created icon (thank you!) - the websocket >>> doesn't "reconnect" if you switch away and go back after a while. Doing >>> some research, it seems that at some point, Apple modified homescreen >>> launched apps to "save state" - which ... doesn't re-execute any JS >>> automatically, seemingly. I did find a pattern to work around this here >>> https://stackoverflow.com/a/56944455 and I've locally applied this on >>> the version I'm running (I don't think I'm on the beta?). I basically did a >>> minor refactor of the code that's tied to click/restart-interval, and used >>> that to tie to the visibilitychanged event that seems to get triggered. >>> >>> Limited testing seems to indicate that this works. Any concerns with me >>> pushing up a PR for this? Anything else I should be aware of? >>> >>> Thanks! >>> >>> Brice Ruth, FCD >>> Software Engineer, Madison WI >>> >> -- >> 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. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/54c9bfde-cefc-4073-b741-003726ca9d5f%40googlegroups.com >> <https://groups.google.com/d/msgid/weewx-user/54c9bfde-cefc-4073-b741-003726ca9d5f%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW4gdeO4hofzZnoQnPT_8e7HO_tzsp9bBeDCjT5-ZT0QPA%40mail.gmail.com.
Re: [weewx-user] Re: Belchertown - PWA re-connect for Websocket
Roger that. Brice Ruth, FCD Software Engineer, Madison WI On Mon, Feb 17, 2020 at 2:05 PM Pat wrote: > PR's are welcome on the Belchertown skin! Please pull against the > development branch and I'll check it out > > On Monday, February 17, 2020 at 2:54:18 PM UTC-5, Brice Ruth wrote: >> >> Good afternoon - >> >> I've noticed that, on the iPhone, when I launch my PWS site from the >> homescreen, using the previously created icon (thank you!) - the websocket >> doesn't "reconnect" if you switch away and go back after a while. Doing >> some research, it seems that at some point, Apple modified homescreen >> launched apps to "save state" - which ... doesn't re-execute any JS >> automatically, seemingly. I did find a pattern to work around this here >> https://stackoverflow.com/a/56944455 and I've locally applied this on >> the version I'm running (I don't think I'm on the beta?). I basically did a >> minor refactor of the code that's tied to click/restart-interval, and used >> that to tie to the visibilitychanged event that seems to get triggered. >> >> Limited testing seems to indicate that this works. Any concerns with me >> pushing up a PR for this? Anything else I should be aware of? >> >> Thanks! >> >> Brice Ruth, FCD >> Software Engineer, Madison WI >> > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/54c9bfde-cefc-4073-b741-003726ca9d5f%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/54c9bfde-cefc-4073-b741-003726ca9d5f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW5_mPhTfSc-P0%2B7Eps-vCgcpDMX7PmK9Kn4S1TUP%3DbLjw%40mail.gmail.com.
[weewx-user] Belchertown - PWA re-connect for Websocket
Good afternoon - I've noticed that, on the iPhone, when I launch my PWS site from the homescreen, using the previously created icon (thank you!) - the websocket doesn't "reconnect" if you switch away and go back after a while. Doing some research, it seems that at some point, Apple modified homescreen launched apps to "save state" - which ... doesn't re-execute any JS automatically, seemingly. I did find a pattern to work around this here https://stackoverflow.com/a/56944455 and I've locally applied this on the version I'm running (I don't think I'm on the beta?). I basically did a minor refactor of the code that's tied to click/restart-interval, and used that to tie to the visibilitychanged event that seems to get triggered. Limited testing seems to indicate that this works. Any concerns with me pushing up a PR for this? Anything else I should be aware of? Thanks! Brice Ruth, FCD Software Engineer, Madison WI -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW7mekhNU9OB6hvh6fDB9aUjpzvhqL1J5ouyUApjpOFhPw%40mail.gmail.com.
Re: [weewx-user] Re: Belchertown skin works, MQTT not updating real time
quot;, "usUnits": "1.0", >> "windSpeed_mph": "23.5736", "windDir": "225.0", "outTemp_F": >> "48.44069175713479", "rainRate_inch_per_hour": "0.0", "pressure_inHg": >> "29.537724517082214", "inTemp_F": "48.44069175713479", "inHumidity": >> "40.10936680311917", "outHumidity": "40.10936680311917", "extraTemp1_F": >> "29.0", "altimeter_inHg": "30.025126837815904", "appTemp_F": >> "30.718254859246187", "barometer_inHg": "30.032273523343694", >> "beaufort_count": "5.0", "cloudbase_foot": "5707.996577917219", >> "dewpoint_F": "25.30550681429903", "heatindex_F": "48.44069175713479", >> "humidex_F": "48.4406917571348", "inDewpoint_F": "25.30550681429903", >> "maxSolarRad_Wpm2": "337.7856265409849", "windchill_F": >> "40.906702199301414", "hourRain_in": "0.02794", "rain24_in": >> "0.447040005", "dayRain_in": "0.167639998"} >> >> >> = >> from sudo tail -f /var/log/syslog (on 192.168.1.190) >> >> Feb 7 15:18:23 raspberrypi weewx[10773] INFO weewx.restx: MQTT: >> Published record 2020-02-07 15:18:00 CST (1581110280) >> Feb 7 15:18:24 raspberrypi weewx[10773] INFO weewx.cheetahgenerator: >> Generated 10 files for report Belchertown in 0.93 seconds >> Feb 7 15:18:24 raspberrypi weewx[10773] INFO weewx.reportengine: Copied >> 2 files to /var/www/html/weewx/belchertown >> Feb 7 15:18:28 raspberrypi weewx[10773] INFO weewx.restx: MQTT: >> Published record 2020-02-07 15:18:23 CST (1581110303) >> Feb 7 15:18:29 raspberrypi weewx[10773] INFO weeutil.rsyncupload: >> rsync'd 18 files (765,224 bytes) in 0.45 seconds >> Feb 7 15:18:34 raspberrypi weewx[10773] INFO weewx.restx: MQTT: >> Published record 2020-02-07 15:18:28 CST (1581110308) >> Feb 7 15:18:39 raspberrypi weewx[10773] INFO weewx.restx: MQTT: >> Published record 2020-02-07 15:18:33 CST (1581110313) >> Feb 7 15:18:44 raspberrypi weewx[10773] INFO weewx.restx: MQTT: >> Published record 2020-02-07 15:18:39 CST (1581110319) >> >> === >> from sudo netstat -tulpn | grep 1883 on 192.168.1.200: >> tcp0 0 0.0.0.0:18830.0.0.0:* >> LISTEN 567/mosquitto >> tcp6 0 0 :::1883 :::* >> LISTEN 567/mosquitto >> >> on 192.168.1.190: >> tcp0 0 0.0.0.0:18830.0.0.0:* >> LISTEN 589/mosquitto >> tcp6 0 0 :::1883 :::* >> LISTEN 589/mosquitto >> >> -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/3109ae06-895c-4432-b41e-3aaa4188b404%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/3109ae06-895c-4432-b41e-3aaa4188b404%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Brice Ruth, FCD Software Engineer, Madison WI -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW6EDMcun7q%3DyA4Hvr90kwUc7Y3W%3DwSKE87%3Df5TAJUnjNQ%40mail.gmail.com.
Re: [weewx-user] rtupdate.wunderground.com certificate error
Yeah, agreed. That was my take as well. I think there's ... other issues, too. Brice Ruth, FCD Software Engineer, Madison WI On Wed, Feb 5, 2020 at 6:06 PM 'Denny Page' via weewx-user < weewx-user@googlegroups.com> wrote: > There are a few people in that thread that are using Arduino, and > complaining about 404 errors. I believe that is what they were referring to > by “embedded device controllers" > > > > On Feb 5, 2020, at 15:53, Thomas Keffer wrote: > > Yeah, I thought that statement was a bit of a cop-out. > > They messed up, pure and simple. > > On Wed, Feb 5, 2020 at 3:51 PM J B wrote: > >> Thanks for the update. >> >> I'm not really sure what he means about embedded device >> controllers...most of us are running RaspberryPis that are sending data >> using Python. I'm pretty sure it can handle host names fine. >> >> On Wednesday, February 5, 2020 at 12:40:31 PM UTC-8, Dave McCreath wrote: >>> >>> Leon >>> >>> The text below was posted by Tim Roche (WU IT) on the WeatherUndergound >>> FaceBook page 17 hours ago: >>> >>> *Quick update: We have some answers for why many of the stations are not >>> sending data. It appears that many of the embedded device controllers don't >>> behave very well with host names, and are sending data to us in a way that >>> is not expected.* >>> >>> *We love that enthusiasts building cool stuff send data to Weather >>> Underground, so while we asses how to fix these issues, we have temporarily >>> rolled back to our legacy system.* >>> >>> *We will be testing over the next week to see how to fix these problems, >>> and will ask for help from some of you.* >>> >>> *I would like to personally apologize for this issue, we felt our >>> testing was robust, but obviously there were gaps. We're still working on a >>> plan and I will try to keep you updated here.* >>> >>> >>> Tim is a regular poster on the site and it's a good source of what's >>> going on. >>> >>> >>> I think the time coincides with everything correcting itself on your >>> system >>> >>> >>> Regards >>> >>> >>> Dave >>> >>> On Wednesday, 5 February 2020 16:42:53 UTC, Leon Shaner wrote: >>>> >>>> FWIW, I haven't seen any 404's since around these times from last night: >>>> >>>> Feb 4 20:43:52 Wunderground-RF: Failed upload attempt 1: HTTP Error >>>> 404: Not Found >>>> Feb 4 20:43:52 Wunderground-RF: Failed to publish record 2020-02-04 >>>> 20:43:53 EST (1580867033): Failed upload after 1 tries >>>> Feb 4 20:49:10 Wunderground-RF: Failed upload attempt 1: >>> error _ssl.c:1039: The handshake operation timed out> >>>> Feb 4 20:49:10 Wunderground-RF: Failed to publish record 2020-02-04 >>>> 20:48:49 EST (1580867329): Failed upload after 1 tries >>>> Feb 4 20:49:45 Wunderground-RF: Failed upload attempt 1: >>> error timed out> >>>> Feb 4 20:49:45 Wunderground-RF: Failed to publish record 2020-02-04 >>>> 20:49:15 EST (1580867355): Failed upload after 1 tries >>>> Feb 4 20:50:19 Wunderground-RF: Failed upload attempt 1: >>> error timed out> >>>> Feb 4 20:50:19 Wunderground-RF: Failed to publish record 2020-02-04 >>>> 20:49:49 EST (1580867389): Failed upload after 1 tries >>>> Feb 4 21:04:41 Wunderground-RF: Failed upload attempt 1: >>> error [Errno 104] Connection reset by peer> >>>> Feb 4 21:04:41 Wunderground-RF: Failed to publish record 2020-02-04 >>>> 21:04:41 EST (1580868281): Failed upload after 1 tries >>>> Feb 4 21:04:44 Wunderground-RF: Failed upload attempt 1: HTTP Error >>>> 404: Not Found >>>> >>>> >>>> Regards, >>>> \Leon >>>> -- >>>> Leon Shaner :: Dearborn, Michigan (iPad) >>>> >>>> >>>>> >> -- >> 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. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/b2f3448a-dc34-4fa6-a938-2264197c25af%40googlegroups.com >> <https://groups.google.com/d/msgid/weewx-user/b2f3448a-dc34-4fa6-a938
Re: [weewx-user] Re: Gravity AS3935 lightning detector
I think there's a problem with your library paths ... because it's not even getting to where it can determine what hardware you have. It can't load the program because it can't find the missing module, period. Brice Ruth, FCD Software Engineer, Madison WI On Thu, Feb 6, 2020 at 12:12 PM Giuseppe Saia wrote: > > > same mistake > no integration with 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/8c6fb56d-72f7-4e7a-bcc3-d370a0aa01d5%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/8c6fb56d-72f7-4e7a-bcc3-d370a0aa01d5%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW6Z%2BQ0mAyCaVt2zW8FLj_e1Tiyz-bRDXuvubMS7TXE1HQ%40mail.gmail.com.
Re: [weewx-user] Re: rtupdate.wunderground.com certificate error
Alrighty. Thanks for that! Brice Ruth, FCD Software Engineer, Madison WI On Wed, Feb 5, 2020 at 2:40 PM Dave McCreath wrote: > Leon > > The text below was posted by Tim Roche (WU IT) on the WeatherUndergound > FaceBook page 17 hours ago: > > *Quick update: We have some answers for why many of the stations are not > sending data. It appears that many of the embedded device controllers don't > behave very well with host names, and are sending data to us in a way that > is not expected.* > > *We love that enthusiasts building cool stuff send data to Weather > Underground, so while we asses how to fix these issues, we have temporarily > rolled back to our legacy system.* > > *We will be testing over the next week to see how to fix these problems, > and will ask for help from some of you.* > > *I would like to personally apologize for this issue, we felt our testing > was robust, but obviously there were gaps. We're still working on a plan > and I will try to keep you updated here.* > > > Tim is a regular poster on the site and it's a good source of what's going > on. > > > I think the time coincides with everything correcting itself on your system > > > Regards > > > Dave > > On Wednesday, 5 February 2020 16:42:53 UTC, Leon Shaner wrote: >> >> FWIW, I haven't seen any 404's since around these times from last night: >> >> Feb 4 20:43:52 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: >> Not Found >> Feb 4 20:43:52 Wunderground-RF: Failed to publish record 2020-02-04 >> 20:43:53 EST (1580867033): Failed upload after 1 tries >> Feb 4 20:49:10 Wunderground-RF: Failed upload attempt 1: > _ssl.c:1039: The handshake operation timed out> >> Feb 4 20:49:10 Wunderground-RF: Failed to publish record 2020-02-04 >> 20:48:49 EST (1580867329): Failed upload after 1 tries >> Feb 4 20:49:45 Wunderground-RF: Failed upload attempt 1: > timed out> >> Feb 4 20:49:45 Wunderground-RF: Failed to publish record 2020-02-04 >> 20:49:15 EST (1580867355): Failed upload after 1 tries >> Feb 4 20:50:19 Wunderground-RF: Failed upload attempt 1: > timed out> >> Feb 4 20:50:19 Wunderground-RF: Failed to publish record 2020-02-04 >> 20:49:49 EST (1580867389): Failed upload after 1 tries >> Feb 4 21:04:41 Wunderground-RF: Failed upload attempt 1: > [Errno 104] Connection reset by peer> >> Feb 4 21:04:41 Wunderground-RF: Failed to publish record 2020-02-04 >> 21:04:41 EST (1580868281): Failed upload after 1 tries >> Feb 4 21:04:44 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: >> Not Found >> >> >> Regards, >> \Leon >> -- >> Leon Shaner :: Dearborn, Michigan (iPad) >> >> >>> -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/77bd16db-0eed-4598-94ea-f7ca3a0dc945%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/77bd16db-0eed-4598-94ea-f7ca3a0dc945%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW5DN%2Bhx9DwuBTwG%2BG%2B2XetJNNou%2Ba5ROpFKakeu14jnvg%40mail.gmail.com.
Re: [weewx-user] Re: Belchertown - mqtt topic
Yeah, I think in the past nginx didn't have the built-in ability to do
this, but it was added at some point. Of course that means there's no
shortage of outdated info available via Google :)
Brice Ruth, FCD
Software Engineer, Madison WI
On Wed, Feb 5, 2020 at 1:08 PM Pat wrote:
> That's a new one for me. I'm doing a lot of proxying but never thought
> about this scenario. Pretty neat!
>
> On Wednesday, February 5, 2020 at 1:57:13 PM UTC-5, Brice Ruth wrote:
>>
>> Most excellent.
>>
>> Fwiw, I was moving from an existing setup using a different skin, that I
>> had exposed via nginx + SSL/TLS + LetsEncrypt ... once I had the basic
>> mosquitto server setup, I was able to proxy the requests for wss://*
>> through nginx w/o going through the additional hassle of securing mosquitto.
>>
>> location /mqtt {
>> proxy_pass http://localhost:9001/mqtt;
>> proxy_http_version 1.1;
>> proxy_set_header Upgrade $http_upgrade;
>> proxy_set_header Connection "upgrade";
>> proxy_read_timeout 86400;
>> }
>>
>> The "path" that you need to proxy through (i.e. "/mqtt) is also not super
>> obvious in any of the docs - I used the dev tools in Chrome to see where it
>> was trying to go and then was able to sort that.
>>
>> Keep up the great work!
>>
>> Brice Ruth, FCD
>> Software Engineer, Madison WI
>>
>>
>> On Wed, Feb 5, 2020 at 12:28 PM Pat wrote:
>>
>>> Thanks for the feedback, you're right it may not be totally clear. I'll
>>> get it updated in the readme
>>>
>>> On Wednesday, February 5, 2020 at 1:00:31 PM UTC-5, Brice Ruth wrote:
>>>>
>>>> Hey Pat - first off, fantastic skin. Also, fantastic documentation -
>>>> wowsa. Thank you for putting so much work into this.
>>>>
>>>> One small note - it isn't clear from all the docs that
>>>> `mqtt_websockets_topic` ought to end with `/loop` -- I used the defaults
>>>> pretty much everywhere, e.g. under [[MQTT]], topic = weather - but this
>>>> through me for a loop (pun intended). The websocket connects and all seems
>>>> honky dorey, but there's no data flowing through. Status in the header is
>>>> yellow with "connected, waiting for data" instead of what you get when it's
>>>> working.
>>>>
>>>> Anyhoo - thanks so much for all your work on this, absolutely
>>>> fantastic!!
>>>>
>>>> Cheers,
>>>>
>>>> Brice Ruth, FCD
>>>> Software Engineer, Madison WI
>>>>
>>> --
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/50b2ca69-db41-4f2c-b3e6-4fba7874b1b2%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/50b2ca69-db41-4f2c-b3e6-4fba7874b1b2%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/47bb5d53-70ad-455c-a914-1b5111c5b299%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/47bb5d53-70ad-455c-a914-1b5111c5b299%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/CAFbExW7RYSPbjXFsx4AFm_-iRBMEM0%2BOaWNG3j1-tubC9LKmMw%40mail.gmail.com.
Re: [weewx-user] Re: Gravity AS3935 lightning detector
Looking at the extension's source, you'll also need the GPIO module ... unless it's already installed as part of something else ... pip install RPi.GPIO from https://pypi.org/project/RPi.GPIO/ Brice Ruth, FCD Software Engineer, Madison WI On Wed, Feb 5, 2020 at 1:12 PM Brice Ruth wrote: > This doesn't seem to be documented, but based on your log output, I think > you need to install a Python module => > > pip install RPi_AS3935 > > from https://pypi.org/project/RPi_AS3935/ > > Brice Ruth, FCD > Software Engineer, Madison WI > > > On Wed, Feb 5, 2020 at 10:35 AM Giuseppe Saia wrote: > >> I also attach the error log file. I hope it will be useful to help me >> >> >> Feb 5 17:26:19 raspberrypi weewx[10352]: engine: Loading service >> user.as3935.AS3935 >> Feb 5 17:26:19 raspberrypi weewx[10352]: sdr: MainThread: shutdown >> process rtl_433 -M utc -F json -R 42 -R 12 >> Feb 5 17:26:19 raspberrypi weewx[10352]: sdr: MainThread: waiting for >> stdout-thread >> Feb 5 17:26:29 raspberrypi weewx[10352]: sdr: MainThread: timed out >> waiting for stdout-thread >> Feb 5 17:26:29 raspberrypi weewx[10352]: sdr: MainThread: waiting for >> stderr-thread >> Feb 5 17:26:39 raspberrypi weewx[10352]: sdr: MainThread: timed out >> waiting for stderr-thread >> Feb 5 17:26:39 raspberrypi weewx[10352]: sdr: MainThread: close stdout >> Feb 5 17:26:39 raspberrypi weewx[10352]: sdr: MainThread: close stderr >> Feb 5 17:26:39 raspberrypi weewx[10352]: engine: Caught unrecoverable >> exception in engine: >> Feb 5 17:26:39 raspberrypi weewx[10352]: No module named >> RPi_AS3935 >> Feb 5 17:26:39 raspberrypi weewx[10352]: Traceback (most >> recent call last): >> Feb 5 17:26:39 raspberrypi weewx[10352]: File >> "/home/weewx/bin/weewx/engine.py", line 888, in main >> Feb 5 17:26:39 raspberrypi weewx[10352]: engine = >> engine_class(config_dict) >> Feb 5 17:26:39 raspberrypi weewx[10352]: File >> "/home/weewx/bin/weewx/engine.py", line 78, in __init__ >> Feb 5 17:26:39 raspberrypi weewx[10352]: >> self.loadServices(config_dict) >> Feb 5 17:26:39 raspberrypi weewx[10352]: File >> "/home/weewx/bin/weewx/engine.py", line 142, in loadServices >> Feb 5 17:26:39 raspberrypi weewx[10352]: >> self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict)) >> Feb 5 17:26:39 raspberrypi weewx[10352]: File >> "/home/weewx/bin/weeutil/weeutil.py", line 1107, in _get_object >> Feb 5 17:26:39 raspberrypi weewx[10352]: mod = >> __import__(module) >> Feb 5 17:26:39 raspberrypi weewx[10352]: File >> "/home/weewx/bin/user/as3935.py", line 73, in >> Feb 5 17:26:39 raspberrypi weewx[10352]: from RPi_AS3935 >> import RPi_AS3935 >> Feb 5 17:26:39 raspberrypi weewx[10352]: ImportError: No >> module named RPi_AS3935 >> Feb 5 17:26:39 raspberrypi weewx[10352]: Exiting. >> >> >> -- >> 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. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/6899ccae-e507-47bd-a622-7127a57421e4%40googlegroups.com >> <https://groups.google.com/d/msgid/weewx-user/6899ccae-e507-47bd-a622-7127a57421e4%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW55SoDyUaboX4hB3SikyZ3csNdQnHHUrgU9y1sbZLZB4Q%40mail.gmail.com.
Re: [weewx-user] Re: Gravity AS3935 lightning detector
This doesn't seem to be documented, but based on your log output, I think you need to install a Python module => pip install RPi_AS3935 from https://pypi.org/project/RPi_AS3935/ Brice Ruth, FCD Software Engineer, Madison WI On Wed, Feb 5, 2020 at 10:35 AM Giuseppe Saia wrote: > I also attach the error log file. I hope it will be useful to help me > > > Feb 5 17:26:19 raspberrypi weewx[10352]: engine: Loading service > user.as3935.AS3935 > Feb 5 17:26:19 raspberrypi weewx[10352]: sdr: MainThread: shutdown > process rtl_433 -M utc -F json -R 42 -R 12 > Feb 5 17:26:19 raspberrypi weewx[10352]: sdr: MainThread: waiting for > stdout-thread > Feb 5 17:26:29 raspberrypi weewx[10352]: sdr: MainThread: timed out > waiting for stdout-thread > Feb 5 17:26:29 raspberrypi weewx[10352]: sdr: MainThread: waiting for > stderr-thread > Feb 5 17:26:39 raspberrypi weewx[10352]: sdr: MainThread: timed out > waiting for stderr-thread > Feb 5 17:26:39 raspberrypi weewx[10352]: sdr: MainThread: close stdout > Feb 5 17:26:39 raspberrypi weewx[10352]: sdr: MainThread: close stderr > Feb 5 17:26:39 raspberrypi weewx[10352]: engine: Caught unrecoverable > exception in engine: > Feb 5 17:26:39 raspberrypi weewx[10352]: No module named > RPi_AS3935 > Feb 5 17:26:39 raspberrypi weewx[10352]: Traceback (most recent > call last): > Feb 5 17:26:39 raspberrypi weewx[10352]: File > "/home/weewx/bin/weewx/engine.py", line 888, in main > Feb 5 17:26:39 raspberrypi weewx[10352]: engine = > engine_class(config_dict) > Feb 5 17:26:39 raspberrypi weewx[10352]: File > "/home/weewx/bin/weewx/engine.py", line 78, in __init__ > Feb 5 17:26:39 raspberrypi weewx[10352]: > self.loadServices(config_dict) > Feb 5 17:26:39 raspberrypi weewx[10352]: File > "/home/weewx/bin/weewx/engine.py", line 142, in loadServices > Feb 5 17:26:39 raspberrypi weewx[10352]: > self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict)) > Feb 5 17:26:39 raspberrypi weewx[10352]: File > "/home/weewx/bin/weeutil/weeutil.py", line 1107, in _get_object > Feb 5 17:26:39 raspberrypi weewx[10352]: mod = > __import__(module) > Feb 5 17:26:39 raspberrypi weewx[10352]: File > "/home/weewx/bin/user/as3935.py", line 73, in > Feb 5 17:26:39 raspberrypi weewx[10352]: from RPi_AS3935 > import RPi_AS3935 > Feb 5 17:26:39 raspberrypi weewx[10352]: ImportError: No module > named RPi_AS3935 > Feb 5 17:26:39 raspberrypi weewx[10352]: Exiting. > > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/6899ccae-e507-47bd-a622-7127a57421e4%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/6899ccae-e507-47bd-a622-7127a57421e4%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW6W6P5tKRyr9LSgYj8gmTYZToyrR4%2BSzhu0ZNb%3Dj_mnow%40mail.gmail.com.
Re: [weewx-user] Re: Belchertown - mqtt topic
Most excellent.
Fwiw, I was moving from an existing setup using a different skin, that I
had exposed via nginx + SSL/TLS + LetsEncrypt ... once I had the basic
mosquitto server setup, I was able to proxy the requests for wss://*
through nginx w/o going through the additional hassle of securing mosquitto.
location /mqtt {
proxy_pass http://localhost:9001/mqtt;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_read_timeout 86400;
}
The "path" that you need to proxy through (i.e. "/mqtt) is also not super
obvious in any of the docs - I used the dev tools in Chrome to see where it
was trying to go and then was able to sort that.
Keep up the great work!
Brice Ruth, FCD
Software Engineer, Madison WI
On Wed, Feb 5, 2020 at 12:28 PM Pat wrote:
> Thanks for the feedback, you're right it may not be totally clear. I'll
> get it updated in the readme
>
> On Wednesday, February 5, 2020 at 1:00:31 PM UTC-5, Brice Ruth wrote:
>>
>> Hey Pat - first off, fantastic skin. Also, fantastic documentation -
>> wowsa. Thank you for putting so much work into this.
>>
>> One small note - it isn't clear from all the docs that
>> `mqtt_websockets_topic` ought to end with `/loop` -- I used the defaults
>> pretty much everywhere, e.g. under [[MQTT]], topic = weather - but this
>> through me for a loop (pun intended). The websocket connects and all seems
>> honky dorey, but there's no data flowing through. Status in the header is
>> yellow with "connected, waiting for data" instead of what you get when it's
>> working.
>>
>> Anyhoo - thanks so much for all your work on this, absolutely fantastic!!
>>
>> Cheers,
>>
>> Brice Ruth, FCD
>> Software Engineer, Madison WI
>>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/50b2ca69-db41-4f2c-b3e6-4fba7874b1b2%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/50b2ca69-db41-4f2c-b3e6-4fba7874b1b2%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/CAFbExW6ejod%2BKazEz8yapz8-b574-%3DftLSMTNrdJ5jVV1dBDpQ%40mail.gmail.com.
[weewx-user] Belchertown - mqtt topic
Hey Pat - first off, fantastic skin. Also, fantastic documentation - wowsa. Thank you for putting so much work into this. One small note - it isn't clear from all the docs that `mqtt_websockets_topic` ought to end with `/loop` -- I used the defaults pretty much everywhere, e.g. under [[MQTT]], topic = weather - but this through me for a loop (pun intended). The websocket connects and all seems honky dorey, but there's no data flowing through. Status in the header is yellow with "connected, waiting for data" instead of what you get when it's working. Anyhoo - thanks so much for all your work on this, absolutely fantastic!! Cheers, Brice Ruth, FCD Software Engineer, Madison WI -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW6Fd3w2cGEZESv3011bHyDevsXMyN2Qe8k_mpV82FzVOg%40mail.gmail.com.
Re: [weewx-user] Re: rtupdate.wunderground.com certificate error
So, I'm a little stumped on why you're getting 404s unless you happen to be
hitting a region that's totally horked - where are you physically located?
I'm currently using 3.9.2-1 on my Pi 4 and I had temporarily disabled
`https`, but now have `https` re-enabled, but with the recent addition of
`/usr/bin/env PYTHONHTTPSVERIFY=0` to stop the weewx thread from failing
out after awhile. I've used rapidfire from the start and I don't see
anywhere that it's using the `weatherstation` URL - do you have
`archive_post` enabled as well, maybe? My errors were always indicating
failures in talking to `rtupdate...` as well, so I'm pretty sure on this
side, it hasn't been talking to anything but the rapidfire URL ... just not
sure why your setup seems to be doing that?
Brice Ruth, FCD
Software Engineer, Madison WI
On Mon, Feb 3, 2020 at 2:35 PM Leon Shaner wrote:
> Hey, WeeWx'ers.
>
> Even my workaround of setting pws_url to the value of the rf_url is still
> getting 404's, even if I explicitly set a Host header. :-(
>
> This is what I have tried... I guess WU is just a steaming pile as per
> usual. :-/
>
> Here is my attempted fix, which is part hack.
> The "fix" is adding the header. The "hack" is forcing the code to use
> the rtupdate URL (because I couldn't spot why the PWS URL was being used
> for RF).
>
> $ diff restx.py restx.py_getting404
> 100d99
> < from urllib.parse import urlparse
> 454,458c453
> < _parseduri = urlparse(url)
> < _parsedhost = '{uri.netloc}'.format(uri=_parseduri)
> < _request.add_header("Host", "%s" % _parsedhost)
> < #log.debug("%s: Added Header: 'Host: %s'"
> < # % (self.protocol_name, _parsedhost))
> ---
> > _request.add_header("User-Agent", "weewx/%s" % weewx.__version__)
> 610,611c605
> < #pws_url =
> "https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php";
> <https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php>
> < pws_url =
> "https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php";
> <https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php>
> ---
> > pws_url =
> "https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php";
> <https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php>
>
> Or in case your line numbers don't match mine (likely), here it is in
> context:
>
> ...
> # Python 2/3 compatiblity shims
> import six
> from six.moves import http_client
> from six.moves import queue
> from six.moves import urllib
> from urllib.parse import urlparse
>
> ...
>
> def get_request(self, url):
> """Get a request object. This can be overridden to add any special
> headers."""
> _request = urllib.request.Request(url)
> _parseduri = urlparse(url)
> _parsedhost = '{uri.netloc}'.format(uri=_parseduri)
> _request.add_header("Host", "%s" % _parsedhost)
> #log.debug("%s: Added Header: 'Host: %s'"
> # % (self.protocol_name, _parsedhost))
> _request.add_header("User-Agent", "weewx/%s" % weewx.__version__)
> return _request
>
>
> ...
>
> # the rapidfire URL:
> rf_url =
> "https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php";
> <https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php>
> # the personal weather station URL:
> #pws_url =
> "https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php";
> <https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php>
> pws_url =
> "https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php";
> <https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php>
>
>
>
>
> l...@isylum.org - Dearborn, Michigan
>
> On 2/3/20 2:43 PM, Leon Shaner wrote:
>
> Tom,
>
> Looking at the code, under the do_rapidfire_post, we clearly see it uses
> rf_url. In my debug output I referenced protocol_name and it's showing
> Wunderground-RF as the protocol, but the hostname is from pws_url.
> I have temporarily set pws_url to the rtupdate URL and my 404's have
> stopped.
> Looks like the rtupdate URL will take regular posts, but the
> weatherstation URL won't take rf p
Re: [weewx-user] Re: rtupdate.wunderground.com certificate error
header would be something like `Host: rtupdate.wunderground.com` ...
basically, whatever you're using as the hostname in the URL, needs to be
sent as the `Host` header ... that allows load-balancers to route the
request to the correct backend.
Brice Ruth, FCD
Software Engineer, Madison WI
On Mon, Feb 3, 2020 at 11:44 AM Leon Shaner wrote:
> Hey, WeeWx'ers,
>
> I am still getting 404 errors from the rtupdate URL site.
> There is a reply over here about it.
> I'm now looking into what the headers need to be.
> Does anyone know?
>
>
> https://apicommunity.wunderground.com/weatherapi/topics/is-the-rtupdate-wunderground-com-address-no-longer-valid
>
> For requests to route properly, the
> host header must be set correctly
> path must be correct
>
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad)
>
> On Feb 1, 2020, at 12:39 PM, Leon Shaner wrote:
>
> Hey, WeeWx'ers.
>
> I took a different approach to working around the WU certificate issue --
> keep SSL but don't verify the CERT. Scroll for that "solution."
>
> But meanwhile, using Wunderground-RF (rapid fire) I am getting an HTTP
> Error 404: Not Found.
> Any ideas on that? Did they change the URL, or is it just down?
>
> I noticed that even their own WunderStation App on iOS/iPadOS is subject
> to the certificate issue and reports all stations as "not reporting" --
> even ones that are, like mine, which I can verify via the WU website has
> the data and has reported within minutes ago.
>
> From the logs, re: RapidFire HTTP 404:
>
> Feb 1 12:31:51 nixie weewx[13184] DEBUG weewx.restx: Wunderground-RF:
> Failed upload attempt 1: HTTP Error 404: Not Found
> Feb 1 12:31:51 nixie weewx[13184] ERROR weewx.restx: Wunderground-RF:
> Failed to publish record 2020-02-01 12:31:51 EST (1580578311): Failed
> upload after 1 tries
> Feb 1 12:31:56 nixie weewx[13184] DEBUG weewx.restx: Wunderground-RF:
> Failed upload attempt 1: HTTP Error 404: Not Found
> Feb 1 12:31:56 nixie weewx[13184] ERROR weewx.restx: Wunderground-RF:
> Failed to publish record 2020-02-01 12:31:56 EST (1580578316): Failed
> upload after 1 tries
> Feb 1 12:32:04 nixie weewx[13184] DEBUG weewx.restx: Wunderground-RF:
> Failed upload attempt 1: HTTP Error 404: Not Found
> Feb 1 12:32:04 nixie weewx[13184] ERROR weewx.restx: Wunderground-RF:
> Failed to publish record 2020-02-01 12:32:04 EST (1580578324): Failed
> upload after 1 tries
> Feb 1 12:32:05 nixie weewx[13184] DEBUG weewx.restx: Wunderground-RF:
> Failed upload attempt 1: HTTP Error 404: Not Found
> Feb 1 12:32:05 nixie weewx[13184] ERROR weewx.restx: Wunderground-RF:
> Failed to publish record 2020-02-01 12:32:05 EST (1580578325): Failed
> upload after 1 tries
> Feb 1 12:32:06 nixie weewx[13184] DEBUG weewx.restx: Wunderground-RF:
> Failed upload attempt 1: HTTP Error 404: Not Found
> Feb 1 12:32:06 nixie weewx[13184] ERROR weewx.restx: Wunderground-RF:
> Failed to publish record 2020-02-01 12:32:05 EST (1580578325): Failed
> upload after 1 tries
>
>
> Here is the diff for my SSL CERT workaround:
>
> $ diff restx.py restx.py.20200201.1
> 110,115d109
> < # SSL certificate hack
> < global WUssl
> < WUssl = ssl.create_default_context();
> < WUssl.check_hostname=False
> < WUssl.verify_mode=ssl.CERT_NONE
> <
> 454d447
> < _request.add_header("User-Agent", "weewx/%s" % weewx.__version__)
> 543,544c536
> < #_response = urllib.request.urlopen(request, data=data_bytes,
> timeout=self.timeout)
> < _response = urllib.request.urlopen(request, data=data_bytes,
> timeout=self.timeout, context=WUssl)
> ---
> > _response = urllib.request.urlopen(request, data=data_bytes,
> timeout=self.timeout)
> 1051,1052c1043
> < #_response = urllib.request.urlopen(request,
> timeout=self.timeout)
> < _response = urllib.request.urlopen(request,
> timeout=self.timeout, context=WUssl)
> ---
> > _response = urllib.request.urlopen(request,
> timeout=self.timeout)
>
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad)
>
> On Jan 31, 2020, at 4:16 PM, Thomas Keffer wrote:
>
>
> Travis: what is the error? If it's a certificate error, Version 4 will do
> a retry after an hour. Unfortunately, Version 3 does not.
>
> On Fri, Jan 31, 2020 at 1:04 PM Travis Bully wrote:
>
>> Not here yet. It'll work for awhile and then will get the random cert
>> error I sent earlier. A restart of weewx will get it going again. I wish
>> restx would just try again after xx seconds.
>>
>>
>>
>> On Frid
Re: [weewx-user] Re: rtupdate.wunderground.com certificate error
Thanks for this JB - to you or anyone else following the community threads - has anyone from WU piped in to say they're re-engaged to fix the remaining issues? I haven't seen any posts from them recently ... Brice Ruth, FCD Software Engineer, Madison WI On Sun, Feb 2, 2020 at 11:14 PM J B wrote: > Like some of you I'm still getting intermittent errors that stop weewx > 3.9.2 from uploading until I restart. Someone over at > https://apicommunity.wunderground.com/ posted this creative > workaround that seems to be working so far. It lowers the security of > python but it's better than sending everything over http. > > tmarschner > <https://apicommunity.wunderground.com/weatherapi/people/tmarschner> > >- 2 Posts >- 0 Reply Likes > > Hi there, > > Here's an alternative workaround that doesn't require you to send your > Wunderground credentials in clear text. It turns off certificate validation > for python. I've tested this on weewx 3.9.2 on a Raspberry Pi (v. 9 > Stretch) running python 2.7.13. > > Modify the weewx startup script /etc/init.d/weewx. > > Find the start-stop-daemon line that starts up weewx (the do_start > routine) and insert "/usr/bin/env PYTHONHTTPSVERIFY=0" into the --exec > parameter as shown below: > > start-stop-daemon --start --chuid $WEEWX_USER --pidfile $PIDFILE --exec > /usr/bin/env PYTHONHTTPSVERIFY=0 $DAEMON -- $DAEMON_ARGS || return 2 > > Cheers, > Tom > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/98106b14-546a-481b-a49c-c8cf3ec19d7c%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/98106b14-546a-481b-a49c-c8cf3ec19d7c%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW5HWGZfx4j5JnrW6p7iw-ghqJLOMV1cN96_tv-krZSq9Q%40mail.gmail.com.
Re: [weewx-user] Re: rtupdate.wunderground.com certificate error
on the *Pi Stupid auto correct On Sun, Feb 2, 2020 at 9:42 PM Brice Ruth wrote: > So, is there a way to get 4.x on the you? Guessing I need to grab the > source if it’s not published yet? > > On Sun, Feb 2, 2020 at 2:53 PM Brice Ruth wrote: > >> I wonder if they forgot to update one... >> >> On Sat, Feb 1, 2020 at 9:57 PM Cameron D >> wrote: >> >>> I am seeing the occasional error in the logs, but running v4 beta 10 and >>> it keeps running and succeeds each time after the error. >>> Errors have been: >>> >>>- self-signed cert (3 times) >>>- cert for wrong hostname (using base server name instead of >>>wunderground's cname) (twice) >>>- connection closed prematurely. (twice) >>> >>> It looks to me as if they are fiddling around with their servers. The >>> server DNS provides 3 IPv4 addrs so maybe we occasionally pick one they are >>> working on and they didn't give enough time for DNS changes to filter >>> through. >>> >>> >>> On Sunday, 2 February 2020 10:12:08 UTC+10, Brice Ruth wrote: >>>> >>>> Is anyone else still seeing errors? It works for a bit, then fails >>>> enough for weewx to fail out and I have to restart... >>>> >>>> >>>> -- >>> 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. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/321a1732-f7bd-4588-bc39-67e8440d80fd%40googlegroups.com >>> <https://groups.google.com/d/msgid/weewx-user/321a1732-f7bd-4588-bc39-67e8440d80fd%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> Brice Ruth, FCD >> Software Engineer, Madison WI >> > -- > Brice Ruth, FCD > Software Engineer, Madison WI > -- Brice Ruth, FCD Software Engineer, Madison WI -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW7_AXbUQ3pQ%3DFCH88so2VVUr0Zq-vZLh0kBnitbAKioSQ%40mail.gmail.com.
Re: [weewx-user] Re: rtupdate.wunderground.com certificate error
So, is there a way to get 4.x on the you? Guessing I need to grab the source if it’s not published yet? On Sun, Feb 2, 2020 at 2:53 PM Brice Ruth wrote: > I wonder if they forgot to update one... > > On Sat, Feb 1, 2020 at 9:57 PM Cameron D wrote: > >> I am seeing the occasional error in the logs, but running v4 beta 10 and >> it keeps running and succeeds each time after the error. >> Errors have been: >> >>- self-signed cert (3 times) >>- cert for wrong hostname (using base server name instead of >>wunderground's cname) (twice) >>- connection closed prematurely. (twice) >> >> It looks to me as if they are fiddling around with their servers. The >> server DNS provides 3 IPv4 addrs so maybe we occasionally pick one they are >> working on and they didn't give enough time for DNS changes to filter >> through. >> >> >> On Sunday, 2 February 2020 10:12:08 UTC+10, Brice Ruth wrote: >>> >>> Is anyone else still seeing errors? It works for a bit, then fails >>> enough for weewx to fail out and I have to restart... >>> >>> >>> -- >> 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. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/321a1732-f7bd-4588-bc39-67e8440d80fd%40googlegroups.com >> <https://groups.google.com/d/msgid/weewx-user/321a1732-f7bd-4588-bc39-67e8440d80fd%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > Brice Ruth, FCD > Software Engineer, Madison WI > -- Brice Ruth, FCD Software Engineer, Madison WI -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW6d3cWOP%2BsRScEUWd0q3a2Ah-TYWoRNa%3DWC-1h84RFDPQ%40mail.gmail.com.
Re: [weewx-user] Re: rtupdate.wunderground.com certificate error
I wonder if they forgot to update one... On Sat, Feb 1, 2020 at 9:57 PM Cameron D wrote: > I am seeing the occasional error in the logs, but running v4 beta 10 and > it keeps running and succeeds each time after the error. > Errors have been: > >- self-signed cert (3 times) >- cert for wrong hostname (using base server name instead of >wunderground's cname) (twice) >- connection closed prematurely. (twice) > > It looks to me as if they are fiddling around with their servers. The > server DNS provides 3 IPv4 addrs so maybe we occasionally pick one they are > working on and they didn't give enough time for DNS changes to filter > through. > > > On Sunday, 2 February 2020 10:12:08 UTC+10, Brice Ruth wrote: >> >> Is anyone else still seeing errors? It works for a bit, then fails enough >> for weewx to fail out and I have to restart... >> >> >> -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/321a1732-f7bd-4588-bc39-67e8440d80fd%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/321a1732-f7bd-4588-bc39-67e8440d80fd%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Brice Ruth, FCD Software Engineer, Madison WI -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW4Z-UtGxhyFDtW%2BL710zz4ks3iPydzUiazz74WuRvVV%2Bg%40mail.gmail.com.
Re: [weewx-user] Re: rtupdate.wunderground.com certificate error
I have 3.9.2-1 (latest available on my Pi 4).
On Sat, Feb 1, 2020 at 6:11 PM Brice Ruth wrote:
> Is anyone else still seeing errors? It works for a bit, then fails enough
> for weewx to fail out and I have to restart...
>
> On Sat, Feb 1, 2020 at 5:43 PM John wrote:
>
>> This edit to wunderfixer beta worked for me. I had about a week of
>> missing data and was having trouble catching up.
>>
>>
>>
>> On Saturday, February 1, 2020 at 1:16:47 PM UTC-6, Leon Shaner wrote:
>>>
>>> Hey, Tom,
>>>
>>> The reason I get 204 back from wunderfixer on date 2020-01-30 is I
>>> really did have 0 records uploaded to WU (due to a full day of certificate
>>> issues).
>>> Under the new API an HTTP 204 is returned for a valid request for which
>>> there is no data.
>>>
>>> Here is my workaround:
>>>
>>> $ diff wunderfixer wunderfixer_tk
>>> 407,409c407
>>> < # Valid response, it's just that WU has no records for
>>> the requested date
>>> < # Return an empty list of TimeStamps (as in WU has no
>>> records)
>>> < return {}
>>> ---
>>> > raise IOError("Probably a bad station ID or invalid
>>> date")
>>>
>>> Or if the line numbers don't match yours, it looks like this in context:
>>>
>>> if hasattr(response, 'code') and response.code != 200:
>>> if response.code == 204:
>>> # Valid response, it's just that WU has no records for
>>> the requested date
>>> # Return an empty list of TimeStamps (as in WU has no
>>> records)
>>> return {}
>>> else:
>>> raise IOError("Bad response code returned: %d" %
>>> response.code)
>>>
>>>
>>> Regards,
>>> \Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPad)
>>>
>>
>>> On Feb 1, 2020, at 12:40 PM, Leon Shaner wrote:
>>>
>>> Hey, WeeWx'ers.
>>>
>>> I took a different approach to working around the WU certificate issue
>>> -- keep SSL but don't verify the CERT. Scroll for that "solution."
>>>
>>> But meanwhile, using Wunderground-RF (rapid fire) I am getting an HTTP
>>> Error 404: Not Found.
>>> Any ideas on that? Did they change the URL, or is it just down?
>>>
>>> I noticed that even their own WunderStation App on iOS/iPadOS is subject
>>> to the certificate issue and reports all stations as "not reporting" --
>>> even ones that are, like mine, which I can verify via the WU website has
>>> the data and has reported within minutes ago.
>>>
>>> From the logs, re: RapidFire HTTP 404:
>>>
>>> Feb 1 12:31:51 nixie weewx[13184] DEBUG weewx.restx: Wunderground-RF:
>>> Failed upload attempt 1: HTTP Error 404: Not Found
>>> Feb 1 12:31:51 nixie weewx[13184] ERROR weewx.restx: Wunderground-RF:
>>> Failed to publish record 2020-02-01 12:31:51 EST (1580578311): Failed
>>> upload after 1 tries
>>> Feb 1 12:31:56 nixie weewx[13184] DEBUG weewx.restx: Wunderground-RF:
>>> Failed upload attempt 1: HTTP Error 404: Not Found
>>> Feb 1 12:31:56 nixie weewx[13184] ERROR weewx.restx: Wunderground-RF:
>>> Failed to publish record 2020-02-01 12:31:56 EST (1580578316): Failed
>>> upload after 1 tries
>>> Feb 1 12:32:04 nixie weewx[13184] DEBUG weewx.restx: Wunderground-RF:
>>> Failed upload attempt 1: HTTP Error 404: Not Found
>>> Feb 1 12:32:04 nixie weewx[13184] ERROR weewx.restx: Wunderground-RF:
>>> Failed to publish record 2020-02-01 12:32:04 EST (1580578324): Failed
>>> upload after 1 tries
>>> Feb 1 12:32:05 nixie weewx[13184] DEBUG weewx.restx: Wunderground-RF:
>>> Failed upload attempt 1: HTTP Error 404: Not Found
>>> Feb 1 12:32:05 nixie weewx[13184] ERROR weewx.restx: Wunderground-RF:
>>> Failed to publish record 2020-02-01 12:32:05 EST (1580578325): Failed
>>> upload after 1 tries
>>> Feb 1 12:32:06 nixie weewx[13184] DEBUG weewx.restx: Wunderground-RF:
>>> Failed upload attempt 1: HTTP Error 404: Not Found
>>> Feb 1 12:32:06 nixie weewx[13184] ERROR weewx.restx: Wunderground-RF:
>>> Failed to publish record 2020-02-01 12:32:05 EST (1580578325): Failed
>>> upload after 1 tries
>>>
>>>
>>
Re: [weewx-user] Re: rtupdate.wunderground.com certificate error
lib.request.urlopen(request, data=data_bytes, >> timeout=self.timeout) >> < _response = urllib.request.urlopen(request, data=data_bytes, >> timeout=self.timeout, context=WUssl) >> --- >> > _response = urllib.request.urlopen(request, data=data_bytes, >> timeout=self.timeout) >> 1051,1052c1043 >> < #_response = urllib.request.urlopen(request, >> timeout=self.timeout) >> < _response = urllib.request.urlopen(request, >> timeout=self.timeout, context=WUssl) >> --- >> > _response = urllib.request.urlopen(request, >> timeout=self.timeout) >> >> >> Regards, >> \Leon >> -- >> Leon Shaner :: Dearborn, Michigan (iPad) >> >> >> On Jan 31, 2020, at 4:16 PM, Thomas Keffer wrote: >> >> Travis: what is the error? If it's a certificate error, Version 4 will do >> a retry after an hour. Unfortunately, Version 3 does not. >> >> On Fri, Jan 31, 2020 at 1:04 PM Travis Bully wrote: >> >> Not here yet. It'll work for awhile and then will get the random cert >>> error I sent earlier. A restart of weewx will get it going again. I wish >>> restx would just try again after xx seconds. >>> >>> >>> >>> On Friday, January 31, 2020 at 2:48:50 PM UTC-5, J B wrote: >>>> >>>> Working here too. I had to restart Weewx. >>>> >>>> On Friday, January 31, 2020 at 11:34:19 AM UTC-8, Brice Ruth wrote: >>>>> >>>>> Looking like it's working to me, too. >>>>> >>>>> Brice Ruth, FCD >>>>> Software Engineer, Madison WI >>>>> >>>>> >>>>> On Fri, Jan 31, 2020 at 1:31 PM Travis Bully wrote: >>>>> >>>>>> Agreed. Seems like I still get one cert error every now and then. >>>>>> Likely still propagating changes through their infrastructure? >>>>>> >>>>>> Jan 31 14:29:25 homeauto03 weewx[3784]: restx: Wunderground-RF: >>>>>> Published record 2020-01-31 14:29:24 EST (1580498964) >>>>>> Jan 31 14:29:26 homeauto03 weewx[3784]: restx: Wunderground-RF: >>>>>> Failed upload attempt 1: >>>>> certificate verify failed (_ssl.c:727)> >>>>>> Jan 31 14:29:31 homeauto03 weewx[3784]: restx: Wunderground-RF: >>>>>> Failed to publish record 2020-01-31 14:29:26 EST (1580498966): Failed >>>>>> upload after 1 tries >>>>>> Jan 31 14:29:31 homeauto03 weewx[3784]: restx: Wunderground-RF: >>>>>> Published record 2020-01-31 14:29:30 EST (1580498970) >>>>>> >>>>>> On Fri, Jan 31, 2020 at 2:30 PM Denny Page wrote: >>>>>> >>>>>>> It's fixed now. >>>>>>> >>>>>>> >>>>>>> On Friday, January 31, 2020 at 8:54:02 AM UTC-8, Denny Page wrote: >>>>>>>> >>>>>>>> Wunderground just posted a note about the intermediate certificate >>>>>>>> issue. Hopefully they will fix it shortly. >>>>>>>> >>>>>>> -- >>>>>>> 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/mYhw6CSKHHg/unsubscribe >>>>>>> . >>>>>>> To unsubscribe from this group and all its topics, send an email to >>>>>>> weewx...@googlegroups.com. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/weewx-user/f5e5741a-e5f8-419b-9c0d-df1972fe5ced%40googlegroups.com >>>>>>> <https://groups.google.com/d/msgid/weewx-user/f5e5741a-e5f8-419b-9c0d-df1972fe5ced%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>> . >>>>>>> >>>>>> -- >>>>>> 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...@googlegroups.com. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/weewx-user/CAF_%2Bh5
Re: [weewx-user] Re: rtupdate.wunderground.com certificate error
Looking like it's working to me, too. Brice Ruth, FCD Software Engineer, Madison WI On Fri, Jan 31, 2020 at 1:31 PM Travis Bully wrote: > Agreed. Seems like I still get one cert error every now and then. Likely > still propagating changes through their infrastructure? > > Jan 31 14:29:25 homeauto03 weewx[3784]: restx: Wunderground-RF: Published > record 2020-01-31 14:29:24 EST (1580498964) > Jan 31 14:29:26 homeauto03 weewx[3784]: restx: Wunderground-RF: Failed > upload attempt 1: certificate verify failed (_ssl.c:727)> > Jan 31 14:29:31 homeauto03 weewx[3784]: restx: Wunderground-RF: Failed to > publish record 2020-01-31 14:29:26 EST (1580498966): Failed upload after 1 > tries > Jan 31 14:29:31 homeauto03 weewx[3784]: restx: Wunderground-RF: Published > record 2020-01-31 14:29:30 EST (1580498970) > > On Fri, Jan 31, 2020 at 2:30 PM Denny Page wrote: > >> It's fixed now. >> >> >> On Friday, January 31, 2020 at 8:54:02 AM UTC-8, Denny Page wrote: >>> >>> Wunderground just posted a note about the intermediate certificate >>> issue. Hopefully they will fix it shortly. >>> >> -- >> 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/mYhw6CSKHHg/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> weewx-user+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/f5e5741a-e5f8-419b-9c0d-df1972fe5ced%40googlegroups.com >> <https://groups.google.com/d/msgid/weewx-user/f5e5741a-e5f8-419b-9c0d-df1972fe5ced%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/CAF_%2Bh57S88%3DZOX1mXK8oZBx-_KEHvDPFP%3Dvtd4u3_1qg7994yg%40mail.gmail.com > <https://groups.google.com/d/msgid/weewx-user/CAF_%2Bh57S88%3DZOX1mXK8oZBx-_KEHvDPFP%3Dvtd4u3_1qg7994yg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW44GxViRDJA1JA6YeiREd-kACvhhD6706r_Ovqh0meJqQ%40mail.gmail.com.
Re: [weewx-user] Re: rtupdate.wunderground.com certificate error
Yeah, that's not a bad way to fix the problem, honestly. Better than sending credentials over cleartext, I just hate messing with cacerts stores that the system manages. Pain and suffering often follow :( Brice Ruth, FCD Software Engineer, Madison WI On Fri, Jan 31, 2020 at 11:13 AM Travis Bully wrote: > For what it's worth, I just updated my keystore with their "bad" digicert > intermediate to fix my issue. I've attached the cert here if you need it. > > > > On Friday, January 31, 2020 at 11:54:02 AM UTC-5, Denny Page wrote: >> >> Wunderground just posted a note about the intermediate certificate issue. >> Hopefully they will fix it shortly. >> > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/42a3d359-85a4-4f52-9e57-c66da178ee9e%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/42a3d359-85a4-4f52-9e57-c66da178ee9e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW5sQSEDwyWHpgnx5WEwzg3K0FaJ6BAJeSnnmittUyEwYg%40mail.gmail.com.
Re: [weewx-user] Re: rtupdate.wunderground.com certificate error
Yeah - it's the intermediate certificate. DIgicert's tool even says what's
wrong with it - SSL works on a "chain of trust" - so, most distributions
trust the "root" certificates - then they issue "intermediate" certificates
and then sign customer's certificates with that. This requires customers to
publish both the server & intermediate certificate(s) to allow the client
to "chain" back to the root certificate that it trusts.
If it helps anyone - I've modified my weewx install to use http temporarily
... I added this in weewx/restx.py around line 597
use_http_to_post = to_bool(_ambient_dict.pop('use_http', False))
if use_http_to_post:
StdWunderground.pws_url =
re.sub("https","http",StdWunderground.pws_url)
StdWunderground.rf_url =
re.sub("https","http",StdWunderground.rf_url)
Then a new config flag in weewx.conf `use_http` will let you toggle on/off
Brice Ruth, FCD
Software Engineer, Madison WI
On Fri, Jan 31, 2020 at 10:39 AM Denny Page wrote:
> For those of you still experiencing an issue, I posted this on the
> Wunderground apicommunity thread:
>
>
>
> So, the certificate isn't verifiable due to authority trust. Easily
> identifiable with wget or curl. It would appear that the certificate
> authority ("DigiCert SHA2 Secure Server CA") is not trusted with at least
> some of the Linux distributions. It is trusted in current MacOs.
>
> -
>
> denny ~ $ wget
> https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php
> --2020-01-31 08:28:41--
> https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php
> Resolving rtupdate.wunderground.com... 169.60.133.170, 169.47.111.58,
> 52.116.188.166
> Connecting to rtupdate.wunderground.com|169.60.133.170|:443... connected.
> ERROR: cannot verify rtupdate.wunderground.com's certificate, issued by
> 'CN=DigiCert SHA2 Secure Server CA,O=DigiCert Inc,C=US':
> Unable to locally verify the issuer's authority.
> To connect to rtupdate.wunderground.com insecurely, use
> `--no-check-certificate'.
> denny ~ $ curl
> https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php
> curl: (60) SSL certificate problem: unable to get local issuer certificate
> More details here: https://curl.haxx.se/docs/sslcerts.html
>
> curl failed to verify the legitimacy of the server and therefore could not
> establish a secure connection to it. To learn more about this situation and
> how to fix it, please visit the web page mentioned above.
> denny ~ $
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/6f2decf9-4c1a-48f6-8a88-6eac8f15c62e%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/6f2decf9-4c1a-48f6-8a88-6eac8f15c62e%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/CAFbExW6Z859c9V28ugBoO8n5jth2PqUea9rBT0VoDW5VbV1R0g%40mail.gmail.com.
Re: [weewx-user] Re: rtupdate.wunderground.com certificate error
Eventually it exits with the SSL error again ... Jan 31 10:20:44 raspberrypi weewx[9240]: restx: Wunderground-RF: Thread > exiting. Reason: hostname 'rtupdate.wunderground.com' doesn't match > either of > '*.prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-.us-south.containers.appdomain.cloud', > 'prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-.us-south.containers.appdomain.cloud', > 'prod-pws-ng-546567.us-south.containers.appdomain.cloud' Brice Ruth, FCD Software Engineer, Madison WI On Fri, Jan 31, 2020 at 10:19 AM Brice Ruth wrote: > Yeah, I'm still seeing errors: > > Jan 31 10:18:28 raspberrypi weewx[9240]: restx: Wunderground-RF: Failed to >> publish record 2020-01-31 10:18:22 CST (1580487502): Failed upload after 1 >> tries > > > Brice Ruth, FCD > Software Engineer, Madison WI > > > On Fri, Jan 31, 2020 at 5:46 AM Dave McCreath > wrote: > >> Spoke too soon. >> >> SSL Certificate error went away last night, still failed to upload (on >> third error), now back to SSL Certificate error again! >> >> Jan 31 10:50:27 raspberrypi weewx[545]: restx: Wunderground-PWS: Thread >> exiting. Reason: hostname 'weatherstation.wunderground.com' doesn't >> match either of >> '*.prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-.us-south.containers.appdomain.cloud', >> 'prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-.us-south.containers.appdomain.cloud', >> 'prod-pws-ng-546567.us-south.containers.appdomain.cloud' >> >> Bummer. >> >> -- >> 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. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/730af4c4-6fea-446f-ac0a-3ef112d65739%40googlegroups.com >> <https://groups.google.com/d/msgid/weewx-user/730af4c4-6fea-446f-ac0a-3ef112d65739%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW5fPymP0%3DUyFtSU5RQVEqS7h6NV%2BOhPjV8fD0CcsHV7Rw%40mail.gmail.com.
Re: [weewx-user] Re: rtupdate.wunderground.com certificate error
Yeah, I'm still seeing errors: Jan 31 10:18:28 raspberrypi weewx[9240]: restx: Wunderground-RF: Failed to > publish record 2020-01-31 10:18:22 CST (1580487502): Failed upload after 1 > tries Brice Ruth, FCD Software Engineer, Madison WI On Fri, Jan 31, 2020 at 5:46 AM Dave McCreath wrote: > Spoke too soon. > > SSL Certificate error went away last night, still failed to upload (on > third error), now back to SSL Certificate error again! > > Jan 31 10:50:27 raspberrypi weewx[545]: restx: Wunderground-PWS: Thread > exiting. Reason: hostname 'weatherstation.wunderground.com' doesn't match > either of > '*.prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-.us-south.containers.appdomain.cloud', > 'prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-.us-south.containers.appdomain.cloud', > 'prod-pws-ng-546567.us-south.containers.appdomain.cloud' > > Bummer. > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/730af4c4-6fea-446f-ac0a-3ef112d65739%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/730af4c4-6fea-446f-ac0a-3ef112d65739%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAFbExW54P8-zkgy3OtwgUxGOTQqGZ1FDVXpRE3FB56G3%2BKCa4A%40mail.gmail.com.
[weewx-user] rtupdate.wunderground.com certificate error
Just a heads up (I've reported this to wunderground) - It looks like the SSL/TLS certificate for `rtupdate.wunderground.com` is > incorrect or the API has been compromised in some way. Accessing > `https://rtupdate.wunderground.com` in a browser such as Chrome yields a > security warning: NET::ERR_CERT_COMMON_NAME_INVALID and the `weewx` > software used to upload data to wunderground reports `hostname > 'rtupdate.wunderground.com' doesn't match either of '*. > prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-.us-south.containers.appdomain.cloud', > > 'prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-.u > s-south.containers.appdomain.cloud', > 'prod-pws-ng-546567.us-south.containers.appdomain.cloud'` - maybe the DNS > was switched to a new API endpoint but the SSL/TLS certificate that matches > the DNS name wasn't configured correctly? > This is blocking all weather station updates to `rtupdate.wunderground.com` > that are using secure transport (which should be required because security > credentials are passed in the requests). -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/0619e1ef-8a4b-49d1-8983-c6f413e31006%40googlegroups.com.
