2021.9.0: More energy, USB discovery, template ❤️

i have this error when i do a “check configuration” ?


Fatal error while loading config: The 'google-auth<2.0dev,>=1.25.0' distribution was not found and is required by google-api-core
Failed config
  General Errors: 
    - The 'google-auth<2.0dev,>=1.25.0' distribution was not found and is required by google-api-core
1 Like

Water does not compute in terms of energy.

1 Like

After upgrading my Home Assistant keeps rebooting. Home Assistant Started… Connection Lost…

Last log entries:

21-09-01 22:08:19 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
21-09-01 22:08:20 INFO (SyncWorker_6) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/odroid-c2-homeassistant with version 2021.9.0
21-09-01 22:08:20 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-09-01 22:08:38 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-09-01 22:08:38 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-09-01 22:11:47 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-09-01 22:11:47 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete

Anyone else having this issue? Maybe an issue with the Odroid C2 version? Has had issues in the past.

1 Like

after upgrading, I get this error.

The unit of sensor.qubino_3_phase_smart_meter_electric_produced_kwh_compensation (DKK) does not match the unit of already compiled statistics (EUR). Generation of long term statistics will be suppressed unless the unit changes back to EUR

how to fix, as DKK is my currency…

I’m seeing this too. Using a raspberry pi 3b+ though.

I’m getting confused with the new device_class options. Here’s what my Tuya plug shows:
image

And here’s the sensor:

This sensors returns consumption regularly and will go up and down, so it’s not a total increasing. Should I just give it time to collect data or I misunderstood the documentation?

Check Home Assistant configuration result:

[22:47:46] ERROR: The configuration check did not pass!
[22:47:46] ERROR: See the output below for more details.
Testing configuration at /tmp/config
ERROR:homeassistant.helpers.check_config:Unexpected error validating config
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/homeassistant/helpers/check_config.py", line 155, in async_check_ha_config_file
    await config_validator.async_validate_config(  # type: ignore
  File "/usr/local/lib/python3.9/site-packages/homeassistant/components/automation/config.py", line 129, in async_validate_config
    await asyncio.gather(
  File "/usr/local/lib/python3.9/site-packages/homeassistant/components/automation/config.py", line 106, in _try_async_validate_config_item
    config = await async_validate_config_item(hass, config, full_config)
  File "/usr/local/lib/python3.9/site-packages/homeassistant/components/automation/config.py", line 74, in async_validate_config_item
    config[CONF_TRIGGER] = await async_validate_trigger_config(
  File "/usr/local/lib/python3.9/site-packages/homeassistant/helpers/trigger.py", line 50, in async_validate_trigger_config
    conf = await platform.async_validate_trigger_config(hass, conf)
  File "/usr/local/lib/python3.9/site-packages/homeassistant/components/device_automation/trigger.py", line 21, in async_validate_trigger_config
    return await getattr(platform, "async_validate_trigger_config")(hass, config)
grep: write error: Broken pipe

Not sure where things are going wrong. Anyone?

Found the netdisco issue! HA 20219.0 requires 2.9.0, but the “ha-samsungtv-encrypted” custom component requires 2.8.3.

i would advise the dev of that custom component

Me too, using a raspberry pi 3b+

My log:

21-09-01 23:16:45 WARNING (MainThread) [supervisor.misc.tasks] Watchdog miss API response from Home Assistant
21-09-01 23:17:00 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-09-01 23:17:01 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-09-01 23:17:56 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-09-01 23:17:57 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-09-01 23:18:45 ERROR (MainThread) [supervisor.misc.tasks] Watchdog found a problem with Home Assistant API!
21-09-01 23:18:45 INFO (SyncWorker_0) [supervisor.docker.interface] Restarting ghcr.io/home-assistant/raspberrypi3-64-homeassistant
21-09-01 23:18:49 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-09-01 23:19:10 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-09-01 23:19:11 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-09-01 23:22:02 INFO (MainThread) [supervisor.backups.manager] Found 7 backup files
21-09-01 23:22:02 INFO (MainThread) [supervisor.backups.manager] Found 7 backup files
21-09-01 23:22:49 INFO (MainThread) [supervisor.backups.manager] Found 7 backup files
21-09-01 23:22:49 INFO (MainThread) [supervisor.backups.manager] Found 7 backup files
21-09-01 23:23:36 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-09-01 23:23:37 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-09-01 23:24:00 INFO (MainThread) [supervisor.backups.manager] Found 7 backup files
21-09-01 23:24:01 INFO (MainThread) [supervisor.backups.manager] Found 7 backup files
21-09-01 23:24:14 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
21-09-01 23:24:37 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-09-01 23:24:38 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-09-01 23:25:34 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-09-01 23:25:35 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-09-01 23:26:14 WARNING (MainThread) [supervisor.misc.tasks] Watchdog miss API response from Home Assistant
21-09-01 23:26:25 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-09-01 23:26:26 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete

is there an issue with nabucasa now?

2021-09-01 22:58:31 ERROR (MainThread) [hass_nabucasa.remote] Timeout connecting to snitun server
2021-09-01 22:58:45 ERROR (MainThread) [snitun.client.client_peer] Challenge/Response error with SniTun server
2021-09-01 22:58:45 ERROR (MainThread) [hass_nabucasa.remote] Connection problem to snitun server

Hi
Any plans on adding a standing day charge to the energy dashboard configuration. In the UK we have a daily charge as well as a kWh charge.
So without the daily charge included in the dashboard it isn’t a real representation of the total costs of what your bills will be.
Thanks

11 Likes

Unbelievable what incredible speed the developers of Home Assistant have! Today is only the first day of the month.
I was reading the full change log and only hardly reached the end!
My upgrade works flawless on Docker. Many, many thanks for this great work!!

2 Likes

Killing wink seems a little quick especially if it’s based off opt in analytics.

And since wink has been around a while I would bet willing to bet it is being used on more instances that have not opted in to sharing analytics. (Myself included)

Plus there are android api keys which can be used even if you can’t get your own client secret.

1 Like

I had the same error but it seemed to update ok for me.

1 Like

Maybe I’m missing something but is there some configuration needed for long term statistics?

If not then where are they stored and how long are they stored by default?

1 Like

brave_T7fote3Xrz

That’s awesome! What happens when I click “Configure” if I already have Zigbee2MQTT running in a container? I don’t want to break anything if I don’t have a few hours to fix it properly.

Edit: Ah I understand more now. Clicking “Configure” will help me set up ZHA, I think.

Just updated and now my raspi3b+ is in a boot loop :frowning:
Straight after “HA has started” it reboots.

1 Like

I have the same issue - restart loop that I cant seem to interrupt

2 Likes

Yay, its not just me. … maybe this released should be pulled??

3 Likes