I changed the "channel" from A to C on both units and seem to be having
many fewer data drop-outs with the Li batteries still in.
It is a bit odd, but I am guessing there is some interference on the A
channel that was messing with my reception.
I wonder if the channels are just a code that is
If you are only trying to display the current you would add something like
the below to sensors.inc or whatever template you want it on. I have not
tested this...
$current.uvBatteryStatus.raw
If you are trying to store the status over time and use the data for graphs
or to track it you will
A new update for the Weather34 skin has been released today.
Features: -
- Full install package using wee_extension --install.
- Single page dynamic console like display which works well with smart
phones, tablets and regular monitor screens.
- Real time updates based on
Hey Thomas -
Thanks for asking. Error string is below. I'm running 3.9.2 for now. It
looks like I run in to a bad cert every 4-5 minutes. Looking at their DNS,
they appear to only have three servers running and they all have the same
certificate string from "Let's Encrypt". Odd.
Jan 31
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
Everything works for me now. No restart was required.
--
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
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
Thanks guys.
Missed that setting in the conf.
On Fri, Jan 31, 2020 at 11:51 AM Thomas Keffer wrote:
> ... or put the CSS and JS files in "copy_always", instead of "copy_once".
>
> On Fri, Jan 31, 2020 at 11:09 AM gjr80 wrote:
>
>> Hi,
>>
>> Correct, .css, .js and .ico are set to ‘copy once’
... or put the CSS and JS files in "copy_always", instead of "copy_once".
On Fri, Jan 31, 2020 at 11:09 AM gjr80 wrote:
> Hi,
>
> Correct, .css, .js and .ico are set to ‘copy once’ (have a look at the
> [CopyGenerator] stanza in Seasons skin.conf). This is by design as the
> files do not change
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
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
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:
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 the Google Groups
"weewx-user"
Hi,
Correct, .css, .js and .ico are set to ‘copy once’ (have a look at the
[CopyGenerator] stanza in Seasons skin.conf). This is by design as the files do
not change from report to report. You have two options, either restart WeeWX
after each change or manually copy them too your web server
Thanks Glen for the detailed instructions. This fixed the problem. And
Kevin R. and all, yeah I plan on changing it back to the SSL link and
changing my password once Weather Underground gets their act together and
fixes this issue.
On Friday, January 31, 2020 at 10:24:26 AM UTC-8, Glenn
I've been working on adding some features to my Seasons skin which involves
some work in the CSS and JS files. When I run a new report, the index.html
is built with all my changes, but the /var/www/html/weewx/seasons.css/js
are not updated. This only seems to happen on the first report run
Concur, an informed decision to be made by the station owner until
weatherunderground resolves their SSL issues.
: Glenn
On Friday, January 31, 2020 at 10:34:42 AM UTC-8, Kevin Rowett wrote:
>
> Be advised...by changing from https protocol to http, your WX station
> password/API key will be
Be advised...by changing from https protocol to http, your WX station
password/API key will be sent in plain text, and if your ISP is comcast...
KR
On Friday, January 31, 2020 at 10:24:26 AM UTC-8, Glenn Godden wrote:
>
> In the weewx /usr/share/weewx/weewx/restx.py file if you change from
>
In the weewx /usr/share/weewx/weewx/restx.py file if you change from
"https" to "http" it will resolve the weatherunderground issue:
*"https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php
Ubuntu makes it pretty straightforward. Copy the file to
/usr/share/ca-certificates and run update-ca-certificates. Better than the
old days, anyway.
This DID fix my problem but it does appear that they continue to mess with
their services. restx will sometimes get the below error which
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
Can at least someone tell me if I need to edit the sensors.inc file?
Il giorno domenica 26 gennaio 2020 17:56:40 UTC+1, Paola Giannusa ha
scritto:
>
> good evening everyone
> I would like to know please how can I correctly insert uvbatterystatus
> (uv800 sensor) on the weewx main page
> I have
Il giorno domenica 26 gennaio 2020 17:56:40 UTC+1, Paola Giannusa ha
scritto:
>
> good evening everyone
> I would like to know please how can I correctly insert uvbatterystatus
> (uv800 sensor) on the weewx main page
> I have already inserted in the sensor map of weewx.conf this line:
>
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.
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
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
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
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
>
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:
>
https://groups.google.com/d/msg/weewx-user/cDFAN1GBCfA/39399_wjAAAJ
On Friday, January 31, 2020 at 2:53:47 AM UTC-5, Kevin Key wrote:
>
> Is there an option to disable use of SSL for pushing data to Weather
> Underground? I am getting nothing but errors and can no longer push to WU.
>
>
--
You
Hi weewx-freaks
I am usung the interceptor for colecting weather data from a Renkforce
WH2600, workes fine.
Then I added the electrcity service to display the values of a solar panel
on the same site, works fine.
The WH2600 triggered the electricty script to have the values time
synchronized.
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
I have the same issue
restx: Wunderground-PWS: Failed to publish record 2020-01-31 11:05:00 UTC
(1580468700): Failed upload after 3 tries
On Friday, January 31, 2020 at 2:43:09 PM UTC+10:30, Kevin Rowett wrote:
>
> I no longer get a ssl cert error.
>
> Now get this error:
>
> restx:
Thanks for the input, the udev script should avoid the problem, I
implemented that. Besides that, I modified alarm.py to also check the
record for missing entries. As it is in the user directory, It should be ok
to do that. :D
(and I replaced the USB/Serial converter. When I installed the
Noted on the wunderground api page too
-
https://apicommunity.wunderground.com/weatherapi/topics/ssl-certificate-error-9lwea9u1krwgd
- seems like they have stuffed something up their end. Cert updates via
apt-get or *sudo /usr/sbin/update-ca-certificates* don't work to solve this.
On Friday,
/usr/share/weewx/weewx/restx.py
look for
pws_url =
"https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php;
probaby need to restart the service too ??
On Friday, 31 January 2020 18:48:59 UTC+11, Kevin Key wrote:
>
> Where is this file located?
>
> On Thursday,
36 matches
Mail list logo
