Skip to content

v1.9.4

Latest
Latest

Choose a tag to compare

View all tags
@alepee alepee released this 29 Oct 22:48
v1.9.4
cf3fbc5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Hitachi Yutaki – Robust Modbus Reconnection Handling (v1.9.4)

Downloads for this release

A new release of the Hitachi Yutaki integration focused on improving reliability and stability when dealing with network interruptions and Modbus gateway connectivity issues.

✨ What's New?

  • Robust Modbus Reconnection Handling: The integration now gracefully handles network disconnects and automatically recovers connectivity with intelligent retry logic:
    • Automatic connection recovery with exponential backoff (up to 3 retry attempts)
    • Proper cleanup and reset of stale connections before reconnecting
    • Enhanced error handling and logging for connection attempts
    • Ensures all entities properly recover once the connection is restored after network interruptions
    • Prevents integration crashes or unexpected behavior during network outages
  • Improved Connection State Management: The Modbus client connection handling has been completely refactored using asyncio, providing more reliable connection state tracking and recovery mechanisms.
  • Better Error Recovery: Connection errors now trigger automatic connection cleanup and reset, preventing stuck states and ensuring fresh connection attempts.

🔧 Maintenance Updates

  • Development Tools:
    • Bump colorlog from 6.9.0 to 6.10.1 (#120)
    • Bump ruff from 0.13.3 to 0.14.2 (#126)
    • Bump pip requirement from <25.3,>=21.0 to >=21.0,<25.4 (#127)

📝 Important Notes

  • No breaking changes; existing setups continue to work seamlessly.
  • This release addresses connectivity issues that could occur after network interruptions or Modbus gateway disconnections.
  • The integration will now automatically retry failed connections with exponential backoff, improving resilience in unstable network environments.
  • Users experiencing reconnection problems should see significant improvements in stability.

🧪 Testing Needed

We would appreciate feedback on:

  • Connection Recovery: Verify that the integration properly recovers after temporary network interruptions (router restart, network cable unplugged/replugged, WiFi disconnection).
  • Gateway Reconnection: Test behavior when the Modbus gateway is temporarily unavailable or powered off/on.
  • Entity State Management: Confirm that all entities correctly transition to unavailable during connection failures and back to normal state once connectivity is restored.
  • Retry Behavior: Observe the retry mechanism during prolonged network outages (should retry up to 3 times with exponential backoff).

🐛 Bug Reports

If you encounter any issues, please open a GitHub issue and include:

  • Your Home Assistant version.
  • Your configuration (heat pump model, gateway type, network setup).
  • Debug-level logs showing connection attempts and retry behavior.
  • A clear description of the problem, including:
    • When the issue occurs (startup, during operation, after network interruption).
    • Duration of network interruptions before issues appear.
    • Whether entities recover correctly after connectivity is restored.
  • Network environment details (WiFi, wired, router model if relevant).

Thanks for helping improve the reliability and resilience of the Hitachi Yutaki integration!

Assets 3
Loading