Can't turn on lights, getting error "argument of type 'NoneType' is not iterable"

Adde · May 19, 2022, 3:58pm

Running in a ProxMox VM with 2 vCPU cores and 4 GB RAM.
Got two IKEA lights and one control outlet.
Controller is ConBee II with version 2.15.03 / 2022-04-21 and firmware 26720700.

Home Assistant Core 2022.5.5
Home Assistant Supervisor 2022.05.2
Home Assistant OS 8.0

Source: components/deconz/light.py:250
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 17:33:14 (12 occurrences)
Last logged: 17:50:28

[140129849338800] argument of type 'NoneType' is not iterable
[140127946090192] argument of type 'NoneType' is not iterable
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 189, in handle_call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1627, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1664, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
    await service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 677, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 964, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 714, in _handle_entity_call
    await result
  File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 536, in async_handle_light_on_service
    await light.async_turn_on(**filter_turn_on_params(light, params))
  File "/usr/src/homeassistant/homeassistant/components/deconz/light.py", line 250, in async_turn_on
    elif "IKEA" in self._device.manufacturer:
TypeError: argument of type 'NoneType' is not iterable

Adde · May 24, 2022, 10:29am

Downgrading Home Assistant Core to version 2021.12.7 solves the problem for now.
It’s getting pretty annoying that it’s so common for stuff to break when upgrading Home Assistant…

bobbinz · August 16, 2022, 11:34am

Is there a better solution to this? I really don’t want to have to downgrade!

Adde · August 16, 2022, 12:50pm

I tried updating HA Core to 8.4 and HA Supervisor to 2022.8.3, I also reloaded the deCONZ integration. It now seems to work.
Other then that, I don’t know.

But my experience is that once you have a version of HA that works for you, never update it

Delmar · October 20, 2022, 11:21am

Having the same issue with some Philips Hue lights, latest HA core and supervisor.

Any suggestions?

tophilza · October 24, 2022, 5:59am

Hi Delmar,

Im having the same issue now. Did you find a solution?

toefftoeff · November 12, 2022, 12:51am

I had the same problem with a GLEDOPTO GL-C-007 Zigbee Light Controller. I removed it in Phoscon, rebooted HA and deconz, added it in Phoscon again and then it also worked in HA. Seems like something went wrong the first time in the Setup.

ygeffens · December 3, 2022, 9:59pm

Did you have to unpair the light first? If no, when you delete it in Phoscon, how do you add it, when you don’t have to put the light in pairing mode.

I’m on Home Assistant 2022.11.5, Supervisor 2022.11.2

I have 5 Ikea lightbulbs. 2 of them are working fine. In the overview of available devices I see the light, with “Ikea of Sweden”. The 3 lights that aren’t working show .

I can control all 5 lights from Phoscon.

dbs · December 4, 2022, 9:56am

If the devices are showing up in Phoscon but not HA, you can go to Developer Tools → Services and issue a decent.device_refresh call to get HA to see them. However, restarting HA should have the same effect.
-David

ygeffens · December 4, 2022, 10:28am

The devices DO show up, as ‘Dimmable Light 7’, 8, 9.
But when I look at the devices listed for the Deconz integration I see behind the device.
Turning the device on or off only results in an error.

A deconz.device_refresh is not solving the problem (just tested).

Now I see what is missing in my first (and second) message.
The editor here is hiding unknown because it was written between ‘<’ and ‘>’

So the line above should read:
But when I look at the devices listed for the Deconz integration I see ‘’’< unknown >’’’ behind the device.

Hapeter · January 8, 2023, 9:12pm

I have a similar problem, I’m getting this error “argument of type ‘NoneType’ is not iterable” after adding a new Gledopto GL-D-004P downlight to deCONZ. The device seems to show up properly in the Phoscon tool. I can control the downlight from the Phoscon interface, but in Home Assistant I can only get it to turn off. Everything else results in this error. I did a HA restart and I unplugged and re-connected the Conbee stick, but this doesn’t seem to help here. I bought 4 of these downlights and so far two have the exact same issues. I’m on 2022.12.8.
For Yves: I don’t understand why the manufacturer and model show as unknown in the device list, I see the same thing. However, I also see this for another Gledopto device that I own and this device (GL-C-006) works without problems. I think I’ve also seen this with Tradfri bulbs and sometimes this information only shows after a while. So the unknown status may be unrelated to the “argument of type ‘NoneType’ is not iterable” error.