Replies: 3 comments 9 replies
-
Thanks for the proposal, but it will be rejected. You can easily create such a sensor using Templates as described in the documentation. The FCR-D is available as an attribute on the CM10 sensor. On top of that, FCR-D changes are already published as Events, again as described in the documentation. Said events can be used to trigger automations. The following events are thrown and can be used to create automations: |
Beta Was this translation helpful? Give feedback.
-
(Too quick to close...) |
Beta Was this translation helpful? Give feedback.
-
I have seen the FCR-D events but I have failed to see any metrics from the latest battery test, ie 96.1% of possible power or however it is available in the logs. Are you saying that it's available somewhere already? |
Beta Was this translation helpful? Give feedback.
-
As I believe you are already parsing the logs for the FCR-D state, would it be possible to also parse for the latest battery test run add a sensor with the result? Having that value, seeing it over time, and also give the possibility for automations/alerts in HA could be beneficial for multiple reasons.
Beta Was this translation helpful? Give feedback.
All reactions