search for: fahnoetech

...figured in the UI? Do you have it set to go into safe mode after a certain number minutes? Earlier, I was just copying and pasting the contents of some files to Roger but did not change anything. -- Todd Benivegna // todd at benivegna.com On Aug 14, 2020, 8:16 AM -0400, Larry Fahnoe <fahnoe at fahnoetech.com>, wrote: > On Thu, Aug 13, 2020 at 7:46 PM Todd Benivegna <todd at benivegna.com> wrote: > > > So I finally got a test in after I changed my RPi to the master and everything else (including my Synology) to slaves.  Before I did that though, I timed the shutdown of my Synolo...

...ver you get a chance I’d really like to compare notes with someone who has NUT and a Synology to see why the heck mine doesn’t work! ;). I’m also using my Pi as the master like you. Thanks. Todd -- Todd Benivegna // todd at benivegna.com On Aug 14, 2020, 11:55 AM -0400, Larry Fahnoe <fahnoe at fahnoetech.com>, wrote: > On Fri, Aug 14, 2020 at 10:31 AM Todd Benivegna <todd at benivegna.com> wrote: > > > I have not edited a single file, including anything to do with NUT, on the Synology via ssh.... ever. How is yours configured in the UI? Do you have it set to go into safe mode a...

...east on DSM 6.x last time I looked at it), so the main NUT configuration on the NUT master must use these values for slaves: UPS - ups Username - monuser Password - secret Therefore protect the NUT network segment appropriately. --Larry -- Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com Minneapolis, Minnesota www.FahnoeTech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170722/c2b0410b/attachment.html>

Roger, Thanks for the idea to add additional items to the notifyflag. That proved the monitor was indeed working as expected and led me to find that my script had myriad issues when run under the nut user. All remedied now. As I progress, I may well end up migrating to the upssched. As a newbie I was simply following the documented "simple" way described here

...eived this e-mail in error, please notify us immediately and delete it thereafter from your system. Any dissemination, distribution or copying of this e-mail is strictly prohibited. P T?nk p? milj?n innan du skriver ut. [cid:image003.jpg at 01D30310.A4A62BB0] Fr?n: Larry Fahnoe [mailto:fahnoe at fahnoetech.com] Skickat: den 22 juli 2017 15:10 Till: Charles Lepple Kopia: Tomas Larsson; nut-upsuser at lists.alioth.debian.org ?mne: Re: [Nut-upsuser] Compaq R3000h support On Sat, Jul 22, 2017 at 7:48 AM, Charles Lepple <clepple at gmail.com<mailto:clepple at gmail.com>> wrote: I also have n...

On Fri, 22 May 2020, Tom Cooper wrote: > Sadly I am still seeing a loss of communication. I will check the device number to see if it has changed.  > Not sure what else to look at. I guess I could create a corn job to restart the driver multiple times a day.  If there is a command such as upsc for which the output depends on the driver running correctly, then it might be better to run a

...rst to test the protocol via a serial terminal client directly connected to the UPS, and then write some simple code from scratch to implement the protocol and use it for my basic needs. Do you think that is a feasible approach? Ambrogio On Mon, Jul 3, 2017 at 10:17 AM Larry Fahnoe <fahnoe at fahnoetech.com> wrote: > I don't have the Tripp-Lite model that you have, however the NUT HCL > http://networkupstools.org/stable-hcl.html suggests that the SU2200RTXLCD2U > ought to work via USB. Tripp-Lite sometimes uses proprietary serial > cables, so you may need to hunt down a pinout...

Hello I asked Tripplite the serial protocol implemented in the UPS model SU2200RTXLCD2U. The protocol is the 4006, which is not supported by the NUT. I connected my UPS unit to a serial terminal client (both from a Windows machine and a Linux machine), set the communication parameters to those indicated in the protocol spec, and tried to open the communication, unfortunately with no success. I

...workupstools/nut/blob/master/drivers/tripplite_usb.c#L675 > > As a result, the last entry in the FAQ will apply: > http://networkupstools.org/docs/FAQ.html > > -- > Charles Lepple > clepple at gmail > > > > -- Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com Minneapolis, Minnesota www.FahnoeTech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20160525/9001e311/attachment.html>

