petro
(Petro)
August 2, 2023, 5:56pm
2
For questions about MQTT Repairs or log warnings, please see this thread:
Everyone, there will be MQTT name changes in the next release of the software. There is nothing to worry about, your names are safe. However the change caused addons like Z2M (and other MQTT integrations) to update their discovery information. As it stands, Z2M will not be able to release a version with this fix until September 2023. During that time a warning will be in your logs indicating that there is an issue. You can safely ignore this warning. As of this writing, there may also be aâŚ
23 Likes
Thanks for another great release!
One thing bugs me in the year of the voice: newly added entities are exposed automatically to assist.
Therefore I made a feature request to make that optional.
If others find that useful, too, please vote here .
3 Likes
syphernl
(Frank)
August 2, 2023, 6:55pm
4
The âoldâ Nest API is supposed to go offline in September, yet after upgrading to 2023.8 the Nest integration wonât load anymore. Nothing is mentioned on the release notes, odd⌠Anyone else experiencing this?
Oof. Apparently it is listed in the full changelogs. I would have expected this in Breaking Changes.
Thrasher204
(Johnathon Thrasher)
August 2, 2023, 7:04pm
5
I just got a weird issue. After the update all my TP link Power strip devices are linked together. So when i turn on/off a single plug all of them turn on/off.
Update this was resolved in 2023.8.1
anderstbl
(Anders Tore Boye Lauridsen)
August 2, 2023, 7:04pm
6
Was a surprise to me as well. Is there a way to get my old Nest camera working again without going back to 2023.7 ?
UPDATE: It works again for me, in 2023.8
Updated for OPower integration, gave it my login info for Evergy and it is coming back with
Logger: homeassistant.config_entries
Source: config_entries.py:952
First occurred: 2:09:28 PM (1 occurrences)
Last logged: 2:09:28 PM
Config entry âEvergy ({username@}gmail.com )â for opower integration not ready yet: 401, message=âUnauthorizedâ, url=URL(âhttps://kcpl.opower.com/ei/edge/apis/multi-account-v1/cws/kcpl/customers?offset=0&batchSize=100&addressFilter= â); Retrying in background
Just want to get that feedback out asap for the dev great release!
poudenes
(Poudenes)
August 2, 2023, 7:21pm
8
openai_conversation.generate_image
2023-08-02 21:20:11.213 ERROR (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Error executing script. Error for call_service at pos 1: Error generating image: Billing hard limit has been reached
Do we all try to create a image of a cat
Documentation seems rather incomplete. For example, how do I actually do the âplay {album} by {artist}â example? I set the trigger but how do I actually pick the media in the media play service? Also, I donât see any Event entities in MQTT - do these somehow start to appear orâŚ?
EDIT: following issue is just cosmetic
Also I haver absolutely no idea what to do with this, even after reading the link. Like am I supposed to rename dozens of devices??
6 Likes
Anyone else having issues with their KASA (TP-Link) KP200 devices not working correctly? I cannot control both sockets individually anymore.
yep same here. ⌠sometimes I wonder if the HA guys have an April 1st once a month inventing things which cause lots of work for simply nothing.
Naming entities by their device is more but just common and if not possible one must raise a request since that ensures to regonise them most easily.
1 Like
This one is fine, a kind guy sent me this on Mastodon
No action required.
TheFes
(The Fes)
August 2, 2023, 7:39pm
14
That will be your personal billing limit. The Open AI integration is not for free
nickrout
(Nick Rout)
August 2, 2023, 7:45pm
15
Really? Read the thread linked in the second post in this thread.
3 Likes
syphernl
(Frank)
August 2, 2023, 7:48pm
16
Thatâs weird as the Nest legacy folder has been removed from HASS
Iâve been trying to get (at least) my Thermostat back to work using SDM but so far no luck. It pairs, but gives an error and then shows no devices.
Also have to see how I can get the Nest Protectâs back up.
1 Like
djbuell
(DJ Buell)
August 2, 2023, 8:12pm
17
Yep. Turn on 1 plug, it turns on the whole strip. Rendered most of my automations useless, had to restore from backup.
Hi Guys,
As always I went through the full changelog and again I am (as always) amazed by the shear amount of issues you guys have been handling. Really impressive! There is one I a missing though. The UOM âbugâ failing pass through at the Utility Meter integration. Next time But otherwise really impressive!
The camera responses are really much faster
1 Like
Thanks for the release. But this change I donât fully understand. Suddenly my media controls are completely gone (not only âdisabledâ) when Spotify is inactive (which happens a lot) and my UI starts to jump up and down. GrrrâŚ
home-assistant:dev
â joostlek:spotify_active_session
opened 06:31PM - 19 Jul 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N⌠OT DELETE ANY TEXT from this template! (unless instructed).
-->
## 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.
-->
At the moment when not having an active device, the spotify media player shows controls to browse media or just click play. Except when you do this, you are greeted with a message in the bottom left corner saying Connection lost. The logs say `No active playback device found` which is technically correct.
To solve this there would be 2 options, or just picking a random device from your device from the Device coordinator and playing the music there, or just to disable the supported feature when the user isn't playing on any device. To allow selecting another device to start playing, we still allow select source.
## 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
- [x] 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)
- [ ] 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 #95397
- This PR is related to issue:
- Link to documentation pull request:
## 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.
-->
- [x] 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`)
- [x] 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:
- [ ] 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/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
Itâs even worse. Same with all my Alexa/Echo devices. They are inactive most of the time by nature. Still I could and often wanted to control their volume. I could do so via the entities card. Until now. Now, no controls are shown when idle. This is not good.
Any chance to bring back the old behavior? Please âŚ
3 Likes