myQ Workaround | Garage door openner | Shelly 1 | Home Assistant
ฝัง
- เผยแพร่เมื่อ 14 ต.ค. 2024
- Keep an eye out for the UPDATED version of this video with a cleaner and better install. If you are looking to install ratgdo but don’t want to wait 3 weeks or more for it to arrive my updated video will be very helpful!
The directions in this video don't include how I set up the Shelly 1 device for two reasons. One, there are already great videos out there
on how to do that. Two, my directions can be used regardless of what relay you use and regardless of the way you connect it to Home Assistant
(ie. Tasmota and MQTT, or ESPHome, or some other method). This video is for those who know how they want to connect their selected relay
to Home Assistant and simply need to work around a garage door opener that doesn't have an easy way to connect their device directly to the Opener.
That said, I do offer how I set mine up below and the resources I used to help you do the same.
To complete the Shelly 1 setup the same way that I did you will need to follow the directions in the following video from Digiblur:
• Upgrade Shelly Switche... - No affiliation, I just like his videos
I added the Tasmota Integration in Home Assistant using MQTT as set up in the Digiblur video above and navigated to it using its IP address -
When setting up your MQTT settings in Tasmota use your Home Assistant ID and Password (the one you use to log in to Home Assistant normally)
as the ID and Password in the Tasmota setup within the shelly device after flashing the tasmota software to it.
You will find it under Configuration/Configure MQTT - User and Password. You will see what I mean when you follow the video above.
I have the Mosquito MQTT integration installed and set up in Home Assistant
This is a great video to help with that: • Home Assistant MQTT In... - No affiliation, I just like his videos
Configuration Tab inside Mosquito:
Certificate File = fullchain.pem
Pricate Key File = privkey.pem
MQTT Customize section code:
active: false
folder: mosquitto
logins: []
customize: null
certfile: fullchain.pem
keyfile: privkey.pem
require_certificate: false
I left the Network settings at default
Home Assistant yaml Code:
Below is the code input in the /config/configuration.yaml file using the File Editor inside Home Assistant
NOTE: the name inside the command_topic, state_topic, and availability_topic is the same as is set inside the
Tasmota Configuration/Configure MQTT under Topic = %topic%
NOTE: simply copy the code below and replace "yourshellyhere" everywhere
you see it with the name you input in your Tasmota setup
#Garage Cover Shelly
mqtt:
cover:
name: "Garage Door Shelly"
command_topic: "cmnd/yourshellyhere/POWER"
state_topic: "stat/yourshellyhere/status"
availability_topic: "tele/yourshellyhere/LWT"
qos: 1
payload_available: "Online"
payload_not_available: "Offline"
payload_open: "ON"
payload_close: "ON"
payload_stop: "ON"
state_open: "open"
state_closed: "closed"
device_class: garage
binary_sensor:
name: "Garage Door State"
state_topic: "stat/yourshellyhere/status"
payload_on: "open"
payload_off: "closed"
availability_topic: "tele/yourshellyhere/LWT"
payload_available: "Online"
payload_not_available: "Offline"
qos: 1
device_class: opening
Thank you to Digiblur for helping via Discord to correct the yaml code for mqtt inside Home Assistant.
To help support the DIY'er and help this channel reach more people (Or simply buy me a coffee because you liked something in the video) - www.buymeacoff...
The music for the intro is by penguinmusic - stylish-rock-beat-trailer-116346 found on Pixabay
Love the ingenuity! Don't let the "You could of" and "You should of" comments discredit your work! There will always be a better solution out there, but the one that works with the budget and tools you have is often the best one. Especially if you came up with it on your own!
Well said! I appreciate your candor. I love all the suggestions so far. I will be working to make some changes in the future and I’ll upload an updated video. You are correct, I did what I could with the current budget and supplies on hand and made it work as-is for now. Thank you for the sentiment!
There are a few things that can be added to the yaml to add additional support for more states. Your current design only has open and closed and these tie directly into the reed switch states. On my own design I implemented opening and closing states. These are derived by creating a moving binary sensor that goes true when button pressed and when timer expires goes to not moving. Then the states transition a few ways- when moving starts and was open becomes closing. When moving starts and was closed becomes opening. When timer expires the state becomes whatever the reed switch says. Now I can get a alert when fail to close because that’s simply a state change from closing to opened. Likewise I get alert for fail to open.
That’s an excellent way to set that up. I will take a deeper look at that
@@thedaddyshow01 when done correctly the icons automatically update for all 5 states. You can go from seeing the icon for a closed door to the up arrow icon indicating movement followed by an icon for an open door. I really like being able to alert on fail to close because I can just drive away without looking and if it fails to close I get alerts. The extra states allow for more intelligence in the automations.
A new myQ workaround video is forthcoming! Please keep an eye out for that this week
This is kind of the perfect situation for 3d printing. You could mount the Shelly and the original switch board into a shared case and it would look nice. I bet you could power the Shelly too, but it would require essentially an itsy bitsy ups...
Either way, awesome project!
Very true! If I can start making money on my videos, I will do that for sure!!
It looks like you are using mqtt or tasmota on the shelly1 device. I tried mqtt a few years ago and was disappointed with the stability. It also takes a lot of steps to setup.
Now, all my Shelly devices are auto detected by “Shelly for hass” integration. I find this to be stable and no issues at all. And it means I don’t have to flash anything as I’m using the vendor firmware. It’s not clear to me what benefit there can be for other firmware since the original is working perfectly for me. And I’ve got a lot of devices so quick setup is important.
I am using Tasmota on this one. It is my first time using it but I’ve had zero issues.
You are better off using a ratgdo, it hooks directly to the button terminal on the operator and speaks directly to the garage door controller. This means it know if the door is moving, and what position the door is in, so you can give it commands like open door to 20%. It also can control other functions of the door, such as the light, give you cycle counts and diagnostic information, and a ton more.
I will look into that!
I have looked into the ratgdo. I appreciate you pointing that out. I will have a video coming shortly on my findings and potentially an install video
How does it know that the door is closed? Or Open?
It knows based on the reed switch I installed on the door. It knows the state of the switch and therefore the state of the door. That gets passed through to Home Assistant
The DIY ratgdo video is up! - th-cam.com/video/5yV5V7prG6c/w-d-xo.html
Why don't you just solder the Shelly's to the remote? No need to run wires and you can put the Shelly anywhere.
Which remote are you speaking of? I still have to have power to the shelly so I’m curious because running no wires would be awesome!
@@thedaddyshow01 open up the remote that came with your garage door opener. Solder the two leads from the Shelly to the button of the remote. To power the Shelly cut a computer power cord and wire it in. Find any open outlet in the garage and plug in.
This would ultimately be the same as what I did only it would use a remote instead of the button. But I do like what you are saying. I will have an updated video coming shortly with some new information and a possible better way to make it work!