from:"Dominic Reich"

Re: [weewx-user] Will the ECOWITT WS2910 work within WEEWX?

2024-09-30 Thread Dominic Reich


Colin Lloyd  wrote:


I've installed WEEWX successfully on my Linux Mint 21 PC. And the web page at
file:///var/www/html/weewx/index.html works OK.

reply from sudo systemctl status weewx gives:

weewx.service - WeeWX
     Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor preset:
enabled)
     Active: failed (Result: exit-code) since Mon 2024-09-30 10:44:45 BST; 1h
1min ago
       Docs: https://weewx.com/docs
    Process: 2214 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, status=
4)
   Main PID: 2214 (code=exited, status=4)
        CPU: 56ms

Sep 30 10:44:45 colin-PC weewxd[2214]: CRITICAL weewx.engine:         
 return FineOffsetUSB(**config_dict[DRIVER_NAME])
Sep 30 10:44:45 colin-PC weewxd[2214]: CRITICAL weewx.engine:         File
"/usr/share/weewx/weewx/drivers/fousb.py", line 967, in __init__
Sep 30 10:44:45 colin-PC weewxd[2214]: CRITICAL weewx.engine:         
 self.openPort()
Sep 30 10:44:45 colin-PC weewxd[2214]: CRITICAL weewx.engine:         File
"/usr/share/weewx/weewx/drivers/fousb.py", line 1022, in openPort
Sep 30 10:44:45 colin-PC weewxd[2214]: CRITICAL weewx.engine:         
 raise weewx.WeeWxIOError("Unable to find USB device")
Sep 30 10:44:45 colin-PC weewxd[2214]: CRITICAL weewx.engine:     
 weewx.WeeWxIOError: Unable to find USB device
Sep 30 10:44:45 colin-PC weewxd[2214]: CRITICAL __main__: Unable to load
driver: Unable to find USB device
Sep 30 10:44:45 colin-PC weewxd[2214]: CRITICAL __main__:       Exiting...
Sep 30 10:44:45 colin-PC systemd[1]: weewx.service: Main process exited, code=
exited, status=4/NOPERMISSION
Sep 30 10:44:45 colin-PC systemd[1]: weewx.service: Failed with result
'exit-code'.

In /etc/weewx/weewx.conf the driver is set to FineOffsetUSB - which pointed to
the (to me) most relevant station to my ECOWITT WS2910 station. But the ECOWITT
is a WiFi station - not USB. So I suspect I have linked up with the wrong
driver. Can anyone tell me which driver or clone system to my ECOWITT I should
be using. This is my first entry into commercial weather stations having
created my own Arduino or Raspberry Pi versions in the past - so am a bit lost.


I think you have two options:

a) use an SDR stick and try to catch the weatherstation directly at its
frequency (in europe 868MHz, etc) - you will need something like
this: 

b) use (and buy) a GW1000/GW1100 from Ecowitt (that listens on that
frequency and provides a webpage) and use the gw1000 driver:
 - you will access the
weatherstation via your network and not over other radio frequencies.

I use the GW1000 driver myself and have never used a SDR driver for a
weatherstation - I have seen on other hobbies that running something
like rtl_fm to listen to frequencies with SDR sticks is a little bit
more CPU consuming than just fetching the data via WiFi (or LAN).

Regarding the webpage on your local filesystem: does it get updated or
what time does it mention, because i doubt it will be updated because of
the stopped weewx service...

-dominic

--
Educating the mind without educating the heart is no education at all.
- Aristotle

--
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/ntqhVHvXJbM3-HHgzh9-0924%40odin.oe7drt.com.

Re: [weewx-user] FTP problem

2024-09-29 Thread Dominic Reich


Guido Groetie  wrote:


