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/usersguide/where/?h=find#where-to-find-things
>
> scott pierce schrieb am Sonntag, 2. Februar 2025 um 20:33:42 UTC+1:
>
>> *Also....where are the executables?  In the documentation it says:*
>>
>> This is a reference guide to the executable utilities that come with 
>> WeeWX:
>>
>>    - wee_config 
>>    <https://weewx.com/docs/4.9/utilities.htm#wee_config_utility> for 
>>    changing the configuration file, and configuring new device drivers;
>>    - wee_database 
>>    <https://weewx.com/docs/4.9/utilities.htm#wee_database_utility> for 
>>    reconfiguring the database;
>>    - wee_debug 
>>    <https://weewx.com/docs/4.9/utilities.htm#wee_debug_utility> for 
>>    producing debug reports for remote support;
>>    - wee_device 
>>    <https://weewx.com/docs/4.9/utilities.htm#wee_device_utility> for 
>>    configuring your hardware;
>>    - wee_extension 
>>    <https://weewx.com/docs/4.9/utilities.htm#wee_extension_utility> for 
>>    installing and removing extensions;
>>    - wee_import 
>>    <https://weewx.com/docs/4.9/utilities.htm#wee_import_utility> for 
>>    importing historical data from external sources;
>>    - wee_reports 
>>    <https://weewx.com/docs/4.9/utilities.htm#wee_reports_utility> for 
>>    running reports without running WeeWX itself;
>>    - weewxd <https://weewx.com/docs/4.9/utilities.htm#weewxd> the main 
>>    weewx program;
>>    - wunderfixer 
>>    <https://weewx.com/docs/4.9/utilities.htm#wunderfixer_utility> for 
>>    resending data missing on the Weather Underground site.
>>
>>
>> *And then to find them....*
>>
>> Location of WeeWX components¶ 
>> <https://weewx.com/docs/5.0/usersguide/where/#location-of-weewx-components>
>>
>>
>> Executables*BIN_ROOT*/usr/share/weewx/
>>
>>
>>
>> *But when I look in that directory....*
>>
>> @spi-1:/usr/share/weewx $ ls
>> __pycache__  weecfg     weectl.py  weeimport  weeutil  weewx_data
>> schemas      weectllib  weedb      weeplot    weewx    weewxd.py
>> @spi-1:/usr/share/weewx $ 
>>
>> *None of them show up.  What am I missing?*
>>
>> *Thanks*
>> *Scott*
>>
>>
>> On Sunday, February 2, 2025 at 12:03:03 PM UTC-5 scott pierce wrote:
>>
>>> 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 additional log 
>>> information.  When I run the status check, it comes back with basically the 
>>> same info...
>>> × weewx.service - WeeWX
>>>      Loaded: loaded (/lib/systemd/system/weewx.service; enabled; preset: 
>>> enabled)
>>>      Active: failed (Result: exit-code) since Sun 2025-02-02 11:35:11 
>>> EST; 23min ago
>>>    Duration: 18min 49.054s
>>>        Docs: https://weewx.com/docs
>>>     Process: 1261 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
>>> status=4)
>>>    Main PID: 1261 (code=exited, status=4)
>>>         CPU: 873ms
>>>
>>> Feb 02 11:35:11 spi-1 weewxd[1261]: CRITICAL weewx.engine:     ****   
>>>  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1444, in _setup
>>> Feb 02 11:35:11 spi-1 weewxd[1261]: CRITICAL weewx.engine:     ****     
>>>  self.hardware_type = self._determine_hardware()
>>> Feb 02 11:35:11 spi-1 weewxd[1261]: CRITICAL weewx.engine:     ****     
>>>                       ^^^^^^^^^^^^^^^^^^^^^^^^^^
>>> Feb 02 11:35:11 spi-1 weewxd[1261]: CRITICAL weewx.engine:     ****   
>>>  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1435, in 
>>> _determine_hardware
>>> Feb 02 11:35:11 spi-1 weewxd[1261]: CRITICAL weewx.engine:     ****     
>>>  raise weewx.WeeWxIOError("Unable to read hardware type")
>>> Feb 02 11:35:11 spi-1 weewxd[1261]: CRITICAL weewx.engine:     **** 
>>>  weewx.WeeWxIOError: Unable to read hardware type
>>> Feb 02 11:35:11 spi-1 weewxd[1261]: CRITICAL __main__: Unable to load 
>>> driver: Unable to read hardware type
>>> Feb 02 11:35:11 spi-1 weewxd[1261]: CRITICAL __main__:     **** 
>>>  Exiting...
>>> Feb 02 11:35:11 spi-1 systemd[1]: weewx.service: Main process exited, 
>>> code=exited, status=4/NOPERMISSION
>>> Feb 02 11:35:11 spi-1 systemd[1]: weewx.service: Failed with result 
>>> 'exit-code'.
>>> ~
>>>
>>> Thanks
>>> Scott
>>> On Saturday, February 1, 2025 at 10:51:51 PM UTC-5 John Kline wrote:
>>>
>>>> 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 <johnsco...@gmail.com> wrote:
>>>>
>>>> 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 in notes...
>>>> when I run a status check this is the result...
>>>> × weewx.service - WeeWX
>>>>      Loaded: loaded (/lib/systemd/system/weewx.service; enabled; 
>>>> preset: enabled)
>>>>      Active: failed (Result: exit-code) since Sat 2025-02-01 21:18:12 
>>>> EST; 7min ago
>>>>    Duration: 35min 33.415s
>>>>        Docs: https://weewx.com/docs
>>>>     Process: 6313 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
>>>> status=4)
>>>>    Main PID: 6313 (code=exited, status=4)
>>>>         CPU: 2.339s
>>>>
>>>> Feb 01 21:18:12 spi-1 weewxd[6313]: CRITICAL weewx.engine:     ****     
>>>>  log.debug("Hardware name: %s", self.hardware_name)
>>>> Feb 01 21:18:12 spi-1 weewxd[6313]: CRITICAL weewx.engine:     ****     
>>>>                                 ^^^^^^^^^^^^^^^^^^
>>>> Feb 01 21:18:12 spi-1 weewxd[6313]: CRITICAL weewx.engine:     ****   
>>>>  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1416, in 
>>>> hardware_name
>>>> Feb 01 21:18:12 spi-1 weewxd[6313]: CRITICAL weewx.engine:     ****     
>>>>  raise weewx.UnsupportedFeature("Unknown hardware type %d" % 
>>>> self.hardware_type)
>>>> Feb 01 21:18:12 spi-1 weewxd[6313]: CRITICAL weewx.engine:     **** 
>>>>  weewx.UnsupportedFeature: Unknown hardware type 10
>>>> Feb 01 21:18:12 spi-1 weewxd[6313]: CRITICAL __main__: Unable to load 
>>>> driver: Unknown hardware type 10
>>>> Feb 01 21:18:12 spi-1 weewxd[6313]: CRITICAL __main__:     **** 
>>>>  Exiting...
>>>> Feb 01 21:18:12 spi-1 systemd[1]: weewx.service: Main process exited, 
>>>> code=exited, status=4/NOPERMISSION
>>>> Feb 01 21:18:12 spi-1 systemd[1]: weewx.service: Failed with result 
>>>> 'exit-code'.
>>>> Feb 01 21:18:12 spi-1 systemd[1]: weewx.service: Consumed 2.339s CPU 
>>>> time.
>>>>
>>>> I'm guessing I put the hardware name in wrong in setup...not sure.  
>>>> Also don't know where to look to check.
>>>> Any suggestions are appreciated.
>>>> Thanks
>>>> Scott
>>>>
>>>> -- 
>>>> 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 visit 
>>>> https://groups.google.com/d/msgid/weewx-user/b5df5db2-394b-4467-8c33-f50631f7f65dn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/b5df5db2-394b-4467-8c33-f50631f7f65dn%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/c5883c80-f4b4-4c91-b2e3-cecb26c4b444n%40googlegroups.com.

Reply via email to