similar to: New User Questions - With Belkin USB

Thanks very much for the help Roger. My ps|grep results almost mirror yours. Only my driver line is different - showing blazer. But I am still seeing: Broadcast Message from nut at loca (somewhere) at 15:25 ... Communications with UPS belkinusb at localhost lost Broadcast Message from nut at loca (somewhere) at 15:25 ... UPS belkinusb at localhost is

Hello all and thanks. I read here <https://mn3m.info/posts/configure-ups-monitor-using-nut-on-debian/> while searching around for my issue's resolution. In this I see that this nut driver is creating and using an entry in /dev (in this case ttyS0). So I "ll tty*" and see nothing with nut. Since this is a USB UPS, I suppose I should be looking for something in /dev/ttyUSB*.

On Jul 15, 2019, at 11:15 AM, David White wrote: > > 2. When I check the results from "netstat -t -n" I am NOT finding anything on 3493. Hmmm. I then tried "netstat -l" since there should be a server socket listening on 3494, right? There is nothing of 3493. But I do see an entry with local address = localhost:nut. When I "cat /etc/services" I find nut listed

Well it is the season for storms and power outages here in the US PNW. I noticed that today when the power went out, NUT mostly did what I hoped/wanted. But it did not actually turn off the UPS at all. The UPS kept beeping and I had to turn it off manually. I thought that NUT would handle this. But perhaps it cannot for my unit? Or perhaps I have things improperly configured? Any suggestions?

On Fri, 12 Jul 2019, David White wrote: > Hello, thanks, and sorry for the delay in getting back. I am running the > script and have move the comment from one D= line to the other. I am, > however, seeing some errors written to the console. They are from line > 64-65 of the script. > > Regarding line 64, I have no /usr/sbin/ups* and suspect the proper > location on my

On Jul 12, 2019, at 2:39 PM, David White wrote: > > Thanks Roger for all your help here. I hope the 2 attachments come through. The .sh is my doctored version of the script and the .report is its output. I welcome any suggestions or ideas about what might be causing my problems with monitoring to the Belkin UPS. Cheers Hi David, Nothing looks out of order in your configuration files.

On Jul 9, 2019, at 12:22 PM, David White wrote: > > So I guess I am wondering if this is related to my problem. I have no idea how the blazer_usb driver works. For the most part, NUT drivers ending in “_usb” (including blazer_usb) do not need a serial device node in /dev. They use libusb to talk directly to the UPS. (If you can reliably read the UPS status with upsc, then the connectivity

On Mon, 8 Jul 2019, David White wrote: > However I am a bit stumped on monitoring. What I want is to execute a script > when the UPS goes on battery. To do this, I think I have to have the > nut-client running. Is this correct? If so I seem to have some troulbe. You need to have nut-monitor.service running. The command systemctl list-unit-files | grep nut should report

Something just occurred to me. My kernel does not include USB->Serial code. Long ago, I had to figure out how to build a module for the ch341 USB->Serial adapter I use for running my Heyu home automation system. I never built one for Cypress and that seems to be what the Belkin is using. I know this because I see a line for it using "lsusb" that disappears if I unplug the UPS.

Hi Everyone, I am new to UPSs and Linux.? I purchased a Belkin F6C750-AVR UPS for our church.? We are?running CENTOS 5.2. I tried the Linux Power Management Software that came with Belkin UPS with NO success. I installed the NUT software. After some experimentation I received some success with the megatec_usb Nut driver: [root at server bin]# /sbin/megatec_usb -u root -a serverups -DDDD

Thanks Roger for all your help here. I hope the 2 attachments come through. The .sh is my doctored version of the script and the .report is its output. I welcome any suggestions or ideas about what might be causing my problems with monitoring to the Belkin UPS. Cheers On 7/12/2019 10:12 AM, Roger Price wrote: > On Fri, 12 Jul 2019, David White wrote: > >> Hello, thanks, and sorry

On Jul 8, 2019, at 6:35 PM, David White wrote: > > This makes me think something remains broken. But > > upsc belkinusb > > right after this gets results. Does "upsc belkinusb at localhost" also work? If not, check to make sure that localhost doesn't resolve to a slightly different address than what upsd is listening to. I don't remember how Ubuntu 14 deals

I just noticed the following curious behavior when using newhidups with upsdrvctl and two different USB devices: My ups.conf contains two devices, both using newhidups: [belkinusb] driver = newhidups port = auto desc = "Belkin UPS, USB interface" vendorid=050d [mgeusb] driver = newhidups port = auto desc = "MGE UPS, USB

I recently bought a Belkin F6H375 UPS. It connects to the computer via USB. Searching the Internet led me to believe that the megatec_usb driver in nut supports this UPS, however I've been unable to get it to work. I have this in ups.conf: [belkinusb] driver = megatec_usb port = auto desc = "Belkin USB" Here's what happens when I try to use it: ~ #

Hi Charles and thanks for your help. 1. I just re-started the Ubuntu/Android system. This runs a root script including "service nut-server start" followed by the same for nut-client. I can check the status on both and they show as running. I can see expected results running "upsc belkinusb". 2. When I check the results from "netstat -t -n" I am NOT finding

hi i have a belkin ups here some setting chmod 0600 /dev/hiddev0 chown nut:root /dev/hiddev0 linux:/home/sonia # /usr/lib/ups/driver/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No matching USB/HID UPS found Driver failed to start (exit status=1) linux:/home/sonia # /usr/lib/ups/driver/upsdrvctl -u root start

Hi all, I've finally gotten around to setting up the netbook that controls my UPS and I would like to make sure that I've got the metacode correct before configuring nut :) Here's what I've got: Belkin UPS F6C120auUNV * Batteries recently replaced * On battery: 24 port switch, PoE AP, antenna power booster, ADSL modem, MythTV server, 19" monitor * On surge

On Tue, 31 Dec 2019, David White wrote: > ... But it did not actually turn off the UPS at all. The UPS kept > beeping and I had to turn it off manually. > > I thought that NUT would handle this. But perhaps it cannot for my unit? Or > perhaps I have things improperly configured? Any suggestions? Thanks and > happy new year! > ########### /etc/nut/upsmon.conf

Hi Charles; I think its not working yet even though I seem to be getting only one error, but I cannot seem to get upsmon to output the current ups status. So, since I cannot find any manpages (is that a separate package, if so I did not see it in the repo.) about the only error I can get out of it is that it is not listening on localhost:3493. Yet that is specified in the conf files: ene