I did a config check and I get this…
Platform error weather.darksky - Integration ‘darksky’ not found.
I have checked everywhere and I cannot find this anywhere… suggestions? It’s not in my config or anywhere in my lovelace.yaml, I checked all my automations…sensors etc…
I’m trying to figure out how to find the error so I can restart…
Thank you all!
Tinkerer
(aka DubhAd on GitHub)
April 12, 2023, 11:18am
2
It would be under weather:
For what it’s worth, Apple bought Darksky a few years ago and announced that their API would be shut down after a long grace period. That ended recently, so Darksky is no more…
Dark Sky has been removed with 2023.4.
Dark Sky has been removed. Apple acquired Dark Sky, and the API has now been shut down. (@gjohansson-ST - #90322)
home-assistant:dev
← gjohansson-ST:darksky_depr_start
opened 09:01PM - 26 Mar 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
Darksky API has been shutdown as per March 31st making the integration not operational. See integrations page for other weather providers.
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
As of March 31st Darksky shutdown the API resulting in a non function integration.
Start deprecation notice (issue) for users who still has integration.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [x] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/26740
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [x] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
1 Like
Yeah I know Apple owns that now… I write modules for other programs so I’ve known it for a while and had to remove it all from my code there…
Still have to find in my HA instance where it is… like I said I’ve looked through everything…
Don’t have that in my config
So it’s not there
petro
(Petro)
April 12, 2023, 12:07pm
7
just search for darksky
. There’s multiple ways to integrate it, all of them use that key.
EDIT: FOUND IT!!!
hahahahha
Thank you!
Yes I get that… I’ve been searching… every single file…integrations…not there.
ui-lovelace, config, etc… All taken out and not there and I keep getting that error…
Other suggestions on how to search everything without spending hours looking at every single file?
Thank you!
petro
(Petro)
April 12, 2023, 12:12pm
9
… Have you never used a find in files function? Notepad++, VSCode both have the ability to search for words in files.
Things like this take 1 minute to find tops. You have to use the correct tools.
Yes I have
But I finally found it!!! Thank you!
Perfect use for the Linux grep command…
1 Like