Add battery test sensor?

[jenshorn]

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.

[faanskit]

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: fcrd_activated, fcrd_deactivated, fcrd_failed
See example automation in the documentation.

[faanskit]

(Too quick to close...)
The issue will be converted to a discussion should feeback be needed.

[jenshorn]

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?

[faanskit]

I actually don't know why it behaves like this, likely i corrupted something when I removed some config attributes.
The only way to fix this is to remove CheckWatt and re-install it. Good thing is that your data remains of you do that.

[faanskit]

#60 was created for this to make it transparent

[jenshorn]

Deleted and re-added the integration. Provide CM10 sensor is now selected by default and everything appears to work. Thank you for your time!

Btw, is there any documentation regarding each of the FCR-D Info 96,0/0,7/90,8 %?

[faanskit]

I've seen it once referenced on facebook, but cannot find it.
I think it is FCR-D Up / Action Time / FCR-D Down

I can have mixed Up and Down.

There are supposed to be documentation available for partners for this.

[faanskit]

Found some info, do not have the reference
Discharge / Response time / Charge
Eg. 99,0/2,9/97,7

Targets (old?):
90% / 10 sec / 90%