All worked fine for me except for Netatmo that throws this error (only connecting to my local station via the api).
Cannot find any “Breaking changes” that relates to configuration changes between 0.92.2 and 0.93.0.
The error: 2019-05-16 09:01:28 ERROR (SyncWorker_29) [homeassistant.components.netatmo.sensor] No Weather or HomeCoach devices found for None
Anyone else experimenting the same issue?
1 reply
@Danielhiversen Thanks for the update with switchbot.
After updating to 0.93, switchbot has stopped working completely and it throws an error saying:
2019-05-16 08:42:43 WARNING (SyncWorker_5) [switchbot] Failed to connect to Switchbot
Traceback (most recent call last):
File "/config/deps/lib/python3.7/site-packages/switchbot/__init__.py", line 35, in _connect
bluepy.btle.ADDR_TYPE_RANDOM)
File "/config/deps/lib/python3.7/site-packages/bluepy/btle.py", line 391, in __init__
self._connect(deviceAddr, addrType, iface)
File "/config/deps/lib/python3.7/site-packages/bluepy/btle.py", line 439, in _connect
raise BTLEDisconnectError("Failed to connect to peripheral %s, addr type: %s" % (addr, addrType), rsp)
bluepy.btle.BTLEDisconnectError: Failed to connect to peripheral d7:2e:95:d5:29:38, addr type: random
2019-05-16 08:42:43 ERROR (SyncWorker_5) [switchbot] Cannot connect to switchbot.
2019-05-16 08:43:00 WARNING (SyncWorker_16) [switchbot] Failed to connect to Switchbot
Traceback (most recent call last):
File "/config/deps/lib/python3.7/site-packages/switchbot/__init__.py", line 35, in _connect
bluepy.btle.ADDR_TYPE_RANDOM)
File "/config/deps/lib/python3.7/site-packages/bluepy/btle.py", line 391, in __init__
self._connect(deviceAddr, addrType, iface)
File "/config/deps/lib/python3.7/site-packages/bluepy/btle.py", line 439, in _connect
raise BTLEDisconnectError("Failed to connect to peripheral %s, addr type: %s" % (addr, addrType), rsp)
bluepy.btle.BTLEDisconnectError: Failed to connect to peripheral d7:2e:95:d5:29:38, addr type: random
2019-05-16 08:43:00 ERROR (SyncWorker_16) [switchbot] Cannot connect to switchbot.
2019-05-16 08:43:02 WARNING (SyncWorker_0) [switchbot] Failed to connect to Switchbot
Traceback (most recent call last):
File "/config/deps/lib/python3.7/site-packages/switchbot/__init__.py", line 35, in _connect
bluepy.btle.ADDR_TYPE_RANDOM)
File "/config/deps/lib/python3.7/site-packages/bluepy/btle.py", line 391, in __init__
self._connect(deviceAddr, addrType, iface)
File "/config/deps/lib/python3.7/site-packages/bluepy/btle.py", line 439, in _connect
raise BTLEDisconnectError("Failed to connect to peripheral %s, addr type: %s" % (addr, addrType), rsp)
bluepy.btle.BTLEDisconnectError: Failed to connect to peripheral d7:2e:95:d5:29:38, addr type: random
2019-05-16 08:43:02 ERROR (SyncWorker_0) [switchbot] Cannot connect to switchbot.
Furthermore, the state of the switch still remains turned on.
Can you please look into it?
Thanks.
1 reply
It fails to connect to your device, so I do not think it is a code issue. Try to move your device closer to your HASS computer.
If that does not work, please open an issue here: https://github.com/home-assistant/home-assistant/issues
the switch is right next to my nuc less than 1.5m away so its not a distance issue. I will open an issue on github.
UPDATE: here is the github link to the newly created issue:
I am sorry to admit that I have become an addict of HA. Is there a cure out there?
Please consider to implement a Lovelace store, for one-place-to-go, easy browsing, implement and update custom Lovelace cards. - So my withdrawal symptoms can cured.
Hi all
after the upgrade Hassio on Docker from 0.92.2 to 0.93 all seems to work fine, but if do a Check Home Assistant configuration I get this
[Info] Start install HomeAssistant latest
You are using pip version 19.0.3, however version 19.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
[Info] Installed homeassistant==0.93.0, check config now
[Error] Wrong config found!
Testing configuration at /tmp/config
INFO:homeassistant.util.package:Attempting install of home-assistant-frontend==20190514.0
INFO:homeassistant.util.package:Attempting install of av==6.1.2
ERROR:homeassistant.util.package:Unable to install package av==6.1.2: Failed building wheel for av
Command "/usr/local/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-9779xhvm/av/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-zpyrqsum/install-record.txt --single-version-externally-managed --prefix --compile --user --prefix=" failed with error code 1 in /tmp/pip-install-9779xhvm/av/
You are using pip version 19.0.3, however version 19.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
ERROR:homeassistant.requirements:Not initializing stream because could not install requirement av==6.1.2
INFO:homeassistant.util.package:Attempting install of speedtest-cli==2.1.1
INFO:homeassistant.util.package:Attempting install of restrictedpython==4.0b8
INFO:homeassistant.util.package:Attempting install of mutagen==1.42.0
INFO:homeassistant.util.package:Attempting install of sqlalchemy==1.3.3
INFO:homeassistant.util.package:Attempting install of influxdb==5.2.0
INFO:homeassistant.util.package:Attempting install of pychromecast==3.2.1
INFO:homeassistant.util.package:Attempting install of netdisco==2.6.0
INFO:homeassistant.util.package:Attempting install of googledevices==1.0.2
INFO:homeassistant.util.package:Attempting install of pyfttt==0.3
INFO:homeassistant.util.package:Attempting install of google-api-python-client==1.6.4
INFO:homeassistant.util.package:Attempting install of httplib2==0.10.3
INFO:homeassistant.util.package:Attempting install of oauth2client==4.0.0
INFO:homeassistant.util.package:Attempting install of hbmqtt==0.9.4
INFO:homeassistant.util.package:Attempting install of paho-mqtt==1.4.0
INFO:homeassistant.util.package:Attempting install of python-telegram-bot==11.1.0
INFO:homeassistant.util.package:Attempting install of distro==1.4.0
INFO:homeassistant.util.package:Attempting install of pyatmo==1.11
INFO:homeassistant.util.package:Attempting install of rflink==0.0.37
INFO:homeassistant.util.package:Attempting install of PyXiaomiGateway==0.12.3
INFO:homeassistant.util.package:Attempting install of aiohttp_cors==0.7.0
INFO:homeassistant.util.package:Attempting install of yeelight==0.5.0
Failed config
General Errors:
- Unable to install all requirements: av==6.1.2
Successful config (partial)
strangely it ask me to upgrade pip to 19.1.1 while it’s already upgraded
bash-4.4# pwd
/config
bash-4.4# pip --version
pip 19.1.1 from /usr/local/lib/python3.7/site-packages/pip (python 3.7)
And this is the System Health panel
What can I check?
Thanks
PS: I don’t have any streaming component in my camera.yaml file
If I remove
stream:
from configuration.yaml, no error message.
PPS:
I’ve seen this solution in the component page, but how to run since I have Hassio and “sudo apt-get” does not work?
The Hass.io Check Home Assistant configuration-plugin reports two errors when I check my config for the latest version, and I’m not sure if I can continue the update because of them.
Failed config
General Errors:
- Unable to install all requirements: homeassistant-pyozw==0.1.4, pydispatcher==2.0.5
- Component not found: hue
I’m currently on 0.92 and everything is working fine, including hue and z-wave devices.
part of the log where it goes wrong:
INFO:homeassistant.util.package:Attempting install of homeassistant-pyozw==0.1.4
ERROR:homeassistant.util.package:Unable to install package homeassistant-pyozw==0.1.4: Failed building wheel for homeassistant-pyozw
Failed cleaning build dir for homeassistant-pyozw
Command "/usr/local/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-0m6k9zx9/homeassistant-pyozw/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-gt3dm0k8/install-record.txt --single-version-externally-managed --prefix --compile --user --prefix=" failed with error code 1 in /tmp/pip-install-0m6k9zx9/homeassistant-pyozw/
ERROR:homeassistant.requirements:Not initializing zwave because could not install requirement homeassistant-pyozw==0.1.4
Platform not found: sensor.essent 
The VS Code debugger component looks really cool, I only use a YAML linter right now but this looks far better.
I’m also getting this message in my log:
The honeywell component is deprecated for EU (i.e. non-US) systems, this functionality will be removed in version 0.96.
I am in fact using the Honeywell component, does this mean they are disabling their API in the same way Google are with the nest? 
I am in the EU.
Please add to interface option to delete Automation… because still can not delete.
looks like you will just have to move to evohome according to the commit
Ah well spotted, thanks. I’ve just just replaced the honeywell component in my config and the message now no longer appears. However the evohome doesn’t have the same functionality.
The deprecated honeywell that gives the message in my log shows me my hot water temperature:
Hot water: 35 degrees
The new replacement evohome component that fixes the message does not show me my hot water temperature:
I’ve searched thru all the entities and my hot water is not there at all, so I’m going back to the old component for now as I have multiple automations based on my hot_water temperature.
At least the Honeywell API isn’t being stopped, and maybe the evohome component will be updated in future to include the functionality of the component it is replacing, hopefully before 0.96.0 is out. 
Yes, I have Hassio in a Docker container on Ubuntu
The message I get is from the Check Home Assistant configuration
If I go in the homeassistant and hassio_supervisor containers (from Portainer) in the console, I see that the pip version is 19.1.1
After update:
Thu May 16 2019 09:51:13 GMT-0400 (Eastern Daylight Time)
Could not parse gps value for name: (‘latitude’, ‘longitude’)
None of my devices I track with Traccar are working
does new meteoalarm sensor take it’s language from the meteoalarm.eu website? if so, why there’s no “pl” language mentioned in docs? it’s supported by website.
also: docs look like not finished & work in progress… said language settings first are defined as “string”, then like “four digits”, and then possibilities are listed as two-letter abbreviations…
instructions not clear, house on fire 
When should you fix Everspring SP816 for it to work.
So far, it is difficult to get motion sensor Everspring SP816 to work.
chistian
Hi… I’m trying to edit an automation (I add an ID to all my old automations), but I get a not found error in chrome console. For example, editing an automation with ID services_005 :
GET https://xxx.xxx.xxx/api/config/automation/config/services_005 404 (Not Found)
r @ app.a259a502.js:651
o @ app.a259a502.js:651
callApi @ app.a259a502.js:725
updated @ chunk.8d87dd6e53fd23372516.js:1797
performUpdate @ app.a259a502.js:2
_enqueueUpdate @ app.a259a502.js:2
async function (async)
_enqueueUpdate @ app.a259a502.js:2
_requestUpdate @ app.a259a502.js:2
initialize @ app.a259a502.js:2
initialize @ app.a259a502.js:2
O @ app.a259a502.js:2
U @ app.a259a502.js:2
(anonymous) @ chunk.8d87dd6e53fd23372516.js:1765
_stampTemplate @ app.a259a502.js:2
_stampTemplate @ app.a259a502.js:2
p @ app.a259a502.js:2
(anonymous) @ app.a259a502.js:2
i @ app.a259a502.js:2
s @ app.a259a502.js:2
__ensureInstance @ app.a259a502.js:725
__render @ app.a259a502.js:725
(anonymous) @ app.a259a502.js:725
(anonymous) @ app.a259a502.js:2
window.MutationObserver.observe.characterData @ app.a259a502.js:2
characterData (async)
run @ app.a259a502.js:2
setConfig @ app.a259a502.js:2
debounce @ app.a259a502.js:2
__debounceRender @ app.a259a502.js:725
x @ app.a259a502.js:2
k @ app.a259a502.js:2
w @ app.a259a502.js:2
_propertiesChanged @ app.a259a502.js:2
_flushProperties @ app.a259a502.js:410
_flushProperties @ app.a259a502.js:2
__enableOrFlushClients @ app.a259a502.js:2
_flushClients @ app.a259a502.js:2
_propertiesChanged @ app.a259a502.js:2
_flushProperties @ app.a259a502.js:410
_flushProperties @ app.a259a502.js:2
_invalidateProperties @ app.a259a502.js:2
(anonymous) @ app.a259a502.js:2
_propertiesChanged @ app.a259a502.js:2
_flushProperties @ app.a259a502.js:410
_flushProperties @ app.a259a502.js:2
_invalidateProperties @ app.a259a502.js:2
setProperties @ app.a259a502.js:2
__tryToMatch @ chunk.4668e986d0cb2701ad4f.js:234
z @ app.a259a502.js:2
k @ app.a259a502.js:2
w @ app.a259a502.js:2
_propertiesChanged @ app.a259a502.js:2
_flushProperties @ app.a259a502.js:410
_flushProperties @ app.a259a502.js:2
__enableOrFlushClients @ app.a259a502.js:2
_flushClients @ app.a259a502.js:2
_propertiesChanged @ app.a259a502.js:2
_flushProperties @ app.a259a502.js:410
_flushProperties @ app.a259a502.js:2
_invalidateProperties @ app.a259a502.js:2
_setProperty @ app.a259a502.js:2
Object.defineProperty.set @ app.a259a502.js:410
value @ chunk.f6e80ec34a06dd5930b3.js:1
value @ app.a259a502.js:894
performUpdate @ app.a259a502.js:2
_enqueueUpdate @ app.a259a502.js:2
async function (async)
_enqueueUpdate @ app.a259a502.js:2
_requestUpdate @ app.a259a502.js:2
set @ app.a259a502.js:2
value @ app.a259a502.js:1197
value @ app.a259a502.js:894
performUpdate @ app.a259a502.js:2
_enqueueUpdate @ app.a259a502.js:2
async function (async)
_enqueueUpdate @ app.a259a502.js:2
_requestUpdate @ app.a259a502.js:2
set @ app.a259a502.js:2
commit @ app.a259a502.js:2
commit @ app.a259a502.js:2
update @ app.a259a502.js:2
_commitTemplateResult @ app.a259a502.js:2
commit @ app.a259a502.js:2
a @ app.a259a502.js:2
U.render @ app.a259a502.js:2
update @ app.a259a502.js:2
performUpdate @ app.a259a502.js:2
_enqueueUpdate @ app.a259a502.js:2
async function (async)
_enqueueUpdate @ app.a259a502.js:2
_requestUpdate @ app.a259a502.js:2
set @ app.a259a502.js:2
commit @ app.a259a502.js:2
commit @ app.a259a502.js:2
update @ app.a259a502.js:2
_commitTemplateResult @ app.a259a502.js:2
commit @ app.a259a502.js:2
update @ app.a259a502.js:2
_commitTemplateResult @ app.a259a502.js:2
commit @ app.a259a502.js:2
a @ app.a259a502.js:2
U.render @ app.a259a502.js:2
update @ app.a259a502.js:2
performUpdate @ app.a259a502.js:2
_enqueueUpdate @ app.a259a502.js:2
async function (async)
_enqueueUpdate @ app.a259a502.js:2
_requestUpdate @ app.a259a502.js:2
set @ app.a259a502.js:2
value @ app.a259a502.js:1272
handleEvent @ app.a259a502.js:2
_boundHandleEvent @ app.a259a502.js:2
S @ app.a259a502.js:2
j @ app.a259a502.js:2
k @ app.a259a502.js:2
(anonymous) @ app.a259a502.js:2
_propertiesChanged @ app.a259a502.js:2
_flushProperties @ app.a259a502.js:410
_flushProperties @ app.a259a502.js:2
_invalidateProperties @ app.a259a502.js:2
_setProperty @ app.a259a502.js:2
Object.defineProperty.set @ app.a259a502.js:410
_locationChanged @ app.a259a502.js:1033
z @ app.a259a502.js:2
k @ app.a259a502.js:2
w @ app.a259a502.js:2
_propertiesChanged @ app.a259a502.js:2
_flushProperties @ app.a259a502.js:410
_flushProperties @ app.a259a502.js:2
_invalidateProperties @ app.a259a502.js:2
_setProperty @ app.a259a502.js:2
Object.defineProperty.set @ app.a259a502.js:410
__computeRoutePath @ app.a259a502.js:1038
z @ app.a259a502.js:2
k @ app.a259a502.js:2
w @ app.a259a502.js:2
_propertiesChanged @ app.a259a502.js:2
_flushProperties @ app.a259a502.js:410
_flushProperties @ app.a259a502.js:2
_invalidateProperties @ app.a259a502.js:2
(anonymous) @ app.a259a502.js:2
_propertiesChanged @ app.a259a502.js:2
_flushProperties @ app.a259a502.js:410
_flushProperties @ app.a259a502.js:2
_invalidateProperties @ app.a259a502.js:2
_setProperty @ app.a259a502.js:2
Object.defineProperty.set @ app.a259a502.js:410
_urlChanged @ app.a259a502.js:1033
(anonymous) @ app.a259a502.js:2
fire @ app.a259a502.js:2
_globalOnClick @ app.a259a502.js:1033
(anonymous) @ app.a259a502.js:2
Show 81 more frames
And I get a blank page in HA:
Anyone with this problem??
1 reply
okay; so if there are no breaking changes listed that should affect me I should just update.
can anyone add any information to this:
* Z-Wave - Not a breaking change perse, just a note: Open Z-Wave has released version 1.6. The configuration files are not compatible with Open Z-Wave 1.4, the version that we are currently using. Don’t copy config files over! We’re waiting for Open Z-Wave Python bindings to update before we can update our code.
What “config files” are we not supposed to copy from where to where?
I don’t understand how this is going to affect an existing installation.
2 replies
I think they mean do not try to copy open-zwave config files from their Github into home assistant.
The XML format of the device configs has changed in the 1.6 version.
Example: https://github.com/OpenZWave/open-zwave/blob/master/config/ge/14294-dimmer.xml
Someone copied those, broke their HA installation and then got all angry at the Open Z-Wave maintainers. Which is sad. Hoping that adding that line will prevent others from harassing volunteers.
For these custom integrations, partners will undergo security audits and we’ll control what data is shared and how it can be used.
If extra_html_url is no longer supported, how difficult is it to switch the extra icon packs like this one or this one to using Lovelace imports?
I see that there is already an issue for custom-ui not working which I believe uses extra_html_url as well.
1 reply
Got the same here:
2019-05-16 19:58:09 INFO (SyncWorker_11) [homeassistant.components.netatmo.sensor] Netatmo refresh interval reset to 439 seconds
2019-05-16 19:58:10 ERROR (SyncWorker_11) [homeassistant.components.netatmo.sensor] No Weather or HomeCoach devices found for Maison
2019-05-16 19:58:10 ERROR (SyncWorker_11) [homeassistant.components.netatmo.sensor] Module name: "XXX" not found
2019-05-16 19:58:10 ERROR (SyncWorker_11) [homeassistant.components.netatmo.sensor] Module name: "XXX" not found
2019-05-16 19:58:10 ERROR (SyncWorker_11) [homeassistant.components.netatmo.sensor] Module name: "XXX" not found
2019-05-16 19:58:10 ERROR (SyncWorker_11) [homeassistant.components.netatmo.sensor] Module name: "XXX" not found
2019-05-16 19:58:10 ERROR (SyncWorker_11) [homeassistant.components.netatmo.sensor] Module name: "XXX" not found
2019-05-16 19:58:10 ERROR (SyncWorker_11) [homeassistant.components.netatmo.sensor] Module name: "XXX" not found
(XXX refers to the module names I have hidden).
EDIT: it appears my weather station data are still correctly gathered, even if these error messages appear in log file.
2 replies
Yeah, we forgot about the icon packs. We will come up with a solution soon. extra_html_url is not gone yet (the ES5 version is though). HTML imports have not made it as a standard, so we need to migrate to JS/module imports, just like we do for Lovelace.
Custom UI is only used in the legacy UI. Those imports can still be rewritten to be JS/module based and will continue to work for now.
2 replies
This update breaks for me cloud component (integration through Google Home app). on 0.92.2 it is working fine but after update I am unable to sync devices or relink through app (“Couldn;t update this setting,check you connection”). Works after restoring 92.2 snapshot without any update/change of config files. I don’t use anything listed in changes/breaking changes.
2 replies
Are you exposing the media player? If yes, that’s the issue and will be fixed in 93.x
Just don’t expose or add a speaker / tv class to your media player
When I first started with HA I tried the automation editor, hated it, and quickly moved to yaml. Because the automations created with the editor had id’s I have since continued to add them. Is this bad? Should I remove them?
Hi!
Not working ONVIF camera after update to 0.93.1
Logs:
2019-05-17 12:35:32 ERROR (MainThread) [homeassistant.components.camera] Error while setting up platform onvif
Traceback (most recent call last):
File “/home/acidquest/.homeassistant/deps/lib/python3.6/site-packages/zeep/loader.py”, line 50, in parse_xml
forbid_entities=settings.forbid_entities)
File “/home/acidquest/.homeassistant/deps/lib/python3.6/site-packages/defusedxml/lxml.py”, line 145, in fromstring
rootelement = _etree.fromstring(text, parser, base_url=base_url)
File “src/lxml/etree.pyx”, line 3222, in lxml.etree.fromstring
File “src/lxml/parser.pxi”, line 1877, in lxml.etree._parseMemoryDocument
File “src/lxml/parser.pxi”, line 1765, in lxml.etree._parseDoc
File “src/lxml/parser.pxi”, line 1127, in lxml.etree._BaseParser._parseDoc
File “src/lxml/parser.pxi”, line 601, in lxml.etree._ParserContext._handleParseResultDoc
File “src/lxml/parser.pxi”, line 711, in lxml.etree._handleParseResult
File “src/lxml/parser.pxi”, line 640, in lxml.etree._raiseParseError
File “”, line 1
lxml.etree.XMLSyntaxError: Document is empty, line 1, column 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “/home/acidquest/.homeassistant/deps/lib/python3.6/site-packages/zeep/wsdl/bindings/soap.py”, line 170, in process_reply
doc = parse_xml(content, self.transport, settings=client.settings)
File “/home/acidquest/.homeassistant/deps/lib/python3.6/site-packages/zeep/loader.py”, line 54, in parse_xml
content=content
zeep.exceptions.XMLSyntaxError: Invalid XML content received (Document is empty, line 1, column 1)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “/usr/local/lib/python3.6/dist-packages/homeassistant/helpers/entity_platform.py”, line 126, in _async_setup_platform
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/local/lib/python3.6/dist-packages/homeassistant/components/onvif/camera.py”, line 101, in async_setup_platform
await hass_camera.async_initialize()
File “/usr/local/lib/python3.6/dist-packages/homeassistant/components/onvif/camera.py”, line 157, in async_initialize
await self._camera.update_xaddrs()
File “/home/acidquest/.homeassistant/deps/lib/python3.6/site-packages/onvif/client.py”, line 233, in update_xaddrs
capabilities = await self.devicemgmt.GetCapabilities({‘Category’: ‘All’})
File “/home/acidquest/.homeassistant/deps/lib/python3.6/site-packages/zeep/asyncio/bindings.py”, line 21, in send
return self.process_reply(client, operation_obj, response)
File “/home/acidquest/.homeassistant/deps/lib/python3.6/site-packages/zeep/wsdl/bindings/soap.py”, line 176, in process_reply
content=response.content)
zeep.exceptions.TransportError: Server returned response (200) with invalid XML: Invalid XML content received (Document is empty, line 1, column 1).
Content: b’’
Since updating to version 0.93 (and version 0.93.1), I am experiencing some strange behavior with Sonos devices exposed to HomeKit.
I have 9 Sonos Media Players and only 6 of them are being exposed to HomeKit. Every time I restart Home Assistant it exposes 6 different Media Players (it seems to randomly select 6 Media Players on HA restart). This had been working perfectly for months and months.
Part of my configure is listed below.
homekit:
filter:
include_domains:
- media_player
entity_config:
media_player.bird_room:
name: “Bird Room Sonos”
feature_list:
- feature: play_pause
media_player.garage:
name: “Garage Sonos”
feature_list:
- feature: play_pause
Any help would be greatly appreciated! Thank you.
2 replies
This little nugget of information is rather well buried. (i.e. that check config is broken).
How about actually updating the release notes themselves to indicate that this is the case; Many have religiously advocated the use of this facility in the past to help prevent inadvertent updates against bad configurations that it really does have a significant impact when it fails to work as expected and if not formally acknowledged will reduce people’s confidence in what they are being told.
Should users wait for an update, or go ahead and upgrade anyway?
Same here. Got the errors but data are correctly displayed and gathered.
you got us there…
to be sure, would you please confirm this means a legacy HA user can safely upgrade to .93 and still use:
extra_html_url:
- /local/custom_ui/state-card-custom-ui.html
- /local/custom_ui/state-card-tiles.html
- /local/custom_ui/state-card-value_only.html
- /local/custom_ui/custom-weather-card.html
is this something the dev team is working on, or something the user should do on their side?
that is not 100% true. Most of all customizations work perfectly fine in Lovelace. In fact, custom-ui has many possibilities Lovelace misses out on still, like full support for templating. Would be really appreciated if the team would consider keeping that supported going forward.
again, that sounds truly great, is there anything the user can do, or do we have to wait for the dev-team to do this.
thanks.
3 replies
There’s a card for templates in Lovelace. 📝 100% Templatable Lovelace Configurations
Has there been a change in the “Unused entities” tab ?
I mainly use picture elements cards so all my entities used to show up there.
Since updating, only ones that are not on any of my picture element cards are in the unused entities tab.
I guess this is sensible, but is not the case for conditional cards etc, they are still there
Am I missing something?
I get a lot of Xiaomi error logs since the Update to 0.93.1
Got exception while fetching the state: Unable to discover the device 192.168.200.28
After a few minutes the device is available again
1 reply
Clicking on 0.93.1 “release notes” in the Hassio dashboard takes you to this blog. Where may I find the specific fixes in 0.93.1? I think I am only seeing the original .93 information here, except when extracting bits here and there in the comments.
Also, why was @w1ll1am23’s critical PubNub Wink component update ( #23710 ) not mentioned in the release notes? It was in fact merged into .93.0.
EDIT: nevermind about the .93.1 release notes. I see it was just added. Thanks. s
After a few restarts seems to be stable again
No data from my Netatmo weather station since ~4h now.
Just checked log file, and I get:
2019-05-17 14:00:15 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.netatmo_cuisine_temperature is taking over 10 seconds
2019-05-17 14:00:15 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.netatmo_cuisine_temperature fails
Traceback (most recent call last):
File "/usr/src/app/homeassistant/helpers/entity.py", line 220, in async_update_ha_state
await self.async_device_update()
File "/usr/src/app/homeassistant/helpers/entity.py", line 377, in async_device_update
await self.hass.async_add_executor_job(self.update)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/app/homeassistant/components/netatmo/sensor.py", line 216, in update
self.netatmo_data.update()
File "/usr/src/app/homeassistant/components/netatmo/sensor.py", line 544, in update
self.station_data = self._detect_platform_type()
File "/usr/src/app/homeassistant/components/netatmo/sensor.py", line 522, in _detect_platform_type
station_data = self.data_class(self.auth)
File "/usr/local/lib/python3.7/site-packages/smart_home/WeatherStation.py", line 23, in __init__
resp = postRequest(self.urlReq, postParams)
File "/usr/local/lib/python3.7/site-packages/smart_home/__init__.py", line 39, in postRequest
if params
File "/usr/local/lib/python3.7/urllib/request.py", line 222, in urlopen
return opener.open(url, data, timeout)
File "/usr/local/lib/python3.7/urllib/request.py", line 525, in open
response = self._open(req, data)
File "/usr/local/lib/python3.7/urllib/request.py", line 543, in _open
'_open', req)
File "/usr/local/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
File "/usr/local/lib/python3.7/urllib/request.py", line 1360, in https_open
context=self._context, check_hostname=self._check_hostname)
File "/usr/local/lib/python3.7/urllib/request.py", line 1320, in do_open
r = h.getresponse()
File "/usr/local/lib/python3.7/http/client.py", line 1321, in getresponse
response.begin()
File "/usr/local/lib/python3.7/http/client.py", line 296, in begin
version, status, reason = self._read_status()
File "/usr/local/lib/python3.7/http/client.py", line 257, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
File "/usr/local/lib/python3.7/socket.py", line 589, in readinto
return self._sock.recv_into(b)
File "/usr/local/lib/python3.7/ssl.py", line 1052, in recv_into
return self.read(nbytes, buffer)
File "/usr/local/lib/python3.7/ssl.py", line 911, in read
return self._sslobj.read(len, buffer)
socket.timeout: The read operation timed out
After a restart, Netatmo data are here again.
Something is definitely going on with this new release regarding Netatmo integration.
Likewise for me with the Google Assistant component … I’ve had to revert 0.92.2 in order to sync.
1 reply
I use custom_ui for changing icon colors, sometimes based on conditional logic. Is there a better way to do that without custom_ui, short of implementing it separately for all cards? The template card looks like it could handle the logic, but not colors directly.
guys with google issues? are you running 93.0 or 93.1 ?
in 93.0 , indeed if you exposed the mediaplayer, that sync was not possible
fixed in 93.1
Probably requires the the dev of the custom-ui to do that part.
Ah … you are correct. It’s now working with 93.1. Thank you
I’m on HassIO and it’s prompted me to upgrade up to 0.93.1, so might just be you. Reboot the host?
1 reply
Yeah, I rebooted. Guess I need to plow through the log to try to understand why I’m not getting the upgrade prompt .
I had this too, long time a go… I think I fixed it by deleting the .db file and reboot
The supervisor contacts a web source and checks for the latest available version.
Hassio always lags behind the release announcement as it takes time to build. Keep in mind the builder may not be in your time zone so a daytime release for you may be overnight for them.
The check is only made a couple of times a day. If one is missed or the timing just isn’t right you may have a delay in getting it to show up.
As for the update to 92 when you are on 93, I think the check must be rather simple and doesn’t check that 93.1 is greater than 92.
1 reply
After a manual update indeed the check did not took place. After the check the prompt Will disappear.
It sounds like the HomeKit integration is starting faster than HA can discover all of your speakers?
Do you have an automation set to disable and delay the HomeKit integration from starting? If not, you should, give it a 15-30 second delay to give HA time to discover everything before the HomeKit integration spins up. Check out the documentation, scroll down to Disable Auto start.
If you already have it set up, you might have the delay set too short, add more time.
1 reply
After reading this, I decided to update the HASSOS to 2.12. Upon reboot, within the system log, I see this:
18-06-22 11:12:18 WARNING (MainThread) [hassio.updater] Can't fetch versions from https://s3.amazonaws.com/hassio-version/stable.json: Cannot connect to host s3.amazonaws.com:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1056)')]
If I understand correctly, the system has to be able to read stable.json to know what the latest stable version is. I have no idea where to begin resolving this certificate_verify_failed error .
EDIT: I see the date in the log is off badly (6/22/18). Within Home Assistant, the date and time displays correctly within the HA log, but not in the system log. Any help on how to correct the system date, or perhaps I’m not on the right track?
EDIT2: I see the date in the system log is now correct. Going to reboot and see if I still cannot retrieve stable.json.
Edit3: Now no errors in system log regarding stable.json, but still prompting me with the old version of Hassio. Not sure how to proceed with troubleshooting.
1 reply
quite right, see my remarks in 0.93: Essent, AmbiClimate, VS Code debugging
hope this gets restored asap, since there’s no real reason to deprecate this…
1 reply
The date & time on your machine are incorrect. It thinks the AWS certificate is dated in the future.
Yes, that is happens if the NTP is not available to update the host time. He adjust it self after he can reach the NTP server and you can simple click reload on Hass.io/System/Supervisor Panel to force a reload of version file.
The Backend check every 8 Hours for updates. Maybe we can try it to 6 Hours but we have over 260 request per seconds to that file now.
1 reply
probably due to HTML_imports being deprecated itself. https://www.chromestatus.com/feature/5144752345317376
also i think the dev of the custom-ui hhas released a version that now works
Climate - EQ3 Bluetooth Smart Thermostats can’t install requirements.
Hello,
after updating from HA 0.92.2 to 0.93.1 my eq3bt thermostats are broken.
It seams Hassbian can not install requirements package python-eq3bt version 0.1.9.
When I try to install python-eq3bt with pip it installs version 0.1.10?
On the same update hassbian updated python to version 3.7.
os: hassbian
python: 3.7.3
ha: 0.93.1
Unable to install package python-eq3bt==0.1.9: ERROR: Complete output from command /srv/homeassistant/bin/python -u -c ‘import setuptools, tokenize;file=’“'”‘/tmp/pip-install-h5o07c45/bluepy/setup.py’“'”‘;f=getattr(tokenize, ‘"’“‘open’”’“‘, open)(file);code=f.read().replace(’”‘"’\r\n’“'”‘, ‘"’"’\n’“'”‘);f.close();exec(compile(code, file, ‘"’“‘exec’”’“‘))’ bdist_wheel -d /tmp/pip-wheel-f50qtumo --python-tag cp37:
ERROR: running bdist_wheel
running build
running build_py
Working dir is /tmp/pip-install-h5o07c45/bluepy
execute make -C ./bluepy clean
execute make -C bluepy -j1
Failed to compile bluepy-helper. Exiting install.
Command was ‘make -C bluepy -j1’ in /tmp/pip-install-h5o07c45/bluepy
Return code was 2
Output was:
b"make: Entering directory ‘/tmp/pip-install-h5o07c45/bluepy/bluepy’\ntar xzf bluez-src.tgz\ntouch ./bluez-5.47/lib/bluetooth.c ./bluez-5.47/lib/hci.c ./bluez-5.47/lib/sdp.c ./bluez-5.47/lib/uuid.c ./bluez-5.47/attrib/att.c ./bluez-5.47/attrib/gatt.c ./bluez-5.47/attrib/gattrib.c ./bluez-5.47/attrib/utils.c ./bluez-5.47/btio/btio.c ./bluez-5.47/src/log.c ./bluez-5.47/src/shared/mgmt.c ./bluez-5.47/src/shared/crypto.c ./bluez-5.47/src/shared/att.c ./bluez-5.47/src/shared/queue.c ./bluez-5.47/src/shared/util.c ./bluez-5.47/src/shared/io-glib.c ./bluez-5.47/src/shared/timeout-glib.c\nPackage glib-2.0 was not found in the pkg-config search path.\nPerhaps you should add the directory containingglib-2.0.pc'\nto the PKG_CONFIG_PATH environment variable\nNo package 'glib-2.0' found\nPackage glib-2.0 was not found in the pkg-config search path.\nPerhaps you should add the directory containingglib-2.0.pc’\nto the PKG_CONFIG_PATH environment variable\nNo package ‘glib-2.0’ found\ncc -L. -g -Wall -Os -DHAVE_CONFIG_H -I./bluez-5.47/attrib -I./bluez-5.47 -I./bluez-5.47/lib -I./bluez-5.47/src -I./bluez-5.47/gdbus -I./bluez-5.47/btio -I./bluez-5.47/sys -o bluepy-helper bluepy-helper.c ./bluez-5.47/lib/bluetooth.c ./bluez-5.47/lib/hci.c ./bluez-5.47/lib/sdp.c ./bluez-5.47/lib/uuid.c ./bluez-5.47/attrib/att.c ./bluez-5.47/attrib/gatt.c ./bluez-5.47/attrib/gattrib.c ./bluez-5.47/attrib/utils.c ./bluez-5.47/btio/btio.c ./bluez-5.47/src/log.c ./bluez-5.47/src/shared/mgmt.c ./bluez-5.47/src/shared/crypto.c ./bluez-5.47/src/shared/att.c ./bluez-5.47/src/shared/queue.c ./bluez-5.47/src/shared/util.c ./bluez-5.47/src/shared/io-glib.c ./bluez-5.47/src/shared/timeout-glib.c \nbluepy-helper.c:33:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/att.c:33:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/gatt.c:32:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/gattrib.c:34:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/utils.c:30:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/btio/btio.c:37:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/src/log.c:38:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/src/shared/io-glib.c:30:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/src/shared/timeout-glib.c:22:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\nMakefile:30: recipe for target ‘bluepy-helper’ failed\nmake: *** [bluepy-helper] Error 1\nmake: Leaving directory ‘/tmp/pip-install-h5o07c45/bluepy/bluepy’\n”ERROR: Failed building wheel for bluepy
ERROR: Complete output from command /srv/homeassistant/bin/python -u -c ‘import setuptools, tokenize;file=’“'”‘/tmp/pip-install-h5o07c45/bluepy/setup.py’“'”‘;f=getattr(tokenize, ‘"’“‘open’”’“‘, open)(file);code=f.read().replace(’”‘"’\r\n’“'”‘, ‘"’"’\n’“'”‘);f.close();exec(compile(code, file, ‘"’“‘exec’”’“‘))’ install --record /tmp/pip-record-dyqemqc8/install-record.txt --single-version-externally-managed --compile --install-headers /srv/homeassistant/include/site/python3.7/bluepy:
ERROR: running install
running build
running build_py
Working dir is /tmp/pip-install-h5o07c45/bluepy
execute make -C ./bluepy clean
execute make -C bluepy -j1
Failed to compile bluepy-helper. Exiting install.
Command was ‘make -C bluepy -j1’ in /tmp/pip-install-h5o07c45/bluepy
Return code was 2
Output was:
b"make: Entering directory ‘/tmp/pip-install-h5o07c45/bluepy/bluepy’\ntar xzf bluez-src.tgz\ntouch ./bluez-5.47/lib/bluetooth.c ./bluez-5.47/lib/hci.c ./bluez-5.47/lib/sdp.c ./bluez-5.47/lib/uuid.c ./bluez-5.47/attrib/att.c ./bluez-5.47/attrib/gatt.c ./bluez-5.47/attrib/gattrib.c ./bluez-5.47/attrib/utils.c ./bluez-5.47/btio/btio.c ./bluez-5.47/src/log.c ./bluez-5.47/src/shared/mgmt.c ./bluez-5.47/src/shared/crypto.c ./bluez-5.47/src/shared/att.c ./bluez-5.47/src/shared/queue.c ./bluez-5.47/src/shared/util.c ./bluez-5.47/src/shared/io-glib.c ./bluez-5.47/src/shared/timeout-glib.c\nPackage glib-2.0 was not found in the pkg-config search path.\nPerhaps you should add the directory containingglib-2.0.pc'\nto the PKG_CONFIG_PATH environment variable\nNo package 'glib-2.0' found\nPackage glib-2.0 was not found in the pkg-config search path.\nPerhaps you should add the directory containingglib-2.0.pc’\nto the PKG_CONFIG_PATH environment variable\nNo package ‘glib-2.0’ found\ncc -L. -g -Wall -Os -DHAVE_CONFIG_H -I./bluez-5.47/attrib -I./bluez-5.47 -I./bluez-5.47/lib -I./bluez-5.47/src -I./bluez-5.47/gdbus -I./bluez-5.47/btio -I./bluez-5.47/sys -o bluepy-helper bluepy-helper.c ./bluez-5.47/lib/bluetooth.c ./bluez-5.47/lib/hci.c ./bluez-5.47/lib/sdp.c ./bluez-5.47/lib/uuid.c ./bluez-5.47/attrib/att.c ./bluez-5.47/attrib/gatt.c ./bluez-5.47/attrib/gattrib.c ./bluez-5.47/attrib/utils.c ./bluez-5.47/btio/btio.c ./bluez-5.47/src/log.c ./bluez-5.47/src/shared/mgmt.c ./bluez-5.47/src/shared/crypto.c ./bluez-5.47/src/shared/att.c ./bluez-5.47/src/shared/queue.c ./bluez-5.47/src/shared/util.c ./bluez-5.47/src/shared/io-glib.c ./bluez-5.47/src/shared/timeout-glib.c \nbluepy-helper.c:33:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/att.c:33:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/gatt.c:32:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/gattrib.c:34:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/utils.c:30:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/btio/btio.c:37:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/src/log.c:38:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/src/shared/io-glib.c:30:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/src/shared/timeout-glib.c:22:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\nMakefile:30: recipe for target ‘bluepy-helper’ failed\nmake: *** [bluepy-helper] Error 1\nmake: Leaving directory ‘/tmp/pip-install-h5o07c45/bluepy/bluepy’\n”
Any suggestion?
1 reply
Hi, i am not able to upgrade my Hassio from 92.2 to 93.1, i tried to reboot my Raspberry pi but it does not work, i am always getting the same error :
19-05-19 15:31:04 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.93.1
19-05-19 15:31:04 INFO (SyncWorker_0) [hassio.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.92.2 to homeassistant/raspberrypi3-homeassistant:0.93.1
19-05-19 15:31:04 INFO (SyncWorker_0) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.93.1.
19-05-19 15:31:05 ERROR (SyncWorker_0) [hassio.docker.interface] Can’t install homeassistant/raspberrypi3-homeassistant:0.93.1 -> 500 Server Error: Internal Server Error (“readlink /mnt/data/docker/overlay2/l: invalid argument”).
19-05-19 15:31:05 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails
Can i get some help with that please ?
I’ve been struggling also on this one… Want to use it as an alarm for thunderstorms as my dog is very anxious for it.
And the odd part is that the sensor did as if the config was ok (no error messages anywhere), and displaying the state as “Safe”. Today it was code orange here for thunderstorms, but my dashboard just keep showing “safe”. So I only knew by accident it wasn’t doing anything bcs of wrong values in the config.
So the values need to be 100% identical as in the XML files, 1 space or something different and it’s not working. (without error message). I also noticed the language need to be set if you’re not in an English part. I live in Belgium (Dutch) and I am ok with everything in English, but the XML file doesn’t provide the info in English (only Dutch and French), so again the sensor just stated “safe” the whole time…
1 reply
Little extra info.
I pulled the base XML file for my country from this url: (replace country code with your own)
http://meteoalarm.eu/ATOM/BE.xml
There you can lookup your region and click on the “title link”. Should be something like this:
http://meteoalarm.eu/CAP/POLY/BE_19052019_156231427.cap.xml
Then you need exact this information (marked in Yellow)
For me, the region needed to be “Limburg / Limbourg” exactly. So with the spaces, slash etc…
Same for the language! (notice I need to use country NL and not BE in my case)
Lots of confusion 
My code is this. And now the alert comes in my HA
- platform: meteoalarm
country: BE
province: ‘Limburg / Limbourg’
language: ‘nl-NL’
After upgrading to 0.93.9 and 0.93.1
I found that my cpu_load has increased and remains around 3-4 and some times increases to 8-10.
Can’t find anything wrong from my logs.
I am on hassio installed on raspbian on rpi3b+.
Please guide if someone can?
Holy christ 0.93 is doing number on me.
I’ve lost my dark sky sensors. Went back to 0.91 and they are there again.
Most things are taking “more than 10 seconds” so the log is full of that.
Had errors with the logbook all of a sudden and now I get “404: Not Found” trying to access it through the browser.
Fresh install of 0.93, roll back to 0.91 (latest snapshot) and I get the “404: Not Found” straight away.
So that means now I am stuck on 0.93 with no dark sky and log errors from everything being slow. On a Pi 3B+ and never seen this before!
Anyone have an idea why I am having trouble all of a sudden?
2 replies
Yeah the graph is definitely sitting higher than it was before
Hello [amelchio] - That did the trick, thank you very much for the response. I really appreciate it! 
Hello [ranunculales] - Yes, that was exactly the issue. Thanks very much for the quick reply!
Using Foscam cameras and split configuration, have cameras.yaml, using lovelace, using the ‘stream’ in the configuration.yaml, using the camera_view: live, and since this steaming started I was trying many things, foscam platform, generic platform, picture entity, glance, etc. and this STREAMING doesn’t work for me! Can we have somewhere a nicely put 1,2,3 instructions for this streaming to work. The iOS app gets slower and slower, UI is loading slower, I don’t know but it used to be faster system before.
1 reply
Can I suggest please that you open separate thread for each problem you are having, and giving the configurations and log that are needed, See How to help us help you - or How to ask a good question
There is still problem with netatmo sensors, after about 12 hours netatmo sensors stop updating…
