Comments (17)
I removed then readded in v3 mode, restarting still shows the alert and still produces this error. I have a working integration and an repair message that I can't dismiss.
Logger: aiohttp.server
Source: /usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py:421
First occurred: 10:24:18 AM (1 occurrences)
Last logged: 10:24:18 AM
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 543, in _handle
resp = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 114, in impl
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
result = await handler(request, **request.match_info)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin
return await func(self, request, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 70, in wrapper
return await method(view, request, data, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/repairs/websocket_api.py", line 130, in post
result = await self._flow_mgr.async_init(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 333, in async_init
flow = await self.async_create_flow(handler, context=context, data=data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/repairs/issue_handler.py", line 76, in async_create_flow
flow = await platform.async_create_fix_flow(self.hass, issue_id, issue.data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/openweathermap/repairs.py", line 60, in async_create_fix_flow
assert entry
AssertionError
from core.
Experiencing the same. When clicking I get an error 500.
from core.
I Think I might have a workarround for OpenWeatherMap API V2.5 deprecated" stays active after service was removed.
- Remove openweathermap
- Restart HA
- If error persist push the repair button.
- Re-install the openweathermap again with Openweathermap app including the API V3.0
- To be shure restart HA
from core.
it should be removed on next HA restart
from core.
And I thought I had a lack of knowledge. Now I see there are more strugling with this error.
from core.
I Think I might have a workarround for OpenWeatherMap API V2.5 deprecated" stays active after service was removed.
1. Remove openweathermap 2. Restart HA 3. If error persist push the repair butten. 4. Re-install the openweathermap again with Openweathermap app including the API V3.0 5. To be shure restart HA
This workaround is working for me.
Thanks a lot @HSA1963
from core.
Step 4 might be ignored if you don't need the integration anymore. Step 5 is always better to be done
Step 3 ended with the error message “Repair problem”. That's why I thought I also needed step 4.
But after the third restart of Home Assistant it worked. Thank you very much.
from core.
Patch #119289 was just released in 2024.6.2 update that says this persistent v2.5 message is fixed.
Well, I just installed this update, and I'm still getting this error. Anyone else?
The developer changed the creation process of the Repair, making it non-persistent. Since yours was created before the update, I assume it is (and remains) persistent. This fix will only work for installations where the update to 2024.6.1 has not yet been applied and the repair has not yet been raised.
from core.
Hey there @fabaff, @freekode, @nzapponi, mind taking a look at this issue as it has been labeled with an integration (openweathermap
) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of openweathermap
can trigger bot actions by commenting:
@home-assistant close
Closes the issue.@home-assistant rename Awesome new title
Renames the issue.@home-assistant reopen
Reopen the issue.@home-assistant unassign openweathermap
Removes the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-information
Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-information
Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
openweathermap documentation
openweathermap source
(message by IssueLinks)
from core.
getting the same error repair message. removed 2.5 and upgraded to 3.0 which is working fine, except for the repair message.
from core.
I Think I might have a workarround for OpenWeatherMap API V2.5 deprecated" stays active after service was removed.
- Re-install the openweathermap again with Openweathermap app including the API V3.0
Unfortunately, I cannot activate API 3.0 because I do not have a credit card. However, a credit card is now required. I would therefore appreciate it if I could remove the integration without taking out an unwanted subscription.
from core.
I Think I might have a workarround for OpenWeatherMap API V2.5 deprecated" stays active after service was removed.
- Re-install the openweathermap again with Openweathermap app including the API V3.0
Unfortunately, I cannot activate API 3.0 because I do not have a credit card. However, a credit card is now required. I would therefore appreciate it if I could remove the integration without taking out an unwanted subscription.
Step 4 might be ignored if you don't need the integration anymore.
Step 5 is always better to be done
from core.
Patch #119289 was just released in 2024.6.2 update that says this persistent v2.5 message is fixed.
Well, I just installed this update, and I'm still getting this error. Anyone else?
from core.
Thanks for the clarification. So bottom line, I should not expect that any future PR can remove this persistent error msg for an existing 3.0 install, and that a reinstall is required.
from core.
Thanks for the clarification. So bottom line, I should not expect that any future PR can remove this persistent error msg, and that a reinstall is required.
I don't know if the developer will find a solution therefore.
But the workaround described by HSA1963 seems to work. (for me at least)
1. Remove openweathermap
2. Restart HA
3. If error persist push the repair butten.
4. Re-install the openweathermap again with Openweathermap app including the API V3.0
5. To be sure restart HA
from core.
I can confirm that the above mention workaround worked for me as well. Thanks for posting your solution!
from core.
workaround worked for me too
from core.
Related Issues (20)
- ecovacs - DEEBOT N10 MAX+ (clojes) - No response received for command "getMapSet_V2" (6 occurrences) HOT 1
- MQTT integration unable to use MQTT SSL HOT 1
- WolfLink with CWL2 "Fehler beim Einrichten: Überprüfe die Protokolle" HOT 4
- Error setting up entry Wemo for wemo HOT 4
- EzViz: translation missing HOT 1
- WiFi will disconnect and be unable to connect again when Home Assistant Core start
- Dallas Temperature Sensor no longer recognized HOT 1
- Squid Web Proxy Domain Filter HOT 3
- Some HomeKit Bridges duplicate devices and entities HOT 1
- Service `automation.trigger` not working as described re: `trigger` variable
- Incorrect firmware update notification for La Marzocco HOT 2
- ping is inconsistent/ambiguous for matter devices HOT 1
- missing fan_mode icons on daikin tile card
- Opower "Unknown Error" HOT 3
- Can't access Windows share owned by user containing a space HOT 1
- Tuya - Wrong Device Category Entered By Manufacturer. DP Instructions Not Used. HOT 3
- sharing home assistant HOT 2
- Netatmo 443 error HOT 15
- Local Roborock Integration entities becomes unavailable when the internet is down HOT 3
- Unit System not retained across restarts
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from core.