[weewx-user] Re: Realtime.txt, realtime.xml and sunbird.txt

[Janez Kranjski]

Tnx.
Now another problem :-)

Check attached log file (realtime.xml problem).



On Monday, January 23, 2017 at 6:37:46 AM UTC+1, mwall wrote:
>
> On Monday, January 23, 2017 at 12:04:40 AM UTC-5, Janez Kranjski wrote:
>>
>> Sorry - but now I don't understand your lines bellow. Until now, I use 
>> the convention mentioned on https://github.com/weewx/weewx/wiki/crt (2. 
>> Modify weeex.conf).
>> Your specification mentioned bellow is somewhat different.
>>
>> Should I try with another filename line?
>>>
>>>
>>>
> if you just want to emit a file with the text (non-xml) formatted 
> realtime, then do this:
>
> [CumulusRealTime]
> realtime_txt = /var/tmp/realtime.txt
>
> if you want to emit two files, one in the xml format and the other in txt 
> format, then do this:
>
> [CumulusRealTime]
> realtime_txt = /var/tmp/realtime.txt
> realtime_xml = /var/tmp/realtime.xml
>
> if you just want to emit the sunbird file, then do this:
>
> [CumulusRealTime]
> sunbird_txt = /var/tmp/sunbird
>
> if you want to emit all three, then do this:
>
> [CumulusRealTime]
> realtime_txt = /var/tmp/realtime.txt
> realtime_xml = /var/tmp/realtime.xml
> sunbird_txt = /var/tmp/sunbird
>
> the parameter 'realtime_txt' is a synonym for 'filename'; for backward 
> compatibility, 'filename' is still recognized.
>
> 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 options, visit https://groups.google.com/d/optout.
Jan 23 07:49:09 raspberrypi weewx[18163]: Starting weewx weather system: weewx.
Jan 23 07:49:09 raspberrypi weewx[18178]: wmr200: MainThread: I Created 
watchdog thread to poke for live data every 30 seconds
Jan 23 07:49:09 raspberrypi weewx[18178]: wmr200: MainThread: I Created USB 
polling thread to read block on device
Jan 23 07:49:09 raspberrypi weewx[18178]: wmr200: Thread-2: I USB polling 
device thread for live data launched
Jan 23 07:49:09 raspberrypi weewx[18178]: wmr200: MainThread: I Reset console 
device
Jan 23 07:49:10 raspberrypi weewx[18178]: wmr200: Thread-2: I USB polling 
device thread signaled to start
Jan 23 07:49:10 raspberrypi weewx[18178]: engine: StdConvert target unit is 0x1
Jan 23 07:49:10 raspberrypi weewx[18178]: wmr200: Thread-1: I Started watchdog 
thread live data
Jan 23 07:49:11 raspberrypi weewx[18178]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, 
windrun=prefer_hardware, heatindex=prefer_hardware, 
maxSolarRad=prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Jan 23 07:49:11 raspberrypi weewx[18178]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jan 23 07:49:11 raspberrypi weewx[18178]: crt: service version is 0.19rc1
Jan 23 07:49:11 raspberrypi weewx[18178]: crt: realtime txt output goes to 
/var/www/html/realtime.txt
Jan 23 07:49:11 raspberrypi weewx[18178]: crt: realtime xml output goes to 
/var/www/html/realtime.xml
Jan 23 07:49:11 raspberrypi weewx[18178]: crt: sunbird output goes to 
/var/www/html/sunbird.txt
Jan 23 07:49:11 raspberrypi weewx[18178]: crt: 'None' values will be displayed 
as NULL
Jan 23 07:49:11 raspberrypi weewx[18178]: crt: units will be displayed as METRIC
Jan 23 07:49:11 raspberrypi weewx[18178]: crt: zambretti forecast: False
Jan 23 07:49:11 raspberrypi weewx[18178]: crt: binding is archive
Jan 23 07:49:11 raspberrypi weewx[18178]: engine: Archive will use data binding 
wx_binding
Jan 23 07:49:11 raspberrypi weewx[18178]: engine: Record generation will be 
attempted in 'hardware'
Jan 23 07:49:11 raspberrypi weewx[18178]: engine: Using archive interval of 300 
seconds (specified by hardware)
Jan 23 07:49:11 raspberrypi weewx[18178]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Jan 23 07:49:11 raspberrypi weewx[18178]: manager: Starting backfill of daily 
summaries
Jan 23 07:49:11 raspberrypi weewx[18178]: manager: Daily summaries up to date
Jan 23 07:49:11 raspberrypi weewx[18178]: restx: StationRegistry: Station will 
be registered.
Jan 23 07:49:11 raspberrypi weewx[18178]: restx: Wunderground-PWS: Data for 
station IGORENJS12 will be posted
Jan 23 07:49:11 raspberrypi weewx[18178]: restx: PWSweather: Posting not 
enabled.
Jan 23 07:49:11 raspberrypi weewx[18178]: restx: CWOP: Posting not enabled.
Jan 23 07:49:11 raspberrypi weewx[18178]: restx: WOW: Posting not enabled.
Jan 23 07:49:11 raspberrypi weewx[18178]: restx: AWEKAS: Posting not enabled.
Jan 23 07:49:11 raspberrypi weewx[18178]: engine: Starting up weewx version 
3.6.2
Jan 23 07:49:15 raspberrypi weewx[18178]: wmr200: MainThread: I Time drift 
between host and console 

