Hue and Wink light entities disappeared after upgrade to 29.1

Configuration
1

Now missing all of my Hue lights. Got the following message in the logs:

16-09-29 10:42:36 homeassistant.bootstrap: Invalid config for [light.hue]: not a file for dictionary value @ data['filename']. Got 'phue.conf'. Please check the docs at https://home-assistant.io/components/light.hue/

Confirmed that the hue hub is still working, IP is the same and the API is up by going to the IP of the hub in my browser. phue.conf is present and hasn’t changed since first installed months ago and working until upgrade.

Nothing abnormal showing in logs regarding the Wink hub, but none of the lights are showing up. Switches and sensors from Wink are showing and operating correctly but no lights.

This is a big problem for me; is there a clean way to roll back to 28.2?

2

I don’t know if this is clean or not…

sudo pip3 install homeassistant==0.28.2

1 Like
3

I am having the same problem with Hue. At one point this morning it strangely started working, but acted like the hue was just a normal switch. Now it’s back to throwing that same error. I also removed my hue configuration and checked if Auto Discovery could find it, it did not as far as I can tell.

1 Like
4

Created a bug issue:

I appreciate it, but I’m afraid to try if you’re not absolutely sure. I’d hate to screw things up further.

5

I have done it before but it has been a while.

Here is this too…

6

Well, HASS just stopped responding; streaming updates died. Nothing in the log, it just ends.

Not sure how you test for segfaults if it doesn’t show in the log but that might be the problem. The log just ends with no traceback and has stopped updating.

I really would not suggest anyone update until some of these bugs are worked out. I am dead in the water.

7

I don’t know about HUE, but if you have Wink in your configuration, remove “refresh_token:…”

1 Like
8

Yeah, I did that and that’s why I have switches and locks. This was never indicated as a breaking change in the release notes but it will prevent the Wink component from loading.

9

Looks like I’m having the segfault issue:

● home-assistant.service - Home Assistant
   Loaded: loaded (/etc/systemd/system/home-assistant.service; enabled)
   Active: failed (Result: signal) since Thu 2016-09-29 11:16:31 EDT; 9min ago
  Process: 14895 ExecStart=/srv/hass/hass_venv/bin/hass -c /home/hass/ (code=killed, signal=SEGV)
 Main PID: 14895 (code=killed, signal=SEGV)

