TapHome
Gathering interest Feature

Client certificate for HTTPS devices in Packet Parser

The Core would present a client certificate to devices whose local HTTPS API asks for one (mutual TLS), so they can be connected through Packet Parser without a bridge in between.

Why and how you would use it

Some devices accept requests to their local HTTPS API only from a client that presents a client certificate with its private key (mutual TLS). Packet Parser can check the device certificate or ignore certificate errors, and it can sign in with a user name and password, but it cannot present a client certificate. The device then ends the connection before any script gets an answer.

What will be possible

We are evaluating this idea. Nothing is scheduled yet.

  • Client certificate on a Packet Parser module. You would add a PKCS#12 file (.p12 or .pfx) with its password in the service settings of the module. The Core would present it whenever the device asks for it. Scripts and templates stay the same.
  • Expiry warning. The module would warn before the certificate expires.

What will not be possible

  • Getting the certificate. It comes from the device or its manufacturer. TapHome would not create it.
  • Other connection types in a first version. TCP with TLS and MQTT brokers that ask for a client certificate are not part of it.

How to solve it today

A reverse proxy on a small computer, a NAS or a router holds the certificate, talks to the device over HTTPS and offers the Core a plain HTTP address for Packet Parser.

Learn more

Do you need this for a device? Vote for this idea and follow it for updates.

Related

Status history

  • Nov 4, 2026 Gathering interest Published

Comments 0

Join the discussion

Sign in with your TapHome account to comment. The team approves comments before they appear.

No comments yet.

Ideas describe direction, not commitments. We do not publish dates; released features are announced in the release notes.