Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

[bolqr]

I install the add-on and integration. I log without problems to my eufy account but when i press the setting buton it comes with the folllowing error:

(Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble)

This error originated from a custom integration.

Logger: homeassistant
Source: custom_components/robovac/tuyalocaldiscovery.py:54
integration: Eufy Robovac (documentation, issues)
First occurred: 11:42:51 PM (98 occurrences)
Last logged: 11:46:51 PM

Error doing job: Exception in callback _SelectorDatagramTransport._read_ready() (None)
Traceback (most recent call last):
File "/config/custom_components/robovac/tuyalocaldiscovery.py", line 50, in datagram_received
padded_data = decryptor.update(data) + decryptor.finalize()
~~~~~~~~~~~~~~~~~~^^
ValueError: The length of the provided data is not a multiple of the block length.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run
self._context.run(self._callback, *self._args)
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 1244, in _read_ready
self._protocol.datagram_received(data, addr)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
File "/config/custom_components/robovac/tuyalocaldiscovery.py", line 54, in datagram_received
data = data.decode()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x89 in position 0: invalid start byte

Any salution for this error?

this as well show up:

Logger: homeassistant.components.vacuum
Source: helpers/deprecation.py:257
integration: Vacuum (documentation, issues)
First occurred: 11:42:48 PM (10 occurrences)
Last logged: 11:42:48 PM

The deprecated constant STATE_CLEANING was used from robovac. It will be removed in HA Core 2026.1. Use VacuumActivity.CLEANING instead, please report it to the author of the 'robovac' custom integration
The deprecated constant STATE_DOCKED was used from robovac. It will be removed in HA Core 2026.1. Use VacuumActivity.DOCKED instead, please report it to the author of the 'robovac' custom integration
The deprecated constant STATE_ERROR was used from robovac. It will be removed in HA Core 2026.1. Use VacuumActivity.ERROR instead, please report it to the author of the 'robovac' custom integration
The deprecated constant STATE_IDLE was used from robovac. It will be removed in HA Core 2026.1. Use VacuumActivity.IDLE instead, please report it to the author of the 'robovac' custom integration
The deprecated constant STATE_RETURNING was used from robovac. It will be removed in HA Core 2026.1. Use VacuumActivity.RETURNING instead, please report it to the author of the 'robovac' custom integration

[DavelSaverage]

I've got the same error trying to set this up today.

[FricoRico]

I thought it was only me, but I guess we all suffer from the same issue.

[doneverhart]

same today

[doneverhart]

Logger: aiohttp.server
Source: /usr/local/lib/python3.13/site-packages/aiohttp/web_protocol.py:481
First occurred: 11:36:59 PM (2 occurrences)
Last logged: 11:38:37 PM

Error handling request from 192.168.50.78
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/aiohttp/web_protocol.py", line 510, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/web_app.py", line 569, in _handle
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 87, in forwarded_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 86, in ban_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 41, in headers_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
result = await handler(request, **request.match_info)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 83, in with_admin
return await func(self, request, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 272, in post
return await super().post(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 74, in wrapper
return await method(view, request, data, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 76, in post
return await self._post_impl(request, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 83, in _post_impl
result = await self._flow_mgr.async_init(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<2 lines>...
)
^
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 316, in async_init
flow = await self.async_create_flow(handler, context=context, data=data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 3682, in async_create_flow
return handler.async_get_options_flow(entry)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^
File "/config/custom_components/robovac/config_flow.py", line 206, in async_get_options_flow
return OptionsFlowHandler(config_entry)
File "/config/custom_components/robovac/config_flow.py", line 221, in init
self.config_entry = config_entry
^^^^^^^^^^^^^^^^^
AttributeError: property 'config_entry' of 'OptionsFlowHandler' object has no setter

[Jimster1]

I also get the same :(

[mickday]

Same here....

[andypiper]

Subscribing to this as I'm seeing the same thing.

[bobek212141-wq]

Same here

[beeaton]

Just got the same error as well. Hopefully this gets fixed

[AwesomeLoui]

I have the same problem, hope this gets fixed soon :)

[Advantage-ts]

I have had this problem and have just managed to get it working

What you’ll see (symptoms)

During setup:
• The integration only asks for Eufy login (no prompt for IP).
• After adding it, clicking Configure / Options throws a 500 and the UI won’t load.

Typical log errors:
• Config flow could not be loaded: 500 Internal Server Error
• AttributeError: property 'config_entry' of 'OptionsFlowHandler' object has no setter
• TypeError: OptionsFlowHandler() takes no arguments
• AttributeError: 'OptionsFlowHandler' object has no attribute '_config_entry'

Result: you can’t store a fixed IP anywhere, so local control is flaky:
• entity goes Unavailable
• controls greyed out
• partial telemetry only

⸻

Root cause

Home Assistant changed how options flows are instantiated and how config_entry is managed.

Older integrations often did one (or more) of these:
• tried to assign self.config_entry = config_entry (no longer allowed: managed property)
• expected the OptionsFlow class to be created with args (HA now constructs it differently)
• relied on _config_entry but never initialised it properly

So HA can’t load the options flow, and you never get the UI fields you need.

⸻

Fix implemented (matches the attached config_flow.py)

This patch does two key things:

1. Make the Options Flow compatible with modern HA
   • OptionsFlowHandler takes no constructor args
   • it uses HA’s managed self.config_entry property
   • it stores an internal reference safely via self._config_entry

Key pattern:
• async_get_options_flow() returns OptionsFlowHandler() with no args
• async_step_init() pulls in self.config_entry instead of trying to set it

2. Add a working place to store a per-vacuum IP address

The config entry stores devices under a vacs structure like:

"vacs[vac_sn] = {
"name": "...",
"mac": "...",
"autodiscovery": True,
"ip_address": ""
}"

Then the Options UI lets you:
• pick which vacuum to edit
• toggle autodiscovery
• enter a static IP (CONF_IP_ADDRESS)
• save it into the config entry via async_update_entry(...)

⸻

Practical workaround steps (what actually makes it reliable)

Step 1 — Lock the vacuum IP on DHCP

On UniFi / UDM / DHCP server:
• create a DHCP reservation for the vacuum’s MAC
• ensure the device always gets the same IP

This prevents local Tuya comms from breaking when IPs change.

Step 2 — Patch the integration (so Options works)

Replace your integration’s config_flow.py with the patched one (the version you posted / attached).

Restart Home Assistant.

Step 3 —

Set the IP through the now-working Options UI

Go to:

Settings → Devices & Services → Robovac → Configure

You should now get a flow like:
• pick action (edit / rescan)
• select vacuum
• set:
• Autodiscovery: off (if you want it pinned)
• IP address: 10.10.x.x
• Save

After that, local polling/control becomes stable because the integration has a known target and isn’t relying on discovery.

⸻

Why this matters (Tuya/Eufy local control reality)

With local Tuya devices, discovery is often the weak point. If HA can’t store/use a fixed IP you’ll see:
• random dropouts / “Unavailable”
• commands not taking
• state stuck “Completed” etc.

Pinning the IP + giving the integration a reliable place to store it is the difference between “sometimes works” and “works every day”.

⸻

Bonus note: “Return-to-base command did not take”

If you also see:

Return-to-base command did not take. This model may use a different DP/value.

That’s usually separate from the options/IP issue — it means your vacuum model uses a different Tuya DP for dock/charge/return. The next step there is to:
• capture DPS changes while pressing “home/dock” in the official app
• identify which DP flips/changes
• update the integration’s DP mapping for your model

vacuum.py
config_flow.py

[andypiper]

These (presumably AI-supported? based on the way this is written) changes did not fix the plugin for my use case - mind you, I've never had it working before either, and I have a pretty early Eufy Robovac 11c model, so it is possible my device was never supported by it. It did something different and the config flow thing appeared to work, but I could not set an IP address, still had errors and my device did not show up.

[bcrowder151]

Same error. Any idea if a fix can/will be implemented?