8000 Vera import switches as lights no longer working in 0.47 · Issue #8098 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Vera import switches as lights no longer working in 0.47 #8098

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ghost opened this issue Jun 18, 2017 · 0 comments · Fixed by #8101
Closed

Vera import switches as lights no longer working in 0.47 #8098

ghost opened this issue Jun 18, 2017 · 0 comments · Fixed by #8101

Comments

@ghost
Copy link
ghost commented Jun 18, 2017

HASS 0.47

Python release (python3 --version):
Python 3.5.2

Component/platform:
Vera

Description of problem:
After upgrade from 0.45 to 0.47 the vera configuration in configuration.yaml to import switches as lights is no longer working. Getting error messages in log related to "AttributeError: 'VeraSwitch' object has no attribute 'get_brightness'"

Expected:
To import switches as lights by adding below list of vera device ids underneath the vera configuration:
lights: [ 5, 16, 18, 21, 33, 39, 41, 42, 51]

Problem-relevant configuration.yaml entries and steps to reproduce:

vera:
  vera_controller_url: http://x.x.x.x:3480
  # Exclude devices - this is a list of vera device ids
  exclude: [ 9, 17, 22, 23]
  # Import switches as lights - this is a list of vera device ids
  lights: [ 5, 16, 18, 21, 33, 39, 41, 42, 51]```

1. 
2. 
3. 

**Traceback (if applicable):**
```bash
2017-06-18 22:21:50 ERROR (Vera Poll Thread) [pyvera.subscribe] Vera thread exce
ption 'VeraSwitch' object has no attribute 'get_brightness'
Traceback (most recent call last):
File "/home/homeassistant/.homeassistant/deps/pyvera/subscribe.py", line 129, 
in _run_poll_server
self._event(device_data)
File "/home/homeassistant/.homeassistant/deps/pyvera/subscribe.py", line 59, i
n _event
self._event_device(device, device_data)
File "/home/homeassistant/.homeassistant/deps/pyvera/subscribe.py", line 96, i
n _event_device
callback(device)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/
vera.py", line 148, in _update_callback
self.update()
File "/srv/homeassistant/lib/python3.5/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'
2017-06-18 22:21:55 INFO (Thread-1) [homeassistant.components.vera] Shutting dow
n subscriptions```

**Additional info:**
tsvi added a commit to tsvi/home-assistant that referenced this issue Jun 19, 2017
@tsvi tsvi mentioned this issue Jun 19, 2017
2 tasks
pvizeli pushed a commit that referenced this issue Jun 19, 2017
* Fix lights issue #8098

* Don't check self._color to decide whether to calll get_color()

self._color is None on init, so get_color() will never be called.
balloob pushed a commit that referenced this issue Jun 21, 2017
* Fix lights issue #8098

* Don't check self._color to decide whether to calll get_color()

self._color is None on init, so get_color() will never be called.
@balloob balloob mentioned this issue Jun 21, 2017
@balloob balloob mentioned this issue Jul 1, 2017
dethpickle pushed a commit to dethpickle/home-assistant that referenced this issue Aug 18, 2017
* Fix lights issue home-assistant#8098

* Don't check self._color to decide whether to calll get_color()

self._color is None on init, so get_color() will never be called.
@home-assistant home-assistant locked and limited conversation to collaborators Oct 20, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

0 participants
2A6C
0