v1.2.13-beta.4

Release v1.2.13-beta.4

Release Date: 2026-02-25

Type: Beta release - Upgrades ModbusLink to v1.5.1 with separate connection timeout.

What's Changed (since v1.2.13-beta.3)

Changed

• Upgraded ModbusLink from v1.4.2 to v1.5.1 - The upstream library now supports a
  separate connection_timeout parameter for TCP connection establishment. Previously,
  the single timeout value (default 10s, user-configurable 5-60s) covered both TCP
  connection and Modbus data operations. Now:

  • Connection timeout: 5 seconds (fixed) - How long to wait when establishing the
    TCP connection to the Alfa device. A LAN device should respond in milliseconds;
    5 seconds is generous and catches unreachable devices faster.
  • Data timeout: User-configurable (default 10s) - How long to wait for Modbus
    read/write responses. This remains unchanged.

• All upstream ModbusLink issues resolved - The 4 issues we were tracking (#3-#6) are
  all closed. Only #6 (connection_timeout) was applicable to our integration. The others
  are not applicable: #3 (individual register reads less efficient than our batch approach),
  #4 (Alfa device doesn't support parallel connections), #5 (RTU/ASCII flush not applicable,
  we use TCP).

Technical Details

• Files changed: manifest.json (dependency version), const.py (+1 constant),
  api.py (+1 parameter), CLAUDE.md (upstream issues + dependencies)
• No user-facing configuration changes - The connection timeout is an internal
  optimization, not exposed in the UI
• Backward compatible - ModbusLink 1.5.1 defaults connection_timeout to None
  (falls back to timeout), so existing behavior is preserved for other users of the library

Testing Focus

After deploying this update:

1. Connection behavior: Verify Modbus connection still establishes normally on restart.
2. Error detection: If you can temporarily set an invalid IP in the reconfigure flow,
   verify the connection error appears within ~5 seconds instead of the full data timeout.
3. Data polling: Verify sensor data continues updating at the configured scan interval.

Full Changelog:
compare/v1.2.13-beta.3...v1.2.13-beta.4