---
title: "Additional CA"
description: "Additional CA is a Marketplace integration for Home Assistant. It has 909 installs sharing analytics, works locally and was last updated October 17, 2026."
canonical: "https://vulpo.app/integrations/marketplace/athozs-hass-additional-ca"
url: "https://vulpo.app/integrations/marketplace/athozs-hass-additional-ca.md"
last-updated: "2026-10-22"
version: "1.4"
---

# Additional CA

> Additional CA is a Marketplace integration for Home Assistant. It has 909 installs sharing analytics, works locally and was last updated October 17, 2026.

Additional CA loads a private Certificate Authority or self-signed certificate into Home Assistant for TLS/SSL access. It lets integrations reach devices and third-party services that use certificates Home Assistant would not otherwise trust, such as a personal HTTPS web server, SMTP or LDAP service. The certificate is loaded again automatically after Home Assistant is upgraded, so the trust does not need to be redone. It works locally and is set up in the UI, with the certificate file placed in the configuration folder. A restart of Home Assistant is needed after changes, and a notice can appear in Settings under Repairs to say so.

Automatic summary of the README and code of Athozs/hass-additional-ca. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact)

[Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=Athozs&repository=hass-additional-ca&category=integration)

On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=Athozs&repository=hass-additional-ca&category=integration)

## Supports

- **Works locally**: Talks to your devices on your own network. No vendor cloud in between.
- **From the Marketplace**: Installed through the Marketplace, formerly HACS.
- **Actively maintained**: Its author released or pushed a change in the last six months.

## Setting it up

Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.

## Troubleshooting

- **Repair notices**: Notices it can show in Settings, Repairs:
  Home Assistant needs to be restarted

## From the README

> The Additional CA integration for Home Assistant automatically loads a private Certificate Authority or self-signed certificate into Home Assistant to access 3rd-party services with TLS/SSL, even after Home Assistant is upgraded.

From the README of [Athozs/hass-additional-ca](https://github.com/Athozs/hass-additional-ca#readme), [MIT License](https://spdx.org/licenses/MIT.html). Shortened.

## At a glance

- Kind: Marketplace integration
- Category: [Computers and network](https://vulpo.app/integrations/category/computers-and-network.md), Cloud and developer tools
- Number: 909 installs sharing analytics; 93 GitHub stars
- Connection: Works locally
- Upkeep: Updated in the last 6 months
- Needs: Needs the Marketplace (HACS on 2026.10 and older)
- Latest version: 0.6.2, last updated October 17, 2026
- Domain: `additional_ca`
- Source: <https://github.com/Athozs/hass-additional-ca>
- Issues: <https://github.com/Athozs/hass-additional-ca/issues>

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about)

Last updated 2026-10-22. Source: https://vulpo.app/integrations/marketplace/athozs-hass-additional-ca

---

- HTML version of this page: https://vulpo.app/integrations/marketplace/athozs-hass-additional-ca
- Site index for agents: https://vulpo.app/llms.txt
- Everything in one document: https://vulpo.app/llms-full.txt
- All pages: https://vulpo.app/sitemap.xml