Hello, I hope it is because of a WIFI connection that is very slow, but when
Weewx is FTP the files to the webserver, I see this errors:
Sep 27 15:46:20 byows-jim weewxd[3001]: ERROR weeutil.ftpupload: Failed
uploading /var/www/html/weewx/year-2024.html to server 192.168.1.74. Reason:>
Sep 27 15:46:34 byows-jim weewxd[3001]: ERROR weewx.reportengine: ftpgenerator:
(0): caught exception '': timed out

snip snip



What can I do to prevent it?


On the same host WeeWX is running, can you reach the FTP server with
another program? Can you ping the FTP servers IP address, can you
resolve the FTP servers DNS name (no idea what you have set in your
configuration, so try both).

-dominic

--
Whenever you find yourself on the side of the majority,
it is time to reform (or pause and reflect).
- Mark Twain

--
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/sqPwm7zbT9gp-MPn3tv-0924%40odin.oe7drt.com.

Re: [weewx-user] Installation of extension fails for pip installed WeeWX but works for apt installed WeeWX

2024-07-14 Thread Dominic Reich


I doubt `sudo` should be used here.

Karen K  wrote:


One user tried to install [1]weewx-DWD into an WeeWX installation made by pip.
The error messages refer to files of core WeeWX:



   (weewx-venv) user@pc:~$ sudo weectl extension install weewx-dwd.zip
   [sudo] Passwort für user:
   Error parsing config file: Unable to find file 'weewx.conf'. Tried
   directories ['/root/weewx-data', '/etc/weewx', '/home/weewx']
   Traceback (most recent call last):
   File "/usr/share/weewx/weeutil/startup.py", line 86, in start_app
   config_path, config_dict = weecfg.read_config(config_option, [config_arg])
   ^^^
   File "/usr/share/weewx/weecfg/init.py", line 147, in read_config
   config_path = find_file(option_path, args, locations=locations, file_name=
   file_name)
   ^^
   File "/usr/share/weewx/weecfg/init.py", line 104, in find_file
   raise OSError(f"Unable to find file '{file_name}'. Tried directories
   {locations}")
   OSError: Unable to find file 'weewx.conf'. Tried directories ['/root/
   weewx-data', '/etc/weewx', '/home/weewx']


I have no glue what happens there. The messages say, that weewx.conf could not
be found. Looking for that file is not part of install.py. 

Unfortunately I cannot try the installation myself actually. And I have no
experience with weewx-venv.

See [2]install.py here.

There is a configure() method in this case, which is not widely used. But there
is no reference to weewx.conf in it. I would have expected that the copying and
linking in it may fail within a virtual environment, but the error messages say
otherwise.



--
Life is really simple, but we insist on making it complicated.
- Confucius

--
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/q7fXzds3zxpb-VmJ7nH-0724%40odin.oe7drt.com.

Re: [weewx-user] Display the first date entry in the database

2024-02-16 Thread Dominic Reich


Meteo Oberwallis  wrote:


Hello everyone
I would like to display the date of the first entry in the weexs.sdb in
Belchertownskin. The reason for this is that you can see how long the weather
station has been in operation. Since I operate several stations, this would
make my work extremely easier. This could say something like "Operating since:
10/2023" or something like that. Can someone help me with that?
Thank you and sunny greetings


Just fetch the first entry from the database.

sqlite3 dbfile.db "SELECT dateTime FROM archive LIMIT 1;"

(untested)

--
The quieter you become, the more you can hear.
- Ram Dass

--
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/d9JLkt9bqdhx-73wMzL-0224%40odin.oe7drt.com.

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

2024-02-14 Thread Dominic Reich


Hello, i replied inline.

Pierre-Yves  wrote:


Thanks Vince

I found in rtl-sdr. rules a rule corresponding to my SDR stick :

SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", ENV
{ID_SOFTWARE_RADIO}="1", MODE="0660", GROUP="plugdev"

I added the weewx user to that group: "sudo usermod -aG plugdev weewx"

I still can start weewx with the  "sudo weewd" command as before but I can't
run weewx in daemon mode. "sudo  systemctl start weewx" gives still the same
error :

Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Starting main
packet loop.
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: Nous espérons que
vous avez reçu de votre administrateur système local
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: les consignes
traditionnelles. Généralement, elles se concentrent sur ces trois éléments :
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:     #1) Respectez la
vie privée des autres.
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:     #2) Réfléchissez
avant d'utiliser le clavier.
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:     #3) De grands
pouvoirs confèrent de grandes responsabilités.
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: un terminal est
requis pour lire le mot de passe; utilisez soit l'option -S pour lire depuis
l'entrée standard ou configurez un outil askpass de demande de mot de passe
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: il est
nécessaire de saisir un mot de passe


I don't speak french, but it looks like you still have a sudo command
somewhere in your unit file.

Would you please show us the contents of your running unit file

systemctl show -P FragmentPath weewx.service

will get you the path of that file. cat that file and paste it here or
if you are confident remove the sudo statement in there somwhere at
ExecStart...="sudo /usr.."

because you should not need sudo when you added weewx to the plugdev
group.

That file contains usually also the information what user runs the
daemon in the end.


Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Main loop exiting.
Shutting engine down.
Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown process sudo
/usr/local/bin/rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k -R 173
-R 172 -R 42 -M utc -F json
Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stdout
Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stderr
Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread stdout-thread:
Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown
stdout-thread
Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call last):
Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread stderr-thread:
Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call last):
Feb 14 08:49:54 raspberrypi weewxd[5905]:   File "/usr/lib/python3.9/
threading.py", line 954, in _bootstrap_inner
Feb 14 08:49:54 raspberrypi weewxd[5905]:   File "/usr/lib/python3.9/
threading.py", line 954, in _bootstrap_inner
Feb 14 08:49:54 raspberrypi weewxd[5905]:     self.run()
Feb 14 08:49:54 raspberrypi weewxd[5905]:   File "/etc/weewx/bin/user/sdr.py",
line 198, in run
Feb 14 08:49:54 raspberrypi weewxd[5905]:     self.run()
Feb 14 08:49:54 raspberrypi weewxd[5905]:   File "/etc/weewx/bin/user/sdr.py",
line 198, in run
Feb 14 08:49:54 raspberrypi weewxd[5905]:     for line in iter
(self._fd.readline, ''):
Feb 14 08:49:54 raspberrypi weewxd[5905]: ValueError: PyMemoryView_FromBuffer
(): info->buf must not be NULL
Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown
stderr-thread
Feb 14 08:49:54 raspberrypi weewxd[5905]:     for line in iter
(self._fd.readline, ''):
Feb 14 08:49:54 raspberrypi weewxd[5905]: ValueError: PyMemoryView_FromBuffer
(): info->buf must not be NULL
Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown complete
Feb 14 08:49:54 raspberrypi weewxd[5905]: CRITICAL __main__: Caught
WeeWxIOError: rtl_433 process is not running
Feb 14 08:49:54 raspberrypi weewxd[5905]: CRITICAL __main__:       Waiting
60.0 seconds then retrying...
Feb 14 08:50:03 raspberrypi weewxd[5905]: INFO __main__: Received signal TERM
(15).
Feb 14 08:50:03 raspberrypi systemd[1]: Stopping WeeWX...
Feb 14 08:50:03 raspberrypi weewxd[5905]: Traceback (most recent call last):
Feb 14 08:50:03 raspberrypi weewxd[5905]:   File "/usr/share/weewx/weewxd.py",
line 166, in main
Feb 14 08:50:03 raspberrypi weewxd[5905]:     engine.run()
Feb 14 08:50:03 raspberrypi weewxd[5905]:   File "/usr/share/weewx/weewx/
engine.py", line 204, in run
Feb 14 08:50:03 raspberrypi weewxd[5905]:     for packet in
self.console.genLoopPackets():
Feb 14 08:50:03 raspberrypi weewxd[5905]:   Fil

Re: [weewx-user] No HTML generation after upgrade from 5.0.0 to 5.0.1

2024-02-08 Thread Dominic Reich

'neu...@bnjpro.dk' via weewx-user wrote:

output of "ls -al /vat/www/rumoclock.dk/web/weewx/" is:
total 920
drwxrwsr-x 7 web1 client1 4096 feb 8 14:19 .

So as you aint answered which user weewx is running I assume it is
running as weewx as that would also explain that you cannot create the
temp files when creating the HTLM output:

Feb 8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:
[Errno 13] Permission denied: '/var/www/rumoclock.dk/web/weewx/index.html.tmp'

You wrote you did `chown -R weewx: /var/www/rumoclock.dk/web/weewx/` -
but that directory is still owned by user web1. So either you did not
run the command or it gets reverted by something else (maybe your
ispconfig tool).

If that's not the case, maybe another directory on the path is missing
permissions, you can check that too with this:

ls -ld /vat/www/{,rumoclock.dk/{,web}}

I doubt /var/www will have wrong permissions, but you can check those
directories as well if everything else looks ok.

Also maybe run `sudo ps ux | grep weewxd` to confirm the daemon runs as
user weewx - it is, probably.

drw-r-xr-x 4 root root 4096 jul 17 2023 ..
[snip files...]

