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
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?
Is the entity registry automatically created by home assistant when one updates to this version?
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.
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.
Not had any errors using MQTT and I use it a lot as I have statestream and various MQTT devices.
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…OK, well that might explain it then I don’t use ssl or an external broker 
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 :).
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.
Seems like something went wrong when the frontend was being downloaded. Remove your <config>/deps folder.
I’ve got the same issue and removing config/deps and restarting didn’t do the trick… Any other ideas?
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
Reverted to 0.63.2 and the problem is gone.
I also reverted to previous version. I tried to delete deps-folder but it didn`t help.