Vera - lights missing

Configuration
1

Just upgraded to 0.47 and it seems that the configuration setting for the Vera component no longer works to specify devices that should be imported as lights. After the upgrade these items were missing entirely from the interface.
Having checked carefully, the Vera device IDs specified as lights aren’t imported at all. If I comment out the line an restart, these devices do get imported as switches [along with all the other Vera devices]. The effect is repeatable by adding or removing the line and restarting Hass and checking in the “<>” section of the developer tools menu.

vera:
  vera_controller_url: http://veraplus.<DOMAIN.TLD>:3480/
  lights: [9, 64, 54, 42, 13, 7, 55]
  exclude: [52, 12, 45, 82, 17, 31, 43, 44, 48, 106, 46, 107, 105, 63, 47, 49, 108, 104, 110, 103]

So I can control the devices if I treat them as switches, but I prefer to have some of these working so they can be dimmed, and anyway I’d have to rewrite all the references in the various groups defined which is not desirable.

2

At least your not alone. I have the exact same problem.

3

Well, after a bit more playing, it seems that the vera device that actually IS a light is detected as such, and ALL the rest are imported as switches - which, I suppose, makes some sense.

It does mean that the documentation page is wrong if that situation is going to persist: there’s no point in specifying “lights”. Including this line just seems to serve the same as exclude.

At what point does this change from a bug to a breaking change?

4

I’m having the same issue with importing switches I like to use as lights.

It is a lot of work to update nu config.

I also would like to know if this is a bug or the documentation is old.

5

Same here. My log shows an exception so this doesn’t seem like expected behavior.

2017-06-21 05:38:44 ERROR (MainThread) [homeassistant.components.light] Error while setting up platform vera
Traceback (most recent call last):
File “/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py”, line 161, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
File “/usr/lib/python3.4/asyncio/tasks.py”, line 372, in wait_for
return fut.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/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/light/vera.py”, line 24, in setup_platform
VeraLight(device, VERA_CONTROLLER) for device in VERA_DEVICES[‘light’])
File “/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py”, line 333, in schedule_add_entities
).result()
File “/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/light/vera.py”, line 24, in
VeraLight(device, VERA_CONTROLLER) for device in VERA_DEVICES[‘light’])
File “/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/light/vera.py”, line 35, in init
VeraDevice.init(self, vera_device, controller)
File “/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/vera.py”, line 144, in init
self.update()
File “/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/light/vera.py”, line 82, in update
self._brightness = self.vera_device.get_brightness()
AttributeError: ‘VeraSwitch’ object has no attribute ‘get_brightness’

6

I updated to 0.47.1 and my lights are back again.

7

Also, resolved by 0.47.1

8

I am also seeing expected behavior. I guess this is Resolved.