core: Certificate Expiry component

Home Assistant release with the issue:

Version 0.99.0

Last working Home Assistant release (if known): n/a

Operating environment (Hass.io/Docker/Windows/etc.):

arch | x86_64 dev | false docker | true hassio | true os_name | Linux python_version | 3.7.4 timezone | America/New_York version | 0.99.0 virtualenv | false

Component/platform:

https://www.home-assistant.io/components/cert_expiry/

Description of problem: Configuring the sensor using YAML certainly not working. Manually add it + bottom right. Certificate. But every time HA restart sensor shows “Unavailable” status (adding new sensor Obihai ). Have to remove from integration, restart, add again.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

sensor:
  - platform: cert_expiry
    host: xxxxxx.xxxxxx.xxxxx

Traceback (if applicable):


Additional information:

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 1
  • Comments: 38 (12 by maintainers)

Commits related to this issue

Most upvoted comments

BTW: Thanks for your work.

yep just test it seem to work just fine, thanks

Something was changed for sure because my sensor stopped working as well. I had the certificate expiry sensor defined in my yaml configuration and it’s been happy for a long time. With 99.x, it stopped working and I got the Integration discovered message. I proceeded to do it and it worked right away, until I restarted; then it would not work anymore. I removed EVERYTHING (integration and yaml config) and just let it HA discover it. I now get “unavailable” for the value of the certificate. Something is wrong for sure…

@tomlut i can assure you this is not the problem. Do this:

  • remove integration
  • do a restart of ha to make sure all ok
  • add integration from integration page

You will see it will work right away until you restart again. You can do this every 5 mins if you want it will work every time.

Even if it were a server side problem, sensor should keep old value in my logic for at least 12 hours until is sure new server value was pulled.