Sep 29 11:16:30 raspi1 hass[14895]: DEBUG:homeassistant.components.api:STREAM 1991210648 FORWARDING <Event state_changed[L]: old_state=<state sensor.ram_free=613.1; icon=mdi:memory, friendly_name=RAM Free, unit_of_measurement=MiB @ 2016-09-29T11:16:00.594024-04:00>, new_state=<state sensor.ram_free=612.3; icon=mdi:memory, friendly_name=RAM Free, unit_of_measurement=MiB @ 2016-09-29T11:16:30.720788-04:00>, entity_id=sensor.ram_free>
Sep 29 11:16:30 raspi1 hass[14895]: DEBUG:homeassistant.components.api:STREAM 1991210648 WRITING data: {"data": {"old_state": {"last_changed": "2016-09-29T15:16:00.594024+00:00", "state": "613.1", "attributes": {"friendly_name": "RAM Free", "unit_of_measurement": "MiB", "icon": "mdi:memory"}, "last_updated": "2016-09-29T15:16:00.594024+00:00", "entity_id": "sensor.ram_free"}, "new_state": {"last_changed": "2016-09-29T15:16:30.720788+00:00", "state": "612.3", "attributes": {"friendly_name": "RAM Free", "unit_of_measurement": "MiB", "icon": "mdi:memory"}, "last_updated": "2016-09-29T15:16:30.720788+00:00", "entity_id": "sensor.ram_free"}, "entity_id": "sensor.ram_free"}, "origin": "LOCAL", "event_type": "state_changed", "time_fired": "2016-09-29T15:16:30.720957+00:00"}
Sep 29 11:16:30 raspi1 hass[14895]: DEBUG:requests.packages.urllib3.connectionpool:"GET /status/sessions?X-Plex-Token=rpqSMcH3WN8bNCpDcYjm HTTP/1.1" 200 90
Sep 29 11:16:30 raspi1 hass[14895]: INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=<state sensor.ram_use=33.7; icon=mdi:memory, friendly_name=RAM Use, unit_of_measurement=% @ 2016-09-29T11:16:00.722467-04:00>, new_state=<state sensor.ram_use=34.0; icon=mdi:memory, friendly_name=RAM Use, unit_of_measurement=% @ 2016-09-29T11:16:30.851461-04:00>, entity_id=sensor.ram_use>
Sep 29 11:16:30 raspi1 hass[14895]: DEBUG:homeassistant.components.api:STREAM 1991210896 FORWARDING <Event state_changed[L]: old_state=<state sensor.ram_use=33.7; icon=mdi:memory, friendly_name=RAM Use, unit_of_measurement=% @ 2016-09-29T11:16:00.722467-04:00>, new_state=<state sensor.ram_use=34.0; icon=mdi:memory, friendly_name=RAM Use, unit_of_measurement=% @ 2016-09-29T11:16:30.851461-04:00>, entity_id=sensor.ram_use>
Sep 29 11:16:30 raspi1 hass[14895]: DEBUG:homeassistant.components.api:STREAM 1991210648 FORWARDING <Event state_changed[L]: old_state=<state sensor.ram_use=33.7; icon=mdi:memory, friendly_name=RAM Use, unit_of_measurement=% @ 2016-09-29T11:16:00.722467-04:00>, new_state=<state sensor.ram_use=34.0; icon=mdi:memory, friendly_name=RAM Use, unit_of_measurement=% @ 2016-09-29T11:16:30.851461-04:00>, entity_id=sensor.ram_use>
Sep 29 11:16:30 raspi1 hass[14895]: DEBUG:homeassistant.components.api:STREAM 1991210896 WRITING data: {"data": {"old_state": {"last_changed": "2016-09-29T15:16:00.722467+00:00", "state": "33.7", "attributes": {"friendly_name": "RAM Use", "unit_of_measurement": "%", "icon": "mdi:memory"}, "last_updated": "2016-09-29T15:16:00.722467+00:00", "entity_id": "sensor.ram_use"}, "new_state": {"last_changed": "2016-09-29T15:16:30.851461+00:00", "state": "34.0", "attributes": {"friendly_name": "RAM Use", "unit_of_measurement": "%", "icon": "mdi:memory"}, "last_updated": "2016-09-29T15:16:30.851461+00:00", "entity_id": "sensor.ram_use"}, "entity_id": "sensor.ram_use"}, "origin": "LOCAL", "event_type": "state_changed", "time_fired": "2016-09-29T15:16:30.851678+00:00"}
Sep 29 11:16:31 raspi1 hass[14895]: DEBUG:homeassistant.components.api:STREAM 1991210648 WRITING data: {"data": {"old_state": {"last_changed": "2016-09-29T15:16:00.722467+00:00", "state": "33.7", "attributes": {"friendly_name": "RAM Use", "unit_of_measurement": "%", "icon": "mdi:memory"}, "last_updated": "2016-09-29T15:16:00.722467+00:00", "entity_id": "sensor.ram_use"}, "new_state": {"last_changed": "2016-09-29T15:16:30.851461+00:00", "state": "34.0", "attributes": {"friendly_name": "RAM Use", "unit_of_measurement": "%", "icon": "mdi:memory"}, "last_updated": "2016-09-29T15:16:30.851461+00:00", "entity_id": "sensor.ram_use"}, "entity_id": "sensor.ram_use"}, "origin": "LOCAL", "event_type": "state_changed", "time_fired": "2016-09-29T15:16:30.851678+00:00"}
Sep 29 11:16:31 raspi1 systemd[1]: home-assistant.service: main process exited, code=killed, status=11/SEGV
Sep 29 11:16:31 raspi1 systemd[1]: Unit home-assistant.service entered failed state.

Man I wish I had waited. I really thought they had this fixed or would not have gone ahead with the new asynch IO in place…

10

This was solved in a later update.