Two problems ! - Githubissues

gawindx / WinNUT-Client

This is a NUT windows client for monitoring your ups hooked up to your favorite linux server.

GNU General Public License v3.0

395 stars 70 forks source link

Two problems ! #59

Closed Dim3333 closed 3 years ago

Dim3333 commented 3 years ago

Hello,

I installed for the first time, WinNUT Client and :

after re-start of Windows, Winnut don't appears in the systray
when i click on the executable file, the icon appears in the systray and disappears immediately. Winnut don't open.

Thanks

gawindx commented 3 years ago

which version do you have installed? the last stable (2.0.4.0) or the last beta (released a few days ago)?

the last stable version contains bugs on the stability of the connection, bugs fixed in the last beta version (as well as others and some improvements).

Have you already configured the parameters or are they the default ones?

Dim3333 commented 3 years ago

I installed the last stable. I configured the parameters without problems.

But now i can't launch WinNUT.

gawindx commented 3 years ago

have you checked in the taskmgr if the process is present or not? (just to be sure because Winnut is configured for a single instance, it will not run if it is already running)

When you say you can't launch it, is that also valid for manual launch?

Dim3333 commented 3 years ago

Not in the taskmgr. If i click on the icon (.exe), WinNUT appears and disappears immediately. Yes, i can't launch it manually.

gawindx commented 3 years ago

So if I am summarizing well, you were able to launch it after installing it and you were able to configure it.

And since then you can no longer execute it.

Can you try to remove the "HKEY_CURRENT_USER\SOFTWARE\WinNUT" key from the registry, that will reset the settings and you should be able to run it again.

It remains to be seen which parameter poses a problem.

On the other hand, I identified a bug on the loading of the default parameters after a new installation so open Winnut once and close it. Open it a second time and you can configure it.

this bug will be resolved in the next stable version (expected in a few days).

Dim3333 commented 3 years ago

It seems that's OK after delete the "HKEY_CURRENT_USER\SOFTWARE\WinNUT" key from the registry. Remarks : The manufacturer, Name, Serial and firmware are indicated as "Unknown". The values (voltage, load, ....) seems to be fixed (no evolution) The load batterie value is fixed at 20%. What is it ?

I have exactly the same values (and issue) that in this topic : https://github.com/gawindx/WinNUT-Client/issues/43

gawindx commented 3 years ago

Two possibilities :

This informations is not retrieved by Nut or the Nut driver
Bad connection between WinNut and Nut (Possible with version 2.0.4.0) or between NUT and the UPS

I would lean more for the second possibility given the abnormal values that you recover

Dim3333 commented 3 years ago

I found, for a Synology NAS, the correct parameters are :

NUT Server : IP of NAS NUT Port : 3493 UPS Name : ups Delay : 5000 NUT Port : 3493 Login : upsmon password : secret

In the french traduction : Préférences -> Divers -> Démmarrer avec Windows (Démarrer).

Ririx02 commented 3 years ago

"Démmarrer avec Windows (Démarrer)." petite parenthèse en passage => "Démarrer avec Windows (Démarrer)." une petite faute ^^

gawindx commented 3 years ago

Là, sur celle la, j'ai pas l'excuse de la langue....

C'est corrigé pour la prochaine version, qui sera dispo ce soir.