Automation to Open Gate, so Luba 2 can mow the front driveway area

[AlohaFlyer]

I have a long driveway and front area outside of my gate, that I want Luba 2 to mow. What would be the best way to trigger an automation that can open my gate?

One thought was to make a mowing area that straddles the gate that stretches 3-4 meters on either side of the gate, then trigger the automation to open when it reaches this area. I just need to find a way to trigger that. I don't think there is a sensor that can give me that info reliably.

Thoughts??

[Kontendesigner]

I have a similar configuration.

My Luba is in the garage and should park/charge there again after mowing. To do this, I trigger the activity mode. As soon as it changes to "MODE_RETURNING", the garage door is opened.

You can trigger as well on position "channel_on"

triggers:
  - trigger: state
    entity_id:
      - sensor.luba_dalos_aktivitatsmodus
    to: MODE_RETURNING
    from: null

[mikey0000]

Sorry I can't believe I didn't reply to this, you also have the sensor which tells you if the mower is on a channel or area, this is helpful for triggers adding to that you can also use a geofence (a bit more work)

[416chase]

Very impressive work @mikey0000. Moving from a Luba1 to a 2 and needed a different solution to my auto gate door. Found out about HA from others reviewing your int... Where do we find the sensor information for channel's? Only thing in the sensor section looks to be for the camera.

[mikey0000]

Device position type will give you what you want

[416chase]

Thanks... Checking the logs for Device Position, I see the following changes to descriptions... AREA_BORDER_ON, CHANNEL_AREA_OVERLAP, AREA_INSIDE, CHARGE_ON. Are there any differentiators for the different channels? Is there a way to see what the mowers next destination is? As in, the task is to mow area 3 and the mower is in Area 1. to get there, the mower starts in area 1 then heads to destination channel 1 to 2. from there the destination is channel 1/2 to Area 2. from there destination is 2 to channel 2 to 3. then finally the final destination is from channel 2/3 to area 3.

[mikey0000]

It doesn't differentiate, it's just channel_on I need to sort on the sensors for the task set, which I'm about to work on.

[Kontendesigner]

I use geofancing to close the garage door when the Luba has switched from the connecting channel to the work area. Then I can be sure that the goal doesn't close and the Luba is still underneath.

trigger: state
entity_id:
  - sensor.luba_dalos_typ_der_geratepositionierung
from: CHANNEL_ON
to: CHANNEL_AREA_OVERLAP