Avainsanana Home Assistant

Blog content in Atom feed broken by terminology explanations

5. marraskuuta 2026 klo 13.14
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Home Assistant, saavutettavuus, Tiny Tiny RSS

Type of issue

Other (issue in content formatting, broken link or image, non-working widget)

Problem description

In the blog, a tooltip is used to render terminology explanations when content is viewed directly in a browser. But feed readers traditionally don’t support styles, and so the content is broken up by the <span class='terminology-tooltip'> elements’ content being shown mid-sentence. For instance, this paragraph in the 2026.11 release post

<p>Targets are a great way to keep your <span class='terminology'>automations<span class='terminology-tooltip'>Automations in Home Assistant allow you to automatically respond to things that happen in and around your home.<a class='terminology-link' href='/docs/automation/'> [Learn more]</a></span></span> and <span class='terminology'>scripts<span class='terminology-tooltip'>A script is a saved list of steps that runs when you start it, for example, from a dashboard, with Assist, or from an automation. Unlike an automation, a script has no triggers, so it doesn’t start by itself.<a class='terminology-link' href='/docs/script/'> [Learn more]</a></span></span> up to date. Point one at an <span class='terminology'>area<span class='terminology-tooltip'>An area in Home Assistant is a <a href="/docs/organizing/">logical grouping</a> of devices and entities that represents a room or space in your home, such as the living room, kitchen, or garage.<a class='terminology-link' href='/docs/organizing/areas/'> [Learn more]</a></span></span>, a <span class='terminology'>floor<span class='terminology-tooltip'>A floor in Home Assistant is a <a href="/docs/organizing/">logical grouping</a> of areas that are meant to match the physical floors in your home...

is basically unreadable in my feed reader (Tiny Tiny RSS):

Suggested solution

IDK what CMS the blog runs on, but it needs to render those terminology explanations in the feed in a way that doesn’t break the content, or not at all.

URL

https://www.home-assistant.io/atom.xml

Version

2026.11.0

How do you know the suggested solution is correct?

No response

Additional information

I’m re-reporting this; I posted #35042 two years ago, but it went ignored, and this is still an issue.

Vastaa viestiin sen kontekstissa (Github)

where-am-i is able to get my location, yet go-hass-agent always reports the same error it does for OP

30. lokakuuta 2026 klo 13.35
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Dell, Home Assistant, Ubuntu

My laptop (a Dell Latitude 5400, running Ubuntu 26.04) is also affected by this. /usr/libexec/geoclue-2.0/demos/where-am-i is able to get my location, yet go-hass-agent always reports the same error it does for OP:

1:17PM DEBUG Location updated.
1:17PM DEBUG Invalid sensor data. error="contains field errors\ninvalid field Name (value(\"\")) failed validation for required: Key: 'Sensor.Name' Error:Field validation for 'Name' failed on the 'required' tag\ninvalid field State (value(\"<nil>\")) failed validation for required: Key: 'Sensor.State' Error:Field validation for 'State' failed on the 'required' tag\ninvalid field Type (value(\"\")) failed validation for required: Key: 'Sensor.Type' Error:Field validation for 'Type' failed on the 'required' tag\ninvalid field UniqueID (value(\"\")) failed validation for required: Key: 'Sensor.UniqueID' Error:Field validation for 'UniqueID' failed on the 'required' tag

The device tracker’s state in HA remains ”Unknown”.

Vastaa viestiin sen kontekstissa (Github)

Nevermind, this happened multiple times again today

31. heinäkuuta 2026 klo 18.54
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Home Assistant

Nevermind, this happened multiple times again today. Guess I just had a lucky streak of a couple of weeks there when it didn’t.

Vastaa viestiin sen kontekstissa (Github)

I think this might be fixed

28. heinäkuuta 2026 klo 11.55
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Home Assistant

I think this might be fixed; at least I haven’t seen the Shortcuts failure notification in a while now, whereas before it was a daily occurrence.

Vastaa viestiin sen kontekstissa (Github)

This was a conflict between the new integration and the third party integration I had been using up until now

17. syyskuuta 2025 klo 13.57
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Home Assistant, Sleep as Android

Okay, this was a conflict between the new integration and the third party integration I had been using up until now. I did uninstall the old integration before trying to setup the new one, but apparently that wasn’t enough; I also had to manually purge all references to sleep_as_android (both old and new) from .storage/core.entity_registry. Only after that (and core restart) the setup showed the webhook URL as expected.

Vastaa viestiin sen kontekstissa (Github)

No webhook URL given during setup

17. syyskuuta 2025 klo 12.46
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Home Assistant, Sleep as Android

The problem

The setup instructions say ”You will be presented a URL during the setup process.” I see no URL during the setup process (nor is it available anywhere after setup).

Steps to reproduce:
Select Settings > Devices & services > Add integration > Sleep as Android

What I expect to happen:
To ”be presented a URL during the setup process.”

What actually happens:

Screenshot of "Configuration for Sleep as Android": an empty popup aside from Submit button.
Screenshot of Sleep as Android's finishing setup ("Device created") popup. Device name and Area selectors and Skip and finish button.

What version of Home Assistant Core has the issue?

core-2025.9.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Sleep as Android

Link to integration documentation on our website

https://www.home-assistant.io/integrations/sleep_as_android/

Diagnostics information

config_entry-sleep_as_android-01K5BG3KZKPF229RQSVK9BYAYC.json

Example YAML snippet


Anything in the logs that might be useful for us?

I’ve tried enabling debug logging for the integration, but it produces no output at all.

Additional information

No response

Vastaa viestiin sen kontekstissa (Github)

Switched to 11.1 and tried updating those components again. No change unfortunately.

14. marraskuuta 2024 klo 12.05
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Home Assistant

Switched to 11.1 and tried updating those components again. No change unfortunately.

home-assistant_2024-11-14T09-59-20.244Z.log

Vastaa viestiin sen kontekstissa (Github)

2024.10.4 can’t update integrations from HACS

14. marraskuuta 2024 klo 9.36
Sijainti: Blogit: Github
Avainsanat: Home Assistant, Snap

After last night’s refresh I’m now running 2024.10.4. Attempting to update Nordpool, fmi-hass-custom and pytapo fail with:

Unable to install package nordpool==0.4.2: error: failed to create file `/snap/home-assistant-snap/637/.lock` Caused by: Permission denied (os error 13)
Unable to install package fmi-weather-client==0.4.0: error: failed to create file `/snap/home-assistant-snap/637/.lock` Caused by: Permission denied (os error 13)
Unable to install package pytapo==3.3.32: error: failed to create file `/snap/home-assistant-snap/637/.lock` Caused by: Permission denied (os error 13)

It’s apparently due some changes in core, as some people running HA inside a customized Docker have also suffered this.

In the previous latest/stable, updating Nordpool and FMI weather client failed with errors about pip’s version, so I had reverted those back to their earlier versions and put off retrying the updates until now. Pytapo could be a dependency of Tapo Camera Control, which also updated recently.

Vastaa viestiin sen kontekstissa (Github)

”terminology-tooltip” span elements break content in Atom feed

3. lokakuuta 2024 klo 16.35
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Home Assistant, Tiny Tiny RSS

A tooltip is used to render explanations for terminology when site content is viewed directly in a browser. But feed readers traditionally don’t support styles, and so the content is broken up by the <span class='terminology-tooltip'> elements’ content being shown mid-sentence. For instance, this paragraph in the 2024.10 release post

<p>We also introduce some small YAML automation syntax changes. If you are still a sucker for writing your automations
in <span class='terminology'>YAML<span class='terminology-tooltip'>YAML is a human-readable data serialization
language. It is used to store and transmit data in a structured format. In Home Assistant, YAML is used for configuration,
for example in the <code>configuration.yaml</code> or <code>automations.yaml</code>
files.<a class='terminology-link' href='/docs/configuration/yaml/'> [Learn more]</a></span></span> (like me), I’m sure
you’ll love these little tweaks that make it all feel more natural.</p>

is shown in my feed reader (Tiny Tiny RSS) as:

Screenshot from 2024-10-03 16-23-50

I’m not sure if this is a recent technical change, or just the first instance of these spans being used, or if I just haven’t been reading the posts that thoroughly, but the 2024.10 release post was the first I noticed this.

Vastaa viestiin sen kontekstissa (Github)

It’s working just fine after switching to 2024.7/candidate

19. heinäkuuta 2024 klo 14.33
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Home Assistant

I’m on amd64 too, and yep, it’s working just fine after switching to 2024.7/candidate. Excellent, thank you!

Vastaa viestiin sen kontekstissa (Github)

Vanhempia »