I’ve these problems and i have no idea sometimes it works sometimes i get this:
16-11-08 18:31:14 homeassistant.components.climate: Error while setting up platform zwave
Traceback (most recent call last):
File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 148, in _async_setup_platform
entity_platform.add_entities, discovery_info
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/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/climate/zwave.py", line 67, in setup_platform
add_devices([ZWaveClimate(value, temp_unit)])
File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/climate/zwave.py", line 95, in __init__
self.update_properties()
File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/climate/zwave.py", line 171, in update_properties
self._target_temperature = int(self._current_temperature)
TypeError: int() argument must be a string or a number, not 'NoneType'
Do you have some configuration to post with this? Somewhere in your setup that you reference climate (other than its ocnfiguration setup)?
Sometimes, if you check the status of a sensor before it’s defined, you’ll get an error (you can test that in your template language to make sure the sensor exists first).
That didn’t correspond to a time when one of these automations triggered - did the error happen at startup? Or when you tried to set the heat via the HASS web interface? Or was it just random?
Just checking - the plugin uses “termostat” instead of “thermostat” when it creates entities? Or is that named derived from your OpenZwave settings?
16-11-09 14:02:37 homeassistant.components.climate: Error while setting up platform zwave
Traceback (most recent call last):
File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 148, in _async_setup_platform
entity_platform.add_entities, discovery_info
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/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/climate/zwave.py", line 67, in setup_platform
add_devices([ZWaveClimate(value, temp_unit)])
File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/climate/zwave.py", line 95, in __init__
self.update_properties()
File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/climate/zwave.py", line 171, in update_properties
self._target_temperature = int(self._current_temperature)
TypeError: int() argument must be a string or a number, not 'NoneType'
That appears to be a problem with the thermostat’s set point. I don’t have one of these, so I’m not sure how they behave, but do you have a way to configure a set point within HASS?
Right. The component calls it “setpoint”, but I imagine that means the target temperature. That error you’re getting happens when COMMAND_CLASS_THERMOSTAT_SETPOINT returns a zero.
16-11-11 17:09:44 homeassistant.components.climate: Error while setting up platform zwave
Traceback (most recent call last):
File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 148, in _async_setup_platform
entity_platform.add_entities, discovery_info
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/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/climate/zwave.py", line 67, in setup_platform
add_devices([ZWaveClimate(value, temp_unit)])
File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/climate/zwave.py", line 95, in __init__
self.update_properties()
File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/climate/zwave.py", line 171, in update_properties
self._target_temperature = int(self._current_temperature)
TypeError: int() argument must be a string or a number, not 'NoneType'
if i start openzwave control panel and Initialize it, and then shut it down and start ha it works strange?
Ok. Your node is not fully initialized to the zwave network.
Here is what you should do:
Stop Hass.
Open up ozwcp, and wait until Node status(rightmost text in the node list) for the node have Ready as text. If it is stuck at Probe og Sleeping, wake the device as per user manual. Repeat this until Status is Ready.
Then hit the save button on top in ozwcp.
Close connection and exit ozwcp and copy the zwcfg_[home_id].xml from the ozwcp directory into hass’s config dir.
Start Hass.
That image shows that things are now OK. If you can see all config parameters node is completely initialized.
You can safely reboot the pi now with the new file in place. But I would recommend that HASS is shut down first, because that file is saved on each shutdown of HASS too.
