My guess is the Aladdin dev team is all about making it happen, but with a big corp there are processes that aren’t as simple as “doing the right thing”, and it’s got to move through the process. Moving something through legal takes work. The HA team definitely made it clear that the license needed to be fixed early on, but maybe it didn’t get the necessary attention early on. Although HA had let it slide they had to hold the feet to the fire otherwise it didn’t seem to be moving forward in an appropriate timeline.
Understandably, HA wouldn’t want to be facilitating breaches of licensing, so it has to come out until it is rectified. …as much of a bummer as that is, it needs to be licensed correctly which is on Aladdin.
Edit - my guess is that maybe the team and legal / whomever is involved isn’t historically familiar with open source, and thought the way it was set up was good enough… HA is legit enough to be vetting those details and making sure it’s done right.
Do we have any visibility into Aladdin process to know when it’s supposed to be fixed? It SUCKS so bad to loose the integration like that!
Can we add pressure on them by hitting their customer support?
Thank you for your feedback. We apologize for any inconvenience. Our team has been focused on working through an upgrade of your phone App that will improve performance. We apologize for the inconvenience we did not write the original Home Assistant API and it was not supported by Genie. We will advise when the new API will be available once we are closer.
Our number is 1-866-599-4995, and our hours of operation are Monday-Friday 8 AM- 7 PM CST, Saturday 9 AM- 5 PM CST. Please visit our website at www.geniecompany.com. We thank you for your time and appreciate your patience.
Thank you,
Here’s how I restored Aladdin Connect support to 2024.7.3. I’m running the full Home Assistant OS in a Proxmox VM, so the steps are probably different in other environments.
From the Home Assistant CLI, type login to drop to the shell.
Go to the main config directory. This is the same directory that contains configuration.yaml.
cd /mnt/data/supervisor/homeassistant
Create a directory for Aladdin Connect. Check that the permissions on these directories match the permissions of other sibling directories.
mkdir -p custom_components/aladdin_connect
cd custom_components/aladdin_connect
Download the Aladdin Connect component from the 2024.6.4 release:
Not familiar with custom components… Does that mean the custom one with version 0.0.1 would automatically supersede the newer one that comes with 2024.7.x, even though they share the same name aladin_connect?
Do I need to re-configure the aladin_connect integration? Or whatever I’ve setup already would automatically start using the custom component codes from 2024.6.4?
Just trying to understand what would get myself into.
Logger: homeassistant.setup
Source: setup.py:322
First occurred: 8:32:30 AM (1 occurrences)
Last logged: 8:32:30 AM
Setup failed for custom integration 'aladdin_connect': Unable to import component: No module named 'genie_partner_sdk'
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/homeassistant/setup.py", line 322, in _async_setup_component
component = await integration.async_get_component()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/homeassistant/loader.py", line 1027, in async_get_component
self._component_future.result()
File "/usr/local/lib/python3.12/site-packages/homeassistant/loader.py", line 1007, in async_get_component
comp = await self.hass.async_add_import_executor_job(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/homeassistant/loader.py", line 1067, in _get_component
ComponentProtocol, importlib.import_module(self.pkg_path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/homeassistant/util/loop.py", line 200, in protected_loop_func
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/importlib/__init__.py", line 90, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 995, in exec_module
File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
File "/config/custom_components/aladdin_connect/__init__.py", line 5, in <module>
from genie_partner_sdk.client import AladdinConnectClient
ModuleNotFoundError: No module named 'genie_partner_sdk'
Also, I’m getting the following error in my logs now that integration has been removed…
Logger: homeassistant.config_entries
Source: config_entries.py:911
First occurred: 9:31:08 AM (1 occurrences)
Last logged: 9:31:08 AM
Migration handler not found for entry [email protected] for aladdin_connect
I’ve been on 2024.6.4, unwilling to update until I had the chance to sort this out, and your instructions made this so much easier! So, I did the core update to 2024.7.3, and then immediately followed your instructions. (Aladdin Connect was configured and working previously).
I used the Advanced SSH & Web Terminal add-on to access CLI. The only difference from that interface was that the homeassistant directory is at /homeassistant, but your hint about same directory w/configuration.yaml got me on track.
Otherwise I was able to follow the directions to the T, and all worked out well! I’ve got everything else updated, restarted, and no errors related to Aladdin Connect. Thanks @_Vynce!
Thank you @_Vynce for these directions. I stopped upgrading at 2024.6 as I was afraid of loosing this integration since it was removed in 2024.7. Today I was able to follow your directions and then upgrade to 2024.8 and my garage door control still works! Thanks for taking the time to write up those step by step directions!
Just last year Chamberlain (myQ) forced their integration to stop working. At the time, Aladdin was happy to tell users that their API would remain open to HA and other platforms. Then they did a complete U-turn and work against open platforms or just make it all difficult to use. I suspect some corporate higher ups (who likely don’t care to understand this very well) made some blanket decision to appear tough on hackers or some other BS security nonsense to justify keeping their walled garden (of exactly one device) so they could eventually monetize it as a service someday. Disappointing.
Well, the only two admin logins I know of (the default homeassistant for SSH, and my user for the HA web interface) do not work for login.
I’ve also seen that you’re required to change the port to 22222 and I’ve seen that you’re forced to use certificates for authentication rather than a login.
I think I tried making that work for about 5 hours and I can’t get passed. Disconnected: No supported authentication methods available (server sent: publickey; keyboard-interactive) when I enter the user homeassistent (or just by pressing enter with nothing in the field).
Keep in mind though this part is just attempting to login to SSH.
