Aladdin API changing

Configuration
36

Looks like there has been a pull request for the integration now.

dj

2 Likes
37

Has anyone gotten this integration working since this pull request? Mine failed to authenticate when I tried it this morning.

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

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.

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

41

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
42

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?

43

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.

44

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
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.

46

I just created an automation to run at the bottom of the hour to reload it.

dj

47

Looks like the official integration will be in the June release.

image
image930×238 16.9 KB

1 Like
48

Sweet! I’ve been watching that PR hoping it would come in next month.

49

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.

EDIT - Genie got it fixed up. I guess there was some rate limiting going on that they adjusted for. :ok_hand:

50

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.

51

On the container version copying this directory from 2024.6.2
/usr/src/homeassistant/homeassistant/components/aladdin_connect
to
/config/custom_components/aladdin_connect

and adding a bogus version to /config/custom_components/aladdin_connect/manifest.json

{
  "domain": "aladdin_connect",
  "name": "Aladdin Connect",
  "codeowners": ["@swcloudgenie"],
  "config_flow": true,
  "dependencies": ["application_credentials"],
  "documentation": "https://www.home-assistant.io/integrations/aladdin_connect",
  "iot_class": "cloud_polling",
  "requirements": ["genie-partner-sdk==1.0.2"],
  "version": "0.0.1"
}

is working on my 2024.7.0 container and will just keep following genie-partner-sdk if it’s license updates.

1 Like
52

That’s awesome news!

Can you help me understand what you worked out?

By “container version”, do you mean the home bridge based version linked above?

So install that and then copy in the files from 2024.6.2?

53

When the official release came out I thought it was worth a try to just wedge it in as a custom_component since it did work in 2024.07.b0. It only complained about the version missing from manifest.json. I didn’t configure it from scratch, but my old aladdin connect integration showed up after restarting the 2024.7.0 container.

Yep, I pulled down the homeassistant/home-assistant:2024.6.2 container where it was working and made a copy of the diredctory.

Yep, afterwards I put the aladdin_connect backup copy from 2024.6.2 in the custom_components of my 2024.7.0 container. Getting the state and open / close the garage worked for me.

1 Like
54

Awesome, thank you for the details. I’ll dig into this so that I can move forward to 2024.7.x soon.

55

I emailed with one of the Aladdin Devs. He said they are working to change the license for the SDK to an OSI friendly license.

I don’t see the folks working on the free 1st party integration as the problem here. From all the commits and issue comments I read, the HA team seemed to have taken a scorched earth approach to what seems to be a small misunderstanding. Please correct me if I’m wrong.

We are currently working on getting this license changed to an OSI-approved license so that we can bring back the integration. Unfortunately, I do not have a timeline yet, but we are aware of the issue and are working to resolve it.

3 Likes