tschoerk

I also get the "Error on device update" for my feed in Zählerpunkt. The consumption works and creates two sensors a live and statistics one, but for the feed in...

Thanks for the hint. I tried it as well, deleted everything like described in the FAQs with reboots between each step and reinstalled everything. The error still persists. Also got...

After testing it on several devices and the error still persisted, I figured it out. The Zählerpunkt which feeds in the unused power as the Anlagetyp "BEZUG" instead of "TAGSTROM",...

Also getting this Error. Logger: custom_components.wnsm.live_sensor Quelle: custom_components/wnsm/live_sensor.py:68 Integration: WienerNetzeSmartmeter ``` 2024-05-07 10:38:08.917 ERROR (MainThread) [custom_components.wnsm.live_sensor] Unable to load consumption 2024-05-07 10:38:08.918 ERROR (MainThread) [custom_components.wnsm.live_sensor] Please file an issue with...

Ok so figured it out after some tinkering. This problem only happens when there are two Zählpunkte. They way that the live sensor update works is that it gets the...

I tested different solutions with my proposed idea of changing the main or default zaehlerpunkt to get the meter readings, but I can't figure out how to do it properly...

Thanks for all the merges today! Regarding this issue: the way consumption is tracked with the live sensor is by getting the meterReadings from the default zaehlpunkt (call to zaehlpunkt/meterReadings...

Can you post the payload from the error and let me know what is the "default" zaehlpunkt at the Smart Meter Portal (then one that shows up on the main...

> I think I get it now @tschoerk. Since I'd not rely on the API too much of Wiener Netze (it has been proven quite irrational sometimes, especially without proper...

I found a solution. The API call to zaehlpunkte/{customer_id}/{zaehlpunkt}/messwerte with the valueType METER_READ gives out the meter readings of the selected dates. This is implemented in the historical_data function of...