On Thursday, December 29, 2016 at 1:55:37 PM UTC-5, Barton Phillips wrote:
>
> I think I will just 'shine them on'. I can't find any information about
> blocked transmissions and now where to ask a question.
>
i understand why the folks at AWEKAS would like to detect bad sensor data
and keep it
1536 on the left and 2064 on the right. The consoles lock up after 6 or so
months of operation. This year going to hard reset
both consoles at the end of the year, so maybe the rain total will remain
correct for at least the spring rain season. When I get time to get one of
the bmp
That worked. Thanks!
On Thursday, December 29, 2016 at 4:29:08 PM UTC-7, Oscar wrote:
>
> I installed weewx-forecast 3.2.6 and am getting the following error
>
> Dec 29 16:25:15 zk30 weewx[26376]: forecast: NWSThread: NWS: downloading
> forecast from '
>
oscar,
in forecast.py, change line 1782 from this:
label = line[0:14].strip()
to this:
label = line[0:14].strip().upper()
normally the NWS point forecasts use all upper case, but the PFM you got
has 3hrly and 6hrly for some reason.
the change to upper() will prevent any
Black Hawk.
foid = BOU
lid = COZ036
On Thursday, December 29, 2016 at 5:09:55 PM UTC-7, mwall wrote:
>
> oscar,
>
> which location identifier (lid) have you designated?
>
> m
>
--
You received this message because you are subscribed to the Google
oscar,
which location identifier (lid) have you designated?
m
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
For more
I installed weewx-forecast 3.2.6 and am getting the following error
Dec 29 16:25:15 zk30 weewx[26376]: forecast: NWSThread: NWS: downloading
forecast from
'http://forecast.weather.gov/product.php?site=NWS=PFM=txt=BOU'
Dec 29 16:25:15 zk30 weewx[26376]: forecast: NWSThread: NWS: forecast
I have one temperature sensor in another (small) building/house (2 sq.m)
where the water filter is located. Now, there are serveral issues there:
1. The sensor consumes batteries very rapidly. I have to change once a
month when it should last a year. I don't know why this is but the sensor
is
Thanks, Dave. That's a much more complete list of options than I was able
to find. %s it is.
-- Lynda.
On Thursday, December 29, 2016 at 1:55:46 PM UTC-5, Dave Webb wrote:
>
> *%%* a literal percent sign ("*%*").
> *%a* The abbreviated weekday name (e.g., *Sun*).
> *%A* The full weekday
*%%* a literal percent sign ("*%*").
*%a* The abbreviated weekday name (e.g., *Sun*).
*%A* The full weekday name (e.g., *Sunday*).
*%b* The abbreviated month name (e.g., *Jan*).
*%B* locale's full month name (e.g., *January*).
*%c* The date and time (e.g., *Thu Mar 3 23:05:25 2005*).
*%C* The
I think I will just 'shine them on'. I can't find any information about
blocked transmissions and now where to ask a question.
On Wednesday, December 28, 2016 at 12:27:04 PM UTC-8, Erwin Heger wrote:
>
> As you can see: Weewx works. What happens on the other side at Awekas ...
> ask them. For
On Thursday, December 29, 2016 at 1:35:54 AM UTC-8, Per Edström wrote:
>
> Actually, there is not that much info available..
>
>
There is a 'huge' amount of information available for how to back up a pi,
how to back up a sqlite3 database, and how to verify a backup is good and
can be restored.
Actually, there is not that much info available..
Isof says one user when Weewx is running but none when Weewx is stopped.
A reboot did solve the Lock-problem but I have to stop Weewx on this unit,
not the other one..
folke@eBox3350.L5E:~$ sqlite3 /var/lib/weewx/weewx.sdb ".backup
13 matches
Mail list logo
