Re: [weewx-user] Questions about weewx-loopdata

> remote_server = ftpupload.net I would expect the remote server to be kairos.moudania.com It looks like you are trying to use an ftp server. If so, that simply won’t work. If you don’t have ssh access to your server, such that you can get rsync to work, you will not be able to use the loopdata

Re: [weewx-user] Questions about weewx-loopdata

i have setup for loopdata [LoopData] [[FileSpec]] loop_data_dir = . filename = loop-data.txt [[Formatting]] target_report = LoopDataReport [[LoopFrequency]] seconds = 30 [[RsyncSpec]] enable = true remote_server = ftpupload.net

Re: [weewx-user] Questions about weewx-loopdata

As the README states: If you need the loop-data.txt file pushed to a remote webserver, you will also need to fill in the RsyncSpec fields; but one can fill that in later, after LoopData is up and running. It appears loopdata is up and running and working on the local machine. Have you set up

Re: [weewx-user] Questions about weewx-loopdata

its correct i have remote server. in remote server uploading the loop-data.txt but uploadind every 5 minutes . Στις Τρίτη, 26 Ιανουαρίου 2021 στις 6:20:42 μ.μ. UTC+2, ο χρήστης jo...@johnkline.com έγραψε: > OK, the behavior we are seeing leads me to believe your web server is on a > remote

Re: [weewx-user] Questions about weewx-loopdata

OK, the behavior we are seeing leads me to believe your web server is on a remote machine; i.e., not on the same machine as weewx. Is that correct? If so, you’ll need to use rsync by filling out and enabling it under: [LoopData] [[RsyncSpec]] > On Jan 26, 2021, at 7:57 AM, Δημήτρης

Re: [weewx-user] Questions about weewx-loopdata

well the actuall /loopdata localhost/weewx/loopdata , refreshing every 60 seconds its ok. but in weather page refreshing every 5 minutes Στις Τρίτη, 26 Ιανουαρίου 2021 στις 5:45:32 μ.μ. UTC+2, ο χρήστης jo...@johnkline.com έγραψε: > Again, how often does your driver write loop records? >

Re: [weewx-user] Questions about weewx-loopdata

Again, how often does your driver write loop records? loop-data.txt is not written in reporting cycles. I am asking you to look at the actual loop-data.txt file that is written to the .../loopdata directory. How often does the contents of that file change. Also, please show what entries you

Re: [weewx-user] Questions about weewx-loopdata

loop-data.txt updates every 5 minutes in web page. but in log see loop-data.txt every 60 secs Στις Τρίτη, 26 Ιανουαρίου 2021 στις 5:19:17 μ.μ. UTC+2, ο χρήστης jo...@johnkline.com έγραψε: > How often does your driver write loop records? > Would you please check the actual loop-data.txt file,

Re: [weewx-user] Questions about weewx-loopdata

How often does your driver write loop records? Would you please check the actual loop-data.txt file, rather than the skin’s report, to see if that file is being updated on every loop record? > On Jan 26, 2021, at 7:15 AM, Δημήτρης Βήχος wrote: > > the loop-data.txt > >

Re: [weewx-user] Questions about weewx-loopdata

the loop-data.txt https://kairos.moudania.com/kolxiko/loopdata/ Στις Τρίτη, 26 Ιανουαρίου 2021 στις 5:07:58 μ.μ. UTC+2, ο χρήστης jo...@johnkline.com έγραψε: > > but data refresh every 5 minutes, with the rest skins of weewx > > Exactly what data are you talking about that refreshes every

Re: [weewx-user] Questions about weewx-loopdata

> but data refresh every 5 minutes, with the rest skins of weewx Exactly what data are you talking about that refreshes every five minutes? > On Jan 26, 2021, at 6:02 AM, Δημήτρης Βήχος wrote: > > i was easily installed the loop-data extension yesterday. i use weewx 4.3 > with wh1080 weather

Re: [weewx-user] Questions about weewx-loopdata

i was easily installed the loop-data extension yesterday. i use weewx 4.3 with wh1080 weather station, but data refresh every 5 minutes, with the rest skins of weewx Στις Πέμπτη, 26 Νοεμβρίου 2020 στις 6:46:10 μ.μ. UTC+2, ο χρήστης jo...@johnkline.com έγραψε: > Thanks for letting me know. > >

Re: [weewx-user] Questions about weewx-loopdata

Thanks for letting me know. > On Nov 26, 2020, at 7:32 AM, geoffs...@gmail.com > wrote: > > Hi John, > > Works great. Here is what I added to the loop-data.py > > Line 735 self.ten_min_packets, self.cfg.ten_min_obstypes) > # Added to allow specific null keys if no data