[weewx-user] Re: Acurite 01536 (Costco) pressure sensor

[David Morgan]

Note from the datasheet that it measures both pressure and temperature, and 
has correction constants built in, but correction must be applied 
externally.

On Sunday, January 22, 2017 at 10:55:11 PM UTC-8, David Morgan wrote:
>
> I have been able to photograph and read the sensor in my unit.   Here is a 
> photo.  The black IC next to it has a different part of a photo pasted over 
> it so you can see the chip labeling.
>
> This may be the proper design PDF for the sensor: 
> http://www.mouser.com/ds/2/418/MS5637-02BA03-768293.pdf
>
>
>
> http://www.mouser.com/ProductDetail/Measurement-Specialties/MS563702BA03-50/?qs=ZSTLft15nNCFYZwlCm%2FnTA%3D%3D
>
>
>

-- 
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 options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Realtime.txt, realtime.xml and sunbird.txt

[mwall]

On Monday, January 23, 2017 at 12:04:40 AM UTC-5, Janez Kranjski wrote:
>
> Sorry - but now I don't understand your lines bellow. Until now, I use the 
> convention mentioned on https://github.com/weewx/weewx/wiki/crt (2. 
> Modify weeex.conf).
> Your specification mentioned bellow is somewhat different.
>
> Should I try with another filename line?
>>
>>
>>
if you just want to emit a file with the text (non-xml) formatted realtime, 
then do this:

[CumulusRealTime]
realtime_txt = /var/tmp/realtime.txt

if you want to emit two files, one in the xml format and the other in txt 
format, then do this:

[CumulusRealTime]
realtime_txt = /var/tmp/realtime.txt
realtime_xml = /var/tmp/realtime.xml

if you just want to emit the sunbird file, then do this:

[CumulusRealTime]
sunbird_txt = /var/tmp/sunbird

if you want to emit all three, then do this:

[CumulusRealTime]
realtime_txt = /var/tmp/realtime.txt
realtime_xml = /var/tmp/realtime.xml
sunbird_txt = /var/tmp/sunbird

the parameter 'realtime_txt' is a synonym for 'filename'; for backward 
compatibility, 'filename' is still recognized.

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 options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Acurite 01536 (Costco)

[David Morgan]

On Wednesday, January 18, 2017 at 4:24:16 PM UTC-8, David Morgan wrote:
>
>
>> I also got a Costco Acurite  01536-RX for Christmas.   
> . I am curious if anyone knows yet what sensors are used.  I have 
> resisted peeking so far, but  that may change. 
>

I have been looking I photos I took of the main board.   I now see that it 
uses a 24C512 EEPROM.   Right next to it appears to be the barometric 
pressure sensor.  Photo is not good enough to read the part number.   Also, 
I believe the humidity and temp sensors are on long leads, and stick out to 
where they are close to the air opening in the upper left side of the unit 
as you look at it from the front.

-- 
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 options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Realtime.txt, realtime.xml and sunbird.txt

[Janez Kranjski]

Sorry - but now I don't understand your lines bellow. Until now, I use the 
convention mentioned on https://github.com/weewx/weewx/wiki/crt (2. Modify 
weeex.conf).
Your specification mentioned bellow is somewhat different.

Should I try with another filename line?
filename = /var/tmp/sunbird

