0.93: Essent, AmbiClimate, VS Code debugging

tubalainen · May 16, 2019, 7:06am

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?

bachoo786 · May 16, 2019, 7:46am

@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.

Danielhiversen · May 16, 2019, 7:57am

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

bachoo786 · May 16, 2019, 7:59am

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:

Tomahawk · May 16, 2019, 9:18am

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.

woody4165 · May 16, 2019, 10:05am

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?

duncank · May 16, 2019, 10:07am

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

Patrick_HA · May 16, 2019, 11:42am

Platform not found: sensor.essent

Codec303 · May 16, 2019, 12:00pm

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.

pepeEL · May 16, 2019, 12:55pm

Please add to interface option to delete Automation… because still can not delete.

mcnovy · May 16, 2019, 1:12pm

Codec303:

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.

looks like you will just have to move to evohome according to the commit

github.com/home-assistant/core

Add a warning that honeywell/EU is to be deprecated

home-assistant:dev ← zxdavb:deprecate_honeywell_eu

opened 02:21PM - 27 Apr 19 UTC

zxdavb

+7 -0

## Description: The **honeywell** component actually contains two mutually-excl…usive integrations, based upon either the `somecomfort` (US) or `evohome-client` (EU) client libraries. The `evohome` functionality is better provided in the **evohome** component, which uses the same client library. This PR will add a warning to users of the `honeywell` component that support for EU-based systems is deprecated in favour of the `evohome` component. _This warning does not apply to / will not be seen by users of US-based systems._ **Related issue (if applicable):** None **Pull request in [home-assistant.io](https://github.com/home-assistant/home-assistant.io) with documentation (if applicable):** None ## Checklist: - [x] The code change is tested and works locally. - [x] Local tests pass with `tox`. **Your PR cannot be merged unless tests pass** - [x] There is no commented out code in this PR. If user exposed functionality or configuration variables are added/changed: - [x] Documentation added/updated in [home-assistant.io](https://github.com/home-assistant/home-assistant.io) If the code communicates with devices, web services, or third-party tools: - [x] [_The manifest file_][manifest-docs] has all fields filled out correctly ([example][ex-manifest]). - [x] New dependencies have been added to `requirements` in the manifest ([example][ex-requir]). - [x] New dependencies are only imported inside functions that use them ([example][ex-import]). - [x] New or updated dependencies have been added to `requirements_all.txt` by running `script/gen_requirements_all.py`. - [x] New files were added to `.coveragerc`. If the code does not interact with devices: **N/A** - [x] Tests have been added to verify that the new code works. [ex-manifest]: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/mobile_app/manifest.json [ex-requir]: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/mobile_app/manifest.json#L5 [ex-import]: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/keyboard/__init__.py#L23 [manifest-docs]: https://developers.home-assistant.io/docs/en/development_checklist.html#_the-manifest-file_

Codec303 · May 16, 2019, 1:31pm

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.

callifo · May 16, 2019, 1:40pm

Anyone with traccar issues? Mine has now stopped working complete and just reports ‘Could not parse gps value for name: (‘latitude’, ‘longitude’)’ every 30 seconds.

anon34565116 · May 16, 2019, 1:46pm

That is within the homeassistant Docker container?

woody4165 · May 16, 2019, 1:53pm

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

Firespyer · May 16, 2019, 1:54pm

After update:

Log Details (WARNING)

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

pejotigrek · May 16, 2019, 2:05pm

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

chris4 · May 16, 2019, 2:50pm

When should you fix Everspring SP816 for it to work.
So far, it is difficult to get motion sensor Everspring SP816 to work.
chistian

matisaul · May 16, 2019, 2:53pm

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??

balloob · May 16, 2019, 3:20pm

You can only edit automations that are defined in automations.yaml . Automations defined outside should not have an ID set.