2022.7: A stunning performance

Blog
300

I have a test installation and a ‘production’ installation.
I’ve upgraded test to 2022.7.0 without issues (well, there was one integration which broke. But that one has been fixed mean while).
When I run the Config checker on test I still get the error in this topic.
Also when I run Config checker on 2022.7.0 (against version 2022.7.1) I get this error.
I’m upgrading test to 2022.7.1 at the moment.

So it feels save to upgrade to 2022.7.x even with this error… As Config checker is depreciated that kind of makes sense. Still would like to be able to test configs against future versions prior to updating.

EDIT
Config checker depreciation comments:
WARNING: This add-on is deprecated because it is no longer needed. Home Assistant now always starts after an update even if your config is invalid. You should do the following after an update to check for issues:
-Check persistent notifications. If an integration could not be loaded because its config is invalid a notification will tell you.
-Check logs. If an integration could be loaded but the config you are using is deprecated a message will tell you what needs to change and by when.
-Follow the red banner. In rare cases HA will start in safe mode. In those cases you should follow the instructions in the red banner at the top of the UI.

301

yes OS updates can be intense.make it a habit to always check the issues before doing the actual update.

it would be helpful to the community ion you posted your experience on 8.3 in the repo Issues · home-assistant/operating-system · GitHub

302

Same here. Were you able to fix it? I should not have updated while on holiday. Now all my cameras are not reachable 🫤

303

I’d be more inclined to put money on it being a 3rd party integration. Or an automation or scipt that loops infinitely.

304

NEVER update while out of house… once i updated and could not open my doors. :blush:

2 Likes
305

The Places custom component appears broken by this release - at least, it’s certainly not behaving correctly for me. Have rolled back to 2022.6.7 for now and back up and running.

306

It did not work for me in 2022.6.7 either.
My prior version, 2022.3.3 worked.

But since this is a custom component it needs to be bug reported to the developer

307

luckily you can do all of that and more with core integrations (eg using the mobile_app) reliably. No need for CC if core has it?

308

Unless something has changed, I don’t think the core “place” functionality does the reverse geocoding that this custom component does, which is extremely useful and critical to certain things that I do.

309

Lessons learned :sweat_smile:

310

I don’t see how core has the functionality of the custom component either.

311

I’ll report a proper bug when I have 5 minutes to collate more data than “it doesn’t work. Pls fix” for the bug ticket :wink:

312

Installed the 2022.7.1 and history page is now working fine with area :slight_smile:

So great :slight_smile:

313

the core mobile_app has geocoded_location if thats what you’re looking for. And then some. Distance and time to any other lat/long can easily be checked based on the current position, or relative to any other. Heck, even a travel route is easily templated. All using core integrations, all under scrutiny of HA checks.

Used the Places integrations some years ago myself, and migrated to core when all of that became an integral part of HA

314

Hi all,

What happend with the history when you include entities etc?
This is not shown anymore in the history. You now need always select entities, areas or devices?

I have this in my split configuration:

#  ██╗  ██╗██╗███████╗████████╗ ██████╗ ██████╗ ██╗   ██╗
#  ██║  ██║██║██╔════╝╚══██╔══╝██╔═══██╗██╔══██╗╚██╗ ██╔╝
#  ███████║██║███████╗   ██║   ██║   ██║██████╔╝ ╚████╔╝
#  ██╔══██║██║╚════██║   ██║   ██║   ██║██╔══██╗  ╚██╔╝
#  ██║  ██║██║███████║   ██║   ╚██████╔╝██║  ██║   ██║
#  ╚═╝  ╚═╝╚═╝╚══════╝   ╚═╝    ╚═════╝ ╚═╝  ╚═╝   ╚═╝
###########################################################################################
# HISTORY
# https://www.home-assistant.io/integrations/history/
###########################################################################################
---
include:
  entities:
    # Humidity
    - sensor.buienradar_humidity
    - sensor.bathroom_humidity
    
    # Device Trackers
    - sensor.kay_presence_homekit
    - device_tracker.cenkay
    - sensor.peter_presence_homekit
    - device_tracker.peter_iphone

    - light.bathroom_all
    - light.bedroom_all
    - light.hallway_all
    - light.balcony_all
    - light.toilet_all
    - light.livingroom_all
    - light.kitchen_all
    - light.sink_all
    - light.kitchen_sink

    # Last messages
    - sensor.alexa_last_message
    - sensor.washing_machine_data
    - sensor.dryer_machine_data
    - sensor.dishwasher_machine_data

    - fan.afzuiging_badkamer
    - device_tracker.milight_hub_2

    # DSMR Current Watt delived now
    - sensor.dsmr_reading_electricity_currently_delivered

    # Zwave Motion sensors
    - binary_sensor.toilet_detection
    - binary_sensor.bathroom_detection
    - binary_sensor.hallway_detection
    - binary_sensor.livingroom_detection
    - binary_sensor.bedroom_detection
    - binary_sensor.kitchen_detection
    - binary_sensor.diningroom_detection
    - binary_sensor.bedroom_door_contact
    - binary_sensor.diningroom_door_contact
    - binary_sensor.frondoor_door_contact
    - binary_sensor.imac_door_contact

    # Zwave Watt and KwH
    - sensor.imac_watt
    - sensor.imac_kwh
    - sensor.toog_watt
    - sensor.toog_kwh
    - sensor.washer_watt
    - sensor.washer_kwh
    - sensor.hallway_watt
    - sensor.hallway_kwh
    - sensor.bank_watt
    - sensor.bank_kwh
    - sensor.dishwasher_watt
    - sensor.dishwasher_kwh
    - sensor.bedroom_watt
    - sensor.bedroom_kwh
    - sensor.peter_watt
    - sensor.peter_kwh
    - sensor.kay_watt
    - sensor.kay_kwh
    - sensor.dryer_watt
    - sensor.dryer_kwh

    # Sensors that have a correction
    - sensor.neo_plug_imac
    - sensor.neo_plug_toog
    - sensor.neo_plug_balcony
    - sensor.neo_plug_xmas_1
    - sensor.neo_plug_hallway
    - sensor.neo_plug_bedroom
    - sensor.neo_plug_peter
    - sensor.neo_plug_kay
    - sensor.neo_plug_dryer
    - sensor.neo_plug_washer
    - sensor.neo_plug_dishwasher
    - sensor.neo_plug_fridge

    # Switches
    - switch.balcony
    - switch.bathroom
    - switch.bedroom
    - switch.toilet
    - switch.hallway
    - switch.cooking
    - switch.diningtable
    - switch.dressoir
    - switch.kitchen
    - switch.sink
    - switch.wall
    - switch.window
315

will try to disable automations, eventhough I do not have any fancy ones running to see if this impacts this. On HACS /3rd party integrations I use quite a few, so it is difficult to tell which one may be causing the problem. but as mentionned I have an almost empty system running for tests and I can see that there is a small leak there as well (several days scale though), hence my idea of the core system, but you may be right that this is 3rd party related.

316

Interesting, thanks. Perhaps it’s come on more than I knew!

Struggling to find documentation for this - could you give me a point in the right direction?

317

sure, start here Mobile App - Home Assistant
and then follow the links for your device

and here Feature overview | Home Assistant Companion Docs is the full documentation of the possibilities

318

did you miss all of those posts in this thread on the subject? :wink: Hard really…

but yes, no more auto show all, nor currently the option to do so

you can manually rebuild that using auto-entities, though it is in no way a true replacement for what was lost on us. (it is way slower)

1 Like
319

I would like multiple datasets with entity’s for the history and had the idea to use groups to create such urls dynamically.

http://<ip_or_hostname>:8123/history?entity_id={% for entity in expand('group.windows')|map(attribute='entity_id')|unique|list|sort -%}
  {{ entity + '%2C' if not loop.last }}{{ entity if loop.last }}
{%- endfor %}

Unfortunately I can’t find a way to create a weblink or button action that supports templating. :frowning: