One idea would be to use a short “for” in the automation so that you have to be in the zone for say 30 seconds or 1 minute or something before it’ll trigger the automation.
Obviously if you want immediate notification (such as when arriving home) this might not be tenable.
Matt
You can create a few smaller circular zones next to each other and work with that, unfortunately we can’t group zones together to make this easier.
This isn’t a bad idea since I do use an input text boolean for the defining of last areas. That way I can have a more customized greeting when I get home. The Zone updates in this latest update paired with better zones would be perfect.
Here’s the feature request: Polygon tracker Zones looks like it’s been around for a bit but voting wise its got a few. Hoping Stefan is right that people are working on it.
I’ve found a feature request for this too, appears to be a less popular one though
Agreed. Especially in a city like NYC. I have zones for different parts of the city with many needs for a non circle definition. For example, northern Manhattan. In order to include all of northern Manhattan in the circle, it also includes parts of NJ and the Bronx because of the geography. The same goes for New York Harbor. When someone is on the Staten Island Ferry, they are in a circle that includes the harbor, parts of NJ, and Brooklyn. I would love free floating rectangles. A long shot wish would be zones based on postal codes. That would totally solve my large area zone issues.
Yeah, for me its like University, I can’t get that in a circle without getting the museum etc next door to it. Same with the gardens in my city, you can’t get the whole thing in a circle without including a block of roads around it so it can result in “Oh did you have a good time at the gardens today” from anyone who has a look Home Assistant during the day when in reality, you never went there.
The Raspberry Pi 5 works. There was an HA OS release in January for it.
I do. But in past deleted those tokens manual and after that I needed to link the skill again. That’s why I asked it.
It is crazy to only allow six month for username to update after you mark something as deprecated. Six years is more reasonable.
To deprecate odd units is also weird when there are so few usable units available. What to use for uncalibrated sensors or sensors with poor data? To force everyone to put in a lot of time figuring out how to get a formula to convert the data or to calibrate sensors seem far from the idea of making home assistant easy to use.
after upgrade to 2024.2 I get an error reauthenticating Tuya. invalid hex color: rgb (32,33,36)
Read the comments about this above. The solution is there.
Read the thread!
Beat ya to it 
Use the default theme
Thanks for the release !
However with 2024.2 I can’t voice control my garage door anymore.
Created a topic there: 2024.2 - regression with garage doors?
Certainly, this time frame can be customized for our own requirements.
Thanks for clearing this up! That’s just the way I would want it to work. 
proximity is a very strange update, why was it necessary to remove the proximity domain, it was convenient.
And it’s not clear why this is at all, there was one proximity entity with a couple of attributes, now this entity has been replaced with 5 sensors, or even more sensors, I have 13 or more, as a result, there is no optimization in the database. The question is why?
Deprecate ‘beat’ display option in Time & Date - what’s wrong with this sensor? If it’s not needed, people don’t add it, and if people use it, they add it. Do a couple of lines of code really interfere with the HA architecture that much? Those. additional sensors in proximity do not interfere (although they put a load on the database) but does beat (swatch time) interfere?
This template will give you .beat time
{% set time = (utcnow() + timedelta(hours=1)).time() %}
{% set sec = time.hour * 3600 + time.minute * 60 + time.second %}
{{ sec // 86.4 }}
If you put it in a trigger based template sensor on a 20 second time pattern, it should give you a reasonable accurate equivalent of the depreciated sensor.