Bye.



On Sunday, January 22, 2017 at 4:16:41 PM UTC+1, mwall wrote:
>
>
> to get realtime.xml or sunbird, you must specify them.  for example, if 
> you want all three files:
>
> [CumulusRealTime]
> ...
> realtime_txt = /var/tmp/realtime.txt
> realtime_xml = /var/tmp/realtime.xml
> sunbird_txt = /var/tmp/sunbird 
>
> 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 options, visit https://groups.google.com/d/optout.

Re: [weewx-user] upgrading from 2.0 to 3.6

[tds]

Just discovered my Vantage Data Logger has ATTRS{idProduct}=="ea61", 
instead of "ea60" in the udev rules supplied with the .deb package. I'm 
using it with an Davis Envoy, instead of a Console. But I suppose the 
product ID should be set with the data logger itself. 

On Sunday, January 22, 2017 at 2:02:58 PM UTC-8, tds wrote:
>
> Yes, it was fairly uneventful. I installed with .deb package and went 
> though the weewx.conf to make sure everything was correct.
>
> Now with the basic function working, I'll start to play with the new 
> features like RapidFire and rsync. I'll also make sure the setup will 
> survive a reboot.
>
> DS
>
>
> On Sunday, January 22, 2017 at 1:22:10 PM UTC-8, Tom Keffer wrote:
>>
>> And otherwise, it went OK?
>>
>> -tk
>>
>> On Sun, Jan 22, 2017 at 12:35 PM, tds  wrote:
>>
>>> OK, I did the migration today. My weewx.sdb was about 74MB. It only took 
>>> the manager a bit over 10 minutes to finish the backfilling. The process 
>>> started at 22:13:07 and finished at 20:24:37. 
>>>
>>> Jan 22 20:24:37 wxpi weewx[3224]: manager: Processed 442781 records to 
>>> backfill 1539 day summaries in 689.98 seconds
>>>
>>> DS.
>>>
>>> On Thursday, January 19, 2017 at 5:05:30 PM UTC-8, gjr80 wrote:

 On Friday, 20 January 2017 10:53:44 UTC+10, vince wrote:
>
>
> Older model pi had issues completing it successfully, but I'm 
> guessing/hoping a pi3 has enough horsepower that it'll succeed.  Be very 
> patient during the conversion process.
>

 IIRC the main issue with the older RPi (other than speed) was that 
 backfilling the daily summaries was done in a single transaction and for 
 large archives this caused memory issues leading to a crash. This issue 
 was 
 addressed in 3.5.0 and the daily summary rebuilds are now done in 
 transactions of so many days rather than one big transaction. So hopefully 
 that aspect should be crash free. And a contemporary RPi should see the 
 rebuild done much faster than original RPi.

 Gary

>>> -- 
>>> 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+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
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 options, visit https://groups.google.com/d/optout.

Re: [weewx-user] upgrading from 2.0 to 3.6

[tds]

Yes, it was fairly uneventful. I installed with .deb package and went 
though the weewx.conf to make sure everything was correct.

Now with the basic function working, I'll start to play with the new 
features like RapidFire and rsync. I'll also make sure the setup will 
survive a reboot.

DS


On Sunday, January 22, 2017 at 1:22:10 PM UTC-8, Tom Keffer wrote:
>
> And otherwise, it went OK?
>
> -tk
>
> On Sun, Jan 22, 2017 at 12:35 PM, tds  
> wrote:
>
>> OK, I did the migration today. My weewx.sdb was about 74MB. It only took 
>> the manager a bit over 10 minutes to finish the backfilling. The process 
>> started at 22:13:07 and finished at 20:24:37. 
>>
>> Jan 22 20:24:37 wxpi weewx[3224]: manager: Processed 442781 records to 
>> backfill 1539 day summaries in 689.98 seconds
>>
>> DS.
>>
>> On Thursday, January 19, 2017 at 5:05:30 PM UTC-8, gjr80 wrote:
>>>
>>> On Friday, 20 January 2017 10:53:44 UTC+10, vince wrote:


 Older model pi had issues completing it successfully, but I'm 
 guessing/hoping a pi3 has enough horsepower that it'll succeed.  Be very 
 patient during the conversion process.

