Oct 03 21:49:07 Ubuntuserver weewxd[12628]: INFO weewx.engine: Using 
binding 'wx_binding' to database 'weewx.sdb'
Oct 03 21:49:07 Ubuntuserver weewxd[12628]: INFO weewx.manager: Starting 
backfill of daily summaries
Oct 03 21:49:07 Ubuntuserver weewxd[12628]: INFO weewx.manager: Daily 
summaries up to date
Oct 03 21:49:07 Ubuntuserver weewxd[12628]: DEBUG weewx.drivers.vantage: 
Getting archive packets since 2026-10-01 21:30:00 SAST (1790883000)
Oct 03 21:49:09 Ubuntuserver weewxd[12628]: DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console
Oct 03 21:49:09 Ubuntuserver weewxd[12628]: DEBUG weewx.drivers.vantage: 
Retrieving 0 page(s); starting index= 0
Oct 03 21:49:09 Ubuntuserver weewxd[12628]: INFO weewx.engine: Starting 
main packet loop.
Oct 03 21:49:09 Ubuntuserver weewxd[12628]: DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console
Oct 03 21:49:09 Ubuntuserver weewxd[12628]: DEBUG weewx.drivers.vantage: 
Requesting 200 LOOP packets.
Oct 03 21:49:10 Ubuntuserver weewxd[12628]: DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console
I started weewx and lookee here. Time to update conf file and see if it 
will  post to wunderground

On Saturday, October 3, 2026 at 9:48:35 PM UTC+2 bushtech wrote:

> HI Tom
> Thanks
> I did your point 1 and did get TEST to come back on screen. The plot 
> thickens lol.
>
> I don't suppose I need to do test two
>
> On Saturday, October 3, 2026 at 9:39:11 PM UTC+2 Tom Keffer wrote:
>
>> And no luck so far with trying the cable on a linux mint machine
>>
>>
>> Do you mean that the "TEST" test failed on a completely independent 
>> machine? If so, that's a pretty clear indication of some kind of hardware 
>> problem. 
>>
>> Focus on getting the "TEST" test to work before getting WeeWX involved. 
>> Two things to try:
>>
>> 1. Unplug the power supply and remove the batteries. This will cause the 
>> console to reset. Reinstall batteries and power supply. Reconfigure if 
>> necessary, but you will probably only have to do a long press on "DONE".  
>> Now try the "TEST" test.
>> 2. Same as #1, but this time reseat the logger while power is off. Don't 
>> remove the logger when power is applied. Try the "TEST" test.
>>
>> -tk
>>
>> On Sat, Oct 3, 2026 at 12:23 PM bushtech <[email protected]> wrote:
>>
>>> Hi Vince
>>> No. Ubuntu 26 long time already and weewx was running happily on it. 
>>> Just did an apt update/upgrade.
>>> The weewx reinstall was from this doc being followed:
>>> https://weewx.com/docs/5.5/quickstarts/debian/
>>> And modemmanager not installed
>>> And no luck so far with trying the cable on a linux mint machine
>>> On Saturday, October 3, 2026 at 9:14:35 PM UTC+2 Vince Skahan wrote:
>>>
>>>> Just to try to complete your problem description - did you go from 
>>>> ubuntu 24 to 26 ?  Sometimes major upgrades have issues.   And was it a 
>>>> clean installation or a dist-upgrade ?
>>>>
>>>> On Saturday, October 3, 2026 at 11:49:52 AM UTC-7 bushtech wrote:
>>>>
>>>>> Sat Oct  3 20:31:11 2026] usb 1-4: USB disconnect, device number 2
>>>>> [Sat Oct  3 20:31:11 2026] pl2303 ttyUSB0: pl2303 converter now 
>>>>> disconnected from ttyUSB0
>>>>> [Sat Oct  3 20:31:11 2026] pl2303 1-4:1.0: device disconnected
>>>>> [Sat Oct  3 20:31:18 2026] usb 1-4: new full-speed USB device number 8 
>>>>> using xhci_hcd
>>>>> [Sat Oct  3 20:31:19 2026] usb 1-4: New USB device found, 
>>>>> idVendor=067b, idProduct=2303, bcdDevice= 4.00
>>>>> [Sat Oct  3 20:31:19 2026] usb 1-4: New USB device strings: Mfr=1, 
>>>>> Product=2, SerialNumber=0
>>>>> [Sat Oct  3 20:31:19 2026] usb 1-4: Product: USB-Serial Controller D
>>>>> [Sat Oct  3 20:31:19 2026] usb 1-4: Manufacturer: Prolific Technology 
>>>>> Inc. 
>>>>> [Sat Oct  3 20:31:19 2026] pl2303 1-4:1.0: pl2303 converter detected
>>>>> [Sat Oct  3 20:31:19 2026] usb 1-4: pl2303 converter now attached to 
>>>>> ttyUSB0
>>>>>
>>>>> I have only ever seen ttyUSBO
>>>>>
>>>>> ps aux | grep weewxd
>>>>> dries      11036  0.0  0.0   9316  2616 pts/1    S+   20:40   0:00 
>>>>> grep --color=auto weewxd
>>>>>
>>>>> I used this: minicom -b 19200 -D /dev/ttyUSB0. Stopped weewx with sudo 
>>>>> systemctl stop weewx. But still nothing
>>>>>
>>>>> At the price of Davis stuff no I dont have a spare
>>>>> I will now remove modemmanager and try  the cable on another linux 
>>>>> machine
>>>>>
>>>>> Thanks for all the help. I really appreciate it
>>>>>
>>>>> I find it unlikely that I had a hardware failure concurrently with a 
>>>>> software update. I did do a complete reinstall of weewx yesterday
>>>>> On Saturday, October 3, 2026 at 8:33:14 PM UTC+2 Tom Keffer wrote:
>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Earlier you said that you tried the minicom test described on the 
>>>>>> wiki page. To be clear, we are talking about the test described under 
>>>>>> Establishing 
>>>>>> connectivity 
>>>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#establishing-connectivity>,
>>>>>>  
>>>>>> right? Make sure weewxd is stopped before trying the test. If the 
>>>>>> Vantage 
>>>>>> truly does not respond, then the problem lies with connectivity, and not 
>>>>>> WeeWX. You need to solve that first.
>>>>>>
>>>>>> Vince made some good suggestions. Follow them. To remove modemmanager 
>>>>>> do "sudo apt remove modemmanager".
>>>>>>
>>>>>> You said that you are using a USB to serial cable. It is possible 
>>>>>> that the driver for the serial converter changed when you upgraded. Do 
>>>>>> you 
>>>>>> have a different USB-to-serial cable that you can try? Alternatively, 
>>>>>> can 
>>>>>> you try the minicom test on another computer? 
>>>>>>
>>>>>>
>>>>>> On Sat, Oct 3, 2026 at 11:06 AM bushtech <[email protected]> wrote:
>>>>>>
>>>>>>> Hi Tom
>>>>>>> Thanks for jumping in. 
>>>>>>> I hope this is enough: 
>>>>>>>
>>>>>>> Oct 03 19:57:28 Ubuntuserver systemd[1]: Started weewx.service - 
>>>>>>> WeeWX.
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO __main__: 
>>>>>>> Initializing weewxd version 5.5.2
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO __main__: Command 
>>>>>>> line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO __main__: Using 
>>>>>>> Python: 3.14.4 (main, Aug 20 2026, 10:41:58) [GCC 15.2.0]
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO __main__: Located 
>>>>>>> at:   /usr/bin/python3
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO __main__: Platform: 
>>>>>>>     Linux-7.0.0-38-generic-x86_64-with-glibc2.43
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO __main__: Locale:   
>>>>>>>     'en_US.UTF-8'
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO __main__: Entry 
>>>>>>> path:   /usr/share/weewx/weewxd.py
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO __main__: 
>>>>>>> WEEWX_ROOT:   /etc/weewx
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO __main__: Config 
>>>>>>> file:  /etc/weewx/weewx.conf
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO __main__: User 
>>>>>>> module:  /etc/weewx/bin/user
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO __main__: Debug:   
>>>>>>>      1
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO __main__: User:     
>>>>>>>     weewx
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO __main__: Group:   
>>>>>>>      weewx
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO __main__: Groups:   
>>>>>>>     tty dialout plugdev weewx
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: DEBUG __main__: 
>>>>>>> loop_on_init: False
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: DEBUG __main__: 
>>>>>>> Initializing engine
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: INFO weewx.engine: 
>>>>>>> Loading station type Vantage (weewx.drivers.vantage)
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: DEBUG 
>>>>>>> weewx.drivers.vantage: Driver version is 3.7.0
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: DEBUG 
>>>>>>> weewx.drivers.vantage: Option loop_request=1
>>>>>>> Oct 03 19:57:28 Ubuntuserver weewxd[10160]: DEBUG 
>>>>>>> weewx.drivers.vantage: Opened up serial port /dev/ttyUSB0; baud 19200; 
>>>>>>> timeout 4.00
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: DEBUG 
>>>>>>> weewx.drivers.vantage: Successfully woke up Vantage console
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: ERROR 
>>>>>>> weewx.drivers.vantage: send_data: no <ACK> received from Vantage console
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: ERROR 
>>>>>>> weewx.drivers.vantage: _determine_hardware; retry #0: 'No <ACK> 
>>>>>>> received 
>>>>>>> from Vantage console'
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: ERROR 
>>>>>>> weewx.drivers.vantage: send_data: no <ACK> received from Vantage console
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: ERROR 
>>>>>>> weewx.drivers.vantage: _determine_hardware; retry #1: 'No <ACK> 
>>>>>>> received 
>>>>>>> from Vantage console'
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: ERROR 
>>>>>>> weewx.drivers.vantage: send_data: no <ACK> received from Vantage console
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: ERROR 
>>>>>>> weewx.drivers.vantage: _determine_hardware; retry #2: 'No <ACK> 
>>>>>>> received 
>>>>>>> from Vantage console'
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: ERROR 
>>>>>>> weewx.drivers.vantage: send_data: no <ACK> received from Vantage console
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: ERROR 
>>>>>>> weewx.drivers.vantage: _determine_hardware; retry #3: 'No <ACK> 
>>>>>>> received 
>>>>>>> from Vantage console'
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: ERROR 
>>>>>>> weewx.drivers.vantage: Unable to read hardware type. Check for 2nd 
>>>>>>> instance 
>>>>>>> of weewx. Also, try power cycli
>>>>>>> ng.
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: ERROR weewx.engine: 
>>>>>>> Import of driver failed: Unable to read hardware type. Check for 2nd 
>>>>>>> instance of weewx. Also,
>>>>>>>  try power cycling.  (<class 'weewx.WeeWxIOError'>)
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****  Traceback (most recent call last):
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****    File "/usr/share/weewx/weewx/engine.py", line 109, in 
>>>>>>> setupStation
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****      self.console = loader_function(config_dict, self)
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****                     ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 35, in 
>>>>>>> loader
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****      return VantageService(engine, config_dict)
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 2070, 
>>>>>>> in 
>>>>>>> __init__
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****      Vantage.__init__(self, **config_dict[DRIVER_NAME])
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****      ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 542, 
>>>>>>> in 
>>>>>>> __init__
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****      self._setup()
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****      ~~~~~~~~~~~^^
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 1468, 
>>>>>>> in 
>>>>>>> _setup
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****      self.hardware_type = self._determine_hardware()
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****                           ~~~~~~~~~~~~~~~~~~~~~~~~^^
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 1459, 
>>>>>>> in 
>>>>>>> _determine_har
>>>>>>> dware
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****      raise weewx.WeeWxIOError(msg)
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL weewx.engine:   
>>>>>>>   ****  weewx.WeeWxIOError: Unable to read hardware type. Check for 2nd 
>>>>>>> instance of weew
>>>>>>> x. Also, try power cycling.
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL __main__: 
>>>>>>> Unable to load driver: Unable to read hardware type. Check for 2nd 
>>>>>>> instance 
>>>>>>> of weewx. Also, tr
>>>>>>> y power cycling.
>>>>>>> Oct 03 19:57:29 Ubuntuserver weewxd[10160]: CRITICAL __main__:     
>>>>>>> ****  Exiting...
>>>>>>> Oct 03 19:57:29 Ubuntuserver systemd[1]: weewx.service: Main process 
>>>>>>> exited, code=exited, status=4/NOPERMISSION
>>>>>>> Oct 03 19:57:29 Ubuntuserver systemd[1]: weewx.service: Failed with 
>>>>>>> result 'exit-code'.
>>>>>>>
>>>>>>> On Saturday, October 3, 2026 at 7:37:21 PM UTC+2 Tom Keffer wrote:
>>>>>>>
>>>>>>>> Your little snippet shows no copies of weewxd running. What you're 
>>>>>>>> seeing is your grep command.
>>>>>>>>
>>>>>>>> Let's get  a proper log to work with. Don't use systemctl status 
>>>>>>>> weewx. It just doesn't show enough context.
>>>>>>>>
>>>>>>>> Set debug=1 in weewx.conf, restart weewxd, let it run for a 
>>>>>>>> reporting cycle (if possible), then post the log. Additional details 
>>>>>>>> on 
>>>>>>>> capturing a good log can be found here 
>>>>>>>> <https://github.com/weewx/weewx/wiki/view-logs>.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sat, Oct 3, 2026 at 9:35 AM bushtech <[email protected]> wrote:
>>>>>>>>
>>>>>>>>>  Not as far as i can see
>>>>>>>>> ps aux | grep weewxd
>>>>>>>>> dries       7716  0.0  0.0   9316  2616 pts/0    S+   18:34   0:00 
>>>>>>>>> grep --color=auto weewxd
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Saturday, October 3, 2026 at 6:22:32 PM UTC+2 Tom Keffer wrote:
>>>>>>>>>
>>>>>>>>>> Oct 03 17:03:21 Ubuntuserver weewxd[1987]: CRITICAL weewx.engine: 
>>>>>>>>>>>     ****  weewx.WeeWxIOError: Unable to read hardware type. Check 
>>>>>>>>>>> for 2nd 
>>>>>>>>>>> instance of weew>
>>>>>>>>>>> Oct 03 17:03:21 Ubuntuserver weewxd[1987]: CRITICAL __main__: 
>>>>>>>>>>> Unable to load driver: Unable to read hardware type. Check for 
>>>>>>>>>>> 2nd instance of weewx. Also, tr>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Did you check for a 2nd instance of weewx?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sat, Oct 3, 2026 at 8:21 AM bushtech <[email protected]> 
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Thanks again
>>>>>>>>>>> Running weewx status again, seem changed
>>>>>>>>>>>
>>>>>>>>>>> weewx.service - WeeWX
>>>>>>>>>>>      Loaded: loaded (/usr/lib/systemd/system/weewx.service; 
>>>>>>>>>>> enabled; preset: enabled)
>>>>>>>>>>>      Active: failed (Result: exit-code) since Sat 2026-10-03 
>>>>>>>>>>> 17:03:21 SAST; 16min ago
>>>>>>>>>>>    Duration: 6.924s
>>>>>>>>>>>  Invocation: c7dde2bbcbf74fd5bc98388f26395f8a
>>>>>>>>>>>        Docs: https://weewx.com/docs
>>>>>>>>>>>     Process: 1987 ExecStart=weewxd /etc/weewx/weewx.conf 
>>>>>>>>>>> (code=exited, status=4)
>>>>>>>>>>>    Main PID: 1987 (code=exited, status=4)
>>>>>>>>>>>    Mem peak: 24.8M
>>>>>>>>>>>         CPU: 279ms
>>>>>>>>>>> Oct 03 17:03:21 Ubuntuserver weewxd[1987]: CRITICAL 
>>>>>>>>>>> weewx.engine:     ****    File 
>>>>>>>>>>> "/usr/share/weewx/weewx/drivers/vantage.py", 
>>>>>>>>>>> line 1468, in _setup
>>>>>>>>>>> Oct 03 17:03:21 Ubuntuserver weewxd[1987]: CRITICAL 
>>>>>>>>>>> weewx.engine:     ****      self.hardware_type = 
>>>>>>>>>>> self._determine_hardware()
>>>>>>>>>>> Oct 03 17:03:21 Ubuntuserver weewxd[1987]: CRITICAL 
>>>>>>>>>>> weewx.engine:     ****                           
>>>>>>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~^^
>>>>>>>>>>> Oct 03 17:03:21 Ubuntuserver weewxd[1987]: CRITICAL 
>>>>>>>>>>> weewx.engine:     ****    File 
>>>>>>>>>>> "/usr/share/weewx/weewx/drivers/vantage.py", 
>>>>>>>>>>> line 1459, in _determine_har>
>>>>>>>>>>> Oct 03 17:03:21 Ubuntuserver weewxd[1987]: CRITICAL 
>>>>>>>>>>> weewx.engine:     ****      raise weewx.WeeWxIOError(msg)
>>>>>>>>>>> Oct 03 17:03:21 Ubuntuserver weewxd[1987]: CRITICAL 
>>>>>>>>>>> weewx.engine:     ****  weewx.WeeWxIOError: Unable to read hardware 
>>>>>>>>>>> type. 
>>>>>>>>>>> Check for 2nd instance of weew>
>>>>>>>>>>> Oct 03 17:03:21 Ubuntuserver weewxd[1987]: CRITICAL __main__: 
>>>>>>>>>>> Unable to load driver: Unable to read hardware type. Check for 2nd 
>>>>>>>>>>> instance 
>>>>>>>>>>> of weewx. Also, tr>
>>>>>>>>>>> Oct 03 17:03:21 Ubuntuserver weewxd[1987]: CRITICAL __main__:   
>>>>>>>>>>>   ****  Exiting...
>>>>>>>>>>> Oct 03 17:03:21 Ubuntuserver systemd[1]: weewx.service: Main 
>>>>>>>>>>> process exited, code=exited, status=4/NOPERMISSION
>>>>>>>>>>> Oct 03 17:03:21 Ubuntuserver systemd[1]: weewx.service: Failed 
>>>>>>>>>>> with result 'exit-code'.
>>>>>>>>>>> lines 1-21/21 (END)
>>>>>>>>>>>
>>>>>>>>>>> Now complaining about vantage.py
>>>>>>>>>>>
>>>>>>>>>>> Here is line 1468
>>>>>>>>>>> 1468             self.hardware_type = self._determine_hardware()
>>>>>>>>>>> and line 1459: 
>>>>>>>>>>> 1459         raise weewx.WeeWxIOError(msg)
>>>>>>>>>>> This was listed with nano -l
>>>>>>>>>>> Doesnt mean much to me
>>>>>>>>>>> On Saturday, October 3, 2026 at 3:59:42 PM UTC+2 John Smith 
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Start with the simple stuff, reconnect everything and check 
>>>>>>>>>>>> dmesg to see if everything is detected properly when reconnected.
>>>>>>>>>>>>
>>>>>>>>>>>> I assume everything was working up until you installed the new 
>>>>>>>>>>>> Ubuntu version, so it could be a bug/issue in the new kernel, so 
>>>>>>>>>>>> maybe try 
>>>>>>>>>>>> downgrading the kernel and/or trying a back ported version if 
>>>>>>>>>>>> there is one.
>>>>>>>>>>>>
>>>>>>>>>>>> It could also be a cable issue, do you have a space to try?
>>>>>>>>>>>>
>>>>>>>>>>>> On Sat, 3 Oct 2026 at 23:16, bushtech <[email protected]> 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks again John
>>>>>>>>>>>>> No reply out of the minicom or screen test
>>>>>>>>>>>>> Hmmm
>>>>>>>>>>>>> On Saturday, October 3, 2026 at 2:59:42 PM UTC+2 John Smith 
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Ok, weewxd now owned by user weewx, was root.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Has been since version 5.0.0 came out
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>  Oct 03 14:23:52 Ubuntuserver weewxd[1986]: ERROR 
>>>>>>>>>>>>>>> weewx.drivers.vantage: send_data: no <ACK> received from 
>>>>>>>>>>>>>>> Vantage cons
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> There is a wiki page for that too 
>>>>>>>>>>>>>> https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sat, 3 Oct 2026 at 22:50, bushtech <[email protected]> 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi John
>>>>>>>>>>>>>>> Thanks a mil for your response.  Ok, weewxd now owned by 
>>>>>>>>>>>>>>> user weewx, was root. And did this: sudo usermod -aG dialout 
>>>>>>>>>>>>>>> weewx to try 
>>>>>>>>>>>>>>> and sort out the USB. No discernable difference noted
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Then ran:  sudo journalctl -u weewx -n 50 --no-pager
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Oct 03 14:23:52 Ubuntuserver weewxd[1986]: DEBUG 
>>>>>>>>>>>>>>> weewx.drivers.vantage: Successfully woke up Vantage console
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Oct 03 14:23:52 Ubuntuserver weewxd[1986]: ERROR 
>>>>>>>>>>>>>>> weewx.drivers.vantage: send_data: no <ACK> received from 
>>>>>>>>>>>>>>> Vantage cons
>>>>>>>>>>>>>>> The second line is where the wheels came off.
>>>>>>>>>>>>>>> Hmmm, lots of head scratching currently
>>>>>>>>>>>>>>> On Saturday, October 3, 2026 at 1:34:20 PM UTC+2 John Smith 
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> status=4/NOPERMISSION
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> That pretty much says it all, weewxd doesn't have 
>>>>>>>>>>>>>>>> permission to access the USB device.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Have you looked at this page? 
>>>>>>>>>>>>>>>> https://github.com/weewx/weewx/wiki/Understanding-permissions
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> It has a section on USB permissions
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sat, 3 Oct 2026 at 18:14, bushtech <[email protected]> 
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi
>>>>>>>>>>>>>>>>> Conf. file 5.5.2
>>>>>>>>>>>>>>>>> Davis Vantage pro using USB to serial cable
>>>>>>>>>>>>>>>>> During ubuntu update got the usual conf file out of date 
>>>>>>>>>>>>>>>>> so kept old one. But afterwards
>>>>>>>>>>>>>>>>> decided to use later conf. file.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> What worries me is Ubuntu 26 uses python 3.14.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The weewx documentation says this:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> *"Python*
>>>>>>>>>>>>>>>>> Python 2.7, or Python 3.5 or later is required."
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Am I between a rock and a hard place or am I being stupid
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> This is what I get when doing sudo systemctl status weewx:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Oct 02 16:05:12 Ubuntuserver weewxd[19832]: CRITICAL 
>>>>>>>>>>>>>>>>> weewx.engine: **** File "/usr/share/weewx/weewx/drivers/v> 
>>>>>>>>>>>>>>>>> Oct 02 16:05:12 
>>>>>>>>>>>>>>>>> Ubuntuserver weewxd[19832]: CRITICAL weewx.engine: **** 
>>>>>>>>>>>>>>>>> self.hardware_type 
>>>>>>>>>>>>>>>>> = self._determine> Oct 02 16:05:12 Ubuntuserver 
>>>>>>>>>>>>>>>>> weewxd[19832]: CRITICAL 
>>>>>>>>>>>>>>>>> weewx.engine: **** ~~~~~~~~~~~~~~~> Oct 02 16:05:12 
>>>>>>>>>>>>>>>>> Ubuntuserver 
>>>>>>>>>>>>>>>>> weewxd[19832]: CRITICAL weewx.engine: **** File 
>>>>>>>>>>>>>>>>> "/usr/share/weewx/weewx/drivers/v> Oct 02 16:05:12 
>>>>>>>>>>>>>>>>> Ubuntuserver 
>>>>>>>>>>>>>>>>> weewxd[19832]: CRITICAL weewx.engine: **** raise 
>>>>>>>>>>>>>>>>> weewx.WeeWxIOError(msg) Oct 02 16:05:12 Ubuntuserver 
>>>>>>>>>>>>>>>>> weewxd[19832]: 
>>>>>>>>>>>>>>>>> CRITICAL weewx.engine: **** weewx.WeeWxIOError: Unable to 
>>>>>>>>>>>>>>>>> read hardw> Oct 
>>>>>>>>>>>>>>>>> 02 16:05:12 Ubuntuserver weewxd[19832]: CRITICAL *main*: 
>>>>>>>>>>>>>>>>> Unable to load driver: Unable to read hardware type. C> Oct 
>>>>>>>>>>>>>>>>> 02 16:05:12 
>>>>>>>>>>>>>>>>> Ubuntuserver weewxd[19832]: CRITICAL *main*: **** 
>>>>>>>>>>>>>>>>> Exiting... Oct 02 16:05:12 Ubuntuserver systemd[1]: 
>>>>>>>>>>>>>>>>> weewx.service: Main 
>>>>>>>>>>>>>>>>> process exited, code=exited, status=4/NOPERMISSION Oct 02 
>>>>>>>>>>>>>>>>> 16:05:12 
>>>>>>>>>>>>>>>>> Ubuntuserver systemd[1]: weewx.service: Failed with result 
>>>>>>>>>>>>>>>>> 'exit-code'.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Please tell me what is gong on here. Is this a hardware 
>>>>>>>>>>>>>>>>> problem now Am I missing something stupid
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>>>>> 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 [email protected].
>>>>>>>>>>>>>>>>> To view this discussion visit 
>>>>>>>>>>>>>>>>> https://groups.google.com/d/msgid/weewx-user/317e81b0-ee8b-43c5-98fb-e4168c00d7ddn%40googlegroups.com
>>>>>>>>>>>>>>>>>  
>>>>>>>>>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/317e81b0-ee8b-43c5-98fb-e4168c00d7ddn%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 [email protected].
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> To view this discussion visit 
>>>>>>>>>>>>>>> https://groups.google.com/d/msgid/weewx-user/3c4d4e1a-aaaa-437f-baaf-17f7142e4bc8n%40googlegroups.com
>>>>>>>>>>>>>>>  
>>>>>>>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/3c4d4e1a-aaaa-437f-baaf-17f7142e4bc8n%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 [email protected].
>>>>>>>>>>>>>
>>>>>>>>>>>> To view this discussion visit 
>>>>>>>>>>>>> https://groups.google.com/d/msgid/weewx-user/087f9cbc-59f9-42f2-b363-99e8b3d6e51bn%40googlegroups.com
>>>>>>>>>>>>>  
>>>>>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/087f9cbc-59f9-42f2-b363-99e8b3d6e51bn%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 [email protected].
>>>>>>>>>>>
>>>>>>>>>> To view this discussion visit 
>>>>>>>>>>> https://groups.google.com/d/msgid/weewx-user/26388e09-f76c-4222-9a76-7ea6a344f699n%40googlegroups.com
>>>>>>>>>>>  
>>>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/26388e09-f76c-4222-9a76-7ea6a344f699n%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 [email protected].
>>>>>>>>>
>>>>>>>> To view this discussion visit 
>>>>>>>>> https://groups.google.com/d/msgid/weewx-user/baa86cce-632e-4dc9-90ed-47fdf9023264n%40googlegroups.com
>>>>>>>>>  
>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/baa86cce-632e-4dc9-90ed-47fdf9023264n%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 [email protected].
>>>>>>>
>>>>>> To view this discussion visit 
>>>>>>> https://groups.google.com/d/msgid/weewx-user/548dd6cd-eb68-45ef-8ea4-a60e616c3563n%40googlegroups.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/weewx-user/548dd6cd-eb68-45ef-8ea4-a60e616c3563n%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 [email protected].
>>>
>> To view this discussion visit 
>>> https://groups.google.com/d/msgid/weewx-user/23db7661-2ebf-4dde-abae-c484074e1541n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/23db7661-2ebf-4dde-abae-c484074e1541n%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 [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/weewx-user/ca60efef-9e77-4028-9ef1-68fba3a0705en%40googlegroups.com.

Reply via email to