<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Jun 3, 2015, at 11:45 AM, Simone Severini <<a href="mailto:severini.simone@gmail.com">severini.simone@gmail.com</a>> wrote:<br><div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi everybody!<div>It has been a journey but I almost manage to make my UPS properly communicate.</div><div><br></div><div>This is the config:</div><div><br></div><div>UPS Mecer/Mustek 2000 VA connected via USB with blazer_usb driver. </div><div>MASTER Raspberry PI-1 </div><div>SLAVE Raspberry PI-2 </div><div>SLAVE iMac OSX 10.10.3 </div><div><br></div><div>I can get access to the UPS from any of the three devices successfully.</div><div><br></div><div>Problems:</div><div>1. When I launch <font color="#000080" face="Courier New, Courier, monospace"><span style="line-height:1">/usr/local/ups/sbin/upsmon -c </span><span style="line-height:13px">fed</span><span style="line-height:1"> </span></font>for testing I see Rasp-2 Slave going down, Rasp-1 going down, iMac completely ignoring and not receiving any broadcast message on the terminal then brutally killed as the UPS auto shutdown.</div></div></blockquote><div dir="ltr"><div><br></div><div>If you search for 'upsmon' in /var/log/system.log on the iMac, does it appear to be logged in to upsd on the master?</div><div><br></div><div>My Mac has a local UPS, so I haven't looked into whether upsmon properly reconnects after sleep.</div><div><br></div></div><blockquote type="cite"><div dir="ltr"><div>2. When I have done a live test, the Master Rasp never intercepted any FLAG from UPS and UPS just died but halting just RASP-1 properly (connected via cable). iMac ignored the whole procedure.</div></div></blockquote><div><br></div><div>You didn't mention which version of NUT you are using, but for recent versions, both the blazer_usb and nutdrv_qx drivers can be configured to generate their own LB signal based on runtime or percent charge. See the documentation for 'ignorelb' in ups.conf.</div><br><blockquote type="cite"><div dir="ltr"><div>3. Is there any way to intercept which type of flag message my UPS sends (log files) to upsmon?</div></div></blockquote><div dir="ltr"><div><br></div><div>If you run upsmon with '-DDD', it will log changes to stderr. Another '-D' should log each poll cycle regardless of whether status has changed.</div><div><br></div><div>Another option is to run upslog to see the rate of discharge when the UPS is on battery. If the charge is falling faster than you expect, the battery may be dead, or the UPS may need to be recalibrated. This may help with the previous question.</div><div><br></div></div><blockquote type="cite"><div dir="ltr"><div>4. I need to halt manually a linux based NAS via SSH. What is the best way (upsched or a script that parses battery.charge and takes decision independently from NUT).</div></div></blockquote><br></div><div>It depends what you want the trigger to be. You can use upssched to power down after a certain amount of time on battery, or when the low battery flag is sent. Either way, you will probably need to ensure that the UPS shuts off its outlets momentarily after the NAS has received the shutdown signal, especially when the power comes back before the UPS battery is depleted.</div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px;"><div>-- </div><div>Charles Lepple</div><div>clepple@gmail</div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br></body></html>