Open tuffig opened 1 year ago
Also, the battery only charges to 90%
A current battery capacity algorithm is based on bus voltage which uses this formula:
percent = (bus_voltage - 6) / 2.4 * 100
so 6V - 0% and 8.4V - 100%
I've used this code from the official SDK.
I have the same issue with the batteries after two years of usage. Maybe it's battery degradation that causes a decrease in voltage as the battery loses capacity over time.
I've added max_percent property to do such calibration.
Thanks for the feedback, the batteries are brand new, but the charge indicator is not a problem for me. More important for me is why the many entries occur in the LOG
More important for me is why the many entries occur in the LOG
In the last update, I made the online status more stable by reducing sensitivity.
charge indicator is not a problem for me
You can now set max percent in the configuration:
sensor:
- platform: waveshare_ups_hat
max_soc: 91
So if 91 is max percent UPS will show 100%.
Hello,
I use the "Home Assistant Operating System" installation. I did the integration manually and before that I turned on I2C on the RASPI. The ups is recognized and I can see online status and charge status. But after some time many entries appear in the logbook:
waveshare_ups_has_online detected 09:00:01 - 1 hour ago waveshare_ups_hat_online reset (no(s) detected) 08:59:31 - 1 hour ago waveshare_ups_has_online detected 08:40:31 - 1 hour ago waveshare_ups_has_online reset (none(s) detected) 08:40:01 - 1 hour ago waveshare_ups_has_online detected 08:36:01 - 1 hour ago waveshare_ups_has_online reset (none(s) detected) 08:35:31 - 1 hour ago waveshare_ups_has_online detected 08:31:01 - 1 hour ago waveshare_ups_has_online reset (none(s) detected) 08:30:01 - 1 hour ago ...
Also, the battery only charges to 90%
I have no more idea that I can do