Testers needed for config flow integration update
See original GitHub issueHi everyone,
Since I launched this a year ago, I’ve been blown away by the enthusiasm and support I’ve received for this project! It’s been amazing to hear all the different use cases, and the API has improved considerably over the past 12 months.
One important update is to modernize this integration away from just relying on the Home Assistant Dark Sky integration to one that can be setup from the GUI, uses coordinated updates, and supports modern Home Assistant API calls. In short, this is that update.
For anyone interested, I’m looking for some people to try out the new version and get some feedback on what works, what doesn’t and where the rough edges are. From my testing, everything seems stable, but since this is a major change I want to test it out as much as possible before a wider release.
As a starting point, this version should behave exactly the same way the production one currently does. If you have an entry in your configuration.yaml. then a new weather entity and/or sensors will be created, and should be identical. Anything else is a bug. Moreover, this integration should now be able to be set up from the GUI integrations page, producing the same integrations that currently exist.
To install and test this version, you’ll need to manually patch the “dev-config-flow” branch into your custom_components directory using SSH and restart Home Assistant Core:
cd "/config/custom_components/"
mv "/config/custom_components/pirateweather/manifest.json" "/config/custom_components/pirateweather/manifest.json.old"
mv "/config/custom_components/pirateweather" "/config/custom_components/pirateweather.old"
git clone --branch dev-config-flow https://github.com/alexander0042/pirate-weather-ha.git
mv "/config/custom_components/pirate-weather-ha/custom_components/pirateweather" "/config/custom_components/pirateweather"
The two outstanding known issues are cleaning up the text options for the monitored conditions, and updating the installation instructions in the README, but I’m sure more will crop up as people start using this version.
Thanks again for the help, and let me know it goes!
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:61 (26 by maintainers)
Top GitHub Comments
OK. I did a hard CPU reboot and re-followed your instructions and all seems to be working.
So, according to logs, I can completely delete the pirateweather data from configuration.yaml now that it’s been imported?
And we’re live! I pushed this update out via HACS today, so I’m going to close this thread for now. If (when) other issues come up with the update, please open new issues and we can tackle them one by one.
Thank you again for everyone for helping to debug this, I really appreciate the help, and wouldn’t have made it to a release without the feedback here,