There seems to be less and less solutions for your situation, but I’m sure we will find one that fits you.
Concerning your idea of using Proximity integration, I had thought of this too but it automatically reports “0” when in your home zone. And since GPS takes time to update and is not reliable, I don’t think this will be good enough, even if I calculate manually your distance from home.
Could you elaborate on the issue you would have with a wifi tracker ? I think you’re talking about needing wifi when arriving, but I was proposing a solution only while leaving home. So as you said, since WiFi is really weak outside, it could detect if you’re parked in your garage or in the street when you start your car.
But if these solutions don’t suit your situation, I would recommend buying an ESP32 to put in your garage to generate an iBeacon that would detect if you are in your garage or outside. This is the most precise solution possible. Plus, it would allow you to automatically close your gate when leaving (but I suggest waiting for my next update for this)
I noticed that too some weeks ago
Unfortunately I can’t do anything to fix this problem as it comes from Home Assistant.
You can see the progress on this issue here
By the way, I forgot to tell you that you could place my yaml file into HA_folder/config/blueprints/automation/etiennec78
However, with this method you won’t be able to update the blueprint through HA. But when the button will be fixed, you will only have to import it again to fix this.
I think it was working until 2024.8 but with 2024.9 I have a huge delay when arriving home.
The gate is never home when I arrive but instead have to wait up to 30 sec. The Problem is, that if I just open with the remote, enter, close the gate it already happened that it was opening after it closed.
I double checked all the settings in the automation, that seems to be all fine. I also checked if the data is transmitted to HA correctly, all fine. Checked the app settings with GPS and Battery stuff, all fine.
Hello, thanks for the feedback.
However I haven’t noticed this bug when updating to 2024.9, so something else might be broken…
Could you please add a map card with position history to your dashboard ? (example)
Maybe your GPS tracker is not reporting your position quickly enough ?
If the issue persists, feel free to open an issue on my GitHub and post your logs as explained in the form. I’ll take a look at them.
I really like your blueprint. Thanks a lot for this great work!
However, I have a question regarding the supported scenarios.
My wife and I have two cars both residing in one big double garage (with only one gate).
We often change who is driving with which car.
So that would result in 4 driving sensors, but only 2 persons and 2 itinerary sensors etc.
Will this work or only for both of us using one car?
Hello Stefan, and thanks for your interest in my project !
I’m currently in a similar situation as yours : we have 2 cars and 3 drivers, but as you saw, my blueprint needs exactly the same number of sensors for each input.
So the solution I use myself is to simply make a custom sensor which combines all car sensors per person.
This way, you will only have 2 car sensors which will turn on no matter what car the person is driving.
Here is a quick tutorial on how to add this sensor : Link
Hi @etiennec78
First of all thank you for this amazing automation.
My user case is the following: I have two gates, a front gate and a few meters down the garage gate. I use two automations, one for each gate with their own cover entities, but all the other entities are shared. I’ve noticed that both automations update the input_datetime. The problem is that they don’t set the same time for the opening of the gate and when I arrive sometimes the second gate opens before the first one or the first one don’t even opens.
What configuration do you recommend for this case?
Hello @manuelmrmorgado
The fact that both ETA sensors are not containing the exact same time is quite weird… I’ll have to look into that. Could you maybe open an issue on github so I can take a look at your blueprint logs ?
I’ll have to admit that I didn’t think about your usecase when developping this blueprint, but having two instances for the same location is quite a waste of compute power (and waze credits), so I’ve just pushed a beta update to let you use multiple gates in my blueprint !
You can update to the latest beta release by going into Settings > Automations & Scenes > Blueprints > Import blueprint, and pasting this link : https://github.com/etiennec78/Home-Automation/blob/dev/Automatic%20Gate%2Fautomatic-gate.yaml
By the way, the error you will receive is normal, you will just have to go into your automation and save it again
Sorry but could you please update again ?
I made a copy paste mistake that I just fixed this morning.
Maybe I should try to avoid making commits when it’s this late
I guess I’ve managed to make 1.0.7 work, I’ve combined both gates in a group.
I’ve tested but this dev version but it isn’t working, when leaving I get a notification saying “command_ble_transmitter” and notting happens. Here’s my config:
I see… I’ve recently updated the code managing iBeacon activation on Android but didn’t have any iOS device at home to test this on. Now the iBeacon activation notification shouldn’t trigger on your iPhone with the latest beta.
However, without logs I couldn’t see why your gate did not open at all, as it currently works on mine
You’ve got a good idea to make a group of gates !
I completely forgot to suggest it to you, but now that the code is here I think I’ll keep it as it makes it easier to configure for future double gate users
I’ve made a commit which should fix the opening of gates not happening on dev branch.
Also, I saw on github that you suggested me to add support for Tesla travel time.
I was also planning on adding Maps and Here support but didn’t hear about Tesla. Could you please tell me which Tesla integration gives you this sensor ?
I’ll give it a try.
Regarding Tesla, the HACS Tesla Custom Integration or in my case Tessie, both give distance to arrival and ETA sensors based on the destination you’ve entered in the car’s nav system. It comes as a timestamp like the one we create for the automation, so I guess that allowing the automation to use that instead of Waze would be a good idea, just add also the condition of the destination sensor to be ‘Home’. Just an idea
The current design of this blueprint would not be compatible with having a datetime entity without a travel time provider, but I’ve been working for some time on a complete redesign which could make this feature possible. (but since school started I didn’t have the time to implement it)
By the way, do you know if this Tesla sensor updates frequently ? If its interval is 15 minutes I wouldn’t recommend it.
Waze seems to be a better solution overall as you don’t need to start an itinerary in your car, and it can update as fast as needed.
