2023.1: Happy New Year of the voice!

ehorsting1982 · January 9, 2023, 10:38am

Weird, I still have disabled entities because of errors with the integration.

2023-01-09 11:05:52.360 WARNING (MainThread) [dsmr_parser.clients.protocol] keep-alive check failed

I do receive data occasionally (this data is after the errors started).

2023-01-06 15:32:11.300 WARNING (MainThread) [dsmr_parser.clients.protocol] keep-alive check failed
2023-01-06 15:32:27.271 DEBUG (MainThread) [dsmr_parser.clients.protocol] received data: /Ene5\XS210 ESMR 5.0

Total consumption does seem to work.

Should I delete the integration and re-configure it?

jwm · January 9, 2023, 11:14am

Do you guys have issues with the amcrest camera integration? I have this message a couple of times a day in the logs:

Logger: homeassistant.components.amcrest
Source: components/amcrest/__init__.py:204
Integration: Amcrest (documentation, issues)
First occurred: 12:07:27 (2 occurrences)
Last logged: 12:07:27

Amcrest Camera camera offline: Login error:
Amcrest Camera camera back online

Rolling back to december release resolves it, so it’s definetly not an issue with the camera or the network.

Kars · January 9, 2023, 11:37am

I also see lots of these keep-alive check failure messages, but I am still on 2022.12.7.
It usually helps if I reboot my “SlimmeLezer”.

ehorsting1982 · January 9, 2023, 11:44am

Tried that already… Without success…

I deleted the integration and re-added. It found the electricity and gas meters. But it still does not work.

After reinstalling I get the following errors:

Traceback (most recent call last):

File “/usr/src/homeassistant/homeassistant/components/dsmr/sensor.py”, line 485, in connect_and_reconnect

await asyncio.sleep(

File “/usr/local/lib/python3.10/asyncio/tasks.py”, line 605, in sleep

return await future

asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File “/usr/src/homeassistant/homeassistant/core.py”, line 1079, in _async_remove_listener

self._listeners[event_type].remove(filterable_job)

ValueError: list.remove(x): x not in list

2023-01-09 13:19:54.596 WARNING (MainThread) [dsmr_parser.clients.protocol] keep-alive check failed

2023-01-09 13:20:54.634 WARNING (MainThread) [dsmr_parser.clients.protocol] keep-alive check failed

2023-01-09 13:21:59.388 WARNING (MainThread) [dsmr_parser.clients.protocol] keep-alive check failed

reinaldo · January 9, 2023, 12:08pm

i tried everything … nothing works here … still:
“Error 400: invalid_request”

maurizio53 · January 9, 2023, 1:54pm

Is anyone having issues integrating the google calendar?
I posted my problem here Google Calendar Integration fails to load

Is there someone who can help me to trace where is the error?

hogend · January 9, 2023, 3:12pm

Your DSMR device is failing or the network connection is unreliable.
The device works as TCP server and homeassistant connects as client.
Clients will not notice if the device restarts and will hang on to an existing connection.
Therefore, a keep-alive message is sent once a minute and, if it is not received, a new connection to the device is initiated.

ehorsting1982 · January 9, 2023, 3:27pm

Thx,

I get that, however, it worked fine before the 2023.1.x updates…

Nonetheless, I will check the DSMR device once again.

ehorsting1982 · January 10, 2023, 7:43am

Pff, I found it. I suddenly realised that my minimalized Domoticz instance (still have to migrate some devices) was also connecting to the DSMR host. Disabled that integration on Domoticz and now it works again in HASS. So in the end it does look like a coincendence that it started failing with the 2023 upgrade…

xtrmenl · January 10, 2023, 8:28am

i’ve reverted back to 2022.12.9 (latest working version)
my assumption is that is has to do with the unitofvolume change in the energy integration by @epenet
and that there is a conflict with the old data

strusic · January 10, 2023, 9:15am

Exacly. After update its not translated. But when I click on it its translated.

RO-Smart · January 10, 2023, 11:37am

Update 2023.1.1 runs fine, 1.2. doesn’t want (solved)
Looks like something with supervisor internet access? I’m newbie, this is my 4th HA update.
Thanks for comments
Dieter
solved: finally I solved it by taking complete from the power and restart, just hang up somewhere while updating. Now 1.4 is running fine.
additional info: several integrations seems broken (see attached screenshot)

23-01-10 11:29:05 INFO (MainThread) [supervisor.backups.manager] Found 6 backup files
23-01-10 11:30:34 WARNING (MainThread) [supervisor.jobs] 'Updater.fetch_data' blocked from execution, no supervisor internet connection
23-01-10 11:35:53 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
23-01-10 11:35:53 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
23-01-10 11:35:53 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
23-01-10 11:35:53 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.DNS_SERVER_FAILED/ContextType.DNS_SERVER
23-01-10 11:35:58 INFO (MainThread) [supervisor.jobs] 'CheckDNSServer.run_check' blocked from execution, no supervisor internet connection
23-01-10 11:35:58 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
23-01-10 11:36:03 INFO (MainThread) [supervisor.jobs] 'CheckAddonPwned.run_check' blocked from execution, no supervisor internet connection
23-01-10 11:36:03 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.DNS_SERVER_IPV6_ERROR/ContextType.DNS_SERVER
23-01-10 11:36:08 INFO (MainThread) [supervisor.jobs] 'CheckDNSServerIPv6.run_check' blocked from execution, no supervisor internet connection
23-01-10 11:36:08 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
23-01-10 11:36:08 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.IPV4_CONNECTION_PROBLEM/ContextType.SYSTEM
23-01-10 11:36:08 INFO (MainThread) [supervisor.resolution.check] System checks complete
23-01-10 11:36:08 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
23-01-10 11:36:08 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-01-10 11:36:08 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
23-01-10 11:36:08 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
23-01-10 11:37:05 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
23-01-10 12:07:06 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
23-01-10 12:30:37 INFO (MainThread) [supervisor.backups.manager] Creating new partial backup with slug f1683022
23-01-10 12:30:38 INFO (MainThread) [supervisor.homeassistant.module] Backing up Home Assistant Core config folder
23-01-10 12:31:49 INFO (MainThread) [supervisor.homeassistant.module] Backup Home Assistant Core config folder done
23-01-10 12:31:50 INFO (MainThread) [supervisor.backups.manager] Creating partial backup with slug f1683022 completed
23-01-10 12:31:50 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2023.1.2
23-01-10 12:31:50 INFO (SyncWorker_2) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/raspberrypi3-64-homeassistant:2023.1.1 to ghcr.io/home-assistant/raspberrypi3-64-homeassistant:2023.1.2
23-01-10 12:31:50 INFO (SyncWorker_2) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/raspberrypi3-64-homeassistant with tag 2023.1.2.
23-01-10 12:31:50 ERROR (SyncWorker_2) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/raspberrypi3-64-homeassistant:2023.1.2: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=2023.1.2&fromImage=ghcr.io%2Fhome-assistant%2Fraspberrypi3-64-homeassistant&platform=linux%2Farm64: Internal Server Error ("Get "https://ghcr.io/v2/": dial tcp 140.82.121.34:443: connect: network is unreachable")
23-01-10 12:31:50 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed

kevincroughs1 · January 10, 2023, 11:59am

Also had to revert to 2022.12.19, both 2023.1.1 and 2023.1.2 breaks the DSMR integration over here

samuel81 · January 11, 2023, 11:18am

2023.1.3 is out according to GitHub and the website, but no one seems to get them:

{
“channel”: “stable”,
“supervisor”: “2022.12.1”,
“homeassistant”: {
“default”: “2023.1.2”,
“qemux86”: “2023.1.2”,
“qemux86-64”: “2023.1.2”,
“qemuarm”: “2023.1.2”,
“qemuarm-64”: “2023.1.2”,
“generic-x86-64”: “2023.1.2”,
“intel-nuc”: “2023.1.2”,
“khadas-vim3”: “2023.1.2”,
“raspberrypi”: “2023.1.2”,
“raspberrypi2”: “2023.1.2”,
“raspberrypi3”: “2023.1.2”,
“raspberrypi3-64”: “2023.1.2”,
“raspberrypi4”: “2023.1.2”,
“raspberrypi4-64”: “2023.1.2”,
“yellow”: “2023.1.2”,
“tinker”: “2023.1.2”,
“odroid-c2”: “2023.1.2”,
“odroid-c4”: “2023.1.2”,
“odroid-n2”: “2023.1.2”,
“odroid-xu”: “2023.1.2”
},

Am I the only weirdo wondering why?

BebeMischa · January 11, 2023, 12:02pm

andrewjswan · January 11, 2023, 1:36pm

Build - Failure

hjatsu · January 11, 2023, 4:23pm

For us newbies this ”disable polling at system settings and then just set an update entity automation” seems about as stupid as it gets. Previously it took a second to set the interval to what ever I wanted (4 times a day) but now I had to browse through all of the Settings > System looking for something about ”polling”— and then spend 10 minutes googling that the right place is actually behind the three dots of that entity(!). Setting up automation then took just a few more minutes, trying to find an action with something about ”update”. Then I still had to learn a little about time patterns to know that I need ”/” symbol to the hour setting or else it would run just once a day.

And the reward to all this time wasted (well I learned a little in the process)? This whole thing does not even seem to work anymore! I mean, what is wrong with this? (even tried adding the entities there but no help)

Incredibly frustrating!

alias: SpeedTest
description: 
trigger:
  - platform: time_pattern
    hours: /6
condition: []
action:
  - service: homeassistant.update_entity
    data: {}
    target:
      device_id: f30b10b8d751c44fe9d700f95931e243
      entity_id:
        - sensor.speedtest_download
        - sensor.speedtest_ping
mode: single

Edit:
I can see this in the logs. No idea what ”extra keys” it is talking about. I suppose the ID should be correct as it’s added by UI. Even tried adding the device again (deleting the entities)

Stopped because an error was encountered at 11.1.2023 18.27.49 (runtime: 0.01 seconds)

extra keys not allowed @ data[‘device_id’]

Kertz1954 · January 11, 2023, 7:20pm

Try this.

action:
  service: homeassistant.update_entity
  data:
    entity_id: sensor.speedtest_ping

Copied from Central Command - 6th Jan.

nickrout · January 11, 2023, 8:03pm

The clue is in the name - update_entity not update_device.

cerebrate · January 11, 2023, 11:37pm

Having just encountered this myself, it would be useful to allow specifying a device to mean “update all entities for this device”, as it isn’t at all obvious that updating sensor.speedtest_ping will also cause sensor.speedtest_upload and sensor.speedtest_download to be updated also, or if you need to specify each entity individually, or…

(Well, I mean, it’s obvious to me, since I know how Speedtest works. It’s not obvious to the modal user.)