Re: [weewx-user] Sunshine Duration

[Ton vanN]

Rereading this thread come to understand that definition/semantics is a 
critical aspect in this discussion.
*Bluntly* summarized:
- Sunshine = seeing difference between lighted area and shadowed area.
Like KarenK's device is doing
- Lightlevel = level of undirected solar radiation, not/hardly 
differentating on wavelength.
Like most light sensors in 'private' PWSes will provide.
- Duration = derivative time-value of one of above, considering the time 
that a specfied threshold level is exceeded, with result expressed as 
accumulating time/day

*Correct understanding?*
If correct, more attention seems needed that nomenclature of variables is 
properly tuned; 
otherwise obvious confusion.
Op zaterdag 4 mei 2024 om 18:17:18 UTC+2 schreef Karen K:

> n7uv...@gmail.com schrieb am Samstag, 4. Mai 2024 um 05:12:04 UTC+2:
>
>
> What is "direct solar irradiance"? Is there someone at the sensor deciding 
> that it's direct? 
>
>
> As Jaques wrote, this is a sensor that sees a very small angle of the sky 
> (approximately half a degree) and it is moving and always looking at the 
> position, where the sun should be seen.
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8ea528a3-45e2-4e6c-ab5f-56665cfa35a1n%40googlegroups.com.

Re: [weewx-user] Sunshine Duration

[Ton vanN]

Looking for a 'proven' calculation for sunshineduration as element of 
WeeWX, see https://github.com/Jterrettaz/sunduration
Shown solution linked to Davis Vantage_Pro.
Different sensors may induce difference in results:
any experiences if linked to Weatherflow_Tempest?

Op zaterdag 26 maart 2022 om 19:41:50 UTC+1 schreef Karen K:

> Now I see it: There is "sum" missing at the end:
>
> $day.sunshine_time.sum
>
>
> Meteo Oberwallis schrieb am Samstag, 26. März 2022 um 19:35:00 UTC+1:
>
>> Hey.
>>
>> Yes. Is in the weewx.sdb. The current sunshine time works. The day 
>> sunshine time not. 
>>
>> Holen Sie sich Outlook für Android 
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3fd60c2b-0677-453b-af2a-9763a7771aefn%40googlegroups.com.

[weewx-user] Extension for Sylphide

[Ton vanN]

VWK (=Vereniging van Weerkundigen) is a Dutch community of 'serious' 
weather observers ( with own website at vwkweb.nl )
Part of the website is generation of weathermaps, obviously needing upload 
of data from members' PWSes. That part of the website is a project called 
Sylphide.
No result when searching in this group, but having WeeWX in operation for 
various other uploads, just wondering whether one of the members of this 
WeeWX-group has an WeeWX-extension to support upload to Sylphide.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/776f51a5-81bc-49fd-b4df-89a645e0826cn%40googlegroups.com.

[weewx-user] Re: The People's Pluviograph!

[Ton vanN]

LoraWAN certainly is a candidate for an airborne link from a sensor to a 
local gateway_to_internet over better distance than with the usual 
meteo-sensors' communication lines. 
SIGFox is a comparable solution for airborne communication over_between 
sensor and gateway-server.
Drawback for both is that they need internet for the next 
communicationsegment from the gateway to the world, 
and in flooded areas that might be a practical handicap, because usually 
cables running from the gateway to the next service-contact.

Another option is to apply GSM, best 2G-version (if still available), 
because that has longest linking range.
With a compatible Mifi-router it is possible to link the sensor airborne 
over wifi to the mifi-router, with the mifi-router over 2G taking care of 
the next airborne step of communication. 
Mifi-router is a small device usually running on battery, which battery is 
fed over USB-port, making it semi-independent of power-grid etc.
Probably not the most inovative solution, but might in practise be an 
airborne bridge over significant distance until arriving at the big 
internetbackbones.

Op maandag 6 november 2023 om 13:03:06 UTC+1 schreef Greg Hall:

> Record-breaking floods in the Northern Rivers regions of the state of New 
> South Wales in Australia last year has set us looking for a way to report 
> hourly, or more frequent, rainfall intensity, to better inform those 
> downstream.
>
> As the official gauge network is sparse and flaky, our present 'solution' 
> is a few human Rain Sentinels' who live high up in the catchment. They 
> agree to read their gauges hourly and get the readings out, by phone as 
> long as that lasts (not very), then CB radio.
>
> We haven't had much success with off-the-shelf weather stations, but maybe 
> there are WeeWx gurus who would know how to help script such a reporting 
> function.
>
> I've bought a couple of 8" tipping bucket gauges, and am playing with 
> Arduino code to keep daily, tips per minute files, on a local SD card, to 
> be relayed on to a LORA-APRS system (o.n.o), and as last resort, on a local 
> display.
>
> Any guidance or assistance very welcome.
>
> Greg
> VK2GTH
> -
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3d50653a-90ec-4073-b7e6-c811e97e35d9n%40googlegroups.com.

Re: [weewx-user] Re: How to revive 'frozen' WeeWX?

[Ton vanN]

Is surprisingly effective remedy:
all files now significantly smaller and WeeWX running smoothly.
But 'digging' to find root-cause for this unpleasant 'growing'.

Op donderdag 19 oktober 2023 om 19:08:55 UTC+2 schreef vince:

> Do a "sudo rm daemon.log.1 debug.1 kern.log.1 user.log.1" to get 
> immediate relief.
>
> Then look at the daemon.log, debug, kern.log, and user.log files that 
> remain to see what is in them.  This is very unusual. You have something in 
> your os that is logging something you need to investigate.Even if you 
> do a "tail -n 20" of each file it will help you determine what is 
> happening.
>
>
> On Thursday, October 19, 2023 at 5:15:18 AM UTC-7 Ton vanN wrote:
>
> *raspberrypi9:~ $ *ls -al /var/log
>
> -rwxrwxr-x  1 root adm 89212455 okt 19 00:00 auth.log.1
>
> -rwxrwxr-x  1 root adm113695224 okt 19 14:06 daemon.log
> -rwxrwxr-x  1 root adm  23122752257 okt 19 00:00 daemon.log.1
> -rw-r-  1 root adm  2756977 okt 19 14:05 debug
> -rw-r-  1 root adm   1048983611 okt 18 23:55 debug.1
>
> -rwxrwxr-x  1 root adm 13796027 okt 18 20:31 kern.log.1
>
> -rw-r-  1 root adm119656811 okt 19 00:00 messages.1
>
> -rw-r-  1 root adm196420717 okt 19 00:00 syslog.1
>
> -rwxrwxr-x  1 root adm  3022087 okt 19 14:05 user.log
> -rwxrwxr-x  1 root adm   1175652544 okt 18 23:55 user.log.1
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/eccba3b5-d929-4845-b635-f6bc4b9f07f6n%40googlegroups.com.

Re: [weewx-user] Re: How to revive 'frozen' WeeWX?

[Ton vanN]

Vince,

Since more than 10 years retired from professional day-to-day Linux 
applications, 
indeed some of my knowledge of Linux has faded, if not vaporated . 

As requested, ran the suggested CLI with results shown below

*raspberrypi9:~ $ *ls -al /var/log
totaal 25394612
drwxr-xr-x  7 root root4096 okt 19 00:00 .
drwxr-xr-x 11 root root4096 okt 14 11:52 ..
-rwxrwxr-x  1 root root   0 jul 24 00:00 alternatives.log
drwxr-xr-x  2 root root4096 jul 24 00:00 apt
-rwxrwxr-x  1 root adm   283792 okt 19 14:06 auth.log
-rwxrwxr-x  1 root adm 89212455 okt 19 00:00 auth.log.1
-rwxrwxr-x  1 root root  170555 okt 14 11:52 boot.log
-rwxrwxr-x  1 root root   0 sep 26  2019 bootstrap.log
-rw-rw  1 root utmp   0 okt  1 00:00 btmp
drwxr-xr-x  2 root root4096 okt 19 00:00 cups
-rwxrwxr-x  1 root adm113695224 okt 19 14:06 daemon.log
-rwxrwxr-x  1 root adm  23122752257 okt 19 00:00 daemon.log.1
-rw-r-  1 root adm  2756977 okt 19 14:05 debug
-rw-r-  1 root adm   1048983611 okt 18 23:55 debug.1
-rwxrwxr-x  1 root root   0 jul 24 00:00 dpkg.log
-rw-r--r--  1 root root2784 feb 12  2023 faillog
-rwxrwxr-x  1 root root2847 dec  4  2022 fontconfig.log
drwxr-xr-x  3 root root4096 dec  4  2022 hp
-rwxrwxr-x  1 root adm  818 okt 19 13:00 kern.log
-rwxrwxr-x  1 root adm 13796027 okt 18 20:31 kern.log.1
-rw-rw-r--  1 root utmp  292292 okt 19 14:04 lastlog
drwx--x--x  2 root root4096 okt 14 11:52 lightdm
-rw-r-  1 root adm   265264 okt 19 14:05 messages
-rw-r-  1 root adm119656811 okt 19 00:00 messages.1
drwx--  2 root root4096 sep 26  2019 private
-rw-r-  1 root adm116739711 okt 19 14:06 syslog
-rw-r-  1 root adm196420717 okt 19 00:00 syslog.1
-rw-r-  1 root adm   228016 okt 18 00:00 syslog.2.gz
-rwxrwxr-x  1 root adm  3022087 okt 19 14:05 user.log
-rwxrwxr-x  1 root adm   1175652544 okt 18 23:55 user.log.1
-rwxrwxr-x  1 root adm0 feb 16  2019 vsftpd.log
-rwxrwxr-x  1 root adm  304 jul 25 17:34 vsftpd.log.2
-rwxrwxr-x  1 root adm  304 jul  5 17:06 vsftpd.log.3
-rwxrwxr-x  1 root adm  304 jun 20 13:59 vsftpd.log.4
-rw-rw-r--  1 root utmp  162048 okt 19 14:04 wtmp
-rw-r--r--  1 root root8703 okt 14 11:52 Xorg.0.log
-rw-r--r--  1 root root8775 feb 17  2019 Xorg.0.log.old

Op woensdag 18 oktober 2023 om 23:49:32 UTC+2 schreef cric...@pobox.com:

> This might be a bit more comprehensive:
> > sudo find / -xdev -size +100 -ls
>
> This will report any "large" files.  If I'm reading the manpage correctly, 
> the number is the count of 512 byte
> blocks by default, so you can fiddle with the number and/or tack on a 
> scale character.  See "man find" and see
> the options for the -size test.
>
> The sudo prevents permissions warnings.
>
> Chris
> On Wednesday, October 18, 2023 at 11:47:04 AM UTC-6 vince wrote:
>
>> I know we have a language issue here, but I think you might need a little 
>> Linux training too.
>>
>> We have already established that your /var/log directory is filling up. 
>>  That is very unusual.  You need to determine what is causing the big logs.
>>
>> Please run the following and provide the output:
>> ls -al /var/log
>>
>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a438179c-7102-46c7-90fe-ad09850118d7n%40googlegroups.com.

Re: [weewx-user] Re: How to revive 'frozen' WeeWX?

[Ton vanN]

After removal of .1-files and .gz-files for checking reran df, showing

Bestandssysteem 1K-blokken Gebruikt Beschikbaar Geb% Aangekoppeld op
/dev/root 30358348 28786676  287176 100% /
devtmpfs4394000  439400   0% /dev
tmpfs   4726800  472680   0% /dev/shm
tmpfs   47268047796  424884  11% /run
tmpfs 512045116   1% /run/lock
tmpfs   4726800  472680   0% /sys/fs/cgroup
/dev/mmcblk0p1  25809549395  208700  20% /boot
tmpfs945364   94532   1% /run/user/1000

/dev/root at 100% occupancy does not seem healthy, and breeding new 
problems  ...

Op dinsdag 17 oktober 2023 om 22:15:54 UTC+2 schreef vince:

> Just delete the big logs from /var/log and reboot - that's all you need to 
> do.
>
> With you providing no data on which files in /var/log are the big ones, no 
> we can't help you much.
>
> On Tuesday, October 17, 2023 at 1:13:19 PM UTC-7 Ton vanN wrote:
>
>> Was on wrong leg, assuming KBs .
>> Unpleasant surprise, which seems to lead to conclusion that this install 
>> cannot be saved, but new start required.
>> What is best practical approach to make new, small configuration while 
>> 'borrowing' from the old configuration the sdb-file and various conf-files?
>> Somewhere a description for that kind of clean-up/restart?
>>
>> Obviously keen to avoid the 'error' that lead to this 'saturated' install:
>> any hint?
>>
>> Op dinsdag 17 oktober 2023 om 13:06:53 UTC+2 schreef Tom Keffer:
>>
>>> The "-m" option to du means that sizes are in *megabytes*. Your 
>>> /var/log directory has 26 *gigabytes* in it.
>>>
>>> On Tue, Oct 17, 2023 at 2:12 AM Ton vanN  wrote:
>>>
>>>> Vince,
>>>> The results of the suggested checks.
>>>>
>>>> *raspberrypi9*:~ $ sudo du -sm /var/log
>>>> 25977   /var/log
>>>> *raspberrypi9:~ $ *sudo du -sm /tmp
>>>> 1   /tmp
>>>> *raspberrypi9:~ $* sudo du -sm /home/pi
>>>> 53  /home/pi
>>>> *raspberrypi9:~ $* sudo du -sm /var/tmp
>>>> 1   /var/tmp
>>>>
>>>> IMHO contents of checked files are minimal 
>>>> Wondering why /dev/root full, with this Raspberry only running WeeWX 
>>>> plus 2 auxiliary Python-scripts (sized 2KB and 1KB), serving periodic 
>>>> upload of weewx.sdb to a remote, backup server
>>>>
>>>> Guessing/speculation:
>>>> might expansion of the file system (via raspi-config) have had some 
>>>> effects?
>>>> Op maandag 16 oktober 2023 om 20:58:56 UTC+2 schreef vince:
>>>>
>>>>> Your / partition is full. You have 29G Size and 29G Used and 0 
>>>>> Available.
>>>>>
>>>>> *raspberrypi9:~ $* df -h
>>>>> Bestandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op
>>>>> /dev/root   29G  29G 0 100% /
>>>>> devtmpfs   430M0  430M   0% /dev
>>>>> tmpfs  462M0  462M   0% /dev/shm
>>>>> tmpfs  462M  47M  415M  11% /run
>>>>> tmpfs  5,0M 4,0K  5,0M   1% /run/lock
>>>>> tmpfs  462M0  462M   0% /sys/fs/cgroup
>>>>> /dev/mmcblk0p1 253M  49M  204M  20% /boot
>>>>> tmpfs   93M0   93M   0% /run/user/1000
>>>>>
>>>>> Check your /var/log partition to see what its size is:
>>>>>
>>>>> sudo du -sm /var/log
>>>>>
>>>>> If it is not many GB, check your /home/pi and /tmp and /var/tmp 
>>>>> directories the same way.
>>>>>
>>>>>
>>>>> -- 
>>>> 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.
>>>>
>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/2311e7cb-34e4-40f2-a659-5463b414dffcn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/2311e7cb-34e4-40f2-a659-5463b414dffcn%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1bd57962-bd79-4007-a403-b2f915e3de54n%40googlegroups.com.

Re: [weewx-user] Re: How to revive 'frozen' WeeWX?

[Ton vanN]

Vince,

As advised, deleted all .1-files and .gz-files to make space an for clean-up
Back in operation, but still pensive on the daemon.log which has a size of 
22.649875 KB
Is that 'healthy', or should it be reduced in some way as precaution 
against new 'saturation'?

Op dinsdag 17 oktober 2023 om 22:15:54 UTC+2 schreef vince:

> Just delete the big logs from /var/log and reboot - that's all you need to 
> do.
>
> With you providing no data on which files in /var/log are the big ones, no 
> we can't help you much.
>
> On Tuesday, October 17, 2023 at 1:13:19 PM UTC-7 Ton vanN wrote:
>
>> Was on wrong leg, assuming KBs .
>> Unpleasant surprise, which seems to lead to conclusion that this install 
>> cannot be saved, but new start required.
>> What is best practical approach to make new, small configuration while 
>> 'borrowing' from the old configuration the sdb-file and various conf-files?
>> Somewhere a description for that kind of clean-up/restart?
>>
>> Obviously keen to avoid the 'error' that lead to this 'saturated' install:
>> any hint?
>>
>> Op dinsdag 17 oktober 2023 om 13:06:53 UTC+2 schreef Tom Keffer:
>>
>>> The "-m" option to du means that sizes are in *megabytes*. Your 
>>> /var/log directory has 26 *gigabytes* in it.
>>>
>>> On Tue, Oct 17, 2023 at 2:12 AM Ton vanN  wrote:
>>>
>>>> Vince,
>>>> The results of the suggested checks.
>>>>
>>>> *raspberrypi9*:~ $ sudo du -sm /var/log
>>>> 25977   /var/log
>>>> *raspberrypi9:~ $ *sudo du -sm /tmp
>>>> 1   /tmp
>>>> *raspberrypi9:~ $* sudo du -sm /home/pi
>>>> 53  /home/pi
>>>> *raspberrypi9:~ $* sudo du -sm /var/tmp
>>>> 1   /var/tmp
>>>>
>>>> IMHO contents of checked files are minimal 
>>>> Wondering why /dev/root full, with this Raspberry only running WeeWX 
>>>> plus 2 auxiliary Python-scripts (sized 2KB and 1KB), serving periodic 
>>>> upload of weewx.sdb to a remote, backup server
>>>>
>>>> Guessing/speculation:
>>>> might expansion of the file system (via raspi-config) have had some 
>>>> effects?
>>>> Op maandag 16 oktober 2023 om 20:58:56 UTC+2 schreef vince:
>>>>
>>>>> Your / partition is full. You have 29G Size and 29G Used and 0 
>>>>> Available.
>>>>>
>>>>> *raspberrypi9:~ $* df -h
>>>>> Bestandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op
>>>>> /dev/root   29G  29G 0 100% /
>>>>> devtmpfs   430M0  430M   0% /dev
>>>>> tmpfs  462M0  462M   0% /dev/shm
>>>>> tmpfs  462M  47M  415M  11% /run
>>>>> tmpfs  5,0M 4,0K  5,0M   1% /run/lock
>>>>> tmpfs  462M0  462M   0% /sys/fs/cgroup
>>>>> /dev/mmcblk0p1 253M  49M  204M  20% /boot
>>>>> tmpfs   93M0   93M   0% /run/user/1000
>>>>>
>>>>> Check your /var/log partition to see what its size is:
>>>>>
>>>>> sudo du -sm /var/log
>>>>>
>>>>> If it is not many GB, check your /home/pi and /tmp and /var/tmp 
>>>>> directories the same way.
>>>>>
>>>>>
>>>>> -- 
>>>> 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.
>>>>
>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/2311e7cb-34e4-40f2-a659-5463b414dffcn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/2311e7cb-34e4-40f2-a659-5463b414dffcn%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/67e08b55-cdd2-4408-a0fd-2d622f09283en%40googlegroups.com.

Re: [weewx-user] Re: How to revive 'frozen' WeeWX?

[Ton vanN]

Was on wrong leg, assuming KBs .
Unpleasant surprise, which seems to lead to conclusion that this install 
cannot be saved, but new start required.
What is best practical approach to make new, small configuration while 
'borrowing' from the old configuration the sdb-file and various conf-files?
Somewhere a description for that kind of clean-up/restart?

Obviously keen to avoid the 'error' that lead to this 'saturated' install:
any hint?

Op dinsdag 17 oktober 2023 om 13:06:53 UTC+2 schreef Tom Keffer:

> The "-m" option to du means that sizes are in *megabytes*. Your /var/log 
> directory has 26 *gigabytes* in it.
>
> On Tue, Oct 17, 2023 at 2:12 AM Ton vanN  wrote:
>
>> Vince,
>> The results of the suggested checks.
>>
>> *raspberrypi9*:~ $ sudo du -sm /var/log
>> 25977   /var/log
>> *raspberrypi9:~ $ *sudo du -sm /tmp
>> 1   /tmp
>> *raspberrypi9:~ $* sudo du -sm /home/pi
>> 53  /home/pi
>> *raspberrypi9:~ $* sudo du -sm /var/tmp
>> 1   /var/tmp
>>
>> IMHO contents of checked files are minimal 
>> Wondering why /dev/root full, with this Raspberry only running WeeWX plus 
>> 2 auxiliary Python-scripts (sized 2KB and 1KB), serving periodic upload of 
>> weewx.sdb to a remote, backup server
>>
>> Guessing/speculation:
>> might expansion of the file system (via raspi-config) have had some 
>> effects?
>> Op maandag 16 oktober 2023 om 20:58:56 UTC+2 schreef vince:
>>
>>> Your / partition is full. You have 29G Size and 29G Used and 0 
>>> Available.
>>>
>>> *raspberrypi9:~ $* df -h
>>> Bestandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op
>>> /dev/root   29G  29G 0 100% /
>>> devtmpfs   430M0  430M   0% /dev
>>> tmpfs  462M0  462M   0% /dev/shm
>>> tmpfs  462M  47M  415M  11% /run
>>> tmpfs  5,0M 4,0K  5,0M   1% /run/lock
>>> tmpfs  462M0  462M   0% /sys/fs/cgroup
>>> /dev/mmcblk0p1 253M  49M  204M  20% /boot
>>> tmpfs   93M0   93M   0% /run/user/1000
>>>
>>> Check your /var/log partition to see what its size is:
>>>
>>> sudo du -sm /var/log
>>>
>>> If it is not many GB, check your /home/pi and /tmp and /var/tmp 
>>> directories the same way.
>>>
>>>
>>> -- 
>> 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.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/2311e7cb-34e4-40f2-a659-5463b414dffcn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/2311e7cb-34e4-40f2-a659-5463b414dffcn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7c457f45-f402-42b4-ad0e-2b0b3d7b55acn%40googlegroups.com.

[weewx-user] Re: How to revive 'frozen' WeeWX?

[Ton vanN]

Vince,
The results of the suggested checks.

*raspberrypi9*:~ $ sudo du -sm /var/log
25977   /var/log
*raspberrypi9:~ $ *sudo du -sm /tmp
1   /tmp
*raspberrypi9:~ $* sudo du -sm /home/pi
53  /home/pi
*raspberrypi9:~ $* sudo du -sm /var/tmp
1   /var/tmp

IMHO contents of checked files are minimal 
Wondering why /dev/root full, with this Raspberry only running WeeWX plus 2 
auxiliary Python-scripts (sized 2KB and 1KB), serving periodic upload of 
weewx.sdb to a remote, backup server

Guessing/speculation:
might expansion of the file system (via raspi-config) have had some effects?
Op maandag 16 oktober 2023 om 20:58:56 UTC+2 schreef vince:

> Your / partition is full. You have 29G Size and 29G Used and 0 
> Available.
>
> *raspberrypi9:~ $* df -h
> Bestandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op
> /dev/root   29G  29G 0 100% /
> devtmpfs   430M0  430M   0% /dev
> tmpfs  462M0  462M   0% /dev/shm
> tmpfs  462M  47M  415M  11% /run
> tmpfs  5,0M 4,0K  5,0M   1% /run/lock
> tmpfs  462M0  462M   0% /sys/fs/cgroup
> /dev/mmcblk0p1 253M  49M  204M  20% /boot
> tmpfs   93M0   93M   0% /run/user/1000
>
> Check your /var/log partition to see what its size is:
>
> sudo du -sm /var/log
>
> If it is not many GB, check your /home/pi and /tmp and /var/tmp 
> directories the same way.
>
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2311e7cb-34e4-40f2-a659-5463b414dffcn%40googlegroups.com.

[weewx-user] Re: How to revive 'frozen' WeeWX?

[Ton vanN]

Correction related to RAM-filing system:
folder /var/tmp/ is present, but completely empty, where expecting at least 
a tmpfs ...
Checking on /etc/fstab miss the additions as described at 
https://domoticproject.com/extending-life-raspberry-pi-sd-card/#Mounting_Filesystems_in_RAM_Disk
Seems to imply that no RAM-filing system has been activated for this 
Raspberry.

Additional info:
file /home/weewx/archive/weewx.sdb has size of 41.956 KB
Op maandag 16 oktober 2023 om 09:05:07 UTC+2 schreef Ton vanN:

> Question of Vince triggers other observation.
> Subject Raspberry should have a RAM-fs, but when viewing the folders, 
> don’t find /var/tmp and it’s subfolders.
> Sign for corruption?
>
> Op maandag 16 oktober 2023 om 00:58:30 UTC+2 schreef Greg from Oz:
>
>> What does df -i show?
>> You could have run out of inodes.
>>
>> On Monday, 16 October 2023 at 07:58:31 UTC+11 vince wrote:
>>
>>> Lets see the output of "df -h" because it sure sounds like /var or /tmp 
>>> is full...
>>>
>>> On Sunday, October 15, 2023 at 11:45:51 AM UTC-7 Ton vanN wrote:
>>>
>>>> Since WeeWX4.4 available have been using it without much problems 
>>>> running on a Raspberry3B with OS=Raspian_Buster. Memory max. expanded 
>>>> through Raspi-Config.
>>>> Setup of WeeWX to (re)start when (re)booting.
>>>> Occasionally stopping, but either by restart through PuttySSH, or (as 
>>>> last resort) by an 'emergency' hard reset, was always able to restart.
>>>> Most used CLI through PuttySSH is sudo /etc/init.d/weewx restart
>>>> It still happily reports: [ ok ] Restarting weewx (via systemctl): 
>>>> weewx.service
>>>>
>>>> However, this weekend such simple measures did not help, and database 
>>>> and many files stuck/frozen at 14-10-23 10:15:00, while last 
>>>> FTP-upload at 14-1023 22:17:36, but related files all 0kb. Date of 
>>>> that FTP-upload also valid for all external uploads coming from WeeWX.
>>>>
>>>> Fresh reinstall (using copies of latest sdb-file etc.) obviously 
>>>> a pragmatic remedy, 
>>>> but would shorter route be available to revive this existing 
>>>> configuration?
>>>>
>>>> Observed 2nd effect: cannot access crontab, getting report that no 
>>>> space left on device.
>>>> But df shows plenty of space
>>>>
>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6497b3a5-875d-42b4-bca6-c5927fcbb7a3n%40googlegroups.com.

[weewx-user] Re: How to revive 'frozen' WeeWX?

[Ton vanN]

@ p q

Which logfile meant? At what location in the WeeWX-folder?

Op maandag 16 oktober 2023 om 13:48:00 UTC+2 schreef Ton vanN:

> Have run 3 variants of df with following results.
>
> *raspberrypi9:~ $* df
> Bestandssysteem 1K-blokken Gebruikt Beschikbaar Geb% Aangekoppeld op
> /dev/root 30358348 30341964   0 100% /
> devtmpfs4394000  439400   0% /dev
> tmpfs   4726800  472680   0% /dev/shm
> tmpfs   47268047740  424940  11% /run
> tmpfs 512045116   1% /run/lock
> tmpfs   4726800  472680   0% /sys/fs/cgroup
> /dev/mmcblk0p1  25809549395  208700  20% /boot
> tmpfs945360   94536   0% /run/user/1000
> *raspberrypi9:~ $* df -i
> Bestandssysteem I-nodes  IGebr   IVrij IGeb% Aangekoppeld op
> /dev/root   1899328 116283 17830457% /
> devtmpfs 109850379  1094711% /dev
> tmpfs118170  1  1181691% /dev/shm
> tmpfs118170523  1176471% /run
> tmpfs118170  3  1181671% /run/lock
> tmpfs118170 15  1181551% /sys/fs/cgroup
> /dev/mmcblk0p10  0   0 - /boot
> tmpfs118170 13  1181571% /run/user/1000
> *raspberrypi9:~ $* df -h
> Bestandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op
> /dev/root   29G  29G 0 100% /
> devtmpfs   430M0  430M   0% /dev
> tmpfs  462M0  462M   0% /dev/shm
> tmpfs  462M  47M  415M  11% /run
> tmpfs  5,0M 4,0K  5,0M   1% /run/lock
> tmpfs  462M0  462M   0% /sys/fs/cgroup
> /dev/mmcblk0p1 253M  49M  204M  20% /boot
> tmpfs   93M0   93M   0% /run/user/1000
> *raspberrypi9:~ $*
>
> Op maandag 16 oktober 2023 om 09:05:07 UTC+2 schreef Ton vanN:
>
>> Question of Vince triggers other observation.
>> Subject Raspberry should have a RAM-fs, but when viewing the folders, 
>> don’t find /var/tmp and it’s subfolders.
>> Sign for corruption?
>>
>> Op maandag 16 oktober 2023 om 00:58:30 UTC+2 schreef Greg from Oz:
>>
>>> What does df -i show?
>>> You could have run out of inodes.
>>>
>>> On Monday, 16 October 2023 at 07:58:31 UTC+11 vince wrote:
>>>
>>>> Lets see the output of "df -h" because it sure sounds like /var or /tmp 
>>>> is full...
>>>>
>>>> On Sunday, October 15, 2023 at 11:45:51 AM UTC-7 Ton vanN wrote:
>>>>
>>>>> Since WeeWX4.4 available have been using it without much problems 
>>>>> running on a Raspberry3B with OS=Raspian_Buster. Memory max. expanded 
>>>>> through Raspi-Config.
>>>>> Setup of WeeWX to (re)start when (re)booting.
>>>>> Occasionally stopping, but either by restart through PuttySSH, or (as 
>>>>> last resort) by an 'emergency' hard reset, was always able to restart.
>>>>> Most used CLI through PuttySSH is sudo /etc/init.d/weewx restart
>>>>> It still happily reports: [ ok ] Restarting weewx (via systemctl): 
>>>>> weewx.service
>>>>>
>>>>> However, this weekend such simple measures did not help, and database 
>>>>> and many files stuck/frozen at 14-10-23 10:15:00, while last 
>>>>> FTP-upload at 14-1023 22:17:36, but related files all 0kb. Date of 
>>>>> that FTP-upload also valid for all external uploads coming from WeeWX.
>>>>>
>>>>> Fresh reinstall (using copies of latest sdb-file etc.) obviously 
>>>>> a pragmatic remedy, 
>>>>> but would shorter route be available to revive this existing 
>>>>> configuration?
>>>>>
>>>>> Observed 2nd effect: cannot access crontab, getting report that no 
>>>>> space left on device.
>>>>> But df shows plenty of space
>>>>>
>>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2def4b8b-6c69-49f5-aa12-639161b29066n%40googlegroups.com.

[weewx-user] Re: How to revive 'frozen' WeeWX?

[Ton vanN]

Have run 3 variants of df with following results.

*raspberrypi9:~ $* df
Bestandssysteem 1K-blokken Gebruikt Beschikbaar Geb% Aangekoppeld op
/dev/root 30358348 30341964   0 100% /
devtmpfs4394000  439400   0% /dev
tmpfs   4726800  472680   0% /dev/shm
tmpfs   47268047740  424940  11% /run
tmpfs 512045116   1% /run/lock
tmpfs   4726800  472680   0% /sys/fs/cgroup
/dev/mmcblk0p1  25809549395  208700  20% /boot
tmpfs945360   94536   0% /run/user/1000
*raspberrypi9:~ $* df -i
Bestandssysteem I-nodes  IGebr   IVrij IGeb% Aangekoppeld op
/dev/root   1899328 116283 17830457% /
devtmpfs 109850379  1094711% /dev
tmpfs118170  1  1181691% /dev/shm
tmpfs118170523  1176471% /run
tmpfs118170  3  1181671% /run/lock
tmpfs118170 15  1181551% /sys/fs/cgroup
/dev/mmcblk0p10  0   0 - /boot
tmpfs118170 13  1181571% /run/user/1000
*raspberrypi9:~ $* df -h
Bestandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op
/dev/root   29G  29G 0 100% /
devtmpfs   430M0  430M   0% /dev
tmpfs  462M0  462M   0% /dev/shm
tmpfs  462M  47M  415M  11% /run
tmpfs  5,0M 4,0K  5,0M   1% /run/lock
tmpfs  462M0  462M   0% /sys/fs/cgroup
/dev/mmcblk0p1 253M  49M  204M  20% /boot
tmpfs   93M0   93M   0% /run/user/1000
*raspberrypi9:~ $*

Op maandag 16 oktober 2023 om 09:05:07 UTC+2 schreef Ton vanN:

> Question of Vince triggers other observation.
> Subject Raspberry should have a RAM-fs, but when viewing the folders, 
> don’t find /var/tmp and it’s subfolders.
> Sign for corruption?
>
> Op maandag 16 oktober 2023 om 00:58:30 UTC+2 schreef Greg from Oz:
>
>> What does df -i show?
>> You could have run out of inodes.
>>
>> On Monday, 16 October 2023 at 07:58:31 UTC+11 vince wrote:
>>
>>> Lets see the output of "df -h" because it sure sounds like /var or /tmp 
>>> is full...
>>>
>>> On Sunday, October 15, 2023 at 11:45:51 AM UTC-7 Ton vanN wrote:
>>>
>>>> Since WeeWX4.4 available have been using it without much problems 
>>>> running on a Raspberry3B with OS=Raspian_Buster. Memory max. expanded 
>>>> through Raspi-Config.
>>>> Setup of WeeWX to (re)start when (re)booting.
>>>> Occasionally stopping, but either by restart through PuttySSH, or (as 
>>>> last resort) by an 'emergency' hard reset, was always able to restart.
>>>> Most used CLI through PuttySSH is sudo /etc/init.d/weewx restart
>>>> It still happily reports: [ ok ] Restarting weewx (via systemctl): 
>>>> weewx.service
>>>>
>>>> However, this weekend such simple measures did not help, and database 
>>>> and many files stuck/frozen at 14-10-23 10:15:00, while last 
>>>> FTP-upload at 14-1023 22:17:36, but related files all 0kb. Date of 
>>>> that FTP-upload also valid for all external uploads coming from WeeWX.
>>>>
>>>> Fresh reinstall (using copies of latest sdb-file etc.) obviously 
>>>> a pragmatic remedy, 
>>>> but would shorter route be available to revive this existing 
>>>> configuration?
>>>>
>>>> Observed 2nd effect: cannot access crontab, getting report that no 
>>>> space left on device.
>>>> But df shows plenty of space
>>>>
>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/74559913-90b4-4fab-b6ba-cf2e4757fa15n%40googlegroups.com.

[weewx-user] Re: How to revive 'frozen' WeeWX?

[Ton vanN]

Question of Vince triggers other observation.
Subject Raspberry should have a RAM-fs, but when viewing the folders, don’t 
find /var/tmp and it’s subfolders.
Sign for corruption?

Op maandag 16 oktober 2023 om 00:58:30 UTC+2 schreef Greg from Oz:

> What does df -i show?
> You could have run out of inodes.
>
> On Monday, 16 October 2023 at 07:58:31 UTC+11 vince wrote:
>
>> Lets see the output of "df -h" because it sure sounds like /var or /tmp 
>> is full...
>>
>> On Sunday, October 15, 2023 at 11:45:51 AM UTC-7 Ton vanN wrote:
>>
>>> Since WeeWX4.4 available have been using it without much problems 
>>> running on a Raspberry3B with OS=Raspian_Buster. Memory max. expanded 
>>> through Raspi-Config.
>>> Setup of WeeWX to (re)start when (re)booting.
>>> Occasionally stopping, but either by restart through PuttySSH, or (as 
>>> last resort) by an 'emergency' hard reset, was always able to restart.
>>> Most used CLI through PuttySSH is sudo /etc/init.d/weewx restart
>>> It still happily reports: [ ok ] Restarting weewx (via systemctl): 
>>> weewx.service
>>>
>>> However, this weekend such simple measures did not help, and database 
>>> and many files stuck/frozen at 14-10-23 10:15:00, while last FTP-upload 
>>> at 14-1023 22:17:36, but related files all 0kb. Date of that 
>>> FTP-upload also valid for all external uploads coming from WeeWX.
>>>
>>> Fresh reinstall (using copies of latest sdb-file etc.) obviously a 
>>> pragmatic remedy, 
>>> but would shorter route be available to revive this existing 
>>> configuration?
>>>
>>> Observed 2nd effect: cannot access crontab, getting report that no space 
>>> left on device.
>>> But df shows plenty of space
>>>
>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/dcefd075-d32d-45e0-966c-56807ee528b6n%40googlegroups.com.

[weewx-user] How to revive 'frozen' WeeWX?

[Ton vanN]

Since WeeWX4.4 available have been using it without much problems running 
on a Raspberry3B with OS=Raspian_Buster. Memory max. expanded through 
Raspi-Config.
Setup of WeeWX to (re)start when (re)booting.
Occasionally stopping, but either by restart through PuttySSH, or (as last 
resort) by an 'emergency' hard reset, was always able to restart.
Most used CLI through PuttySSH is sudo /etc/init.d/weewx restart
It still happily reports: [ ok ] Restarting weewx (via systemctl): 
weewx.service

However, this weekend such simple measures did not help, and database and 
many files stuck/frozen at 14-10-23 10:15:00, while last FTP-upload at 
14-1023 22:17:36, but related files all 0kb. Date of that FTP-upload 
also valid for all external uploads coming from WeeWX.

Fresh reinstall (using copies of latest sdb-file etc.) obviously a 
pragmatic remedy, 
but would shorter route be available to revive this existing configuration?

Observed 2nd effect: cannot access crontab, getting report that no space 
left on device.
But df shows plenty of space

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/89069d87-3803-429c-ba6c-3cc15a574f96n%40googlegroups.com.

[weewx-user] Re: Weewx and API Integration

[Ton vanN]

AWEKAS API is described at 
https://www.awekas.at/board/index.php?attachment/4815-awekas-station-api-v1-3-pdf/

Op dinsdag 13 september 2022 om 22:35:06 UTC+2 schreef gjr80:

> Hi,
>
> I am not aware of any utility that exists that can import Awekas data into 
> WeeWX. The WeeWX utility wee_import 
>  has the ability 
> to import data via the WeatherUnderground API but not Awakes. That being 
> said, the modular nature of wee_import means it would be relatively 
> straightforward for you to adapt wee_import to import data from Awekas by 
> writing a new Awekas capable front end. This would depend of course on the 
> capabilities of the Awekas API.
>
> Gary
> On Wednesday, 14 September 2022 at 05:17:47 UTC+10 
> sebastian...@googlemail.com wrote:
>
>> Good evening, I use the weather station from Bresser 7 in 1 Clearview and 
>> send the data to Awekas. Now I would like to download the data to Weewx via 
>> API. Is there a possibility? Many Thanks
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5744b25f-2d3a-421c-8fe7-aaa727299600n%40googlegroups.com.

[weewx-user] Re: Dual Skin + Dual FTP

[Ton vanN]

Vince,

Thanks for this very practical solution!
Even simpler than 'simple' FTP-duplication ..

Op woensdag 24 augustus 2022 om 07:07:45 UTC+2 schreef vince:

> Put both skins under public_html and then you'll be able to transfer them 
> all up to your remote server in one transaction.
>
> /home/weewx/public_html for the Standard skin
> /home/weewx/public_html/Seasons for the Seasons skin
>
> On Tuesday, August 23, 2022 at 8:56:32 AM UTC-7 ton...@gmail.com wrote:
>
>> Presently using Standard skin as basis for presentation through remote 
>> server,
>> uploading the files from folder /home/weewx/public_html to a folder at 
>> remote webserver by means of the built-in FTP of Weewx.
>> Have activated Seasons skin, saving Seasons-files in other folder 
>> /home/weewx/Seasons_html.
>> Would be convenient just to duplicate the setup and apply FTP to forward 
>> the Seasons-files to another folder at the remote server.
>> Using present weewx.conf might use RSync for the 2nd uploadchannel, but 
>> simplicity is preffered and hence aiming for dual FTP. 
>>
>> Have looked around in the documentation and this group, but did not find 
>> info on simple dual parallel FTP. 
>> What is appropriate setup in weewx.conf to get such functionality?
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4140cc9e-072e-4fe1-987a-f1e4ad4b2b98n%40googlegroups.com.

[weewx-user] Dual Skin + Dual FTP

[Ton vanN]

Presently using Standard skin as basis for presentation through remote 
server,
uploading the files from folder /home/weewx/public_html to a folder at 
remote webserver by means of the built-in FTP of Weewx.
Have activated Seasons skin, saving Seasons-files in other folder 
/home/weewx/Seasons_html.
Would be convenient just to duplicate the setup and apply FTP to forward 
the Seasons-files to another folder at the remote server.
Using present weewx.conf might use RSync for the 2nd uploadchannel, but 
simplicity is preffered and hence aiming for dual FTP. 

Have looked around in the documentation and this group, but did not find 
info on simple dual parallel FTP. 
What is appropriate setup in weewx.conf to get such functionality?

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d2bb8032-739f-4081-9557-c47215aa053fn%40googlegroups.com.

[weewx-user] Re: Shutdown of Tempest-dataflow & display

[Ton vanN]

Additional info.
WeatherDisplay parallel reading output from the Tempest-hub, same as 
Domoticz reports fixed values since that time, also with actual time-stamp, 
not the 'freezing' as for WeeWX.

Op donderdag 9 juni 2022 om 19:46:04 UTC+2 schreef Ton vanN:

> Some 24 hours ago I observed a 'freezing' of the WeeWX-picture at 
> https://vannwnhzn.nl/WeeWX0/index.html
> Still continues.
>
> First thought is that upload for the html-file has stopped.
> Because for upload using the FTP-function in WeeWX, implicitly it means 
> that WeeWX has to be checked.
> Observation in WeeWX is that all files of WeeWX still get actual 
> datestamp, but contents have completely been frozen on approx. June 8th, 
> 16:25
> Restart of WeeWX (regardless of route) has no effects: no further visible 
> processing.
>
> This afternoon (as second thought) the penny dropped that this was also 
> the time that Weatherflow_Tempest as datafeeding sensor through UDP went on 
> strike:
> Tempest hub shows red light, meaning that the dataflow from the sensor (or 
> the hub itself) has problems.
> Also see at the Weatherflow-server that data & display has been frozen at 
> the time mentioned above.
> Locally in Domoticz I see that since that time the data from the 
> UDP-sniffer is also solid as a rock.
> Hard reset of the Tempest hub has no effect.
>
> *Question:*
> is it correct observation that when an interface-driver of WeeWX has no 
> inputs with changing time-validity, then all subsequent dataflows also stop 
> & freeze?
> *Or* is this apparently simultaneous event just an unhappy coincidence? 
> *Or* some aspects specific for the Tempest hub & interface-driver? 
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7e792e16-03e4-486d-b2db-a6ad16b7e2a9n%40googlegroups.com.

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

Improvement always possible, ;-) sometimes needed.

The setup with the HWA-template correctly produces the output-file, *but* 
the periodicity is unstable.
Any idea what could be the cause?

Op dinsdag 4 mei 2021 om 12:13:36 UTC+2 schreef Ton vanN:

> New template now running without errors (on WeeWX4.4.0 on 
> Raspian_Buster) and the output-file checked to be compatible with the 
> serversoftware of HetWeerActueel (version HWA2.0)
> Backwards compatibility of this new template with older WeeWX-versions 
> (using Python2.x, and now using the 'old' template) *not* checked!
>
> Duplicate posting is not a good idea.
> Also because the members of HetWeerActueel are >90% dutch-speaking, 
> therefore the resulting solution is described (in  dutch) at 
> https://www.hetweeractueel.nl/forum/viewtopic.php?p=73156#p73156
>
> Would like to thank all contributors to my probing & trying:
> your hints really assisted to keep me to move forward!
>
> Op maandag 3 mei 2021 om 00:55:23 UTC+2 schreef gjr80:
>
>> It's a bit of python 2v3 and poor coding. The first thing to remember is 
>> that in a WeeWX Cheetah template .formatted (now .formatted()) returns a 
>> string, .raw returns the raw value; typically an int or a float or None 
>> (though it could also be a string if the underlying field is a string but 
>> there are none of those in any of the WeeWX shipped schemas).
>>
>> Under python2 you can compare strings to numerics (int and float) without 
>> error, that being said you will not get the correct answer but it won't 
>> raise an error. Try doing this:
>>
>> gary@buster5:~$ python2
>> Python 2.7.16 (default, Oct 10 2019, 22:02:15) 
>> [GCC 8.3.0] on linux2
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> "5" > 4
>> True
>> >>> "3" > 4
>> True
>> >>> 
>>
>> Note that the second expression gives and incorrect answer. Python 3 is a 
>> little more picky, trying the same under python3 raises an error:
>>
>> gary@buster5:~$ python3
>> Python 3.7.3 (default, Jan 22 2021, 20:04:44) 
>> [GCC 8.3.0] on linux
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> "5" > 4
>>
>> Traceback (most recent call last):
>>   File "", line 1, in 
>> TypeError: '>' not supported between instances of 'str' and 'int'
>>
>> Then add into the mix the fact that a .raw could return the python value 
>> None. Python 2 will happily allow None in a comparison but python3 will 
>> not, it will raise a TypeError albeit with a different error message.
>>
>> So getting back to the original comparison expression in the report. 
>> Under python2 it will operate without error, it may give the wrong result 
>> under certain conditions but it will not cause an error that will force the 
>> template generation to abort. Under python3 the expression will raise an 
>> error on every generation and the template will abort. The obvious solution 
>> is to change .format to .raw, that will work under most conditions but 
>> if $trend.barometer.raw is ever None (quite possible on startup or if 
>> there has been an interruption) it will fail. The solution is to either 
>> catch the error and deal with it or alter the conditional to check for 
>> None, eg (untested):
>>
>> #if $trend.barometer.raw is not None and $trend.barometer.raw > 0
>> #do something
>> #end if
>>
>> Gary
>> On Monday, 3 May 2021 at 07:56:41 UTC+10 peterq...@gmail.com wrote:
>>
>>> Yes. 
>>>
>>> I can't find the official documentation but See 
>>> https://devopedia.org/python-2-vs-3
>>> Although Python is strongly typed, Python 2 permits strange comparisons: 
>>> None 
>>> < 3 < "2"
>>>
>>> On Sun, May 2, 2021 at 2:47 PM Ton vanN  wrote:
>>>
>>>> Reason for my speculation:
>>>> at the HWA-forum several people already using WeeWx for years with the 
>>>> original HWA-template, *probably* started & still operating with 
>>>> Python2.x, and never heard complaints about the template.
>>>>
>>>> That triggers another aspect: 
>>>> when issuing for the HWA-Forum this updated version of the template, 
>>>> some advice must be given that (backwards) application with Python2.x must 
>>>> be checked.
>>>> Best to give this template-version and also the older version a 
>

Re: [weewx-user] Is anyone using a Davis Airlink with weewx?

[Ton vanN]

Upload to a website is one approach, but has anyone tried to link the 
Airlink-data in Weewx to the uploads to WUnderground, Aeris and AWEKAS (or 
other similar organisations)?
WU seems to 'restrict' itself to acceptance of data from PurpleAir, while 
AWEKAS at it's website has descriptions 'hinting' to interface with Weewx.
Experiences? Scripts (in this forum, or elsewhere on internet)? 

Op maandag 19 oktober 2020 om 17:35:16 UTC+2 schreef wryb...@gmail.com:

> I made a Python script to get the data from my Airlink, in case it's 
> useful to anyone I posted it here:
>
> https://github.com/wrybread/AirLink-Data-Uploader
>
> In that package is also a script for an ESP32 that gets the data from an 
> Airlink and uploads it to a remote webserver. Handy for people who don't 
> have a server running on the same LAN as their Airlink.
>
>
>
> On Sun, Oct 18, 2020 at 11:11 AM rich T  wrote:
>
>> Here is what I'm using: weewx-airlink. 
>>
>> On Sunday, October 18, 2020 at 1:59:32 PM UTC-4, Ken Waters wrote:
>>>
>>> It looks like this link that was previously posted answered my question:
>>> https://weatherlink.github.io/airlink-local-api/.  I don't know why 
>>> Davis Instruments doesn't provide that information with the product.  After 
>>> reading this Github article I was able to easily locate the IP from my 
>>> router as well as the 'did' code.  Now I get to have some fun building a 
>>> new database.  I'd still like to get it into my WeeWx system as well, 
>>> though.
>>>
>>> Thanks for posting!
>>>
>>> [image: image.png]
>>>
>>> On Sun, Oct 18, 2020 at 10:44 AM Ken Waters  wrote:
>>>
 My AirLink just arrived.  How do I get the data out of it to bring into 
 my server and into WeeWx?  Also, on a tangent, I noticed that my AirLink 
 data are not getting displayed on the Davis map 
 https://www.weatherlink.com/map.  I know I've got a lot to learn about 
 how to use this but ultimately I'd love to have it be available in WeeWx.

 I am running WeeWx 3.9.2 on an Ubuntu server with a Vantage Pro 2.

 Thanks,

 Ken

 On Tue, Sep 15, 2020 at 5:32 PM Alec Bennett  wrote:

> I just bought an Airlink:
>
>
> https://www.davisinstruments.com/product/airlink-professional-air-quality-sensor/
>
> Looking forward to be able to put a number on the horrible air we've 
> been having here in Northern California.
>
> I'm wondering if I can integrate it with weewx? 
>
> Is that the sort of thing a plugin would do?
>
> Thanks for any help.
>
> -- 
> 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...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/5a473b16-ad4d-4d00-a813-0004ee17f836n%40googlegroups.com
>  
> 
> .
>
 -- 
>>
> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/waXSbdBxCWo/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/00c995df-22b0-44f8-916d-7c03de6e3806o%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7e550e21-0fc2-4183-bf1e-0259882dd72an%40googlegroups.com.

[weewx-user] Re: ET-value for display in Standard-skin

[Ton vanN]

*Suggestion* for change of values at Standard skin, for more meaningful 
ET-display.

Under 'Current Conditions':
Equivalent to RainRate (in mm/hr) replace ET (in mm) by ET/hour (in mm/hr).
Under 'Since Midnight':
Equivalent to Today's Rain replace Low ET by Today's ET
Equivalent to High Rain Rate) replace High ET by High ET/hour

Op donderdag 27 mei 2021 om 16:45:20 UTC+2 schreef Ton vanN:

> Already applying that approach on my website for showing actual 
> balance_today (from own calculations): vannwnhzn.nl/BalanceE_Info.txt
> Now only need to tweak WeeWX's Standard skin to show similar values.
> For that purpose the extension is useful.
>
> *Sidestep,* but in that website also own calculation of absolute 
> humidity: vannwnhzn.nl/AV1_Info.txt
> IMHO the better & unambiguous info to judge water-contents of air for 
> control of ventilation, irrigation etc.
>
> Op donderdag 27 mei 2021 om 15:03:26 UTC+2 schreef kk44...@gmail.com:
>
>> Yes. ET refers to the archive interval (typical 5 minutes). And ET for 5 
>> minutes is a very very small amount. You need to sum it over a longer 
>> interval, for example a day. You can do that by the tag $day.ET.sum. Or 
>> you install the extension mentioned in that message.
>>
>> ton...@gmail.com schrieb am Donnerstag, 27. Mai 2021 um 14:45:07 UTC+2:
>>
>>> *Or* is the answer in this message 
>>> <https://groups.google.com/g/weewx-user/c/jZE-G8zDpRM/m/kgOrArxrAQAJ>? 
>>> Meaning that ET as displayed is the calculated value, but always approx. 
>>> 0.0 due to rounding?
>>> In that perspective more useful to take ET_today of ET_last24hr with 
>>> comparison against Rain_today respectively Rain_last24hr.
>>>
>>> Op donderdag 27 mei 2021 om 14:33:01 UTC+2 schreef Ton vanN:
>>>
>>>> Now running WeeWX for some time.
>>>> At http://vannwnhzn.nl/WeeWX0/index.html with uploaded Standard skin.
>>>> In that Standard skin see ET always at 0-value, although certainly an 
>>>> actual value > 0.
>>>> In Customization Guide see ET available as calculated value.
>>>>
>>>> Looked in the documentation and in the messages in this Group for info 
>>>> on the setting(s) to get ET-value to Standard skin-display, but not yet 
>>>> finding.
>>>> Must be simple, but apparently missed: *Where? How?*
>>>>
>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/fe423c2c-d503-4391-9a5d-6ff998c88fden%40googlegroups.com.

[weewx-user] Re: ET-value for display in Standard-skin

[Ton vanN]

Already applying that approach on my website for showing actual 
balance_today (from own calculations): vannwnhzn.nl/BalanceE_Info.txt
Now only need to tweak WeeWX's Standard skin to show similar values.
For that purpose the extension is useful.

*Sidestep,* but in that website also own calculation of absolute humidity: 
vannwnhzn.nl/AV1_Info.txt
IMHO the better & unambiguous info to judge water-contents of air for 
control of ventilation, irrigation etc.

Op donderdag 27 mei 2021 om 15:03:26 UTC+2 schreef kk44...@gmail.com:

> Yes. ET refers to the archive interval (typical 5 minutes). And ET for 5 
> minutes is a very very small amount. You need to sum it over a longer 
> interval, for example a day. You can do that by the tag $day.ET.sum. Or 
> you install the extension mentioned in that message.
>
> ton...@gmail.com schrieb am Donnerstag, 27. Mai 2021 um 14:45:07 UTC+2:
>
>> *Or* is the answer in this message 
>> <https://groups.google.com/g/weewx-user/c/jZE-G8zDpRM/m/kgOrArxrAQAJ>? 
>> Meaning that ET as displayed is the calculated value, but always approx. 
>> 0.0 due to rounding?
>> In that perspective more useful to take ET_today of ET_last24hr with 
>> comparison against Rain_today respectively Rain_last24hr.
>>
>> Op donderdag 27 mei 2021 om 14:33:01 UTC+2 schreef Ton vanN:
>>
>>> Now running WeeWX for some time.
>>> At http://vannwnhzn.nl/WeeWX0/index.html with uploaded Standard skin.
>>> In that Standard skin see ET always at 0-value, although certainly an 
>>> actual value > 0.
>>> In Customization Guide see ET available as calculated value.
>>>
>>> Looked in the documentation and in the messages in this Group for info 
>>> on the setting(s) to get ET-value to Standard skin-display, but not yet 
>>> finding.
>>> Must be simple, but apparently missed: *Where? How?*
>>>
>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9198715f-1e41-463d-b0bc-cb78f22d5c02n%40googlegroups.com.

