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

removed 'local' reading of manifest.json

+fix-it

Maintenance release: addressing 'HomeAssistantType' deprecation warning

This update will fix the warning

HomeAssistantType was used from <integration-name>, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.HomeAssistant instead, please report it to the author of the '<integration-name>' custom integration

when starting HA

Setup Error-Message enhancement

When during the setup no data can be read from the Pulse, there might be just the wrong IP/Host or Node Number provided.

Configuration Option to ignore parser errors & warnings

As result of issue #20 you have now the possibility (via the Integration configuration) to ignore logging of parser errors and warnings (to keep your HA log a bit more clear).

Enhanced (DEBUG) logging

When there are issues with the integration there is now additional DEBUG log output that will help to trace the possible root cause.

If you want to report an issue mare sure you have log data prepared (as described here)

Unit updates (internal only)

Make sure that the integration is compatible with upcoming changes in HA 2025.1

Improved German translation

Thanks @PattaFeuFeu

"Better" default Entities when no OBIS codes could be detected

I some situations it can happen that the integration is not able to detect the available OBIS-Codes (different data fields the power meter is able to provide). When you are running in such a situation (during initial installation or HA start-up) then only two Entities (imported total & current power) will be configured (will be available).

Thanks @davidm-glitch for your feedback.

Added alternative sources for Instantaneous Power (L1, L2 & L3) v3

NEVERENDING Story Easymeter Q3D...

Looks like, that some power meters use alternative OBIS codes to provide 'instantaneous power' information... previously the OBIS code 16.7.0 was only implemented (sum) - but there exist also 1.7.0, (positive), 2.7.0 (negative) and 15.7.0 (absolute) - which have been added with this release.

And also added some 'for me not plausible' OBIS codes for Easymeter Q3D (ffff instead of 00ff).. sigh

And added 'Aliase' to the EntityDescriptors (so that the code can find the alternatives during startup)

Make Node Number configurable (expert setting)

Implement #10

When you want to adjust the node number on existing installations, you need to remove the the existing device from your home assistant installation. BUT for all existing users: there is no reason to do so (since you have already a working version that make use of node number 1)