Re: [weewx-user] Questions about weewx-loopdata

Hi John, Works great. Here is what I added to the loop-data.py Line 735 self.ten_min_packets, self.cfg.ten_min_obstypes) # Added to allow specific null keys if no data available in loop packet must_have_keys = [ 'current.dateTime', 'current.extraTemp1.raw',

Re: [weewx-user] Questions about weewx-loopdata

Awesome! This is sort of what I suspected that most use cases, NULL is a problem. I can just hard code the entire Davis loop which will work for my needs. Thanks you, Geoff On Wednesday, November 25, 2020 at 6:45:44 AM UTC-8 jo...@johnkline.com wrote: > In the general case, including keys

Re: [weewx-user] Questions about weewx-loopdata

Hi John, This is a great extension. I'm wondering if there is a way to be able to include sending data that is null or none for a particular key? I'm using a davis vantage pro2, weewx 4.2. I'd like to use this to make a JSON output that can be ingested into a home automation system. So far it

Re: [weewx-user] Questions about weewx-loopdata

A fix is released (v2.7.2). There is no hurry to install the new release; but once you’ve installed it, you can remove the field I asked you to add to weewx.conf. > On Nov 16, 2020, at 9:04 AM, Geni wrote: > > Ok, works > Thank you > > jo...@johnkline.com schrieb am Montag, 16. November

Re: [weewx-user] Questions about weewx-loopdata

Ok, works Thank you jo...@johnkline.com schrieb am Montag, 16. November 2020 um 16:05:21 UTC+1: > I can duplicate this problem and will issue a fix. > > In the meantime, you can add: > rainyear.outTemp.max > to the fields clause in the LoopData section of weewx.conf? > > That will stop this

Re: [weewx-user] Questions about weewx-loopdata

I can duplicate this problem and will issue a fix. In the meantime, you can add: rainyear.outTemp.max to the fields clause in the LoopData section of weewx.conf? That will stop this problem. If you get similar errors for other periods where you have no fields listed, you’ll have to temporarily

[weewx-user] Questions about weewx-loopdata

Hi john since weewx 4.2.0 the loop-data.txt is no longer generated? regards Geni -- 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] Questions about weewx-loopdata 2.x

@John: I installed version 2.6. how do i get the values: -- 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

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

That slipped through in the upgrade section. Yes, you want trend.barometer.formatted if you are looking if you don’t want a label. (Use trend.barometer if you want a label.) I’ll fix that in the upgrade section today (or just remove the upgrade section.) > On Jul 20, 2020, at 12:23 AM,

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Hi John, since version 2.0.b8 the display works as expected. I have just installed 2.0.b10 and see no difference on the fast. What I don't understand is why the documented field "trend.barometerRate.formatted" does not provide any information in the loop-data.txt. Do I get my information from

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Give 2.0.b7 a spin. trend has now been generalized (as opposed to only working with barometer). It will also honor the time_span configured for the target report. If the numbers don’t look right to you, the last 36 records in the archive table would be more helpful than sending screenshots of

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

I’ve already well on my way to replacing this. Trend will work for all scalar values, not just barometer. The code is done, but I need to add it to the tests. > On Jul 17, 2020, at 11:17 PM, geni08...@gmail.com > wrote: > >  I don't think there are any errors in the database, the

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

I don't think there are any errors in the database, the barometer trend is displayed in my season with a credible value that also matches the value in the index.html from the weatherboard (as documented in the older answer). I also attached the

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

As the documentation states, trend.barometer and 10m.windGust are special cases. In this case, where we are talking about trend.barometer, it is alway the delta from three hours ago and uses archive records to compute the starting reading. Also, it is expressed as a per hour rate. Thus, it

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

I’m not sure which parts of Bechlertown rely on MQTT and which parts rely on auto refreshing the page. For the former, if the info is available in LoopData, you would need to add an id to the HTML element and then set the contents via javascript in the same way as WeatherBoard does it.

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Cool. This is looking good: https://livewetter.hcpeters.de/ > On Jul 16, 2020, at 2:53 PM, 'hctp...@googlemail.com' via weewx-user > wrote: > > John, > > I think you are right as there a many processes writing files on and on to > disk... > But it took me 20sec to move the loop-data.txt

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

John, I think you are right as there a many processes writing files on and on to disk... But it took me 20sec to move the loop-data.txt to tempfs! So I did just for fun: changed loop_data_dir = /dev/shm and made a softlink in the weatherboard html dir: *loop-data.txt* ->

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Hi John, Thank you for your help so far, my next goal is to update the Belchertown template with weewx-loopdata. MQTT needs an infrastructure there ... I find your solution really elegant. Do you have a tip for me where to start? jo...@johnkline.com schrieb am Donnerstag, 16. Juli 2020 um

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

