Fix DeviceClasses for Potential's & Current's

Solve #46

Supporting default HA sensor customization's

By default HA sensors can be customized by the user [mainly this are unit factor's and the display precision]. This feature was totally ignored by previous implementations of this integration and with this release its finally supported.

The change implies, that for some of the existing sensors the default display (precision) have been adjusted - if you dislike the new display format you can now simply adjust it the sensor settings.

HACS default ONLY

Only required for cleaned up HACS.json

Extended support for 'IEC-62056-21' meters

As reported by @dieMichaels - there are IEC-62056-21 meters that does not include *255 before the ( that contains the actual value... So the parser have been adjusted in order to handle this situation. RegEx FTW!

Fixing device_class of Wirkleistung

unit_of_measurement=UnitOfPower.WATT implies device_class=SensorDeviceClass.POWER

fixing #30

Adjustments for latest HA release (get rid of warning)

2024.7.0

use 'async_forward_entry_setups' & 'async_unload_platforms'

A experimental 'IEC-62056-21' parser version

Ben shared some alternative 'IEC-62056-21' output, that easily could be parsed as plaintext - at least that's the plan - let's consider this as 'experimental' (#29)

Just maintenance

Try to improve "not implemented yet" handling for none SML or Plaintext modes

Fix: Detected blocking call to open inside the event loop by custom integration (V2)

2024.6.1

fix for changed init-procedure

Fix: Detected blocking call to open inside the event loop by custom integration

removed 'local' reading of manifest.json

+fix-it