[weewx-user] Re: ET-value for display in Standard-skin

[Ton vanN]

*Or* is the answer in this message 
<https://groups.google.com/g/weewx-user/c/jZE-G8zDpRM/m/kgOrArxrAQAJ>? 
Meaning that ET as displayed is the calculated value, but always approx. 
0.0 due to rounding?
In that perspective more useful to take ET_today of ET_last24hr with 
comparison against Rain_today respectively Rain_last24hr.

Op donderdag 27 mei 2021 om 14:33:01 UTC+2 schreef Ton vanN:

> Now running WeeWX for some time.
> At http://vannwnhzn.nl/WeeWX0/index.html with uploaded Standard skin.
> In that Standard skin see ET always at 0-value, although certainly an 
> actual value > 0.
> In Customization Guide see ET available as calculated value.
>
> Looked in the documentation and in the messages in this Group for info on 
> the setting(s) to get ET-value to Standard skin-display, but not yet 
> finding.
> Must be simple, but apparently missed: *Where? How?*
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/33321127-fff8-4490-a227-0a15e71c0041n%40googlegroups.com.

[weewx-user] ET-value for display in Standard-skin

[Ton vanN]

Now running WeeWX for some time.
At http://vannwnhzn.nl/WeeWX0/index.html with uploaded Standard skin.
In that Standard skin see ET always at 0-value, although certainly an 
actual value > 0.
In Customization Guide see ET available as calculated value.

Looked in the documentation and in the messages in this Group for info on 
the setting(s) to get ET-value to Standard skin-display, but not yet 
finding.
Must be simple, but apparently missed: *Where? How?*

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5ef61dee-2724-4e2d-b212-b099a2df9643n%40googlegroups.com.

Re: [weewx-user] Re: Help getting Tempest setup with Weewx on Pi running Debian

[Ton vanN]

[Removed my previous version of this message, because it contained info not 
needed]

If I look at the sensor-map you inserted in weaterheflowudp.py for your 
Tempest-setup, I see codes like AR-8830 and SK-8830
In my opinion there is the error, causing time-out for the 
UDP-messagehandling. 

The required sensor-code you find by going to the Weatherflow-webpage 
showing the info from your Tempest-station:
easiest via https://tempestwx.com/station/x/ in which x is the 
unique Weatherflow-number for your station.
Then tick the 'sensorhead' at the 2nd line, top right side of the display, 
and in the window popping up, the required number will show at the left 
side of each subwindow (something like ST-x ).
*That* number must be inserted in all lines of the *Tempest *sensormap [
*not* the Air/Sky-sensormap!].

Stumbled also on that aspect: 
see the discussion in this group between me and vince around 5th of May 
under title Tempest Weewx

Other aspect met in practise:
some other software is 'not friends' with WeeWX.
Had that experience with Domoticz.
Now run WeeWX as only software at a RPI0W_RaspianBuster, without any 
problem.

Op maandag 24 mei 2021 om 21:41:28 UTC+2 schreef vince:

> On Monday, May 24, 2021 at 11:36:37 AM UTC-7 corey...@gmail.com wrote:
>
>> These are my logs. Checking the CWOP site it seems that the unit starts 
>> to report and then stops. Thoughts appreciated.
>>
>>
> It doesn't matter what CWOP shows if weewx on the pi isn't quite happy.
>
> What model pi are you running on ?
> What extensions are you running ?
> What skins are enabled ?
> Are you wired or wifi ?
> If you're wifi are you 2.4GHz or 5GHz ?
> Is your wifi stable ?
>
> My wild guess is that you are running too much stuff on a pi-zero or 
> similar minimal device or that your wifi is unstable, or both.
>
> But you've provided us really nothing to go on in terms of understanding 
> your setup.  See the FAQ 
> for how 
> to report a problem so we can try to help better.
>
> If you want to diagnose your Tempest setup directly without weewx you can 
> try my UDP listener from 
> https://github.com/vinceskahan/weatherflow-udp-listener - I'd suggest the 
> --raw --debug options.   If you run my listener at the same time as the 
> weewx driver, you need to set share_sockets=true for the weewx driver so 
> that multiple programs can listen for traffic at the same time.
>
>  
>
>  
>
>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d0d148db-7aeb-454d-a001-37ff8ed4bccbn%40googlegroups.com.

[weewx-user] Re: XML-parse

[Ton vanN]

'conced' = convinced

Op zaterdag 8 mei 2021 om 13:29:48 UTC+2 schreef Ton vanN:

> @gjr80 / Gary,
>
> ;-) Recent experience conced me that proper use of sensormapping may make 
> the difference .
>
> My next effort is aimed at using an XML-file as input for WeeWX.
>
> https://github.com/gjr80/weewx-xmlparse calls in section 5. a 
> sensormapdescription by url = 
> https://github.com/gjr80/weewx-xmlparse/blob/master
> But calling results in 404-errorreport.
> At what url can the 'correct' sensormapdesription be found?
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c9bcb170-52a9-44b6-984d-6912e4c05a0an%40googlegroups.com.

[weewx-user] XML-parse

[Ton vanN]

@gjr80 / Gary,

;-) Recent experience conced me that proper use of sensormapping may make 
the difference .

My next effort is aimed at using an XML-file as input for WeeWX.

https://github.com/gjr80/weewx-xmlparse calls in section 5. a 
sensormapdescription by url = 
https://github.com/gjr80/weewx-xmlparse/blob/master
But calling results in 404-errorreport.
At what url can the 'correct' sensormapdesription be found?

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9816b084-b77d-4210-84df-fe8568809c4dn%40googlegroups.com.

Re: [weewx-user] Tempest Weewx

[Ton vanN]

;-) Now checking more in case of doubt of meaning .
Is it correct understanding that in fact it *functionally* is 'Cut' 
of the subject block of text, not 'Copy'?

In hindsight, had read the warning about need for the sensor map, but not 
translated/understood that in this way.

Op woensdag 5 mei 2021 om 19:49:20 UTC+2 schreef vince:

> On Wednesday, May 5, 2021 at 8:41:08 AM UTC-7 ton...@gmail.com wrote:
>
>> However, surprised that I had to duplicate the subject text to weewx.conf 
>> to get the read-out of the Udp-messages.
>>
>>
> No, you had to 'add' the remaining lines to weewx.conf to tell the driver 
> what to do.
>
> When you run "wee_config --reconfig" to tell weewx to use the WF driver, 
> it adds the first two lines only.  You need to 'add' the remaining lines to 
> tell the driver how you want it to operate.  Nothing is duplicated.
>
> There are a variety of WeatherFlow drivers for weewx.  I believe one of 
> them is trying to automate this more for you.
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4e8f4c4e-0ce8-4c6c-9a87-5916235d8564n%40googlegroups.com.

Re: [weewx-user] Tempest Weewx

[Ton vanN]

Vince,

“Duplication” is the aspect that triggered my comment.
The sensormap is part of the driver-software.
After initial install the reference in weewx.conf by 2 lines pointing to 
that driver-software is clear, singular, unambiguous and simple.
That the sensormap in the driver has to be tuned to the 
systeemnumberconfiguration is obvious.
However, surprised that I had to duplicate the subject text to weewx.conf 
to get the read-out of the Udp-messages.

Op woensdag 5 mei 2021 om 16:31:19 UTC+2 schreef vince:

> On Wednesday, May 5, 2021 at 3:42:21 AM UTC-7 ton...@gmail.com wrote:
>
>> inserting in weewx.conf a *copy* of text out of the 
>> WeatherflowUDP-driver does the trick.
>> Not obvious and seems undocumented, but it works ...
>>
>> Instead of the setup introduced by first install of the extension
>>
>> [WeatherFlowUDP]
>> driver = user.weatherflowudp 
>>
>> make it [with obvious adaptation to your sensor-number!]
>>
>>
> I'm missing what is not obvious or documented.
>
> Many drivers and extensions require you to edit weewx.conf to 'configure' 
> the driver after you use wee_extension to 'install' the driver, especially 
> anything with a sensor_map required.
>
> This particular driver's GitHub page's instructions even has the exact 
> stanza that you need to edit into your file.
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f2233885-c73d-4dab-851f-61612512ce38n%40googlegroups.com.

Re: [weewx-user] Tempest Weewx

[Ton vanN]

Met a similar experience.
After some experiments with Simulator followed by Weatherflow Tempest as 
datasource, wanted a clean database for further operation with Tempest.
Deleted the database expecting WeeWX to restart with a new database, but 
not happening.
Reconfiguring to Simulator proved that WeeWX was still OK, but after 
switching again to weatherflowudp.py as driver no signs of life.

inserting in weewx.conf a *copy* of text out of the WeatherflowUDP-driver 
does the trick.
Not obvious and seems undocumented, but it works ...

Instead of the setup introduced by first install of the extension

[WeatherFlowUDP]
driver = user.weatherflowudp 

make it [with obvious adaptation to your sensor-number!]

[WeatherFlowUDP]
driver = user.weatherflowudp
log_raw_packets = false
udp_address = 
# udp_address = 0.0.0.0
# udp_address = 255.255.255.255
udp_port = 50222
udp_timeout = 90
share_socket = True

[[sensor_map]]
outTemp = air_temperature.ST-00021804.obs_st
outHumidity = relative_humidity.ST-00021804.obs_st
pressure = station_pressure.ST-00021804.obs_st
#lightning_strikes =  lightning_strike_count.ST-00021804.obs_st
#avg_distance =  lightning_strike_avg_distance.ST-00021804.obs_st
outTempBatteryStatus = battery.ST-00021804.obs_st
windSpeed = wind_speed.ST-00021804.rapid_wind
windDir = wind_direction.ST-00021804.rapid_wind
#luxXXX = illuminance.ST-00021804.obs_st
UV = uv.ST-00021804.obs_st
rain = rain_accumulated.ST-00021804.obs_st
windBatteryStatus = battery.ST-00021804.obs_st
radiation = solar_radiation.ST-00021804.obs_st
   #lightningXXX = distance.ST-00021804.evt_strike
   #lightningYYY = energy.ST-00021804.evt_strike




Op dinsdag 4 mei 2021 om 00:47:10 UTC+2 schreef rons...@gmail.com:

> I reinstalled weewx. WeatherflowUDP and it worked 
>
> On Sunday, May 2, 2021, Ron Sell  wrote:
>
>> I am not sure what is going on. I can still only capture wind speed and 
>> direction. 
>>
>> the data is there in the log but it won't capture it.  I pointed 
>> everything back to my AIR and it worked. Changed it back to the tempest and 
>> alli get is N/A
>> attached my weewx.conf incase someone notices a typo.
>>
>>
>> On Sat, May 1, 2021 at 6:41 PM vince  wrote:
>>
> I don't see it, but there has to be a typo in weewx.conf someplace.
>>>
>>> My old Tempest weewx.conf is at 
>>> https://community.weatherflow.com/t/weewx-udp-driver-for-weatherflow-station/283/189
>>>  
>>> if you want to take a look there.   Of course you'll have to edit in your 
>>> serial numbers for your sensor.
>>>
>>> On Saturday, May 1, 2021 at 2:02:40 PM UTC-7 rons...@gmail.com wrote:
>>>

 I am using this udp driver"
 https://github.com/captain-coredump/weatherflow-udp

 log attached

 snip from log:
 May  1 17:01:19 raspberrypi weewxd: weatherflowudp: MainThread: raw 
 packet: {'fs': [1, 0, 15675411, 524288], 'seq': 837, 'firmware_revision': 
 '169', 'timestamp': 1619902878, 'serial_number': 'HB-00012441', 'uptime': 
 8414, 'reset_flags': 'BOR,PIN,POR', 'mqtt_stats': [49, 0], 'rssi': -25, 
 'type': 'hub_status', 'radio_stats': [5, 1, 0, 3, 0]}
 May  1 17:01:20 raspberrypi weewxd: weatherflowudp: MainThread: raw 
 packet: {'firmware_revision': 134, 'timestamp': 1619902879, 'voltage': 
 2.585, 'rssi': -68, 'hub_sn': 'HB-00012441', 'uptime': 19985, 'hub_rssi': 
 -60, 'sensor_status': 0, 'debug': 0, 'serial_number': 'ST-00021019', 
 'type': 'device_status'}
 May  1 17:01:20 raspberrypi weewxd: weatherflowudp: MainThread: raw 
 packet: {'firmware_revision': 134, 'serial_number': 'ST-00021019', 'type': 
 'obs_st', 'obs': [[1619902879, 0.54, 3.03, 5.93, 215, 3, 967.62, 16.41, 
 29.09, 63223, 2.87, 527, 0.0, 0, 0, 0, 2.585, 1]], 'hub_sn': 'HB-00012441'}
 May  1 17:01:22 raspberrypi weewxd: weatherflowudp: MainThread: raw 
 packet: {'serial_number': 'ST-00021019', 'type': 'rapid_wind', 'ob': 
 [1619902881, 2.24, 196], 'hub_sn': 'HB-00012441'}
 May  1 17:01:22 raspberrypi weewx[1884] INFO weewx.restx: MQTT: 
 Published record 2021-05-01 17:01:21 EDT (1619902881)
 May  1 17:01:25 raspberrypi weewxd: weatherflowudp: MainThread: raw 
 packet: {'serial_number': 'ST-00021019', 'type': 'rapid_wind', 'ob': 
 [1619902884, 2.24, 205], 'hub_sn': 'HB-00012441'}
 May  1 17:01:25 raspberrypi weewx[1884] INFO weewx.restx: MQTT: 
 Published record 2021-05-01 17:01:24 EDT (1619902884)
 May  1 17:01:28 raspberrypi weewxd: weatherflowudp: MainThread: raw 
 packet: {'serial_number': 'ST-00021019', 'type': 'rapid_wind', 'ob': 
 [1619902887, 1.88, 248], 'hub_sn': 'HB-00012441'}
 May  1 17:01:28 raspberrypi weewx[1884] INFO weewx.restx: MQTT: 
 Published record 2021-05-01 17:01:27 EDT (1619902887)
 May  1 17:01:29 raspberrypi weewxd: weatherflowudp: MainThread: 

[weewx-user] Re: Clean the database(s) before a certain date

[Ton vanN]

Gary,
Completely agree with your latest response, and that was reason for my 
earlier [remark] that for Weatherflow-operation I should turn to a more 
dedicated thread.
Also agree with your discussion of compressed file or uncompressed text: is 
dilemma how & when to choose.

Question of 'cleaning database' closed.




Op woensdag 5 mei 2021 om 11:32:20 UTC+2 schreef gjr80:

> A couple of observations. Deleting the database has nothing to do with the 
> Weatherflow driver not working - that is almost certainly due to incorrect 
> setup/config of the Weatherflow driver. Secondly, don’t reinstall. Clearly 
> WeeWX is operating fine (the simulator works fine). Better to spend your 
> time troubleshooting the issue.
>
> I can’t  help much with Weatherflow setup, I am not familiar with the 
> station or the driver. I suggest you revisit the Weatherflow driver 
> setup/config, and if you have no luck start a new thread making sure you 
> post a log extract showing the full WeeWX startup and a few archive 
> periods. A sanitised copy of your weewx.conf would also help (the WeeWX 
> utility wee_debug  
> can help with this, just be sure that whatever you post contains no 
> sensitive info such as user names, passwords, api keys etc, wee_debug 
> should obfuscate these for you but it’s not perfect). You might also find 
> the wiki article Help! Posting to weewx user 
>  has some useful 
> advice for getting a good log extract, note the tip to use two terminal 
> sessions, one to issue commands and a second to tail the log.
>
> One final request, appreciate the reason why you might compress files for 
> posting, but it does make life hard for some of us using mobile devices. 
> Plain text is fine - I am told Google has plenty of storage space. If you 
> have problems posting a particular file eg .log, just rename it to .txt 
> with a note explaining.
>
> Gary
> On Wednesday, 5 May 2021 at 19:04:14 UTC+10 ton...@gmail.com wrote:
>
>> Gary,
>> The closing remark in your message is not without merit and needs to be 
>> applied 
>>
>> ;-( Enthousiastically wiped weewx.sdb from /home/weewx/archive (*without 
>> first shifting a copy elswhere*) and now in trouble.
>> At restart of WeeWX (= with weatherflowudp as driver) no signs of life, 
>> except the logging of raw packets (because of related setting).
>> Then executed the actions as shown in the attached zip-file.
>> Now headscratching how to proceed:
>> - with Simulator as datasource everything OK and database filling
>> - with WeatherflowUDP as driver see raw packets passing, but no further 
>> signs of life, seemingly confirmed by time-out information.
>>
>> A complete fresh reinstall & setup obviously will remedy the problem, but 
>> quicker correction would be nice 
>>
>> [This problem (in my case) has direct practical relation with 'cleaning' 
>> of the database, but possibly better to shift the discussion to another, 
>> more appropiate thread dealing with integration of Tempest]
>>
>> Op dinsdag 4 mei 2021 om 22:03:37 UTC+2 schreef gjr80:
>>
>>> The thread you linked describes the process to (1) have WeeWX use a 
>>> clean database and (2) change the driver from simulator to FineOffsetUSB 
>>> (fousb). Step 3 was all about the latter, it has nothing to do with 
>>> clearing the database. If you simply want to have WeeWX start with a clean 
>>> database then the easiest thing to do is to stop weewx, delete the database 
>>> file (a default install will use database weewx.sdb located in either 
>>> /var/lib/weewx or /home/weewx/archive) and then restart WeeWX. WeeWX will 
>>> automatically create a clean database during startup. Unless you have 
>>> manually changed the structure of your archive this will give you a clean 
>>> database with the same structure (schema) as the original.
>>>
>>> Of course if you want to keep the old database/data you should make a 
>>> copy of the database before deleting.
>>>
>>> Gary
>>>
>>> On Wednesday, 5 May 2021 at 05:14:38 UTC+10 ton...@gmail.com wrote:
>>>
 Have started operation of WeeWX with the Simulator.
 Now switched to Tempest, and getting real data.

 The thread 
 https://groups.google.com/g/weewx-user/c/NJ_XFLbWrNc/m/fpRqGIBWBQAJ 
 describes a method to transition the database(s) from Simulator to 'Real' 
 sensor by defining completely new database(s).
 But what is the easy way to *wipe *the data in the database(s) *while* 
 maintaining the datastructure?
 In other words:
 can the goal be achieved with less action than redefinition according 
 to steps 2.+3. in the quoted message?

>>>

-- 
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 discussion on the web visit 

[weewx-user] Re: Clean the database(s) before a certain date

[Ton vanN]

Gary,
The closing remark in your message is not without merit and needs to be 
applied 

;-( Enthousiastically wiped weewx.sdb from /home/weewx/archive (*without 
first shifting a copy elswhere*) and now in trouble.
At restart of WeeWX (= with weatherflowudp as driver) no signs of life, 
except the logging of raw packets (because of related setting).
Then executed the actions as shown in the attached zip-file.
Now headscratching how to proceed:
- with Simulator as datasource everything OK and database filling
- with WeatherflowUDP as driver see raw packets passing, but no further 
signs of life, seemingly confirmed by time-out information.

A complete fresh reinstall & setup obviously will remedy the problem, but 
quicker correction would be nice 

[This problem (in my case) has direct practical relation with 'cleaning' of 
the database, but possibly better to shift the discussion to another, more 
appropiate thread dealing with integration of Tempest]

Op dinsdag 4 mei 2021 om 22:03:37 UTC+2 schreef gjr80:

> The thread you linked describes the process to (1) have WeeWX use a clean 
> database and (2) change the driver from simulator to FineOffsetUSB (fousb). 
> Step 3 was all about the latter, it has nothing to do with clearing the 
> database. If you simply want to have WeeWX start with a clean database then 
> the easiest thing to do is to stop weewx, delete the database file (a 
> default install will use database weewx.sdb located in either 
> /var/lib/weewx or /home/weewx/archive) and then restart WeeWX. WeeWX will 
> automatically create a clean database during startup. Unless you have 
> manually changed the structure of your archive this will give you a clean 
> database with the same structure (schema) as the original.
>
> Of course if you want to keep the old database/data you should make a copy 
> of the database before deleting.
>
> Gary
>
> On Wednesday, 5 May 2021 at 05:14:38 UTC+10 ton...@gmail.com wrote:
>
>> Have started operation of WeeWX with the Simulator.
>> Now switched to Tempest, and getting real data.
>>
>> The thread 
>> https://groups.google.com/g/weewx-user/c/NJ_XFLbWrNc/m/fpRqGIBWBQAJ 
>> describes a method to transition the database(s) from Simulator to 'Real' 
>> sensor by defining completely new database(s).
>> But what is the easy way to *wipe *the data in the database(s) *while* 
>> maintaining the datastructure?
>> In other words:
>> can the goal be achieved with less action than redefinition according to 
>> steps 2.+3. in the quoted message?
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2eb50314-fba4-404b-b340-1c0c7c50e74bn%40googlegroups.com.


SysLog20210505.rar
Description: application/rar

[weewx-user] Clean the database(s) before a certain date

[Ton vanN]

Have started operation of WeeWX with the Simulator.
Now switched to Tempest, and getting real data.

The thread 
https://groups.google.com/g/weewx-user/c/NJ_XFLbWrNc/m/fpRqGIBWBQAJ 
describes a method to transition the database(s) from Simulator to 'Real' 
sensor by defining completely new database(s).
But what is the easy way to *wipe *the data in the database(s) *while* 
maintaining the datastructure?
In other words:
can the goal be achieved with less action than redefinition according to 
steps 2.+3. in the quoted message?

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/21250326-e1b4-4ba7-88ff-a35844c0f529n%40googlegroups.com.

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

New template now running without errors (on WeeWX4.4.0 on 
Raspian_Buster) and the output-file checked to be compatible with the 
serversoftware of HetWeerActueel (version HWA2.0)
Backwards compatibility of this new template with older WeeWX-versions 
(using Python2.x, and now using the 'old' template) *not* checked!

Duplicate posting is not a good idea.
Also because the members of HetWeerActueel are >90% dutch-speaking, 
therefore the resulting solution is described (in  dutch) at 
https://www.hetweeractueel.nl/forum/viewtopic.php?p=73156#p73156

Would like to thank all contributors to my probing & trying:
your hints really assisted to keep me to move forward!

Op maandag 3 mei 2021 om 00:55:23 UTC+2 schreef gjr80:

> It's a bit of python 2v3 and poor coding. The first thing to remember is 
> that in a WeeWX Cheetah template .formatted (now .formatted()) returns a 
> string, .raw returns the raw value; typically an int or a float or None 
> (though it could also be a string if the underlying field is a string but 
> there are none of those in any of the WeeWX shipped schemas).
>
> Under python2 you can compare strings to numerics (int and float) without 
> error, that being said you will not get the correct answer but it won't 
> raise an error. Try doing this:
>
> gary@buster5:~$ python2
> Python 2.7.16 (default, Oct 10 2019, 22:02:15) 
> [GCC 8.3.0] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> "5" > 4
> True
> >>> "3" > 4
> True
> >>> 
>
> Note that the second expression gives and incorrect answer. Python 3 is a 
> little more picky, trying the same under python3 raises an error:
>
> gary@buster5:~$ python3
> Python 3.7.3 (default, Jan 22 2021, 20:04:44) 
> [GCC 8.3.0] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> "5" > 4
>
> Traceback (most recent call last):
>   File "", line 1, in 
> TypeError: '>' not supported between instances of 'str' and 'int'
>
> Then add into the mix the fact that a .raw could return the python value 
> None. Python 2 will happily allow None in a comparison but python3 will 
> not, it will raise a TypeError albeit with a different error message.
>
> So getting back to the original comparison expression in the report. Under 
> python2 it will operate without error, it may give the wrong result under 
> certain conditions but it will not cause an error that will force the 
> template generation to abort. Under python3 the expression will raise an 
> error on every generation and the template will abort. The obvious solution 
> is to change .format to .raw, that will work under most conditions but if 
> $trend.barometer.raw is ever None (quite possible on startup or if there 
> has been an interruption) it will fail. The solution is to either catch the 
> error and deal with it or alter the conditional to check for None, eg 
> (untested):
>
> #if $trend.barometer.raw is not None and $trend.barometer.raw > 0
> #do something
> #end if
>
> Gary
> On Monday, 3 May 2021 at 07:56:41 UTC+10 peterq...@gmail.com wrote:
>
>> Yes. 
>>
>> I can't find the official documentation but See 
>> https://devopedia.org/python-2-vs-3
>> Although Python is strongly typed, Python 2 permits strange comparisons: 
>> None 
>> < 3 < "2"
>>
>> On Sun, May 2, 2021 at 2:47 PM Ton vanN  wrote:
>>
>>> Reason for my speculation:
>>> at the HWA-forum several people already using WeeWx for years with the 
>>> original HWA-template, *probably* started & still operating with 
>>> Python2.x, and never heard complaints about the template.
>>>
>>> That triggers another aspect: 
>>> when issuing for the HWA-Forum this updated version of the template, 
>>> some advice must be given that (backwards) application with Python2.x must 
>>> be checked.
>>> Best to give this template-version and also the older version a related, 
>>> distinguishing name.
>>>
>>> Op zondag 2 mei 2021 om 23:33:32 UTC+2 schreef Ton vanN:
>>>
>>>> Peter, that was the hint required!
>>>> The HWA-template now has become active.
>>>>
>>>> Speculation, but could this be an aspect of changing from Python2.x to 
>>>> Python3.x?
>>>>
>>>>
>>>> Op zondag 2 mei 2021 om 23:06:42 UTC+2 schreef peterq...@gmail.com:
>>>>
>>>>> Looks like that could be it. The .formatted is turning the barometer 
>>>>&

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

Reason for my speculation:
at the HWA-forum several people already using WeeWx for years with the 
original HWA-template, *probably* started & still operating with Python2.x, 
and never heard complaints about the template.

That triggers another aspect: 
when issuing for the HWA-Forum this updated version of the template, some 
advice must be given that (backwards) application with Python2.x must be 
checked.
Best to give this template-version and also the older version a related, 
distinguishing name.

Op zondag 2 mei 2021 om 23:33:32 UTC+2 schreef Ton vanN:

> Peter, that was the hint required!
> The HWA-template now has become active.
>
> Speculation, but could this be an aspect of changing from Python2.x to 
> Python3.x?
>
>
> Op zondag 2 mei 2021 om 23:06:42 UTC+2 schreef peterq...@gmail.com:
>
>> Looks like that could be it. The .formatted is turning the barometer 
>> value into a string and comparing it against zero, which is an int. Might 
>> try 
>>
>> $trend.barometer.raw > 0
>>
>> I would have thought that Python would have cast the string into an int 
>> for you, but apparently not. 
>>
>> On Sun, May 2, 2021 at 1:45 PM Ton vanN  wrote:
>>
>>> The error report for the HWA-template is like
>>>  
>>>May  2 22:20:46 Raspberry8 weewx[2139] ERROR 
>>> weewx.cheetahgenerator:  Ignoring template 
>>> /home/weewx/skins/Standard/openweerdata.htm.tmpl
>>> May  2 22:20:46 Raspberry8 weewx[2139] ERROR 
>>> weewx.cheetahgenerator:  Reason: '>' not supported between instances of 
>>> 'str' and 'int'
>>>
>>> That seems to point to the section in the template which determines 
>>> barotrend
>>> with first scriptlines
>>>
>>>   #if $trend.barometer.formatted > 0
>>>   \$barTrend = "Rising";
>>>   #end if
>>>
>>> *Not* *[?]* to the earlier section which translates windDir.raw into 
>>> windDirection, because those scriptlines have 'real' values for comparison 
>>>
>>>   #if $current.windDir.raw >= 11.25 and $current.windDir.raw < 33.75
>>>   \$windDirection = "NNO"; 
>>>
>>> Apparently some tiny detail which differentiates a comparison with 
>>> integer value and a comparison with real value:
>>> *or* is the problem in the lefthandside of the comparison?
>>> Op zondag 2 mei 2021 om 21:29:59 UTC+2 schreef Ton vanN:
>>>
>>>> That aspect of /home/weewx/skin/basic now solved.
>>>> Related question: solution also applicable for v4.5?
>>>>
>>>> Now focus on finding solution for HWA-template. 
>>>>
>>>> Op zondag 2 mei 2021 om 17:26:42 UTC+2 schreef tke...@gmail.com:
>>>>
>>>>> It looks like the example skin "basic" has a few issues. To get it to 
>>>>> work, go into basic/index.html.tmpl and change this
>>>>>
>>>>>   
>>>>> #include $Extras.current
>>>>>         
>>>>> #include $Extras.hilo
>>>>>   
>>>>>
>>>>> to this
>>>>>
>>>>>   
>>>>> #include "current.inc"
>>>>> 
>>>>> #include "hilo.inc"
>>>>>   
>>>>>
>>>>> In the file current.inc, change this
>>>>>
>>>>> #if $trend.windSpeed.formatted > 0
>>>>>   
>>>>> #elif $trend.windSpeed.formatted < 0
>>>>>   
>>>>> #end if
>>>>>
>>>>>
>>>>> to this
>>>>>
>>>>> #if $trend.windSpeed.raw > 0
>>>>>   
>>>>> #elif $trend.windSpeed.raw < 0
>>>>>   
>>>>> #end if
>>>>>
>>>>>
>>>>> On Sun, May 2, 2021 at 12:45 AM Ton vanN  wrote:
>>>>>
>>>>>> Digging a bit deeper, the reason given for that errorreport is 
>>>>>> correct, because subfolder INST_SKIN_ROOT indeed does not exist
>>>>>> Reason: [Errno 2] Bestand of map bestaat niet: 
>>>>>> '/home/weewx/skins/basic/INST_SKIN_ROOT/basic/current.inc'
>>>>>> But why is WeeWx asking for it? This is standard configuration 
>>>>>> (besides my activation of StdReport and related mod of skin.conf).
>>>>>>
>>>>>> Op zondag 2 mei 2021 om 

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

Peter, that was the hint required!
The HWA-template now has become active.

Speculation, but could this be an aspect of changing from Python2.x to 
Python3.x?


Op zondag 2 mei 2021 om 23:06:42 UTC+2 schreef peterq...@gmail.com:

> Looks like that could be it. The .formatted is turning the barometer value 
> into a string and comparing it against zero, which is an int. Might try 
>
> $trend.barometer.raw > 0
>
> I would have thought that Python would have cast the string into an int 
> for you, but apparently not. 
>
> On Sun, May 2, 2021 at 1:45 PM Ton vanN  wrote:
>
>> The error report for the HWA-template is like
>>  
>>May  2 22:20:46 Raspberry8 weewx[2139] ERROR 
>> weewx.cheetahgenerator:  Ignoring template 
>> /home/weewx/skins/Standard/openweerdata.htm.tmpl
>> May  2 22:20:46 Raspberry8 weewx[2139] ERROR 
>> weewx.cheetahgenerator:  Reason: '>' not supported between instances of 
>> 'str' and 'int'
>>
>> That seems to point to the section in the template which determines 
>> barotrend
>> with first scriptlines
>>
>>   #if $trend.barometer.formatted > 0
>>   \$barTrend = "Rising";
>>   #end if
>>
>> *Not* *[?]* to the earlier section which translates windDir.raw into 
>> windDirection, because those scriptlines have 'real' values for comparison 
>>
>>   #if $current.windDir.raw >= 11.25 and $current.windDir.raw < 33.75
>>   \$windDirection = "NNO"; 
>>
>> Apparently some tiny detail which differentiates a comparison with 
>> integer value and a comparison with real value:
>> *or* is the problem in the lefthandside of the comparison?
>> Op zondag 2 mei 2021 om 21:29:59 UTC+2 schreef Ton vanN:
>>
>>> That aspect of /home/weewx/skin/basic now solved.
>>> Related question: solution also applicable for v4.5?
>>>
>>> Now focus on finding solution for HWA-template. 
>>>
>>> Op zondag 2 mei 2021 om 17:26:42 UTC+2 schreef tke...@gmail.com:
>>>
>>>> It looks like the example skin "basic" has a few issues. To get it to 
>>>> work, go into basic/index.html.tmpl and change this
>>>>
>>>>   
>>>> #include $Extras.current
>>>> 
>>>> #include $Extras.hilo
>>>>   
>>>>
>>>> to this
>>>>
>>>>   
>>>> #include "current.inc"
>>>> 
>>>> #include "hilo.inc"
>>>>   
>>>>
>>>> In the file current.inc, change this
>>>>
>>>> #if $trend.windSpeed.formatted > 0
>>>>   
>>>> #elif $trend.windSpeed.formatted < 0
>>>>   
>>>> #end if
>>>>
>>>>
>>>> to this
>>>>
>>>> #if $trend.windSpeed.raw > 0
>>>>   
>>>> #elif $trend.windSpeed.raw < 0
>>>>   
>>>> #end if
>>>>
>>>>
>>>> On Sun, May 2, 2021 at 12:45 AM Ton vanN  wrote:
>>>>
>>>>> Digging a bit deeper, the reason given for that errorreport is 
>>>>> correct, because subfolder INST_SKIN_ROOT indeed does not exist
>>>>> Reason: [Errno 2] Bestand of map bestaat niet: 
>>>>> '/home/weewx/skins/basic/INST_SKIN_ROOT/basic/current.inc'
>>>>> But why is WeeWx asking for it? This is standard configuration 
>>>>> (besides my activation of StdReport and related mod of skin.conf).
>>>>>
>>>>> Op zondag 2 mei 2021 om 09:27:56 UTC+2 schreef Ton vanN:
>>>>>
>>>>>> Perhaps related:
>>>>>> the error reported in time-segment 08:21:58 is strange, because the 
>>>>>> file index.html.tmpl is actually present at the indicated location.
>>>>>>
>>>>>> Op zondag 2 mei 2021 om 08:35:33 UTC+2 schreef Ton vanN:
>>>>>>
>>>>> Tom,
>>>>>>> ;-) That was a really good advice!
>>>>>>> Turned to running WeeWX as daemon, started the logging and got a 
>>>>>>> different read-out which now includes a reference to the HWA-template.
>>>>>>> That confirms my 'nagging feeling' that something is not OK with the 
>>>>>>> handling of that HWA-template: see time-segment 08:21:59
>>>>>>> Next step is finding a soulution .
>>>>>>&g

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

The error report for the HWA-template is like
 
   May  2 22:20:46 Raspberry8 weewx[2139] ERROR weewx.cheetahgenerator: 
 Ignoring template /home/weewx/skins/Standard/openweerdata.htm.tmpl
May  2 22:20:46 Raspberry8 weewx[2139] ERROR 
weewx.cheetahgenerator:  Reason: '>' not supported between instances of 
'str' and 'int'

That seems to point to the section in the template which determines 
barotrend
with first scriptlines

  #if $trend.barometer.formatted > 0
  \$barTrend = "Rising";
  #end if

*Not* *[?]* to the earlier section which translates windDir.raw into 
windDirection, because those scriptlines have 'real' values for comparison 

  #if $current.windDir.raw >= 11.25 and $current.windDir.raw < 33.75
  \$windDirection = "NNO"; 

Apparently some tiny detail which differentiates a comparison with integer 
value and a comparison with real value:
*or* is the problem in the lefthandside of the comparison?
Op zondag 2 mei 2021 om 21:29:59 UTC+2 schreef Ton vanN:

> That aspect of /home/weewx/skin/basic now solved.
> Related question: solution also applicable for v4.5?
>
> Now focus on finding solution for HWA-template. 
>
> Op zondag 2 mei 2021 om 17:26:42 UTC+2 schreef tke...@gmail.com:
>
>> It looks like the example skin "basic" has a few issues. To get it to 
>> work, go into basic/index.html.tmpl and change this
>>
>>   
>> #include $Extras.current
>> 
>> #include $Extras.hilo
>>   
>>
>> to this
>>
>>   
>> #include "current.inc"
>> 
>> #include "hilo.inc"
>>   
>>
>> In the file current.inc, change this
>>
>> #if $trend.windSpeed.formatted > 0
>>   
>> #elif $trend.windSpeed.formatted < 0
>>   
>> #end if
>>
>>
>> to this
>>
>> #if $trend.windSpeed.raw > 0
>>   
>> #elif $trend.windSpeed.raw < 0
>>   
>> #end if
>>
>>
>> On Sun, May 2, 2021 at 12:45 AM Ton vanN  wrote:
>>
>>> Digging a bit deeper, the reason given for that errorreport is correct, 
>>> because subfolder INST_SKIN_ROOT indeed does not exist
>>> Reason: [Errno 2] Bestand of map bestaat niet: 
>>> '/home/weewx/skins/basic/INST_SKIN_ROOT/basic/current.inc'
>>> But why is WeeWx asking for it? This is standard configuration (besides 
>>> my activation of StdReport and related mod of skin.conf).
>>>
>>> Op zondag 2 mei 2021 om 09:27:56 UTC+2 schreef Ton vanN:
>>>
>>>> Perhaps related:
>>>> the error reported in time-segment 08:21:58 is strange, because the 
>>>> file index.html.tmpl is actually present at the indicated location.
>>>>
>>>> Op zondag 2 mei 2021 om 08:35:33 UTC+2 schreef Ton vanN:
>>>>
>>> Tom,
>>>>> ;-) That was a really good advice!
>>>>> Turned to running WeeWX as daemon, started the logging and got a 
>>>>> different read-out which now includes a reference to the HWA-template.
>>>>> That confirms my 'nagging feeling' that something is not OK with the 
>>>>> handling of that HWA-template: see time-segment 08:21:59
>>>>> Next step is finding a soulution .
>>>>>
>>>>> Op zaterdag 1 mei 2021 om 20:02:10 UTC+2 schreef tke...@gmail.com:
>>>>>
>>>>>> This is most likely being caused by the terminal session detaching 
>>>>>> from the process. This can happen when you ssh into a computer, start a 
>>>>>> process, then exit the ssh session.
>>>>>>
>>>>>> Either run weewxd as a daemon, or keep the terminal window open.
>>>>>>
>>>>>> That's the best I can come up with.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, May 1, 2021 at 4:24 AM Anton vanNwnhzn@GMail <
>>>>>> ton...@gmail.com> wrote:
>>>>>>
>>>>>>> Addition to description of *Sequence1*.
>>>>>>>
>>>>>>> Once weewx has been started, at Putty's CLI appears the expected 
>>>>>>> stream of print-out.
>>>>>>> At the keyboard break that stream ends with an error report.
>>>>>>> Perhaps that error report also provides some relevant info?
>>>>>>> See below the last printout from the loop and the error report 
>>>>>>> mentioned above.
>>>>>>>

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