It looks like you are on a roll! I think you are asking why I don’t have the actual values filled in for windGust in the template. The answer for $10m.windGust.max is that the $10m period is only understood by LoopData. If you put $10m.windGust.max in the template, it would cause an error.

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Thanks for sending those links. Again, I don’t think it’s necessary to move the file to ram disk. With modern SSDs and wear leveling, and especially with a file this size. You might want to do some web searches before deciding if its worth the effort. > On Jul 15, 2020, at 1:14 PM,

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

John, so maybe a project for the next days to put the loop-data.tx into ram and serve it via apache2. The WeatherBoard site: https://livewetter.hcpeters.de and my main weather site: https://wetter.hcpeters.de/ . The gauges you see on the main site seems to use Javascript so that's why I

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

I do not personally regard it as a problem. Others may have a different opinion. It certainly is not necessary to have it on the SSD, but you would have to configure apache2 (or whatever web server you are using), to be able to serve loop-data.txt. BTW, is your site visible externally? If

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

John, is this a problem to write the loop-data.txt file every 2sec on a SSD regarding durability!? Or would it be better to place it on a ramdisk (tmpfs) like /dev/shm ... Regards, Christian jo...@johnkline.com schrieb am Mittwoch, 15. Juli 2020 um 21:35:27 UTC+2: > Great news! > > The

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Great news! The purpose of LoopData is to be able to add to any skin, but it does require knowledge of JavaScript. > On Jul 15, 2020, at 12:33 PM, John Kline wrote: > >  >  > tail -f loop-data.txt won’t work because a new file is created on every loop. > > You can use: > watch cat

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

tail -f loop-data.txt won’t work because a new file is created on every loop. You can use: watch cat loop-data.txt You screen shots are not of any javascript errors that might be on the page. Would you send me the following file? /var/www/html/weewx/weatherboard/index.html >> On Jul 15, 2020,

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

John, the path was wrong, you were right all the time. The loop-data.txt must be placed into the weatherboard html dir! Now found the java console in Safari and it gives me the error with the wrong path! Now it updates and runs fine! Would be nice to add the live functionality in any skin but

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

