0.80: Lovelace updates, webhooks, TRÅDFRI switches

Blog
31

Can this webhook be used in the flic hub? afraid I don’t know much about webhooks and how to make it work :confused:

32

evohome component doesn’t work.
The log: Invalid config for [evohome]: expected a dictionary for dictionary value @ data[‘evohome’]. Got [OrderedDict([(‘username’, ‘username’), (‘password’, ‘password’)])]. (See /home/homeassistant/.homeassistant/configuration.yaml, line 231). Please check the docs at https://home-assistant.io/components/evohome/

2 Likes
33

Not 100% sure what all that means (presumably on the main entity configuration?), but sounds like a no - want them accessible in HASS front end / via the API (through Taskr) but not from Google Assistant (as they either don’t work (Radio538) or aren’t useful)

Additionally, one interesting thing, is that in the updated Google Home app if you try and control one of the aliased devices using the alias (“headboard light”) nothing happens in HASS

34

I can second this.

35

Yea so why can’t you do this, all this does is stop it from been exposed to google assistant instead of using exclude entity:

expose_by_default: false
exposed_domains:
  - script

entity_config:
  
  script.pushbullet:
    expose: false

  script.radio583:
    expose: false

  script.stop_bedroom_music_devices:
    expose: false
36

For those migrating their google assistant component to version 0.80 there is an additional step.

You need to change the fulfillment url under build -> create action and remove the ?api_password part of the url and change it to https://[YOUR HOME ASSISTANT URL:PORT]/api/google_assistant

If you don’t change the url you get 404 error when you try to link the test account.

37

I’ve had 2 crashes within 6 hours with 0.80.0 for unknown reason.
Anyone else?

38

Mine won’t start at all after a requested HA restart. I can ssh to the PI but I can’t get HA running anymore.

39

Hi all,

Should the aqara vibration sensor work on 0.80? The documentation now list it as supported and there’s even a automation example. Unfortunately, mine didn’t show up on interface :-(.

40

The IFTTT example is not working for me…
I was able to initiate a trigger but can NOT use the data passed in the trigger.

I verified that the data I send appears in the trigger (on the DB table)
but it seems like the trigger additional data can not be parsed within the automation:

Passing the following in IFTTT:

{ "action": "testme","a":"This is A","b":"Something else" }

Automation action:

      - service: notify.mainnotification
        data:
          message: '{{ trigger.event.data.a }}'
          title: '{{ trigger.event.data.b }}'

Log Error:

ServiceCall notify.mainnotification (c:e470d168c107459c9890a499f4ef35eb): message=<homeassistant.helpers.template.Template object at 0x6d647970>, title=<homeassistant.helpers.template.Template object at 0x6d647650>>
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/template.py", line 132, in async_render
    return self._compiled.render(kwargs).strip()
  File "/usr/local/lib/python3.6/site-packages/jinja2/asyncsupport.py", line 76, in render
    return original_render(self, *args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/jinja2/environment.py", line 1008, in render
    return self.environment.handle_exception(exc_info, True)
  File "/usr/local/lib/python3.6/site-packages/jinja2/environment.py", line 780, in handle_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/local/lib/python3.6/site-packages/jinja2/_compat.py", line 37, in reraise
    raise value.with_traceback(tb)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.6/site-packages/jinja2/sandbox.py", line 385, in getattr
    value = getattr(obj, attribute)
jinja2.exceptions.UndefinedError: 'trigger' is undefined

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/core.py", line 1177, in _event_to_service_call
    await service_handler.func(service_call)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/notify/__init__.py", line 106, in async_notify_message
    kwargs[ATTR_TITLE] = title.async_render()
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/template.py", line 134, in async_render
    raise TemplateError(err)
homeassistant.exceptions.TemplateError: UndefinedError: 'trigger' is undefined
41

After migrating my google assistant component (local) to version 0.80 and re-linking the app in Google-Assistant on my mobile phone, a brief message is displayed on my phone saying something like “successfully linked your [test] application_name”, but the devices do not show up in Google-Assistant. In the list of “Linked Devices” my “[test] application_name” does not show up, but it is on top of the list of “Add new” devices.

I can repeat trying to add the app, it seems to go through with the “successfully linked” message, but it really does not do it.

Any ideas? I tried chrome and firefox on my phone, emptied cache, set up google home on a spare mobile device and retried, etc, but no luck.

42

I find the breaking changes [0.80] to Google Assistant confusing.
The headline says:
Use Home Assistant Cloud to integrate with Google Assistant without any effort.

One paragraph down the next headline says:
To use Google Assistant, your Home Assistant configuration has to be externally accessible with a hostname and SSL certificate. If you haven’t already configured that, you should do so before continuing.

So, which is it?
If one is required to have a hostname & SSL certificate, what is the point in a Cloud account?

43

If you use the google assistant behind a reverse proxy, you’ll need some extra paths for oAuth2. This is what i needed:

Proxypass /api/google_assistant http://xxx.xxx.xxx.xxx:8123/api/google_assistant disablereuse=on
ProxyPassReverse /api/google_assistant http://xxx.xxx.xxx.xxx:8123/api/google_assistant
Proxypass /auth http://xxx.xxx.xxx.xxx:8123/auth disablereuse=on
ProxyPassReverse /auth http://xxx.xxx.xxx.xxx:8123/auth
Proxypass /frontend_latest http://xxx.xxx.xxx.xxx:8123/frontend_latest disablereuse=on

44

Anyone using Caddy and Google Assistant?

45

If you use Home Assistant Cloud, you can do everything via the configuration panel in the user interface. The instructions you’re reading are for the manual installation if you want to do it yourself.

46

Thanks for this. Hopefully your example can be included in the documentation instead of a forum post.

47

Thanks for the reply.
The instructions are not very explicit, but I guessed that was the case.
Perhaps improved documentation might help

48

Since 0.80 i can’t create new automations in the automation editor with Google Chrome. It shows a blank page. Some existing automations aren’t editable too, showing the same blank page.

I do not have this issue when using Microsoft Edge.

The google chrome console shows:
Uncaught (in promise) TypeError: Cannot read property ‘hours’ of undefined
at state_StateTrigger.render (286a08fb18870c9c81b7.chunk.js:1)
at renderComponent (8752a4221f36038e73c0.chunk.js:1)
at setComponentProps (8752a4221f36038e73c0.chunk.js:1)
at buildComponentFromVNode (8752a4221f36038e73c0.chunk.js:1)
at idiff (8752a4221f36038e73c0.chunk.js:1)
at innerDiffNode (8752a4221f36038e73c0.chunk.js:1)
at idiff (8752a4221f36038e73c0.chunk.js:1)
at diff (8752a4221f36038e73c0.chunk.js:1)
at renderComponent (8752a4221f36038e73c0.chunk.js:1)
at setComponentProps (8752a4221f36038e73c0.chunk.js:1)

49

Yes the Google Integration works perfectly with Caddy - This is what I am using.

1 Like
50

There are migrating to 0.8 instructions here:

see also this post here:

Above is assuming your using google assistant, but not using the new cloud component.