Closed MACscr closed 4 years ago
Fpl changed the way it expose data, Im working on it
On Tue, Jun 30, 2020 at 2:22 PM Mark Chaney notifications@github.com wrote:
Seems after the resent changes, there is no longer any total usage tracking for the billing cycle? Is that the case?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dotKrad/hass-fpl/issues/5, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD6TTAUGTNYBEMEEDNBJMMLRZIUM7ANCNFSM4OMQ4XOA .
No problem. Sure wish they provided an api and also access to the bidgely data.
they don't provide an Api, I'm using the api they are using with the web app, kind of reverse engineering
On Tue, Jun 30, 2020 at 2:32 PM Mark Chaney notifications@github.com wrote:
No problem. Sure wish they provided an api and also access to the bidgely data.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dotKrad/hass-fpl/issues/5#issuecomment-651968736, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD6TTASW3BLNF5JV7FRPNQLRZIVSHANCNFSM4OMQ4XOA .
Completely understand. Thats why I said i WISHED they had an api. =P
I ended up creating a custom sensor template using the daily usage total:
fpl_total_power_usage:
friendly_name: "Total Power Usage"
value_template: "{{ state_attr('sensor.fpl_1XXXXXXXX','daily_usage') | sum(attribute='usage') }}"
unit_of_measurement: kWh
Seems after the resent changes, there is no longer any total usage tracking for the billing cycle? Is that the case?