Switch does go back on again, when switching off via Home Assistant GUI about hacs-homee

[hajo62]

Thanks for your fast response.
Haven't seen a log entry.
I will check (logs and the rest) when it occurs the next time.

[hajo62]

It happened again.

• Does the Fibaro plug actually turn off despite the UI not updating correctly?
  No, it does not change it's state

• Are there any errors in your HA logs?

2021-07-15 08:49:04 ERROR (MainThread) [frontend.js.latest.202106030] https://myHomeassistant/lovelace/repeater?edit=1:0:0 Uncaught
2021-07-15 08:50:08 ERROR (MainThread) [frontend.js.latest.202106030] https://myHomeassistant/lovelace/repeater?edit=1:0:0 Uncaught
2021-07-15 08:58:10 ERROR (MainThread) [frontend.js.latest.202106030] https://myHomeassistant/lovelace/repeater:0:0 Uncaught 

And after HA Restart, I saw:

Logger: homeassistant
Source: custom_components/homee/config_flow.py:140
Integration: homee (documentation, issues)
First occurred: 13:02:59 (1 occurrences)
Last logged: 13:02:59
Error doing job: Task exception was never retrieved

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 153, in async_init
    flow, result = await task
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 179, in _async_init
    result = await self._async_handle_step(flow, flow.init_step, data, init_done)
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 260, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
  File "/config/custom_components/homee/config_flow.py", line 140, in async_step_zeroconf
    self.homee_id = discovery_info.get(zeroconf.ATTR_NAME)
AttributeError: module 'homeassistant.components.zeroconf' has no attribute 'ATTR_NAME'

Regarding the debug info: I missed to set the switch. Just set it now and that's what I see on Developer Tools / Entities / Attributes:

current_power_w: 0
today_energy_kwh: 0.07
homee_data: 
id: 11
name: FIBARO Repeater
profile: 13
attributes:
  - id: 100
    type: 1
  - id: 101
    type: 44
  - id: 102
    type: 45
  - id: 103
    type: 4
  - id: 104
    type: 47
  - id: 105
    type: 48
  - id: 106
    type: 3
  - id: 107
    type: 347

friendly_name: FIBARO Repeater
device_class: outlet

Not sure if set helps. Will do a HA restart and look if the next failure will show more info in the attributes. Or would I see the debug info?

(I had mixed some log entires and therefore posted this although in the HA forum. But there someone ansered this:
https://community.home-assistant.io/t/correct-reasons-for-log-entries/322494/3
I think, it's useful)

[hajo62]

I'll close the issue.
Looks like it works - although I haven't changed something except the HA version to 2021.11.4

[FreshlyBrewedCode]

This happens commonly if HA has lost the connection to homee or homee takes to long to respond. Once you toggle the switch a command should be dispatched to homee but the switch will return to the actual state of the HA entity after a few seconds. So if homee does not update and report the new state back to HA the switch will flip back on/off to the last known state.

I will need some additional information:

• Does the Fibaro plug actually turn off despite the UI not updating correctly?
• Are there any errors in your HA logs?
• What is the debug information of the Fibaro plug entity? (toggle "Add debug information" in the configuration and click on the entity)

Restarting HA will reload the integration and perform a fresh reconnect to homee which fixes any previous connection problems.

[FreshlyBrewedCode]

Thanks for the info. At first glance, it looks like the integration is just losing the connection to homee. You could try to verify this by checking if you get the same behavior for other devices or if the problem only occurs for the Fibaro plug.
Although very unlikely, it could also be a problem between homee and the plug. You could verify this by toggling the plug from the homee UI and check if it actually switches and if the HA UI updates as well.

If it is "just" a connection problem there is unfortunately very little I can do to help. I am struggling with occasional disconnects myself and the integration should try to reconnect after it lost the connection to homee but sometimes restarting HA is the only way to restore the connection.

[hajo62]

Hi,

• Same behavior for other devices: Yes
• Toggling the plug from the homee UI: That works well as well as the state change is shown in HA, too.

[FreshlyBrewedCode]

That works well as well as the state change is shown in HA

This is strange. This may suggest that there is a problem with the service that is used to send new values to homee. Do you have more than one homee configured in HA?

You can also try to manually call the service next time the issue occurs by going to the services section of the HA developer tools and calling the homee.set_value service with the following data:

node: 11
attribute: 100
value: 0    # 0 for off, 1 for on

[hajo62]

Just one homee.

Like this?

Looks like it does not work, too.

Edited: I think I made a mistake. Haven't got it to run manually again. Just a short time after HA restart.

Could I assist to grab useful debug information?

[Gaili]

Same problem with my HA and Homee

[FreshlyBrewedCode]

As mentioned on the forum, you could try to reload the integration to force it to reconnect:

This could even be automated using the reload_config_entry service, however, I have not tried it yet.

[Gaili]

Yeah it`s working with reload, meanwhile i have a workaround with mqqt.
greets