I've only just noticed a while back that my APCUPSD PI (rev 220.127.116.11) is not getting data from the UPS (APC XS1300) ...and it would appear it hasn't since last September.
The problem might not be the PI: Windows (7-32) device manager sees the UPS and appears to have the correct driver, but neither the PowerChute (Personal 3.02) software nor the PI seem to see the UPS anymore.
After several attempts at fixes I uninstalled everything including the "device". When I plug the UPS back in, Windows recognizes the UPS and reinstalls the correct driver, but when I try to reinstall PowerChute it can't because it can't see the UPS; neither does the PI. If I click on "Enable" on the device page the icon goes green for a 1/2 second and then goes back to "disconnected".
I'm using 127.0.0.1 and port 3551. And here's the error from the log:
An unexpected error occured in the connect function/subroutine: [System.Net.Sockets.SocketException (0x80004005): No such host is known at System.Net.Dns.GetAddrInfo(String name) at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6) at System.Net.Dns.GetHostEntry(String hostNameOrAddress) at HSPI_APCUPSD.hs_socket_io.Connect(String RemoteHostName, Int32 RemotePort, Boolean usesSizePrefixedMsg, Boolean useASyncIO)]
The warning is: Communication error with UPS1 upon connect: Connection refused.
Anyone else having, or had, this issue?
Does PowerChute, or any particular service have to be installed for the PI to work?
Any ideas? I suspect it might be windows issue subsequent to an update.
urrent Date/Time: 3/18/2017 4:40:54 PM
HomeSeer Version: HS3 Pro Edition 18.104.22.1683
Operating System: Microsoft Windows 7 Professional - Work Station
System Uptime: 0 Days 0 Hours 39 Minutes 0 Seconds
IP Address: 192.168.2.111
Number of Devices: 408
Number of Events: 138
Available Threads: 400
22.214.171.124: Device History
126.96.36.199: HSTouch Server