Thanks. I’ve just made the leap and as you said everything is working as expected. Just had to update SmartIR.
I wonder if SmartIR is throwing out the testing as it’s not up to a compatible version.
I really like the improvements on the UI but I loved the hidden sidebar on desktop and on tables in landscape mode. I prefer to make it configurable.
As of 0.96.3 it is configurable. Look under your profile.
Such a cool project, BUT I can’t count how often I’ve had to re-do my configuration because things break in obscure ways (and yes, I always read the “breaking changes” section). Too bad I don’t have the time to do this over, and over again, so what used to be a pretty awesome HASS setup I had to reduce to just controlling my zwave devices, and only automating my porch lights. Stuff just breaks way too frequently, and usually in difficult to diagnose ways. Just my 2ct…
1 Like
I think this is a situation where you have to give the Devs a massive break. HA isn’t even version 1.0 yet, you have to expect there to be some breakage along the way. Things are contributed from a lot of people and things end up evolving, the odd tweak here, the odd addition there and before you know it a platform is way out of hand, and so to ensure that things are more stable and maintainable moving forward I think its only right that any major pain in aligning them to a design standard should happen before we hit 1.0.
The devs all put in so much time, effort and passion, they often have some hard choices to make, do they always get them right, no, on occasion like everyone there will be a little misstep, but on the whole I think we should all be pretty grateful, as without their sometime thankless efforts we wouldn’t even have a project or community and life would just be that little bit harder and hold a little less joy for us all.
So even though I was one of the people who didn’t like the way the new menu worked (and still not 100% on the updated functionality I much preferred the old method), I still appreciate the efforts of devs like @balloob, @frenck, @pvizeli, @OttoWinter and countless others contributors (who I am sorry the names of do not spring to mind) to you all a big 
and a 
thank-you
9 Likes
Yep for open source software it’s pretty amazing that something with so many components and configurations works as well as it does.
Sure it’s not perfect, and things will break along the way, but issues are usually fixed or a workaround is found.
Also both positive and negative feedback, as long as it’s constructive, is important IMO. For example not everyone is a fan of the new sidebar but I’m glad people can give their opinion, and we now have the option of setting is back to the old way.
If no one said anything we would would not have had happen, and it’s great also to see the devs using the feedback. 
Not disagreeing, it’s pretty awesome work, especially considering it’s all free and open. I do realize it’s not even 1.0 yet. And yes, of course, a big thank you to all contributors and developers, it’s pretty awesome work. Just wish it wasn’t as brittle. I quite enjoy using HASS, but I feel like I have to stick to a version almost forever and only do an upgrade expecting that I have to re-do my entire setup each and every time.
I don’t find it brittle. I update at version .0, ie no waiting for .1 around here. It never seems to break. Bloody fantastic.
I upgraded from 0.96.3 to .5 and Hass.io on vm broke.
Logs show:
2019-07-27 14:51:52 ERROR (MainThread) [homeassistant.components.switch] homekit_controller: Error on device update!
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 261, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 378, in async_device_update
await self.async_update()
File "/usr/src/homeassistant/homeassistant/components/homekit_controller/__init__.py", line 103, in async_update
self._chars_to_poll
File "/usr/src/homeassistant/homeassistant/components/homekit_controller/connection.py", line 193, in get_characteristics
**kwargs,
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/homekit/controller/ip_implementation.py", line 172, in get_characteristics
self.session = IpSession(self.pairing_data)
File "/usr/local/lib/python3.7/site-packages/homekit/controller/ip_implementation.py", line 416, in __init__
c2a_key, a2c_key = get_session_keys(conn, pairing_data, write_fun)
File "/usr/local/lib/python3.7/site-packages/homekit/protocol/__init__.py", line 311, in get_session_keys
response_tlv = write_fun(request_tlv, step2_expectations)
File "/usr/local/lib/python3.7/site-packages/homekit/protocol/__init__.py", line 79, in write_http
connection.endheaders(request)
File "/usr/local/lib/python3.7/http/client.py", line 1239, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.7/site-packages/homekit/http_impl/http_client.py", line 44, in _send_output
self.send(msg)
File "/usr/local/lib/python3.7/http/client.py", line 966, in send
self.connect()
File "/usr/local/lib/python3.7/http/client.py", line 938, in connect
(self.host,self.port), self.timeout, self.source_address)
File "/usr/local/lib/python3.7/socket.py", line 727, in create_connection
raise err
File "/usr/local/lib/python3.7/socket.py", line 716, in create_connection
sock.connect(sa)
TimeoutError: [Errno 110] Operation timed out
Yeah, I’ve been fortunate to not have issues with upgrades either, though I do generally wait for .1 releases. @tomuta, are there particular specific components that seem to break for you each time you upgrade?
I had to delete .storage/homekit_controller-entity-map
I have 2 z wave thermostats. Does this change affect me? If it’s already been asked I’m sorry so please enlighten me. 
It affects every climate integration, so the answer is yes.
Edit: for everyone’s benefit the discussion of the climate change, with a list of integrations which have been updated is here Climate 1.0 by pvizeli · Pull Request #23899 · home-assistant/core · GitHub
However that list will not include custom components that have been updated. I am pretty sure the list in the PR will only be for integrations that are in core.
I have to delete .storage/homekit_controller-entity-map every time I reboot Home Assistant (if the file exists) otherwise I end up with TimeoutError: [Errno 110] Operation timed out
To be taken with a measure of salt. The MQTT climate integration is checked off but, after trying it in 0.96.x, it’s only partially converted.
One of the main features of Climate 1.0 is the separation of operation mode and operating state. That important feature is missing in MQTT HVAC (but a PR was recently accepted so the feature will probably become available in 0.97). In addition, it doesn’t handle the new preset_modes correctly (an issue I intend to post in GitHub).
Other climate platforms have had similar, ‘feature-is-only-partially-implemented’ issues (notably Ecobee). I imagine it’ll take another version or two before it’s all sorted out.
Netatmo thermostat error
2019-07-28 15:47:02 ERROR (MainThread) [homeassistant.components.climate] Error while setting up platform netatmo
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
SLOW_SETUP_MAX_WAIT)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/netatmo/climate.py", line 128, in setup_platform
for room_id in room_data.get_room_ids():
File "/usr/src/homeassistant/homeassistant/components/netatmo/climate.py", line 397, in get_room_ids
if not self.setup():
File "/usr/src/homeassistant/homeassistant/components/netatmo/climate.py", line 408, in setup
self.homestatus = pyatmo.HomeStatus(self.auth, home=self.home)
File "/usr/local/lib/python3.7/site-packages/smart_home/Thermostat.py", line 152, in __init__
raise NoDevice("No device found, errors in response")
smart_home.NoDevice: No device found, errors in response
Error with the NETATMO device - internal device with unrealistic temperature …
I had to go back to version 0.95
the device through netatmo application results at a lower 3 ° temperature, the value returned by homassistant is probably a value the maximum temperature and not the one in real time
Thanks! I went to the link however I can’t see how to fix this breaking change. Should I just simply delete my entities and delete them from my z wave stick and re add them? I’m sorry if I have overlooked this.
Could you please open an issue on Gihub or at least provide further information in a separate thread?
The only thing you’ll need to update are any automations or scripts that may use the former operation_mode service call vs the new hvac_mode as well as set_away_mode and set_hold_mode they changed to set_preset_mode.