-
-
Notifications
You must be signed in to change notification settings - Fork 28.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2023.8.2 #98255
Conversation
* Add device naming to Yeelight * Add extra light entity to fix superclass * Add extra light entity to fix superclass
* Fix for issue #97694 Issue #97694 points out that the visibility range is a string with a band of distances, not a single value, which is causing issues for front end components. Removed the device class to leave as an informational string value. * Removed *all* empty device_class statements * Missed an empty device_class :(
… `hw_info` (#97766) Don't assume that battery_level value is always present in hw_info
* Bumping to PyTado 0.16 and adding test coverage * Removing comment * Upgrading the deprecated functions * Updating tests to support paramterization * Delete test_config_flow.py Reverting the tests, which will be placed in a different PR. * Revert "Delete test_config_flow.py" This reverts commit 1719ebc. * Reverting back changes
* Ensure webhooks take HA cloud into account * Avoid circular import
Fix Samsung device info
Command Line template error
* Bump pysensibo to 1.0.33 * for loop
Bump bimmer_connected to 0.13.9 Co-authored-by: rikroe <rikroe@users.noreply.github.com>
* Fix homekit_controller triggers when value is None * fixes * cover
* bump to 0.32.2 * fix test
Co-authored-by: alexyao2015 <alexyao2015@users.noreply.github.com>
…IP address (#97953) Fix missing key and cert
The tomorrow.io integration isn't working for new users due to changes made by tomorrow.io. This fixes that with the following changes: * Add 60 minute timestep option * Change default timestep to 60 minutes
Bump bellows to 0.35.8
Can this be added to the patch release please? |
@bdr99 That PR was merged two days ago? How is this comment made only now and here? 🤷 |
@frenck I had asked in the PR description if it could be added to the next patch release. I noticed that it wasn't added, so that's why I commented here. Is there some other place I should be asking instead? |
Well, the PR should have been the place to handle this, before this all happens. I will add it, but it sets me back about an hour in the release process. Just to give a small idea:
Like, I'm happy to do that. But it is better to avoid :) ../Frenck |
@frenck Thank you, and sorry to cause you all of that extra work. If there is anything I should have done differently to prevent this from happening, please let me know. I'm not sure what I could have done beyond asking in the PR description. |
No problem, as I said happy to do that. It was missed in the PR review, which is a bummer. But something you could have checked for after the merge maybe. It is interesting though, as this happens at times. But it also just now made me realize how often we ask if something should or should not go into a patch release in reviews. Maybe something the bot / PR template could help us with 🤔 ../Frenck |
Maybe for a discussion elsewhere but clicking the bugfix in the PR description and/or write as such in the PR title would have helped (and could be picked up by the bot) |
In PR description link to docs PR is wrong and is home-assistant/home-assistant.io#28540 |
battery_level
value is always present in Tractivehw_info
(@bieniu - #97766) (tractive docs)pyairvisual
to 2023.08.1 (@bachya - #97999) (airvisual docs) (airvisual_pro docs) (dependency)Docs PR: home-assistant/home-assistant.io#28540