0.118: Grid and logbook cards, quick navigation, native template types

[KCYeoh (Yeoh)]

I’m on 0.117.5 version. I’m wondering if the latest version fix the TTS

[pepe59]

You haven’t read the post above you. Yes version 0.118.5 fixes TTS

[nickrout]

Then you should read the release notes, which refers to tts and links to the PR. https://www.home-assistant.io/blog/2020/11/18/release-118/#release-01185---december-5

[WeatherWitch]

Yep Fixed in 118.5 I believe they are now using a new API

[finity]

Does anyone know how to get the “services” section of developers tools to recognize that you want to use templates?

The following works fine as a service call in an automation:

service: device_tracker.see
data:
  dev_id: toyota_tacoma
  location_name: "{{ states('device_tracker.my_mobile_app') }}"
  gps: 
    - "{{ state_attr('device_tracker.my_mobile_app', 'latitude') }}"
    - "{{ state_attr('device_tracker.my_mobile_app', 'longitude') }}"

but if I paste the following in the service data section:

dev_id: toyota_tacoma
location_name: "{{ states('device_tracker.my_mobile_app') }}"
gps: 
  - "{{ state_attr('device_tracker.my_mobile_app', 'latitude') }}"
  - "{{ state_attr('device_tracker.my_mobile_app', 'longitude') }}"

I get an error that says:

Failed to call service device_tracker/see. invalid latitude for dictionary value @ data['gps']

and this works in a service call:

service: variable.set_variable
data:
  variable: tacoma_location_saved
  value: "{{ states.device_tracker.toyota_tacoma.state }}"
  attributes:
    latitude: "{{ states.device_tracker.toyota_tacoma.attributes.latitude }}"
    longitude: "{{ states.device_tracker.toyota_tacoma.attributes.longitude }}"

but not in the service data section.

I get this:

So its not recognizing I want to interpret the templates as such.

[st3v3nFr]

Replying to my self, but also for anyone running this issue : it was only a ring issue, everything is back to normal without doing anything.
Sorry for posting an issue that… is not.
By the way : thanks to all DEV for this amazing product, i can’t go back to previous system ( homekit, homebridge, etc… ).

[tom_l]

One of my Kodi media players disappeared from home assistant, despite being on the network, operating and no changed settings (including IP address). So I deleted the integration and restarted. Still no Kodi found when adding the integration manually. So I rebooted the kodi box and it was found again by home assistant so I re-added it. However now I get the following error:

Logger: homeassistant.components.media_player
Source: helpers/entity_platform.py:490
Integration: Media Player ([documentation](https://www.home-assistant.io/integrations/media_player), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+media_player%22))
First occurred: 16:36:32 (1 occurrences)
Last logged: 16:36:32

Platform kodi does not generate unique IDs. ID fd943380-fa78-4306-b758-1d0f263c38b9 already exists - ignoring media_player.osmckodi

How do I resolve this without delving into the .storage files?

This must be possible from the UI right?

Pigs arse it is.

This is the problem with your UI. It is not fixable via the UI when things go wrong.

Bring back YAML integration configuration. It worked and was easily fixable unlike this current abomination.

[Sparks (John van Veggel)]

Gents,
I lifted to 0.118.4 this morning. In Scripts and Automations UI, when choosing to execute a service related to media (like media_player.volume_set), the pulldown to select the media player has dissapeared. The original code is still there when I open the action with YAML. Very inconvenient. Hope you can fix quickly in the next release.
tnx
John

[pepe59]

I just tried it and it works well in HA 0.118.5.

[firstof9]

@tom_l

This is the problem with your UI. It is not fixable via the UI when things go wrong.

I’d like a way to modify these entries via the UI as some type of “advanced user” feature myself.

[heyepic (Matt)]

Anyone running the Synology Hass.io package by SynoCommunity?

Both updates showed up for Core and Supervisor - I first updated Supervisor but when I try to update to Home Assistant Core 0.118.5, I get Unknown error, see supervisor.

Under System > Supervisor, I see:
You are running an unsupported installation. Learn more
Your installtion is running in an unhealthy state. Learn more (you have a typo here)

In logs, I see:

20-12-07 20:02:23 WARNING (MainThread) [supervisor.jobs] 'HomeAssistantCore.update' blocked from execution, system is not healthy
20-12-07 20:24:36 WARNING (MainThread) [supervisor.jobs] 'AddonManager.update' blocked from execution, system is not healthy
20-12-07 20:25:20 WARNING (MainThread) [supervisor.jobs] 'AddonManager.update' blocked from execution, system is not healthy
20-12-07 20:25:50 WARNING (MainThread) [supervisor.jobs] 'HomeAssistantCore.update' blocked from execution, system is not healthy

[finity]

@tom_l

How do I resolve this without delving into the .storage files?

Hmm…

I think I remember asking exactly that same question a while back in that other thread and if memory serves I was never given an answer then…

[tkhan456]

Not sure if it has to do with 0.118.5, but my I had a node-red flow that had a “switch” node in it. It would would switch the payload from “on” to “off.” Was working fine until I updated. Now for some reason the msg.payload won’t change unless I have the initial node feeding in data output as boolean value instead of a string like it was before. Weird but thought I’d throw it out there.

[TheAzzi]

I’ve seen this before, and it’s usually a browser cache issue. Try reloading the page (F5).

[isaste (sbik)]

Hi @heyepic

I got excatly the same issue on my side (also running it under Synology)
Impossible to upgrade my 0.118.4 version to 2020.12.1
System always reports “Unknown error, see supervisor” and here are the error I have under supervisor (same as you)
I really don"t know how to fix this. If someone has any idea that would be great.
Thanks

[DavidFW1960 (David)]

Did you click on the read more link or look in the supervisor log?

Most likely you are not using Debian Buster or HAOS and are using watchtower. Just a guess.

[isaste (sbik)]

Yes indeed Watchtower was installed but not working (I never be able to make it work properly)
I uninstall it and restarted Supervisor, but I have same issue (without Watchtower mentionned in the Log this time)
The Log alert me on some other issues, but I don’t know how to fix them
See below : (as reminder I’m running Docker on a Synology NAS)

[DavidFW1960 (David)]

There is a way you can disable the check for healthy I believe. Check out the ha su options help via ssh…

[isaste (sbik)]

Do you have any detailed procedure how to do this ?

[sparkydave (🇦🇺 Dave)]

Unhealthy state

Sigh. Disable the supervisor feature as alluded to by ludeeus (thanks): /usr/share/hassio/homeassistant$ ha jobs options --ignore-conditions healthy No one wants to told they have to change the OS they used for years or decades (especially those with more than just HA on their home server). Or to be told their system is unhealthy and HA rendered broken as a… protection. Yes, the decision was made. Did everyone agree with it? No. Doesn’t mean it needs to be mentioned constantly like we voted o…