What you need to do
Nothing. Update when the Homebridge UI offers it.
Reporting a bug, from this release on
Open the plugin dashboard, choose Debug diagnostics, pick the area that is misbehaving and follow it through. It hands back an encrypted archive and a bug report already filled in with your versions — no serial numbers, addresses, tokens or login details, and nothing is uploaded anywhere.
A report opened by hand instead arrives with no archive and no versions, which is a week of questions before anyone can look at it. Those are now closed on arrival with a pointer back to this path. Nothing is lost by that: the report the plugin writes takes a couple of minutes.
Never attach a Homebridge backup, a config.json or a raw log. They hold your eufy password, your other plugins' logins and your HomeKit pairing code in readable form, and the issue page is public. Only the .eufysupport.gz file is safe to attach, and anything else is removed on sight.
What changed
The prepared report now fills in your Homebridge version. Triage was asking for that line even though the plugin had recorded it all along, so two reports filed correctly last week were held for nothing.
The support case id has come off the form. The archive's own filename carries it, and a case id placed in a URL travels through browser history and every proxy between you and GitHub.