-
Notifications
You must be signed in to change notification settings - Fork 15
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
Incorrect Meter being selected #205
Comments
I tried contacting Wiener Netze to ask them to remove the inactive meter from my account, but 3 weeks later I have still not received any response. Is there no way to fix this inside HA? |
I think there is a problem with the manual configuration part. Using the config flow, by removing all configuration from your json config files and removing all sensors + integration and reinstalling it should do the trick. I'll have a look into the manual config setup. I guess this was not bubbling up, because nearly all of us are using the auto setup with config flow. |
ah okay. Now I get it. The statistics sensor is inactive due to some limitations regarding WienerNetze API and Home Assistant. It is completely normal. Your setup works as expected. Please see the FAQs for the reason why this is happening #19 |
I deleted all the WNSM Files and reinstalled the latest version (1.4.3). It is still selecting an inactive meter. Here is a screencap: |
@DarwinsBuddy I just removed and reinstalled the integration and am now on 1.4.5. This issue still persists. Can I somehow provide more information to help fix it? |
Hi
|
I have two Smart Meters listed in my account, but one of the meters has been inactive for over a year. The integration is selecting the inactive meter instead of the active meter.
A good solution would be to ask the user which meter should be used for the integration after the user logs in with their ID & Password.
In the mean time is there a way to change which meter gets selected?
I tried adding data to my
configuration.yml
andsecrets.yml
files manually, but the data isn't takingThe text was updated successfully, but these errors were encountered: