Plum Lightpad component fails to initialize lights.

[rjroch]

Home Assistant release with the issue:

0.85.1

Last working Home Assistant release (if known):
0.85.0

Operating environment (Hass.io/Docker/Windows/etc.):

Raspberry pi manual install

Component/platform:

plum_lightpad

Description of problem:
Lightpads fail to initialize and are not available. Light rings show up in GUI but can not be configured.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

plum_lightpad:
  username: !secret email_address
  password: !secret plum_password

Traceback (if applicable):

Jan 21 16:22:07 hass hass[4334]: 2019-01-21 16:22:07 INFO (MainThread) [homeassistant.loader] Loaded light.plum_lightpad from homeassistant.components.light.plum_lightpad
Jan 21 16:22:07 hass hass[4334]: 2019-01-21 16:22:07 INFO (MainThread) [homeassistant.components.light] Setting up light.plum_lightpad
Jan 21 16:22:07 hass hass[4334]: 2019-01-21 16:22:07 INFO (MainThread) [homeassistant.components.light] Setting up light.plum_lightpad
Jan 21 16:22:07 hass hass[4334]: 2019-01-21 16:22:07 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Jan 21 16:22:07 hass hass[4334]: Traceback (most recent call last):
istant.core] Error doing job: Task exception was never retrieved
Jan 21 16:22:07 hass hass[4334]: Traceback (most recent call last):
Jan 21 16:22:07 hass hass[4334]:   File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
Jan 21 16:22:07 hass hass[4334]:     result = coro.send(None)
Jan 21 16:22:07 hass hass[4334]:   File "/srv/homeassistant/homeassistant_venv_3.5.3/lib/python3.5/site-packages/homeassistant/helpers/entity_platform.py", line 352, in _async_add_entity
Jan 21 16:22:07 hass hass[4334]:     await entity.async_update_ha_state()
Jan 21 16:22:07 hass hass[4334]:   File "/srv/homeassistant/homeassistant_venv_3.5.3/lib/python3.5/site-packages/homeassistant/helpers/entity.py", line 239, in async_update_ha_state
Jan 21 16:22:07 hass hass[4334]:     attr = self.state_attributes or {}
Jan 21 16:22:07 hass hass[4334]:   File "/srv/homeassistant/homeassistant_venv_3.5.3/lib/python3.5/site-packages/homeassistant/components/light/__init__.py", line 438, in state_attributes
Jan 21 16:22:07 hass hass[4334]:     if supported_features & SUPPORT_COLOR_TEMP:
Jan 21 16:22:07 hass hass[4334]: TypeError: unsupported operand type(s) for &: 'NoneType' and 'int'

Additional information:

[rjroch]

I have some further details. This issue appears to be related to the light rings being disabled when Home Assistant is initialized. If the rings are on, the switch portion of the light initializes properly. That being said, I now have a strange circumstance where the light ring toggles in Home Assistant are turning on and off rapidly.

[ColinHarrington]

Were there any other warnings or errors in setting up the plum_lightpad component?

I don't believe that I tested the integration with the light rings disabled. I'll give that a shot and report back when I get a chance.

[froz]

It's an odd error. Once it occurs, the switch always fails to initialize unless the glow ring is disabled and then enabled again prior to restarting homeassistant. I never disable my glow rings, so I'm not sure what triggers the failure. The traceback posted above is the only error message in the log.

Also, I have not seen the rapid toggling of the glow ring.

[froz]

After seeing this twice more in the past month, I altered the code to stop returning None when the glow ring is off, which, by the way, is either turning itself off, or its state is not restored correctly during restarts once in every blue moon. Not returning None avoids the error. However, I have no idea what the root cause is.

--- src/home-assistant/homeassistant/components/plum_lightpad/light.py  2019-04-07 17:45:35.568734488 -0700
+++ homeassistant/lib/python3.7/site-packages/homeassistant/components/plum_lightpad/light.py   2019-04-07 14:51:27.618734488 -0700
@@ -72,7 +72,7 @@
         """Flag supported features."""
         if self._load.dimmable:
             return SUPPORT_BRIGHTNESS
-        return None
+        return 0

     async def async_turn_on(self, **kwargs):
         """Turn the light on."""

[froz]

I took a look to find the cause. The Pypi module has the following code:

 @property
    def dimmable(self):
        return bool(self.primaryLightpad.glow_enabled)

The effect is to trigger the reported error if the lightpad glow ring is off at discovery. Not sure what the intention here was -- as far as I know, no one has figured out how to control the glow ring brightness (it is dimmable in the Plum app), but it seems odd to use the glow ring state to determine whether the lightpad is in switch mode or in dimmer mode, which is what this code is doing. If the lightpad is in switch mode, the OP's error is triggered unless the change I made above is done (return 0 instead of None).

[stale]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[stale]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[ColinHarrington]

@froz I think you are right about the supported_features, The features seem to be bit flags and 0 would be a better choice than None