2022.7: A stunning performance

I timed my restart from clicking the button. I have no complaints. I was just adding my $.02 worth for comparison purposes on my HA “Blue” ODROID.

Thanks!

I just noticed that there is a discrepancy in the Entity ID for certain entities when listed using Settings–>Entities and when using shortcut <E>.
Check out this listing which is from Settings–>Entities and note the entity named Speillys Bad 1 (note that the word Bad in my language means Bathroom):

Then compare this to the listing of the same items using the shortcut E:

image

In the above list, the Entity ID is missing the trailing number “1”
I have made several attempts to edit the ID, then update and then restart HA, but to no avail.
The strange thing is that the other Bathroom light named Speillys Bad 2 does not suffer from the same issue. This might be just a trifle, but it appears to be a bug, right?

Thanks Dave. I had already updated and kept looking - found an issue with Skybell talking about this error. I cleared out all of my Skybell stuff from YAML (configured through GUI now) and that fixed it for me.

Hi Deckard, I just updated to the latest version of ssh 9.6.0 and core 2022.7.5 without a problem.
I two-ued SkyBell and have recently taken it out and switched to Ring. Looking at backup files I do believe that I commented SkyBell out before doing the backup for the update so I do think that SkyBell could be the culprit here as well.
Here is my old SkyBell code from configuration.yaml but it does on contain any code that I think will cause a problem as the error message stated
“‘<’ not supported between instances of ‘BinarySensorEntityDescription’ and ‘BinarySensorEntityDescription’ same as before with…” although SkyBell does use a binary sensor so is possible.

#skybell removed 13-07-2022 got Ring
#skybell:
  username: !secret skybell_username
  password: !secret skybell_password
binary_sensor:
  - platform: skybell
    monitored_conditions:
      - button
      - motion
camera:
  - platform: skybell
    monitored_conditions:
    - avatar
    - activity
    activity_name: "Last Activity"
#endSkybell

Well at least I think we got to the bottom of it and got it all working.
All the best
Dave

What did you make out of this? Started over with empty database?

Hi

I just updated to 2022.7.5 from 2022.6.7 and in my main dashboard I get an “Unknown error” and it doesn’t show up.

I have some other dashboards and most of them works fine.

This is the log I get

Logger: homeassistant.components.websocket_api.http.connection
Source: util/yaml/loader.py:244
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 09:28:48 (17 occurrences)
Last logged: 09:32:19

[139754267410048] Error handling message: Unknown error (unknown_error)
[139753590495680] Error handling message: Unknown error (unknown_error)
[139753589475840] Error handling message: Unknown error (unknown_error)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 27, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/lovelace/websocket.py", line 30, in send_with_error_handling
    result = await func(hass, connection, msg, config)
  File "/usr/src/homeassistant/homeassistant/components/lovelace/websocket.py", line 72, in websocket_lovelace_config
    return await config.async_load(msg["force"])
  File "/usr/src/homeassistant/homeassistant/components/lovelace/dashboard.py", line 186, in async_load
    is_updated, config = await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/lovelace/dashboard.py", line 205, in _load_config
    config = load_yaml(self.path, Secrets(Path(self.hass.config.config_dir)))
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 155, in load_yaml
    return parse_yaml(conf_file, secrets)
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 168, in parse_yaml
    return _parse_yaml(SafeLoader, content, secrets)
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 198, in _parse_yaml
    yaml.load(content, Loader=lambda stream: loader(stream, secrets))
  File "/usr/local/lib/python3.10/site-packages/yaml/__init__.py", line 81, in load
    return loader.get_single_data()
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 51, in get_single_data
    return self.construct_document(node)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 55, in construct_document
    data = self.construct_object(node)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 100, in construct_object
    data = constructor(self, node)
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 325, in _ordered_dict
    nodes = loader.construct_pairs(node)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 155, in construct_pairs
    value = self.construct_object(value_node, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 100, in construct_object
    data = constructor(self, node)
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 356, in _construct_seq
    (obj,) = loader.construct_yaml_seq(node)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 408, in construct_yaml_seq
    data.extend(self.construct_sequence(node))
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 129, in construct_sequence
    return [self.construct_object(child, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 129, in <listcomp>
    return [self.construct_object(child, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 100, in construct_object
    data = constructor(self, node)
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 325, in _ordered_dict
    nodes = loader.construct_pairs(node)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 155, in construct_pairs
    value = self.construct_object(value_node, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 100, in construct_object
    data = constructor(self, node)
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 356, in _construct_seq
    (obj,) = loader.construct_yaml_seq(node)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 408, in construct_yaml_seq
    data.extend(self.construct_sequence(node))
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 129, in construct_sequence
    return [self.construct_object(child, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 129, in <listcomp>
    return [self.construct_object(child, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 100, in construct_object
    data = constructor(self, node)
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 325, in _ordered_dict
    nodes = loader.construct_pairs(node)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 155, in construct_pairs
    value = self.construct_object(value_node, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 100, in construct_object
    data = constructor(self, node)
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 356, in _construct_seq
    (obj,) = loader.construct_yaml_seq(node)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 408, in construct_yaml_seq
    data.extend(self.construct_sequence(node))
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 129, in construct_sequence
    return [self.construct_object(child, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 129, in <listcomp>
    return [self.construct_object(child, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 100, in construct_object
    data = constructor(self, node)
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 325, in _ordered_dict
    nodes = loader.construct_pairs(node)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 155, in construct_pairs
    value = self.construct_object(value_node, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 100, in construct_object
    data = constructor(self, node)
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 356, in _construct_seq
    (obj,) = loader.construct_yaml_seq(node)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 408, in construct_yaml_seq
    data.extend(self.construct_sequence(node))
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 129, in construct_sequence
    return [self.construct_object(child, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 129, in <listcomp>
    return [self.construct_object(child, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 100, in construct_object
    data = constructor(self, node)
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 325, in _ordered_dict
    nodes = loader.construct_pairs(node)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 155, in construct_pairs
    value = self.construct_object(value_node, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 100, in construct_object
    data = constructor(self, node)
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 325, in _ordered_dict
    nodes = loader.construct_pairs(node)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 155, in construct_pairs
    value = self.construct_object(value_node, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 100, in construct_object
    data = constructor(self, node)
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 325, in _ordered_dict
    nodes = loader.construct_pairs(node)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 155, in construct_pairs
    value = self.construct_object(value_node, deep=deep)
  File "/usr/local/lib/python3.10/site-packages/yaml/constructor.py", line 100, in construct_object
    data = constructor(self, node)
  File "/usr/src/homeassistant/homeassistant/util/yaml/loader.py", line 244, in _include_yaml
    fname = os.path.join(os.path.dirname(loader.get_name()), node.value)
  File "/usr/local/lib/python3.10/posixpath.py", line 90, in join
    genericpath._check_arg_types('join', a, *p)
  File "/usr/local/lib/python3.10/genericpath.py", line 152, in _check_arg_types
    raise TypeError(f'{funcname}() argument must be str, bytes, or '
TypeError: join() argument must be str, bytes, or os.PathLike object, not 'list'

What can I check?
Is there any other things I can do to understand where the error can be?

Thanks

Have you cleared your browser cache?

Is anyone else having issues with ESPHome not updating any platform: homeassistant sensors post upgrade?

I have a NodeMCU connected to my gate, and since the update, the text_sensor that indicates whether it is open or closed is just returning ‘unavailable’. No matter what I do?

Latest version of ESPHome (2022.6.2), and I’ve tried uninstalling and reinstalling, and have tried a number of options around text_sensor, most recently this:

text_sensor:
  - platform: homeassistant
    id: gate_status_text
    name: "Smart Gate Status Text"
    entity_id: input_text.gate_status_text

Nothing in the logs that I can see. Anyone else seeing this?

Yes, cache cleared and also used different browsers

And how does this matter in daily use of HA? Besides of the startup time, do the lights switch some millisecondes faster when using a more sophisticated device compared to i.e. a RPI? :thinking:

Reminds me very much of my times at the boarding school: “Who has the biggest one wins.” :rofl:

1 Like

As much as I totally agree with your sentiment here, one thing of significant change that I did notice when changing from a RPi to a NUC was that I no longer had random crashes.

1 Like

I fully agree on this one: Me too experienced random crashes like 1-2 times every couple of month when running HA on a RPI4. Never happened again after switching to a x86-64 device :+1:t4:

When on the Pi, I had to worry constantly about the size of the .db file and the lifetime of the SD card. I was periodically making a clone of the SD card because they would fail. (This was in addition to daily snapshots to the thumbdrive).

Since switching to the NUC I haven’t had a single crash of Home Assistant and there’s so much memory on the SSD that it will be years before it fills up.

I already acknowledged that my system is gross overkill. I did try Docker with my favorite distro: Ubuntu. Not a month went by when a Home Assistant update complained that the most popular Linux Distro was now unsupported and I had to “trick” HA into doing the upgrade. That is when I bought another NUC i3 and dedicated it to Home Assistant using the X86 image from Home Assistant. This has been rock solid.

I switched from a SD to a SSD on my pi4b 8g and would offer that switching made all the difference in both speed and stability.

I’ve not a single crash or hang I can attribute to the pi itself since. Previously I did have a few random drops or hangs. And the whole system is just, snappier.

I probably would have considered this except that I switched to the NUC before the Pi4 was introduced. And the Pi4 that I did buy was an early version and can’t be made to boot from SSD. But it does serve it’s purpose streaming video to our Halloween decorations.

1 Like

Just for balance, I want to add that I’ve been running HA on a RPi 3B+ for over 3-1/2 years so far. I bought my SD card per the specs in the Getting Started instructions. I keep my database size under control. I don’t use the built-in backup system (which writes to the SD card) unless I change something. For routine backups I just copy all the config files to my NAS.

I’ve got nothing against faster hardware, but I can’t really justify it yet. My little Pi does everything I want, and I’ve never needed to get out a stopwatch to track any delays.

2 Likes

I’m hoping, I’m not stepping on anyones toes, but my RPi does start in under 30 seconds. I don’t think this is comparable, as it only depends on the specific setup. :slight_smile: Let me configure your NUC, and I can practically guarantee to up your starting time to more than half an hour, if ever! :rofl: :rofl: :rofl:

The only thing I can really say is an improvement (and a must), is using a SSD with the Pi. That does some reliability and performance improvements, but I never use the cpu power, the Pi provides. How could I even use anything from the higher power a NUC provides?

But don’t get me wrong, I’m all in with the NUCs and more power (thanks Tim! :rofl:), but to pinpoint it on starting and load times, or reliability, is just the official version for the wife. :rofl: :rofl: :rofl:

2 Likes

Isn’t it heating season in the bottom half of the world right now?

2 Likes

Same here, using the pi4 8g with a ssd and it is rock stable. Have 27 container running and it runs just fine. The ssd is a must!

3 Likes

generic_thermostat stuck in celsius after update