0.96: Notion, updated sidebar, advanced mode

Thanks dev for the hard work.
Just a note that the Climate 1.0 seems to be one of the major breaking changes but it’s not listed as such in an appropriate section of the release.
Would be great to do so in the future as not every user reads blogs like this one.

Hi all

I’m experiencing a really strange behaviour while upgrading from 0.96.3 to 0.96.4 on an Intel NUC with Proxmox and with Ubuntu Server as VM OS.

I’ve tried via CLI with hassio ha update after issuing hassio ha check and hassio ha restart and also via Web UI from Settings->General->Restart, but the result is that in Proxmox I get a yellow triangle on the Hassio VM name and the VM hangs and it’s impossible to shutdown.

I always do a daily snapshot of the VM, so I just rolled back, but trying again I get same result.

Anyone with a platform like mine ?

Any suggestion on what to check?

Thanks

Looks like the hard disk of your VM has no space left. Try deleting some data like snapshots and give the VM some more disk space.

1 Like

Thanks @gerard33

You solved my issue, not related to hassio upgrade, but to proxmox.

I have an Envoy-C controller, so I guess I’ll have to wait!

I think my code is good for the c and the s- metered as well. just try the url I put down for resource:

http://envoy/api/v1/production

or try changing envoy to your envoy’s ip address

ERROR: No matching distribution found for homeassistant==0.96.5

This doesn’t look like it supposed to… :woozy_face:
Anyone else getting this?

me too, using pip. Looks like patience is required?

1 Like

Ah d*mn it I tried to find where to buy “patience” they are out of stock.

Hi, I have an issue I do not understand (and cannot find anything similar by searching) - I am running the ‘Check Home Assistant Configuration’ pre upgrade to 0.96.4 and getting the following error:

Failed config
General Errors:
- Platform not found: climate.sensibo

Successful config (partial)

I am currently running Hassio on a RP3 with HA 0.95.4 and have had no troubles with Sensibo previously (and not had the warning pre upgrade before).

Any assistance as to what is causing error is appreciated.

My Sensibo config in configuration.yaml is:

#INTEGRATIONS
#sensibo
climate:
  - platform: sensibo
    api_key: !secret sensiboapi

Full log from the upgrade checker is:

[10:27:29] INFO: Installing Home Assistant: latest…
[10:27:29] INFO: Please be patient, this might take a few minutes…
WARNING: You are using pip version 19.1.1, however version 19.2.1 is available.
You should consider upgrading via the ‘pip install --upgrade pip’ command.
[10:35:34] INFO: Installed Home Assistant 0.96.4
[10:35:34] INFO: Don’t worry, this temporary installation is not overwriting your current one.
[10:35:34] INFO: Making a copy of your configuration for checking…
[10:36:59] INFO: Checking your configuration against this version…
[10:40:28] ERROR: The configuration check did not pass!
[10:40:28] ERROR: See the output below for more details.
INFO:homeassistant.util.package:Attempting install of colorlog==4.0.2
Testing configuration at /tmp/config
INFO:homeassistant.util.package:Attempting install of wakeonlan==1.1.6
INFO:homeassistant.util.package:Attempting install of home-assistant-frontend==20190721.1
INFO:homeassistant.util.package:Attempting install of pywemo==0.4.34
INFO:homeassistant.util.package:Attempting install of aiohttp_cors==0.7.0
INFO:homeassistant.util.package:Attempting install of mutagen==1.42.0
INFO:homeassistant.util.package:Attempting install of sqlalchemy==1.3.5
INFO:homeassistant.util.package:Attempting install of influxdb==5.2.0
Failed config
General Errors:
- Platform not found: climate.sensibo

Successful config (partial)

The sensibo error is a false alarm. It works with 0.96.4

Works now for me.

Hello everyone.

I just realized the update home 096.5 and since then I can not read the temperature sensor DS18b20

when I go to / sys / bus / w1 / devices I can not find my probes anymore,

a little help would not be refu to unlock this conflict thank you in advance friends

Finally I just removed the “dtoverlay = w1-gpio” boot / config.txt followed by a reboot rpi4

then I reactivate dtoverlay = w1-gpio + a reboot and everything came back as before

++ people

I’ve upgraded to 0.96, now on 0.96.4, and nmap_tracker component seems to work fine. However, I still see the error when running the config checker.

Thanks very much - upgrade to 0.96.5 and everything working with Sensibo

Thanks. I’ve done the same now. As you say, the nmap tracker works fine even though the config check fails.

Yep, had exactly these messages aswell,

But I updated anyway, and had no issues with Unify, and SmartIR was fine after the update of that component.

Knotty

1 Like

I have the same issue. Deconz completely unusable. Removed the integration, cannot add it back.
Reverted back to 0.95.4… issue remains… stuck now…

2019-07-27 06:17:06 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py”, line 418, in start
resp = await task
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py”, line 458, in _handle
resp = await handler(request)
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py”, line 119, in impl
return await handler(request)
File “/usr/src/app/homeassistant/components/http/real_ip.py”, line 33, in real_ip_middleware
return await handler(request)
File “/usr/src/app/homeassistant/components/http/ban.py”, line 67, in ban_middleware
return await handler(request)
File “/usr/src/app/homeassistant/components/http/auth.py”, line 216, in auth_middleware
return await handler(request)
File “/usr/src/app/homeassistant/components/http/view.py”, line 115, in handle
result = await result
File “/usr/src/app/homeassistant/components/config/config_entries.py”, line 119, in post
return await super().post(request)
File “/usr/src/app/homeassistant/components/http/data_validator.py”, line 46, in wrapper
result = await method(view, request, *args, **kwargs)
File “/usr/src/app/homeassistant/helpers/data_entry_flow.py”, line 57, in post
handler, context={‘source’: config_entries.SOURCE_USER})
File “/usr/src/app/homeassistant/data_entry_flow.py”, line 71, in async_init
return await self._async_handle_step(flow, flow.init_step, data)
File “/usr/src/app/homeassistant/data_entry_flow.py”, line 123, in _async_handle_step
result = await getattr(flow, method)(user_input) # type: Dict
File “/usr/src/app/homeassistant/components/deconz/config_flow.py”, line 76, in async_step_user
self.bridges = await async_discovery(session)
File “/usr/local/lib/python3.7/site-packages/pydeconz/utils.py”, line 66, in async_discovery
response = await async_request(session.get, URL_DISCOVER)
File “/usr/local/lib/python3.7/site-packages/pydeconz/utils.py”, line 91, in async_request
“Invalid content type: {}”.format(res.content_type))
pydeconz.errors.ResponseError: Invalid content type: text/html

reply to self… my issue with Deconz is fixed. RC was that https://dresden-light.appspot.com/discover was unreachable… its up now. re-added Deconz integration. all fine now