Probably all mine are set to like 2mins to get max runtime. I guess if yiu are saying you need 20 mins if min runtime than it could be considered discharged even while its charging weird. Ill lok at adding discharged to battery state.
By the way if anyone is looking to hook up their ups to monitor with the netcard but it is not near your router these work really well with the ups netcard when set to access pt mode
TP-Link AC750 Dual Band Wi-Fi Travel Router TL-WR902AC
new version 2.5 in github and on package manager..
v 2.5 aug 2022 apparently even if ups is charging but you set your low battery duration to a weird number like 20 minutes it will show battery status as discharged until it surpasses that
added the follwing attributes (model number, serial number, firmware version, battery type, manuf. date) so test on your ups to make sure it didnt break anything
Ie manuf date .serial number etc. To figure out some are missing you will need to turn on debugging and i may need to tweek it for your firmware version.
It looks like only model and battery type are missing.
Also other normal attributes are missing like last My guess is your network card firmware is not fully supported or doesn't have everything. It will be hard to debug Without having one of those cards. What card is it and what firmware version is on it?
Also shouldn't have a current check time as low as 1 minute that can cause undue load on the hub and it may not even finish updating in that time.
Can you add Output in Wh ? It would be very useful for dashboards.
If this is not available in can be calculated in the background. I already used that for the hubitat dashboard but for Grafana this method makes more sense. If you get the model you already have the total watts output. If not maybe you can use a field for manual input. Then you multiply the total by OutputWattsPercentage, and divide by 100.
new version 3.5.
the last round of changes i noticed that quit was being issue too early in the sequence never moved it to the end of the new commands so it was closing the socket too early.. It sometimes worked, but sometimes depending on if and when data came back after quit got out of sync..
Also, I had a quit at the end of the list of commands to be issued, but for some reason the telnet library seems to have changed and hubitat now seems to be interpretting the commands and when it sees the quit now closes the socket immediately even before any input comes back so I had to remove that. Previously i explicitely had to issue the closeConnection command to close the socket..
i dont that that is really accurate.. i am thinkng the outputcurrent * the outputvoltage should be the watts. for one thing the rating on the model number is VA not watts
You have a model rating in VA which for my UPS is 1000 and one rating in Wh which is 700.
(700*35%)/100 = 245 Wh. I know this is accurate because i have a smart plug on the input.
