Moon sensor after this update is broken. Before translation was working well, now it shows like that
How do you expect it to look?
So is the post I replied to.
Thats fine, and nobody is questioning the decision or arguing about this. However, as you have seen, there was some confusion/surprise why this was changed, therefore I suggested that it might help to avoid this by mentioning the background for the change in the PR.
Erm… nope. Frankly, repeating what others have said in a condescending tone, while completely missing the point of the comment/suggestion and pointing to the changelog (which everyone was aware of and does not contain the referenced info), isn’t really that helpful.
Well whatever - I made my suggestion to include background info, not wasting more of my time with pointless arguments here, good riddance.
4 Likes
I’m seeing the same. The sun entity is translated to my language, but the moon entity stays in english. In the past it was also translated…
I see, frontend issue then I think.
Thank you for editing your post.
You said that, which is why I linked to the full release notes. You gave no indication that you knew this. I don’t know what is so offensive about calling someone out for saying unjustified things. And I was trying to be helpful with my first post by giving you a generic solution to the problem — regardless of whether I agree with the original change of deprecating setting a scan interval. You only complained and gave no indication that you knew any of that until after my post.
4 Likes
Dsmr is still working correctly here
However the ha energy is showing strange figures
I consumed 99,9 of my solar generation (solar generation is added to full electricity usage) and no feed to the grid
Whilst dsmr shows 5kw Backfeed and 5kw less consumption
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?
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.
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”.
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
i tried everything … nothing works here … still:
“Error 400: invalid_request”
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?
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.
Thx,
I get that, however, it worked fine before the 2023.1.x updates…
Nonetheless, I will check the DSMR device once again.
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…
2 Likes
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
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
