gohassgo

Another boatload of changes! Awesome!

Regarding this one…
zha: Add support for XBee radios (@rcloran - #12205)

If I read this correctly, you can only use one radio type at a time. Correct?

Thanks!

jimbob1001

Should the entity registry ignore entity_namespace? (I am using entity_namespace to append “plex” & “sonos” to media_players but this was ignored by the entity registry)

Also, in hue I use the setting to allow_hue_groups and although they show as entities in the frontend these groups don’t show up in the registry - wondered if that’s expected behaviour?

Great work as always,
Thanks,
James

1 reply

elRadix

Nice update, just tested the mercedes me component. Seems there is couple issues/bug?

The latest trip information is reporting strange number. Also the fuel range is not reporting any data.

1 reply

syphernl

Seems like this release broke OpenZWave, according to this issue. I’m seeing the same here, with both Python 3.5 and 3.6.

4 replies

ReneNulschDE

hi,

thanks for testing this.

The shown number is the latest trip id. I’ve used this as a “travel book” in the last month and not as a real indicator. If you would like to get the “distance traveled” you could use a template sensor

For the fuel range issue, could you please click here, logon with your mercedesme account and search for fuelRangeKm.

Thanks for your feedback and help to make this component better.

BR
Rene

1 reply

elRadix

How do use the travel book in general?

Ok, logged on, strange that it’s not reporting the value in the api:
“fuelRangeKm”:"NOT_PRESENT
“fuelRangeKm”:null

Can you make like a formula to calculate based on the latest consumption data if data is ‘not_present’ or ‘null’?
“liquidConsumptionReset”: 7.599999904632568,
“liquidConsumptionStart”: 8.800000190734863,

1 reply

broesie

No problem with z-wave here, running hass.io…

balloob Founder of Home Assistant

I’ll add a fix to make sure we can register them taking entity namespace into consideration. For the ones that are already registered you’ll need to update the entity id yourself.

If it doesn’t work for Hue groups, it means that we don’t have a unique ID set for them yet.

cooldog

Same here. openZwave is broken. Reinstalling the previous version now.

ReneNulschDE

Hi,

I’m exporting the results out of the states table currently.

Example: select state, attributes, last_changed from states where entity_id = 'sensor.latest_trip' group by state

The idea for the future is:

• Have an automation that fires an event after a trip has completed.
• Collect the GPS information out of the database for the start and end time
• reverse lookup the address for start and end
• take the information and add a line in a google sheet

To the fuelRange problem:

• in the next version I’ll check availabilities and hide unavailable sensors
• could you please explain your formula idea a little bit?

Thx
Rene

ghvader

no issues with open zwave on a raspbian install coming from 0.61

clyra

Hi there,

Thanks for another version, and this one fixed the xiaomi power strip. Great. But I did find something like a breaking changing: I use to write my automations directly by editing files in a automation folder and use to write a file for each xiaomi wireless button that I have. So, I ended with a few automations with the same alias, like “toggle hall light” for the single click of the buttons on each end of the hall. After upgrading to the 0.63 some of these automations just stopped to work!

After a lot of checks of buttons, batteries, etc, I thougth about the entity registry thing and had the idea of adding unique IDs for each automation with the “id:” and it seems to solve the problem (there was one that I had to change the alias too, but I’m not sure… should be another mistake). Should a note be added to the breaking changes?

Tinkerer Solution Institution

Possibly it’s due to the cython package being missing - others have reported it as a hidden error. Try activating the venv and doing pip install cython.

1 reply

syphernl

Unfortunately Cython is not missing. If I remove all “zwave” files from the libs, HA installs them and I don’t see any difference between those used by 0.62.1 and 0.63

Edit:
For some reason, if I do a make update && make build && make install-api on the python-openzwave checkout (with my venv active) it is working just fine.

pejotigrek

is it me, or xiaomi vacuum still doesn’t work?

3 replies

oakbrad

My Xiaomi vacuum is not working either. Downgrading back to .60 right now. Same error as others here

TypeError: subcon should be a Construct field

No problems with zwave though.

edit: and after downgrading, it’s back

diogos88

It’s working well for me. Upgraded from 0.62.1 (which didn’t worked) to 0.63.

1 reply

pejotigrek

I also came from 0.62.1, but can’t discover the vacuum now [I also couldn’t on 0.62.1].
I’m assuming that you did not change anything in configuration? just plain update and it works out-of-the-box?

1 reply

itchaboy

Xiaomi purifier and vacuum both not working here either 0.63

2018-02-11 18:39:28 ERROR (MainThread) [homeassistant.components.vacuum] Error while setting up platform xiaomi_miio
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 84, in async_setup
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
    return fut.result()
  File "/usr/lib/python3.6/asyncio/futures.py", line 245, in result
    raise self._exception
  File "/usr/lib/python3.6/asyncio/tasks.py", line 180, in _step
    result = coro.send(None)
  File "/usr/lib/python3.6/asyncio/coroutines.py", line 210, in coro
    res = func(*args, **kw)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/vacuum/xiaomi_miio.py", line 90, in async_setup_platform
    from miio import Vacuum
  File "/usr/lib/python3.6/site-packages/miio/__init__.py", line 2, in <module>
    from miio.protocol import Message, Utils
  File "/usr/lib/python3.6/site-packages/miio/protocol.py", line 179, in <module>
    Const(0x2131, Int16ub),
  File "/usr/lib/python3.6/site-packages/construct/core.py", line 1894, in __init__
    super(Const, self).__init__(subcon)
  File "/usr/lib/python3.6/site-packages/construct/core.py", line 291, in __init__
    raise TypeError("subcon should be a Construct field")
TypeError: subcon should be a Construct field

jkvalence

Zoneminder not working on 0.63 as docker container

Error while setting up platform zoneminder
Traceback (most recent call last):
File “/usr/src/app/homeassistant/helpers/entity_platform.py”, line 84, in async_setup
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/local/lib/python3.6/asyncio/tasks.py”, line 358, in wait_for
return fut.result()
File “/usr/local/lib/python3.6/asyncio/futures.py”, line 243, in result
raise self._exception
File “/usr/local/lib/python3.6/asyncio/tasks.py”, line 180, in _step
result = coro.send(None)
File “/usr/local/lib/python3.6/asyncio/coroutines.py”, line 212, in coro
res = func(*args, **kw)
File “/usr/src/app/homeassistant/components/camera/zoneminder.py”, line 56, in async_setup_platform
monitors = zoneminder.get_state(‘api/monitors.json’)
File “/usr/src/app/homeassistant/components/zoneminder.py”, line 124, in get_state
return _zm_request(‘get’, api_url)
File “/usr/src/app/homeassistant/components/zoneminder.py”, line 104, in _zm_request
cookies=ZM[‘cookies’], timeout=DEFAULT_TIMEOUT)
KeyError: ‘cookies’

1 reply

mrlime

Getting the same zoneminder errors in Ubuntu with python 3.5.

aswieton

It’s not working for me too. Still the same error.

matchett808

My custom components are loosing their friendly name (and other attributes) have I missed a breaking change?

Initially came from 0.61, but works fine on 0.62.1

toonazd

Limitless led not working after update, not showing on frontend.

1 reply

apt

Netatmo weather station not working after 0.63.x update.

Error while setting up platform netatmo
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/helpers/entity_platform.py", line 84, in async_setup
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 243, in result
    raise self._exception
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/app/homeassistant/components/camera/netatmo.py", line 42, in setup_platform
    for camera_name in data.get_camera_names():
  File "/usr/src/app/homeassistant/components/netatmo.py", line 84, in get_camera_names
    self.update()
  File "/usr/src/app/homeassistant/util/__init__.py", line 306, in wrapper
    result = method(*args, **kwargs)
  File "/usr/src/app/homeassistant/components/netatmo.py", line 115, in update
    self.camera_data = lnetatmo.CameraData(self.auth, size=100)
  File "/usr/local/lib/python3.6/site-packages/smart_home/Camera.py", line 78, in __init__
    self.default_camera = list(self.cameras[self.default_home].values())[0]
IndexError: list index out of range

1 reply

balloob Founder of Home Assistant

The errors is raised inside the constructor of the netatmo package

1 reply

balloob Founder of Home Assistant

Limitless led should be fixed in 0.63.1

1 reply

apt

What can be done to fix it?

1 reply

balloob Founder of Home Assistant

Someone that has netatmo gear should see what is wrong and fix it?

2 replies

apt

I have Kit.

It was working fine prior to 0.63.x, whats changed?

milras

Unfortunately the xiaomi wifi plugs are still not working since version 61.1:

2018-02-12 23:21:48 WARNING (MainThread) [homeassistant.components.recorder] From version 0.64.0 the ‘recorder’ component will by default purge data older than 10 days. To keep data longer you must configure ‘purge_keep_days’ or ‘purge_interval’.
2018-02-12 23:22:07 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform efergy is taking over 10 seconds.
2018-02-12 23:22:07 ERROR (MainThread) [homeassistant.components.switch] Error while setting up platform xiaomi_miio
Traceback (most recent call last):
File “/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py”, line 84, in async_setup
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/lib/python3.6/asyncio/tasks.py”, line 358, in wait_for
return fut.result()
File “/usr/lib/python3.6/asyncio/futures.py”, line 245, in result
raise self._exception
File “/usr/lib/python3.6/asyncio/tasks.py”, line 180, in _step
result = coro.send(None)
File “/usr/lib/python3.6/asyncio/coroutines.py”, line 210, in coro
res = func(*args, **kw)
File “/usr/lib/python3.6/site-packages/homeassistant/components/switch/xiaomi_miio.py”, line 41, in async_setup_platform
from miio import Device, DeviceException
File “/usr/lib/python3.6/site-packages/miio/init.py”, line 2, in
from miio.protocol import Message, Utils
File “/usr/lib/python3.6/site-packages/miio/protocol.py”, line 179, in
Const(0x2131, Int16ub),
File “/usr/lib/python3.6/site-packages/construct/core.py”, line 1894, in init
super(Const, self).init(subcon)
File “/usr/lib/python3.6/site-packages/construct/core.py”, line 291, in init
raise TypeError(“subcon should be a Construct field”)
TypeError: subcon should be a Construct field
2018-02-12 23:22:08 ERROR (MainThread) [homeassistant.components.switch] Error while setting up platform xiaomi_miio
Traceback (most recent call last):
File “/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py”, line 84, in async_setup
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/lib/python3.6/asyncio/tasks.py”, line 358, in wait_for
return fut.result()
File “/usr/lib/python3.6/asyncio/futures.py”, line 245, in result
raise self._exception
File “/usr/lib/python3.6/asyncio/tasks.py”, line 180, in _step
result = coro.send(None)
File “/usr/lib/python3.6/asyncio/coroutines.py”, line 210, in coro
res = func(*args, **kw)
File “/usr/lib/python3.6/site-packages/homeassistant/components/switch/xiaomi_miio.py”, line 41, in async_setup_platform
from miio import Device, DeviceException
File “/usr/lib/python3.6/site-packages/miio/init.py”, line 2, in
from miio.protocol import Message, Utils
File “/usr/lib/python3.6/site-packages/miio/protocol.py”, line 179, in
Const(0x2131, Int16ub),
File “/usr/lib/python3.6/site-packages/construct/core.py”, line 1894, in init
super(Const, self).init(subcon)
File “/usr/lib/python3.6/site-packages/construct/core.py”, line 291, in init
raise TypeError(“subcon should be a Construct field”)
TypeError: subcon should be a Construct field

Per4merKC

So is it safe to check the entity_registry.yaml into GitHub? Is there a security concern here or are these IDs unique to my system?

diogos88

I did not changed my configuration. I just upgraded from 0.62.1 and it worked.

Jelob

Limitless led still doesn’t work in 0.63.1

apt

The following fixed the issue with Netatmo. Wasn’t aware needed to remove entities from the new entity_registry.yaml

https://github.com/home-assistant/home-assistant/issues/12355#issuecomment-365375135

Valiceemo

Also having problems with Limitless led component having upgraded to 0.63.1

1 reply

Dissi

Update seems to broke up the aiohttp again.
Tryed the version aiohttp-3.0.1 and aiohttp-2.3.10.

Any ideas?

2018-02-14 11:56:59 ERROR (MainThread) [homeassistant.loader] Error loading homeassistant.components.history. Make sure all dependencies are installed
Traceback (most recent call last):
File “/usr/local/lib/python3.5/dist-packages/homeassistant/loader.py”, line 142, in get_component
module = importlib.import_module(path)
File “/usr/lib/python3.5/importlib/init.py”, line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File “”, line 986, in _gcd_import
File “”, line 969, in _find_and_load
File “”, line 958, in _find_and_load_unlocked
File “”, line 673, in _load_unlocked
File “”, line 673, in exec_module
File “”, line 222, in _call_with_frames_removed
File “/usr/local/lib/python3.5/dist-packages/homeassistant/components/history.py”, line 20, in
from homeassistant.components.http import HomeAssistantView
File “/usr/local/lib/python3.5/dist-packages/homeassistant/components/http/init.py”, line 15, in
from aiohttp import web
File “/root/.homeassistant/deps/lib/python3.5/site-packages/aiohttp/web.py”, line 15, in
from . import (hdrs, web_exceptions, web_fileresponse, web_middlewares,
File “/root/.homeassistant/deps/lib/python3.5/site-packages/aiohttp/web_middlewares.py”, line 5, in
from aiohttp.web_urldispatcher import SystemRoute
File “/root/.homeassistant/deps/lib/python3.5/site-packages/aiohttp/web_urldispatcher.py”, line 21, in
from yarl import URL, unquote
ImportError: cannot import name ‘unquote’
2018-02-14 11:56:59 ERROR (MainThread) [homeassistant.loader] Unable to find component history
2018-02-14 11:56:59 ERROR (MainThread) [homeassistant.setup] Setup failed for history: Component not found.
2018-02-14 11:56:59 ERROR (MainThread) [homeassistant.loader] Error loading homeassistant.components.frontend. Make sure all dependencies are installed
Traceback (most recent call last):
File “/usr/local/lib/python3.5/dist-packages/homeassistant/loader.py”, line 142, in get_component
module = importlib.import_module(path)
File “/usr/lib/python3.5/importlib/init.py”, line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File “”, line 986, in _gcd_import
File “”, line 969, in _find_and_load
File “”, line 958, in _find_and_load_unlocked
File “”, line 673, in _load_unlocked
File “”, line 673, in exec_module
File “”, line 222, in _call_with_frames_removed
File “/usr/local/lib/python3.5/dist-packages/homeassistant/components/frontend/init.py”, line 14, in
from aiohttp import web
File “/root/.homeassistant/deps/lib/python3.5/site-packages/aiohttp/web.py”, line 15, in
from . import (hdrs, web_exceptions, web_fileresponse, web_middlewares,
File “/root/.homeassistant/deps/lib/python3.5/site-packages/aiohttp/web_middlewares.py”, line 5, in
from aiohttp.web_urldispatcher import SystemRoute
File “/root/.homeassistant/deps/lib/python3.5/site-packages/aiohttp/web_urldispatcher.py”, line 21, in
from yarl import URL, unquote
ImportError: cannot import name ‘unquote’
2018-02-14 11:56:59 ERROR (MainThread) [homeassistant.loader] Unable to find component frontend

broesie

In 0.63.2 limitless is downgraded to 1.0.8…

1 reply

Valiceemo

yes I know.
I posted this before the upgrade to 0.63.2 was released.

thanks

Ivan711

Oh…
Beginning with version 0.62 Mirobo/xiaomi-philips don’t work.
[homeassistant.components.vacuum.xiaomi_miio] Got exception while fetching the state: Unable to discover the device 192.168.1.10
[miio.device] error while reading discover results: _decode() takes 3 positional arguments but 4 were given

simonhq

Since moving to 0.63.2 this morning, I now have an entity_registry.yaml file with my hue lights in it, but none of those lights are now available in the states view (and thus I can’t see or interact with them, breaking my groups, automations etc.) was I suppose to add anything new to configuration to make these visible?

Dolores

Is the entity registry automatically created by home assistant when one updates to this version?

keithh666

I know this is a strange question but is BLE tracking ever going to work on HA?

In my experience it hasn’t worked for 8months+, it doesn’t work on AIO, Hassbian, HASS.IO or Win 10, gattlib fails to load no matter what platform I use, maybe it’s just my hardware but I don’t think so.

agent_kith

MQTT, XiaoMi Vacuum and XiaoMi fan not working after upgrading from 63.2 to 63.3. Anybody facing the same issues?

I have downgraded back to 63.2. XiaoMi fan & Vacuum works again, but MQTT is still not working. Later today I’m going to wipe out my virtualenv seutp and reinstall 63.3 fresh and see if that works better.

1 reply

keithh666

Not had any errors using MQTT and I use it a lot as I have statestream and various MQTT devices.

1 reply

agent_kith

Strange… I’m getting a SSL error when connecting to my CloudMQTT instance. HomeAssistant can’t connect, but my android client works. CloudMQTT port isn’t blocked (I can telnet to it).

Error during setup of component mqtt

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/setup.py", line 145, in _async_setup_component
    result = yield from component.async_setup(hass, processed_config)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/mqtt/__init__.py", line 399, in async_setup
    success = yield from hass.data[DATA_MQTT].async_connect()
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/mqtt/__init__.py", line 506, in async_connect
    self._mqttc.connect, self.broker, self.port, self.keepalive)
  File "/usr/lib/python3.5/asyncio/futures.py", line 361, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.5/asyncio/tasks.py", line 296, in _wakeup
    future.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 274, in result
    raise self._exception
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.5/site-packages/paho/mqtt/client.py", line 768, in connect
    return self.reconnect()
  File "/srv/homeassistant/lib/python3.5/site-packages/paho/mqtt/client.py", line 927, in reconnect
    sock.do_handshake()
  File "/usr/lib/python3.5/ssl.py", line 988, in do_handshake
    self._sslobj.do_handshake()
  File "/usr/lib/python3.5/ssl.py", line 633, in do_handshake
    self._sslobj.do_handshake()
socket.timeout: _ssl.c:629: The handshake operation timed out

Connection lost. Reconnecting…

1 reply

keithh666

OK, well that might explain it then I don’t use ssl or an external broker

1 reply

agent_kith

Thanks keithh666…

Wiped my /srv/homeassistant folder, and created a new virtualenv… Installed a fresh copy of 63.3, both MQTT and XiaoMi is working (and so is everything else).

Not too sure what happens when I upgraded from .2 to .3… But thankfully a fresh 63.3 instance fixed it all :).

Peltsi

Hi all!

I am a newbie here and after 0.63.3 update I can`t reach frontend. It gives me 404 error.

I found this from log:

2018-02-22 19:37:21 ERROR (MainThread) [homeassistant.setup] Error during setup of component frontend
Traceback (most recent call last):
File “/usr/lib/python3.6/site-packages/homeassistant/setup.py”, line 145, in _async_setup_component
result = yield from component.async_setup(hass, processed_config)
File “/usr/lib/python3.6/site-packages/homeassistant/components/frontend/init.py”, line 319, in async_setup
import hass_frontend
ValueError: source code string cannot contain null bytes

I am very thankful if someone could give me a hint what is wrong with this.

2 replies

balloob Founder of Home Assistant

Seems like something went wrong when the frontend was being downloaded. Remove your <config>/deps folder.

ZyberSE

I’ve got the same issue and removing config/deps and restarting didn’t do the trick… Any other ideas?

1 reply

balloob Founder of Home Assistant

If you’re running Home Assistant in a virtual environment, try this:

# activate the virtual environment
source bin/activate
# Remove frontend package
pip3 uninstall home-assistant-frontend==20180209.0

1 reply

ZyberSE

I’m running hass.io

ZyberSE

Reverted to 0.63.2 and the problem is gone.

Peltsi

I also reverted to previous version. I tried to delete deps-folder but it didn`t help.