How To: Driveway Swing Gate Automation (Shelly + BFT) - Working Perfectly with states!

On the other hand - only “moving” status is missing. It still shows the opened/closed state and it allows to open/close the gates.
And what is more important to me - it works locally.

Hello Curtis

The information supplied is just and sound. The details provided are clear and informative. I believe my gate uses the exact BFT Thalia control board, but I differ from you because I am using the Shelly Plus 1 and connecting the cable to the same…

  1. Finally, wire the ‘SW’ input of the Shelly to terminal #26 of the Thalia (AUX output N.O) and terminal #27 to the L(-). You can also use terminals #20 and #21.

It does not appear to power the Shelly 1 Plus, thus leaving me at a loss.
I’m wondering if there is a significant difference between the two Shelly devices, the Shelly 1 and the Shelly Plus 1.
Is it still possible to connect the Shelly Plus 1 to this Thalia board and receive enough power to carry out the operation?

Thank you @sos_nz Thank you @Khar for the project…
i use shelly uno and as khar stated i did it and everything works as it should…door opening-closing information while the door is moving…i own a botticelli smart bt a 850
sorry for my bad english…
Screenshot_1

I’m using your writeup, which is great, thank you for clarifying the details so well!
There are some questions I hope you can help me with though.

One of the problems I have, is that we also use normal RF remote controls in the car, and as soon as you use a different trigger of any sorts to trigger the gate, the status loses track and thinks its closed while its not.

Basically, using RF to control the gate doesn’t trigger any change in Input 2.

Any good idea how to get around this? I do have another Shelly with a Reed switch and was thinking to somehow have the extra Shelly control 70-71 to stop the gate, but also try to get the closed state.

Here’s an update to my Shelly Plus 1 BFT Thalia configuration.
It turns out there was no power on my ports 50 and 51 because of a blown fuse on the board. I was told I should bypass those port and run the power direct from the battery input on Power Terminal Board 24v.
This worked I was able to power the Shelly Plus 1 and open and close the gate via the Shelly app and Home assistant via the Shelly Integration built into Home Assistant .
My only issue is I’m not able to tell if the gate is open or closed on the current configuration.
Supplied: Configuration and Entities

Any assistance would be greatly appreciated.


Hi Guys, i have the BFT Ultra A600 and i am looking into this automation. I’m after some advise as i already have a 4 core cable that’s running from my garage where all my network devices are upto the gate motor. Can i repurpose it and use that to integrate the motor into my home assistant or perhaps use the cable to extend the shelly into the garage?

Hi @rupertas i have the BFT A600 sliding gate motor and the board looks very similar to yours except that i dont have the magnetic locks. can i still follow your wiring scheme to make it work with Shelly Uni?




@Khar @rupertas i have setup the shelly Uni as per your instructions and i got it working but the remote is not functioning as expected. When i open from the remote, the gate closes back immediately. Any advice?

did you configure uni to auto switch off?
could it be that uni permanently is on “Close”?

Other thing is to look at BFT configuration, there is some option to auto close after a period of time

Do not have further ideas :frowning:

Thank so i got it mostly working. Only thing that is different is my channel 1 and 2 are behaving differently. Channel 1 is closed and 2 is open. I re-verified all the wiring already.

Hi @David_M i also have the bft ultra with a merak board and i have the same problem with the gate always in open state.

Did you figure this out?

ok so i did a factory reset of the shellyuni and also had a look at the configs again.

The config is correct, what I’m noticing is, AUX3=8 is always showing as off whether its open or closed. Although it briefly transitions to On for about 1s and changes back to Off when i press the button to open the gate from a closed position.

When i change AUX3=1 then i see it On when Open, Off when Closed and intermittent on/off when operating. How do i handle this in my HA template. when closing the gate, its fluctuating between open/close due to AUX3=1 setting.

did you manage to solve this? what did you use?

Hey @jitesh_88 - No I didn’t getting working, but I’m going to have another crack at it again soon. After connecting Uni sensor to motor board I had some unusual behaviour with the gate going back and forth, even when using the remote, similar to you.

I’ve got it mostly working, the only issue is i cannot use aux3=8, for time being ive set aux3=1 for GATE OPEN which is pulsating on/off when the gate is closing and i hear this clicking sound from the motor as it’s pulsating between on/off. I also tried swapping AUX 0&3 but same results.

I have updated my sensor accordingly

- platform: template
  covers: 
    bft_gates:
      device_class: gate
      unique_id: bft_gates
      friendly_name: "BFT Gates"
      value_template: >-
        {% if is_state('binary_sensor.bft_shelly_gates_moving', 'off') and is_state('binary_sensor.bft_shelly_gates_closed', 'off') %}
          closed
        {% elif is_state('binary_sensor.bft_shelly_gates_moving', 'off') and is_state('binary_sensor.bft_shelly_gates_closed', 'on') %}
          open
        {% endif %}
      optimistic: true
      open_cover:
        service: switch.turn_on
        data:
          entity_id: switch.bft_shelly_channel_2_open
      close_cover:
        service: switch.turn_on
        data:
          entity_id: switch.bft_shelly_channel_1_close

How would you go about drawing power from the board? For some reason ports 50-51 have no power when measured, and I am not sure what I have connected to these ports, but everything is working, including the photo sensors.

There was a mention here about the fuses being broken when these ports have no power, but mine are all fine.

Try to measure it as AC. Mine is AC voltage.

@jitesh_88 - I opened up this cold case and have been able to getting working the same as your scenario, which is good.

The open/close state does pulsate when closing - I tried changing AUX0 from 6 (‘flashing’) to 2 (‘courtesy light’), but it made no difference. There is also a pulsate on close logic setting I disabled, but that didn’t work either.

I now want to find a simple device I can have inside that will light up orange/green depending on the gate status. Having the closing status pulsate will actually help with this kind of indicator.

So my settings are AUX0=6 & AUX3=1 and cover yaml below:

 - platform: template
    covers:
      driveway_gates:
        device_class: gate
        friendly_name: "Driveway Gates"
        value_template: >-
          {% if is_state('binary_sensor.driveway_gates_open', 'on') %}
            open
          {% else %}
            closed
          {% endif %}
        optimistic: true
        open_cover:
          - service: button.press
            target:
              entity_id: button.open_driveway_gates
        close_cover:
          - service: button.press
            target:
              entity_id: button.close_driveway_gates

image

1 Like

I discovered this write up which has helped me tremendously. The thing I am struggling with is the cover. The statement in the interactions is to simply put the YAML below into configuration.yaml.

cover.bft_gate:
  device_class: gate

This didn’t work. When running “Check Configuration” the circle just kept on circling., so I tried

cover:
  cover.gate:
    device_class: gate

Using Check Configuration gives this error:

Configuration warnings
Invalid config for 'cover' at configuration.yaml, line 131: required key 'platform' not provided

Need help urgently.

When you use this template, how are you dealing with the closing gate when the fence is pulsating on/off. The cover state will keep pulsating too