I came upon this because my moon info was not populating.
When I tried to install pyephem there were errors that setup couldn't be
found.
I corrected that with pip install --upgrade setuptools
Then pyephem installed fine.
This was likely due to an upgrade of Mint from 18.3 to 19
I believe it was
It's seeming like that's my best option - Move the NOAA reports to a 2nd
skin, then add that skin to the install.py.
On Friday, August 24, 2018 at 7:11:01 PM UTC-4, gjr80 wrote:
>
> On Saturday, 25 August 2018 08:14:40 UTC+10, Pat wrote:
>>
>>
>> I'm assuming if this is only affecting the
On Saturday, 25 August 2018 08:14:40 UTC+10, Pat wrote:
>
>
> I'm assuming if this is only affecting the highchartsDay class - and not
> the others - that there's a way to make the day charts play nice with the
> other SLEs?
>
No, it will affect the others, week will be the same, month and year
Fair enough. This is where my knowledge of the SLEs is weakest.
I'm assuming if this is only affecting the highchartsDay class - and not
the others - that there's a way to make the day charts play nice with the
other SLEs?
On Friday, August 24, 2018 at 6:07:39 PM UTC-4, gjr80 wrote:
>
> If
If you are only using 2018 data then no, the year NOAA reports have no effect.
If you include 2017 data then the year NOAA reports will cause the same issue.
Have a look at the very first line of the error trace I posted, that is due to
a yearly NOAA report for 2016.
There is no conflict/issue
Still trying to do some testing, step by step through the process. It looks
like if you remove only the SummaryByMonth NOAA report, the extension
completes successfully.
So there's some sort of clash between highchartsDay and
the NOAA--MM.txt.tmpl template?
On Friday, August 24, 2018 at
Just a point of clarification, well wrongness actually. I said that for the
[[ToDate]] reports the timespan parameter is the current archive period. It is
not, it is in fact the period from the timestamp of first good record in the
archive through until the timestamp of the last record in the
I admit I was feeling a bit daft reading through this because I couldn't
replicate it. Thanks for providing your test information, it allowed me to
to replicate it so I can see the problem first hand. I took my 3 year old
database (which was working), copied to a new lab system, truncated it to
Following up on myself: I got impatient, and using the documentation of
rtl_433¹ and weewx-sdr I installed them, and configured weewx thus:
[Station]
...
station_type = SDR
...
[SDR]
driver = user.sdr
cmd = /usr/local/bin/rtl_433 -q -U -F json -R 32
Andrew writes:
> have you tried clearing the memory by power cycling the station - remove
> all power - batteries and usb - and start the station again
As I wrote in my first email:
"I have tried changing batteries, hard resetting it, leaving it
unpowered for 14 days, all to no avail."
have you tried clearing the memory by power cycling the station - remove
all power - batteries and usb - and start the station again
On Friday, 24 August 2018 19:39:31 UTC+3, Adam Sjøgren wrote:
>
> mwall writes:
>
> > On Thursday, August 23, 2018 at 2:56:23 PM UTC-4, Adam Sjøgren wrote:
>
>
mwall writes:
> On Thursday, August 23, 2018 at 2:56:23 PM UTC-4, Adam Sjøgren wrote:
>> Configuring weewx to get information from --current instead the history
>> would be easier [for me, anyway :-)]. Is it possible, and if so, how?
> first try clearing the station memory - it looks like you
Hallo
Danke ich werde das mal Testen..
Am Donnerstag, 22. Februar 2018 22:07:13 UTC+1 schrieb Kalli:
>
> hallo
>
> ich benutze WD-Live
> da wird aber leider die Mondphase nicht angezeigt.
> muss da noch was eingesellt werden.
>
>
>
> Hello
>
> I use WD-Live
> but unfortunately the moon phase is
Hallo Kalli,
Die aktuellen Bedingungen werden von WeatherUnderground in festen
Intervallen erhalten. Eine Standardinstallation verwendet ein
30-Minuten-Intervall. Sie können dieses Intervall nach oben oder nach unten
ändern, auch wenn es keinen Sinn hat, es kürzer als Ihre
I'm convinced. Home now so set up a VM running 3.8.2 with no data in the
db. Runs fine. Download user.belchertown_highchartsSearchX.highchartsDay
and add a search_list_extensions option to Standard skin.conf using
user.belchertown_highchartsSearchX.highchartsDay as the only SLE. Runs
without
Interesting, but my lab system has over 3 years of data without trouble
with the generator.
On Friday, August 24, 2018 at 8:48:33 AM UTC-4, gjr80 wrote:
>
> No, and you won't run into the situation I described unless you have
> archive data running across multiple months and you force WeeWX to
No, and you won't run into the situation I described unless you have archive
data running across multiple months and you force WeeWX to regenerate the
[[SummaryByMonth]] reports in your skin (could happen on [[SummaryByYear]] too
if you have data spanning multiple years).
Gary
--
You
Thanks for the insight Gary. I haven't run into this problem yet - even on
brand new VM's with only 5 minutes worth of Simulator data.
On Friday, August 24, 2018 at 5:27:05 AM UTC-4, gjr80 wrote:
>
> Yes I have seen similar errors on numerous occasions, but I have never
> seen a cause like this
Woke up wondering if this is the classic case of reusing variable names.
going to try to replicate it today on a Raspberry Pi.
On Fri, Aug 24, 2018, 7:22 AM gjr80 wrote:
> Can't comment further without seeing a good couple of archive periods of a
> log extract that includes the full error
Can't comment further without seeing a good couple of archive periods of a log
extract that includes the full error trace.
Gsry
--
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,
With my clean install there was no data in the archive, but the error still
occurred. After several hours the situation still persisted.
On Friday, 24 August 2018 10:27:05 UTC+1, gjr80 wrote:
>
> Yes I have seen similar errors on numerous occasions, but I have never
> seen a cause like this one
Yes I have seen similar errors on numerous occasions, but I have never seen a
cause like this one before. I believe the cause is that the SLEs are being run
against the [[SummaryByMonth]] and [[SummaryByYear]] reports.
The timespan parameter that is used in the SLE signatures is a TimeSpan
Hallo Gir80
ich habe festgestellt, das die Anzeige für das Aktuelle Wetter sehr lange
dauert bis diese sich ändert.
Von Sonne nach Regen dauert sehr lange oder ändert sich garnicht, da sollte
noch mal was gemacht werden.
denn wenn es Regnet sollte auch Aktuell: Regen da stehen.
mfg. Kalli
Am
It is a deb installation, the server is configured for unattended updates.
In troubleshooting the issues briefly last week I noticed weewx was a newer
version than I recalled, and matched the current version on the website.
The backup conf date also matched the last day weewx was posting
Hallo
ich denke das die Basis Defekt ist.
das war mei meiner wh1080 auch drei mal neues Display gekauft.
jetzt hab ich die wh-4000
mfg.
Kalli
Am Donnerstag, 23. August 2018 05:06:04 UTC+2 schrieb BEIJY BUA:
>
> Good Morning
> I have a Problem with my WH3080, it always show at the Display 1013,2
looks to me like a farenheit to Celsius conversion somewhere is doing the
-32 without also doing the *5/9 ……..
On Friday, 24 August 2018 07:31:32 UTC+3, Colin Larsen wrote:
>
> Just did a brand new install - smooth as butter with no errors that I can
> see.
>
> Pat, can you explain the temp
26 matches
Mail list logo
