From 3aa2a03084e1dab87e0e9633ada97a3be9c8e925 Mon Sep 17 00:00:00 2001 From: jjlawren Date: Mon, 2 Mar 2020 22:47:52 -0600 Subject: [PATCH] Update cert_expiry for #32066 (#12178) --- source/_integrations/cert_expiry.markdown | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/source/_integrations/cert_expiry.markdown b/source/_integrations/cert_expiry.markdown index bd9145cd66d6..1bdae51a1826 100644 --- a/source/_integrations/cert_expiry.markdown +++ b/source/_integrations/cert_expiry.markdown @@ -18,7 +18,7 @@ The `cert_expiry` sensor fetches information from a configured URL and displays There are 2 options in configuring the `cert_expiry` sensor: -- Via the Home Assistant user interface where it will let you enter a name, host and port for the certificate to check. +- Via the Home Assistant user interface where it will let you enter a host and port for the certificate to check. - Via the Home Assistant `configuration.yaml` file. @@ -39,13 +39,17 @@ port: required: false default: 443 type: integer -name: - description: The friendly name for the certificate. - required: false - default: SSL Certificate Expiry - type: string {% endconfiguration %} +## Attributes + +The Certificate Expiry entities provide extra attributes to represent the state of the certificate. + +| Name | Description | +| ---- | ----------- | +| `is_valid` | If the certificate is able to be validated: `True` / `False`. +| `error` | A human-readable error description if the certificate is considered invalid, "None" otherwise. +
Make sure that the URL exactly matches your endpoint or resource.