UPS disconnect

[lshollis2024]

I too have a UPS disconnect problem. My newly installed F4-423 v6.0.461 recognizes my new Cyberpower CP1500PFCLCD and it connectes without any problems. But after a day or less it becomes disconnected. It says that the usb device is not connected. But if I pull the usb plug the system says the usb device was unplugged. This make absolutely no sense. What is wrong with this OS? There is no way that the connection to my UPS should disconnect on its own. What use is a UPS that isn't reliable?

[EthanLiu]

I too have a UPS disconnect problem. My newly installed F4-423 v6.0.461 recognizes my new Cyberpower CP1500PFCLCD and it connectes without any problems. But after a day or less it becomes disconnected. It says that the usb device is not connected. But if I pull the usb plug the system says the usb device was unplugged. This make absolutely no sense. What is wrong with this OS? There is no way that the connection to my UPS should disconnect on its own. What use is a UPS that isn't reliable?

Hello, after verification, it is true that this model of UPS has a disconnection problem. We will find out the reason for the disconnection as soon as possible to solve your problem.

[lshollis2024]

This is lsusb on console. The system auto detect got the wrong device. I have a Cyberpower cp1500pfclcd and not that listed below. Could be a problem. The ups tool in tos say no ups is attached but it is in the list of attached devices.

Bus 001 Device 005: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 001 Device 003: ID 0764:0601 Cyber Power System, Inc. PR1500LCDRT2U UPS
Bus 001 Device 004: ID 03f0:140c Hewlett-Packard HP Wireless Keyboard Kit
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[lshollis2024]

I have fixed the UPS disconnection problem for my specific case. I switched out my Cyberpower CP1500PFCLCD for and older APC UPS that I have, model BACk-UPS XS 1500G. When I hooked this to my F4-423 and booted for the first time it saw a UPS was connected but said it was still the Cyberpower UPS. But after I rebooted for a second time it found the APC UPS and connected to it by default. It even identified the correct model id. It has stayed connected for about 24 hours so far. I also looked into how TOS is connecting to the UPS. It uses NUT. I can run sudo "upscmd -l ups" and other NUT related commands like "sudo service nut-server status" and see that the APC is up and running. I can also see the UPS settings, voltages and charge etc. While I can't edit the conf files I can still see where it is finally working. So as best as I can tell the problem probably lies with the drive that is being used by NUT to interact with the Cyberpower UPS. The autodetect feature does get the model number wrong when the CP UPS is attached so that could be the issue. Perhaps the TM team can look into that. For those interested there is a good writeup about how to install and use NUT on a Raspberry Pi. It is very helpful. Do a search for "MelGrubb.ToBlog" Good information in there.

[TMzethar]

Okay, thank you for the additional information that will help us determine the problem.