They are always in the release notes like was linked above. But if you were using it, you’d likely see this in your logs:
The ‘utility_meter.select_tariff’ service has been deprecated and will be removed in HA Core xxxxxxx
1 Like
Yup, I know they are. What I do not know, is when the release notes talk about “previously deprecated…”, how to find easily THAT release note, where it was announced to be deprecated.
Great to (finally) see the Fully Kiosk Browser - Home Assistant integration coming to core 
As I’m using it currently via HACS as custom integration, I was wondering what will happen once updated to HA 2022.9.
- Will it continue to work out of the box without any changes?
- Do I need to remove it from HACS and readd it from the official integrations list (HA Core)?
- Is there a difference in terms of supported features or anything else to keep in mind?
I care about these questions as it was quite some work to integrate my devices with all my customization (renaming all entities etc.) and I really hope there’s no need to go through that again 
2 Likes
FYI
If you don’t use default_config and want to use the new Schedule Helper, be sure to add schedule: to your configuration.yaml file. Otherwise, “Schedule” will be displayed but disabled in the list of available Helpers.
This information is included in the documentation for the Schedule integration. However the documentation for default_config overlooks to mention that Schedule is one of the many integrations bundled into default_config.
4 Likes
I love the new UI changes!
Is there any way to expand all the collapsible cards simultaneously instead of opening them one by one?
It’s an option I might expect to see in the … menu > Expand All Cards
As when debugging, the new UI requires lots more clicking to see all the details.
5 Likes
There are a few differences, I tried to outline them all in this issue on the repository for the custom component. Since they use different domains, it should technically be possible to run both integrations at the same time while you migrate.
3 Likes
Perfect, that answer is a) really helpful, sounds b) quite comfortable (I’m gonna compare and potentially go the registry hack and restart way) and came c) very quickly. 
Does it? I’ve just added bluetooth proxy to a couple of spare esp32’s, nothing bluetoothy is available via the esphome integration and trying to add the Bluetooth integration fails with “no unconfigured bluetooth devices connected” or similar
I think you also need ‘hardware:’ in your config if you want that functionality and don’t use default_config.
2 Likes
This was demonstrated in the stream. You do not need to add the Bluetooth integration if you do not have a dongle. The supported bluetooth devices that the bluetooth_proxy picks up will appear as if by magic in Home Assistant, ready to be configured, in the same way they would if you were using a dongle - without having to add the Bluetooth integration.
3 Likes
Scheduler! Yes! Love it! But why is the UI limit to such strict times? Also, the UI doesn’t seem to work ok the iOS companion app or mobile Safari very well… can’t select a time on the table 
1 Like
The esphome device doesn’t need its own bluetooth config entry. Everything it needs to connect the esphome device to the bluetooth manager is stored in the esphome config entry.
1 Like
Amazing update, thanks guys!
The Bluetooth remotes using ESP32s is quite interesting and I’m wondering: are devices associated to an specific bluetooth adapter/remote? Like, I added a bluetooth LED using a USB adapter that has been iffy because its quite far, if I put an ESP32 bluetooth remote close to it, do I need to remove / re-add the LED device?
If not, will it automatically use that one communicate with it? How does HA know which one to use? Does it have some sense of the signal level to each device from each adapter/remote?
1 Like
This was explained in the stream, that HA keeps a track of what adaptor has a stronger signal - so it knows which adaptor to use to communicate to the device with.
However the ESP32s right now are passive only, you cannot control a device with a bluetooth_proxy - yet. But that is being worked on.
4 Likes
Great! This implementation seems really amazing, very flexible and poweful… Kudos guys!
Looking forward to being able to use ESP32 remotes for active connections…
Great update!
Frustrating timing for me - just this week I swapped coordinator and did a full repair 🤦
Thanks but the need for the hardware key is documented in both the Hardware integration and the default_config integration.
In contrast, the schedule key is not documented in the default_config integration. That omission may trip up users who don’t use default_config and prefer to cherry-pick its integrations individually.
For those users it’s common practice to review default_config's documentation whenever there’s a monthly release to see if any new integrations were added (in August it was bluetooth). However, for September’s release, schedule isn’t mentioned in default_config's documentation but it’s definitely part of the default_config integration.
Nice work all, especially excited to try out the weekly schedule!
Happy birthday Home Assistant! 
Great release yet again.
The weekly schedule helper has enabled me to delete hundreds of lines of code and countless input_booleans, input_datetimes and template sensors.
Some things that would be nice to have (feature request here):
- A Scheduler card for displaying and setting schedules.
- Finer grained control. 30 minutes is too coarse to be of any use for my irrigation control.
4 Likes
Maybe help them get the documentation up to date? Anyone can submit a PR on any of the documentation pages, its not that difficult, there are some links at the bottom of every page for that…