Guys, this is a really good forum. It’s clear you’re trying to help and figure things out.
Let me clarify a few points.
The problem, as I understand it, isn’t with the addon itself, but with the system core.
Not only the Samba password is checked online, but also the SSH. There might be something else, too.
I found the discussion link I was reading, and it also suggested a workaround: use the command
ha resolution check options --enabled=false addon_pwned
I was able to run SSH without a password, using the generated key, and I used this command. But it didn’t work.
Your connection probably works because when you installed the addon and set the password, you had a normal connection to the server, which allowed the addon to work properly.
I can’t connect to this server for reasons beyond my control. Again, changing the DNS didn’t help, and my router won’t let me set up a VPN.
But the main question is, how did we get to the point where our beloved Home Assistant project has become dependent on cloud checks and servers? Isn’t its ability to operate autonomously its main value?