Re: [Nut-upsuser] [EXTERNAL] AVRX750/500 issues

2020-07-22 Thread Scott Colby
Hi David, thanks for your help with this! My AVR750U is serial 2945CVLOM87C901526. I also have a ticket open with TrippLite support, #00686888, where they advised me that they don't support NUT (understandable) and to try the TrippLite software. I'll take a stab at that to see if the UPS is capable

Re: [Nut-upsuser] [EXTERNAL] AVRX750/500 issues

2020-07-22 Thread David Zomaya
>>>Thanks for chiming in @David Zomaya. Tripp Lite replaced my AVRX550U once >>>thinking that the powering back on was a defective unit, but the replacement >>>does the same thing. The SN on the first one is 2935AVHOM87BB00152. >>> >>>NUT has my model listed as protocol 2010, 2935AVHOM87BB0

[Nut-upsuser] AVRX750/500 issues

2020-07-22 Thread objecttothis
Thanks for chiming in @David Zomaya. Tripp Lite replaced my AVRX550U once thinking that the powering back on was a defective unit, but the replacement does the same thing. The SN on the first one is 2935AVHOM87BB00152. NUT has my model listed as protocol 2010, so that needs to be corrected to

Re: [Nut-upsuser] [EXTERNAL] AVRX750/500 issues

2020-07-22 Thread David Zomaya
For what it's worth, productID should = protocol number. I think objecttothis had 2012 but Scott had 3024. A lot of our smaller standby and line-interactive units recently changed to 302x protocols, hence this post to the development list: https://alioth-lists.debian.net/pipermail/nut-upsdev/202

[Nut-upsuser] AVRX750/500 issues

2020-07-22 Thread objecttothis
I wouldn't be surprised if they both use the same driver. I think they are essentially the same model, but with one having a slightly larger battery. My issue is primarily with the UPS turning back on after having shut off like it should. @Scott Colby if you take a look at the config files I