My weewx output is actually generated and put in the standard output folder: /
var/www/html/weewx/ All files in here are chmod 644 and chown weewx:weewx.

But in order to be shown right in my setup using a open-source control-panel
called ispconfig, In the working root of my primary homepage I have made a
folder called /weewx (hence the /var/www/rumoclock.dk/web/weewx/ with the chown
of that particular virtual homepage chown client1:web1- That folder is
symlinked to the standard output folder. This has worked from version 4.10.2 up
til 5.0.0, but gives me a hard time in 5.0.1 after the upgrade. I can't figure
out why.

torsdag den 8. februar 2024 kl. 20.10.18 UTC+1 skrev vince:

We would need to see "ls -al /var/www/rumoclock.dk/web/weewx/" and also
tell us what user+group weewx is running as.

On Thursday, February 8, 2024 at 5:55:20 AM UTC-8 neu...@bnjpro.dk wrote:

I was to fast. It did come up with the resent generated html, but it
will not continue generating new html pages. It made one for the time I
was at when I did the chown -R weewx: /var/www/rumoclock.dk/web/weewx/

Feb 8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:
PermissionError: [Errno 13] Permission denied: '/var/www/
rumoclock.dk/web/weewx/index.html.tmp'
Feb 8 14:54:16 frej weewxd[754]: ERROR weewx.reportengine:
Generator terminated

--
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/ac78ec0e-1723-4858-9c8c-d87cc0a5cfa0n%40googlegroups.com.

--
Be the change that you wish to see in the world.
- Mahatma Gandhi

--
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/%24fczqnfvnz-%24rZXlPtl-%24RmbQX-2024%40odin.oe7drt.com.

Re: [weewx-user] Re: rsync: host key verification failed - problem

2024-02-08 Thread Dominic Reich

Kalju wrote:

Hi all,

Facing same issue with ERROR weeutil.rsyncupload: Host key verification
failed error.
However, it's really strange...
I can ssh to remote site as both root as well as pi user
I can do manual rsync with no problems but weewx builtin rsync returns above
error
At the moment my weewx installation is syncing using cron with no problems but
I want to understand why builtin rsync fails
Problem started after upgrade from weewx 5.0.0 to 5.0.1

Any ideas?

Adding the debug info should output the actual rsync command initiated by
weewx to the logs. That's what I assume when looking at line 104 in
`src/weeutil/rsyncupload.py` from the sources of 5.0.1.

Maybe that gives a clue in which the actual rsync commands differ and
why it might fail within Weewx.

Somewhere around 5.0.1 or 5.1.x the user got switched to weewx (not root
anymore) so maybe there is a problem? (I can't remember when the switch
was (it was mentioned on the list somwhere) and haven't found it in the
docs yet)

I'd always suggest looking as what weewx is running so you may not have
to play the guessing game on which user to look at.

sudo ps ux | grep weewxd

should return the user that actually runs the (python) daemon like on my
old Raspberry this runs still as root with 4.10.2.

root 690 2.8 1.5 647360 60428 ?Sl Feb06 75:38 python3
/usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid
/etc/weewx/weewx.conf

As it was a package-installation I never messed with it, though I
welcome the change to a non-root package installation per default :)

