2024.1: Happy automating!

Blog
333

Seems updating to 2024.1.4 keeps rolling back to 2024.1.3 nothing interesting in the logs?

1 Like
334

I had trouble updating to 2024.4 from 2024.3 because of empty yamls (only contained comments). Updated 5 or 6 times before it would not roll back.Fixed by adding a yaml tag.

1 Like
335

Probably related to Fix loading empty yaml files with include_dir_named #107853

336

Can you be more specific please?

I donā€™t think I have any

337

Same issue for me

338

Iā€™m going to check the backup .1 log but I just donā€™t have time for this crap today

339

I long ago split my yaml to packages using

homeassistant:
  packages: !include_dir_named packages

Just added a yaml tag (input_boolean) and 2024.4 installed fine

# #### Empty package ####
input_boolean:
# input_button:
# input_number:
# input_select:
340

Has value takes an entity_id only

Edit: seems Iā€™m late to the party

1 Like
341

Ah ok. I use packages too. So create an empty package with your yaml or can I add that to any other package?

342

Stuck in the install loop. :frowning: Hoping to see a more thorough workaround description.

343

No, the problem was I had 2 packages that only contained commented yaml. I deleted one and uncommented the input_boolean: in the other.

344

Ok I added input_boolean: to one of the yaml files in my packages and it still wonā€™t update

345

I suspect every yaml with only commented yaml and nothing active will need this added, if you have more than just that one.

346

Sorry, perhaps you misunderstood, there was nothing special about input_boolean. It was just to prevent the package from being empty (containing only comments). I had two "empty " packages, you may have others.I found the name of my bad package in home-assistant.log.fault

347

Ah okā€¦ like I said Iā€™ll check that when I am able tomorrowā€¦ Thanks.

348

Could have a similar origin as my issue with secrets.
I failed to reproduce this ā€œempty yaml fileā€ glitch.

349

I did this:

{{ states('sensor.home_power') }}
{{ states('sensor.home_power') | has_value }}
{{ has_value(states('sensor.home_power'))

But now saw my mistakeā€¦

{{ states('sensor.home_power') }}
{{ 'sensor.home_power' | has_value }}
{{ has_value('sensor.home_power') }}

(When I posted this it did cross my mind that it would very likely have been picked up already, so it was odd in that sense. Still, I couldnā€™t see my error. I thought I was making it easy by simplifying my examples, but it was an oversimplification.)

350

No, that doesnā€™t matter. You can use single quotes or double quotes.

The main difference was that I used has_value on a string with an entity_id (sensor.energy) while was using it on the strings "123" and abc which are obviously not entity_ids

1 Like
351

Same here. I found this in the logs (not sure if this has anything to do with this):

Error doing job: Fatal write error on datagram transport

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 1190, in sendto
    self._sock.sendto(data, addr)
TypeError: str, bytes or bytearray expected, not NoneType
352

Similar to the few posts from #341 onwards I had failed updates due to empty yaml files in my config directoryā€¦

A combination of entering correct yaml into them or removing them from config solved the issue.