Phillips Hue errors on fresh Hassbian

Configuration
1

Hello,

I’m new to HASS and while being able to control my Hue lights i keep having errors :

17-01-04 11:56:30 homeassistant.core: Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/lib/python3.4/asyncio/tasks.py”, line 233, in _step
result = coro.throw(exc)
File “/srv/homeassistant/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py”, line 386, in _update_entity_states
yield from update_coro
File “/srv/homeassistant/lib/python3.4/site-packages/homeassistant/helpers/entity.py”, line 216, in async_update_ha_state
yield from self.hass.loop.run_in_executor(None, self.update)
File “/usr/lib/python3.4/asyncio/futures.py”, line 388, in iter
yield self # This tells Task to wait for completion.
File “/usr/lib/python3.4/asyncio/tasks.py”, line 286, in _wakeup
value = future.result()
File “/usr/lib/python3.4/asyncio/futures.py”, line 277, in result
raise self._exception
File “/usr/lib/python3.4/concurrent/futures/thread.py”, line 54, in run
result = self.fn(*self.args, **self.kwargs)
File “/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/light/hue.py”, line 397, in update
self.update_lights(no_throttle=True)
File “/srv/homeassistant/lib/python3.4/site-packages/homeassistant/util/init.py”, line 296, in wrapper
result = method(*args, **kwargs)
File “/srv/homeassistant/lib/python3.4/site-packages/homeassistant/util/init.py”, line 296, in wrapper
result = method(*args, **kwargs)
File “/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/light/hue.py”, line 207, in update_lights
lightgroups[lightgroup_id].schedule_update_ha_state()
File “/srv/homeassistant/lib/python3.4/site-packages/homeassistant/helpers/entity.py”, line 290, in schedule_update_ha_state
self.hass.add_job(self.async_update_ha_state(force_refresh))
AttributeError: ‘NoneType’ object has no attribute ‘add_job’

My configuration is only this :

light:

  • platform: hue
    host: 10.11.0.186

Am i missing something ?

2

your indentation is wrong if this is actually what is in your configuration.yaml file. Host should be indented the same amount as platform.

3

Thanks for the pointer, but i think my configuration file is correctly indented.
would i be able to control the lights if it wasn’t ?

here is what it looks like

(with some new parameters to see if that helps : no changes)

4

Typically when you see this type of error, you have mis-spelled something when referencing the object, or you are using an attribute path that doesn’t exist in the object. Is this failing in an automation or are these just error messages you see in the log and are wondering about?

5

Well,
here is the full configuration file currently running on my hass :
https://hastebin.com/apenesegef.makefile

I stripped it down to the minimum possible (i think ?).
I do not have any automation set yet as i do not want to invest time in something who produces errors for no apparent reason ?

Besides having errors in logs i also see a lag between the button activation (on webUI) and the black notification (bottom left).

6

Please post your config inline using the </> button so that we can all see it without going to what appears to be a makefile.

7

It is not a makefile.
hastebin is the tool suggested to use in the HASS official chatroom.

here is my full config

homeassistant:
  name: Home
  latitude: 45
  longitude: -0.2167
  elevation: 5
  unit_system: metric
  time_zone: Europe/Paris

frontend:

http:

light:
  - platform: hue
    host: 10.11.0.186
    allow_unreachable: true
    scan_interval: 10

any ideas ?

8

Do you have more than one light platform? If not, then you don’t need the dash.

#
# Hue API
#
light:
  platform: hue
  host: 192.168.1.151
  allow_unreachable: true
  filename: phue.conf
9

no more ideas here. One of the HA development team will have to look at that.

10

Yes, i had LIFX configured too (wich does not produces errors nor lag).

But as said i’m trying to have nothing but the hue configuration, so for testing i also removed the (for now) unnecessary dash.

here is my current full config

homeassistant:
  name: Home
  latitude: 45
  longitude: -0.2167
  elevation: 5
  unit_system: metric
  time_zone: Europe/Paris

frontend:

http:

light:
  platform: hue
  host: 10.11.0.186
  allow_unreachable: true
  scan_interval: 10
  filename: phue.conf

I’m trying to make sure that i do not have any mistakes in my configuration, anything left ?

11

Is there a way to catch their attention ?

12

Most are pretty good about monitoring the site. There is a bug reporting process on github I think. But I haven’t done that yet. One other thing you could try would be to post a link to this discussion on the developers group.

13

The only other thing I can think of is to rename the phue.conf file and comment default_view (if you’re using it) so you can see the configurator and try to create a new phue.conf just in case something got hosed there.

14

Thanks,

I think i’m not the only one : https://github.com/home-assistant/home-assistant/issues/4994
As suggested here, i’ve done a cleanup on my Hue bridge (via mobile app).

An BAM no more errors nor lag when using the UI.

Now, i’m restoring my more complete configuration file ! :slight_smile:

Feels good to have a No errors have been reported. message now :slight_smile:

Thanks for your help !

1 Like
15

It would be nice though if the developers would figure out what is causing that and trap/handle the error without a dump.

16

I had the same issue, cleanup has worked perfectly to fix it.