-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Remove relative time sensor from cert_expiry #42338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove relative time sensor from cert_expiry #42338
Conversation
Could you adjust the text in the breaking change field to be end-user friendly? For example, explain why this was removed, and preferably, if available, an alternative. |
Done, let me know if it's good enough now. Simone |
The description has confused the relative and absolute time terms. It's the days unit sensor that uses relative time and the timestamp sensor that uses absolute time. |
Yeah you are right, I changed the way of expressing and swapped the terms. Simone |
This PR is removing the relative time sensor. We should update that too in the description. |
I've updated the description regarding relative vs absolute sensor removal. |
Please update the first paragraph in the docs page for this integration: Link the docs PR in this PR description. Then we can merge. |
Done. Simone |
* 'dev' of https://github.com/home-assistant/core: (32 commits) Disable parsing scientific/complex number notation in template type (home-assistant#43170) Remove relative time sensor from cert_expiry (home-assistant#42338) Further improve MFI tests (home-assistant#43167) Update translations Guard against empty ssdp locations (home-assistant#43156) Fix playing of Spotify URIs on Sonos (home-assistant#43154) Add missing 'hassio' translation string (home-assistant#43127) Streamline SimpliSafe errors (home-assistant#43117) Update xknx to 0.15.3 (home-assistant#42026) Fix beat calculation (home-assistant#43142) Mock time_date sensor tests (home-assistant#43141) [ci skip] Translation update Fix bug preventing Notion entities from updating their bridge (home-assistant#43122) Bump hass-nabucasa to 0.37.2 (home-assistant#43146) Shelly: minor improvements (home-assistant#43138) Add support for learning RF commands with Broadlink remotes (home-assistant#39671) Fix incorrect Notion battery state calculation (home-assistant#43108) Bump hatasmota to 0.0.30 (home-assistant#43140) Add VSCode debug launch conf (home-assistant#43130) Revert "shelly_naming" rebase errors (home-assistant#43134) ...
Breaking change
In order to optimize stability and performance of HomeAssistant, sensors should use only absolute time values (store the date of the event) and not relative time values (seconds from event) so the db value doesn't change each seconds.
"cert_expiry" integration has both of them, so to adhere to HomeAssistant development rules, the offending sensor is now removed.
If your config was based on it, please switch to the other one.
Removed relative time sensor from cert_expiry
Proposed change
Removed relative time sensor from cert_expiry.
Type of change
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: