Skip to content

Releases: myTselection/telenet_telemeter

1.1.0

15 Apr 19:57
Compare
Choose a tag to compare
  • Fetching daily details for FUP with new Telenet backend in order to get correct peak & offpeak usage details.
  • Fixed removal issues #17

1.0.0

03 Apr 13:56
Compare
Choose a tag to compare
  • Fixed compatibility issues with new and old Telenet backend in combination with FUP or CAP type of subscriptions
  • typo fix for squeezed attribute

0.9.5

02 Apr 12:05
Compare
Choose a tag to compare

Trying to solve compatibility issues with new Telenet backend and many different product types (FUP & CAP)
related to #26
related to #25
related to #24

0.9.4

24 Mar 21:28
Compare
Choose a tag to compare

Bugfix (#24) for limited subscriptions connected to new Telenet backend.

0.9.3

23 Mar 13:14
Compare
Choose a tag to compare

typo fix

0.9.2 New sensor names!

23 Mar 13:00
Compare
Choose a tag to compare

product identifier set for v1 backend, used in sensor name

Please note: the sensor names have changed since r0.9.1! this might have an impact on your lovelace/automations/services!!

0.9.1

23 Mar 12:28
996ca3a
Compare
Choose a tag to compare

What's Changed

  • Implementation of Telenet API V2, utils cleanup and unique sensor IDs by @geertmeersman in #22

Full Changelog: 0.9.0...0.9.1

0.9.0 DRAFT new Telenet backend

20 Mar 22:53
Compare
Choose a tag to compare

First trial to get compatible with the new Telenet backend, based on feedback provided in #16 by @geertmeersman.
People having new Telenet telemeter website, could try this new release to see if telemeter data is fetched again, no guarantee as I can't test it myself for now.
Still compatible with old Telenet backend

0.8.2

20 Mar 20:30
Compare
Choose a tag to compare

protection for division by zero, related to #19

0.8.1

19 Mar 18:46
Compare
Choose a tag to compare

catch if missing product details, related to #19