No "hue" attribute for L530 bulb

[JayUK]

No "hue" attribute for L530 bulb

[Petros15]

Same here. It's a v1 bulb and it suddenly became irresponsive. Updating to the latest integration version did not solve the problem. The bulb now behaves erraticaly. It doesn't always register commands, its status is not updated properly and it also often returns "TapoError.ERR_DEVICE: Rate limit exceeded" in addition to the "hue" error.

Soft resetting the bulb and reinstalling it in both the Tapo app and HA did not help.

[norbee37]

Here too. Both errors show up and at some point the device gets unavailable. Though strangely at least in the beginning it actually toggles couple of times then stops working.

[Kisinu]

Same here. I guess it all started after last tapo integration update.

service light/turn_on. 'NoneType' object has no attribute 'hue'

[serin113]

This is probably a duplicate of #746: it has the same NoneType'd self.device.hs object error, and affects the same firmware (1.3.0) and hardware (L530 v1.0).

There's PR #748 which seems to fix the NoneType error, but doesn't fix the erratic behavior of the bulb: the "rate limit exceeded" error, and the color resetting to white when adjusting the brightness.

[serin113]

This is probably a duplicate of #746: it has the same NoneType'd self.device.hs object error, and affects the same firmware (1.3.0) and hardware (L530 v1.0).

There's PR #748 which seems to fix the NoneType error, but doesn't fix the erratic behavior of the bulb: the "rate limit exceeded" error, and the color resetting to white when adjusting the brightness.

Some updates on this:

I tried reverting to earlier versions to trace where this issue started: v3.0.0 doesn't have it, but v3.1.0 and above do.

#748 fixes this specific issue, since the recently introduced new interface does allow the hs object to be none: https://github.com/petretiandrea/plugp100/blob/0c092b33e233b7881188b05e9b01f967e043ca8b/plugp100/new/components/light_component.py#L41

    @property
    def hs(self) -> Optional[HS]:
        if self._state.hue is not None and self._state.saturation is not None:
            return HS(self._state.hue, self._state.saturation)
        return None

Why the L530E (v1.0) doesn't have hue & saturation isn't obvious to me, but it's the exact same issue I have with the default Tapo integration (home-assistant/core#111757). I'm guessing this issue was introduced by a recent firmware update, because even reverting to a previously working version of this integration didn't fix the color+brightness resetting.

The python-kasa project has recently merged a fix for this exact model, maybe it'll help with the new interface (but it's not in a release yet): python-kasa/python-kasa#840