What you need to do
Sign in again once after updating. Your devices stop updating in HomeKit until you do.
- Open the Homebridge Eufy settings. A dialog says a sign-in is needed.
- Choose Sign in again, and complete the captcha or the verification code if Eufy asks for one.
- Restart Homebridge when the page asks you to.
This happens once. This beta moves to version 0.2.0 of the Eufy library underneath, and that version keeps the saved session in a new form, so a session saved by an earlier beta can't be reused. Your settings and your HomeKit accessories stay as they are.
Signing in is harder to miss
- When the saved session can no longer be used, the settings page now opens a dialog in front of everything, with one button that takes you to the sign-in. Before, the page said the device status was stale and suggested a diagnostic run or a restart. Neither helped.
- When Eufy sends you a verification code, the page now says so in plain words. It used to show a technical line such as
code sent via app-push/sendmsg/verify_code. - If a captcha answer is refused, the page now says so before showing the new captcha. It used to swap the image without a word.
Pet detection on more cameras
Pet detections now trigger the motion sensor on every camera that reports them, not only on doorbells. If you already had it on a doorbell, nothing changes for you.
Also from the library update
- Two identical cameras on one HomeBase: if their Eufy records don't give each camera its own channel, the plugin now refuses to address the second one, rather than risk showing one camera's video under the other's name. If one of your cameras stops streaming after this update, open an issue with a diagnostics archive from the settings page.
- Memory: event thumbnails take much less memory to rebuild.
- Sessions: a rejected sign-in token is no longer mistaken for an expired one, and a token that keeps being replaced is not retried in a loop.