Julius2342 / pyvlx

PyVLX - controling VELUX windows with Python via KLF 200
GNU Lesser General Public License v3.0
74 stars 26 forks source link

nodes.py - TypeError #17

Closed gibman closed 5 years ago

gibman commented 5 years ago

Hi running hass.io 0.89.1 with a klf 200 unit with the latest firmware. (I just bought the unit :=)

I have various products setup in the velux webinterface.

It seems it wont load up properly in hass.io.

hass.io configuration.yaml

velux: host: "192.168.1.123" password: "wifipass"

hass.io logs:

[homeassistant.setup] Error during setup of component velux Traceback (most recent call last): File “/usr/local/lib/python3.7/site-packages/homeassistant/setup.py”, line 151, in _async_setup_component hass, processed_config) File “/usr/local/lib/python3.7/site-packages/homeassistant/components/velux/init.py”, line 30, in async_setup await hass.data[DATA_VELUX].async_start() File “/usr/local/lib/python3.7/site-packages/homeassistant/components/velux/init.py”, line 57, in async_start await self.pyvlx.load_nodes() File “/usr/local/lib/python3.7/site-packages/pyvlx/pyvlx.py”, line 83, in load_nodes await self.nodes.load(node_id) File “/usr/local/lib/python3.7/site-packages/pyvlx/nodes.py”, line 70, in load await self._load_all_nodes() File “/usr/local/lib/python3.7/site-packages/pyvlx/nodes.py”, line 91, in _load_all_nodes self.add(node) File “/usr/local/lib/python3.7/site-packages/pyvlx/nodes.py”, line 54, in add raise TypeError() TypeError

I'd be glad to help you out in debugging this :)

Julius2342 commented 5 years ago

This should be fixed if you run latest pyvlx (which was also merged last weekend in current dev branch of home assistant). May you retry?

gibman commented 5 years ago

I'd like to :).

No idea how to update pyvlx on the hass.io device. If you could give me some directions ?

Julius2342 commented 5 years ago

No idea, i just run a development environment. You could just edit the dependency within velux/__init__.py. Or just wait for the next release ...

gibman commented 5 years ago

Ok- Im up and running with the latest code 0.2.10

The problem is indeed fixed as you said.