Re: [weewx-user] Re: first user - a lot of issues

[Alex Vanuxem]

hey,

It was under wsl.
but now i installed under windows 11, hyper-v and installed an ubuntu
latest version under a virtual machine, i have the full program;
now i'm struggling again;
again no syslog, it says its installed, but cant start it
i can invoke ./bin/weewxd , i see a lot of data coming in in my terminal,
but no reports to var/www/html/ weewx,
i guess it something to do with permissions? or am i just dumb
thank you for your time,







Op vr 4 nov. 2022 om 22:24 schreef Rainer Lang :

> When you want to use weewx under WSL (which works perfectly by the way -
> at least with the Interceptor and the Ecowitt Gateway driver),
> you need to make sure that the connectivity between the virtual machine in
> which WSL is running and the local network the WSL host computer is running
> in
> has been established.
> There are recipes for that - Google is your friend - they describe Windows
> Powershell commands to be applied for this to work.
>
> That's not a weewx specific issue - it applies to any application running
> in WSL (Windows Subsystem for Linux) and needing to contact/communicate
> with the local network of the host computer.
>
> On 04.11.2022 19:47, vince wrote:
>
> We really need more information on your setup.
>
> It 'seems' like you are trying to run a rather unusual configuration.
>
> I noticed this in your errors.txt file:
>
>- "Linux-5.10.102.1-microsoft-standard-WSL2-x86_64-with-glibc2.29"
>
>==> are you trying to run weewx under Windows WSL perhaps ?
>
> I also see the following:
>
>- Message: 'Socket error while opening port %d to ethernet host %s.'
>Arguments: (2, '192.168.0.248') --- Logging error --- Traceback (most
>recent call last): File "/usr/share/weewx/weewx/drivers/vantage.py", line
>338, in openPort self.socket.connect((self.host, self.port)) OSError:
>[Errno 113] No route to host
>
>  ==> this is a networking issue in your setup
>
> We can't try to duplicate the problem(s) without knowing more about your
> setup.
>
> --
> 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/19a056c8-8f87-4460-b31c-feb78448ccbbn%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/fef7077b-712b-cc8e-9aa2-02c9e91e260f%40gmail.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/CAHaYyo%2BUxKKd55E8VixmNnARUgsF-bEzqZvNQbjjD8UGxDNjLA%40mail.gmail.com.

Re: [weewx-user] Re: first user - a lot of issues

[Rainer Lang]

When you want to use weewx under WSL (which works perfectly by the way - 
at least with the Interceptor and the Ecowitt Gateway driver),
you need to make sure that the connectivity between the virtual machine 
in which WSL is running and the local network the WSL host computer is 
running in

has been established.
There are recipes for that - Google is your friend - they describe 
Windows Powershell commands to be applied for this to work.


That's not a weewx specific issue - it applies to any application 
running in WSL (Windows Subsystem for Linux) and needing to 
contact/communicate

with the local network of the host computer.

On 04.11.2022 19:47, vince wrote:

We really need more information on your setup.

It 'seems' like you are trying to run a rather unusual configuration.

I noticed this in your errors.txt file:

  * "Linux-5.10.102.1-microsoft-standard-WSL2-x86_64-with-glibc2.29"

           ==> are you trying to run weewx under Windows WSL perhaps ?

I also see the following:

  * Message: 'Socket error while opening port %d to ethernet host %s.'
Arguments: (2, '192.168.0.248') --- Logging error ---
Traceback (most recent call last): File
"/usr/share/weewx/weewx/drivers/vantage.py", line 338, in openPort
self.socket.connect((self.host, self.port)) OSError: [Errno 113]
No route to host

             ==> this is a networking issue in your setup

We can't try to duplicate the problem(s) without knowing more about 
your setup.


--
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/19a056c8-8f87-4460-b31c-feb78448ccbbn%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/fef7077b-712b-cc8e-9aa2-02c9e91e260f%40gmail.com.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

[vince]

You can also use the -n switch to go back in the file longer.

For example to go back 500 lines:
sudo tail -n 500 -f /var/log/syslog

On Friday, November 4, 2022 at 12:46:56 PM UTC-7 Tom Keffer wrote:

> You're starting up weewxd, then doing tail -f /var/log/syslog. By the time 
> you do the "tail", you've missed the critical information about how weewxd 
> is starting up.
>
> Please follow the directions in *Posting to weewx-user 
> *. That 
> way, we can see the startup sequence.
>
> On Fri, Nov 4, 2022 at 11:30 AM Günther Wrana  wrote:
>
>> I don't think anything has changed with the killall command.
>>
>> pi@wetterpi:/$ sudo killall weewxd
>> weewxd: Kein Prozess gefunden
>> pi@wetterpi:/$ sudo killall weewxd
>> weewxd: Kein Prozess gefunden
>> pi@wetterpi:/$ sudo /etc/init.d/weewx start
>> [ ok ] Starting weewx (via systemctl): weewx.service.
>> pi@wetterpi:/$ sudo tail -f /var/log/syslog
>> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weewx/imagegenerator.py", line 109, in 
>> gen_images
>> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
>>   self.image_dict[timespan][plotname])
>> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weewx/imagegenerator.py", line 249, in 
>> gen_plot
>> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
>>   **option_dict)
>> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weewx/xtypes.py", line 116, in get_series
>> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
>>   raise weewx.UnknownType(msg)
>> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
>>   weewx.UnknownType: 'wind' or 'vecdir'
>> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
>>   Generator terminated
>> Nov  4 19:20:25 wetterpi weewx[29729] INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx
>> Nov  4 19:20:31 wetterpi weewx[29729] ERROR weewx.restx: AWEKAS: Failed 
>> to publish record 2022-11-04 19:20:00 CET (1667586000): Failed upload after 
>> 3 tries
>> Nov  4 19:25:22 wetterpi weewx[29729] INFO weewx.manager: Added record 
>> 2022-11-04 19:25:00 CET (1667586300) to database 'weewx.sdb'
>> Nov  4 19:25:22 wetterpi weewx[29729] INFO weewx.manager: Added record 
>> 2022-11-04 19:25:00 CET (1667586300) to daily summary in 'weewx.sdb'
>> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator: 
>> Evaluation of template /etc/weewx/skins/Seasons/index.html.tmpl failed with 
>> exception ''
>> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:  
>> Ignoring template /etc/weewx/skins/Seasons/index.html.tmpl
>> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:  
>> Reason: 'ObservationBinder' object is not callable
>> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:  
>>  Traceback (most recent call last):
>> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:  
>>File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in generate
>> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:  
>>  unicode_string = compiled_template.respond()
>> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:  
>>File 
>> "cheetah__etc_weewx_skins_Seasons_index_html_tmpl_1667331923_6578603_46130.py",
>>  
>> line 271, in respond
>> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:  
>>  TypeError: 'ObservationBinder' object is not callable
>> Nov  4 19:25:26 wetterpi weewx[29729] INFO weewx.restx: Wunderground-PWS: 
>> Published record 2022-11-04 19:25:00 CET (1667586300)
>> Nov  4 19:25:27 wetterpi weewx[29729] INFO weewx.cheetahgenerator: 
>> Generated 7 files for report SeasonsReport in 3.05 seconds
>> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: Caught 
>> unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'
>> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
>>   'wind' or 'vecdir'
>> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
>>   Traceback (most recent call last):
>> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
>> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
>>   obj.start()
>> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weewx/reportengine.py", line 378, in start
>> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
>>   self.gen_ts = gen_ts
>> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

[Tom Keffer]

You're starting up weewxd, then doing tail -f /var/log/syslog. By the time
you do the "tail", you've missed the critical information about how weewxd
is starting up.

Please follow the directions in *Posting to weewx-user
*. That
way, we can see the startup sequence.

On Fri, Nov 4, 2022 at 11:30 AM Günther Wrana  wrote:

> I don't think anything has changed with the killall command.
>
> pi@wetterpi:/$ sudo killall weewxd
> weewxd: Kein Prozess gefunden
> pi@wetterpi:/$ sudo killall weewxd
> weewxd: Kein Prozess gefunden
> pi@wetterpi:/$ sudo /etc/init.d/weewx start
> [ ok ] Starting weewx (via systemctl): weewx.service.
> pi@wetterpi:/$ sudo tail -f /var/log/syslog
> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine:
> File "/usr/share/weewx/weewx/imagegenerator.py", line 109, in
> gen_images
> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine:
>   self.image_dict[timespan][plotname])
> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine:
> File "/usr/share/weewx/weewx/imagegenerator.py", line 249, in
> gen_plot
> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine:
>   **option_dict)
> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine:
> File "/usr/share/weewx/weewx/xtypes.py", line 116, in get_series
> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine:
>   raise weewx.UnknownType(msg)
> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine:
>   weewx.UnknownType: 'wind' or 'vecdir'
> Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine:
>   Generator terminated
> Nov  4 19:20:25 wetterpi weewx[29729] INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx
> Nov  4 19:20:31 wetterpi weewx[29729] ERROR weewx.restx: AWEKAS: Failed to
> publish record 2022-11-04 19:20:00 CET (1667586000): Failed upload after 3
> tries
> Nov  4 19:25:22 wetterpi weewx[29729] INFO weewx.manager: Added record
> 2022-11-04 19:25:00 CET (1667586300) to database 'weewx.sdb'
> Nov  4 19:25:22 wetterpi weewx[29729] INFO weewx.manager: Added record
> 2022-11-04 19:25:00 CET (1667586300) to daily summary in 'weewx.sdb'
> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:
> Evaluation of template /etc/weewx/skins/Seasons/index.html.tmpl failed with
> exception ''
> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator: 
> Ignoring template /etc/weewx/skins/Seasons/index.html.tmpl
> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator: 
> Reason: 'ObservationBinder' object is not callable
> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator: 
>  Traceback (most recent call last):
> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator: 
>  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in generate
> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator: 
>unicode_string = compiled_template.respond()
> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator: 
>  File
> "cheetah__etc_weewx_skins_Seasons_index_html_tmpl_1667331923_6578603_46130.py",
> line 271, in respond
> Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator: 
>  TypeError: 'ObservationBinder' object is not callable
> Nov  4 19:25:26 wetterpi weewx[29729] INFO weewx.restx: Wunderground-PWS:
> Published record 2022-11-04 19:25:00 CET (1667586300)
> Nov  4 19:25:27 wetterpi weewx[29729] INFO weewx.cheetahgenerator:
> Generated 7 files for report SeasonsReport in 3.05 seconds
> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: Caught
> unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'
> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine:
>   'wind' or 'vecdir'
> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine:
>   Traceback (most recent call last):
> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine:
> File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine:
>   obj.start()
> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine:
> File "/usr/share/weewx/weewx/reportengine.py", line 378, in start
> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine:
>   self.gen_ts = gen_ts
> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine:
> File "/usr/share/weewx/weewx/imagegenerator.py", line 42, in run
> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine:
>   self.gen_images(self.gen_ts)
> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine:
> File "/usr/share/weewx/weewx/imagegenerator.py", line 109, in
> gen_images
> Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine:
>   self.image_dict[timespan][plotname])
> Nov  4 

Re: [weewx-user] Re: first user - a lot of issues

[vince]

We really need more information on your setup.

It 'seems' like you are trying to run a rather unusual configuration.

I noticed this in your errors.txt file:

   - "Linux-5.10.102.1-microsoft-standard-WSL2-x86_64-with-glibc2.29"

   ==> are you trying to run weewx under Windows WSL perhaps ?

I also see the following:

   - Message: 'Socket error while opening port %d to ethernet host %s.' 
   Arguments: (2, '192.168.0.248') --- Logging error --- Traceback (most 
   recent call last): File "/usr/share/weewx/weewx/drivers/vantage.py", line 
   338, in openPort self.socket.connect((self.host, self.port)) OSError: 
   [Errno 113] No route to host
   
 ==> this is a networking issue in your setup

We can't try to duplicate the problem(s) without knowing more about your 
setup.

-- 
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/19a056c8-8f87-4460-b31c-feb78448ccbbn%40googlegroups.com.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

[Günther Wrana]

I don't think anything has changed with the killall command.

pi@wetterpi:/$ sudo killall weewxd
weewxd: Kein Prozess gefunden
pi@wetterpi:/$ sudo killall weewxd
weewxd: Kein Prozess gefunden
pi@wetterpi:/$ sudo /etc/init.d/weewx start
[ ok ] Starting weewx (via systemctl): weewx.service.
pi@wetterpi:/$ sudo tail -f /var/log/syslog
Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/imagegenerator.py", line 109, in 
gen_images
Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
  self.image_dict[timespan][plotname])
Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/imagegenerator.py", line 249, in 
gen_plot
Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
  **option_dict)
Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/xtypes.py", line 116, in get_series
Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
  raise weewx.UnknownType(msg)
Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
  weewx.UnknownType: 'wind' or 'vecdir'
Nov  4 19:20:25 wetterpi weewx[29729] ERROR weewx.reportengine: 
  Generator terminated
Nov  4 19:20:25 wetterpi weewx[29729] INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx
Nov  4 19:20:31 wetterpi weewx[29729] ERROR weewx.restx: AWEKAS: Failed to 
publish record 2022-11-04 19:20:00 CET (1667586000): Failed upload after 3 
tries
Nov  4 19:25:22 wetterpi weewx[29729] INFO weewx.manager: Added record 
2022-11-04 19:25:00 CET (1667586300) to database 'weewx.sdb'
Nov  4 19:25:22 wetterpi weewx[29729] INFO weewx.manager: Added record 
2022-11-04 19:25:00 CET (1667586300) to daily summary in 'weewx.sdb'
Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator: 
Evaluation of template /etc/weewx/skins/Seasons/index.html.tmpl failed with 
exception ''
Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/Seasons/index.html.tmpl
Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:  
Reason: 'ObservationBinder' object is not callable
Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:  
 Traceback (most recent call last):
Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in generate
Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:    
   unicode_string = compiled_template.respond()
Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:    
 File 
"cheetah__etc_weewx_skins_Seasons_index_html_tmpl_1667331923_6578603_46130.py", 
line 271, in respond
Nov  4 19:25:25 wetterpi weewx[29729] ERROR weewx.cheetahgenerator:  
 TypeError: 'ObservationBinder' object is not callable
Nov  4 19:25:26 wetterpi weewx[29729] INFO weewx.restx: Wunderground-PWS: 
Published record 2022-11-04 19:25:00 CET (1667586300)
Nov  4 19:25:27 wetterpi weewx[29729] INFO weewx.cheetahgenerator: 
Generated 7 files for report SeasonsReport in 3.05 seconds
Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'
Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
  'wind' or 'vecdir'
Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
  Traceback (most recent call last):
Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
  obj.start()
Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/reportengine.py", line 378, in start
Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
  self.gen_ts = gen_ts
Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/imagegenerator.py", line 42, in run
Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
  self.gen_images(self.gen_ts)
Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/imagegenerator.py", line 109, in 
gen_images
Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
  self.image_dict[timespan][plotname])
Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/imagegenerator.py", line 249, in 
gen_plot
Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
  **option_dict)
Nov  4 19:25:29 wetterpi weewx[29729] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/xtypes.py", 

Re: [weewx-user] Re: first user - a lot of issues

[Alex Vanuxem]

the first is an errorlog when i start weewx
the second is errorlog of syslog

thx

Op vr 4 nov. 2022 om 19:07 schreef Alex Vanuxem :

>
>
> Op vr 4 nov. 2022 om 19:07 schreef Alex Vanuxem :
>
>> hi thx
>>
>> i forgot to init.d the rsyslog.
>>
>> now i have syslog see attach. I can connect to my ftp through the linux
>> gui.
>>
>> but since today no data is coming in, ???
>> sorry i'm a newbie.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Op do 3 nov. 2022 om 23:24 schreef Tom Keffer :
>>
>>> (Vince, I think he went to the correct link.)
>>>
>>> Alex, what operating system are you using? These days, almost all
>>> operating systems put something in /var/log.
>>>
>>> If we can't figure it out, there is a way to get WeeWX to log to a
>>> standard file. Add this to the bottom of weewx.conf:
>>>
>>> [Logging]
>>> [[root]]
>>>   handlers = rotate,
>>>
>>> [[handlers]]
>>> # Log to a set of rotating files
>>> [[[rotate]]]
>>> level = DEBUG
>>> formatter = verbose
>>> class = logging.handlers.RotatingFileHandler
>>> filename = /var/tmp/weewx.log
>>> maxBytes = 1000
>>> backupCount = 4
>>>
>>> This will put the weewx-related log entries in /var/tmp/weewx.log. Post
>>> that.
>>>
>>> On Thu, Nov 3, 2022 at 2:19 PM Alex Vanuxem 
>>> wrote:
>>>
 i'm sorry . There's nothing there on both locations specified in the
 doc you posted.  Thanks though any other suggestions? Grtz alex



 Op do 3 nov. 2022 21:59 schreef vince :

> Look at the bottom of
> https://github.com/weewx/weewx/wiki/WeeWX-Frequently-Asked-Questions
>
> On Thursday, November 3, 2022 at 1:36:29 PM UTC-7 vanuxe...@gmail.com
> wrote:
>
>> thx, installed it, but I'm learning python and linux as we speak,
>> bare with me please.
>> where can I find the log? not in var/log... apologize for my
>> dumbness, thanks again
>>
>> Op donderdag 3 november 2022 om 20:26:50 UTC+1 schreef vince:
>>
>>> You need to install a syslog daemon .
>>>
>>> sudo apt-get install -y rsyslog
>>>
>>> On Thursday, November 3, 2022 at 12:13:07 PM UTC-7
>>> vanuxe...@gmail.com wrote:
>>>
 Hi Guys,

 I'm Alex from Belgium, a weather amateur, got a Vantage Pro 2,
 airlinks, and soil and leaf sensors.

 got a website at  Meteo Sint-Katelijne-Waver, Belgium
 (sint-katelijne-waver-meteo.be)
 

 so finally i'm getting some data in
 at var/www/html/weewx/index.html.

 using for the moment vantage pro 2 iplink, i have also wll, thats
 for later.

 but when i start weewx i get a lot of errors see attachment.

 next thing is to send it to my website, i'm missing something...

 thanks




 Op donderdag 3 november 2022 om 01:21:24 UTC+1 schreef Alex Vanuxem:

> hey Guys,
>
> I'm trying weewx for the first time, no experience in python, a
> little bit in php
>
> done the setup as required.
>
> running ubuntu as a virtual machine on windows, want to check it
> out before i buy a raspberry.
>
> problems: in the config file I see a lot of setups which I dont
> get when performing the the how to.
>
> sudo tail -f /var/log/syslog doesn't exist, I'm stuck with the
> nOrth pole default thing.
>
> and sudo ./bin/weewxd doesn't exist???
>
> although i configured the config manually and copied it.
>
> what files do you want to troubleshout?
>
> I've set up a cumulusMX, pwsWD and a meteotemplate website, so
> this should work too?
>
> Bare with me please,
>
> THX
>
> alex
>
 --
> 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/dc807670-b1e8-46c7-9cef-121c27c8a812n%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
 

Re: [weewx-user] Re: first user - a lot of issues

[Alex Vanuxem]

Op vr 4 nov. 2022 om 19:07 schreef Alex Vanuxem :

> hi thx
>
> i forgot to init.d the rsyslog.
>
> now i have syslog see attach. I can connect to my ftp through the linux
> gui.
>
> but since today no data is coming in, ???
> sorry i'm a newbie.
>
>
>
>
>
>
>
>
>
>
> Op do 3 nov. 2022 om 23:24 schreef Tom Keffer :
>
>> (Vince, I think he went to the correct link.)
>>
>> Alex, what operating system are you using? These days, almost all
>> operating systems put something in /var/log.
>>
>> If we can't figure it out, there is a way to get WeeWX to log to a
>> standard file. Add this to the bottom of weewx.conf:
>>
>> [Logging]
>> [[root]]
>>   handlers = rotate,
>>
>> [[handlers]]
>> # Log to a set of rotating files
>> [[[rotate]]]
>> level = DEBUG
>> formatter = verbose
>> class = logging.handlers.RotatingFileHandler
>> filename = /var/tmp/weewx.log
>> maxBytes = 1000
>> backupCount = 4
>>
>> This will put the weewx-related log entries in /var/tmp/weewx.log. Post
>> that.
>>
>> On Thu, Nov 3, 2022 at 2:19 PM Alex Vanuxem 
>> wrote:
>>
>>> i'm sorry . There's nothing there on both locations specified in the doc
>>> you posted.  Thanks though any other suggestions? Grtz alex
>>>
>>>
>>>
>>> Op do 3 nov. 2022 21:59 schreef vince :
>>>
 Look at the bottom of
 https://github.com/weewx/weewx/wiki/WeeWX-Frequently-Asked-Questions

 On Thursday, November 3, 2022 at 1:36:29 PM UTC-7 vanuxe...@gmail.com
 wrote:

> thx, installed it, but I'm learning python and linux as we speak, bare
> with me please.
> where can I find the log? not in var/log... apologize for my dumbness,
> thanks again
>
> Op donderdag 3 november 2022 om 20:26:50 UTC+1 schreef vince:
>
>> You need to install a syslog daemon .
>>
>> sudo apt-get install -y rsyslog
>>
>> On Thursday, November 3, 2022 at 12:13:07 PM UTC-7
>> vanuxe...@gmail.com wrote:
>>
>>> Hi Guys,
>>>
>>> I'm Alex from Belgium, a weather amateur, got a Vantage Pro 2,
>>> airlinks, and soil and leaf sensors.
>>>
>>> got a website at  Meteo Sint-Katelijne-Waver, Belgium
>>> (sint-katelijne-waver-meteo.be)
>>> 
>>>
>>> so finally i'm getting some data in at var/www/html/weewx/index.html.
>>>
>>> using for the moment vantage pro 2 iplink, i have also wll, thats
>>> for later.
>>>
>>> but when i start weewx i get a lot of errors see attachment.
>>>
>>> next thing is to send it to my website, i'm missing something...
>>>
>>> thanks
>>>
>>>
>>>
>>>
>>> Op donderdag 3 november 2022 om 01:21:24 UTC+1 schreef Alex Vanuxem:
>>>
 hey Guys,

 I'm trying weewx for the first time, no experience in python, a
 little bit in php

 done the setup as required.

 running ubuntu as a virtual machine on windows, want to check it
 out before i buy a raspberry.

 problems: in the config file I see a lot of setups which I dont get
 when performing the the how to.

 sudo tail -f /var/log/syslog doesn't exist, I'm stuck with the
 nOrth pole default thing.

 and sudo ./bin/weewxd doesn't exist???

 although i configured the config manually and copied it.

 what files do you want to troubleshout?

 I've set up a cumulusMX, pwsWD and a meteotemplate website, so this
 should work too?

 Bare with me please,

 THX

 alex

>>> --
 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/dc807670-b1e8-46c7-9cef-121c27c8a812n%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/CAHaYyoJ5V4qo-J5e9OWZkg0hT3XT8SMr_cfCz0DgiMoSdMfu4g%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" 

Re: [weewx-user] Re: first user - a lot of issues

[Alex Vanuxem]

hi thx

i forgot to init.d the rsyslog.

now i have syslog see attach. I can connect to my ftp through the linux gui.

but since today no data is coming in, ???
sorry i'm a newbie.










Op do 3 nov. 2022 om 23:24 schreef Tom Keffer :

> (Vince, I think he went to the correct link.)
>
> Alex, what operating system are you using? These days, almost all
> operating systems put something in /var/log.
>
> If we can't figure it out, there is a way to get WeeWX to log to a
> standard file. Add this to the bottom of weewx.conf:
>
> [Logging]
> [[root]]
>   handlers = rotate,
>
> [[handlers]]
> # Log to a set of rotating files
> [[[rotate]]]
> level = DEBUG
> formatter = verbose
> class = logging.handlers.RotatingFileHandler
> filename = /var/tmp/weewx.log
> maxBytes = 1000
> backupCount = 4
>
> This will put the weewx-related log entries in /var/tmp/weewx.log. Post
> that.
>
> On Thu, Nov 3, 2022 at 2:19 PM Alex Vanuxem 
> wrote:
>
>> i'm sorry . There's nothing there on both locations specified in the doc
>> you posted.  Thanks though any other suggestions? Grtz alex
>>
>>
>>
>> Op do 3 nov. 2022 21:59 schreef vince :
>>
>>> Look at the bottom of
>>> https://github.com/weewx/weewx/wiki/WeeWX-Frequently-Asked-Questions
>>>
>>> On Thursday, November 3, 2022 at 1:36:29 PM UTC-7 vanuxe...@gmail.com
>>> wrote:
>>>
 thx, installed it, but I'm learning python and linux as we speak, bare
 with me please.
 where can I find the log? not in var/log... apologize for my dumbness,
 thanks again

 Op donderdag 3 november 2022 om 20:26:50 UTC+1 schreef vince:

> You need to install a syslog daemon .
>
> sudo apt-get install -y rsyslog
>
> On Thursday, November 3, 2022 at 12:13:07 PM UTC-7 vanuxe...@gmail.com
> wrote:
>
>> Hi Guys,
>>
>> I'm Alex from Belgium, a weather amateur, got a Vantage Pro 2,
>> airlinks, and soil and leaf sensors.
>>
>> got a website at  Meteo Sint-Katelijne-Waver, Belgium
>> (sint-katelijne-waver-meteo.be)
>> 
>>
>> so finally i'm getting some data in at var/www/html/weewx/index.html.
>>
>> using for the moment vantage pro 2 iplink, i have also wll, thats for
>> later.
>>
>> but when i start weewx i get a lot of errors see attachment.
>>
>> next thing is to send it to my website, i'm missing something...
>>
>> thanks
>>
>>
>>
>>
>> Op donderdag 3 november 2022 om 01:21:24 UTC+1 schreef Alex Vanuxem:
>>
>>> hey Guys,
>>>
>>> I'm trying weewx for the first time, no experience in python, a
>>> little bit in php
>>>
>>> done the setup as required.
>>>
>>> running ubuntu as a virtual machine on windows, want to check it out
>>> before i buy a raspberry.
>>>
>>> problems: in the config file I see a lot of setups which I dont get
>>> when performing the the how to.
>>>
>>> sudo tail -f /var/log/syslog doesn't exist, I'm stuck with the nOrth
>>> pole default thing.
>>>
>>> and sudo ./bin/weewxd doesn't exist???
>>>
>>> although i configured the config manually and copied it.
>>>
>>> what files do you want to troubleshout?
>>>
>>> I've set up a cumulusMX, pwsWD and a meteotemplate website, so this
>>> should work too?
>>>
>>> Bare with me please,
>>>
>>> THX
>>>
>>> alex
>>>
>> --
>>> 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/dc807670-b1e8-46c7-9cef-121c27c8a812n%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/CAHaYyoJ5V4qo-J5e9OWZkg0hT3XT8SMr_cfCz0DgiMoSdMfu4g%40mail.gmail.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
> 

Re: [weewx-user] $almanac varying values

[Tom Keffer]

Makes sense. Sounds like for your application constant values for
temperature and pressure would probably be best.

On Fri, Nov 4, 2022 at 10:36 AM Karen K  wrote:

> tke...@gmail.com schrieb am Freitag, 4. November 2022 um 17:01:25 UTC+1:
>
>> $almanac(almanac_time=1655805600,
>> temperature=$current(timestamp=1655805600).outTemp.raw,
>> pressure=$current(timestamp=1655805600).barometer.raw).sunrise
>>
>> Hopefully that works!
>>
>
> It works perfect!
>
>
>> Are you just experimenting, or do you have a use case where you want the
>> corrected sunrise at a specific time?
>>
>>>
>>>
> Additionally to the weather observations we use WeeWX to store and
> visualize the data of our photovoltaics system. There I am creating a table
> like the NOAA tables, showing sunrise and sunset time and the time the sun
> is up enough for photovoltaics and the energy production and also the
> energy consumption for the time when the sun is up and when the sun is down
> separately. When the sun is up we can use the energy directly out of the
> photovoltaics system. When the sun is down we need to use a battery storage
> system and/or buy energy from an electric power plant. So it seems useful
> to know at which time of day we consume how much energy.
>
> --
> 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/42990583-7baf-4178-9ba2-a7cea7915120n%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/CAPq0zEDT_yNcNYBN10vAjxQBT3zcxz9TR%2BsadVRiqgarJZr9Aw%40mail.gmail.com.

Re: [weewx-user] $almanac varying values

[Karen K]

tke...@gmail.com schrieb am Freitag, 4. November 2022 um 17:01:25 UTC+1:

> $almanac(almanac_time=1655805600, 
> temperature=$current(timestamp=1655805600).outTemp.raw, 
> pressure=$current(timestamp=1655805600).barometer.raw).sunrise
>
> Hopefully that works!
>

It works perfect!
 

> Are you just experimenting, or do you have a use case where you want the 
> corrected sunrise at a specific time?
>
>>
>>
Additionally to the weather observations we use WeeWX to store and 
visualize the data of our photovoltaics system. There I am creating a table 
like the NOAA tables, showing sunrise and sunset time and the time the sun 
is up enough for photovoltaics and the energy production and also the 
energy consumption for the time when the sun is up and when the sun is down 
separately. When the sun is up we can use the energy directly out of the 
photovoltaics system. When the sun is down we need to use a battery storage 
system and/or buy energy from an electric power plant. So it seems useful 
to know at which time of day we consume how much energy.

-- 
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/42990583-7baf-4178-9ba2-a7cea7915120n%40googlegroups.com.

Re: [weewx-user] $almanac varying values

[Tom Keffer]

This is a good point. I had it wrong. The value for almanac_time is used
for the position of the heavenly body. The database lookup is done with
whatever the "current  time" is, generally the last timestamp in the
database.

So, to set both, you'd have to do something like:

$almanac(almanac_time=1655805600,
temperature=$current(timestamp=1655805600).outTemp.raw,
pressure=$current(timestamp=1655805600).barometer.raw).sunrise

Hopefully that works!

Are you just experimenting, or do you have a use case where you want the
corrected sunrise at a specific time?

On Fri, Nov 4, 2022 at 8:42 AM Karen K  wrote:

> tke...@gmail.com schrieb am Freitag, 4. November 2022 um 13:38:42 UTC+1:
>
>> If you provide almanac_time, then it looks them up in the database.
>> Otherwise, it uses the last time stamp in the database.
>>
>>>
>>>
> In my first example I provided an almanac_time. And there was a database
> record for that time. If it would use almanac_time to look into the
> database, I would guess it should get the same temperature and pressure for
> the same almanac_time all the time. But if so, why then vary the
> calculated sunrise values?
>
> I am afraid it uses the actual temperature and pressure instead of that at
> almanac_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/b2817b08-2f27-43b9-b02b-2de9123d3829n%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/CAPq0zEBoOh72aM4DOjJ0a3UkzZ3o0yzRUSJa3Uzg9uPCVbWYHw%40mail.gmail.com.

Re: [weewx-user] $almanac varying values

[Karen K]

tke...@gmail.com schrieb am Freitag, 4. November 2022 um 13:38:42 UTC+1:

> If you provide almanac_time, then it looks them up in the database. 
> Otherwise, it uses the last time stamp in the database.
>
>>
>>
In my first example I provided an almanac_time. And there was a database 
record for that time. If it would use almanac_time to look into the 
database, I would guess it should get the same temperature and pressure for 
the same almanac_time all the time. But if so, why then vary the calculated 
sunrise values?

I am afraid it uses the actual temperature and pressure instead of that at 
almanac_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/b2817b08-2f27-43b9-b02b-2de9123d3829n%40googlegroups.com.

[weewx-user] Re: UDP listener (for Weatherflow Tempest) won't run

[weatherl...@gmail.com]

Dumb on my part. I'm on a VM and didn't have the network set up right. All 
fixed, many thanks

On Thursday, November 3, 2022 at 5:01:05 PM UTC-4 vince wrote:

> It's not hearing anything.   Your hub is either offline or your network 
> isn't getting the broadcast messages to the system you're listening on. 
>  Did you perhaps VLAN your network and put the hub on a different VLAN ?
>
> You'll need to crtl-C twice to stop it.  The error is normal so it can be 
> ignored.
>
> On Thursday, November 3, 2022 at 1:26:06 PM UTC-7 weatherl...@gmail.com 
> wrote:
>
>> I realize this is not strictly a WeeWx issue but perhaps Vince can see 
>> from the Terminal results below what I might be doing wrong.
>>
>> I've always been able to run this but can get it to work this time.
>>
>> Ubuntu 20.04
>> UDP Listener V 4.x
>>
>> I issue:
>> /Downloads/WeeWx/weatherflow-udp-listener-master$ python3 listen.py 
>> --decoded
>>
>> and nothing happens.
>>
>> When I hit Ctrl-C, this is the result.
>>
>>
>>
>>
>>
>>
>>
>> *^CTraceback (most recent call last):  File "listen.py", line 785, in 
>> t.join()  File "/usr/lib/python3.8/threading.py", line 1011, in 
>> joinself._wait_for_tstate_lock()  File 
>> "/usr/lib/python3.8/threading.py", line 1027, in _wait_for_tstate_lock
>> elif lock.acquire(block, timeout):KeyboardInterrupt*
>>
>> I know the Tempest is working as I receive its data in the Tempest App on 
>> the iPad.
>>
>

-- 
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/bc67ce4d-ddf9-4392-9be3-de795acbf265n%40googlegroups.com.

Re: [weewx-user] $almanac varying values

[Greg Troxel]

Tom Keffer  writes:

> If you provide almanac_time, then it looks them up in the database.
> Otherwise, it uses the last time stamp in the database.
>
> If the database is not available, then it defaults to 15°C and 1010 mbar.

I am curious about the rationale for 1010, vs 1013.25.  And, barometric
vs station pressur for sunrise, or maybe it's really surface pressure at
the tangent point.   But I get it that this delta is in the weeds, vs
980 and 1030 maybe being detectably different.

I have not attempted to average my pressures over multiple years to see
if that comes out at the standard pressure, which would be a blend of a
"average is different from standard" signal and calibration error.

-- 
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/rmi5yfu6fol.fsf%40s1.lexort.com.


signature.asc
Description: PGP signature

Re: [weewx-user] $almanac varying values

[Tom Keffer]

If you provide almanac_time, then it looks them up in the database.
Otherwise, it uses the last time stamp in the database.

If the database is not available, then it defaults to 15°C and 1010 mbar.

On Fri, Nov 4, 2022 at 5:14 AM Karen K  wrote:

> tke...@gmail.com schrieb am Donnerstag, 3. November 2022 um 23:42:17
> UTC+1:
>
>> Pressure and temperature also factor into the calculation. If you want to
>> hold them constant as well, then use something like:
>>
>> $current.dateTime , $almanac(almanac_time=1655805600, temperature=20.0,
>> pressure=1010.0).sunrise
>>
>
> Could you say, where $almanac gets temperature and pressure from, if they
> are not provided by the user?
>
>
> --
> 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/4c0df27b-1bc7-4f96-a631-8bae6435752cn%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/CAPq0zED1WRDJpXHgAtroMsytUX%2BqXuOwNmkLj%2Bot69qFHedTrg%40mail.gmail.com.

Re: [weewx-user] $almanac varying values

[Karen K]

tke...@gmail.com schrieb am Donnerstag, 3. November 2022 um 23:42:17 UTC+1:

> Pressure and temperature also factor into the calculation. If you want to 
> hold them constant as well, then use something like:
>
> $current.dateTime , $almanac(almanac_time=1655805600, temperature=20.0, 
> pressure=1010.0).sunrise
>

Could you say, where $almanac gets temperature and pressure from, if they 
are not provided by the user?
 

-- 
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/4c0df27b-1bc7-4f96-a631-8bae6435752cn%40googlegroups.com.

Re: [weewx-user] Re: cant registrer my weather stations

[matthew wall]

On Thursday, November 3, 2022 at 5:06:41 PM UTC-4 tke...@gmail.com wrote:

> The problem is the "location" option. Here's the error showing up on 
> weewx.com:
>
> 2022.11.03 17:45:34 execute failed: Incorrect string value: 
> '\xCE\x9C\xCE\xB5\xCF\x84...' for column 'description' at row 1 
> reg={description=Μετεωρολογικός Σταθμός Νέων Μουδανιών 
> Χαλκιδικής,last_addr=87.202.32.10,last_seen=1667497534,latitude=40.2430,longitude=23.2770,platform_info=Linux-5.10.0-16-amd64-x86_64-with-glibc2.31,python_info=3.9.2,station_model=WΗ1080,station_type=FineOffsetUSB,station_url=
> https://kairos.moudania.com,user_agent=weewx/4.9.1,weewx_info=4.9.1}
>
> Unfortunately, the registry does not handle utf-8 characters well, which 
> is a known problem. See Issue #7 
> .
>
> I would fix it myself, but all that stuff is written in Perl by mwall, and 
> I don't have a clue how that language works.
>

for the record, on 03nov2022, i modified the registry database schema so 
that the 'description' field would use utf8 4-byte encoding instead of 
latin1.  more detail in the issue mentioned above.

no changes to the perl code :)

-- 
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/4bf7e697-e5ca-47a8-9c49-4e6aee8da592n%40googlegroups.com.

Re: [weewx-user] Time and date format in Weewx database

[Tom Keffer]

Not to be too terribly pedantic, but unix time does deal with leap seconds.
It's just that it deals with them using a discontinuity at midnight. The
result is that if you calculate the difference in unix epoch time between,
say, 23:55 and 00:10, it will *always* be 900 seconds, even if a leap
second was inserted in there. However, if you were to calculate the
difference in UTC, it would be 901 seconds if a leap second occurred.

99.9% of the time, this is what you want. It's a brilliant solution to a
difficult problem. The only problem is that every couple of years or so,
there will be a unit timestamp that is ambiguous. There will be two times
with the same timestamp.



On Fri, Nov 4, 2022 at 3:35 AM Greg Troxel  wrote:

>
> Phillip Fischer  writes:
>
> > Thank You! I am fairly new to the world of linux and learning new things
> > each day! I appreciate your time to answer my question.
>
> This is likely beyond what you care about, but note that the time values
> are the number of seconds since January 1, 1970 UTC **as if there were
> no leap seconds**.
>
> But with weather data every 15 minuts, that just means that occasionally
> those timestamps that differ from 900 will be 901 (or maybe in the
> future 899 seconds apart).  And, surely your weather station doesn't
> have leap second support, and your computer doesn't have a network
> connection.
>
>
> But seriously, I don't know how you are dealing with time, and probably
> you want to have a GPS receiver and run ntpd to sync the RPI's clock,
> and understand how that relates to the weather station's clock.
>
> You probably also want to run the RPI in UTC, and also the weather
> stations, so that there is no daylight savings time confusion.  weewx
> does not as far as I know support "operate in UTC but produce
> graphs/summaries in local time (meaning "today" as a 24h period,
> min/max, etc.)".  But you are just going to process the weewx.sdb
> elsewhere.
>
> I would also put a USB SSD or stick in the Pi and back up the weewx.sdb
> to that daily, in a way that doesn't overwrite the previous backups.
> And a UPS (even a Pi UPS with a battery, but beware of lithium batteries
> below freezing).
>
> --
> 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/rmimt9757os.fsf%40s1.lexort.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/CAPq0zEAJxSXy1dOwePPPWDVXuSoPGdfYVUx9R4kvk%2Bpm%3DDsSsg%40mail.gmail.com.

Re: [weewx-user] Time and date format in Weewx database

[Greg Troxel]

Phillip Fischer  writes:

> Thank You! I am fairly new to the world of linux and learning new things 
> each day! I appreciate your time to answer my question.

This is likely beyond what you care about, but note that the time values
are the number of seconds since January 1, 1970 UTC **as if there were
no leap seconds**.

But with weather data every 15 minuts, that just means that occasionally
those timestamps that differ from 900 will be 901 (or maybe in the
future 899 seconds apart).  And, surely your weather station doesn't
have leap second support, and your computer doesn't have a network
connection.


But seriously, I don't know how you are dealing with time, and probably
you want to have a GPS receiver and run ntpd to sync the RPI's clock,
and understand how that relates to the weather station's clock.

You probably also want to run the RPI in UTC, and also the weather
stations, so that there is no daylight savings time confusion.  weewx
does not as far as I know support "operate in UTC but produce
graphs/summaries in local time (meaning "today" as a 24h period,
min/max, etc.)".  But you are just going to process the weewx.sdb
elsewhere.

I would also put a USB SSD or stick in the Pi and back up the weewx.sdb
to that daily, in a way that doesn't overwrite the previous backups.
And a UPS (even a Pi UPS with a battery, but beware of lithium batteries
below freezing).

-- 
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/rmimt9757os.fsf%40s1.lexort.com.


signature.asc
Description: PGP signature

Re: [weewx-user] Time and date format in Weewx database

[Phillip Fischer]

Thank You! I am fairly new to the world of linux and learning new things 
each day! I appreciate your time to answer my question.

I've successfully converted the time and date stamps!

On Friday, 4 November 2022 at 11:33:50 UTC+2 peterq...@gmail.com wrote:

> A little more background. It's a unix epoch datetime. The number of 
> seconds since 1970 iirc. Google unix epoch.
>
> On Fri, Nov 4, 2022, 10:14 AM Glenn McKechnie  
> wrote:
>
>> unixepoch, epochtime, unixtime
>>
>> from a linux terminal...
>>
>> $ date -d now +'%s'
>> 1667553105
>>
>> $ date -d @1667553105
>> Fri 04 Nov 2022 20:11:45 AEDT
>>
>> man date
>>
>> within a mysql (mariadb)...
>> SELECT FROM_UNIXTIME(datetime, '%d-%m-%Y %H:%i') from archive WHERE
>> dateTime = 166734;
>>
>> there'll be something similar for sqlite
>>
>> On 04/11/2022, Phillip Fischer  wrote:
>> > I hope that someone would be able to point me in the right direction.
>> >
>> > I am aiming to use Weewx to log data from a weather station console of a
>> > station that is set up in a remote, out of the way area as part of my
>> > research. Due to an oversight in Station specs, I was given a station 
>> that
>> > will need to be downloaded every two weeks or else the data is 
>> overwritten,
>> >
>> > but getting to the site every two weeks is not going to happen!
>> >
>> > I've got the station running, connected to a Raspberry Pi Zero 2 and it 
>> is
>> > working and logging data without issue.
>> >
>> > It is easy to get into the .sdb and convert the data to .csv for export 
>> to
>> > analyse the data off site. There is no cell signal, wifi or any other 
>> way
>> > of connectivity at the site so the data needs to be physically 
>> downloaded.
>> >
>> > I am however a bit stumped as I cannot figure out in what format the 
>> date
>> > and time is stored as. It seems to be a serial number, but I am not sure
>> > how to convert that back to Date and Time.
>> >
>> > Does anyone perhaps have an idea on how to get the conversion done? I
>> > cannot find any explanation in the documentation about the units of the
>> > database values.
>> >
>> > dateTime
>> > 1667481600
>> > 1667481900
>> > 1667483700
>> > 1667484000
>> > 1667484300
>> > 1667484600
>> > 1667484900
>> > 1667485200
>> > 1667485500
>> > 1667485800
>> > 1667486100
>> >
>> > --
>> > 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/88e58150-35a5-4841-bea2-452d573b6f6dn%40googlegroups.com
>> .
>> >
>>
>>
>> -- 
>>
>>
>> Cheers
>>  Glenn
>>
>> rorpi - read only raspberry pi & various weewx addons
>> https://github.com/glennmckechnie
>>
>> -- 
>> 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/CAAraAzi8A02nYOkcwdDuz0ig_omcGZpWEKdTr%2B1fy9Oda1Pvog%40mail.gmail.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/9a6f9434-8477-46d1-a9c3-bd6197ba1990n%40googlegroups.com.

Re: [weewx-user] Time and date format in Weewx database

[p q]

A little more background. It's a unix epoch datetime. The number of seconds
since 1970 iirc. Google unix epoch.

On Fri, Nov 4, 2022, 10:14 AM Glenn McKechnie 
wrote:

> unixepoch, epochtime, unixtime
>
> from a linux terminal...
>
> $ date -d now +'%s'
> 1667553105
>
> $ date -d @1667553105
> Fri 04 Nov 2022 20:11:45 AEDT
>
> man date
>
> within a mysql (mariadb)...
> SELECT FROM_UNIXTIME(datetime, '%d-%m-%Y %H:%i') from archive WHERE
> dateTime = 166734;
>
> there'll be something similar for sqlite
>
> On 04/11/2022, Phillip Fischer  wrote:
> > I hope that someone would be able to point me in the right direction.
> >
> > I am aiming to use Weewx to log data from a weather station console of a
> > station that is set up in a remote, out of the way area as part of my
> > research. Due to an oversight in Station specs, I was given a station
> that
> > will need to be downloaded every two weeks or else the data is
> overwritten,
> >
> > but getting to the site every two weeks is not going to happen!
> >
> > I've got the station running, connected to a Raspberry Pi Zero 2 and it
> is
> > working and logging data without issue.
> >
> > It is easy to get into the .sdb and convert the data to .csv for export
> to
> > analyse the data off site. There is no cell signal, wifi or any other way
> > of connectivity at the site so the data needs to be physically
> downloaded.
> >
> > I am however a bit stumped as I cannot figure out in what format the date
> > and time is stored as. It seems to be a serial number, but I am not sure
> > how to convert that back to Date and Time.
> >
> > Does anyone perhaps have an idea on how to get the conversion done? I
> > cannot find any explanation in the documentation about the units of the
> > database values.
> >
> > dateTime
> > 1667481600
> > 1667481900
> > 1667483700
> > 1667484000
> > 1667484300
> > 1667484600
> > 1667484900
> > 1667485200
> > 1667485500
> > 1667485800
> > 1667486100
> >
> > --
> > 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/88e58150-35a5-4841-bea2-452d573b6f6dn%40googlegroups.com
> .
> >
>
>
> --
>
>
> Cheers
>  Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>
> --
> 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/CAAraAzi8A02nYOkcwdDuz0ig_omcGZpWEKdTr%2B1fy9Oda1Pvog%40mail.gmail.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/CAA1SM225DWn9ySN0QBtJ_2nF%2Ba8%2B55G-MTBwWj5Sj3k60OLezg%40mail.gmail.com.

Re: [weewx-user] Time and date format in Weewx database

[Glenn McKechnie]

unixepoch, epochtime, unixtime

from a linux terminal...

$ date -d now +'%s'
1667553105

$ date -d @1667553105
Fri 04 Nov 2022 20:11:45 AEDT

man date

within a mysql (mariadb)...
SELECT FROM_UNIXTIME(datetime, '%d-%m-%Y %H:%i') from archive WHERE
dateTime = 166734;

there'll be something similar for sqlite

On 04/11/2022, Phillip Fischer  wrote:
> I hope that someone would be able to point me in the right direction.
>
> I am aiming to use Weewx to log data from a weather station console of a
> station that is set up in a remote, out of the way area as part of my
> research. Due to an oversight in Station specs, I was given a station that
> will need to be downloaded every two weeks or else the data is overwritten,
>
> but getting to the site every two weeks is not going to happen!
>
> I've got the station running, connected to a Raspberry Pi Zero 2 and it is
> working and logging data without issue.
>
> It is easy to get into the .sdb and convert the data to .csv for export to
> analyse the data off site. There is no cell signal, wifi or any other way
> of connectivity at the site so the data needs to be physically downloaded.
>
> I am however a bit stumped as I cannot figure out in what format the date
> and time is stored as. It seems to be a serial number, but I am not sure
> how to convert that back to Date and Time.
>
> Does anyone perhaps have an idea on how to get the conversion done? I
> cannot find any explanation in the documentation about the units of the
> database values.
>
> dateTime
> 1667481600
> 1667481900
> 1667483700
> 1667484000
> 1667484300
> 1667484600
> 1667484900
> 1667485200
> 1667485500
> 1667485800
> 1667486100
>
> --
> 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/88e58150-35a5-4841-bea2-452d573b6f6dn%40googlegroups.com.
>


-- 


Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

-- 
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/CAAraAzi8A02nYOkcwdDuz0ig_omcGZpWEKdTr%2B1fy9Oda1Pvog%40mail.gmail.com.

Re: [weewx-user] Time and date format in Weewx database

[Stephen Hocking]

Hi Phillip,

It's in Unix Epoch time - this website will help you on how to convert it
to a sensible date & time.

https://www.epochconverter.com/#:~:text=The%20Unix%20epoch%20(or%20Unix,01T00%3A00%3A00Z)
.

On Fri, 4 Nov 2022 at 19:38, Phillip Fischer  wrote:

> I hope that someone would be able to point me in the right direction.
>
> I am aiming to use Weewx to log data from a weather station console of a
> station that is set up in a remote, out of the way area as part of my
> research. Due to an oversight in Station specs, I was given a station that
> will need to be downloaded every two weeks or else the data is overwritten,
> but getting to the site every two weeks is not going to happen!
>
> I've got the station running, connected to a Raspberry Pi Zero 2 and it is
> working and logging data without issue.
>
> It is easy to get into the .sdb and convert the data to .csv for export to
> analyse the data off site. There is no cell signal, wifi or any other way
> of connectivity at the site so the data needs to be physically downloaded.
>
> I am however a bit stumped as I cannot figure out in what format the date
> and time is stored as. It seems to be a serial number, but I am not sure
> how to convert that back to Date and Time.
>
> Does anyone perhaps have an idea on how to get the conversion done? I
> cannot find any explanation in the documentation about the units of the
> database values.
>
> dateTime
> 1667481600
> 1667481900
> 1667483700
> 1667484000
> 1667484300
> 1667484600
> 1667484900
> 1667485200
> 1667485500
> 1667485800
> 1667486100
>
> --
> 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/88e58150-35a5-4841-bea2-452d573b6f6dn%40googlegroups.com
> 
> .
>


-- 

  "I and the public know
  what all schoolchildren learn
  Those to whom evil is done
  Do evil in return"W.H. Auden, "September 1, 1939"

-- 
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/CA%2BxzKjBVSYm%2BqFuK%3Ds0mfbu2B0Y5gYmDeTOdWk2fyE_4dFi8Bw%40mail.gmail.com.

[weewx-user] Time and date format in Weewx database

[Phillip Fischer]

I hope that someone would be able to point me in the right direction.

I am aiming to use Weewx to log data from a weather station console of a 
station that is set up in a remote, out of the way area as part of my 
research. Due to an oversight in Station specs, I was given a station that 
will need to be downloaded every two weeks or else the data is overwritten, 
but getting to the site every two weeks is not going to happen!

I've got the station running, connected to a Raspberry Pi Zero 2 and it is 
working and logging data without issue.

It is easy to get into the .sdb and convert the data to .csv for export to 
analyse the data off site. There is no cell signal, wifi or any other way 
of connectivity at the site so the data needs to be physically downloaded.

I am however a bit stumped as I cannot figure out in what format the date 
and time is stored as. It seems to be a serial number, but I am not sure 
how to convert that back to Date and Time.

Does anyone perhaps have an idea on how to get the conversion done? I 
cannot find any explanation in the documentation about the units of the 
database values.

dateTime
1667481600
1667481900
1667483700
1667484000
1667484300
1667484600
1667484900
1667485200
1667485500
1667485800
1667486100

-- 
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/88e58150-35a5-4841-bea2-452d573b6f6dn%40googlegroups.com.