>>>
>>> IIRC the main issue with the older RPi (other than speed) was that 
>>> backfilling the daily summaries was done in a single transaction and for 
>>> large archives this caused memory issues leading to a crash. This issue was 
>>> addressed in 3.5.0 and the daily summary rebuilds are now done in 
>>> transactions of so many days rather than one big transaction. So hopefully 
>>> that aspect should be crash free. And a contemporary RPi should see the 
>>> rebuild done much faster than original RPi.
>>>
>>> Gary
>>>
>> -- 
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 options, visit https://groups.google.com/d/optout.

Re: [weewx-user] upgrading from 2.0 to 3.6

[Thomas Keffer]

And otherwise, it went OK?

-tk

On Sun, Jan 22, 2017 at 12:35 PM, tds  wrote:

> OK, I did the migration today. My weewx.sdb was about 74MB. It only took
> the manager a bit over 10 minutes to finish the backfilling. The process
> started at 22:13:07 and finished at 20:24:37.
>
> Jan 22 20:24:37 wxpi weewx[3224]: manager: Processed 442781 records to
> backfill 1539 day summaries in 689.98 seconds
>
> DS.
>
> On Thursday, January 19, 2017 at 5:05:30 PM UTC-8, gjr80 wrote:
>>
>> On Friday, 20 January 2017 10:53:44 UTC+10, vince wrote:
>>>
>>>
>>> Older model pi had issues completing it successfully, but I'm
>>> guessing/hoping a pi3 has enough horsepower that it'll succeed.  Be very
>>> patient during the conversion process.
>>>
>>
>> IIRC the main issue with the older RPi (other than speed) was that
>> backfilling the daily summaries was done in a single transaction and for
>> large archives this caused memory issues leading to a crash. This issue was
>> addressed in 3.5.0 and the daily summary rebuilds are now done in
>> transactions of so many days rather than one big transaction. So hopefully
>> that aspect should be crash free. And a contemporary RPi should see the
>> rebuild done much faster than original RPi.
>>
>> Gary
>>
> --
> 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 options, visit https://groups.google.com/d/optout.
>

-- 
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 options, visit https://groups.google.com/d/optout.

Re: [weewx-user] upgrading from 2.0 to 3.6

[tds]

OK, I did the migration today. My weewx.sdb was about 74MB. It only took 
the manager a bit over 10 minutes to finish the backfilling. The process 
started at 22:13:07 and finished at 20:24:37. 

Jan 22 20:24:37 wxpi weewx[3224]: manager: Processed 442781 records to 
backfill 1539 day summaries in 689.98 seconds

DS.

On Thursday, January 19, 2017 at 5:05:30 PM UTC-8, gjr80 wrote:
>
> On Friday, 20 January 2017 10:53:44 UTC+10, vince wrote:
>>
>>
>> Older model pi had issues completing it successfully, but I'm 
>> guessing/hoping a pi3 has enough horsepower that it'll succeed.  Be very 
>> patient during the conversion process.
>>
>
> IIRC the main issue with the older RPi (other than speed) was that 
> backfilling the daily summaries was done in a single transaction and for 
> large archives this caused memory issues leading to a crash. This issue was 
> addressed in 3.5.0 and the daily summary rebuilds are now done in 
> transactions of so many days rather than one big transaction. So hopefully 
> that aspect should be crash free. And a contemporary RPi should see the 
> rebuild done much faster than original RPi.
>
> Gary
>

-- 
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 options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Hints on creating coldest/warmest day/night all-time stats?

[Jared]

Okay, I got some basic thoughts down and I think I'm ready to actually 
create a service.  Or something.  This is a simple task and there's a bunch 
of ways to do it, so I'm coming across a lot of "where do I do it" 
questions.  Do I write more code and have my python file do it manually, or 
do I take advantage of what's already built into weewx?  If so, how?

I decided that I want to go with a separate database called day_night.sdb 
with two tables, 'day' and 'night'.  I made the tables with the following 
schemas.  Just a timestamp, the units, and the average day/night 
temperature respectively for that day.  

CREATE TABLE day (`dateTime` INTEGER NOT NULL UNIQUE PRIMARY KEY, `usUnits` 
INTEGER NOT NULL, `temp` REAL);
CREATE TABLE night (`dateTime` INTEGER NOT NULL UNIQUE PRIMARY KEY, 
`usUnits` INTEGER NOT NULL, `temp` REAL);