ok...last post for now...maybe this is the problem, see screenshot... hctp...@googlemail.com schrieb am Mittwoch, 15. Juli 2020 um 20:54:42 UTC+2: > ...and the error form the browser after changes as screenshot > > hctp...@googlemail.com schrieb am Mittwoch, 15. Juli 2020 um 20:49:18 >

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Ok, cat /var/www/html/weewx/loop-data.txt {"current.dateTime.raw": 1594838795, "current.windDir.ordinal_compass": "NW", "day.rain.sum": "3,0 mm", "current.dewpoint": "8,9\u00b0C", "current.outTemp": "16,7\u00b0C", "current.rainRate": "0,0 mm/h", "current.windSpeed": "3,2 km/h",

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Also, please add all of the fields required by WeatherBoard (see the README). current.dateTime.raw current.windDir.ordinal_compass day.rain.sum current.dewpoint current.outTemp current.rainRate current.windSpeed current.windSpeed.raw 10m.windGust.max day.windGust.max You are missing

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

 Hi Christian, wee_extension should not have been using python2 if you did a python3 install of weewx; but let’s put that aside. Of course, you should care that WeatherBoard is not updating on every loop cycle, that’s the whole point of it. I might be better if you deleted all you have done

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

John, I struggeld installing the extension. I got: Traceback (most recent call last): File "/usr/share/weewx/wee_extension", line 13, in import weecfg.extension File "/usr/share/weewx/weecfg/__init__.py", line 22, in import configobj ImportError: No module named configobj ..but the

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

That's correct, I have a problem understanding the JavaScript entries and the WeatherBord template. I started again with the original files. As soon as I make the smallest change, the wind update no longer works. I work with Notepad++ and then copy the file into the skin folder via the console.

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

 You need to be care as to how you state things. I can clearly see that you have added current.inHumidity to LoopData and you show that it is appearing correctly in the loop-data.txt. inHumidity is not part of the WeatherBoard skin. You have added it. You have a JavaScript error that says

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Hi Christian, Please let me know what was tricky about installing loop-data. Since you are getting loop-data, I suspect that the LoopData extension and the WeatherBoard extension don’t agree about where to find the loop-data.txt file. Would you send both the LoopData section and the

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

John, I just installed the loop-data extension and the weatherboard skin to give it a try. :-) A really nice extension. It was a bit tricky to install it but I hope loop-data is running. I get this /var/www/html/weewx/loop-data.txt file with this text: {"current.dateTime.raw": 1594814866,

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Of course inHumidity is not defined. You need to read the doc and specifically the part about upgrading. inHumidity is now current.inHumidity.formatted It’s in the doc. Also, why are you using 2.0.b3? Please use the latest on master as I’ve merged it in. It is 2.0.b6 (which happens to be

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

@John: WeaterBoard 2.0b3 causes problems. everything worked until the time with the old version. With version 2 I get the error: Uncaught ReferenceError: inHumidity is not defined, and refreshing doesn't seem to work properly. The syntax also seems different? I'll test that with

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

It looks like you are missing the following in the fields line: current.dateTime.raw That is, to upgrade, dateTime needs to be changed to current.dateTime.raw I’ll update the How to Upgrade section to reflect that. > On Jul 14, 2020, at 6:01 AM, Geni 0815 wrote: > >  > @John: I installed

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

@John: I installed version 2.0.b6, almost everything worked right away, congratulations. What is not yet running is the label: Live and the clock at the bottom right. Am Freitag, 10. Juli 2020 20:09:30 UTC+2 schrieb John Kline: > > I had a look. You never actually write FMT_windDir in the

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Of course, loop-data.txt is not created with all fields. It would be huge. Rather, it is created with the fields you specify in the LoopData fields line in weewx.conf. The equivalent of $current.barometer in LoopData is barometer. You don’t specify that field. Instead, you specify

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

The loop-data.txt file is not created with all fields! The entry: $current.barometer ($trend.barometer.formatted) in the index.html.tmpl results in the correct formatting. jo...@johnkline.com schrieb am Freitag, 10. Juli 2020 um 20:09:30 UTC+2: > I had a look. You never actually write

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

I had a look. You never actually write FMT_windDir in the JavaScript. Just add: + ‘ (‘ + result[‘FMT_windDir’] + ‘)’ on the appropriate line in realtime_updater.inc. As for barometerRate. I do see it. I just spills over to the next line. It looks like I am not properly formatting

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Hi John, I'm on the mountain, there was more. Can you please keep an eye on the two files? jo...@johnkline.com schrieb am Freitag, 10. Juli 2020 um 16:05:18 UTC+2: > You need to add the fields: > barometerRate > FMT_windDir > to the fields line in the LoopData section of weewx.conf. > > After

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

You need to add the fields: barometerRate FMT_windDir to the fields line in the LoopData section of weewx.conf. After you do that and restart WeeWX, verify that you see these readings in loop-data.txt. Finally, you need to set these values in the JavaScript. If you have already done all of the

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

>> On Jul 9, 2020, at 1:52 AM, geni08...@gmail.com >> wrote: > Question for my understanding: > If or why is the id = string supplemented with $current, $day or not at all? > In the examples, no IDs is supplemented with current, day or none at all. Some values say $current, which means

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Question for my understanding: If or why is the id = string supplemented with $current, $day or not at all? [image: loop1.jpg] jo...@johnkline.com schrieb am Mittwoch, 8. Juli 2020 um 20:35:22 UTC+2: > > > On Jul 8, 2020, at 1:36 AM, geni08...@gmail.com > wrote: > >  weewx-weatherboard 1.3a

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

> On Jul 8, 2020, at 1:36 AM, geni08...@gmail.com > wrote: > >  weewx-weatherboard 1.3a the label entries are implemented. > What is the easiest way now > Indoor temperature > barometer > Indoor and outdoor humidity > to show signs on the display? To get these readings in loop-data.txt,

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

weewx-weatherboard 1.3a the label entries are implemented. What is the easiest way now Indoor temperature barometer Indoor and outdoor humidity to show signs on the display? jo...@johnkline.com schrieb am Dienstag, 7. Juli 2020 um 20:10:24 UTC+2: > Most of the WeatherBoard will now use the

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

no error in the log file, and weewx-loopdate has mastered midnight. I will look at weewx-weatherboard in a moment jo...@johnkline.com schrieb am Dienstag, 7. Juli 2020 um 20:10:24 UTC+2: > Most of the WeatherBoard will now use the strings in Defaults, so you > should see it in German after you

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Most of the WeatherBoard will now use the strings in Defaults, so you should see it in German after you install. For the custom strings, just update the strings in the WeatherBoard>Labels>Generic section of weewx.conf. > On Jul 7, 2020, at 6:47 AM, John Kline wrote: > >  > I’ve created a

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

I’ve created a branch of WeatherBoard that substitutes appTemp for dewpoint. It is here: https://github.com/chaunceygardiner/weewx-weatherboard/tree/appTemp > On Jul 7, 2020, at 12:09 AM, John Kline wrote: > >  > There was a subtle difference in how I was creating the next day accumulator >

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

There was a subtle difference in how I was creating the next day accumulator vs. how WeeWX proper is doing it. I’ve changed that. Please install 1.3.15 and let me know how it goes at midnight. > On Jul 6, 2020, at 10:44 PM, geni08...@gmail.com > wrote: > > Jul 7 00:00:01 Wetter-Raspi

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Jul 7 00:00:01 Wetter-Raspi rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="295" x-info="https://www.rsyslog.com;] rsyslogd was HUPed Jul 7 00:00:01 Wetter-Raspi systemd[1]: logrotate.service: Succeeded. Jul 7 00:00:01 Wetter-Raspi systemd[1]: Started Rotate log files. Jul

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Jul 7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: Traceback (most recent call last): Jul 7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: File "/usr/share/weewx/user/loopdata.py", line 365, in process_queue Jul 7 00:00:00 Wetter-Raspi

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

It looks like loopdata stopped again at midnight (I looked at your sight). I think it likely that something in the packet at midnight is causing this. Loopdata does print a stack trace on an unexpected exception before exiting. Would you have a look in the log and send it? If the stack trace

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

BTW, I should probably make dewpoint position on the weatherboard configurable between dewpoint and appTemp. That would save you from having to hack on the javaascript. Also, I could make the legend configurable for translation. I’ll try to do that today or tomorrow. > On Jul 6, 2020, at

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Yep, you’ll need to make your changes to switch to appTemp. That’s both a change in index.html.tmpl and in the realtime_updater.inc file. A new day accumulator gets created at midnight, so I am very interested in that loopdata crash. Do you have a stacktrace in the log? Please send what you

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

I have replaced the index.html.tmpl with an old version! However, the appTemp is not yet running. Loopdate also crashed at midnight, so watch that today. jo...@johnkline.com schrieb am Montag, 6. Juli 2020 um 15:50:11 UTC+2: > Now that I’m up for the morning, I went to look at your

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Now that I’m up for the morning, I went to look at your WeatherBoard page to see what the JavaScript error was, but I see that it is up and runnning! > On Jul 6, 2020, at 3:44 AM, John Kline wrote: > >  > Send realtime_updater.inc and weewx.conf. > The JavaScript is broken. I’ll have a look.

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Send realtime_updater.inc and weewx.conf. The JavaScript is broken. I’ll have a look. > On Jul 5, 2020, at 10:35 PM, geni08...@gmail.com > wrote: > > I have weewx-loopdata 1.1.13, only the default km_per_hour definition -> the > loop-data.txt is OK. > Why is my WeatherBoard not working? Only

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

I have weewx-loopdata 1.1.13, only the default km_per_hour definition -> the loop-data.txt is OK. Why is my WeatherBoard not working? Only time is running. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

1.3.9 has been pushed. I would appreciate it if you would remove the lines I asked you to add so that you can test that this is no longer needed. >>> >>> [[[Units]]] >>> Labels >>> km_per_hour = " km/h" >> On Jul 5, 2020, at 7:08 AM, John Kline

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

OK, I see what I need to do. 1.3.9 will fix this. Life calls at present, but I’ll fix and push within a few hours. In the meantime, the change below will get you get you km/h will tide you over. BTW, thank you for trying this extension. You have identified quite a few problems and I

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Not too interesting. I see it on the WeatherBoard report here: https://affolter.familyds.net/wetter/weatherboard/ You no longer are producing it, but the JavaScript is happily fetching the latest values. As for why you don’t see km/h, I obviously am not managing the dictionaries correctly. I

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

Now it gets interesting, where do you see kph on my season page? Am Sonntag, 5. Juli 2020 14:18:00 UTC+2 schrieb John Kline: > > That’s great that you are up and running. I had a look at your > WeatherBoard report and indeed I see kph. > > I just tried this myself. I targeted SeasonsReport

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

That’s great that you are up and running. I had a look at your WeatherBoard report and indeed I see kph. I just tried this myself. I targeted SeasonsReport (since that is what you did) and added the km/h and it’s working for me. Let’s compare our SeasonsReport entries. I have the

[weewx-user] Questions about weewx-loopdata 1.3.x

@John: I have new installed the weewx-loopdata here my settings in weewx.conf. In my SeasonsReport the field *km_per_hour *is correctly displayed with km/h. appended a loop_data.txt and kph is still in it. How does your built-in tests