Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detected that custom integration 'eufy_security' sets option flow config_entry explicitly #1286

Open
iSteve-O opened this issue Jan 13, 2025 · 2 comments

Comments

@iSteve-O
Copy link

Describe the bug

Latest version of HA throws error.

Additional information

Go to Settings -> System -> Repairs -> Click on 3 dots (...) -> System Information and get Version and Installation Type to below fields;

  • Home Assistant Installation Type (OS - Supvervised - Core): OS

  • Home Assistant Core Version: 2025.1.2

  • Eufy Security Add-on Version: 1.9.1

  • Eufy Security Integration Version: 8.1.1

  • Using go2rtc Add-on or webrtc custom integration with integrated go2rtc: no

  • Debug Logs from Home Assistant (How to enable debug logs for eufy_security integration? #624) - Without this, I will automatically resolve this issue

    2025-01-12 10:25:03.759 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'eufy_security' sets option flow config_entry explicitly, which is deprecated at custom_components/eufy_security/config_flow.py, line 27: self.config_entry = config_entry. This will stop working in Home Assistant 2025.12, please create a bug report at https://github.com/fuatakgun/eufy_security/issues

  • Logs from Eufy Security Add-on (either from Add-ons page of Home Assistant or Docker output):

  • Would you share your device with me in case further debugging required? (Yes/No):

Additional context

Add any other context about the problem goes here. Mainly, share everything as log files and use screenshots as last resort.

@steyrblade
Copy link

Is there a dot missing in the error message "...This will stop working in Home Assistant 2025.12..."
2025.12 = 2025.1.2???
==>Because its already not running any more in my system

@fuatakgun
Copy link
Owner

I believe it is December 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants