Remote Home-Assistant 3.2 Problems

I’ve been using Remote Home-Assistant for over a year under Hass OS with a RPi4 master and an RPi3B+ slave, both with USB Z-wave sticks. What a great piece of software! However, on updating to Remote Home-Assistant 3.2 I have three problems I have not been able to resolve, which may be complicated by also updating to Z-Wave js:

  1. The first problem is an almost 5 sec latency on commands to the slave. the problem seems to be more pronounced for a z-wave dimmer compared to locks and switches. Not sure if switching to Z-Wave js is a factor in this latency.

  2. The second is that when I click on the Remote Home-Assistant options menu (in Configuration Integrations), I get “Error - Config flow could not be loaded”. The log shows

Logger: aiohttp.server
Source: custom_components/remote_homeassistant/
First occurred: 11:16:36 AM (3 occurrences)
Last logged: 1:37:40 PM

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/aiohttp/", line 422, in _handle_request
    resp = await self._request_handler(request)
  File "/usr/local/lib/python3.8/site-packages/aiohttp/", line 499, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.8/site-packages/aiohttp/", line 119, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/", line 56, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/", line 18, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/", line 72, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/", line 129, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/", line 129, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/config/", line 191, in post
    return await super().post(request)
  File "/usr/src/homeassistant/homeassistant/components/http/", line 60, in wrapper
    result = await method(view, request, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/", line 69, in post
    result = await self._flow_mgr.async_init(
  File "/usr/src/homeassistant/homeassistant/", line 122, in async_init
    flow = await self.async_create_flow(handler, context=context, data=data)
  File "/usr/src/homeassistant/homeassistant/", line 1141, in async_create_flow
    return cast(OptionsFlow, HANDLERS[entry.domain].async_get_options_flow(entry))
  File "/config/custom_components/remote_homeassistant/", line 94, in async_get_options_flow
    return OptionsFlowHandler(config_entry)
  File "/config/custom_components/remote_homeassistant/", line 191, in __init__
    self.remote =[DOMAIN][self.config_entry.entry_id][
AttributeError: 'NoneType' object has no attribute 'data'
  1. The following problem has been dogging me since I first started using Remote Home-Assistant (previous versions). Commands from the master execute on the slave, but I get a warning message in the log:
Logger: homeassistant.helpers.service
Source: helpers/
First occurred: 11:09:04 AM (18 occurrences)
Last logged: 1:21:56 PM

Unable to find referenced entities light.lamp_dimmer

I have tried just about every setting in the Yaml configuration file without success to resolve this issue.

I would appreciate any help to understand how these issues might be resolved.

Thanks in advance!

1 Like

have the same problem

My answers to each question:

  1. I can’t really tell why that is, but there has been similar reports before. Conclusion have been to be unrelated to the integration at least.
  2. Fixed in 3.2.1
  3. It’s a minor inconvenience that I haven’t managed to reproduce in order to fix it. It is however harmless and you can ignore it (gives an annoying log entry though).

Thanks Pierre.
I missed that Lukas released version 3.3 that fixes the option flow problem.