When enabling integrations, only pure-python module or cross-compiled modules delivered in package as wheels will work.

Many integrations require additional native Python 3 modules that have to be available as compiled wheels for the respective DSM architecture.

Here is an example of an error message visible in logs (accessible from webui or on the system at /var/packages/homeassistant/var/homeassistant.log) when module has to be built for architecture and requires a package upgrade to do so:

2018-12-09 01:42:26 ERROR (Thread-10) [homeassistant.util.package]
Unable to install package homekit==0.10: Failed building wheel for gmpy2
Failed building wheel for py25519

Please submit a request for additonal integration you are interested in. We will do our best to get it available in next version update.

This section will report "integrations" for which specific components are known to fail or work and their current status on DSM.

Some Components are fully configurable in the Home Assistant Frontend, but others are based on manual settings in the configuration file.

To access the configuration file, you need to enable SSH service to gain access to your system. You need a file editor like the default installed vi or vim. The installation of nano is recommended for beginners (contained in SynoCli File Tools).

Then use the following command to edit the configuration according to application documentation

sudo nano /var/packages/homeassistant/var/config/configuration.yaml

When restarting the service after configuration changes, please check the service log in the webui (or in /var/packages/homeassistant/var/homeassistant.log).

To manually add python modules for integrations you need ssh access to your system.

If such modules (and their dependencies) are pure python, you will succeed to install with:

/var/packages/homeassistant/target/env/bin/pip install {module}=={version}

Such manually installed modules can be added to a custom requirements file to get re-installed on package updates (since 2022.10.5-19).

For that add your custom modules to the file:

/var/packages/homeassistant/var/requirements-custom.txt

As homeassistant has such a lot of dependent python packages, there are still incompatible packages after installation.

When an integration fails to install within homeassistant, this can often be solved by restarting homeassistant: since Homeassistant Core 2022.10.5 the restart in homeassistant does not work anymore. You have to stop/run in the DSM package center (or synopkg restart homeassistant in the shell on an ssh session).

• How to give access to usb device #4651

State as of Home Assistant Package Versions

• 0.114.2-9
• 0.118.5-11
• 2021.1.5-13
• 2021.8.8-14
• 2021.9.7-15
• 2022.10.5-19
• 2023.1.7-20
• 2023.7.3-22 WARNING: only aarch64 and x64 archs are used to validate working integrations in the list below. Packages are provided for x64 (x86_64), evansport (i686) and aarch64 (arm64). armv7 and qoriq models are not supported anymore (deactivated per 2025/02/22).
• 2025.1.4 is under development in #6453. It will require DSM >= 7.1 and support Models with x64 architecture. There is a chance that evansport (i686) and aarch64 (arm64) will be supported too. It might be that even 32-bit arm (armv7) will be supported.
  Currently x64 and evansport packages are available as github build artifacts.