Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

More than 5 switches causes issues

See original GitHub issue

Everything works perfectly if I have less than 5 switches manually defined. Once I define 5 or more, I get the following error:

2018-04-07 21:07:13 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
    result = coro.send(None)
  File "/home/homeassistant/.homeassistant/custom_components/lutron_caseta_pro.py", line 251, in _read_next
    yield from callback.call(mode, integration, action, value)
  File "/home/homeassistant/.homeassistant/custom_components/lutron_caseta_pro.py", line 213, in call
    yield from attr(*args, **kwargs)
  File "/home/homeassistant/.homeassistant/custom_components/switch/lutron_caseta_pro.py", line 54, in read_output
    yield from device.async_update_ha_state()
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity.py", line 192, in async_update_ha_state
    raise RuntimeError("Attribute hass is None for {}".format(self))
RuntimeError: Attribute hass is None for <Entity Master Bedroom Fan: on>

Every time I reboot, the device listed as having the error changes. Sometimes its a switch and sometimes its a fan. When I got this error, I removed one of my switches from my configuration.yaml file. After a reboot, everything worked fine. I tried adding back in the 5th switch and after a reboot, the error came back.

Issue Analytics

State:
Created 5 years ago
Comments:14 (6 by maintainers)

Top GitHub Comments

1reaction

upsertcommented, Jun 24, 2018

I’ve updated the component to set the initial values in a different added_to_hass function to help with this issue. I was waiting for the update 0.72 and with these changes in place, I also had no issue updating to 0.72 and all switches and controls responding as expected.

If you are having any of the issues on upgrade or on HA restart mentioned above, please update your copy of the component and add a comment here if there are still issues.

0reactions

upsertcommented, Aug 26, 2018

This issue is now stale and at least for the startup, appears to be resolved. No more issues found or reported. Closing it.