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 "unknown hardware type" error, but it's worth a try. -tk On Mon, Feb 3, 2025 at 8:34 AM scott pierce <johnscottpie...@gmail.com> wrote: > *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/weewx.service; enabled; preset: > enabled) > Active: failed (Result: exit-code) since Mon 2025-02-03 11:17:57 EST; > 11min ago > Duration: 9min 1.723s > Docs: https://weewx.com/docs > Process: 1091 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, > status=4) > Main PID: 1091 (code=exited, status=4) > CPU: 474ms > > Feb 03 11:17:57 spi-1 weewxd[1091]: CRITICAL weewx.engine: **** > File "/usr/share/weewx/weewx/drivers/vantage.py", line 540, in __init__ > Feb 03 11:17:57 spi-1 weewxd[1091]: CRITICAL weewx.engine: **** > log.debug("Hardware name: %s", self.hardware_name) > Feb 03 11:17:57 spi-1 weewxd[1091]: CRITICAL weewx.engine: **** > ^^^^^^^^^^^^^^^^^^ > Feb 03 11:17:57 spi-1 weewxd[1091]: CRITICAL weewx.engine: **** > File "/usr/share/weewx/weewx/drivers/vantage.py", line 1416, in > hardware_name > Feb 03 11:17:57 spi-1 weewxd[1091]: CRITICAL weewx.engine: **** > raise weewx.UnsupportedFeature("Unknown hardware type %d" % > self.hardware_type) > Feb 03 11:17:57 spi-1 weewxd[1091]: CRITICAL weewx.engine: **** > weewx.UnsupportedFeature: Unknown hardware type 10 > Feb 03 11:17:57 spi-1 weewxd[1091]: CRITICAL __main__: Unable to load > driver: Unknown hardware type 10 > Feb 03 11:17:57 spi-1 weewxd[1091]: CRITICAL __main__: **** Exiting... > Feb 03 11:17:57 spi-1 systemd[1]: weewx.service: Main process exited, > code=exited, status=4/NOPERMISSION > Feb 03 11:17:57 spi-1 systemd[1]: weewx.service: Failed with result > 'exit-code'. > > > > On Sunday, February 2, 2025 at 11:46:26 PM UTC-5 Graham Eddy wrote: > >> 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, vince <vince...@gmail.com> wrote: >> >> All I can suggest is (a) verify which groups 'weewx' is in and (b) >> perhaps try to run weewx interactively - just run "weewxd" and it should do >> the right thing thing >> >> >> -- > 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 visit > https://groups.google.com/d/msgid/weewx-user/7130ad30-8260-446c-b676-92c76e65f813n%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/7130ad30-8260-446c-b676-92c76e65f813n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEDO6R8Q43TM_gSft8t7KqsK4fP7yxvW%3D4rdb5D%3DC9wfNw%40mail.gmail.com.
