-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wnsm: Error on device update #223
Comments
Hi @sonypsx
In order to rule out the first two possibilities, could you
Thanks in advance. |
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 there's only 1 sensor created (the live one, not the statistics one) and that one is empty, so it's not usable in the energy dashboard. I only have that feedin Zählerpunkt for a couple of days, maybe it has to be a certain age before it's usable? Core 2024.5.2
|
hi, @tschoerk it works nicely for me. I am running on y x86 device, HA updated to the latest version, same for wnsm and HACS. I had issues before, but I removed the wnsm deleted all at.. data eintries etc. rebootet. then it worked. if you log in the Portal of Wiener Netze it works nicely I assume? |
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 an error like described in issue #227 maybe they are stemming from the same issue. |
strange .. the code base 1.40 works (at least for me), so either some config data in your smartmeter is different creating an issue, or something is wrong with your data. |
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", like the normal Zählerpunkte. Checking the API calls directly at the Wiener Netze Portal showed me the correct URL. The correct parameter for rolle is E002 (quarterly check in this case) instead of the hard-coded V002 (or E001 instead of V001). I made a fix by changing the get_zaehlpunkt method in the client.py to also return the Anlagentyp and then check if the type is BEZUG. If true, then the role is changed to E001 or E002 depending on the valuetype. I will make a pull request, maybe it's viable to use - at least the idea should be. Not too much experience with it. Restarted HA and now I have a fourth entity with all the feeding statistics to use for the energy dashboard. |
Hello,
first i am excited that this nice piece of software is avail!
But,I never got that wnsm working completly. The only value i can get is the value of my grid export smartmeter point. All other features like Historical data or the Grid import Smartmeter value aren't working since i found this addon.
Am i am doing something wrong?
Hint: i am aware that currently Wiener Netze do some maintenance these days, but it wasn't working before also so ...
Using:
Core 2024.3.0
Supervisor 2024.02.1
Operating System
HACS:
Integrations Version: 1.34.0
Frontend Version: 20220906112053
wnsm: v1.4.6
2024-03-10 21:49:00.368 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform wnsm is taking over 10 seconds. 2024-03-10 21:49:00.442 ERROR (MainThread) [homeassistant.components.sensor] wnsm: Error on device update! Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 682, in _async_add_entity await entity.async_device_update(warning=False) File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1262, in async_device_update await self.async_update() File "/config/custom_components/wnsm/statistics_sensor.py", line 123, in async_update await self._import_bewegungsdaten(smartmeter) File "/config/custom_components/wnsm/statistics_sensor.py", line 187, in _import_bewegungsdaten recording = await self.get_bewegungsdaten(smartmeter) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/wnsm/base_sensor.py", line 154, in get_bewegungsdaten response = await self.hass.async_add_executor_job( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/wnsm/api/client.py", line 504, in bewegungsdaten raise SmartmeterQueryError("Historical data is empty") custom_components.wnsm.api.errors.SmartmeterQueryError: Historical data is empty 2024-03-10 21:49:01.194 ERROR (MainThread) [custom_components.wnsm.live_sensor] Unable to load consumption 2024-03-10 21:49:01.195 ERROR (MainThread) [custom_components.wnsm.live_sensor] Please file an issue with this error and (anonymized) payload in github {'hasSmartMeter': True, 'isDataDeleted': False, 'zaehlpunkt': 'AT0010000000000000001xxxxxxxx', 'type': 'BEZUG', 'address': 'Adresse', 'zip': '1234'} {} {'lastValue': 302025, 'lastReading': '2024-03-08T23:00:00.000Z', 'lastValidated': True, 'lastType': '1-2:2.8.0'} {'optIn': True, 'consumptionAverage': 0, 'consumptionMinimum': 0, 'consumptionMaximum': 0}
The text was updated successfully, but these errors were encountered: