jsmith
(Justin Smith)
May 2, 2024, 11:42pm
31
This worked for me as well… thanks @andyrak
kevin59
(KW)
May 3, 2024, 1:22am
32
Thanks so much! It’s silly but the ability to open/close my garage door was one of my favorite HA tasks. I have a zone based automation to open my door when I enter the zone if my door is closed. Man I missed having that.
Thanks so much for pointing to a temporary solution for this! Honestly I was afraid that Aladdin was pulling a MyQ on us but trying to act like they were updating their API until we all forgot about it.
Andy, thanks so much for your efforts on this. I installed it today and it works great. Here are some details of my Aladdin Connect: Model: ALDCM, IC: 2133A-ALDCM, MFG Date: 20211126D10206
zachrb11
(Zachrb11)
May 5, 2024, 4:42pm
35
Thank you! This worked great, really appreciate it!
dljordaneku
(Darrell Lee Jordan)
May 7, 2024, 8:06pm
36
Looks like there has been a pull request for the integration now.
home-assistant:dev
← Genie-Garage:aladdin-connect-api-ugrade
opened 04:26PM - 07 May 24 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
This should entirely replace the existing `aladdin_connect` component, which is as of now broken.
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
This is the official Genie garage integration, which will replace the existing broken integration.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [X] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
I have not made any attempt to deprecate or otherwise remove the existing `aladdin_connect` component. If you need assistance with this, just let me know the proper steps to take care of this. As of now, this PR simply adds the new working integration alongside the existing one.
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [X] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
**NOTE**: I am not able to run the tests locally, they all fail because of bad imports. I am not a Python developer and am having trouble figuring out how to fix this issue.
- [X] There is no commented out code in this PR.
- [X] I have followed the [development checklist][dev-checklist]
- [X] I have followed the [perfect PR recommendations][perfect-pr]
- [X] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
**NOTE**: All testing was done manually with the external library
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [X] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [X] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [X] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
dj
2 Likes
gozasc
May 9, 2024, 11:11am
37
Has anyone gotten this integration working since this pull request? Mine failed to authenticate when I tried it this morning.
dljordaneku
(Darrell Lee Jordan)
May 10, 2024, 2:31am
38
Are you using the current integration? I don’t think it will work if you upgraded the app on your phone. The current integration uses the old API and the pull request is the official one that uses the new API.
Dj
gozasc
May 10, 2024, 8:13pm
39
Yep, got it figured out-- thanks!
One note: if I open the door via HA, then close it using my garage door opener or the wall control, it still shows open in HA. Hoping a future update will be able to poll the Aladdin service for open/closed status.
dljordaneku
(Darrell Lee Jordan)
May 11, 2024, 1:50am
40
I think once the official integration is released it should. Is your door an actual wifi compatible system or are you using the retrofit kit they sell?
dj
There was a bug preventing automations from being able to open/close/toggle the doors in the previous version; I’ve fixed it in the latest release, v0.2.2.
1 Like
Wow, I’ve missed this until now. Will this work if I have signed in from the mobile app and “updated to the new API?” Or whatever they were saying would happen if you log in?
I can confirm, it works great. You guys are awesome!
*Haha, and judging by the PR from Aladdin it looks like I found this just before they fixed the main integration.
As a hacky stop gap you can use
service: homeassistant.reload_config_entry
data: {}
target:
entity_id: cover.main_garage_door
to reload the integration. This causes a status update.
I opened an issue on Github.
Here’s an automation that will get this updating. It requires something as a motion trigger. You even get “is closing” while it’s in process. Might have to play with the repeat qty, mine took about 25 seconds to get from the close request to “closed”.
alias: Temp - Update Garage Status on Motion
description: ""
trigger:
- platform: state
entity_id:
- binary_sensor.frigate_lorex_11_shop_2_motion
to: "on"
condition: []
action:
- repeat:
count: 7
sequence:
- service: homeassistant.reload_config_entry
data: {}
target:
entity_id:
- cover.main_garage_door
- delay:
hours: 0
minutes: 0
seconds: 5
milliseconds: 0
mode: single
1 Like
dljordaneku
(Darrell Lee Jordan)
May 24, 2024, 11:59pm
45
I’m seeing the same thing. I loaded the integration and logged in and saw the door was open which it was. My son came in and closed it but the status still showed it was open. I reloaded and then it changed to closed.
dljordaneku
(Darrell Lee Jordan)
May 28, 2024, 1:40am
46
I just created an automation to run at the bottom of the hour to reload it.
dj
dljordaneku
(Darrell Lee Jordan)
May 29, 2024, 8:27pm
47
Looks like the official integration will be in the June release.
1 Like
Sweet! I’ve been watching that PR hoping it would come in next month.
Just a heads up. Myself and someone else are having issues with the core integration after initial success. Might be worth hanging on to the HACS version for a bit.
opened 02:45PM - 06 Jun 24 UTC
closed 08:30PM - 06 Jun 24 UTC
integration: aladdin_connect
### The problem
After upgrading to 2024.6.0 yesterday The integration worked … initially. I was able to control both doors.
This morning I saw errors about missing entities and investigated after one of my automations did not function.
I reloaded the Aladdin Connect integration, and I got the error "failed to set up, see logs".
Before I restarted there was a very similar error in the log in addition to the one below, the notable difference for me was that there was a different key where devices is listed here. Unfortunately I did not copy it.
As far as I can tell everything was working great last night after the update and initial configuration.
I want to add "thank you to everyone who brought this integration back online!".
### What version of Home Assistant Core has the issue?
2024.6.1
### What was the last working version of Home Assistant Core?
_No response_
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Aladdin Connect
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/aladdin_connect/
### Diagnostics information
_No response_
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
```txt
Logger: homeassistant.config_entries
Source: config_entries.py:594
First occurred: 07:23:54 (4 occurrences)
Last logged: 07:38:52
Error setting up entry [email protected] for aladdin_connect
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/aladdin_connect/__init__.py", line 36, in async_setup_entry
await coordinator.async_setup()
File "/usr/src/homeassistant/homeassistant/components/aladdin_connect/coordinator.py", line 33, in async_setup
self.doors = await self.acc.get_doors()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/genie_partner_sdk/client.py", line 21, in get_doors
for device in data["devices"]:
~~~~^^^^^^^^^^^
KeyError: 'devices'
```
### Additional information
_No response_
EDIT - Genie got it fixed up. I guess there was some rate limiting going on that they adjusted for.
Sad news but it looks like some of the code Genie uses isn’t open source liscensed correctly, so the new integration is out for 2024.7.0
It sounds like there’s potential for it to get rectified if Genie sorts it out. I hope so. They did put a lot of work into building it, so I’m hopeful.
Maybe we have to keep using this alternative for now… I’m gonna hang tight on updating core for a couple days before deciding.
opened 12:13AM - 27 Jun 24 UTC
closed 07:13PM - 02 Jul 24 UTC
integration: aladdin_connect
### The problem
With the latest beat 7.0b2, the new Aladdin Connect Integration… is failing to load.
### What version of Home Assistant Core has the issue?
2024.7.0b2
### What was the last working version of Home Assistant Core?
2023.6.x
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Aladdin Connect
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/aladdin_connect/
### Diagnostics information
N/A
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
```txt
Logger: homeassistant.setup
Source: setup.py:271
First occurred: 6:44:52 PM (1 occurrences)
Last logged: 6:44:52 PM
Setup failed for 'aladdin_connect': Dependency is disabled - This integration is disabled because it uses non-open source code to operate.
```
### Additional information
_No response_