That aspect of /home/weewx/skin/basic now solved.
Related question: solution also applicable for v4.5?

Now focus on finding solution for HWA-template. 

Op zondag 2 mei 2021 om 17:26:42 UTC+2 schreef tke...@gmail.com:

> It looks like the example skin "basic" has a few issues. To get it to 
> work, go into basic/index.html.tmpl and change this
>
>   
> #include $Extras.current
> 
> #include $Extras.hilo
>   
>
> to this
>
>   
> #include "current.inc"
> 
> #include "hilo.inc"
>   
>
> In the file current.inc, change this
>
> #if $trend.windSpeed.formatted > 0
>   
> #elif $trend.windSpeed.formatted < 0
>   
> #end if
>
>
> to this
>
> #if $trend.windSpeed.raw > 0
>   
> #elif $trend.windSpeed.raw < 0
>   
> #end if
>
>
> On Sun, May 2, 2021 at 12:45 AM Ton vanN  wrote:
>
>> Digging a bit deeper, the reason given for that errorreport is correct, 
>> because subfolder INST_SKIN_ROOT indeed does not exist
>> Reason: [Errno 2] Bestand of map bestaat niet: 
>> '/home/weewx/skins/basic/INST_SKIN_ROOT/basic/current.inc'
>> But why is WeeWx asking for it? This is standard configuration (besides 
>> my activation of StdReport and related mod of skin.conf).
>>
>> Op zondag 2 mei 2021 om 09:27:56 UTC+2 schreef Ton vanN:
>>
>>> Perhaps related:
>>> the error reported in time-segment 08:21:58 is strange, because the file 
>>> index.html.tmpl is actually present at the indicated location.
>>>
>>> Op zondag 2 mei 2021 om 08:35:33 UTC+2 schreef Ton vanN:
>>>
>> Tom,
>>>> ;-) That was a really good advice!
>>>> Turned to running WeeWX as daemon, started the logging and got a 
>>>> different read-out which now includes a reference to the HWA-template.
>>>> That confirms my 'nagging feeling' that something is not OK with the 
>>>> handling of that HWA-template: see time-segment 08:21:59
>>>> Next step is finding a soulution .
>>>>
>>>> Op zaterdag 1 mei 2021 om 20:02:10 UTC+2 schreef tke...@gmail.com:
>>>>
>>>>> This is most likely being caused by the terminal session detaching 
>>>>> from the process. This can happen when you ssh into a computer, start a 
>>>>> process, then exit the ssh session.
>>>>>
>>>>> Either run weewxd as a daemon, or keep the terminal window open.
>>>>>
>>>>> That's the best I can come up with.
>>>>>
>>>>>
>>>>>
>>>>> On Sat, May 1, 2021 at 4:24 AM Anton vanNwnhzn@GMail  
>>>>> wrote:
>>>>>
>>>>>> Addition to description of *Sequence1*.
>>>>>>
>>>>>> Once weewx has been started, at Putty's CLI appears the expected 
>>>>>> stream of print-out.
>>>>>> At the keyboard break that stream ends with an error report.
>>>>>> Perhaps that error report also provides some relevant info?
>>>>>> See below the last printout from the loop and the error report 
>>>>>> mentioned above.
>>>>>>
>>>>>> LOOP:   2021-05-01 13:17:59 CEST (1619867879) altimeter: 
>>>>>> 31.165113295698216, appTemp: 28.451970776082117, barometer: 
>>>>>> 31.0991633433, cloudbase: 1300.0558352360692,consBatteryVoltage: 
>>>>>> 12.743352544782736, dateTime: 1619867879, dewpoint: 27.19647824994742, 
>>>>>> heatindex: 32.6713164908827, heatingVoltage: 11.71583632592742, humidex: 
>>>>>> 32.6713164908827, inDewpoint: 31.079532540856405, inHumidity: 
>>>>>> 29.9665337326, inTemp: 63.0167331337, inTempBatteryStatus: 0, 
>>>>>> maxSolarRad: 812.0133117257177, outHumidity: 79.9749002984, outTemp: 
>>>>>> 32.6713164908827, outTempBatteryStatus: 0, pressure: 31.0991633433, 
>>>>>> radiation: 888.7102401456455, rain: 0, rainBatteryStatus: 0, rainRate: 
>>>>>> 0.0, 
>>>>>> referenceVoltage: 12.0, rxCheckPercent: 45.10949739082836, 
>>>>>> supplyVoltage: 
>>>>>> 12.0, txBatteryStatus: 0, usUnits: 1, UV: 12.441943362039037, 
>>>>>> windBatteryStatus: 0, windchill: 32.6713164908827, windDir: 
>>>>>> 359.8494017905, windGust: 5.019940321204786e-07, windGustDir: 
>>>>>> 359.8494017905, windSpeed: 4.1832835950827985e-07
>

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

Digging a bit deeper, the reason given for that errorreport is correct, 
because subfolder INST_SKIN_ROOT indeed does not exist
Reason: [Errno 2] Bestand of map bestaat niet: 
'/home/weewx/skins/basic/INST_SKIN_ROOT/basic/current.inc'
But why is WeeWx asking for it? This is standard configuration (besides my 
activation of StdReport and related mod of skin.conf).

Op zondag 2 mei 2021 om 09:27:56 UTC+2 schreef Ton vanN:

> Perhaps related:
> the error reported in time-segment 08:21:58 is strange, because the file 
> index.html.tmpl is actually present at the indicated location.
>
> Op zondag 2 mei 2021 om 08:35:33 UTC+2 schreef Ton vanN:
>
>> Tom,
>> ;-) That was a really good advice!
>> Turned to running WeeWX as daemon, started the logging and got a 
>> different read-out which now includes a reference to the HWA-template.
>> That confirms my 'nagging feeling' that something is not OK with the 
>> handling of that HWA-template: see time-segment 08:21:59
>> Next step is finding a soulution .
>>
>> Op zaterdag 1 mei 2021 om 20:02:10 UTC+2 schreef tke...@gmail.com:
>>
>>> This is most likely being caused by the terminal session detaching from 
>>> the process. This can happen when you ssh into a computer, start a process, 
>>> then exit the ssh session.
>>>
>>> Either run weewxd as a daemon, or keep the terminal window open.
>>>
>>> That's the best I can come up with.
>>>
>>>
>>>
>>> On Sat, May 1, 2021 at 4:24 AM Anton vanNwnhzn@GMail  
>>> wrote:
>>>
>>>> Addition to description of *Sequence1*.
>>>>
>>>> Once weewx has been started, at Putty's CLI appears the expected stream 
>>>> of print-out.
>>>> At the keyboard break that stream ends with an error report.
>>>> Perhaps that error report also provides some relevant info?
>>>> See below the last printout from the loop and the error report 
>>>> mentioned above.
>>>>
>>>> LOOP:   2021-05-01 13:17:59 CEST (1619867879) altimeter: 
>>>> 31.165113295698216, appTemp: 28.451970776082117, barometer: 
>>>> 31.0991633433, cloudbase: 1300.0558352360692,consBatteryVoltage: 
>>>> 12.743352544782736, dateTime: 1619867879, dewpoint: 27.19647824994742, 
>>>> heatindex: 32.6713164908827, heatingVoltage: 11.71583632592742, humidex: 
>>>> 32.6713164908827, inDewpoint: 31.079532540856405, inHumidity: 
>>>> 29.9665337326, inTemp: 63.0167331337, inTempBatteryStatus: 0, 
>>>> maxSolarRad: 812.0133117257177, outHumidity: 79.9749002984, outTemp: 
>>>> 32.6713164908827, outTempBatteryStatus: 0, pressure: 31.0991633433, 
>>>> radiation: 888.7102401456455, rain: 0, rainBatteryStatus: 0, rainRate: 
>>>> 0.0, 
>>>> referenceVoltage: 12.0, rxCheckPercent: 45.10949739082836, supplyVoltage: 
>>>> 12.0, txBatteryStatus: 0, usUnits: 1, UV: 12.441943362039037, 
>>>> windBatteryStatus: 0, windchill: 32.6713164908827, windDir: 
>>>> 359.8494017905, windGust: 5.019940321204786e-07, windGustDir: 
>>>> 359.8494017905, windSpeed: 4.1832835950827985e-07
>>>> ^CTraceback (most recent call last):
>>>>   File "./bin/weewxd", line 264, in 
>>>> main()
>>>>   File "./bin/weewxd", line 157, in main
>>>> engine.run()
>>>>   File "/home/weewx/bin/weewx/engine.py", line 208, in run
>>>> for packet in self.console.genLoopPackets():
>>>>   File "/home/weewx/bin/weewx/drivers/simulator.py", line 162, in 
>>>> genLoopPackets
>>>> time.sleep(sleep_time)
>>>> KeyboardInterrupt
>>>> pi@Raspberry8:/home/weewx $ 
>>>> Op 1-5-2021 om 12:28 schreef Ton vanN:
>>>>
>>>> As requested, a leaner realisation.
>>>> In attached file the results of 2 sequences executed:
>>>> - in both cases 'clean restart' of the raspberry to ensure that no 
>>>> unintended process running, followed by 1 direct switch-on of weewx
>>>> - the sequences differ in the way going to logging, as described in the 
>>>> file
>>>> - in sequence1 apparently oneshot run before weewx stops. Exit of 
>>>> logging is by keyboard break.
>>>> - in sequence2 stream of repeating logging info. Also terminated the 
>>>> logging by keyboard break.
>>>>
>>>> Op vrijdag 30 april 2021 om 17:34:47 UTC+2 schreef tke...@gmail.com:
>>>>
>>>>> You have 

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

Perhaps related:
the error reported in time-segment 08:21:58 is strange, because the file 
index.html.tmpl is actually present at the indicated location.

Op zondag 2 mei 2021 om 08:35:33 UTC+2 schreef Ton vanN:

> Tom,
> ;-) That was a really good advice!
> Turned to running WeeWX as daemon, started the logging and got a different 
> read-out which now includes a reference to the HWA-template.
> That confirms my 'nagging feeling' that something is not OK with the 
> handling of that HWA-template: see time-segment 08:21:59
> Next step is finding a soulution .
>
> Op zaterdag 1 mei 2021 om 20:02:10 UTC+2 schreef tke...@gmail.com:
>
>> This is most likely being caused by the terminal session detaching from 
>> the process. This can happen when you ssh into a computer, start a process, 
>> then exit the ssh session.
>>
>> Either run weewxd as a daemon, or keep the terminal window open.
>>
>> That's the best I can come up with.
>>
>>
>>
>> On Sat, May 1, 2021 at 4:24 AM Anton vanNwnhzn@GMail  
>> wrote:
>>
>>> Addition to description of *Sequence1*.
>>>
>>> Once weewx has been started, at Putty's CLI appears the expected stream 
>>> of print-out.
>>> At the keyboard break that stream ends with an error report.
>>> Perhaps that error report also provides some relevant info?
>>> See below the last printout from the loop and the error report mentioned 
>>> above.
>>>
>>> LOOP:   2021-05-01 13:17:59 CEST (1619867879) altimeter: 
>>> 31.165113295698216, appTemp: 28.451970776082117, barometer: 
>>> 31.0991633433, cloudbase: 1300.0558352360692,consBatteryVoltage: 
>>> 12.743352544782736, dateTime: 1619867879, dewpoint: 27.19647824994742, 
>>> heatindex: 32.6713164908827, heatingVoltage: 11.71583632592742, humidex: 
>>> 32.6713164908827, inDewpoint: 31.079532540856405, inHumidity: 
>>> 29.9665337326, inTemp: 63.0167331337, inTempBatteryStatus: 0, 
>>> maxSolarRad: 812.0133117257177, outHumidity: 79.9749002984, outTemp: 
>>> 32.6713164908827, outTempBatteryStatus: 0, pressure: 31.0991633433, 
>>> radiation: 888.7102401456455, rain: 0, rainBatteryStatus: 0, rainRate: 0.0, 
>>> referenceVoltage: 12.0, rxCheckPercent: 45.10949739082836, supplyVoltage: 
>>> 12.0, txBatteryStatus: 0, usUnits: 1, UV: 12.441943362039037, 
>>> windBatteryStatus: 0, windchill: 32.6713164908827, windDir: 
>>> 359.8494017905, windGust: 5.019940321204786e-07, windGustDir: 
>>> 359.8494017905, windSpeed: 4.1832835950827985e-07
>>> ^CTraceback (most recent call last):
>>>   File "./bin/weewxd", line 264, in 
>>> main()
>>>   File "./bin/weewxd", line 157, in main
>>> engine.run()
>>>   File "/home/weewx/bin/weewx/engine.py", line 208, in run
>>> for packet in self.console.genLoopPackets():
>>>   File "/home/weewx/bin/weewx/drivers/simulator.py", line 162, in 
>>> genLoopPackets
>>> time.sleep(sleep_time)
>>> KeyboardInterrupt
>>> pi@Raspberry8:/home/weewx $ 
>>> Op 1-5-2021 om 12:28 schreef Ton vanN:
>>>
>>> As requested, a leaner realisation.
>>> In attached file the results of 2 sequences executed:
>>> - in both cases 'clean restart' of the raspberry to ensure that no 
>>> unintended process running, followed by 1 direct switch-on of weewx
>>> - the sequences differ in the way going to logging, as described in the 
>>> file
>>> - in sequence1 apparently oneshot run before weewx stops. Exit of 
>>> logging is by keyboard break.
>>> - in sequence2 stream of repeating logging info. Also terminated the 
>>> logging by keyboard break.
>>>
>>> Op vrijdag 30 april 2021 om 17:34:47 UTC+2 schreef tke...@gmail.com:
>>>
>>>> You have many instances of weewxd all running simultaneously. Kill them 
>>>> all, then start one.
>>>>
>>>> On Fri, Apr 30, 2021 at 7:56 AM Ton vanN  wrote:
>>>>
>>>>> As requested.
>>>>>
>>>>> Scanning the logging see repeated reporting of loading of StdReport, 
>>>>> but no text clearly pointing to errors in execution of StandardReport, 
>>>>> nor 
>>>>> any results.
>>>>> But as explained in the first message of this thread, have 'limited' 
>>>>> experience with weewx ...
>>>>>
>>>>> Op vrijdag 30 april 2021 om 11:28:53 UTC+2 schreef gjr80:
>>>>>
>>>>&

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

Tom,
;-) That was a really good advice!
Turned to running WeeWX as daemon, started the logging and got a different 
read-out which now includes a reference to the HWA-template.
That confirms my 'nagging feeling' that something is not OK with the 
handling of that HWA-template: see time-segment 08:21:59
Next step is finding a soulution .

Op zaterdag 1 mei 2021 om 20:02:10 UTC+2 schreef tke...@gmail.com:

> This is most likely being caused by the terminal session detaching from 
> the process. This can happen when you ssh into a computer, start a process, 
> then exit the ssh session.
>
> Either run weewxd as a daemon, or keep the terminal window open.
>
> That's the best I can come up with.
>
>
>
> On Sat, May 1, 2021 at 4:24 AM Anton vanNwnhzn@GMail  
> wrote:
>
>> Addition to description of *Sequence1*.
>>
>> Once weewx has been started, at Putty's CLI appears the expected stream 
>> of print-out.
>> At the keyboard break that stream ends with an error report.
>> Perhaps that error report also provides some relevant info?
>> See below the last printout from the loop and the error report mentioned 
>> above.
>>
>> LOOP:   2021-05-01 13:17:59 CEST (1619867879) altimeter: 
>> 31.165113295698216, appTemp: 28.451970776082117, barometer: 
>> 31.0991633433, cloudbase: 1300.0558352360692,consBatteryVoltage: 
>> 12.743352544782736, dateTime: 1619867879, dewpoint: 27.19647824994742, 
>> heatindex: 32.6713164908827, heatingVoltage: 11.71583632592742, humidex: 
>> 32.6713164908827, inDewpoint: 31.079532540856405, inHumidity: 
>> 29.9665337326, inTemp: 63.0167331337, inTempBatteryStatus: 0, 
>> maxSolarRad: 812.0133117257177, outHumidity: 79.9749002984, outTemp: 
>> 32.6713164908827, outTempBatteryStatus: 0, pressure: 31.0991633433, 
>> radiation: 888.7102401456455, rain: 0, rainBatteryStatus: 0, rainRate: 0.0, 
>> referenceVoltage: 12.0, rxCheckPercent: 45.10949739082836, supplyVoltage: 
>> 12.0, txBatteryStatus: 0, usUnits: 1, UV: 12.441943362039037, 
>> windBatteryStatus: 0, windchill: 32.6713164908827, windDir: 
>> 359.8494017905, windGust: 5.019940321204786e-07, windGustDir: 
>> 359.8494017905, windSpeed: 4.1832835950827985e-07
>> ^CTraceback (most recent call last):
>>   File "./bin/weewxd", line 264, in 
>> main()
>>   File "./bin/weewxd", line 157, in main
>> engine.run()
>>   File "/home/weewx/bin/weewx/engine.py", line 208, in run
>>     for packet in self.console.genLoopPackets():
>>   File "/home/weewx/bin/weewx/drivers/simulator.py", line 162, in 
>> genLoopPackets
>> time.sleep(sleep_time)
>> KeyboardInterrupt
>> pi@Raspberry8:/home/weewx $ 
>> Op 1-5-2021 om 12:28 schreef Ton vanN:
>>
>> As requested, a leaner realisation.
>> In attached file the results of 2 sequences executed:
>> - in both cases 'clean restart' of the raspberry to ensure that no 
>> unintended process running, followed by 1 direct switch-on of weewx
>> - the sequences differ in the way going to logging, as described in the 
>> file
>> - in sequence1 apparently oneshot run before weewx stops. Exit of logging 
>> is by keyboard break.
>> - in sequence2 stream of repeating logging info. Also terminated the 
>> logging by keyboard break.
>>
>> Op vrijdag 30 april 2021 om 17:34:47 UTC+2 schreef tke...@gmail.com:
>>
>>> You have many instances of weewxd all running simultaneously. Kill them 
>>> all, then start one.
>>>
>>> On Fri, Apr 30, 2021 at 7:56 AM Ton vanN  wrote:
>>>
>>>> As requested.
>>>>
>>>> Scanning the logging see repeated reporting of loading of StdReport, 
>>>> but no text clearly pointing to errors in execution of StandardReport, nor 
>>>> any results.
>>>> But as explained in the first message of this thread, have 'limited' 
>>>> experience with weewx ...
>>>>
>>>> Op vrijdag 30 april 2021 om 11:28:53 UTC+2 schreef gjr80:
>>>>
>>>>> The config files and template tell us what should be happening but the 
>>>>> log will tell us what is actually happening. Have you looked in the log? 
>>>>> Are there any errors? You already have debug = 1 in weewx.conf so you 
>>>>> should be able to work out from the log what is being generated and what 
>>>>> is 
>>>>> not. Post at least 10 minutes of log here and we can see what is going 
>>>>> on. 
>>>>>
>>>>> Gary
>>>>> On Friday, 30 April 2021 at 

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

As requested, a leaner realisation.
In attached file the results of 2 sequences executed:
- in both cases 'clean restart' of the raspberry to ensure that no 
unintended process running, followed by 1 direct switch-on of weewx
- the sequences differ in the way going to logging, as described in the file
- in sequence1 apparently oneshot run before weewx stops. Exit of logging 
is by keyboard break.
- in sequence2 stream of repeating logging info. Also terminated the 
logging by keyboard break.

Op vrijdag 30 april 2021 om 17:34:47 UTC+2 schreef tke...@gmail.com:

> You have many instances of weewxd all running simultaneously. Kill them 
> all, then start one.
>
> On Fri, Apr 30, 2021 at 7:56 AM Ton vanN  wrote:
>
>> As requested.
>>
>> Scanning the logging see repeated reporting of loading of StdReport, but 
>> no text clearly pointing to errors in execution of StandardReport, nor any 
>> results.
>> But as explained in the first message of this thread, have 'limited' 
>> experience with weewx ...
>>
>> Op vrijdag 30 april 2021 om 11:28:53 UTC+2 schreef gjr80:
>>
>>> The config files and template tell us what should be happening but the 
>>> log will tell us what is actually happening. Have you looked in the log? 
>>> Are there any errors? You already have debug = 1 in weewx.conf so you 
>>> should be able to work out from the log what is being generated and what is 
>>> not. Post at least 10 minutes of log here and we can see what is going on. 
>>>
>>> Gary
>>> On Friday, 30 April 2021 at 19:00:29 UTC+10 ton...@gmail.com wrote:
>>>
>>>> Tom,
>>>> Puzzled/baffled, because following the hints from you and taking into 
>>>> account also the hints from the much earlier discussion between you and 
>>>> Franklin Bockstael, but still no file openweerdata.htm appearing in folder 
>>>> /home/weewx/public_html.
>>>>
>>>> Have attached the (probably) relevant setup-files:
>>>> - weewx.conf which in folder /home/weewx enables Standard-skin and sets 
>>>> the related HTML_Root to /home/weewx/public_html
>>>> (*on purpose*, to get a different output from 'basic' etc.)
>>>> - skin.conf which in folder /home/weewx/skins/Standard in the 
>>>> [ToDate]-segment at the first lines enables/sets the template for owd (and 
>>>> disables the 'later', other templates)
>>>> - the template openweerdata.htm.tmpl as located in 
>>>> /home/weewx/skins/Standard 
>>>>
>>>> The adapted conf-files seem OK, but now the nagging feeling that the 
>>>> template has an inhibiting error.
>>>> But that is contradicted by the fact that Franklin Bockstael has it in 
>>>> operation since long time without problems.
>>>>
>>>> During testing not running WeeWx as daemon, but 'discrete start' by 
>>>> command ./bin/weexd
>>>>
>>>> Do you see a solution?
>>>>
>>>>
>>>> Op woensdag 28 april 2021 om 15:40:06 UTC+2 schreef tke...@gmail.com:
>>>>
>>>>> I should add that the template must also be listed in the 
>>>>> corresponding skin.conf, in the [[ToDate]] section.
>>>>>
>>>>> On Wed, Apr 28, 2021 at 6:31 AM Tom Keffer  wrote:
>>>>>
>>>>>> Yes, the skin has to be enabled for any of the templates in the 
>>>>>> skin's folder to be processed. So, if you put your "HWA" template in 
>>>>>> ./Standard, then the report StandardReport must be enabled.
>>>>>>
>>>>>> Or, you can put HWA in your "./basic" folder, then enable your basic 
>>>>>> report.
>>>>>>
>>>>>> Either way will work. 
>>>>>>
>>>>>> On Wed, Apr 28, 2021 at 1:07 AM Ton vanN  wrote:
>>>>>>
>>>>>>> *Brainwave?*
>>>>>>> Aiming at a first, basic realisation the folder 
>>>>>>> /home/weewx/skins/Standard seeming the 'obvious' place, the template 
>>>>>>> for 
>>>>>>> generation of the HWA-file was put in that folder.
>>>>>>> Considering similarity with generation of other html-files the call 
>>>>>>> to the HWA-template was put in skin.conf in same folder 
>>>>>>> /home/weewx/skins/Standard
>>>>>>>
>>>>>>> Looking in /home/weewx at the below setting in weewx.conf, starting 
>>>>>>> to doubt 

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

As requested.

Scanning the logging see repeated reporting of loading of StdReport, but no 
text clearly pointing to errors in execution of StandardReport, nor any 
results.
But as explained in the first message of this thread, have 'limited' 
experience with weewx ...

Op vrijdag 30 april 2021 om 11:28:53 UTC+2 schreef gjr80:

> The config files and template tell us what should be happening but the log 
> will tell us what is actually happening. Have you looked in the log? Are 
> there any errors? You already have debug = 1 in weewx.conf so you should be 
> able to work out from the log what is being generated and what is not. Post 
> at least 10 minutes of log here and we can see what is going on. 
>
> Gary
> On Friday, 30 April 2021 at 19:00:29 UTC+10 ton...@gmail.com wrote:
>
>> Tom,
>> Puzzled/baffled, because following the hints from you and taking into 
>> account also the hints from the much earlier discussion between you and 
>> Franklin Bockstael, but still no file openweerdata.htm appearing in folder 
>> /home/weewx/public_html.
>>
>> Have attached the (probably) relevant setup-files:
>> - weewx.conf which in folder /home/weewx enables Standard-skin and sets 
>> the related HTML_Root to /home/weewx/public_html
>> (*on purpose*, to get a different output from 'basic' etc.)
>> - skin.conf which in folder /home/weewx/skins/Standard in the 
>> [ToDate]-segment at the first lines enables/sets the template for owd (and 
>> disables the 'later', other templates)
>> - the template openweerdata.htm.tmpl as located in 
>> /home/weewx/skins/Standard 
>>
>> The adapted conf-files seem OK, but now the nagging feeling that the 
>> template has an inhibiting error.
>> But that is contradicted by the fact that Franklin Bockstael has it in 
>> operation since long time without problems.
>>
>> During testing not running WeeWx as daemon, but 'discrete start' by 
>> command ./bin/weexd
>>
>> Do you see a solution?
>>
>>
>> Op woensdag 28 april 2021 om 15:40:06 UTC+2 schreef tke...@gmail.com:
>>
>>> I should add that the template must also be listed in the corresponding 
>>> skin.conf, in the [[ToDate]] section.
>>>
>>> On Wed, Apr 28, 2021 at 6:31 AM Tom Keffer  wrote:
>>>
>>>> Yes, the skin has to be enabled for any of the templates in the skin's 
>>>> folder to be processed. So, if you put your "HWA" template in ./Standard, 
>>>> then the report StandardReport must be enabled.
>>>>
>>>> Or, you can put HWA in your "./basic" folder, then enable your basic 
>>>> report.
>>>>
>>>> Either way will work. 
>>>>
>>>> On Wed, Apr 28, 2021 at 1:07 AM Ton vanN  wrote:
>>>>
>>>>> *Brainwave?*
>>>>> Aiming at a first, basic realisation the folder 
>>>>> /home/weewx/skins/Standard seeming the 'obvious' place, the template for 
>>>>> generation of the HWA-file was put in that folder.
>>>>> Considering similarity with generation of other html-files the call to 
>>>>> the HWA-template was put in skin.conf in same folder 
>>>>> /home/weewx/skins/Standard
>>>>>
>>>>> Looking in /home/weewx at the below setting in weewx.conf, starting to 
>>>>> doubt that such choice is correct.
>>>>>
>>>>> [[StandardReport]]
>>>>> # This is the old "Standard" skin. By default, it is not 
>>>>> enabled.
>>>>> skin = Standard
>>>>> enable = false
>>>>>[[basic]]
>>>>> skin = basic
>>>>> HTML_ROOT = /var/weewx/reports
>>>>> [[[Extras]]]
>>>>> current = INST_SKIN_ROOT/basic/current.inc
>>>>> hilo = INST_SKIN_ROOT/basic/hilo.inc
>>>>>
>>>>> If enable=false, *it looks as if*  'Standard'will not be called and 
>>>>> (as consequence no call to the HWA-template at it's present location).
>>>>> But if that assumption is correct, where should I alternatively put 
>>>>> the template and call to the HWA-template to stay in line with 'normal 
>>>>> practise'?
>>>>> *[Or simple enabling of 'Standard'?]*
>>>>> Op woensdag 28 april 2021 om 08:30:52 UTC+2 schreef Ton vanN:
>>>>>
>>>>>> As requested, attached is the repeating segment of the syslog with 
>>>>&

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

Tom,
Puzzled/baffled, because following the hints from you and taking into 
account also the hints from the much earlier discussion between you and 
Franklin Bockstael, but still no file openweerdata.htm appearing in folder 
/home/weewx/public_html.

Have attached the (probably) relevant setup-files:
- weewx.conf which in folder /home/weewx enables Standard-skin and sets the 
related HTML_Root to /home/weewx/public_html
(*on purpose*, to get a different output from 'basic' etc.)
- skin.conf which in folder /home/weewx/skins/Standard in the 
[ToDate]-segment at the first lines enables/sets the template for owd (and 
disables the 'later', other templates)
- the template openweerdata.htm.tmpl as located in 
/home/weewx/skins/Standard 

The adapted conf-files seem OK, but now the nagging feeling that the 
template has an inhibiting error.
But that is contradicted by the fact that Franklin Bockstael has it in 
operation since long time without problems.

During testing not running WeeWx as daemon, but 'discrete start' by command 
./bin/weexd

Do you see a solution?


Op woensdag 28 april 2021 om 15:40:06 UTC+2 schreef tke...@gmail.com:

> I should add that the template must also be listed in the corresponding 
> skin.conf, in the [[ToDate]] section.
>
> On Wed, Apr 28, 2021 at 6:31 AM Tom Keffer  wrote:
>
>> Yes, the skin has to be enabled for any of the templates in the skin's 
>> folder to be processed. So, if you put your "HWA" template in ./Standard, 
>> then the report StandardReport must be enabled.
>>
>> Or, you can put HWA in your "./basic" folder, then enable your basic 
>> report.
>>
>> Either way will work. 
>>
>> On Wed, Apr 28, 2021 at 1:07 AM Ton vanN  wrote:
>>
>>> *Brainwave?*
>>> Aiming at a first, basic realisation the folder 
>>> /home/weewx/skins/Standard seeming the 'obvious' place, the template for 
>>> generation of the HWA-file was put in that folder.
>>> Considering similarity with generation of other html-files the call to 
>>> the HWA-template was put in skin.conf in same folder 
>>> /home/weewx/skins/Standard
>>>
>>> Looking in /home/weewx at the below setting in weewx.conf, starting to 
>>> doubt that such choice is correct.
>>>
>>> [[StandardReport]]
>>> # This is the old "Standard" skin. By default, it is not 
>>> enabled.
>>> skin = Standard
>>> enable = false
>>>[[basic]]
>>> skin = basic
>>> HTML_ROOT = /var/weewx/reports
>>> [[[Extras]]]
>>> current = INST_SKIN_ROOT/basic/current.inc
>>> hilo = INST_SKIN_ROOT/basic/hilo.inc
>>>
>>> If enable=false, *it looks as if*  'Standard'will not be called and (as 
>>> consequence no call to the HWA-template at it's present location).
>>> But if that assumption is correct, where should I alternatively put the 
>>> template and call to the HWA-template to stay in line with 'normal 
>>> practise'?
>>> *[Or simple enabling of 'Standard'?]*
>>> Op woensdag 28 april 2021 om 08:30:52 UTC+2 schreef Ton vanN:
>>>
>>>> As requested, attached is the repeating segment of the syslog with 
>>>> debug=1
>>>>
>>>> Op dinsdag 27 april 2021 om 13:21:12 UTC+2 schreef tke...@gmail.com:
>>>>
>>>>> Please try again, but this time set debug=1 first. 
>>>>>
>>>>> Stop weewx
>>>>> Set debug=1 (in weewx.conf)
>>>>> Restart weewx
>>>>> Post the log from startup. 
>>>>>
>>>>> -tk
>>>>>
>>>>> On Fri, Mar 26, 2021 at 5:41 AM Ton vanN  wrote:
>>>>>
>>>>>> Related syslog-segment from RPI_CLI obtained with PuttySSH
>>>>>>
>>>>>> Op vrijdag 26 maart 2021 om 10:00:19 UTC+1 schreef Ton vanN:
>>>>>>
>>>>>>> Novice to WeeWX.
>>>>>>> Have the main progam as simulator up and running (= see files 
>>>>>>> updating in folder public_html ).
>>>>>>> Now trying to implement a template to generate an uploadfile for 
>>>>>>> HetWeerActueel.
>>>>>>> [has been discussed earlier in this forum, but that discussion 
>>>>>>> apparently not ending with working solution]
>>>>>>>
>>>>>>> Template [attached in zip-file] should generate a htm-file.
>>>>>>> For activation of the template I insert

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

*Brainwave?*
Aiming at a first, basic realisation the folder /home/weewx/skins/Standard 
seeming the 'obvious' place, the template for generation of the HWA-file 
was put in that folder.
Considering similarity with generation of other html-files the call to the 
HWA-template was put in skin.conf in same folder /home/weewx/skins/Standard

Looking in /home/weewx at the below setting in weewx.conf, starting to 
doubt that such choice is correct.

[[StandardReport]]
# This is the old "Standard" skin. By default, it is not 
enabled.
skin = Standard
enable = false
   [[basic]]
skin = basic
HTML_ROOT = /var/weewx/reports
[[[Extras]]]
current = INST_SKIN_ROOT/basic/current.inc
hilo = INST_SKIN_ROOT/basic/hilo.inc

If enable=false, *it looks as if*  'Standard'will not be called and (as 
consequence no call to the HWA-template at it's present location).
But if that assumption is correct, where should I alternatively put the 
template and call to the HWA-template to stay in line with 'normal 
practise'?
*[Or simple enabling of 'Standard'?]*
Op woensdag 28 april 2021 om 08:30:52 UTC+2 schreef Ton vanN:

> As requested, attached is the repeating segment of the syslog with debug=1
>
> Op dinsdag 27 april 2021 om 13:21:12 UTC+2 schreef tke...@gmail.com:
>
>> Please try again, but this time set debug=1 first. 
>>
>> Stop weewx
>> Set debug=1 (in weewx.conf)
>> Restart weewx
>> Post the log from startup. 
>>
>> -tk
>>
>> On Fri, Mar 26, 2021 at 5:41 AM Ton vanN  wrote:
>>
>>> Related syslog-segment from RPI_CLI obtained with PuttySSH
>>>
>>> Op vrijdag 26 maart 2021 om 10:00:19 UTC+1 schreef Ton vanN:
>>>
>>>> Novice to WeeWX.
>>>> Have the main progam as simulator up and running (= see files updating 
>>>> in folder public_html ).
>>>> Now trying to implement a template to generate an uploadfile for 
>>>> HetWeerActueel.
>>>> [has been discussed earlier in this forum, but that discussion 
>>>> apparently not ending with working solution]
>>>>
>>>> Template [attached in zip-file] should generate a htm-file.
>>>> For activation of the template I inserted the following text in 
>>>> /home/weewx/skins/Standard/skin.conf at the end of the section 
>>>> CheetahGenerator
>>>>
>>>> [[HWA]]
>>>> # Report that generates an uploadfile for HetWeerActueel.
>>>> [[[OWD]]]
>>>> template = openweerdata_wx.htm.tmpl
>>>>  
>>>> Would expect the generated htm-file to appear in folder public_html
>>>> When running WeeWX no errors (which is OK), but also nowhere the 
>>>> expected htm-file:
>>>> what needs to be done to activate file-generation?  
>>>>
>>> -- 
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/d6591a4a-09d9-41f7-8092-5e0fcbc113ccn%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/d6591a4a-09d9-41f7-8092-5e0fcbc113ccn%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/33bd4fee-48c9-42dd-9e1e-ce04ba727dddn%40googlegroups.com.

Re: [weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

As requested, attached is the repeating segment of the syslog with debug=1

Op dinsdag 27 april 2021 om 13:21:12 UTC+2 schreef tke...@gmail.com:

> Please try again, but this time set debug=1 first. 
>
> Stop weewx
> Set debug=1 (in weewx.conf)
> Restart weewx
> Post the log from startup. 
>
> -tk
>
> On Fri, Mar 26, 2021 at 5:41 AM Ton vanN  wrote:
>
>> Related syslog-segment from RPI_CLI obtained with PuttySSH
>>
>> Op vrijdag 26 maart 2021 om 10:00:19 UTC+1 schreef Ton vanN:
>>
>>> Novice to WeeWX.
>>> Have the main progam as simulator up and running (= see files updating 
>>> in folder public_html ).
>>> Now trying to implement a template to generate an uploadfile for 
>>> HetWeerActueel.
>>> [has been discussed earlier in this forum, but that discussion 
>>> apparently not ending with working solution]
>>>
>>> Template [attached in zip-file] should generate a htm-file.
>>> For activation of the template I inserted the following text in 
>>> /home/weewx/skins/Standard/skin.conf at the end of the section 
>>> CheetahGenerator
>>>
>>> [[HWA]]
>>> # Report that generates an uploadfile for HetWeerActueel.
>>> [[[OWD]]]
>>> template = openweerdata_wx.htm.tmpl
>>>  
>>> Would expect the generated htm-file to appear in folder public_html
>>> When running WeeWX no errors (which is OK), but also nowhere the 
>>> expected htm-file:
>>> what needs to be done to activate file-generation?  
>>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/d6591a4a-09d9-41f7-8092-5e0fcbc113ccn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/d6591a4a-09d9-41f7-8092-5e0fcbc113ccn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/45aeb6de-d3c2-4854-acd3-bafded1c3945n%40googlegroups.com.
Apr 28 08:21:46 Raspberry8 weewx[2529] CRITICAL __main__:   Waiting 10 
seconds then retrying...
Apr 28 08:21:56 Raspberry8 weewx[2529] INFO __main__: retrying...
Apr 28 08:21:56 Raspberry8 weewx[2529] INFO __main__: Using configuration file 
/home/weewx/weewx.conf
Apr 28 08:21:56 Raspberry8 weewx[2529] INFO __main__: Debug is 1
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG __main__: Initializing engine
Apr 28 08:21:56 Raspberry8 weewx[2529] INFO weewx.engine: Loading station type 
Simulator (weewx.drivers.simulator)
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdTimeSynch
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
Apr 28 08:21:56 Raspberry8 weewx[2529] INFO weewx.engine: StdConvert target 
unit is 0x1
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdConvert
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdCalibrate
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG weewx.engine: Loading service 
weewx.engine.StdQC
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdQC
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG weewx.manager: Daily summary 
version is 4.0
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG weewx.engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdWXXTypes
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdWXXTypes
Apr 28 08:21:56 Raspberry8 weewx[2529] DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdPressureCooker
Apr 28 08:21:57 Raspberry8 weewx[2529] DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdPressureCooker
Apr 28 08:21:57 Raspberry8 weewx[2529] DEBUG weewx.engine: Loading service 
weewx.

[weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

Expecting the result-file in folders /var/weewx/reports and by alias in  
/home/weewx/public_html, but nothing appears.

Studying skin.conf under /home/weewx/skins/Standard have feeling that the 
link in section [[ToDate]] should[?] be

#[[ToDate]]
# added for generation of HWA-uploadfile
[[[owd]]]
template = openweerdata_wx.htm.tmpl

But still no output coming.

Is the above setup correct assumption and fill-in,  some subtle missing 
element, or completely on wrong track? 
Hints much appreciated.   


Op vrijdag 26 maart 2021 om 13:41:42 UTC+1 schreef Ton vanN:

> Related syslog-segment from RPI_CLI obtained with PuttySSH
>
> Op vrijdag 26 maart 2021 om 10:00:19 UTC+1 schreef Ton vanN:
>
>> Novice to WeeWX.
>> Have the main progam as simulator up and running (= see files updating in 
>> folder public_html ).
>> Now trying to implement a template to generate an uploadfile for 
>> HetWeerActueel.
>> [has been discussed earlier in this forum, but that discussion apparently 
>> not ending with working solution]
>>
>> Template [attached in zip-file] should generate a htm-file.
>> For activation of the template I inserted the following text in 
>> /home/weewx/skins/Standard/skin.conf at the end of the section 
>> CheetahGenerator
>>
>> [[HWA]]
>> # Report that generates an uploadfile for HetWeerActueel.
>> [[[OWD]]]
>> template = openweerdata_wx.htm.tmpl
>>  
>> Would expect the generated htm-file to appear in folder public_html
>> When running WeeWX no errors (which is OK), but also nowhere the expected 
>> htm-file:
>> what needs to be done to activate file-generation?  
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a5586573-8597-46d0-815e-7733bfe336b0n%40googlegroups.com.

[weewx-user] Re: Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

Related syslog-segment from RPI_CLI obtained with PuttySSH

Op vrijdag 26 maart 2021 om 10:00:19 UTC+1 schreef Ton vanN:

> Novice to WeeWX.
> Have the main progam as simulator up and running (= see files updating in 
> folder public_html ).
> Now trying to implement a template to generate an uploadfile for 
> HetWeerActueel.
> [has been discussed earlier in this forum, but that discussion apparently 
> not ending with working solution]
>
> Template [attached in zip-file] should generate a htm-file.
> For activation of the template I inserted the following text in 
> /home/weewx/skins/Standard/skin.conf at the end of the section 
> CheetahGenerator
>
> [[HWA]]
> # Report that generates an uploadfile for HetWeerActueel.
> [[[OWD]]]
> template = openweerdata_wx.htm.tmpl
>  
> Would expect the generated htm-file to appear in folder public_html
> When running WeeWX no errors (which is OK), but also nowhere the expected 
> htm-file:
> what needs to be done to activate file-generation?  
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d6591a4a-09d9-41f7-8092-5e0fcbc113ccn%40googlegroups.com.
 sudo tail -f /var/log/syslog

Mar 14 08:24:47 raspberrypi dhcpcd[423]: wlan0: received approval for 
192.168.0.187
Mar 14 08:24:47 raspberrypi dhcpcd[423]: wlan0: received approval for 
192.168.0.187
Mar 14 08:24:47 raspberrypi dhcpcd[423]: wlan0: received approval for 
192.168.0.187
Mar 14 08:24:47 raspberrypi weewx[31930] INFO __main__: retrying...
Mar 14 08:24:47 raspberrypi dhcpcd[423]: wlan0: received approval for 
192.168.0.187
Mar 14 08:24:47 raspberrypi weewx[31930] INFO __main__: Using configuration 
file /home/weewx/weewx.conf
Mar 14 08:24:47 raspberrypi weewx[31930] INFO __main__: Debug is 0
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: Loading station 
type Simulator (weewx.drivers.simulator)
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: StdConvert target 
unit is 0x1
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: Archive will use 
data binding wx_binding
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: Using archive 
interval of 300 seconds (specified in weewx configuration)
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.restx: StationRegistry: 
Registration not requested.
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.restx: Wunderground: 
Posting not enabled.
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.restx: PWSweather: Posting 
not enabled.
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.restx: CWOP: Posting not 
enabled.
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.restx: WOW: Posting not 
enabled.
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.restx: AWEKAS: Posting not 
enabled.
Mar 14 08:24:47 raspberrypi weewx[31930] INFO __main__: Starting up weewx 
version 4.4.0
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: Clock error is 
-0.04 seconds (positive is fast)
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.manager: Starting backfill 
of daily summaries
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.manager: Daily summaries up 
to date
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: Starting main 
packet loop.
Mar 14 08:24:48 raspberrypi dhcpcd[423]: wlan0: received approval for 
192.168.0.187
Mar 14 08:24:48 raspberrypi weewx[12140] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Mar 14 08:24:48 raspberrypi dhcpcd[423]: wlan0: received approval for 
192.168.0.187
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__: Caught OSError: 
[Errno 5] Invoer-/uitvoerfout
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__:   Traceback 
(most recent call last):
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__: File 
"/home/weewx/bin/weewxd", line 157, in main
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__:   
engine.run()
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__: File 
"/home/weewx/bin/weewx/engine.py", line 210, in run
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__:   
self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__: File 
"/home/weewx/bin/weewx/engine.py", line 245, in dispatchEvent
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__: **

[weewx-user] Use of template for generation of uploadfile for HetWeerActueel

[Ton vanN]

Novice to WeeWX.
Have the main progam as simulator up and running (= see files updating in 
folder public_html ).
Now trying to implement a template to generate an uploadfile for 
HetWeerActueel.
[has been discussed earlier in this forum, but that discussion apparently 
not ending with working solution]

Template [attached in zip-file] should generate a htm-file.
For activation of the template I inserted the following text in 
/home/weewx/skins/Standard/skin.conf at the end of the section 
CheetahGenerator

[[HWA]]
# Report that generates an uploadfile for HetWeerActueel.
[[[OWD]]]
template = openweerdata_wx.htm.tmpl
 
Would expect the generated htm-file to appear in folder public_html
When running WeeWX no errors (which is OK), but also nowhere the expected 
htm-file:
what needs to be done to activate file-generation?  

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d8a3780f-80e2-48c3-8ee6-2e9ffbd20675n%40googlegroups.com.
<>

[weewx-user] Re: Installing weewx 4.4.0 on RPI: what next after step 5 of setup.htm?

[Ton vanN]

Fresh catch of this morning

Op zaterdag 13 maart 2021 om 20:54:22 UTC+1 schreef vince:

> /var/log/syslog on a pi
>
> On Saturday, March 13, 2021 at 11:13:01 AM UTC-8 ton...@gmail.com wrote:
>
>> Vince,
>> Which logfile is wanted?
>> Reason for the question:
>> the logging at step 5 is passing at flashing speed ..
>>
>> Op zaterdag 13 maart 2021 om 18:46:47 UTC+1 schreef vince:
>>
>>> We cannot help without seeing some logfile information.
>>>
>>> We would need to see your log from the time weewx started through one or 
>>> two reporting cycles.
>>>
>>> On Saturday, March 13, 2021 at 9:36:10 AM UTC-8 ton...@gmail.com wrote:
>>>
 After crash, started with fresh install on Raspberry already having 
 Domoticz (which is including Apache2).
 Used procedure with setup.py as per /home/weewx/docs/setup.htm 
 Progressed with setup *till* Step 6. 
 At step 5. see weewx-messages passing.

 However now lost, because /home/weewx/public_html as mentioned in Step 
 6 is not present.

 During installation apparently something missed to get reporting in 
 place:
 how to correct? Hint to applicable description?



-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d36d304d-231e-4322-905a-149330f70d07n%40googlegroups.com.
 sudo tail -f /var/log/syslog

Mar 14 08:24:47 raspberrypi dhcpcd[423]: wlan0: received approval for 
192.168.0.187
Mar 14 08:24:47 raspberrypi dhcpcd[423]: wlan0: received approval for 
192.168.0.187
Mar 14 08:24:47 raspberrypi dhcpcd[423]: wlan0: received approval for 
192.168.0.187
Mar 14 08:24:47 raspberrypi weewx[31930] INFO __main__: retrying...
Mar 14 08:24:47 raspberrypi dhcpcd[423]: wlan0: received approval for 
192.168.0.187
Mar 14 08:24:47 raspberrypi weewx[31930] INFO __main__: Using configuration 
file /home/weewx/weewx.conf
Mar 14 08:24:47 raspberrypi weewx[31930] INFO __main__: Debug is 0
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: Loading station 
type Simulator (weewx.drivers.simulator)
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: StdConvert target 
unit is 0x1
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: Archive will use 
data binding wx_binding
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: Using archive 
interval of 300 seconds (specified in weewx configuration)
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.restx: StationRegistry: 
Registration not requested.
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.restx: Wunderground: 
Posting not enabled.
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.restx: PWSweather: Posting 
not enabled.
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.restx: CWOP: Posting not 
enabled.
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.restx: WOW: Posting not 
enabled.
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.restx: AWEKAS: Posting not 
enabled.
Mar 14 08:24:47 raspberrypi weewx[31930] INFO __main__: Starting up weewx 
version 4.4.0
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: Clock error is 
-0.04 seconds (positive is fast)
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.manager: Starting backfill 
of daily summaries
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.manager: Daily summaries up 
to date
Mar 14 08:24:47 raspberrypi weewx[31930] INFO weewx.engine: Starting main 
packet loop.
Mar 14 08:24:48 raspberrypi dhcpcd[423]: wlan0: received approval for 
192.168.0.187
Mar 14 08:24:48 raspberrypi weewx[12140] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Mar 14 08:24:48 raspberrypi dhcpcd[423]: wlan0: received approval for 
192.168.0.187
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__: Caught OSError: 
[Errno 5] Invoer-/uitvoerfout
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__:   Traceback 
(most recent call last):
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__: File 
"/home/weewx/bin/weewxd", line 157, in main
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__:   
engine.run()
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__: File 
"/home/weewx/bin/weewx/engine.py", line 210, in run
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__:   
self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
Mar 14 08:24:48 raspberrypi weewx[12140] CRITICAL __main__: File 
"/home/weewx/bin/weewx/engine.py", line 245, in dispatchEvent
Mar 14 08:24:48 raspberrypi 

[weewx-user] Re: Installing weewx 4.4.0 on RPI: what next after step 5 of setup.htm?

[Ton vanN]

Vince,
Which logfile is wanted?
Reason for the question:
the logging at step 5 is passing at flashing speed ..

Op zaterdag 13 maart 2021 om 18:46:47 UTC+1 schreef vince:

> We cannot help without seeing some logfile information.
>
> We would need to see your log from the time weewx started through one or 
> two reporting cycles.
>
> On Saturday, March 13, 2021 at 9:36:10 AM UTC-8 ton...@gmail.com wrote:
>
>> After crash, started with fresh install on Raspberry already having 
>> Domoticz (which is including Apache2).
>> Used procedure with setup.py as per /home/weewx/docs/setup.htm 
>> Progressed with setup *till* Step 6. 
>> At step 5. see weewx-messages passing.
>>
>> However now lost, because /home/weewx/public_html as mentioned in Step 6 
>> is not present.
>>
>> During installation apparently something missed to get reporting in place:
>> how to correct? Hint to applicable description?
>>
>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/55b4c1f7-3df9-47ad-a08d-7fc20ea81cf7n%40googlegroups.com.

[weewx-user] Installing weewx 4.4.0 on RPI: what next after step 5 of setup.htm?

[Ton vanN]

After crash, started with fresh install on Raspberry already having 
Domoticz (which is including Apache2).
Used procedure with setup.py as per /home/weewx/docs/setup.htm 
Progressed with setup *till* Step 6. 
At step 5. see weewx-messages passing.

However now lost, because /home/weewx/public_html as mentioned in Step 6 is 
not present.

During installation apparently something missed to get reporting in place:
how to correct? Hint to applicable description?

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9d11a612-ceec-4feb-9c8e-19cbb0dbb57an%40googlegroups.com.

[weewx-user] Re: Installation of version 4.2.0

[Ton vanN]

'Problem' for adding usb-capability solved by using a command-string 
linking to another usb-module
sudo pip3 install pyusb
After running that string at least the configuration-menu has no complaints 
anymore and shows all devices with usb-interface.

Op woensdag 16 december 2020 om 17:35:08 UTC+1 schreef vince:

> I would simply symlink 'from' the existing tree 'to' the weewx directory:
>ln -s /home/weewx/public_html /home/pi/domoticz/www/weewx
>
> Then you should see the web pages from weewx in your web if you use 
> http://hostname/weewx 
>
>
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d61e40c2-c58e-45f6-927c-94014d9878f4n%40googlegroups.com.

[weewx-user] Re: Installation of version 4.2.0

[Ton vanN]

Making progress: 
now weewx up & running with simulator

Next is  linking to a webserver.
Apache already running on all my Raspberries due to Domoticz.
It's folder (within the Domoticz-installation) is /home/pi/domoticz/www
No folder /var/www present
Therefore references in the WeeWx-setup instructions not immediately 
applicable.
Trying to install Apache at another level results in failure, with response 
as described below.

*CLI-input:*
sudo apt-get install apache2 -y   [also tried with apt 
and pip3, without success]
*Response:*
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd
De statusinformatie wordt gelezen... Klaar
Pakket apache2 is niet beschikbaar, hoewel er naar verwezen wordt door
een ander pakket. Mogelijk betekent dit dat het pakket ontbreekt,
verouderd is, of enkel beschikbaar is van een andere bron
E: Pakket 'apache2' heeft geen kandidaat voor installatie

*Google-translated:*
Package lists are being read ... Done 
Tree of requirements is built The status information is being read ... Done 
Package apache2 is not available, although it is referenced by another 
package. This may mean that the package is missing, obsolete, or only 
available from another source 
E: Package 'apache2' has no candidate for installation

Must be people with previous, comparable experience for this configuration:
*what is a practical solution (regardless whether Apache or other 
webserver, but Apache/nginx for Domoticz must remain operational!)?*
Op woensdag 16 december 2020 om 09:57:52 UTC+1 schreef Ton vanN:

> *Another test from CLI:*
>  sudo pip3 install python3-configobj
> *Response:*
> Looking in indexes: https://pypi.org/simple, 
> https://www.piwheels.org/simple
> Collecting python3-configobj
> Could not install packages due to an EnvironmentError: 404 Client Error: 
> Not Found for url: https://pypi.org/simple/python3-configobj/
>
> *But latest variation finally was OK!*
> sudo pip3 install configobj
> *Response:*
> Looking in indexes: https://pypi.org/simple, 
> https://www.piwheels.org/simple
> Collecting configobj
>   Downloading 
> https://www.piwheels.org/simple/configobj/configobj-5.0.6-py3-none-any.whl
> Requirement already satisfied: six in /usr/lib/python3/dist-packages (from 
> configobj) (1.12.0)
> Installing collected packages: configobj
> Successfully installed configobj-5.0.6
>
>
> Op woensdag 16 december 2020 om 09:45:31 UTC+1 schreef Ton vanN:
>
>> This morning tried a few more variations as described in the 
>> setup-instruction, but no luck with modules configobj and usb.
>> Intending to apply WeeWx, the module for usb is not really required 
>> (instead a UDP-sniffer to be applied), but configobj seems critical.
>>
>> Op woensdag 16 december 2020 om 09:36:19 UTC+1 schreef Ton vanN:
>>
>>> *Example command-line & response *(with basic translation manually 
>>> added behind each line).
>>> Had to use sudo, because otherwise remark that no admission and question 
>>> whether I have administrator rights.
>>> Python3, because (although Python2.7 is on the machine as part of 
>>> Domoticz) generally I try to apply Python3.x
>>>
>>> sudo apt-get install python3-configobj
>>> Pakketlijsten worden ingelezen... Klaar
>>> => Packagelist read ... Ready
>>> Boom van vereisten wordt opgebouwd=> 
>>> Tree of Requisites being built
>>> De statusinformatie wordt gelezen... Klaar      => 
>>> Status info being read ... Ready
>>> E: Kan pakket python3-configobj niet vinden   => 
>>> Package python3-configobj cannot be found
>>>
>>>
>>> Op woensdag 16 december 2020 om 09:24:36 UTC+1 schreef Ton vanN:
>>>
>>>> Vince,
>>>>
>>>> First step was straightforward, simple use of this instruction 
>>>> (considering that the target machine is Raspberry with Raspian Buster 
>>>> (latest):
>>>> http://weewx.com/docs/debian.htm
>>>> Response from the installation process (directly translated from the 
>>>> dutch text):
>>>> python-configobj (>= 4.5) but cannot be installed
>>>> python-cheetah (>= 2.0) but cannot be installed
>>>> python-usb (>= 0.4) but cannot be installed 
>>>>
>>>> After this error report, then I tried this instruction for individual 
>>>> installation of the files:
>>>> http://weewx.com/docs/setup.htm
>>>> Response for each of the files  was that the file could not be found.
>>>>
>>>> Op dinsdag 15 december 2020 om 1

[weewx-user] Re: Installation of version 4.2.0

[Ton vanN]

*Another test from CLI:*
 sudo pip3 install python3-configobj
*Response:*
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting python3-configobj
Could not install packages due to an EnvironmentError: 404 Client Error: 
Not Found for url: https://pypi.org/simple/python3-configobj/

*But latest variation finally was OK!*
sudo pip3 install configobj
*Response:*
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting configobj
  Downloading 
https://www.piwheels.org/simple/configobj/configobj-5.0.6-py3-none-any.whl
Requirement already satisfied: six in /usr/lib/python3/dist-packages (from 
configobj) (1.12.0)
Installing collected packages: configobj
Successfully installed configobj-5.0.6


Op woensdag 16 december 2020 om 09:45:31 UTC+1 schreef Ton vanN:

> This morning tried a few more variations as described in the 
> setup-instruction, but no luck with modules configobj and usb.
> Intending to apply WeeWx, the module for usb is not really required 
> (instead a UDP-sniffer to be applied), but configobj seems critical.
>
> Op woensdag 16 december 2020 om 09:36:19 UTC+1 schreef Ton vanN:
>
>> *Example command-line & response *(with basic translation manually added 
>> behind each line).
>> Had to use sudo, because otherwise remark that no admission and question 
>> whether I have administrator rights.
>> Python3, because (although Python2.7 is on the machine as part of 
>> Domoticz) generally I try to apply Python3.x
>>
>> sudo apt-get install python3-configobj
>> Pakketlijsten worden ingelezen... Klaar=> 
>> Packagelist read ... Ready
>> Boom van vereisten wordt opgebouwd=> Tree 
>> of Requisites being built
>> De statusinformatie wordt gelezen... Klaar  => 
>> Status info being read ... Ready
>> E: Kan pakket python3-configobj niet vinden       => 
>> Package python3-configobj cannot be found
>>
>>
>> Op woensdag 16 december 2020 om 09:24:36 UTC+1 schreef Ton vanN:
>>
>>> Vince,
>>>
>>> First step was straightforward, simple use of this instruction 
>>> (considering that the target machine is Raspberry with Raspian Buster 
>>> (latest):
>>> http://weewx.com/docs/debian.htm
>>> Response from the installation process (directly translated from the 
>>> dutch text):
>>> python-configobj (>= 4.5) but cannot be installed
>>> python-cheetah (>= 2.0) but cannot be installed
>>> python-usb (>= 0.4) but cannot be installed 
>>>
>>> After this error report, then I tried this instruction for individual 
>>> installation of the files:
>>> http://weewx.com/docs/setup.htm
>>> Response for each of the files  was that the file could not be found.
>>>
>>> Op dinsdag 15 december 2020 om 19:08:12 UTC+1 schreef vince:
>>>
>>>> Please post the exact transcript of everything you did and what the 
>>>> computer returned.
>>>>
>>>> It's fine if you would like to google translate the transcript into 
>>>> English.
>>>>
>>>>
>>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d75d1ea5-a85d-4491-ae8b-876bfa055600n%40googlegroups.com.

[weewx-user] Re: Installation of version 4.2.0

[Ton vanN]

This morning tried a few more variations as described in the 
setup-instruction, but no luck with modules configobj and usb.
Intending to apply WeeWx, the module for usb is not really required 
(instead a UDP-sniffer to be applied), but configobj seems critical.

Op woensdag 16 december 2020 om 09:36:19 UTC+1 schreef Ton vanN:

> *Example command-line & response *(with basic translation manually added 
> behind each line).
> Had to use sudo, because otherwise remark that no admission and question 
> whether I have administrator rights.
> Python3, because (although Python2.7 is on the machine as part of 
> Domoticz) generally I try to apply Python3.x
>
> sudo apt-get install python3-configobj
> Pakketlijsten worden ingelezen... Klaar=> 
> Packagelist read ... Ready
> Boom van vereisten wordt opgebouwd=> Tree 
> of Requisites being built
> De statusinformatie wordt gelezen... Klaar  => 
> Status info being read ... Ready
> E: Kan pakket python3-configobj niet vinden   => 
> Package python3-configobj cannot be found
>
>
> Op woensdag 16 december 2020 om 09:24:36 UTC+1 schreef Ton vanN:
>
>> Vince,
>>
>> First step was straightforward, simple use of this instruction 
>> (considering that the target machine is Raspberry with Raspian Buster 
>> (latest):
>> http://weewx.com/docs/debian.htm
>> Response from the installation process (directly translated from the 
>> dutch text):
>> python-configobj (>= 4.5) but cannot be installed
>> python-cheetah (>= 2.0) but cannot be installed
>> python-usb (>= 0.4) but cannot be installed 
>>
>> After this error report, then I tried this instruction for individual 
>> installation of the files:
>> http://weewx.com/docs/setup.htm
>> Response for each of the files  was that the file could not be found.
>>
>> Op dinsdag 15 december 2020 om 19:08:12 UTC+1 schreef vince:
>>
>>> Please post the exact transcript of everything you did and what the 
>>> computer returned.
>>>
>>> It's fine if you would like to google translate the transcript into 
>>> English.
>>>
>>>
>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/092e3b35-c6aa-4a30-98d6-c54184a91d9bn%40googlegroups.com.

[weewx-user] Re: Installation of version 4.2.0

[Ton vanN]

*Example command-line & response *(with basic translation manually added 
behind each line).
Had to use sudo, because otherwise remark that no admission and question 
whether I have administrator rights.
Python3, because (although Python2.7 is on the machine as part of Domoticz) 
generally I try to apply Python3.x

sudo apt-get install python3-configobj
Pakketlijsten worden ingelezen... Klaar=> 
Packagelist read ... Ready
Boom van vereisten wordt opgebouwd=> Tree 
of Requisites being built
De statusinformatie wordt gelezen... Klaar  => 
Status info being read ... Ready
E: Kan pakket python3-configobj niet vinden   => 
Package python3-configobj cannot be found


Op woensdag 16 december 2020 om 09:24:36 UTC+1 schreef Ton vanN:

> Vince,
>
> First step was straightforward, simple use of this instruction 
> (considering that the target machine is Raspberry with Raspian Buster 
> (latest):
> http://weewx.com/docs/debian.htm
> Response from the installation process (directly translated from the dutch 
> text):
> python-configobj (>= 4.5) but cannot be installed
> python-cheetah (>= 2.0) but cannot be installed
> python-usb (>= 0.4) but cannot be installed 
>
> After this error report, then I tried this instruction for individual 
> installation of the files:
> http://weewx.com/docs/setup.htm
> Response for each of the files  was that the file could not be found.
>
> Op dinsdag 15 december 2020 om 19:08:12 UTC+1 schreef vince:
>
>> Please post the exact transcript of everything you did and what the 
>> computer returned.
>>
>> It's fine if you would like to google translate the transcript into 
>> English.
>>
>>
>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4c945063-4f31-4f73-8575-0f15d2cd705cn%40googlegroups.com.

[weewx-user] Re: Installation of version 4.2.0

[Ton vanN]

Vince,

First step was straightforward, simple use of this instruction (considering 
that the target machine is Raspberry with Raspian Buster (latest):
http://weewx.com/docs/debian.htm
Response from the installation process (directly translated from the dutch 
text):
python-configobj (>= 4.5) but cannot be installed
python-cheetah (>= 2.0) but cannot be installed
python-usb (>= 0.4) but cannot be installed 

After this error report, then I tried this instruction for individual 
installation of the files:
http://weewx.com/docs/setup.htm
Response for each of the files  was that the file could not be found.

Op dinsdag 15 december 2020 om 19:08:12 UTC+1 schreef vince:

> Please post the exact transcript of everything you did and what the 
> computer returned.
>
> It's fine if you would like to google translate the transcript into 
> English.
>
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/03a58c1b-156c-471c-a685-da9e3f2083bdn%40googlegroups.com.

[weewx-user] Installation of version 4.2.0

[Ton vanN]

Tried a fresh installation of weewx on Raspberry3B+/RaspianBuster.
Stuck, being unable to install some prerequisites.
Prior to install of main program of weewx already difficulties, but very 
clear message when running the install-instruction from Raspberry's CLI:
apt-get install weewx

Then reports (with related dutch text that installation not possible):
python-configobj (>= 4.5) maar het is niet installeerbaar
python-cheetah (>= 2.0) maar het is niet installeerbaar
python-usb (>= 0.4) maar het is niet installeerbaar

Looked in the manuals and tried the various options, and looked in this 
group, but not yet seen a remedy:

*a workaround available for installation of these 3 prerequisites?Is this 
effect version-dependent, and might install of older version better work?*

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f5f85a12-8982-4283-807b-8efa7d4b9a72n%40googlegroups.com.

[weewx-user] Re: "Grassland Temperature Sum" (or how it is called in English, german "Grünlandtemperatursumme" (GTS))

[Ton vanN]

Your observation is correct: "Grünland' is different from the '*general*' 
GrowingDegreeDays:
wikipedia explains as per https://en.wikipedia.org/wiki/Growing_degree-day 
With your observation if fact you open can of worms, because a large amount 
of variations of GrowingDegree Days related to different animals, insects 
and plants.

;-) Each country has it's variations as well .


Op dinsdag 15 december 2020 om 17:13:50 UTC+1 schreef kk44...@gmail.com:

> I found the aggregation type "growing degree day" ("growdeg"). 
>
> There is a special version of that in Europe. In Germany it is called 
> "Grünlandtemperatursumme". I found no translation to English. The word in 
> the subject is translated word by word.
>
> It is based on the daily average temperature, as growing degree day is. 
> The base temperature is 0 degrees centigrade (32 degrees Fahrenheit).
>
>- In January, all the values are multiplied by 0.5.
>- In February, all the values are multiplied by 0.75.
>- Form March on, the values are used as is.
>
> The sum is calculated from Jan. 1st to May 31st.
>
> The day, when the value exceeds 200 in spring (if calculated in 
> centigrade), is considered the start of growing of the plants.
>
> Some german weather networks ask for those values (sum and date).
>
> It seems to me that the actual aggregation function does not cover that 
> version.
>
>
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/09d811ed-e5fd-4843-969c-695c85edc579n%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Don't forget to add 2 linse at the start of the script!
import json 
import dicttoxml

Op zondag 23 februari 2020 09:16:12 UTC+1 schreef Ton vanN:
>
> Olivier,
>
> 1. Use of JSON/XML
> Why not a database or MQTT? Reason = 'history of System-concept'
> Within my configuration I have a structure in which from various sources a 
> set of JSON/XML-files is uploaded to a 'Central server', and all users can 
> pick as they like:
> *some* of these files are 'public' and used by external applications for 
> remote access to (a piece of) my actual data.
> Obvious then try to fit HP3001 in that structure.
> ;-) Although sure I should modernize (in parallel to the 'production') in 
> the direction of MQTT etc. 
> 2. 'Misuse' of WeeWX
> My 2 PWSes (WS7000 + TFA_Nexus) have directly related software taking the 
> interfaces of the sensors and applying the data for various purposes.
> However, those 2 PWSes have weak elements. In my configuration also an 
> amount of other sensors feeding to Domoticz.
> Some of the weaknesses can be remedied by feeding alternative data from 
> Domoticz, but the software mentioned above only allows limited 'correction'.
> Therefore the idea to make with help of WeeWX-elements ;-) the '3rd & 
> perfect PWS' compiled from the best dataset available in my configuration.
>
> Meanwhile have inserted and tested some 'plugins' in the 
> WS3000-readerscript in the vicinity of lines 380 ~ 390, for orientation in 
> the following script-segment some existing lines before and aft the 
> insertion.
> Result is generation of a JSON-file and an XML-file put in folder /home/pi
> From there an FTP-function (to be choosen by the User) picks the files and 
> processes them for further applications, such as the upload to the 
> mentioned 'Central Server'.
>
> Geef de code hier op...
> # Read datasets for new_packet
> nberrors = 0
> while nberrors < self.max_tries:
> # Get a stream of raw packets, then convert them
> try:
> read_sensors_command = self.COMMANDS['sensor_values']
> raw_data = self._get_raw_data(read_sensors_command)
> # Convert data sets for new_packet
> if not raw_data:  # empty record
> raise IOError("Failed to get any data from the 
> station")
> formatted_data = self._raw_to_data(raw_data, 
> read_sensors_command)
> logdbg('data: %s' % formatted_data)
> new_packet = self._data_to_wxpacket(formatted_data)
> logdbg('packet: %s' % new_packet)
> # Make JSON-file
> with open('/home/pi/HP3001_data.json', 'w') as outfile:
> json.dump(formatted_data, outfile)
> # Make XML-file
> HP3001_xml = dicttoxml.dicttoxml(new_packet, attr_type=
> False)
> xml_output = open("/home/pi/HP3001_data.xml",'w')
> xml_output.write(HP3001_xml)
> xml_output.close()
> # End of JSON/XML-Compilation
> return new_packet
>
>
>
>
> Op zondag 16 februari 2020 17:48:05 UTC+1 schreef Olivier Guyotot:
>>
>> ok, in fact I am getting very confused by what you are trying to do. Why 
>> do you want to mis-use weewx? And why use XML or JSON files, rather than a 
>> database?
>> And if the goal is to integrate the WS-3000 with Domoticz, can't this be 
>> done directly (by writing a plugin or add-on to Domoticz)?
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f39e907a-4f44-4633-8dd9-109c7989a3cb%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Olivier,

Related to reading the WS3000/HP300x, have split the effort in 2 segments:
a) export of data from the WS3000-reader in a layout and to a location 
which can be accessed by the "User".
In my case either JSON-format, or XML-format. 
This function seems best located at side of the Reader.
b) import of the data from a) to 'Users"of which Domoticz is one. 
This function seems best located at side of each "User".

Op zondag 16 februari 2020 17:48:05 UTC+1 schreef Olivier Guyotot:
>
> ok, in fact I am getting very confused by what you are trying to do. Why 
> do you want to mis-use weewx? And why use XML or JSON files, rather than a 
> database?
> And if the goal is to integrate the WS-3000 with Domoticz, can't this be 
> done directly (by writing a plugin or add-on to Domoticz)?
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0b853760-6965-4676-88c0-428f5e08f1f2%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Olivier,

1. Use of JSON/XML
Why not a database or MQTT? Reason = 'history of System-concept'
Within my configuration I have a structure in which from various sources a 
set of JSON/XML-files is uploaded to a 'Central server', and all users can 
pick as they like:
*some* of these files are 'public' and used by external applications for 
remote access to (a piece of) my actual data.
Obvious then try to fit HP3001 in that structure.
;-) Although sure I should modernize (in parallel to the 'production') in 
the direction of MQTT etc. 
2. 'Misuse' of WeeWX
My 2 PWSes (WS7000 + TFA_Nexus) have directly related software taking the 
interfaces of the sensors and applying the data for various purposes.
However, those 2 PWSes have weak elements. In my configuration also an 
amount of other sensors feeding to Domoticz.
Some of the weaknesses can be remedied by feeding alternative data from 
Domoticz, but the software mentioned above only allows limited 'correction'.
Therefore the idea to make with help of WeeWX-elements ;-) the '3rd & 
perfect PWS' compiled from the best dataset available in my configuration.

Meanwhile have inserted and tested some 'plugins' in the 
WS3000-readerscript in the vicinity of lines 380 ~ 390, for orientation in 
the following script-segment some existing lines before and aft the 
insertion.
Result is generation of a JSON-file and an XML-file put in folder /home/pi
>From there an FTP-function (to be choosen by the User) picks the files and 
processes them for further applications, such as the upload to the 
mentioned 'Central Server'.

Geef de code hier op...
# Read datasets for new_packet
nberrors = 0
while nberrors < self.max_tries:
# Get a stream of raw packets, then convert them
try:
read_sensors_command = self.COMMANDS['sensor_values']
raw_data = self._get_raw_data(read_sensors_command)
# Convert data sets for new_packet
if not raw_data:  # empty record
raise IOError("Failed to get any data from the station")
formatted_data = self._raw_to_data(raw_data, 
read_sensors_command)
logdbg('data: %s' % formatted_data)
new_packet = self._data_to_wxpacket(formatted_data)
logdbg('packet: %s' % new_packet)
# Make JSON-file
with open('/home/pi/HP3001_data.json', 'w') as outfile:
json.dump(formatted_data, outfile)
# Make XML-file
HP3001_xml = dicttoxml.dicttoxml(new_packet, attr_type=False
)
xml_output = open("/home/pi/HP3001_data.xml",'w')
xml_output.write(HP3001_xml)
xml_output.close()
# End of JSON/XML-Compilation
return new_packet




Op zondag 16 februari 2020 17:48:05 UTC+1 schreef Olivier Guyotot:
>
> ok, in fact I am getting very confused by what you are trying to do. Why 
> do you want to mis-use weewx? And why use XML or JSON files, rather than a 
> database?
> And if the goal is to integrate the WS-3000 with Domoticz, can't this be 
> done directly (by writing a plugin or add-on to Domoticz)?
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2ce4e57f-0795-411f-8bf9-df9215ba2199%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Is really a side-step and an indirect way, 
but 'mis-using' weewx to create a weatherstation based on 'other data' (for 
example) can be realised via User's Guide · gjr80/weewx-xmlparse Wiki · 
GitHub 
<https://github.com/gjr80/weewx-xmlparse/wiki/User's-Guide#sensor-and-units-mapping>
 
Main requirement seems that you have to compile a compatible XML-file from 
that 'other data'.

Op donderdag 13 februari 2020 21:08:41 UTC+1 schreef Ton vanN:
>
> Olivier has made the read-out of WS3000 an extension to 'another' 
> weatherstation.
> For just reading & processing the output of WS3000 a number of adaptation 
> have to be made.
>
> In my setup I have WeeWX operating with the Simulator which generates 
> fake-weather.
> On the other hand I have plenty of data from real weather-sensors.
> That data is good enough to 'inject' into the Simulator, resulting in one 
> merged data-set with all actual data.
> Have looked around, but not seen in this Google-group, nor in WeeWX-wiki 
> such a possibility.
> Did I miss the info, or not yet developed?
>
>
> Op donderdag 13 februari 2020 11:23:59 UTC+1 schreef Ton vanN:
>>
>> Forgot to hint that RistoK's HowTo-Instructions for fitting the 
>> ws3000-driver on a Raspberry would have been very useful for my efforts 
>> (probably significantly reducing my questions and experiments), but 
>> unfortunately those instructions no longer accessible, because the hosting 
>> server has gone ...
>> Now smells a bit like 'reinventing the wheel', unless somebody can 
>> reproduce those instructions.
>>
>> Op donderdag 13 februari 2020 11:05:46 UTC+1 schreef Ton vanN:
>>>
>>> @Olivier,
>>> Changed the WeeWX-setup to the 'normal' configuration resulting after 
>>> installation with the tar-file and setup.py.
>>> At least the script ws3000.py now starts running, but not without 
>>> errors: error report has been sent by Email.
>>> Looking at the errorreports, *apparently* the version Python2.7 as part 
>>> of Raspian_Buster is conflicting with functions in script ws3000.py
>>>
>>> Op woensdag 12 februari 2020 19:39:15 UTC+1 schreef Olivier Guyotot:
>>>>
>>>> If your installation was done using the Debian package manager, then 
>>>> you need to deploy the ws3000.py file in /usr/share/weewx/user.
>>>>
>>>> And the command to run would presumably be:
>>>> PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/ws3000.py
>>>>
>>>> Unfortunately I have no experience with this type of installation, and 
>>>> no way to test it. I won't be of much help here.
>>>>
>>>> NOTE: I just noticed that in your configuration, you specified driver = 
>>>>>> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
>>>>>> Where did you see this info?
>>>>>> Or otherwise formulated: where shal I put such line?
>>>>>
>>>>> I saw that in the StdConvert issue thread, where you posted part of 
>>>> your weex.conf, didn't you?
>>>>
>>>> What you need is a section such as:
>>>> [WS3000]
>>>> # This section is for the Ambient Weather WS3000
>>>>
>>>> # The driver to use
>>>> driver = user.ws3000
>>>>
>>>> # The station model, e.g., WS3000, WS3000-X3, WS3000-X5 (all the 
>>>> same...)
>>>> model = WS3000
>>>>
>>>> # [Optional] USB read/write timeout (helps on Raspberry Pi)
>>>> # Default is 1000
>>>> timeout =  1000
>>>>
>>>> The rest should be optional.
>>>>
>>>>
>>>>
>>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ca7c7a9c-2c73-4963-b06d-d6fafa0fc149%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

*Question 3,* to have 'loose' coupling between this reader-script and any 
follow-on function.
Is it possible to add one or more lines for export/save of the JSON-file to 
a designated folder?

Op zondag 16 februari 2020 08:38:02 UTC+1 schreef Ton vanN:
>
> Fitted the stand-alone reader *on an 'empty' Raspberry without weewx* 
> (just Raspian_Buster + latest Domoticz_beta).
> In new folder /home/pi/Install-files
> Slight name-change to match my system-configuration.
>
> First result from Putty's CLI shown below.
>
> pixx@raspberrypixx:~ $ sudo python 
> /home/pi/Install_files/hp3001_reader_python_script.py
> Traceback (most recent call last):
>   File "/home/pi/Install_files/hp3001_reader_python_script.py", line 4, in 
> 
> import usb.core
> ImportError: No module named usb.core
>
> More or less as expected the 'import'-section causes first trouble, 
> calling modules not present.
> Not further tested, expecting 'more of the same'. Seems to demonstrate 
> that 'stand-alone' in this case is not 100%.
>
> After installation on that machine of *weewx in the 'basic' form 
> according to the UserGuide*, the result is as below (for my 
> configuration):
>
> pixx@raspberrypixx:~ $ sudo python 
> /home/pi/Install_files/hp3001_reader_python_script.py
> {'dateTime': 1581756586, 'extraHumid4': 88, 'extraHumid5': 88, 
> 'extraHumid2': 54, 'extraHumid3': 88, 'extraHumid1': 56, 'extraTemp4': 
> 11.4, 'extraTemp5': 11.4, 'extraTemp2': 16.8, 'extraTemp3': 11.3, 
> 'usUnits': 17, 'extraTemp1': 17.2}
>
> Looks good!
> Probably simplest solution with least effort is installation of weewx 
> before running of the reader-script:
> installation may be, either 'basic', or via setup.py
>
> *Next questions*
> - the output of this script on Putty's CLI is recognized as a JSON-file
> - reading a program from another programmer is not always easy.
> Therefore the quick requests to the programmer (*Olivier?*) for 
> support of my views:
> 1. What is the line of the script with the print-command and the 
> JSON-file-name for this output?
> 2. Output by the JSON-file now dynamically limited to data from valid 
> sensors.
> => if a sensor goes down (such as 'battery empty'), then a different 
> JSON-file.
> For subsequent processing somewhat easier/simpler if 'empty' fields are 
> still there.
> How/where to change the script to get that?
>
> Op vrijdag 14 februari 2020 08:50:02 UTC+1 schreef Ton vanN:
>>
>> Risto,
>>
>> This script sure helps:
>> after stripping out the comments, it ran without errors at first try!
>> Seems quite a good starting point for my planned further effort in 
>> direction of Domoticz and for graphing with RRDTool.
>> Like you did, tested while weewx still around & active: therefore next to 
>> test that it runs without weewx
>> If not, to be checked whether it runs with weewx installed by the 
>> 'simple' method (spreading the files from /root).
>>
>> Last week ;-) quickly learned a lot about weewx by try& error:
>> Olivier_G thanks for the continuous support for this NOOB!
>>
>> My conclusion for first use of weewx:
>> the first installation of weewx makes the difference, but :-(  that is 
>> unknown for a first time user of weewx.
>> Perhaps a suggestion that in a description for an addition/modification 
>> for aspects such as the driver/interface for HP300x or WS3000 in one of the 
>> first comment lines it is clearly stated that an installation through 
>> setup.py is assumed, putting files in /home/weewx (*or* by the 'simple' 
>> method).
>> After I changed to use of setup.py, the scripts from both Matthewwall and 
>> Olivier_G started running.
>>
>> Op vrijdag 14 februari 2020 07:02:38 UTC+1 schreef Risto H. Kurppa:
>>>
>>> Not sure if it helps anyone, but with Oliver's help about a year or so 
>>> ago, I stripped the ws3000 weewx driver code to work as standalone, without 
>>> needing weewx. That way I was able to just read the values to MQTT for 
>>> further use, without weewx dependency. The code is not cleaned in any way 
>>> and it's actually possible that it still uses some weewx things here or 
>>> there- I still have also weewx installed and haven't tested it without 
>>> weewx.
>>>
>>> https://pastebin.com/37WkUz7N
>>>
>>> Feel free to use & edit & expand. Or Olivier, maybe you want to add an 
>>> standalone script to your github?
>>>
>>> Risto
>>>
>>>
>>>
>>> On Fri, Feb 14, 2020 at 12:26 AM Ton vanN  wrote:
>>>
>>>> Perhaps not 100% done according to Olivie

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Fitted the stand-alone reader *on an 'empty' Raspberry without weewx* (just 
Raspian_Buster + latest Domoticz_beta).
In new folder /home/pi/Install-files
Slight name-change to match my system-configuration.

First result from Putty's CLI shown below.

pixx@raspberrypixx:~ $ sudo python 
/home/pi/Install_files/hp3001_reader_python_script.py
Traceback (most recent call last):
  File "/home/pi/Install_files/hp3001_reader_python_script.py", line 4, in 

import usb.core
ImportError: No module named usb.core

More or less as expected the 'import'-section causes first trouble, calling 
modules not present.
Not further tested, expecting 'more of the same'. Seems to demonstrate that 
'stand-alone' in this case is not 100%.

After installation on that machine of *weewx in the 'basic' form according 
to the UserGuide*, the result is as below (for my configuration):

pixx@raspberrypixx:~ $ sudo python 
/home/pi/Install_files/hp3001_reader_python_script.py
{'dateTime': 1581756586, 'extraHumid4': 88, 'extraHumid5': 88, 
'extraHumid2': 54, 'extraHumid3': 88, 'extraHumid1': 56, 'extraTemp4': 
11.4, 'extraTemp5': 11.4, 'extraTemp2': 16.8, 'extraTemp3': 11.3, 
'usUnits': 17, 'extraTemp1': 17.2}

Looks good!
Probably simplest solution with least effort is installation of weewx 
before running of the reader-script:
installation may be, either 'basic', or via setup.py

*Next questions*
- the output of this script on Putty's CLI is recognized as a JSON-file
- reading a program from another programmer is not always easy.
Therefore the quick requests to the programmer (*Olivier?*) for 
support of my views:
1. What is the line of the script with the print-command and the 
JSON-file-name for this output?
2. Output by the JSON-file now dynamically limited to data from valid 
sensors.
=> if a sensor goes down (such as 'battery empty'), then a different 
JSON-file.
For subsequent processing somewhat easier/simpler if 'empty' fields are 
still there.
How/where to change the script to get that?

Op vrijdag 14 februari 2020 08:50:02 UTC+1 schreef Ton vanN:
>
> Risto,
>
> This script sure helps:
> after stripping out the comments, it ran without errors at first try!
> Seems quite a good starting point for my planned further effort in 
> direction of Domoticz and for graphing with RRDTool.
> Like you did, tested while weewx still around & active: therefore next to 
> test that it runs without weewx
> If not, to be checked whether it runs with weewx installed by the 'simple' 
> method (spreading the files from /root).
>
> Last week ;-) quickly learned a lot about weewx by try& error:
> Olivier_G thanks for the continuous support for this NOOB!
>
> My conclusion for first use of weewx:
> the first installation of weewx makes the difference, but :-(  that is 
> unknown for a first time user of weewx.
> Perhaps a suggestion that in a description for an addition/modification 
> for aspects such as the driver/interface for HP300x or WS3000 in one of the 
> first comment lines it is clearly stated that an installation through 
> setup.py is assumed, putting files in /home/weewx (*or* by the 'simple' 
> method).
> After I changed to use of setup.py, the scripts from both Matthewwall and 
> Olivier_G started running.
>
> Op vrijdag 14 februari 2020 07:02:38 UTC+1 schreef Risto H. Kurppa:
>>
>> Not sure if it helps anyone, but with Oliver's help about a year or so 
>> ago, I stripped the ws3000 weewx driver code to work as standalone, without 
>> needing weewx. That way I was able to just read the values to MQTT for 
>> further use, without weewx dependency. The code is not cleaned in any way 
>> and it's actually possible that it still uses some weewx things here or 
>> there- I still have also weewx installed and haven't tested it without 
>> weewx.
>>
>> https://pastebin.com/37WkUz7N
>>
>> Feel free to use & edit & expand. Or Olivier, maybe you want to add an 
>> standalone script to your github?
>>
>> Risto
>>
>>
>>
>> On Fri, Feb 14, 2020 at 12:26 AM Ton vanN  wrote:
>>
>>> Perhaps not 100% done according to Olivier's latest message, but got the 
>>> same result in weewx.conf
>>> Now (in the next days) an update for display & database .
>>>
>>> Op donderdag 13 februari 2020 22:26:08 UTC+1 schreef Olivier Guyotot:
>>>>
>>>> Here, I put the code on github, with some basic installation 
>>>> instructions.
>>>> https://github.com/hublol/WS-3000_WeeWx
>>>>
>>>> I haven't tested those instructions recently, they might be incomplete 
>>>> right now, but it's a start and I'll work to improve them if needed.
>>>>
>>> -- 
>>> You received this message becaus

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Risto,

This script sure helps:
after stripping out the comments, it ran without errors at first try!
Seems quite a good starting point for my planned further effort in 
direction of Domoticz and for graphing with RRDTool.
Like you did, tested while weewx still around & active: therefore next to 
test that it runs without weewx
If not, to be checked whether it runs with weewx installed by the 'simple' 
method (spreading the files from /root).

Last week ;-) quickly learned a lot about weewx by try& error:
Olivier_G thanks for the continuous support for this NOOB!

My conclusion for first use of weewx:
the first installation of weewx makes the difference, but :-(  that is 
unknown for a first time user of weewx.
Perhaps a suggestion that in a description for an addition/modification for 
aspects such as the driver/interface for HP300x or WS3000 in one of the 
first comment lines it is clearly stated that an installation through 
setup.py is assumed, putting files in /home/weewx (*or* by the 'simple' 
method).
After I changed to use of setup.py, the scripts from both Matthewwall and 
Olivier_G started running.

Op vrijdag 14 februari 2020 07:02:38 UTC+1 schreef Risto H. Kurppa:
>
> Not sure if it helps anyone, but with Oliver's help about a year or so 
> ago, I stripped the ws3000 weewx driver code to work as standalone, without 
> needing weewx. That way I was able to just read the values to MQTT for 
> further use, without weewx dependency. The code is not cleaned in any way 
> and it's actually possible that it still uses some weewx things here or 
> there- I still have also weewx installed and haven't tested it without 
> weewx.
>
> https://pastebin.com/37WkUz7N
>
> Feel free to use & edit & expand. Or Olivier, maybe you want to add an 
> standalone script to your github?
>
> Risto
>
>
>
> On Fri, Feb 14, 2020 at 12:26 AM Ton vanN > 
> wrote:
>
>> Perhaps not 100% done according to Olivier's latest message, but got the 
>> same result in weewx.conf
>> Now (in the next days) an update for display & database .
>>
>> Op donderdag 13 februari 2020 22:26:08 UTC+1 schreef Olivier Guyotot:
>>>
>>> Here, I put the code on github, with some basic installation 
>>> instructions.
>>> https://github.com/hublol/WS-3000_WeeWx
>>>
>>> I haven't tested those instructions recently, they might be incomplete 
>>> right now, but it's a start and I'll work to improve them if needed.
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/qDe-El03C2k/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/1e03f915-8022-454a-813a-fc7afc99e064%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/1e03f915-8022-454a-813a-fc7afc99e064%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> -- 
> | risto h. kurppa
> | risto at kurppa dot fi
> | http://risto.kurppa.fi
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7df25f81-fd1e-40a6-8214-8349df7beee6%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Op vrijdag 14 februari 2020 07:02:38 UTC+1 schreef Risto H. Kurppa:
>
> Not sure if it helps anyone, but with Oliver's help about a year or so 
> ago, I stripped the ws3000 weewx driver code to work as standalone, without 
> needing weewx. That way I was able to just read the values to MQTT for 
> further use, without weewx dependency. The code is not cleaned in any way 
> and it's actually possible that it still uses some weewx things here or 
> there- I still have also weewx installed and haven't tested it without 
> weewx.
>
> https://pastebin.com/37WkUz7N
>
> Feel free to use & edit & expand. Or Olivier, maybe you want to add an 
> standalone script to your github?
>
> Risto
>
>
>
> On Fri, Feb 14, 2020 at 12:26 AM Ton vanN > 
> wrote:
>
>> Perhaps not 100% done according to Olivier's latest message, but got the 
>> same result in weewx.conf
>> Now (in the next days) an update for display & database .
>>
>> Op donderdag 13 februari 2020 22:26:08 UTC+1 schreef Olivier Guyotot:
>>>
>>> Here, I put the code on github, with some basic installation 
>>> instructions.
>>> https://github.com/hublol/WS-3000_WeeWx
>>>
>>> I haven't tested those instructions recently, they might be incomplete 
>>> right now, but it's a start and I'll work to improve them if needed.
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/qDe-El03C2k/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/1e03f915-8022-454a-813a-fc7afc99e064%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/1e03f915-8022-454a-813a-fc7afc99e064%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> -- 
> | risto h. kurppa
> | risto at kurppa dot fi
> | http://risto.kurppa.fi
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/deb44eba-ac01-4b3f-890e-8e2636577e2e%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Perhaps not 100% done according to Olivier's latest message, but got the 
same result in weewx.conf
Now (in the next days) an update for display & database .

Op donderdag 13 februari 2020 22:26:08 UTC+1 schreef Olivier Guyotot:
>
> Here, I put the code on github, with some basic installation instructions.
> https://github.com/hublol/WS-3000_WeeWx
>
> I haven't tested those instructions recently, they might be incomplete 
> right now, but it's a start and I'll work to improve them if needed.
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1e03f915-8022-454a-813a-fc7afc99e064%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Olivier has made the read-out of WS3000 an extension to 'another' 
weatherstation.
For just reading & processing the output of WS3000 a number of adaptation 
have to be made.

In my setup I have WeeWX operating with the Simulator which generates 
fake-weather.
On the other hand I have plenty of data from real weather-sensors.
That data is good enough to 'inject' into the Simulator, resulting in one 
merged data-set with all actual data.
Have looked around, but not seen in this Google-group, nor in WeeWX-wiki 
such a possibility.
Did I miss the info, or not yet developed?


Op donderdag 13 februari 2020 11:23:59 UTC+1 schreef Ton vanN:
>
> Forgot to hint that RistoK's HowTo-Instructions for fitting the 
> ws3000-driver on a Raspberry would have been very useful for my efforts 
> (probably significantly reducing my questions and experiments), but 
> unfortunately those instructions no longer accessible, because the hosting 
> server has gone ...
> Now smells a bit like 'reinventing the wheel', unless somebody can 
> reproduce those instructions.
>
> Op donderdag 13 februari 2020 11:05:46 UTC+1 schreef Ton vanN:
>>
>> @Olivier,
>> Changed the WeeWX-setup to the 'normal' configuration resulting after 
>> installation with the tar-file and setup.py.
>> At least the script ws3000.py now starts running, but not without errors: 
>> error report has been sent by Email.
>> Looking at the errorreports, *apparently* the version Python2.7 as part 
>> of Raspian_Buster is conflicting with functions in script ws3000.py
>>
>> Op woensdag 12 februari 2020 19:39:15 UTC+1 schreef Olivier Guyotot:
>>>
>>> If your installation was done using the Debian package manager, then you 
>>> need to deploy the ws3000.py file in /usr/share/weewx/user.
>>>
>>> And the command to run would presumably be:
>>> PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/ws3000.py
>>>
>>> Unfortunately I have no experience with this type of installation, and 
>>> no way to test it. I won't be of much help here.
>>>
>>> NOTE: I just noticed that in your configuration, you specified driver = 
>>>>> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
>>>>> Where did you see this info?
>>>>> Or otherwise formulated: where shal I put such line?
>>>>
>>>> I saw that in the StdConvert issue thread, where you posted part of 
>>> your weex.conf, didn't you?
>>>
>>> What you need is a section such as:
>>> [WS3000]
>>> # This section is for the Ambient Weather WS3000
>>>
>>> # The driver to use
>>> driver = user.ws3000
>>>
>>> # The station model, e.g., WS3000, WS3000-X3, WS3000-X5 (all the 
>>> same...)
>>> model = WS3000
>>>
>>> # [Optional] USB read/write timeout (helps on Raspberry Pi)
>>> # Default is 1000
>>> timeout =  1000
>>>
>>> The rest should be optional.
>>>
>>>
>>>
>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/04cf036b-f9db-4682-8492-24e015754df8%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Forgot to hint that RistoK's HowTo-Instructions for fitting the 
ws3000-driver on a Raspberry would have been very useful for my efforts 
(probably significantly reducing my questions and experiments), but 
unfortunately those instructions no longer accessible, because the hosting 
server has gone ...
Now smells a bit like 'reinventing the wheel', unless somebody can 
reproduce those instructions.

Op donderdag 13 februari 2020 11:05:46 UTC+1 schreef Ton vanN:
>
> @Olivier,
> Changed the WeeWX-setup to the 'normal' configuration resulting after 
> installation with the tar-file and setup.py.
> At least the script ws3000.py now starts running, but not without errors: 
> error report has been sent by Email.
> Looking at the errorreports, *apparently* the version Python2.7 as part 
> of Raspian_Buster is conflicting with functions in script ws3000.py
>
> Op woensdag 12 februari 2020 19:39:15 UTC+1 schreef Olivier Guyotot:
>>
>> If your installation was done using the Debian package manager, then you 
>> need to deploy the ws3000.py file in /usr/share/weewx/user.
>>
>> And the command to run would presumably be:
>> PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/ws3000.py
>>
>> Unfortunately I have no experience with this type of installation, and no 
>> way to test it. I won't be of much help here.
>>
>> NOTE: I just noticed that in your configuration, you specified driver = 
>>>> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
>>>> Where did you see this info?
>>>> Or otherwise formulated: where shal I put such line?
>>>
>>> I saw that in the StdConvert issue thread, where you posted part of your 
>> weex.conf, didn't you?
>>
>> What you need is a section such as:
>> [WS3000]
>> # This section is for the Ambient Weather WS3000
>>
>> # The driver to use
>> driver = user.ws3000
>>
>> # The station model, e.g., WS3000, WS3000-X3, WS3000-X5 (all the 
>> same...)
>> model = WS3000
>>
>> # [Optional] USB read/write timeout (helps on Raspberry Pi)
>> # Default is 1000
>> timeout =  1000
>>
>> The rest should be optional.
>>
>>
>>
>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7d68949c-e4c2-42c1-a56c-e61da89e711b%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

@Olivier,
Changed the WeeWX-setup to the 'normal' configuration resulting after 
installation with the tar-file and setup.py.
At least the script ws3000.py now starts running, but not without errors: 
error report has been sent by Email.
Looking at the errorreports, *apparently* the version Python2.7 as part of 
Raspian_Buster is conflicting with functions in script ws3000.py

Op woensdag 12 februari 2020 19:39:15 UTC+1 schreef Olivier Guyotot:
>
> If your installation was done using the Debian package manager, then you 
> need to deploy the ws3000.py file in /usr/share/weewx/user.
>
> And the command to run would presumably be:
> PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/ws3000.py
>
> Unfortunately I have no experience with this type of installation, and no 
> way to test it. I won't be of much help here.
>
> NOTE: I just noticed that in your configuration, you specified driver = 
>>> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
>>> Where did you see this info?
>>> Or otherwise formulated: where shal I put such line?
>>
>> I saw that in the StdConvert issue thread, where you posted part of your 
> weex.conf, didn't you?
>
> What you need is a section such as:
> [WS3000]
> # This section is for the Ambient Weather WS3000
>
> # The driver to use
> driver = user.ws3000
>
> # The station model, e.g., WS3000, WS3000-X3, WS3000-X5 (all the 
> same...)
> model = WS3000
>
> # [Optional] USB read/write timeout (helps on Raspberry Pi)
> # Default is 1000
> timeout =  1000
>
> The rest should be optional.
>
>
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d7c19a77-9960-49af-9290-3b261f342ad1%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Gary,

Completely agree.
After the experiments, this evening checked the location of weewx-files, 
and that is 100% in accordance with http://www.weewx.com/docs/debian.htm
as could be expected, because the installation was also in accordance with 
that document.
Also at my Raspberry weewx_root is /

Probably it means that for ws3000.py some adaptations are required for 
alignment with those different locations, to enable installation of 
ws3000.py
In hindsight taking care of differences dependent on installation procedure:
a) as described in User Guide
b) via setup.py

Anton

Anton

