jontofront/ecoNET-300-Home-Assistant-Integration v1.3.6-beta.2

on GitHub

Pre-release for testing. Install it only if you want to help test. Stable 1.3.6 follows after testing. If something goes wrong, go back to v1.3.5 in HACS (⋮ → Redownload → v1.3.5).

Everything from v1.3.6-beta.1, plus a quieter log.

What's new

🔇 Quiet log when the device is offline (new in beta.2)

When the ecoNET300 module did not answer, for example after a power cut or a network problem, the log got an error every 15 seconds, such as API error: sysParams endpoint returned no usable data, plus several Timeout error, retry warnings (#255).

Now, as Home Assistant recommends, the log shows only two lines:

• Device <host> is unavailable: <reason> when the module stops answering;
• Device <host> is available again after <N> failed updates when it answers again.

Nothing else changes: entities keep their last values for 10 minutes and then become Unavailable, and after 5 failed updates Repairs still shows Connection to ecoNET300 device failed.

The module also sometimes sends an answer without data. The integration now asks once more after 1 second, so such a hiccup no longer counts as the device being offline.

🔐 Ready for aiohttp 4.0

ecoNET300 logged in to your module with a part of the aiohttp library that will be removed in aiohttp 4.0 (#267). Now the integration builds the login itself. The module receives exactly the same login data as before, so nothing changes for you.

Small changes

• Service authentication successful is no longer written to the log on every update.
• Unused code was removed from the part of the integration that talks to the module.
• Documentation checks now use the project settings (#268).

After updating

No reinstall or reconfiguration is needed. Restart Home Assistant after the update. Device names, entity IDs and history stay the same.

Please test

• The integration connects after a restart, and sensors update as before.
• Changing a setting (for example a number or switch) still works.
• No Unauthorized access or invalid_auth in the log.
• If the controller has a service password, the service parameters are still available.
• Unplug the ecoNET300 module (or its network cable) for a minute: the log shows one Device ... is unavailable line instead of repeated errors, and one Device ... is available again line after you plug it back in.

Please report the results in #270.

Full changelog: v1.3.5...v1.3.6-beta.2