-
Notifications
You must be signed in to change notification settings - Fork 19
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
FormatException in GetPowerUsage causes repeated disconnects #123
Comments
Hi, Could you please do the following for me:
After that, please attach the entire log file to your next comment here. Thank you! |
|
Thank you for providing that - this confirms that something strange is happening in this area:
I'll need some time to create a debug build for you, but if you could please test when I do then I'd really appreciate it. |
Hello, I have the same problem: it was working great with v2.2.8690, but starting with v2.2.8693, it stopped working with the same symptoms... My NUT server is an Raspberry Pi Zero running RaspBian 12, connected to a Technoware Era Plus 1100 UPS via USB Here are my logs:
|
Hi all, thank you for the reports. This one is a bit of a mystery to me. I've added some debugging code so when you hit the error next time, it will print out additional information into the log file. It also won't disconnect anymore, instead the power calculation will just be zero. I have that debug build cooking over here. Once the download is available, please go ahead and run it, and report back with a few things for me:
Thank you! |
The debug version is working now
|
Your power/load indicator should have been broken and displaying zero, but it's clear to me now that this was just a careless mistake on my part. New build has dropped here, please test again when you get the chance. I expect that the |
Hello @gbakeman , the latest debug build (WinNUT-Client-debugbuild-v2.2.8747.34564) allows me to use NinNUT again, but the error seems to remain (see logs attached) and the load value indicates 0 even though the load percentage indicates 37%:
|
It sounds like I still haven't fully understood the problem! 😄 I'm going to take a deeper look at this and ask for your patience while I work on a few things. Please stay tuned for another update. |
I've made an attempt to standardize some code that I think was causing the problem. I'm not quite sure how to change my computer's locale to correctly reproduce the issue, so thank you for testing these changes for me. Please give the new build here a try and let me know if you see any problems. In the future if you want to upload a log, please click and drag the log into your comment on GitHub - that way it's uploaded as an attachment. Thank you! |
Your last build seems to work correctly: Thank you ^_^ |
Excellent, thank you everyone. I'll have a pre-release update out soon. |
Im using NUT server on Tomato firmware router. Last working version was v2.2.8690. After that WinNut gets data for a second then recconects in a loop.
The text was updated successfully, but these errors were encountered: