Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-03 Thread vince
Worth a try. I do like the "ls -l /dev | grep USB" command to better see what's what in /dev given that it looked like he has a USB keyboard and mouse plugged in. On Monday, February 3, 2025 at 12:14:41 PM UTC-8 Warren Gill wrote: > The system install should have put a udev rule in place. This

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-03 Thread Warren Gill
The system install should have put a udev rule in place. This causes the kernel to create an alias to the device whenever it detects it plugging in (or at boot). Because if you have more than one serial device the envoy could get a different device name (ttyUSB1, ttyUSB3, etc.) every time it plugs

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-03 Thread vince
ok - lets go back to the beginning. Is weewx getting data from your station and continuing to run other than these messages, or is it not ? In other words do we have something breaking it from working, or is this just an annoyance in the logging/reporting stuff ? If it's working - you 'cou

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-03 Thread scott pierce
This is getting a tad frustrating! On Monday, February 3, 2025 at 12:37:32 PM UTC-5 Tom Keffer wrote: > Now you're back to a permissions error. > > On Mon, Feb 3, 2025 at 9:26 AM scott pierce wrote: > >> *Doesn't look like it worked.* >> >> × weewx.service - WeeWX >> Loaded: loaded (/lib/s

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-03 Thread Tom Keffer
Now you're back to a permissions error. On Mon, Feb 3, 2025 at 9:26 AM scott pierce wrote: > *Doesn't look like it worked.* > > × weewx.service - WeeWX > Loaded: loaded (/lib/systemd/system/weewx.service; enabled; preset: > enabled) > Active: failed (Result: exit-code) since Mon 2025-0

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-03 Thread scott pierce
*Doesn't look like it worked.* × weewx.service - WeeWX Loaded: loaded (/lib/systemd/system/weewx.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Mon 2025-02-03 12:18:41 EST; 5min ago Duration: 5min 21.472s Docs: https://weewx.com/docs Process:

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-03 Thread Tom Keffer
There have been a few other incidents of "Unknown hardware type 10". The solution seems to be to clear the logger. Try this procedure: weectl device --dump weectl device --clear-memory The "--dump" command will attempt to salvage any data on the logger. It will probably fail because of the "unk

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-03 Thread scott pierce
*Yep, WeeWx is already a member of that group. Here is the latest systems status I just ran. Seems the unknown hardware issue is still there. * *Is there another log or status that I can run that will provide more/complete information?* *Thanks* *Scott* Loaded: loaded (/lib/systemd/system

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread Graham Eddy
weewx is reporting permission error. it seems to be using /dev/ttyUSB0 ➔ check perms on that file: $ ls -l /dev/ttyUSB0 it will probably show group ‘dialout’ has read/write on it, so make sure user ‘weewx’ is in that group e.g. $ sudo adduser weewx dialout ⊣GE⊢ > On 3 Feb 2025, at 1:36 pm, v

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread vince
Sure looks like /dev/ttyUSB0 to me. Lets eliminate group membership - give https://github.com/weewx/weewx/wiki/Understanding-permissions#more-details-about-which-groups-can-do-what a quick read and note the mention of group 'dialout' being the typical one needed for accessing USB devices. Usi

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread scott pierce
[3.419141] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.419150] Bluetooth: BNEP filters: protocol multicast [3.419158] Bluetooth: BNEP socket layer initialized [3.448003] Adding 524272k swap on /var/swap. Priority:-2 extents:8 across:2228224k SS [3.608444] macb 1f0010.e

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread vince
Do the unplug plugin test and show ‘sudo dmesg’ please On Sunday, February 2, 2025 at 4:15:01 PM UTC-8 scott pierce wrote: > scott@spi-1:/etc/weewx $ sudo lsusb > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 003: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread scott pierce
scott@spi-1:/etc/weewx $ sudo lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (model 1576) Bus 003 Device 002: ID 046d:c077 Logitech, Inc. Mouse Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub B

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread vince
Sure it could, try “lsusb” to list the usb devices found. You might need to preface it with sudo. Alternately unplug it, wait a couple seconds, plug it back in and run “sudo dmesg” to see kernel messages that usually have enough info to figure it out. On Sunday, February 2, 2025 at 4:01:50 PM

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread scott pierce
Ran the journal log and it produced this: Feb 01 16:48:38 scott systemd[1]: Started weewx.service - WeeWX. Feb 01 16:48:38 scott weewxd[3395]: INFO __main__: Initializing weewxd version 5.1.0 Feb 01 16:48:38 scott weewxd[3395]: INFO __main__: Command line: /usr/share/weewx/weewxd.py /etc/weewx/w

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread scott pierce
Here is what I have: scott@spi-1:~ $ groups scott adm dialout cdrom sudo audio video plugdev games users input render netdev lpadmin weewx gpio i2c spi scott@spi-1:~ $ and scott@spi-1:~ $ groups weewx weewx : weewx On Sunday, February 2, 2025 at 4:10:06 PM UTC-5 vince wrote: > weewx.service:

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread vince
weewx.service: Main process exited, code=exited, status=4/NOPERMISSION generally means the user running the command is not in the required unix groups, which can be a little tricky to get right especially as a new linuc user. Try ‘groups’ to see which groups your account is in, and ‘groups weew

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread scott pierce
*and here are the results when I run weectl device...still showing an unknown hardware issue:* @-1:~ $ weectl device Using configuration file /etc/weewx/weewx.conf Using driver weewx.drivers.vantage. Using Vantage driver version 3.6.2 (weewx.drivers.vantage) Unable to wake up console... sleeping

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread scott pierce
*Here is the info that came through after running weectl debug:* System info Platform: Linux-6.6.74+rpt-rpi-2712-aarch64-with-glibc2.36 Python Version: 3.11.2 Load Information 1 minute load average: 0.00 5 minute load average: 0.04 15 minute load average: 0.13 Ge

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread scott pierce
Yes, big rookie mistake. Working through it now. Thanks for pointing out!! Scott On Sunday, February 2, 2025 at 2:37:45 PM UTC-5 michael.k...@gmx.at wrote: > Maybe you missed that you refer to a 4.9 version of the docs, but you've > installed a 5.1 version? > https://weewx.com/docs/5.1/usersg

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread 'michael.k...@gmx.at' via weewx-user
Maybe you missed that you refer to a 4.9 version of the docs, but you've installed a 5.1 version? https://weewx.com/docs/5.1/usersguide/where/?h=find#where-to-find-things scott pierce schrieb am Sonntag, 2. Februar 2025 um 20:33:42 UTC+1: > *Alsowhere are the executables? In the documentati

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread scott pierce
*Alsowhere are the executables? In the documentation it says:* This is a reference guide to the executable utilities that come with WeeWX: - wee_config for changing the configuration file, and configuring new device dri

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-02 Thread scott pierce
Hi, I was able to update the confi file and change the Debug to 1...which in itself is a huge win as it took me a while to figure out how to even access the file. (permissions have been a bear to learn). I have read a lot in the last 24 hours! That said, I still don't know how to access any add

Re: [weewx-user] First Day with WeeWX Some Good, but...

2025-02-01 Thread 'John Kline' via weewx-user
If you set debug = 1 and restart weewx, we’ll get to see the hardware_type read from the envoy.The line in the log will contain “Hardware type is “On Feb 1, 2025, at 6:34 PM, scott pierce wrote:Successfully installed WeeWX on Rpi 5 and it's ingesting data from Davis Envoy USB Weather Link data lo

[weewx-user] First Day with WeeWX Some Good, but...

2025-02-01 Thread scott pierce
Successfully installed WeeWX on Rpi 5 and it's ingesting data from Davis Envoy USB Weather Link data logger. Also, I have been able to view reports...so that's nice. I'm just beginning this journey so still a lot to learn and set up. One quick question I can't find an answer to in the group or i