Roger, I get 4.3.8(1)-release There was good reason, BTW, for the script to NOT fine the journal script on my machine. I had not downloaded it yet. On 7/14/2019 9:06 AM, Roger Price wrote: > On Sun, 14 Jul 2019, David White wrote: > >> ... I saw nothing that looked like a problem with the report save the >> sections <scriptname> "Cannot access <scriptname>.

On Apr 13, 2018, at 3:55 AM, Jon Bendtsen <jon.bendtsen at jonix.dk> wrote: > > On 13/04/2018 07.56, zefanjas wrote: >> Hi, >> is there a command to get a list of connected slaves you can run on the >> nutserver? I want to monitor the slaves and if their are actually >> connected to server. > > if there is no such command in NUT, then on my Debian

So I finally got a test in after I changed my RPi to the master and everything else (including my Synology) to slaves.  Before I did that though, I timed the shutdown of my Synology since it is the slowest slave to shutdown.  It took 40 seconds to shutdown, so I changed HOSTSYNC in upsmon.conf on the master (“Proton”) to 60.  I then did a test ("sudo upsmon -c fsd”). The slaves shutdown, then

On Mon, 10 Aug 2020, Todd Benivegna wrote: > synoups: https://hastebin.com/xexafofiha.bash Wow! What a mess. It looks as if Synology wanted to write their own "NUT", but decided it would be easier to put their ideas in a script when they saw they could use upssched.conf to call it. NUT intends such a script for timer management. Synology use it for general system management.

...re notes with someone who has NUT and a > Synology to see why the heck mine doesn’t work! ;). I’m also using my Pi as > the master like you. Thanks. > > Todd > > -- > > *Todd Benivegna* // todd at benivegna.com > On Aug 14, 2020, 11:55 AM -0400, Larry Fahnoe <fahnoe at fahnoetech.com>, > wrote: > > On Fri, Aug 14, 2020 at 10:31 AM Todd Benivegna <todd at benivegna.com> > wrote: > >> I have not edited a single file, including anything to do with NUT, on >> the Synology via ssh.... ever. How is yours configured in the UI? Do you >> ha...

...d a >> Synology to see why the heck mine doesn’t work! ;). I’m also using my Pi as >> the master like you. Thanks. >> >> Todd >> >> -- >> >> *Todd Benivegna* // todd at benivegna.com >> On Aug 14, 2020, 11:55 AM -0400, Larry Fahnoe <fahnoe at fahnoetech.com>, >> wrote: >> >> On Fri, Aug 14, 2020 at 10:31 AM Todd Benivegna <todd at benivegna.com> >> wrote: >> >>> I have not edited a single file, including anything to do with NUT, on >>> the Synology via ssh.... ever. How is yours configured i...

..._______________________________________________ >> Nut-upsuser mailing list >> Nut-upsuser at lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser >> [1] > > -- > > Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com > Minneapolis, Minnesota www.FahnoeTech.com [2] > > Links: > ------ > [1] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > [2] http://www.FahnoeTech.com -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil at pricom.co...

...r than the tech. UPS unit: Model SMART2200 Model # SM1834 Date code -LW1GE (Nov 1998) Serial number E00321344 So, any opinions about how long one should expect a UPS like this to last or any words of wisdom on how to revive this one? --Larry Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com ?? ? ? ? ? Minneapolis, Minnesota ? ? ? www.FahnoeTech.com

...bluetoothd[592]: Terminating May 24 18:02:02 pi bluetoothd[592]: Stopping SDP server May 24 18:02:02 pi bluetoothd[592]: Exit May 24 18:02:02 pi upsd[992]: mainloop: Interrupted system call May 24 18:02:02 pi upsd[992]: Signal 15: exiting -- Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com Minneapolis, Minnesota www.FahnoeTech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20160525/f4a33f32/attachment-0001.html>

...60 Quick update... > 10.507657 refresh_report_buffer: expected 3 bytes, but got 2 instead > 10.507671 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, > ReportID: 0x0f, Offset: 0, Size: 16, Value: 0 --Larry -- Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com Minneapolis, Minnesota www.FahnoeTech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20160528/7982a943/attachment-0001.html>

On 28.05.2016 19:46, Larry Fahnoe wrote: > On Sat, May 28, 2016 at 11:05 AM, abi <abi at abinet.ru > <mailto:abi at abinet.ru>> wrote: > > However I was unable to shutdown.return it. Maybe protocol is not > fully compatible? > > 0.145757 Initiating UPS shutdown > 0.145760 upsdrv_shutdown... > 0.145763