In case host keys have changed on the server a deletion of the known_hosts
file within ~/.ssh could also help, probably.

-dominic

Thank you forward :-)
On Friday, July 21, 2023 at 1:14:24 PM UTC+3 Tomasz Lewicki wrote:

Thank you for replies.

@Warren Gill: yes, I was thinking about crontab but wanted to use built-in
solution. Of course crontab is good as backup solution.

@vince: you're right, I didn't think about it from this side. Just for
record for future seekers:

1. I logged as root ('sudo -i' from 'pi' account)
2. generated SSH keys ('ssh-keygen')
3. copied them to external server ('ssh-copy-id ace...@external.domain.com
-p 222')
4. copied /home/pi/.ssh/config to /root/.ssh/config
5. changed owner of 'config' ('chown root:root /root/.ssh/config')
6. waited for next synchronization
7. smiled because everything worked as expected :)

--
Educating the mind without educating the heart is no education at all.
- Aristotle

--
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/%24tcqbskwxq-%24bksDsvl-%24pdtHn-2024%40odin.oe7drt.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

2024-02-06 Thread Dominic Reich


'michael.k...@gmx.at' via weewx-user  wrote:



sudo apt install weewx=4.10.2


and to not upgrade again set it on hold:

sudo apt-mark hold weewx


Stefan Gliessmann schrieb am Dienstag, 6. Februar 2024 um 13:02:38 UTC+1:

   I run weewx 4.10.2 on Ubuntu.
   I did an sudo apt update, too,  and weewx 5.x got installed.
   Since then, weewx is no longer running.

   How did you revert back to weewx 4.10.2? 

   TIA,
   Stefan

   On Tuesday, February 6, 2024 at 10:36:52 AM UTC+1 Stefanos Kalaitzis wrote:


   I had the same error with sdr driver(weewx v5 )  running on debian 12 .
   The problem solved by making udev rules ... maybe you are in the same
   situation as i was.


   Στις Τρί 6 Φεβ 2024, 11:29 ο χρήστης Mks Mk  έγραψε:

   The system was running weewx v5.0.0 with no issue then we did the
   upgrade to v5.0.1 (sudo apt update) and weewx failed to run.
   we downgraded weewx to v5.0.0 but it did not work this time, so we
   went back to v4.10.2 and it run just fine.
   did the upgrade again and got the same error.so we are back to
   v4.10.2
   we tested the sdr hardware using rtl_433 and it is working fine.
   we are not sure of what to do next!

   log:
   weewxd[2386]: INFO __main__: Starting up weewx version 5.0.1
   weewxd[2386]: INFO weewx.engine: Using binding 'wx_binding' to
   database 'weewx.sdb'
   weewxd[2386]: INFO weewx.manager: Starting backfill of daily
   summaries
   weewxd[2386]: INFO weewx.manager: Daily summaries up to date
   weewxd[2386]: INFO weewx.engine: Starting main packet loop.
   weewxd[2386]: ERROR user.sdr: rtl_433 version 23.11-41-g06b03b7a
   branch master at 202402051043 inputs file rtl_tcp RTL-SDR
   weewxd[2386]: ERROR user.sdr: Use "-F log" if you want any
   messages, warnings, and errors in the console.
   weewxd[2386]: ERROR user.sdr: usb_open error -3
   weewxd[2386]: ERROR user.sdr: Please fix the device permissions,
   e.g. by installing the udev rules file rtl-sdr.rules
   weewxd[2386]: INFO weewx.engine: Main loop exiting. Shutting engine
   down.
   weewxd[2386]: INFO user.sdr: shutdown process rtl_433 -f 433.7M -s
   1024k -R 40
   weewxd[2386]: Exception in thread stdout-thread:
   weewxd[2386]: Traceback (most recent call last):
   weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954,
   in _bootstrap_inner
   weewxd[2386]: Exception in thread stderr-thread:
   weewxd[2386]: Traceback (most recent call last):
   weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954,
   in _bootstrap_inner
   weewxd[2386]:     self.run()
   weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
   weewxd[2386]:     for line in iter(self._fd.readline, ''):
   weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must
   not be NULL
   weewxd[2386]:     self.run()
   weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
   weewxd[2386]:     for line in iter(self._fd.readline, ''):
   weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must
   not be NULL
   weewxd[2386]: INFO user.sdr: shutdown complete
   weewxd[2386]: CRITICAL __main__: Caught WeeWxIOError: rtl_433
   process is not running
   weewxd[2386]: CRITICAL __main__:       Waiting 60.0 seconds
   then retrying...

   --
   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/
   4c62d6c3-d690-49e8-8151-8b9af8dd5b43n%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/3eff3ae3-8343-437e-a259-ae24753baa61n%40googlegroups.com.



--
If you tell the truth, you don't have to remember anything.
- Mark Twain

--
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/%24kwshnkklb-%24RmhmQzk-%24qdrNT-2024%40odin.oe7drt.com.

Re: Re: [weewx-user] Firefox can’t find the file at /var/www/html/weewx/index.html.

2024-02-03 Thread Dominic Reich

Phil Bilboe wrote:

Thanks for the input, I'm running Weewx on an old laptop with Kubuntu just for
learning purposes. I've installed Lighttpd and its working so thanks again.
Out of interest, my hope is to run Weewx and interogate my Ecowitt gateway with
the GW1000 driver on a Raspberry Pi. Would you recommend I install a web
server, Apache2, Nginx or Lighttpd first on the Raspberry PI OS before
installing Weewx or doesn't it matter?

That should not matter, just match the directories later where WeeWX
writes the files and the webserver reads them.

On Friday 2 February 2024 at 20:48:14 UTC Δημήτρης Βήχος wrote:

install first apache2. then type in firefox http://localhost/weewx/

Στις Παρασκευή 2 Φεβρουαρίου 2024 στις 10:02:24 μ.μ. UTC+2, ο χρήστης
Dominic Reich έγραψε:

Phil Bilboe wrote:

>I pretty sure weewx is running the simulator, however I get Firefox
can’t find
>the file at /var/www/html/weewx/index.html. when I paste into my web
browser.

The files are on the computer that runs weewx, not your local computer.
You will need a webserver that serves the diretory
`/var/www/html/weewx`. For testing purpose you could go into that
directory (on your Raspberry? you didn't told us where your WeeWX is
running) and run a simple http server with python: `python -m
http.server`.
You would then browser this via Firefox with `http://192.168.1.13:8000`
where this would be the address of the computer that runs WeeWX.

If you want this to be running at all time I suggest installing Apache2
or Nginx
webserver (`apt get apache2` or `apt get nginx`).

--
If you tell the truth, you don't have to remember anything.
- Mark Twain

--
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/ac7f8a98-11a8-4e46-87f3-71e99aea2821n%40googlegroups.com.

--
The weak are always anxious for justice and equality.
The strong pay no heed to either.
- Aristotle

--
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/%24jthhmtdls-%24ZbRsNsc-%24jtRKF-2024%40odin.oe7drt.com.

Re: [weewx-user] Firefox can’t find the file at /var/www/html/weewx/index.html.

2024-02-02 Thread Dominic Reich


Phil Bilboe  wrote:


I pretty sure weewx is running the simulator, however I get Firefox can’t find
the file at /var/www/html/weewx/index.html. when I paste into my web browser.


The files are on the computer that runs weewx, not your local computer.
You will need a webserver that serves the diretory
`/var/www/html/weewx`. For testing purpose you could go into that
directory (on your Raspberry? you didn't told us where your WeeWX is
running) and run a simple http server with python: `python -m http.server`.
You would then browser this via Firefox with `http://192.168.1.13:8000`
where this would be the address of the computer that runs WeeWX.

If you want this to be running at all time I suggest installing Apache2 or Nginx
webserver (`apt get apache2` or `apt get nginx`).

--
If you tell the truth, you don't have to remember anything.
- Mark Twain

--
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/%24wvvpctzst-%24DxdSQGd-%24VscdV-2024%40odin.oe7drt.com.

Re: [weewx-user] Re: How do you enable forecast in Weewx-wdc

2024-01-07 Thread Dominic Reich


I think it is possible but not worth the hassle (for non-developers like
me).

The api reports wind gust, so there should be a way to create an
extra row in the forecast_table.inc (and maybe more) files from the
weewx-forecast extension.

#v+
{
  "dt": 1705082400,
  "main": {
"temp": 267.72,
"feels_like": 264.07,
"temp_min": 267.72,
"temp_max": 267.72,
"pressure": 1034,
"sea_level": 1034,
"grnd_level": 890,
"humidity": 67,
"temp_kf": 0
  },
  "weather": [
{
  "id": 800,
  "main": "Clear",
  "description": "clear sky",
  "icon": "01n"
}
  ],
  "clouds": {
"all": 2
  },
  "wind": {
"speed": 2.21,
"deg": 198,
"gust": 2.38
  },
  "visibility": 1,
  "pop": 0,
  "sys": {
"pod": "n"
  },
  "dt_txt": "2024-01-12 18:00:00"
}
#v-

-dominic

Nicholas Waton  wrote:


Thank you!

Is there a way to show forecasted wind gusts? 
I am using the OWM forecast.

On Tuesday, October 4, 2022 at 6:06:04 PM UTC-7 David Bätge wrote:

   There is also a dedicated page for enabling forecast in the wiki of the
   skin: https://github.com/Daveiano/weewx-wdc/wiki/Support-for-weewx-forecast

   Let me know if there are still questions!

   gary@gmail.com schrieb am Sonntag, 2. Oktober 2022 um 17:02:39 UTC+1:

   Don't forget that you will need to add the following to the skin. conf
   [CheetahGenerator]
           search_list_extensions 

   user.forecast.ForecastVariables,
   user.weewx_wdc_forecast.WdcForecastUtil

   On Sunday, October 2, 2022 at 11:57:44 AM UTC-4 gary@gmail.com
   wrote:

   weewx.conf
   Adjust HTML_ROOT to your paths
   Use your WU API key
   Get your NWS values and use those.

       [[WdcReport]]
           skin = weewx-wdc
           enable = true
           HTML_ROOT = /home/web/wdc
           lang = en

       [[forecast]]
           skin = forecast
           HTML_ROOT = /home/web/forecast

   [Forecast]
       data_binding = forecast_binding
       #[[XTide]]
       #    location = "INSERT_LOCATION_HERE (e.g., Boston)"
       [[Zambretti]]
           hemisphere = NORTH
       [[NWS]]
           lid = MAZ011
           foid = BOX
       [[WU]]
           api_key = 
       #[[OWM]]
       #    api_key = INSERT_OWM_API_KEY_HERE
       #[[UKMO]]
       #    api_key = INSERT_UKMO_API_KEY_HERE
       #    location = INSERT_UK_LOCATION_HERE
       #[[Aeris]]
       #    client_id = INSERT_AERIS_CLIENT_ID_HERE
       #    client_secret = INSERT_AERIS_CLIENT_SECRET_HERE
       #[[WWO]]
       #    api_key = INSERT_WWO_API_KEY_HERE
       #[[DS]]
       #    api_key = INSERT_DS_API_KEY_HERE


   skin.conf
   Make adjustments for your location.

   # configuration file for the weewx-wdc skin
   SKIN_NAME = Weather Data Center
   SKIN_VERSION = 2.1.0

   [Extras]
       # Show a link to the GitHub respository of this skin. Set to
   False to hide.
       github_link = True

       # This radar image would be available as $Extras.radar_img
       #radar_img = https://www.dwd.de/DWD/wetter/radar/
   radfilm_sac_akt.gif
       # This URL will be used as the image hyperlink:
       #radar_url =    https://www.dwd.de/DE/leistungen/radarbild_film
   /radarbild_film.html

       [[forecast_zambretti]]
           enable = True
           hemisphere = NORTH                  

       [[forecast_table_settings]]
           source = WU
           num_periods = 72
           num_days = 5
           show_legend = 1
           show_hourly = 0
           show_day = 1
           show_date = 1
           show_outlook = 1
           show_temp = 1
           show_dewpoint = 0
           show_humidity = 0
           show_wind = 1
           show_tides = 0
           show_sun = 0
           show_moon = 0
           show_pop = 1
           show_precip = 1
           show_obvis = 0

   On Thursday, September 29, 2022 at 2:42:44 PM UTC-4 
   scott.d...@gmail.com wrote:


   I am having difficulty enabling the forecast feature in
   weewx-wdc
   What needs to be included in weewx.conf to have a forecast from
   WU, AERIS, or NWS?


