petrho
(Peter)
September 4, 2024, 6:03pm
10
Hi, why is some of the untracked consumtion negative value?
e-raser
September 4, 2024, 6:15pm
11
Are there no “Other noteworthy changes ” this month or is it a bug (because it is listed in the index on top of the announcement page but the section does not exist)?
so my sections doesnt change same as before anything wrong?
there are no settings like in the screenshot
rsonke
(Rob)
September 4, 2024, 6:32pm
13
Maybe you have some overlap/duplicates in what you measure individually?
balloob
(Paulus Schoutsen)
September 4, 2024, 6:37pm
14
Good catch. That was an empty link in the TOC, I removed it. Noteworthy stuff is under integrations sub-header.
2 Likes
e-raser
September 4, 2024, 6:41pm
15
I guessed it’s a template thing. And I just needed a new - admin approved, what a great bonus - proof that I read the release notes (usually twice)
petrho
(Peter)
September 4, 2024, 6:45pm
16
Can it be a rounding error?
Upgrading before the release live broadcast , that’s new …
zigomatic
(zigomatic)
September 4, 2024, 6:58pm
18
There is a functionality for changing the faulty in dev tools - statistics.
But for me, for my case, the DB was updated but the bar graph was not.
I clocked the August to Yale integration change for my Connexis lock. No biggie there.
Seems the Yale Smart Living Integration for my alarm and Key Fre Connected lock is borked by the update - in process on github. I’d suggest anyone using it to hold fire if you need it!
brunosabot
(Bruno Sabot)
September 4, 2024, 7:12pm
20
Just for the wider sections, this update is incredible! Thank you soooo much!
Edit: guess who just updated his dashboards with a column_span option!
2 Likes
PlayFaster
(Play Faster)
September 4, 2024, 7:37pm
21
Hi. I have seen this before on previous updates. In my case, the problem seems to resolve itself, usually within an hour. Not sure if the same will happen in your case …
extrem nice update, big fan of the untracked energy dashboard. Would be great if its also included in the individual devices total usage
view
5 Likes
_pm
(Peter)
September 4, 2024, 8:06pm
23
Whoohoo! Was waiting for the wider sections, thanks!! This will be the moment to convert my existing dashboards
1 Like
Currently I am using my Yale lock with August integration. In core version 2024.9 they ask to replace August integration with the Yale integration. I am trying to configure the Yale integration but none of the options work with my current username and password. Is there a problem?
phidauex
(Sam)
September 4, 2024, 8:27pm
25
Same problem here, can’t log into the Yale Home integration. My guess is that it may be locale based - in most of the world, other than North America (or maybe just USA?), people were migrated in 2023 from the Yale Access app to the Yale Home app, which imported their login information from Yale Access as part of the migration, but which I gather is a separate system.
However, for some reason that is completely unclear to me, USA/North America is still on Yale Access, and we can’t download the Yale Home app, or migrate accounts.
There may be some other way to migrate, but I wasn’t able to determine it from Yale’s documentation.
rodak
September 4, 2024, 8:29pm
26
Are you selecting the correct Yale integration?
For me, this worked without issues:
iona
September 4, 2024, 8:41pm
27
I can’t seem to adjust the new Section Width for existing sections with cards in them for some reason, it works only for new blank sections.
Adding column_span: 2
manually via yaml works fine however.
krismarc
(Krzysztof)
September 4, 2024, 8:59pm
28
You missed to mention new UI configuration for LCN integration.
…I was awaiting for a while for this one
home-assistant:dev
← alengwenus:dev-lcn-frontend
opened 06:02PM - 22 Jan 24 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
This adds a custom panel for the LCN integration. The panel allows to add/delete LCN devices and entities and thus replaces the configuration via configuration.yaml. Along with the panel a Config Flow is added which allows setting up a new LCN integration via a host device.
The configuration via configuration.yaml is marked as deprecated, however an import is still possible.
## New requirement
lcn-frontend - the package containing the panel frontend code https://github.com/alengwenus/lcn-frontend
## Screenshots
Add/delete devices for LCN hardware modules/groups
![lcn_devices_small](https://github.com/user-attachments/assets/71dbceb7-e2c0-40c4-967f-e29b8f8edfe0)
Add/delete entities to a LCN device for the corresponding domains.
![lcn_create_entity_small](https://github.com/home-assistant/core/assets/26517052/2366b7f7-57ee-4efd-a7ee-6caf955adbb6)
## 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!)
- [x] 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 #
- 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 Ruff (`ruff format 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:
- [x] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [x] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [x] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [x] 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
Bigger wider sections for big cards, smarter energy monitoring, a new LLM option, Works with Home Assistant Matter devices, and more open source.
1 Like
phidauex
(Sam)
September 4, 2024, 9:05pm
29
I tried both “Yale” and “Yale Home” from the list, and both seem to direct to the same login flow (below), and neither accept my usual Yale Access account info, which works on both August and Yale Access apps.
What region of the world are you in? It seems some regions may have been migrated to the Yale Home accounts, and other regions (USA/NA) are still on Yale Access only.