Closed camedomotic-unofficial closed 3 months ago
I noticed that, instead of leaving blank (default value) the Network section of the add-on configuration page, if I set manually the port value to a specific number (e.g. 3493), then the server becomes discoverable and the issue is addressed.
Even if this workaround fixed the issue to me, I would recommend to fix the default port management (when the port number is left to its default, blank, value in the configuration) so that it actually works.
This fixes the issue:
Note: The host a0d7b954-nut can be used to allow Home Assistant to communicate directly with the addon.
Does this host not work when setting up the HA integration without exposing the port?
Closing this, it's documented and if you want external access to the addon it is within the UI, which the addon itself cannot influence.
I'm facing the very same issue. With the slight difference, that setting the network port to 3493 still makes no difference:
So... what's wrong with the addon? How to locally check if the addon actually runs on the specified port?
--> netstat | grep 3493
on the host (HA OS) gives nothing.
Do I need to open another issue or... can we re-open this one and clarify the situation?
As per the documentation https://github.com/hassio-addons/addon-nut/blob/main/nut/DOCS.md#home-assistant-community-add-on-network-ups-tools
Note: The host a0d7b954-nut can be used to allow Home Assistant to communicate directly with the addon
So use a0d7b954-nut
as the host not localhost
This assumes that the NUT server is running and there are no errors in the logs.
Thanks for pointing to that important information.
Unfortunately that makes zero difference:
The addon is running, latest addon log excerpt:
67013.663674 [D1] mainloop: UPS [eaton_3s] is now connected as FD -1
67015.664853 [D1] mainloop: UPS [eaton_3s] is not currently connected
67015.665073 [D1] mainloop: UPS [eaton_3s] is now connected as FD -1
67017.667154 [D1] mainloop: UPS [eaton_3s] is not currently connected
67017.667376 [D1] mainloop: UPS [eaton_3s] is now connected as FD -1
67018.640692 67018.663924 [D1] mainloop: UPS [eaton_3s] is not currently connected
Poll UPS [eaton_3s@localhost] failed - Driver not connected
67018.664140 [D1] mainloop: UPS [eaton_3s] is now connected as FD -1
67020.664715 [D1] mainloop: UPS [eaton_3s] is not currently connected
67020.665189 [D1] mainloop: UPS [eaton_3s] is now connected as FD -1
I have no idea what's wrong with the addon. Help highly appreciated. I'm trying for hours over several months to finally get this running.
Tested different usernames/passwords (maybe the password is not allowed to have certain special characters?), tried completely without authentication (leave front door open option), tested with network port configured/not configured, tried "localhost", "a0d7b954-nut", "a0d7b954_nut", ... NOTHING works. Debug log needed? I could not spot any suspicious in there.
Problem/Motivation
I can't connect to my NUT instance neither from Home Assistant nor from any other laptop on my LAN. If I try to check the connectivity to the port 3493, it seems to be closed, even if the log says NUT is listening.
Expected behavior
localhost
on port3493
.telnet
ornc
on port3493
of my HA server, I would expect to get a Port listening message.Actual behavior
Steps to reproduce
localhost
, port3493
.Alternative:
telnet
that server on port 8123 (standard HA port) > SuccededLog
This is my NUT instance log on startup (DEBUG level):