--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group

Re: [weewx-user] Pipe errors etc

2023-12-18 Thread Dominic Reich

* David Hindley [Mon, Dec 18 2023 08:09 +]:

When I type

ps -aux|grep weewx

I get

root 535 5.6 6.1 117524 58128 ?Sl 10:16 2:42 python2
/usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid
/etc/weewx/weewx.conf
pi2130 0.0 0.0 4368 564 pts/0S+ 11:04 0:00 grep
--color=auto weewx

And, then typing

sudo /etc/init.d/weewx stop

produces

Stopping weewx (via systemctl): weewx.service.

but then repeating the grep command, still shows the 535 process still
running?

How do I stop weewx - do I have to use kill 535 perhaps?

That is an option, but I'd first confirm that weewx is not getting
stopped (that can take some seconds to happen though).

If you confirm weewx unstopped after 10 seconds you could kill the
process number with `sudo kill 535` (sending TERM signal to the process)
and if that does not work either you can KILL the process with
`sudo kill -9 535` which will force the process to kill.

You would normally kill a process with TERM, which tells the process to
save and finish, KILL will quit the process regardless of unfinished
operations of that process.

This is usually described in the `signal(3)` manpage, but could differ on
your operating system.

You could also use the pid file of weewx, which could look something
like that to force kill the process:
`sudo kill -9 $(cat /var/run/weewx.pid)`

HTH

- dominic

Thanks

David.

On Sat, 16 Dec 2023 at 19:39, vince wrote:

Sorry - we can't fix your network. Lots of legacy embedded type 2.4GHz
wifi things have issues staying on the network and stable. I'd suggest
you try to see if your wifi is being interfered with from a neighbor
perhaps. Maybe you can switch which channel your wifi is on.

FWIW, we have too many neighbors here with misconfigured wifi to even
count, depending on who moves in/out and who visits them occasionally.
What I eventually needed to do was (a) move everything in the house that
could do it over to 5GHz wifi, and (b) buy a Unifi AcLite AP and basically
try to out-radiate the neighbors. Problem went away at that point.

--
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/q67cvEsXtjQ/unsubscribe.
To unsubscribe from this group and all its topics, 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/b4ebe949-5ee5-4221-b91c-ba84e21d64f4n%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/CAHtYHVLtTSA9rq-fKN%2BPaDMJazz41B1OdBVfxHxKJa%3DZ%2BRim4A%40mail.gmail.com.