During v5 setup platform name is incorrect

[jhongturney]

Preflight Checklist

• I have searched the existing issues and this bug has not been reported before.
• I understand V4 is no longer maintained, and that a fix will only ever land in V5.
• I am using a dedicated guest admin account (not my main Eufy account).
• I have restarted Homebridge and the issue persists.

Environment

- **Plugin Version**: 5.0.0-beta.9
- **eufy SDK**: 0.2.0-beta.10
- **Node.js Version**: v24.20.0
- **Homebridge Version**: 
- **OS**: linux arm64
- **Support Case ID**: 
- **Diagnostics profile**: device-representation (now)
- **Missing evidence**: plugin-log, sdk-log, homekit-log

Area

Installation / Setup

Diagnostics Archive

N/A

What happened?

When installing or upgrading the platform value is automatically specified as EufySecurity but the plugin expects HomebridgeEufy. Manually correcting this unblocks the plugin from loading.

[github-actions]

Thanks for the report. Before anyone can look into this, there is something to sort out first.

No diagnostics archive is attached, and without it the logs that would say which part failed do not exist.

To produce one: open the plugin settings, select the device that is misbehaving, click Run diagnostics, and follow it through. Reproduce the problem once while it is collecting, then drag the file it gives you into a comment here. It is encrypted and redacted — no serial numbers, addresses, tokens or login details, and the plugin uploads nothing anywhere.

---

The environment block is missing a line: Homebridge Version.

Editing them into the report is enough. They decide which code you are running, and the answers are on the Homebridge status page and in the plugin settings.

This issue stays open and picks itself back up as soon as that lands.