-
Notifications
You must be signed in to change notification settings - Fork 38
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
High SOC and Wattage number #305
Comments
Hello and thank you for opening this issue. |
Hi, The On my test instance, which is a clone of my working instance since I didn't want to mess up my data, there is a spike today 17:24:58. At 17:24:57, I see this error in the log: Then, at 17:24:58, I see this:
I'm also seeing some logs from other integrations about the network going down briefly, but I believe this is due to a saturated Ethernet connection while my backup is running. My test HA instance and the working instance are on the same Proxmox host and I am getting the same errors on the working instance, but on that one the readings stay normal. |
The problem
Hello, since a few weeks, the Victron integration on my Home Assistant had been reporting percentages above 100% for the batteries, and unreal numbers for the power Watts. This issue started with the update to Home Assistant 2.0. I have reverted a earlier backup of my Home Assistant (which now has version 1.4) be be able to keep using the integration in the meantime.
Environment
I am having this issue with Home Assistant 2.0 and up. I converted back from Remcom's repo to this one since this one seems to be active again, and I'm using the latest release 0.4.2.
Problem-relevant
configuration dialog
Not sure where to get this info, but this is in the configuration box if I click configure next to the device:
Traceback/Error logs
These are logs form the exact time a extremely high value appeared on Home Assistant. Nothing changed physically, and HA Core 1.4 with integration version 0.3.5 from Remcom is not reporting any anomalies during that period.
In case of unit ID issue, missing devices or non-updating devices
Additional information
Here's a screenshot of the issue:
The text was updated successfully, but these errors were encountered: