Not on that information.
Hi nickrout, thanks for the reply. I basically have no idea what I’m doing nor confidence that I followed instructions correctly. I guess my first question is how I go to the main config directory in the CLI. I followed Vynce’s directions but he’s using a proxmox VM so I’m not sure if it is the same on HA installed on a thin client?
How did you install HA?
Actually it is pretty simple. The directory you want us your config directory. The same one that has your configuration.yaml . Configuration.yaml - Home Assistant
I booted the thin client from a flash drive with ubuntu and used the disk utility to install HA on the internal drive of the client. I hooked up a monitor and keyboard to the client and entered in the commands into the command line interface that Vynce spelled out above. I have never had Aladdin working or any connection or software related to Aladdin installed on my hub. I found this thread and hoped I could connect my HA hub to my garage doors but that’s when I realized I was in over my head. I need someone to explain it to me as if I were a five year old lol!
Ok. I figured it out and got it working! Thank you for your help. From the link you sent I was able to install the Terminal and access the CLI from there. Then I was able to read back through the thread and work things out from there. Thanks again!
Anybody having problems with automations using genie garage door as trigger? I got the integration working using the custom component and can control and see the state of my doors from HA. I then set up an automation that should turn my garage ceiling lights on when the garage door is opened or closed. It works great if I open or close the garage door from the HA app, but if I open or close it from my car remote or the button on the wall the automation doesn’t run. Not sure if it’s something I did wrong in the automation or if other people have had issues with this? This newb would appreciate any advice!
In my experience, ever since the update to the new API the states haven’t been as good at staying current. Occasionally they get out of sync.
For me, maybe unrelated to getting out of sync is that the WiFi on these kinda sucks. I moved my AP to literally inside the garage and one drops occasionally. So bad I had to program a smart plug to to switch it off when it drops for a couple minutes.
Thanks for the reply. I haven’t noticed any connectivity issues as my door is very responsive to commands from the app. Sounds like maybe the states aren’t working great. That’s good to know. Bummed that this may be as good as it gets because I was really looking forward to having more light than just the bulbs attached to the opener when the garage door is activated.
1 Like
Not to put too fine a point on this, but who do we have to lean on to get this working again? Is it Nabucassa or Aladdin? It seems to me that this should not be THAT difficult to resolve.
It’s Aladdin. They dropped the ball on getting the licensing changed to be compatible with Home Assistant’s requirements.
Last I check they went non-responsive to a couple inquiries on the GitHub PR.
When the whole myQ fiasco happened, I asked Aladdin support about their policy that allowed access to their cloud. They replied stating, they “had no plan to prevent 3rd-party applications from using their API”. Then 6 months later they effectively shut-down their API. Disappointing as that was, I’d still buy Genie over anything myQ. At least their openers can be triggered with a relay, unlike myQ which has a proprietary circuit board preventing that.
That’s interesting! I’m not sure why, but I thought there was something special about the signal between the wall switch and motor.
Can you tell me anything more about what the relay set up is?
I might keep the hacked integration around for status / position, but use the relay to trigger the door. That avoids the situation where the opener gets out of sync and refuses to move without a local control.
Does it vary from one model to another? So the only way to be sure is to check your own garage door opener: Supposedly there is one cable with 2 wires between your wall switch and 2 terminals on your opener. So you take a bare wire or paper clip, and connect those 2 terminals… does your garage door open and close each time you do that?
Alternatively you can open the wall switch and see if you can achieve the same via 2 of the leads in the wall switch.
1 Like
I suppose they have no plan to block 3rd party integration, and evidently, it’s also true they have no plan to maintain and keep things going.
I agree. If that’s the only 2 choices we have got.
They promised and didn’t give. They licensed their API under a non open license. Fuckers.
Just found this little tid bit after your suggestion and some searching. I’m encouraged and will give shorting the terminals a try. What relay are you using?
At the time I couldn’t wrap my head around how they were getting all of the additional functions on two wires, and I think I assume they were using some type of secured protocol
Genie Series II Wall Console
Two Wire, 5V, White is Neutral
R1, 121 Ohms
R2, 82 Ohms
LEDLocked = R2
Unlocked = R2 + R1 + LED
Light (Push Button Toggle) = R1 + R2 (push button shorts the LED)
Open/Close (Push Button Toggle) = (push button closes the circuit)
Definitely do your paper clip tests. And if shorting the terminals works, there are many options for you.
- You can still do RATGDO, and following the dry contact wiring instead.
- You can find zigbee or z-wave or wifi dry contact relays of your choice, and use that to simulate clicking the wall switch.
2.1) Ideally you can find something that offers the momentary switch feature, where the relay would engage for, say, half a second, and automatically disengage, just like what human finger would do to the wall switch. If not, that’s less ideal but fine also, because you can setup the relay to behave that way via automation.
2.2) So tuya has maybe two dozens of zigbee options out there - here are some examples I googled. I personally did z-wave and shared my project here in this forum. And then you have wifi options such as Meross, Tailwind, NEXX, OpenGarage, Shelly 1, Shelly Uni, … I like Athom also. With many of those packaged options, you might be able to get door status locally without relying on any Alladin cloud. - Or you can build your own ESPHome based solution, there are tons of examples here in this forum or on Youtube. Taking full control of your garage door locally. (And have fun!
) - Not recommended but still a feasible option: check whether Aladdin talks to Homebridge and how well that works. If yes, a convoluted way to approach this would be to get Alladin to talk to Homebridge instance in your home server, and then get your Homebridge to talk to HA via this integration. A lot of hoops to jump through, and you will have to know what you are doing, so not for everyone; plus doing so still would not help you if/when Alladin changes or breaks something again / would not help you break free from Aladdin. Hence not recommended.
I use this connected to the “doorbell” button wires. It’s Zigbee and setups up easily. It even resets the relay automatically. So don’t have to command it back open after triggering it. You’ll hear two clicks (closed/open).
Yitouniu Zigbee 1CH DC 7-32V USB 5V Relay Smart Switch Module,Wireless APP Remote Control with Inching/Self-Lock Switch modle,Works with Tuya Zigbee Gateway,Alexa,Google Home (Required ZigBee Hub) - Amazon.com
I use a Shelly uni to short the terminal briefly. It has a setting for that.