#NUT add-on and integration running fine, but how to connect the Synology as client

1 messages · Page 1 of 1 (latest)

merry helm
#

several online posts suggest we create a dedicated user https://www.reddit.com/r/homelab/comments/5ssb5h/ups_server_on_raspberry_pi/ and others, but the options they propose, mostly the password: secret is not accepted by the Add-on. Makes sense 😉

It also suggests we ssh into the DSM, and change user settings, but I really dont like that, I cant imagine the Home Assistant add-on not being able to take care of it via it's settings somehow.

all I end up with in the DSM is this. I also tried another suggestion, to explicitly mentiuon the port on the server. Makes no difference at all.

if anyone here would know of a fix, please dont hold back

(I can't use the NUT server on the Synology, it isn't online always. It must be on the HA server. USB from UPS to HA server working fine, and integrations shows all entities)

Schermafbeelding_2025-04-06_om_13.30.51.png
prime pawn
merry helm
#

there is this which states the port is opened

Schermafbeelding_2025-04-06_om_17.42.23.png
#

I've also tried to enter that into the field explicitly, as is suggested in several other posts, but that doesn change things

prime pawn
#

put 3493 in the box and save

#

have you restarted the addon since making the change?

merry helm
#

yes, that happens automatically

prime pawn
#

is there anything in the log when you try and connect to it?

merry helm
#

yeah, well it depends. mostly breaks on the password, and then the add-on simply does not start, unless I select the I want to be pawned toggle

#

other than that, nothing I can see in the add-on log

#

made me wonder if the Synology client requires a certain privilege to connect.

# 
[16:02:37] WARNING: Password is in the Have I Been Pwned database!
[16:02:37] WARNING: Password appeared 1008712 times!
[16:02:37] FATAL: 
[16:02:37] FATAL: We are trying to help you to protect your system the
[16:02:37] FATAL: best we can. Therefore, this add-on checks your
[16:02:37] FATAL: configured password against the HaveIBeenPwned database.
[16:02:37] FATAL: 
[16:02:37] FATAL: Unfortunately, your configured password is considered
[16:02:37] FATAL: unsafe. We highly recommend you to pick a different one.
[16:02:37] FATAL: 
[16:02:37] FATAL: Please change the password in the 'users[1].password' option.
[16:02:37] FATAL: 
[16:02:37] FATAL: Check the add-on manual for more information.
[16:02:37] FATAL: ```
prime pawn
#

so thee synology requires specific credentials but the server doesn't like that because its a stupid idea?

merry helm
#

haha, yes that seems to be the case....

#

or, at least that is what I understand of it right now

prime pawn
#

have you put on the i_like_to_be_pwned option?

merry helm
#

yes, in that case the add-on startups fine. But still get the same 'cant connect ' notification in the DSM

prime pawn
#

can you post the full nut addon yaml?

fallow axle
#

Looking at your forum post it appears you have myups

#

You can also test connectivity using upsc from a remote client

prime pawn
#

chaos

fallow axle
#

Yeah not exactly well implemented 😉 Good to know the credentials for anyone with a Synology

prime pawn
merry helm
#

so not monuser?

prime pawn
#

not username but name

#

your posted image shows

name: myups
change that to
name: ups

merry helm
#

well yes, that was it!

#

only changed that, and didnt add a dedicated user at all, and now get

Schermafbeelding_2025-04-06_om_19.49.09.png
#

thanks you @fallow axle and @prime pawn .

#

marking that as solved! 😉

digital needle