petro Great contributor
Nice work. Been using the beta, it’s been rock solid. Thanks 
Nice work. Been using the beta, it’s been rock solid. Thanks
Nice work, and still waiting for the most requested automation organizer/labels! #69996 
What happened to tuya? We haven’t seen anything Bluetooth for tuya as well!!
I almost never upgrade to the .0 release anymore, but I am very tempted to do so to start re-working my dashboards with sub views.
Sub views rock, great feature!!! Thank you all…
Posted in wrong thread, apologies.
Those sub views bring us a big step towards those beautiful pop-up-like boxes which hover above the current view (which is blurred) as seen on many custom themes.
I really hope this is a first step into that direction so we can have those beautiful dashboards one day without custom frontend integrations. I‘m sure the new colleague and Mushroom cards designer will bring much experience for this so we all profit from this in the future.
Great update!
1 reply
Thanks everyone, great update again.
I feel like I need to buy Bluetooth stuff
Thanks for this, too late to start updating & checking today.
One question for starters: I have some time ago even started a question thread in the forum about how to customize panel overly rounded corners away, because I #!&%%#¤& hate them.
So: how to remove those restyled rounded corners??
1 reply
So many exciting things this month 
I’m happy to have iBeacons working without the need for a custom integration from HACS.
But Zigbee & Matter are supposed to be built into the Yellow, which is the main reason I ordered one – whenever it was first announced.
Nope. Makes no sense, was mentioned during the session
Sorry…misread you question I thought you were looking for a point of sale for the skyconnect.
I believe the zigbee chip in the yellow will also support Matter. However, I’m not sure if it will allow them to run concurrently like the skyconnect.
Active BT requires an updated version of EspHome that is not yet released. Hopefully very soon 
. I’m itching to test it out myself.
The release notes
For this occasion, ESPHome will have an additional release, which adds this functionality.
I’m still a bit confused on the Active Bluetooth functionality. I have 3 esp home proxies that I flashed with the software via the steps from the previous release.
Today, both the esphome add on and the devices themselves had software updates.
Sooo…do I have to do anything at this point? I’ve seen in videos where you have to put Active in the YAML vs reflashing them per this update vs waiting on an update on these comments.
Can I get instructions on updating proxies to work if you have them set up already?
1 reply
From the ESPHome docs:
Configuration:
bluetooth_proxy:
- active (Optional, boolean): Enables proxying active connections. Defaults to
false. Requires Home Assistant 2022.10 or later.
Assuming you’re on ESPHome 2022.9.3 and HASS 2022.10.0, add active: true to your bluetooth_proxy config and re-flash your device.
Subviews - this feature is revolutionary!
IMHO many people now will start to rewrite their dashboards)).
Passing data to Google Sheets - for me the 2nd great feature.
Since I am still a beginner, not using many integrations so far…
We need much more information on how Matter / Thread is going to work.
I don’t know if I NEED to get the SkyConnect because it’s unclear how the fabrics etc work.
I have 2 Google Nest Gen 2 displays, which we know will be getting thread activated and matter enabled soon, so if matter enabled devices are added to Google Home - can they then be shared to the Home Assistant fabric without Home Assistant needing an actual radio?
I had hoped we were going to learn at least a bit about this when the release video said they were going to discuss matter at the end.
2 replies
Right but the whole point of multiadmin in matter, is that you can share devices to other ecosystems. Eg - you can add a device to Google Home, and then share it to Alexa, Apple, SmartThings etc - but in these cases, all these ecosystems have their own radio, so that is the part I don’t understand. It doesn’t make sense that a device talking to 5 (that’s the matter maximum) different ecosystems would be physically talking to 5 different networks too. Each ecosystem has something called a fabric, which essentially handles security and authorisation - by installing certificates on to the matter device.
But ideally we could do with some confirmation of this.
2 replies
Sounds nice? I don’t trust google or amazon. We shall see. I’ll keep you posted when I get mine.
So the dashboard sub views are really cool…but how do I get the parent button (i.e. the button you use to navigate to the view) show the state of the items in the subview? I’ve moved all my lighting cards into their own areas (i.e. subviews) so now you no longer need to scroll through a long list - just a couple of taps and you’re done. However, on the ‘home’ page all the buttons show an ‘off’ status even though for some of them there are lights on…I just have no way of knowing this now without trawling through each subview…
Is there an easy way to create some sort of state linkage between subview state and the entities in the subview?
1 reply
Nice! That works well… 
I appreciate the Automation Editor’s ability to display automations that don’t reside in automations.yaml (100% of my automations). The read-only view is very convenient and the Migrate feature is a nice addition as well (although I won’t be using it anytime soon).
Nice to see the Automation Editor is getting some needed attention (including last month’s major facelift). Keep up the great work!
2 replies
That’s up to how you’ve organized your ESPHome. By default, yes, you would add that to each config file. You can also use something like packages to modularize things. That’s what I do: I have a ble_proxy package that contains common BLE proxy configurations, then import that package into each proxy device’s config.
Although designed to work together. Thread is not the same as Matter. The two are not dependent on each other.
I doubt HA will tie Matter support to Thread. Matter is effectively an IP protocol. I don’t see why HA would need a radio for any Thread-via-Matter device as long as the border router is behaving in an open way.
Still, I’m skeptical there won’t be less than open implementations. Even if fully open at first, I wouldn’t trust the Google/Amazon types not to handicap it later on.
I’ll be sitting on the sidelines until the dust settles.
1 reply
Thanks. This is sort of what I was thinking - it seemed unlikely to me that a device would join multiple thread networks in order for multiadmin to work, but most of the videos on Matter focus on matter specifically. Perhaps I need to find go and find some deep dive videos on Thread and Border Routers.
I’m in the middle of deciding if I want to get Nest WiFi Pro, which would mean I would have 3 border routers in my home (that’s obviously not the only reason I’m thinking about it though).
@laxarus I am using my BT enabled smart lock using HomeKit Controller and ESPHome BT Proxy. I used USB adapter before, however after a moment of not using the device, triggering action would take around 10 seconds. I was told this could improve timings since ESPHome uses different way of using BT, however my tests so far are not cheerful. Few issues even pairing the device. And now actions take literally minutes. Plenty of errors related to some sort of timeouts and read errors. I hope this is something either directly related to my ESP (using M5StickC) or that can be easily fixed.
Some more info here: Bluetooth Tedee lock via HomeKit Controller · Issue #79461 · home-assistant/core · GitHub
Anyone able to get Thread with HomeKit controller working? I tried both an eve smart plug and nano leaf essentials bulb but keep getting errors. HA is on the same vlans as my HomePod minis and I followed the pairing instructions.
YAML automations to UI is AMAZING. Can’t wait.
Looking at ESPHome 2022.9.0 - 21st September 2022 — ESPHome it should work in 2022.9.3, sorry for the misinformation.
1 reply
it just stops compiling when I’m on 2022.9.3 (2022.9.1 is fine) no idea why, very strange, i’ll keep hunting
Thanks, I’ll give that a shot!
Well, my energy dashboard is blown showing watts as kilowatts.
Confirmed working. Thanks again - been looking forward to getting these thread-capable bulbs in HA for awhile!
some of them work according to the docs, I have one of these on the way tomorrow
https://www.home-assistant.io/integrations/govee_ble/#supported-devices
Wonder if there are any outside bluetooth temp sensors with a display, that Govee H5102 is tempting to keep in a dry area and test it out 
The version mentioned in this thread, HA 2022.10 and esphome 2022.9.3
I think I misunderstood what this does, but I’m confused. I was already using my esp32 to receive BLE signals from devices, but I thought having it be a proxy would basically be a range extender for Bluetooth, like through the Bluetooth integration. Is this new change only to allow active connections?
As for “Edit yaml automations in UI” feature:
I can see that this is a continuation of a “move everything to UI” trend (which I dislike since in some cases it causes deprecation of yaml).
For me, I see no scenarios when I decide to edit automations in UI.
Yes, I do create automations in UI - but only a skeleton automation, just for testing small things.
One more thing about “yaml vs UI”.
Today I got a warning about a “season” integration.
I kept it in yaml:
sensor:
- platform: season
name: season
type: meteorological
Now people MUST have this integration in UI.
And surely this integration does not allow to CHANGE the “type” option - I need to REMOVE this integration and then ADD AGAIN with a new settings.
Agree that in a real life users do not need to change this option.
But this is just a small example.
In many integrations moved to UI people CANNOT change settings - they have to REMOVE->ADD AGAIN.
This is not a good approach.
Not edit, view. If you made an automation in yaml outside of automations.yaml you still cannot edit it in the UI. But now you can view it read only in the UI editor.
Which frankly is extremely handy. I have all my automations in yaml packages and I can’t tell you how many times I’ve clicked that pencil icon just hoping to look at it and been disappointed when I remembered I couldn’t. Often if something is broken I only have my phone and studio code really doesn’t work well with that. And if I wait until I’m back at my computer Im probably going to forget about and any traces will be gone.
So yea, I think it’s pretty handy. Even if you never plan to hit the migrate button. Particularly for the phone look use case. Ive played “try to find the bug” with ssh to vim on my phone enough times to know it’s not all that fun. I mean I’m still going to do that to fix the bug but at least I will already have identified the issue and know exactly where to go.
1 reply
Probably you are right. I myself never got (so far) into situation when I need to change ASAP something - due to limited possibilities of my HA setup. But on my iPhone 5S (640×1136) it will be quite a challenge to fix a problem… Currently I only manage to open AnyDesk, login to remote home PC, then start Putty, then start SSH session and type something in a console (like “sudo docker stop HA”).
yeah, it’s a bit of a mystery yet whether eg Samsung Smart tags or the Tiles will be supported. I did see several carkits and Traffic spotters registered, along with a few Fitbits of passersby
What would be the generic usecase for these beacons. They’re not accurate enough to allow for room presence, and we should use them for in/out of home mainly. I know when my Bins (4 of them) are out, as I do for my car.
What else would be useful to add to HA logic?
1 reply
Anybody else uses a promity sensor as a numeric trigger getting these warnings on startup and automation reload now? Automation still triggers fine. Warnings are new, nothing has changed on my end. Didn’t see anything in the release notes.
WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing '[Notify] Presence LED Notification' trigger: In 'numeric_state' condition: entity proximity.sphone_home state 'not set' cannot be processed as a number
- platform: numeric_state
entity_id:
- proximity.jphone_home
- proximity.sphone_home
below: 4 # km
Unfortunately, looks like the broken import of the Pushover configuration from 2022.9 is still broken in 2022.10.0. At least, the Pushover UI still does not allow any manipulation of any configuration settings.
Any thoughts on this? Am I best deleting this and starting over, rather than persisting with the automated import, or do I need to reset this to get it to reattempt the import with 2022.10?
I’ve tried to update but it seems that updating the core my automations report issues, downgrading solves the isssue bu now I’m stuck to 2022.9.7.
If someone’s having the same issue please report here 2022.10 core update broke automations
OK here, but I have a simpler config:
ESPHome allows you to generate a iBeacon. Works flawlessly for me.
I use one the other way round. Opening a door when I approach it. Using iOS app geofency to fire a webhook when I approach it.
1 reply
right, a fixed beacon. thats smart ofc 
how does the iOS fire a web hook? Id love to give that a try.
The app that allows to fire a webhook based on zones or iBeacons is called Geofency.
Works flawless.
You can either act on the webhooks directly or do something like that:
I do not understand why webhooks do not fire events by their own.
There shall be a list of known webhooks to prevent DOS but then just convert them to events.
I might change my code to derive the event name to be the first part of the hook up until a ‚-‘, e.g.
Edit: added a WTH on that. 
Do you happen to know of an equivalent android app? I have searched the play store, but there are dozens of apps. I could test a whole lot of them, but if anyone can point me in the right direction…
I had the same issue on my phone app. Restarting the app fixed the issue. Maybe clear (browser) cache?
After updating to Version 10.0 I’m getting an error that I need to upgrade to 9.0! What gives?
It is indeed browser cache. Reload the web page helps.
The Google Sheets integration is awesome! It’s nice to be able to quickly write some info to a sheet so I can review it later.
wow, this is quite something. It must be the most cautiously written paragraph in the full HA interface, trying to touch all and not forget anything…:
For a second I thought this was an April 1 prank… wont prevent from starting…
Aware why this has become what is has become, why don’t we change that Check configuration to Check Yaml syntax, and if ok return 'Yaml syntax is ok`.
It would also immediately make clear why this is on this (Yaml) page
In a second line we could point user to the advised way of real config checking: Terminal and ha core check
Just upgraded to 2022.10 and getting the following timer error which was not present on 2022.9.6. No changes to config.
Any help is appreciated or I’ll be rolling back as I use the timers religiously.
Running the following on dedicated intel NUC:
Home Assistant 2022.10.0
Supervisor 2022.09.1
Operating System 9.0
Frontend 20221005.0 - latest
Logger: homeassistant.setup
Source: helpers/collection.py:182
First occurred: 8:43:59 AM (1 occurrences)
Last logged: 8:43:59 AM
Error during setup of component timer
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 235, in _async_setup_component
result = await task
File "/config/custom_components/timer/__init__.py", line 144, in async_setup
await yaml_collection.async_load(
File "/usr/src/homeassistant/homeassistant/helpers/collection.py", line 211, in async_load
await self.notify_changes(change_sets)
File "/usr/src/homeassistant/homeassistant/helpers/collection.py", line 161, in notify_changes
await asyncio.gather(
File "/usr/src/homeassistant/homeassistant/helpers/collection.py", line 418, in _collection_changed
for entity in await asyncio.gather(
File "/usr/src/homeassistant/homeassistant/helpers/collection.py", line 375, in _add_entity
entities[change_set.item_id] = collection.create_entity(
File "/usr/src/homeassistant/homeassistant/helpers/collection.py", line 182, in create_entity
return entity_class.from_yaml(config)
AttributeError: 'function' object has no attribute 'from_yaml'
except, it doesn’t. Is it now an official functionality, then I can raise a github issue
Refresh the page.
The selector was updated to allow multiple entities.
service: zwave_js.refresh_value
data:
entity_id:
- switch.in_wall_toggle_switch_500s
If you use a list instead it works. The “fill example data” needs to be update. Either input will still work in automations.
1 reply
You have an invalid device trigger in an automation. Post the automation that’s not available.
Thanks, must have forgotten/missed I was using custom timer and not integrated timer 