So I need to hit the real weewx database, query it, then write to my 
database.  As a test I made a python file, imported the sqlite3 module, and 
performed some database writes.  This worked fine.  I suppose I could query 
the weewx database this way as well, do the calculations, and then write, 
but this feels like it's not the right way to think about things.  I feel 
like I should be using more of the internal weewx stuff.

For example I see [DatabaseTypes] in weewx.conf.  Would I add my database 
file here or that unnecessary since I don't think I'll be using any wee 
database functions (I'm not writing to the standard database after all). 
 As far as the service itself, it seems like this would piggyback off 
StdArchive as an archive_service?  What's the best way for me to test stuff 
as I'm figuring it out?

Am I on the right track or no?  :)



On Monday, January 16, 2017 at 5:41:05 PM UTC-5, Jared wrote:
>
> Oh and I suppose I need Units as well.
>
> On Monday, January 16, 2017 at 5:34:41 PM UTC-5, Jared wrote:
>>
>> At this point I'm starting to feel like this would be a neat little 
>> project for me to get familiar with a number of things (weewx, python, 
>> sqlite, etc.), so I'm feeling a bit ambitious and think I'll give this a 
>> try myself.
>>
>> I definitely think storing the info in a database is the way to go. 
>>  mwall mentioned creating a separate database and then running a service 
>> twice a day.  I like this approach because it will allow me to mess around 
>> as a noob without potentially screwing up the real database.  
>>
>> I also like the sunrise/sunset as the day/night boundary idea.  With that 
>> said, what do you guys think makes the most sense from the standpoint of 
>> database construction and then calling upon it usefully later?  This is 
>> what I was thinking (and please let me know if this is silly, especially if 
>> my primary key makes no sense).  The DB will have one table with the 
>> primary key, day, and night values.  I can use something like -MM-DD as 
>> the primary key.  Night would be the average temperature between sunset the 
>> previous day and sunrise of the present day.  Day would be populated at 
>> sunset with the average temperature between sunrise and sunset. 
>>  Alternatively, the primary key could be the unix epoch for 00:00 GMT of 
>> that day to keep conversions more fluid (since the service would only 
>> populate it at sunrise and sunset and the value is not really 
>> time-dependent but rather date-dependent).  Or it could just be the unix 
>> epoch for the time that the service runs.  Whatever makes it easier for 
>> later recall.
>>
>> On Monday, January 16, 2017 at 4:33:26 PM UTC-5, gjr80 wrote:
>>>
>>> weewx-WD provides warmest night/coldest day stats by maintaining two 
>>> fields, outTempDay and outTempNight, in the weewx-WD database. Data is 
>>> stored using the 0600-1800 day. Aggregates over month, year all time etc 
>>> now become very simple, just part of the standard weewx machinery and you 
>>> avoid some pretty messy and slow queries that would have to operate on the 
>>> archive. The downside is you are essentially double recording outTemp but 
>>> what's another few Mbytes.
>>>
>>> I agree it's a very useful statistic and one that is quite relevant here 
>>> at this time of year.
>>>
>>> Gary
>>>
>>>

-- 
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 options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Realtime.txt, realtime.xml and sunbird.txt

[mwall]

On Sunday, January 22, 2017 at 9:19:07 AM UTC-5, Janez Kranjski wrote:
>
> I tried ... but ... do I need a "sunbird.txt.tmpl"?
>

by default, only the realtime (in txt format) will be emitted.

to get realtime.xml or sunbird, you must specify them.  for example, if you 
want all three files:

[CumulusRealTime]
...
realtime_txt = /var/tmp/realtime.txt
realtime_xml = /var/tmp/realtime.xml
sunbird_txt = /var/tmp/sunbird 

btw, if the only thing you need is sunbird, you can do that trivially using 
the standard weewx reporting system (but you'll only get it at every 
archive interval, not at every loop)

also btw, the actual usefulness of sunbird is questionable - it provides 
only sunrise, sunset, and the time the data were last updated.  calculating 
sunrise and sunset is trivial to do, and a timestamp without the rest of 
the data is of marginal value (once again, just emit a timestamp to file in 
one of your regular weewx reports).

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 options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Realtime.txt, realtime.xml and sunbird.txt

[Janez Kranjski]

I tried ... but ... do I need a "sunbird.txt.tmpl"?

On Sunday, January 22, 2017 at 1:55:28 AM UTC+1, mwall wrote:
>
> janez,
>
> please try the attached crt 0.19rc1
>
> it implements realtime.xml (except for yesterday hi/lo and record hi/lo) 
> and sunbird
>
> there are still many ambiguities, for example:
>
> which time zone are the sunbird values supposed to be in?
> what format are the date/time in sunbird supposed to be?
> what precision is required for the values in realtime.xml? 
> what should be used when a reading is NULL?
> are the units supposed to be included or not?
> are the units case sensitive?
>
> the two files you posted are not specifications - they are templates.
>
> where is the specification for sunbird?
> where is the specification for realtime.xml?
>
> the only specification i know are these two pages:
>
> http://wiki.sandaysoft.com/a/Realtime.txt
>
> http://wiki.sandaysoft.com/a/Webtags
>
> and, as documented in crt.py, they are ambiguous.
>
> in lieu of specifications, you'll have to find a whole bunch of examples, 
> with corner cases, to figure out the ambiguities.
>
> 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 options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Niculskin - Date and time Formatting.

[Darryn Capes-Davis]

John,

I have done a bit of thinking and testing on my Ubuntu setup. Three things 
here.

1. Missing LC_ALL is an issue. Find your favourite information to fix on 
Google.
2. Missing LC_ALL will mean "%x %X" will give what you are seeing on 
index.html
3. I expect that Niculskin code for localising strings is giving havoc to 
weewx ConfigObj code and making weewx.conf override skin.conf (just a 
guess).

Fixes?

A. Fix LC_ALL (Looks like setting in /etc/environment is best bet). Can 
test by running in python interpreter .

You will see for me, where I also have the LC_ALL issue, I get the wrong 
format with "%x %X", even though the rest of my LC_X and en_AU.

>>> import datetime
>>> datetime.datetime.now().strftime("%x %X")
'01/22/17 19:16:00'

 B. Since you don't need Niculskin localisation, you can not use the 
Niculskin binaries CheetahGeneratorTranslated. Revert back to 
weewx.cheetahgenerator.CheetahGenerator.

Good luck.

Cheers

Darryn

On Sunday, January 22, 2017 at 3:07:11 PM UTC+11, gjr80 wrote:

> You did stop/start or reload weewx after making changes to weewx.conf? 
> Not required for changes to skin.conf but is required for weewx.conf 
> changes.
>
> Gary
>
> On Sunday, 22 January 2017 00:56:30 UTC+10, John Rye wrote:
>
>>
>>
>> On Sunday, 22 January 2017 01:08:11 UTC+13, Darryn Capes-Davis wrote:
>>>
>>> John,
>>>
>>> > What locale is your server? 
>>>
>>
>> [lists@amd64 ~]$ locale
>> LANG=en_NZ.UTF-8
>> LC_CTYPE="en_NZ.UTF-8"
>> LC_NUMERIC="en_NZ.UTF-8"
>> LC_TIME="en_NZ.UTF-8"
>> LC_COLLATE="en_NZ.UTF-8"
>> LC_MONETARY="en_NZ.UTF-8"
>> LC_MESSAGES="en_NZ.UTF-8"
>> LC_PAPER="en_NZ.UTF-8"
>> LC_NAME="en_NZ.UTF-8"
>> LC_ADDRESS="en_NZ.UTF-8"
>> LC_TELEPHONE="en_NZ.UTF-8"
>> LC_MEASUREMENT="en_NZ.UTF-8"
>> LC_IDENTIFICATION="en_NZ.UTF-8"
>> LC_ALL=
>> [lists@amd64 ~]$ 
>>
>>   So physically in New Zealand as is the server.
>>  
>>
>>> > I ask as the only way you would be getting the display on your site 
>>> would be from the format string "%x %X" on a US locale server. 
>>>
>>
>>  Agreed. However I have altered all the time format strings in weewx.conf 
>> in line with what is shown in 
>> http://weewx.com/docs/customizing.htm#Units_TimeFormats. I don't see any 
>> point in going further and custominsing as per strftime - it shouldn't be 
>> necessary
>>
>>>
>>> > However I can't see how the format "%x %X" would be being used?
>>>
>>
>> I'm beginning to wonder if its hard-coded in the javascript (/me 
>> shudders) because I'm fairly sure I was able to alter the formatting in the 
>> Standard skin.
>>
>> Cheers
>>
>> John in NZ
>>
>>

-- 
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 options, visit https://groups.google.com/d/optout.