Op woensdag 12 februari 2020 00:00:04 UTC+1 schreef gjr80:
>
> Your issue (to do with file locations) is due to the way in which WeeWX 
> was installed. Installation via setup.py  results in WeeWX files being 
> located in /home/weewx by default. Installation via a package results in 
> the WeeWX files being spread over a number of different locations. Refer to 
> Where 
> to find things <http://weewx.com/docs/usersguide.htm#Where_to_find_things> 
> in the User's Guide.
>
> Gary
>
> On Wednesday, 12 February 2020 08:36:05 UTC+10, Ton vanN wrote:
>>
>> Olivier,
>>
>> Perhaps the underlaying Linux_version makes a difference.
>> In my configuration it is Raspian_Buster_Lite.
>>
>> Anton
>>
>> Op dinsdag 11 februari 2020 22:29:08 UTC+1 schreef Ton vanN:
>>>
>>> Olivier,
>>>
>>> Puzzled, because apparently weewx has been installed in my configuration 
>>> in a different way than you expect.
>>> See the inserted text.
>>>
>>> ;-( Some more thinking to be done ...
>>> Waiting for your next suggestions.
>>>
>>> Anton
>>>
>>> Op dinsdag 11 februari 2020 20:17:29 UTC+1 schreef Olivier Guyotot:
>>>>
>>>> Alright, so the good news is that the vendor_id and product_id are 
>>>> still the same.
>>>>
>>>> NOTE: I just noticed that in your configuration, you specified driver = 
>>>> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
>>>>
>>> Where did you see this info? 
>>> Or otherwise formulated: where shal I put such line?
>>>
>>>
>>>> Assuming that you installed the driver correctly in the bin/user 
>>>> directory, 
>>>>
>>> In my configuration no folder /bin/user; therefore created and put 
>>> ws3000.py in that folder with x-attribute set, to enable execution
>>> Most weewx-files found in folder /etc/weewx
>>>
>>> to check if the current code is working with your station you could try 
>>>> the following:
>>>> 1. first, stop weewx.
>>>> 2. from the weewx folder, run the command:
>>>> PYTHONPATH=bin python bin/user/ws3000.py
>>>>
>>>> To get this running from Putty's CLI, I had to change into 
>>> PYTHONPATH=bin python /bin/user/ws3000.py
>>>
>>> Result is that the execution stops at the first comment-line.
>>> At least positive is that ws3000.py has been found and is executed.
>>> Have taken out all comment lines from ws3000.py between """ and """
>>> Then running
>>> PYTHONPATH=bin python /bin/user/ws3000.py
>>> => result is an error report telling 
>>>   File "/bin/user/ws3000.py", line 17, in 
>>> import weewx.drivers
>>> ImportError: No module named weewx.drivers
>>>
>>> Then stopped, to write this response .
>>>
>>> NOTE: you may have to replace the 'logdbg' statements by 'print', lines 
>>>> 624 and 626, if you don't see the data (check in the logs first).
>>>>
>>>> Something else that you could try is to enable debug in the weewx 
>>>> configuration file (debug = 1), start weewx, and send me the log.
>>>>
>>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5fa2135e-cdd1-4fb3-b5ae-912f720cbf60%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Have checked the other Raspberries within my reach whether they have a 
folder /bin/user/
Result:
Raspian_Stretch => no folder /bin/user/
Raspian_Buster_Desktop => no folder /bin/user/

Op dinsdag 11 februari 2020 23:36:05 UTC+1 schreef Ton vanN:
>
> Olivier,
>
> Perhaps the underlaying Linux_version makes a difference.
> In my configuration it is Raspian_Buster_Lite.
>
> Anton
>
> Op dinsdag 11 februari 2020 22:29:08 UTC+1 schreef Ton vanN:
>>
>> Olivier,
>>
>> Puzzled, because apparently weewx has been installed in my configuration 
>> in a different way than you expect.
>> See the inserted text.
>>
>> ;-( Some more thinking to be done ...
>> Waiting for your next suggestions.
>>
>> Anton
>>
>> Op dinsdag 11 februari 2020 20:17:29 UTC+1 schreef Olivier Guyotot:
>>>
>>> Alright, so the good news is that the vendor_id and product_id are still 
>>> the same.
>>>
>>> NOTE: I just noticed that in your configuration, you specified driver = 
>>> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
>>>
>> Where did you see this info? 
>> Or otherwise formulated: where shal I put such line?
>>
>>
>>> Assuming that you installed the driver correctly in the bin/user 
>>> directory, 
>>>
>> In my configuration no folder /bin/user; therefore created and put 
>> ws3000.py in that folder with x-attribute set, to enable execution
>> Most weewx-files found in folder /etc/weewx
>>
>> to check if the current code is working with your station you could try 
>>> the following:
>>> 1. first, stop weewx.
>>> 2. from the weewx folder, run the command:
>>> PYTHONPATH=bin python bin/user/ws3000.py
>>>
>>> To get this running from Putty's CLI, I had to change into 
>> PYTHONPATH=bin python /bin/user/ws3000.py
>>
>> Result is that the execution stops at the first comment-line.
>> At least positive is that ws3000.py has been found and is executed.
>> Have taken out all comment lines from ws3000.py between """ and """
>> Then running
>> PYTHONPATH=bin python /bin/user/ws3000.py
>> => result is an error report telling 
>>   File "/bin/user/ws3000.py", line 17, in 
>> import weewx.drivers
>> ImportError: No module named weewx.drivers
>>
>> Then stopped, to write this response .
>>
>> NOTE: you may have to replace the 'logdbg' statements by 'print', lines 
>>> 624 and 626, if you don't see the data (check in the logs first).
>>>
>>> Something else that you could try is to enable debug in the weewx 
>>> configuration file (debug = 1), start weewx, and send me the log.
>>>
>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a9f2b1a6-cd54-495a-9404-f3299ec882c1%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Olivier,

Perhaps the underlaying Linux_version makes a difference.
In my configuration it is Raspian_Buster_Lite.

Anton

Op dinsdag 11 februari 2020 22:29:08 UTC+1 schreef Ton vanN:
>
> Olivier,
>
> Puzzled, because apparently weewx has been installed in my configuration 
> in a different way than you expect.
> See the inserted text.
>
> ;-( Some more thinking to be done ...
> Waiting for your next suggestions.
>
> Anton
>
> Op dinsdag 11 februari 2020 20:17:29 UTC+1 schreef Olivier Guyotot:
>>
>> Alright, so the good news is that the vendor_id and product_id are still 
>> the same.
>>
>> NOTE: I just noticed that in your configuration, you specified driver = 
>> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
>>
> Where did you see this info? 
> Or otherwise formulated: where shal I put such line?
>
>
>> Assuming that you installed the driver correctly in the bin/user 
>> directory, 
>>
> In my configuration no folder /bin/user; therefore created and put 
> ws3000.py in that folder with x-attribute set, to enable execution
> Most weewx-files found in folder /etc/weewx
>
> to check if the current code is working with your station you could try 
>> the following:
>> 1. first, stop weewx.
>> 2. from the weewx folder, run the command:
>> PYTHONPATH=bin python bin/user/ws3000.py
>>
>> To get this running from Putty's CLI, I had to change into 
> PYTHONPATH=bin python /bin/user/ws3000.py
>
> Result is that the execution stops at the first comment-line.
> At least positive is that ws3000.py has been found and is executed.
> Have taken out all comment lines from ws3000.py between """ and """
> Then running
> PYTHONPATH=bin python /bin/user/ws3000.py
> => result is an error report telling 
>   File "/bin/user/ws3000.py", line 17, in 
> import weewx.drivers
> ImportError: No module named weewx.drivers
>
> Then stopped, to write this response .
>
> NOTE: you may have to replace the 'logdbg' statements by 'print', lines 
>> 624 and 626, if you don't see the data (check in the logs first).
>>
>> Something else that you could try is to enable debug in the weewx 
>> configuration file (debug = 1), start weewx, and send me the log.
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a18dff77-f766-4dfd-b2ca-f9f2969569c9%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Olivier,

Puzzled, because apparently weewx has been installed in my configuration in 
a different way than you expect.
See the inserted text.

;-( Some more thinking to be done ...
Waiting for your next suggestions.

Anton

Op dinsdag 11 februari 2020 20:17:29 UTC+1 schreef Olivier Guyotot:
>
> Alright, so the good news is that the vendor_id and product_id are still 
> the same.
>
> NOTE: I just noticed that in your configuration, you specified driver = 
> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
>
Where did you see this info? 
Or otherwise formulated: where shal I put such line?


> Assuming that you installed the driver correctly in the bin/user 
> directory, 
>
In my configuration no folder /bin/user; therefore created and put 
ws3000.py in that folder with x-attribute set, to enable execution
Most weewx-files found in folder /etc/weewx

to check if the current code is working with your station you could try the 
> following:
> 1. first, stop weewx.
> 2. from the weewx folder, run the command:
> PYTHONPATH=bin python bin/user/ws3000.py
>
> To get this running from Putty's CLI, I had to change into 
PYTHONPATH=bin python /bin/user/ws3000.py

Result is that the execution stops at the first comment-line.
At least positive is that ws3000.py has been found and is executed.
Have taken out all comment lines from ws3000.py between """ and """
Then running
PYTHONPATH=bin python /bin/user/ws3000.py
=> result is an error report telling 
  File "/bin/user/ws3000.py", line 17, in 
import weewx.drivers
ImportError: No module named weewx.drivers

Then stopped, to write this response .

NOTE: you may have to replace the 'logdbg' statements by 'print', lines 624 
> and 626, if you don't see the data (check in the logs first).
>
> Something else that you could try is to enable debug in the weewx 
> configuration file (debug = 1), start weewx, and send me the log.
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1adfc593-12ed-4d83-a3c0-c23c27421e89%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

On command *lsusb* the following response

Bus 001 Device 002: ID 0483:5750 STMicroelectronics
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub






Op maandag 10 februari 2020 19:30:49 UTC+1 schreef Olivier Guyotot:
>
> I haven't touched this in a while (it's just running on its own), my 
> memory is a bit fuzzy... It will take time for me to properly remember 
> everything.
>
> That being said, there are 2 major things to check:
> 1. that your station is indeed working like a WS3000.
> 2. what is the correct configuration to use.
>
> Let's start with 2.
>
> In your case, the first thing to check is if you can use the default or if 
> you need to update the vendor_id and product_id.
>
> Just run 
> lsusb
> on your raspberry and please post the output here.
>
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ad0739eb-2086-4f98-a83c-521a1b67859a%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

This thread makes interesting reading.

Have a Misol console type HP3001 (which probably is a next version/clone of 
HP3000), and assume therefore that the discussed HP3000/WS3000-driver will 
be applicable.
5 Sensors attached.
At processor-side have a configuration with Raspbian Buster on 
Raspberry_Zero_W
Installed ss described by Jack Stromberg at 
https://jackstromberg.com/2018/06/setting-up-weewx-with-a-raspberry-pi/
Lacking a better choice set WeeWX for 'Simulator'
Seems to work.

Next step is installation of the WS3000-driver, reconfig with that driver 
and then restart incl. de USB-interface to the Console of WS3000/HP300x
Have read the attachment to previous message, but NOOB needing simple 
instructions.

*Any hints for the next steps?*

Op dinsdag 30 oktober 2018 17:49:35 UTC+1 schreef olivier...@gmail.com:
>
> Here is an updated version of the driver, including:
> - the fix for sub-zero temperatures
> - improved error handling/retry (something that wasn't working properly 
> before)
> - the usb timeout is now a configuration setting
> - additional comments
>
> It probably won't fix the root cause of the 'crash' issue, but at least it 
> should now properly retry so the problem might be more transparent. And the 
> error reporting will be more useful to figure out what's wrong should an 
> exception occur.
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a6439b41-4926-4fc9-915b-bb1319348ac1%40googlegroups.com.

[weewx-user] Re: StdConvert issue?

[Ton vanN]

Olivier,

Nice that it works with a Simulator, but how to make the next & final steps 
towards the real interface of the HP300x-console?

Have been trying with your proposed ideas in the WS3000-thread, but no luck.
Have stron feeling that in file weewx.conf the 'station'-section is the 
place to tune.
For comment my present layout (which does not work):

[HP3000]
# This section is for HP-3000 temperature/humidity sensors

# The model name such as Ambient WS-3000-X5
model = WS3000

# The driver to use
driver = user.hp3000

[[sensor_map]]
inTemp = t_1
outTemp = t_2
extraTemp1 =
extraTemp2 =
extraTemp3 = t_3
extraTemp4 = t_4
extraTemp5 = t_5
extraTemp6 = t_6
extraTemp7 = t_7
extraTemp8 = t_8
inHumidity = h_1
outHumidity = h_2
extraHumid1 =
extraHumid2 =
extraHumid3 = h_3
extraHumid4 = h_4
extraHumid5 = h_5
extraHumid6 = h_6
extraHumid7 = h_7
extraHumid8 = h_8

Is this a suitable approach, or a complete mistake?
Why? And what would be the correct solution?
Alternatively, what is a working practical setup to get this interface 
operational?

Most curious, Anton


Op donderdag 18 januari 2018 23:36:01 UTC+1 schreef olivier...@gmail.com:
>
> Hello,
>
> Just a bit of background: I currently have a VP2 and I recently bought a 
> WS3000 with 8 sensors to monitor the inside temperature in various places. 
> What I would like to do is to store all the data in the same database. My 
> goal is to enhance each VP2 record with the temperature coming from the 
> WS3000.
>
> I found absolutely everything I needed to do this in the documentation, so 
> congrats, you did a really great job documenting weewx and the 
> possibilities of this tool are just amazing. I love it!
>
> Anyway, here is what I did:
> - rewrote a brand new driver for the WS3000, which works with the standard 
> weewx code (no need to use the USB branch).
> - created a small service that gets the current sensor values from the 
> WS3000 and adds them to each new record (and loop packet as well).
> - modified the database schema to include extraTemp1 to 8 and extraHumid1 
> to 8, to store the data from the WS3000.
>
> This all seems to work quite well (so far tested with the Simulator only), 
> except for a weird problem: all the temperature are properly converted to 
> the appropriate metrics, except for extraTemp8.
> Is there some kind of limit to the number of values that get converted 
> with StdConvert?
>
> NOTE: WS3000 reports temperature in °C. I modified the Simulator to do the 
> same, but I store the values in the database using °F.
>
> Any clue on what's wrong?
>
> Here is a typical loop packet:
> LOOP:   2018-01-18 23:32:07 CET (1516314727) altimeter: None, appTemp: 
> 106.743627453, barometer: None, cloudbase: 1601.11136389, dateTime: 
> 1516314727, dewpoint: 83.6206936222, extraHumid1: 47, extraHumid2: 46, 
> extraHumid3: 48, extraHumid4: 46, extraHumid5: 45, extraHumid6: 44, 
> extraHumid7: 47, extraHumid8: 46, extraTemp1: 74.12, extraTemp2: 73.94, 
> extraTemp3: 74.12, extraTemp4: 74.12, extraTemp5: 74.12, extraTemp6: 74.3, 
> extraTemp7: 74.3, extraTemp8: 23.6, heatindex: 115.825270834, humidex: 
> 120.858219625, inDewpoint: None, inHumidity: 29.9996112567, inTemp: None, 
> maxSolarRad: None, outHumidity: 79.9997084411, outTemp: 90.6655836233, 
> pressure: None, radiation: 0, rain: 0.0, usUnits: 1, UV: 0, windchill: 
> 90.6655836233, windDir: 359.998250647, windGust: 0.000130440063404, 
> windGustDir: 359.998250647, windSpeed: 0.000108700052838
>
> => as you can see, extraTemp8 is still expressed in °C, while all the 
> others are in °F.
>
> Thanks!
>
> PS: I attached all the files I am currently using:
> - the WS3000 driver
> - the data service
> - my weewx.conf
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a370bca4-c704-47ee-a9dc-b31c727878c2%40googlegroups.com.

Re: [weewx-user] StdConvert issue?

[Ton vanN]

Op vrijdag 19 januari 2018 14:43:07 UTC+1 schreef olivier...@gmail.com:
>
> OK, thanks, it's all working now.
>
> I just need to do some clean up and figure out how to share all of this...
>
> On Thursday, 18 January 2018 23:46:23 UTC+1, Tom Keffer wrote:
>>
>> There is indeed such a limit. The observation types extraTemp1 through 
>> extraTemp7 are defined, but anything beyond that, are not. It's very 
>> easy to add more. Put the following in user/extensions.py:
>>
>> import weewx.units
>> weewx.units.obs_group_dict['extraTemp8'] = 'group_temperature'
>>
>>
>> That should be all you need.
>>
>> -tk
>>
>>
>> On Thu, Jan 18, 2018 at 3:36 PM,  wrote:
>>
>>> Hello,
>>>
>>> Just a bit of background: I currently have a VP2 and I recently bought a 
>>> WS3000 with 8 sensors to monitor the inside temperature in various places. 
>>> What I would like to do is to store all the data in the same database. My 
>>> goal is to enhance each VP2 record with the temperature coming from the 
>>> WS3000.
>>>
>>> I found absolutely everything I needed to do this in the documentation, 
>>> so congrats, you did a really great job documenting weewx and the 
>>> possibilities of this tool are just amazing. I love it!
>>>
>>> Anyway, here is what I did:
>>> - rewrote a brand new driver for the WS3000, which works with the 
>>> standard weewx code (no need to use the USB branch).
>>> - created a small service that gets the current sensor values from the 
>>> WS3000 and adds them to each new record (and loop packet as well).
>>> - modified the database schema to include extraTemp1 to 8 and 
>>> extraHumid1 to 8, to store the data from the WS3000.
>>>
>>> This all seems to work quite well (so far tested with the Simulator 
>>> only), except for a weird problem: all the temperature are properly 
>>> converted to the appropriate metrics, except for extraTemp8.
>>> Is there some kind of limit to the number of values that get converted 
>>> with StdConvert?
>>>
>>> NOTE: WS3000 reports temperature in °C. I modified the Simulator to do 
>>> the same, but I store the values in the database using °F.
>>>
>>> Any clue on what's wrong?
>>>
>>> Here is a typical loop packet:
>>> LOOP:   2018-01-18 23:32:07 CET (1516314727) altimeter: None, appTemp: 
>>> 106.743627453, barometer: None, cloudbase: 1601.11136389, dateTime: 
>>> 1516314727, dewpoint: 83.6206936222, extraHumid1: 47, extraHumid2: 46, 
>>> extraHumid3: 48, extraHumid4: 46, extraHumid5: 45, extraHumid6: 44, 
>>> extraHumid7: 47, extraHumid8: 46, extraTemp1: 74.12, extraTemp2: 73.94, 
>>> extraTemp3: 74.12, extraTemp4: 74.12, extraTemp5: 74.12, extraTemp6: 74.3, 
>>> extraTemp7: 74.3, extraTemp8: 23.6, heatindex: 115.825270834, humidex: 
>>> 120.858219625, inDewpoint: None, inHumidity: 29.9996112567, inTemp: None, 
>>> maxSolarRad: None, outHumidity: 79.9997084411, outTemp: 90.6655836233, 
>>> pressure: None, radiation: 0, rain: 0.0, usUnits: 1, UV: 0, windchill: 
>>> 90.6655836233, windDir: 359.998250647, windGust: 0.000130440063404, 
>>> windGustDir: 359.998250647, windSpeed: 0.000108700052838
>>>
>>> => as you can see, extraTemp8 is still expressed in °C, while all the 
>>> others are in °F.
>>>
>>> Thanks!
>>>
>>> PS: I attached all the files I am currently using:
>>> - the WS3000 driver
>>> - the data service
>>> - my weewx.conf
>>>
>>> -- 
>>> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5935ef58-0c7b-4fb5-9976-811d6ab29760%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

Sorry, small typing-mistake: my console is Misol HP3001

Op zondag 9 februari 2020 14:02:30 UTC+1 schreef Ton vanN:
>
> This thread makes interesting reading.
>
> Have a Misol console type HP3010 (which probably is a next version/clone 
> of HP3000), and assume therefore that the discussed HP3000-driver will be 
> applicable.
> 5 Sensors attached.
> At processor-side have a configuration with Raspbian Buster on 
> Raspberry_Zero_W
> Lacking a better choice set WeeWX for 'Simulator' [or should that better 
> be FineOffset WS3000?]
> The 5 Sensors not yet included in weewx.conf
>
> For my configuration the manuals on github etc. needed some tweaking, 
> because during installation  the files arrived at other places.
> Now got the pieces operational, but the overall result is negative: 
> no read-out visible from the console, and the web-interface is fixed/fake.
>
> *Any hints for next steps?*
>
> Op dinsdag 30 oktober 2018 17:49:35 UTC+1 schreef olivier...@gmail.com:
>>
>> Here is an updated version of the driver, including:
>> - the fix for sub-zero temperatures
>> - improved error handling/retry (something that wasn't working properly 
>> before)
>> - the usb timeout is now a configuration setting
>> - additional comments
>>
>> It probably won't fix the root cause of the 'crash' issue, but at least 
>> it should now properly retry so the problem might be more transparent. And 
>> the error reporting will be more useful to figure out what's wrong should 
>> an exception occur.
>>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e948c3b8-761a-4bc8-8d8d-136d22184a2d%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

This thread makes interesting reading.

Have a Misol console type HP3010 (which probably is a next version/clone of 
HP3000), and assume therefore that the discussed HP3000-driver will be 
applicable.
5 Sensors attached.
At processor-side have a configuration with Raspbian Buster on 
Raspberry_Zero_W
Lacking a better choice set WeeWX for 'Simulator' [or should that better be 
FineOffset WS3000?]
The 5 Sensors not yet included in weewx.conf

For my configuration the manuals on github etc. needed some tweaking, 
because during installation  the files arrived at other places.
Now got the pieces operational, but the overall result is negative: 
no read-out visible from the console, and the web-interface is fixed/fake.

*Any hints for next steps?*

Op dinsdag 30 oktober 2018 17:49:35 UTC+1 schreef olivier...@gmail.com:
>
> Here is an updated version of the driver, including:
> - the fix for sub-zero temperatures
> - improved error handling/retry (something that wasn't working properly 
> before)
> - the usb timeout is now a configuration setting
> - additional comments
>
> It probably won't fix the root cause of the 'crash' issue, but at least it 
> should now properly retry so the problem might be more transparent. And the 
> error reporting will be more useful to figure out what's wrong should an 
> exception occur.
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8dc00070-ebda-42d9-9110-b56adda2474c%40googlegroups.com.

[weewx-user] Re: HP300x and Raspberry

[Ton vanN]

Borrowing some bits and pieces from internet [such as 
https://jackstromberg.com/2018/06/setting-up-weewx-with-a-raspberry-pi/ and 
https://github.com/matthewwall/weewx-hp3000/issues/1 ] I got an operational 
configuration on a Raspberry, consisting of Raspian Buster + WeeWX3.9.2 + 
HP3000-driver + web-interface.
So far, so good, but it seems that the pieces of the chain are still not 
joint:
- no error reports
- no read-out visiblefrom my console HP3010
- lacking better choice I selected 'simulator' as weatherstation => the 
web-interface is showing 'fake-info'
- set FTP to point at an external server, but no uploaded report visible at 
the destination

*Any hints to get the elements of the chain connected?*

Op woensdag 29 januari 2020 11:35:18 UTC+1 schreef Ton vanN:
>
> Some further search reveals that unde the name of Ambient Weather WS-3000 
> station much more applicable info can be found.
>
> Op zondag 26 januari 2020 13:13:38 UTC+1 schreef Ton vanN:
>>
>> The website for WeeWX mentions/shows under section compatible Hardware 
>> the HP3000 package (= Console with max. 8 T from 
>> FineOffset/Ambient).
>>
>> At this moment the (probably) very similar package HP3001 from MiSol 
>> measures 5* T at my house.
>> Thinking about an online read-out etc. of it's USB-interface by a 
>> Raspberry.
>> *Purpose*: registration in SQLite3 and some graphic output as tables 
>> and/or graphs.
>>
>> Not able to find any examples, but (considering the description at 
>> WeeWX's website) 'Re-inventing the wheel' to get started seems unnecessary 
>> effort:
>> *has somebody an operational setup of HP300x & Raspberry, and willing to 
>> share the experience?*
>>
>>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/52803e60-5559-40b5-8729-1614ce5d4735%40googlegroups.com.

[weewx-user] Re: HP300x and Raspberry

[Ton vanN]

Some further search reveals that unde the name of Ambient Weather WS-3000 
station much more applicable info can be found.

Op zondag 26 januari 2020 13:13:38 UTC+1 schreef Ton vanN:
>
> The website for WeeWX mentions/shows under section compatible Hardware the 
> HP3000 package (= Console with max. 8 T from FineOffset/Ambient).
>
> At this moment the (probably) very similar package HP3001 from MiSol 
> measures 5* T at my house.
> Thinking about an online read-out etc. of it's USB-interface by a 
> Raspberry.
> *Purpose*: registration in SQLite3 and some graphic output as tables 
> and/or graphs.
>
> Not able to find any examples, but (considering the description at WeeWX's 
> website) 'Re-inventing the wheel' to get started seems unnecessary effort:
> *has somebody an operational setup of HP300x & Raspberry, and willing to 
> share the experience?*
>
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3ada8e14-4c2b-4461-9c79-a4b036ede38d%40googlegroups.com.

[weewx-user] HP300x and Raspberry

[Ton vanN]

The website for WeeWX mentions/shows under section compatible Hardware the 
HP3000 package (= Console with max. 8 T from FineOffset/Ambient).

At this moment the (probably) very similar package HP3001 from MiSol 
measures 5* T at my house.
Thinking about an online read-out etc. of it's USB-interface by a Raspberry.
*Purpose*: registration in SQLite3 and some graphic output as tables and/or 
graphs.

Not able to find any examples, but (considering the description at WeeWX's 
website) 'Re-inventing the wheel' to get started seems unnecessary effort:
*has somebody an operational setup of HP300x & Raspberry, and willing to 
share the experience?*

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f4ee6d16-ba07-4873-ba6b-86fb5c778a14%40googlegroups.com.

[weewx-user] Re: TFA Nexus and UV-Index?

[Ton vanN]

Hi Michael,

TFA_Nexus definitely has no UV-sensor in the catalogue of interfacing 
sensors.
It is a bit odd, but the windsensor of TFA_Nexus provides a related 
temperature reading.

As indicated in the other response, you have to find the data related to 
light and to UV outside the TFA_Nexus.
Examples for light-values: programs WsWin and WeatherDisplay have 2 
functions to get virtual light-values.
1) Modify a T by replacing the NTC-resistor for a LDR or for 
photodiode 
=> resistance is a function of light-input
The software translates into a light-value. Accuracy is [euphemistally] 
very limited.
2) Solar-Jar is a Temperature-sensor in a glass jar. The sun heats the air 
in the jar (or not).
The difference between the temperature inside the jar and another 
thermometer outside the jar is a measure for the lightlevel.
;-) Do not talk about accuracy ..

The program WsWin has a wsmerge-function by which you can import UV-data 
into the set of sensors elsewhere (= outside TFA_Nexus).

Op maandag 25 februari 2019 18:06:40 UTC+1 schreef Michael:
>
> Hi,
>
> I use the weather station TFA Nexus (35.1075). I am now interested in the 
> value UV index. From TFA there is the solar wind sensor (30.3168). 
> Unfortunately I find unclear information whether the wind sensor also 
> transmits the UV index. 
> If someone uses this wind sensor here and can tell me whether the UV index 
> is transmitted. If not, is there another alternative for the TFA Nexus in 
> connection with a Raspi?
>
> Many thanks in advance
> Michael
>

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d73b4883-f605-4f94-9e43-a40aba3d2855%40googlegroups.com.