No AI, please. Just the log.

On Mon, Jan 26, 2026 at 7:10β€―AM killic <[email protected]> wrote:

> πŸ“‹ WeatherLink IP Error Log Summary
>
> *Device Information:*
>
>    - WeatherLink IP: 192.168.2.161
>    - Firmware: 115
>    - Hardware: 111
>    - TCP Port: 22222
>
> *Software Environment:*
>
>    - WeeWX Version: 5.2.0
>    - Python: 3.13.5
>    - OS: Raspberry Pi OS (Debian, Linux 6.12.62)
>    - Driver: weewx.drivers.vantage
>
> ------------------------------
> πŸ”΄ Main Errors 1. Connection Established but Protocol Fails
> Connection to 192.168.2.161 22222 port [tcp/*] succeeded!
>
> βœ… TCP connection works (verified with netcat) ❌ Vantage protocol
> communication fails immediately
> 2. Wake-Up Command Failures
> ERROR weewx.drivers.vantage: ip-write error: [Errno 32] Broken pipe ERROR
> weewx.drivers.vantage: Unable to wake up Vantage console ERROR
> weewx.drivers.vantage: ip-read error: [Errno 104] Connection reset by peer
>
> The device does not respond to wake-up commands and immediately closes the
> connection.
> 3. EEPROM Read Failures
> ERROR weewx.drivers.vantage: While getting EEPROM data value at address
> 0x2D weewx.RetriesExceeded: While getting EEPROM data value at address 0x2D
>
> Cannot read station configuration from EEPROM memory.
> 4. LOOP Data Request Failures
> ERROR weewx.drivers.vantage: LOOP batch try #1; error: timed out ERROR
> weewx.drivers.vantage: LOOP batch try #2; error: Unable to wake up Vantage
> console ERROR weewx.drivers.vantage: LOOP batch try #3; error: Unable to
> wake up Vantage console ERROR weewx.drivers.vantage: LOOP max batch errors
> (3) exceeded.
>
> Device does not provide continuous LOOP data packets.
> 5. Archive Download Behavior
>
> When loop_on_init = False (default):
> INFO weewx.manager: Added record 2025-12-28 09:45:00 CET to database
> 'weewx.sdb' INFO weewx.manager: Added record 2025-12-28 10:00:00 CET to
> database 'weewx.sdb' [...continues loading archives...] ERROR
> weewx.drivers.vantage: DMPAFT max tries (5) exceeded. CRITICAL __main__:
> Caught WeeWxIOError: Max tries exceeded while getting archive data.
>
> βœ… Device successfully sends historical archive data ❌ After sending
> archives, device stops responding and disconnects
> ------------------------------
> πŸ§ͺ Tests Performed
>
>    1. *Network Connectivity:* βœ… PASS
>       - TCP connection successful (netcat test)
>       - Port 22222 accessible
>       - No firewall blocking
>    2. *Multiple Systems Tested:*
>       - Proxmox LXC container: Same errors
>       - Raspberry Pi 4 (physical): Same errors
>       - *Conclusion:* Not a virtualization or system issue
>    3. *Configuration Options Tested:*
>       - Default settings: Fails after archive download
>       - loop_on_init = True: Still fails on wake-up
>       - catchup_on_restart = False: Device still disconnects
>       - *Conclusion:* Configuration changes don't resolve the issue
>    4. *Network Equipment:*
>       - UniFi network tested
>       - No client isolation
>       - No IDS/IPS blocking detected
>       - *Conclusion:* Not a network equipment issue
>
> ------------------------------
> πŸ“Š Typical Error Sequence
>
>    1. WeeWX connects to 192.168.2.161:22222 βœ…
>    2. Attempts to wake up console ❌
>
> ERROR: ip-write error: [Errno 32] Broken pipe ERROR: Unable to wake up
> Vantage console
>
>    3. Connection terminates immediately
>    4. WeeWX retries and fails repeatedly
>    5. Service crashes after max retries exceeded
>
> ------------------------------
> πŸ’‘ Observations
>
>    - *WeatherLink.com uploads work perfectly* - Device successfully sends
>    data to Davis cloud
>    - *Local Vantage protocol fails completely* - Device refuses protocol
>    communication
>    - *Behavior is consistent* - Same errors across different systems and
>    configurations
>    - *TCP layer works* - Only protocol layer fails
>
> ------------------------------
> ❓ Questions for Support
>
>    1. Is there a firmware bug affecting local Vantage protocol
>    communication?
>    2. Should the WeatherLink IP respond to wake-up commands?
>    3. Is there a way to factory reset the device?
>    4. Could this be a hardware failure requiring RMA?
>
> Le lundi 26 janvier 2026 Γ  16:06:11 UTC+1, Tom Keffer a Γ©crit :
>
>> Hard to say without seeing the log. See the wiki section *How to produce
>> a useful log
>> <https://github.com/weewx/weewx/wiki/view-logs#how-to-produce-a-useful-log-report>*
>> .
>>
>> -tk
>>
>> On Mon, Jan 26, 2026 at 7:01β€―AM killic <[email protected]> wrote:
>>
>>> Hello,
>>>
>>> My WeatherLink IP accepts TCP connections on port 22222 but does not
>>> respond correctly to the Vantage protocol:
>>>
>>>    - Errors: "Unable to wake up console"
>>>    - Errors: "Broken pipe" during communication attempts
>>>    - Unable to read EEPROM at address 0x2D
>>>    - Device does not transmit continuous LOOP data
>>>
>>> *Current firmware:* 115
>>> *Hardware version:* 111
>>>
>>> The device successfully sends historical archive data when WeeWX first
>>> connects, but then stops communicating and disconnects. I've tested with
>>> both a Proxmox LXC container and a Raspberry Pi 4, with the same results.
>>> The TCP connection is established successfully (verified with netcat), but
>>> the Vantage protocol communication fails.
>>>
>>> I've tried:
>>>
>>>    - Restarting the WeatherLink IP (power cycle)
>>>    - Testing from different systems (LXC container and Raspberry Pi)
>>>    - Verifying network connectivity (TCP port 22222 is accessible)
>>>    - Using WeeWX 5.2.0 with the standard Vantage driver
>>>
>>> The WeatherLink IP continues to upload data to WeatherLink.com
>>> successfully, but local connectivity via the Vantage protocol does not work.
>>>
>>> Can you help me resolve this issue?
>>>
>>> Thank you,
>>>
>>>
>>>
>>> *Additional testing:*
>>>
>>>    - Tried with loop_on_init = True to skip archive download
>>>    - Result: Still "Unable to wake up console" and "Connection reset by
>>>    peer"
>>>    - The device refuses even the basic wake-up command
>>>    - TCP connection works (verified with netcat) but protocol
>>>    communication fails immediately
>>>
>>> --
>>> 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/4151b8f8-021a-41f3-92e4-9f8500118f8an%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/4151b8f8-021a-41f3-92e4-9f8500118f8an%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/f39ec875-7d9b-4b73-a9f6-4d726295af7cn%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/f39ec875-7d9b-4b73-a9f6-4d726295af7cn%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/CAPq0zECOOMehrh-jiT-S9GUsrzKgELNY%3DyiwrwwisR0aDUTScQ%40mail.gmail.com.

Reply via email to