Ooops - Deleted Reactor Ex Machina II

[Andr]

@toggledbits
So, back from vacation so time to take another shot at this

npm list:

C:\reactor\ext\NUTController>npm list
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
reactor-nutcontroller@0.1.22305 C:\reactor\ext\NUTController
`-- node-nut@1.0.3

NutController config

  - id: nut
    implementation: NUTController
    enabled: true
    #name: Eddie UPS NUTController
    config:
      server: 22.33.44.11        # modify the IP address as needed
      port: 3493              # optional, default shown
      username: "***"      # optional, no user auth if not set
      password: "***"  # optional, must be specified if username is used

[toggledbits]

Try commenting out the username from config. Authentication isn't needed for the queries being used.

[Andr]

@toggledbits
Yep, that did it
Thanks once again @toggledbits

Any thougts about getting more System Info into MSR by the way?
This got me thinking on another possible solution. Reactor already monitors "System Memory" "Uptime" and so on, so maybe it also could monitor Powersource, Battery Level, Charging State? Then let Reactor react with its magic

[toggledbits]

Hmmm... are you (mis)understanding the way NUTController publishes its data? It publishes UPS info on an entity for each UPS that NUT reports. Here, for example, is the data for a test "dummy" UPS that one can configure in NUT:

battery_maintenance.charging=false
battery_maintenance.rechargeable=true
battery_maintenance.replace=true
battery_power.level=0.2
battery_power.since=1692217178132
power_source.source="battery"
x_nut_ups.battery_charge="20"
x_nut_ups.battery_charger.status="discharging"
x_nut_ups.battery_date.maintenance="05/01/2022"
x_nut_ups.device_mfr="Dummy Manufacturer"
x_nut_ups.device_model="Dummy UPS"
x_nut_ups.device_type="ups"
x_nut_ups.driver_name="dummy-ups"
x_nut_ups.driver_parameter.mode="dummy"
x_nut_ups.driver_parameter.pollinterval="2"
x_nut_ups.driver_parameter.port="/etc/nut/dummy.seq"
x_nut_ups.driver_parameter.synchronous="no"
x_nut_ups.driver_version="2.7.4"
x_nut_ups.driver_version.internal="0.14"
x_nut_ups.input_voltage=1580
x_nut_ups.ups_mfr="Dummy Manufacturer"
x_nut_ups.ups_model="Dummy UPS"
x_nut_ups.ups_status="OB LB"

So you can see it's reporting battery state, power level, current power source, etc.

Or are you asking for something else and I'm not getting it?

[Andr]

@toggledbits
No, I get how NutController works. So far at least...

But when I got stuck several times trying to set up NUT I almost gave up. At the same time I remembered seeing some System Info in MSR and if could find data about battery level, charging and so on I would not even need the NUT Installation.
And that would be a big bonus for me as I realize that when my NUT installation fails one day it would take me long time to figure it out and also one less process/config to handle.

And from System Info I assume we could get info about temperatures, storage levels, fan speeds and so on?
This could be used to send warning notifications from MSR.

So yes, I was asking something else that come up in my head when I tried to find another way than using NUT.