The integration now uploads its client certificate to the UPS automatically, so the manual import in the card's web interface is usually no longer needed.
Changes
- Automatic certificate upload (#134): during setup, reauth and reconfigure, the integration checks whether the Network-M2/M3 card trusts its client certificate and uploads it if not. The card accepts the upload while Pairing with clients is started in its web interface (the
/settings/certificatepage; the repair issue links to it). If pairing is not started, a repair issue explains how to start it, with the manual import as the alternative, and setup retries on its own. - EC client certificates (#133): newly generated certificates use an ECDSA P-256 key instead of RSA-4096 and are valid for 15 years. Their common name now ends in a short key hash (e.g.
homeassistant.local-3fa91c07), so a regenerated certificate is not mistaken for an older one. - Quieter connection failures (#134): a connection the broker rejects fails at once instead of retrying for 10 seconds, and is reported once by Home Assistant's "not ready yet" message instead of repeated errors with stack traces.
Upgrading
No action needed. Existing entries keep their stored certificate and key; the new behaviour applies to newly generated certificates.
Full changelog: v0.5.2...v0.6.0