Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
wmarcolinW

wmarcolin

@wmarcolin
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[HowTo] Using HABridge with Reactor
therealdbT
If you’re like me and still running HABridge to control your devices locally via Alexa, you might need to tweak your endpoints to call Reactor via HTTP. Here’s the best way to do it, IMO: Insert the Reactor Canonical ID (e.g., zwavejs>71-1) into the MapID field, but make sure it’s URL-encoded like this: zwavejs%3E71-1. Then, configure these endpoints as needed: On: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.on Off: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.off Dim: For lights: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/dimming.set?level=${intensity.decimal_percent} For roller shutters: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/position.set?value=${intensity.decimal_percent} Color: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/rgb_color.set_rgb?red=${color.r}&green=${color.g}&blue=${color.b} Just replace [ReactorIP] with your actual IP address. By using these placeholders, you can standardize your endpoints across all devices, making maintenance easier. This setup works with any device mapped under MSR, regardless of the controller (ZWaveJS, Vera, HASS, OpenSprinkler, virtual, MQTT, DynamicEntities, etc.). If you need different calls, just go to the entities, get the action and parameters, and adjust accordingly. Enjoy super fast access to your devices via Alexa! If you're migrating from Vera, the endpoints are (URL-encoded) in a file called device.db, in JSON format, under your config. You'd write a script to align the new endpoints to the new one, if you prefer to do it automatically. YMMV.
How-To
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Genuinely impressed with Zigbee and HA / Reactor
CatmanV2C
Just for the record, in case anyone is following, I'm really rather impressed. I have installed one of these: https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 That's connected (physically) to the VM running on my Synology, with a 2m USB extension. The same host also runs Openluup, Mosquito, HA Bridge. Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions. Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA. https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so... https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt. And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one). A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....) Commended to the house. Thanks for everyone that got me on the right lines. C
Zigbee
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Zigbee2mqtt installed! sytemctl not happy :(
CatmanV2C
Hello oh great ones. After a couple of hours messing with ports and permissions I have Zigbee2mqtt installed and running on my virtual pi Can connect to the front end and everything Odd one though, simply cannot get systemctl to work and the error is, well, unhelpful. The service file is this: [Unit] Description=zigbee2mqtt After=network.target [Service] Environment=NODE_ENV=production Type=notify ExecStart=/usr/local/bin/node index.js WorkingDirectory=/opt/zigbee2mqtt StandardOutput=inherit # Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5) StandardError=inherit WatchdogSec=10s Restart=always RestartSec=10s User=pi [Install] WantedBy=multi-user.target Straight out of the docs with the change to point to my local node install (which we know works as it's the same as the very fine Reactor is using. Running manually pnpm start in /opt/zigbee2mqtt works fine However: catman@openluup:/etc/systemd/system$ sudo systemctl start zigbee2mqtt.service Job for zigbee2mqtt.service failed because the control process exited with error code. See "systemctl status zigbee2mqtt.service" and "journalctl -xe" for details. Which I have catman@openluup:/etc/systemd/system$ sudo systemctl status zigbee2mqtt.service ● zigbee2mqtt.service - zigbee2mqtt Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Tue 2025-12-16 12:32:42 GMT; 4s ago Process: 3093 ExecStart=/usr/local/bin/node index.js (code=exited, status=217/USER) Main PID: 3093 (code=exited, status=217/USER) and -- A start job for unit zigbee2mqtt.service has begun execution. -- -- The job identifier is 17477. Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed to determine user credentials: No such process Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed at step USER spawning /usr/local/bin/node: No such process -- Subject: Process /usr/local/bin/node could not be executed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The process /usr/local/bin/node could not be executed and failed. -- -- The error number returned by this process is ERRNO. Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=217/USER -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit zigbee2mqtt.service has exited. -- -- The process' exit code is 'exited' and its exit status is 217. Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit zigbee2mqtt.service has entered the 'failed' state with result 'exit-code'. Dec 16 12:35:16 openluup systemd[1]: Failed to start zigbee2mqtt. -- Subject: A start job for unit zigbee2mqtt.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit zigbee2mqtt.service has finished with a failure. Which strikes me as very odd. Any blindingly obvious things I'm missing? TIA! C
Zigbee
Any thoughts on which is better
CatmanV2C
Obviously a quiet forum, but perhaps it's time I'm looking at rolling Zigbee into my system, in large part for the Aqara FP300 presence sensors which seem to finally provide a solution to if the wasp is actually in the box. My current set up is as follows: One Debian VM on Synology NAS running: Z-wave Server Open Luup Multi system reactor HA bridge Mosquito MQQT broker This machine has a UZB Z-wave stick connected via the USB port on the NAS Another HAOS VM on the same NAS running HAOS I've got some older Z-wave stuff that I keep around until it fails. I have some Tuya stuff integrated in HA My thought was to get either a SMLIGHT SLZB-06M or an Aqara Hub M2 Integrate them via Zigbee2MQQT (running on the Debian machine) and then expose them in HA so I can continue to automate in MSR. Thoughts on which of those devices wold be preferable long term. Both are POE capable which is good. It also appears I could add a USB dongle to the NAS and expose it to the HAOS machine. Any thoughts from the assembled experts here? TIA C
Zigbee
Single protocol?
CatmanV2C
Another question to the hive mind. Prompted by the fact that I lost yet another z-wave device over the weekend due to a power issue. It looks like z-way server is reporting another device failed (although it's working fine) and message queue is far too long IMHO. Also the failed device has been removed in the expert interface, but still there in the 'normal' one. Sigh. Currently I have z-wave, Tuya, thinking about Zigbee.... Does anyone use one single protocol for everything? Right now I'm feeling that as the z-wave stuff dies, I'm just gonna replace it with something else.... C
General Discussion
HDMI oddness
CatmanV2C
Not really Smart Home stuff, but going to ask as we have smart people... Bear with me on this one. Asking here because of the font of knowledge! For many eek years I have had a Virgin V6 box and a Raspberry Pi running Kodi connected to my TV through a cheap *** HDMI switch. It all worked beautifully but the absolutely critical thing was that the TV remote passed the signals back to the Pi to allow remote control of Kodi. Couple of changes of late: Installed a soundbar on the TV using the ARC (audio return channel). That then turns the soundbar on and off when the TV turns on and off and the TV volume control controls the soundbar volume direct. Everything continues to work Upgraded the software of the Tivo box to Virgin 360. This is literally software only. You get sent a snacky new Bluetooth remote hit 'upgrade' on the screen and off it goes. Now, things are not playing well. Typically when I turn on to watch Kodi the soundbar comes on (as it should) but the TV either puts out sound through its own speakers and the soundbar, or just the soundbar. It's not possible to control the volume of the soundbar through the TV. Also it's not longer possible to control Kodi using the TV remote. If I turn the TV360 box off, i.e. power it down, before turning on to watch Kodi, everything is fine. This makes little to no sense to me. My assumption is that the cheap *** HDMI switch is getting something from the TV360 connection that it didn't used to get when the software was Tivo and that's screwing up the HDMI communications. I'm upgrading the switch to something a little less chap, but wondered if anyone could validate my theory at all? TIA C
General Discussion
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
Oh the joy of pairing
CatmanV2C
When I remember the old days Just added a new Tuya plug (OK so it's cloud) Start to finish, visible in HA and MSR < 30 seconds... C
Vera
Home Assistant Connect ZWA-2 & ZBT-2
therealdbT
Topic thumbnail image
Hardware
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
About
Posts
295
Topics
33
Shares
0
Groups
0
Followers
0
Following
2

Posts

Recent Best Controversial
  • Stop the MSR by an external switch on Hubitat.
    wmarcolinW wmarcolin

    Hi @toggledbits

    Yes, the idea is to stop the reactor, but almost stop it! What I mean is that the Reactor can stop and start working again via an external switch, for example from HE.

    In other words, MSR would not execute actions, it would listen normally and update the status of devices normally, but it would not execute any Rule Sets or Reactions if this external switch were turned off. If you turn it on, everything goes back to working.

    The idea would be to have a dashboard that can turn this switch on or off. Of course, if it is not configured in reactor.yaml, this functionality would not exist.

    Thanks,
    Wilson

    Multi-System Reactor
  • Stop the MSR by an external switch on Hubitat.
    wmarcolinW wmarcolin

    @toggledbits

    Any sugestion boss?

    Thanks

    Multi-System Reactor
  • Stop the MSR by an external switch on Hubitat.
    wmarcolinW wmarcolin

    Use case:

    When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled.

    To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work.

    Then another situation: the water pump system and garden irrigation, another switch.

    In short, I had to create several virtual switches in Hubitat to disable rules in MSR.

    Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR.

    If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR.

    Would it be possible to do something like this? Any recommendations from the experts?

    Multi-System Reactor
  • Set Reaction > Script Action
    wmarcolinW wmarcolin

    @toggledbits said in Set Reaction > Script Action:

    each id in getEntity("groups>dgc_PushableButton_N0").attributes.sys_group.members:
    performAction( id, "x_hubitat_Refresh.refresh", {} )

    EXCELLENT, IT WORKED!!! Thank you very much.

    I was already working on this script, based on the example at the beginning of this discussion, but I was using performOnEntity.

    each id in getEntity('groups>dgc_PushableButton_N0').attributes.sys_group.members: performOnEntity(id, 'x_hubitat_Refresh.refresh')

    Thank you very much for your help. Another lesson learned, and I am already putting more optimizations into practice.

    Multi-System Reactor
  • Set Reaction > Script Action
    wmarcolinW wmarcolin

    @toggledbits

    Sorry, I don't understand, it doesn't work the way it's written below.

    c78b3851-56c0-4d7e-873d-9935042d9555-image.png

    What information do I have to assign to grup_actions, or is it something else?

    Thanks
    Wilson

    Multi-System Reactor
  • Set Reaction > Script Action
    wmarcolinW wmarcolin

    @therealdb

    This feature is really fantastic. I'm changing a lot of rules for it.

    Now you could help me with this one. I need to know if the button is stuck, i.e., if it hasn't returned to zero, and force a refresh.

    The selection rule is already correct, but now I can't understand how to define the Group Action to apply x_hubitatRefresh.refresh.

            "dgc_PushableButton_N0":
          name: DGC PushableButton Not 0
          select:
            - include_capability:
              - x_hubitat_PushableButton
            - exclude_entity:
              - "hubitatC8>2672"  # Alarm Sirene
              - "hubitatC8>2100"  # Remote Adriane
              - "hubitatC8>420"   # Remote Quad
          group_actions: x_hubitat_Refresh
          filter_expression: >
            entity.attributes.x_hubitat_PushableButton.pushed != 0 and
            entity.attributes.x_hubitat_PushableButton.pushed != null

    Could you help me with your experience?

    This is what I want to change.

    6bc1ff1f-4403-4906-b947-f11916b2ab16-image.png

    Only apply refresh, to the button selected by the DynamicGroup.

    Or in this case is Script that I need to create?

    Thanks.

    Multi-System Reactor
  • Set Reaction > Script Action
    wmarcolinW wmarcolin

    @toggledbits

    fe8bb433-b91b-4260-9864-7f3d6074778c-Untitled.jpg

    I don't know what other words to use to describe Reactor! If I had read the entire manual, I wouldn't have posted about Group Action. Now that I've read everything that DynamicGroupController can do, it's impressive.

    I was definitely one of the enthusiasts when this was implemented, and now with this option to take actions, it's wonderful. It's going to simplify a lot of rules for me.

    Thank you very much @t. Every day I'm surprised by the things that can be done in Reactor.

    Multi-System Reactor
  • Set Reaction > Script Action
    wmarcolinW wmarcolin

    @Crille

    Thank you for your comment, but I need this to be executed by an action already within the routines I program in Reactor.

    So using it within the configuration would not help me.

    The selection of devices is indeed within the Dynamic Group, which is perfect, but I was wondering if I could do something like a script, which would require a routine like the one I have today, where I send a list of devices to be turned on, even if they are already on, so I don't have to create a group to analyze the status of each one.

    I want to do something smarter.

    Anyway, thank you, and let's see if we have any other recommendations.

    Multi-System Reactor
  • Set Reaction > Script Action
    wmarcolinW wmarcolin

    Hi

    Use case: possibility of using a script instead of setting up an action in this way.

    4bff09e1-539b-46c8-8c37-090b1b966284-image.png

    If I have a variable that contains the device IDs within the array, could I use a script to execute the powe_switch.on command for the devices in this list?

    b4dfc617-412a-42ff-ae7b-ae8f0d65c39e-image.png

    I tried to understand in the manual (https://reactor.toggledbits.com/docs/Script-Action/) how to use this script feature, but I was unsuccessful. Are there any examples here in the forum of how to use it so I can continue my development?

    Thanks.

    Multi-System Reactor
  • [Solved] Limit HA Entity in MSR
    wmarcolinW wmarcolin

    @toggledbits

    While you're at it, could you add to Santa's list a request for a function that, when given two coordinates, returns the distance between them?

    I'll explain the use case: when Life360 worked on Hubitat, one of the variables was precisely the distance between the device and the point determined as the home. However, as I said, it hasn't worked for a long time.

    This was one of the reasons for installing Home Assistance, which works perfectly, but it doesn't have this information, so I had to do the calculation.

    I know, you're going to say what a horrible thing, what a mess, but it's working.

    I prepared a series of calculations, using the coordinates of my home as a reference, for my phone WIL and my wife's phone ADRI. The phone coordinates come from Life360.

    525b8ca4-86c2-424f-a3c6-6b11aba39730-image.png

    Next, I have the calculations.

    391c3a64-dbf9-4a7d-b01c-2a583a6bc83f-image.png

    So, I have the result.

    36c24be1-f4ec-426e-af61-485de33457de-image.png

    I used this formula Python.

    from math import radians, sin, cos, sqrt, atan2

def haversine(lat1, lon1, lat2, lon2):
    R = 6371  # raio da Terra em km

    dlat = radians(lat2 - lat1)
    dlon = radians(lon2 - lon1)

    lat1 = radians(lat1)
    lat2 = radians(lat2)

    a = sin(dlat/2)**2 + cos(lat1) * cos(lat2) * sin(dlon/2)**2
    c = 2 * atan2(sqrt(a), sqrt(1 - a))

    return R * c  # distância em km

    Thanks.

    Multi-System Reactor
  • [Solved] Limit HA Entity in MSR
    wmarcolinW wmarcolin

    Hi @toggledbits

    As I mentioned, I don't think it's a performance issue. Looking at the memory and processing of the Reactor and HA VM, the consumption is insignificant. I have more than 370 devices between ZWave and ZigBee, the Reactor is connected to a Hubitat C8, Hubitat C7, Zemismart M1, Aqara, and now HA, and it doesn't even affect processing.

    My only desire was to remove elements from the Reactor in Entity that I don't care about. However, this is more a matter of usage habit than performance.

    And by the way, the implementation in the latest version of the link to go directly to the rule or devices is fantastic. You still need to tweak the Entity Widgets for the Entity list. I think that instead of calling by Entity Name, it is calling by Canonical ID, and this is not working. But the idea is fantastic.

    How is Santa's wish list coming along? You could have a post with this list just so we know what's coming down the road at some point.

    Thanks!

    Multi-System Reactor
  • [Solved] Limit HA Entity in MSR
    wmarcolinW wmarcolin

    Hi @toggledbits

    I understand, I know that the system is very robust and supports thousands of interactions, I even imagine that because the two VMs of Reactor and HASS are on the same computer, the speed of communication is enormous.

    So, apart from the overload issue that not have, I'm thinking about the practicality of using it, by removing from the list of HASS entity devices that I'm not interested in viewing in Reactor.

    Looking at the manual, excuse my incompetence, I really couldn't identify how to configure not to load the Entity in Reactor, I made several attempts and I can't remove the devices. Below is my last attempt. If you can help me with the correct configuration.

    
  - id: hass
    enabled: true
    implementation: HassController
    name: Home Assistant System
    config:
      source: 'ws://192.xxx.xxx.xxx:8123'
      access_token: "eyJhbxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxc0N>
      #
      # ignore_cert - If true, suppresses certificate validation when using wss:// (Websocket
      #               with SSL/TLS) and thus allows a self-signed certificate to be used on
      #               the Hass system.
      #ignore_cert: false
      #
      # dump_all_states - This is for troubleshooting. Do not enable unless asked.
      #dump_all_states: false
      exclude_entities:
        - "hass>sensor_sun*"

    Thanks.

    Multi-System Reactor
  • [Solved] Limit HA Entity in MSR
    wmarcolinW wmarcolin

    Hi @toggledbits

    I'm new to HA, and I just finished integrating it with MSR. It was very easy to configure and interact between platforms.

    However, one thing that bothered me is that all HA Entities were sent to MSR, and in my opinion, this generates unnecessary integration overload. I searched the manual and here in the forum for a way to delete everything I don't want to come to MSR, such as all this information from Sun *.

    fbacfe91-6a1f-42c5-a2bf-8179f9bfdef1-image.png

    Is it possible to configure this, as we already do with Vera, for example? And if possible, would using a wildcard such as hass>sun* automatically exclude all other entities of this type?

    Thanks.

    Multi-System Reactor
  • Throttled problem
    wmarcolinW wmarcolin

    @toggledbits

    Looking for a solution, I implement this script.

    #!/bin/bash

# Nome do UPS configurado em /etc/nut/ups.conf
UPS_NAME="TrippLite"

# Comando para verificar o status do UPS
if upsc "$UPS_NAME@localhost" | grep -q "DATA-STALE"; then
    echo "$(date): DATA-STALE detectado. Reiniciando o serviço NUT." >> /var/log/monitor_nut.log
    systemctl restart nut-driver.service
    systemctl restart nut-server.service
    systemctl restart nut-monitor.service
else
    echo "$(date): Serviço funcionando normalmente." >> /var/log/monitor_nut.log
fi

    We'll see if it eases the problem, but here's the situation with the NUT.

    Multi-System Reactor
  • Throttled problem
    wmarcolinW wmarcolin

    @toggledbits

    I removed the crontab stop and restart process with a set time, and then restarted the MSR to follow the new logs, below.

    [latest-25016]2025-01-28T14:28:58.785Z <NUTController:null> Module NUTController v25026
[latest-25016]2025-01-28T14:28:59.438Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.16>
[latest-25016]2025-01-28T14:28:59.444Z <NUTController:INFO> NUTController#nut connected to "192.168.50.8":3493
[latest-25016]2025-01-28T14:28:59.444Z <NUTController:INFO> NUTController#nut setting client username (Reactor) >
[latest-25016]2025-01-28T14:28:59.544Z <NUTController:INFO> NUTController#nut client not yet ready; waiting
[latest-25016]2025-01-28T14:28:59.544Z <NUTController:INFO> NUTController#nut client ready after authentication
[latest-25016]2025-01-28T14:29:00.631Z <NUTController:INFO> NUTController#nut initial query succeeded with 1 ite>
[latest-25016]2025-01-28T14:29:00.688Z <NUTController:INFO> NUTController#nut initializing TrippLite
[latest-25016]2025-01-28T15:04:17.580Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T15:04:17.580Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T15:04:27.602Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T15:04:27.603Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T15:04:37.610Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T15:04:37.610Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T15:04:47.618Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T15:04:47.619Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T15:04:57.682Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T15:04:57.682Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T15:05:07.687Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T15:05:07.687Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T15:05:18.056Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T15:05:18.056Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T15:05:28.059Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T15:05:28.059Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T15:05:38.068Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T15:05:38.068Z <NUTController:CRIT> !DATA-STALE
.
. start the DAT-STALE
.
[latest-25016]2025-01-28T16:59:13.198Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T16:59:23.199Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T16:59:23.200Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T16:59:33.202Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T16:59:33.203Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T16:59:43.213Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T16:59:43.214Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T16:59:53.227Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T16:59:53.227Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T17:00:03.330Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T17:00:03.330Z <NUTController:CRIT> !DATA-STALE
.
. nothing change than I restart the process (
.
#systemctl restart nut-driver.service
#systemctl restart nut-server.service
#systemctl restart nut-monitor.service
.
[latest-25016]2025-01-28T17:00:13.332Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T17:00:13.332Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T17:00:23.336Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T17:00:23.336Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T17:00:33.362Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T17:00:33.363Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T17:00:43.414Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T17:00:43.414Z <NUTController:CRIT> !DRIVER-NOT-CONNECTED
[latest-25016]2025-01-28T17:00:44.544Z <NUTController:NOTICE> NUTController#nut connection closed; attempting re>
[latest-25016]2025-01-28T17:00:44.596Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.16>
[latest-25016]2025-01-28T17:00:44.597Z <NUTController:INFO> NUTController#nut connected to "192.168.50.8":3493
[latest-25016]2025-01-28T17:00:44.597Z <NUTController:INFO> NUTController#nut setting client username (Reactor) >
[latest-25016]2025-01-28T17:00:44.598Z <NUTController:INFO> NUTController#nut client ready after authentication
[latest-25016]2025-01-28T17:00:44.648Z <NUTController:INFO> NUTController#nut initial query succeeded with 1 ite>
[latest-25016]2025-01-28T17:00:54.705Z <NUTController:INFO> NUTController#nut initial query succeeded with 1 ite>
[latest-25016]2025-01-28T17:00:54.748Z <NUTController:INFO> NUTController#nut initializing TrippLite
[latest-25016]2025-01-28T17:28:37.934Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T17:28:37.934Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T17:28:47.942Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T17:28:47.942Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T17:28:57.945Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T17:28:57.946Z <NUTController:CRIT> !DATA-STALE
[latest-25016]2025-01-28T17:29:07.959Z <NUTController:ERR> NUTController#nut failed to get detail for TrippLite:>
[latest-25016]2025-01-28T17:29:07.960Z <NUTController:CRIT> !DATA-STALE
.
. but after 8min DATA-STALE again
.

    When it failed I consulted upsc directly and the answer I got was the one below.

    root@main:/home/wilson/reactor/logs# upsc TrippLite@192.168.50.8
Init SSL without certificate database
Error: Data stale
root@main:/home/wilson/reactor/logs#

    Importantly, in MSR the NUT service does not crash, but it stops updating.

    654abd95-559a-41de-a535-c4ae65f81943-image.png

    See that the device goes into an uninformed/excluded status.

    ee8ca3f8-76e0-4020-8364-5644bc593555-image.png

    I don't think the problem lies with the MSR/NUTConttoler, it's a matter of the NUT itself managing the UPS. I've been in this situation for more than a year and I can't get out of the problem loop, so some time ago I adopted the stop and restart crontab to alleviate the problem.

    Multi-System Reactor
  • Throttled problem
    wmarcolinW wmarcolin

    Hi @toggledbits !!

    I installed the new version, and at the same time created a log file specifically for NUTController, below is what I captured in the first 20 minutes, remembering that every 10 minutes I stop and restart the service to mitigate the problem.

    [latest-25016]2025-01-27T18:42:31.243Z <NUTController:null> Module NUTController v25026
[latest-25016]2025-01-27T18:42:31.840Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-27T18:42:31.848Z <NUTController:INFO> NUTController#nut connected to "192.168.50.8":3493
[latest-25016]2025-01-27T18:42:31.848Z <NUTController:INFO> NUTController#nut setting client username (Reactor) and password
[latest-25016]2025-01-27T18:42:31.887Z <NUTController:INFO> NUTController#nut client ready after authentication
[latest-25016]2025-01-27T18:42:31.960Z <NUTController:INFO> NUTController#nut initial query succeeded with 1 items returned
[latest-25016]2025-01-27T18:42:32.007Z <NUTController:INFO> NUTController#nut initializing TrippLite
[latest-25016]2025-01-27T18:50:01.750Z <NUTController:NOTICE> NUTController#nut connection closed; attempting reconnect...
[latest-25016]2025-01-27T18:50:01.808Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-27T18:50:01.810Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-27T18:50:01.811Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (1 fails)
[latest-25016]2025-01-27T18:50:03.811Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-27T18:50:03.812Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-27T18:50:03.812Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (2 fails)
[latest-25016]2025-01-27T18:50:05.897Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-27T18:50:05.898Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-27T18:50:05.911Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (3 fails)
.
. repeat same fail 4....28
.
[latest-25016]2025-01-27T18:50:58.732Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-27T18:50:58.733Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-27T18:50:58.734Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (29 fails)
[latest-25016]2025-01-27T18:51:00.740Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-27T18:51:00.741Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-27T18:51:00.742Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (30 fails)
[latest-25016]2025-01-27T18:51:02.762Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-27T18:51:02.764Z <NUTController:INFO> NUTController#nut connected to "192.168.50.8":3493
[latest-25016]2025-01-27T18:51:02.764Z <NUTController:INFO> NUTController#nut setting client username (Reactor) and password
[latest-25016]2025-01-27T18:51:02.764Z <NUTController:INFO> NUTController#nut client ready after authentication
[latest-25016]2025-01-27T18:51:02.826Z <NUTController:INFO> NUTController#nut initial query succeeded with 1 items returned
[latest-25016]2025-01-27T18:51:02.875Z <NUTController:INFO> NUTController#nut initializing TrippLite
[latest-25016]2025-01-27T19:00:01.389Z <NUTController:NOTICE> NUTController#nut connection closed; attempting reconnect...
[latest-25016]2025-01-27T19:00:01.440Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-27T19:00:01.440Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-27T19:00:01.441Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (1 fails)
[latest-25016]2025-01-27T19:00:03.441Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-27T19:00:03.444Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-27T19:00:03.445Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (2 fails)
[latest-25016]2025-01-27T19:00:05.454Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-27T19:00:05.455Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-27T19:00:05.462Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (3 fails)
.
. repeat same fail 4....28
.
[latest-25016]2025-01-27T19:00:58.245Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-27T19:00:58.246Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-27T19:00:58.246Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (29 fails)
[latest-25016]2025-01-27T19:01:00.246Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-27T19:01:00.248Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-27T19:01:00.248Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (30 fails)
[latest-25016]2025-01-27T19:01:02.250Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-27T19:01:02.250Z <NUTController:INFO> NUTController#nut connected to "192.168.50.8":3493
[latest-25016]2025-01-27T19:01:02.250Z <NUTController:INFO> NUTController#nut setting client username (Reactor) and password
[latest-25016]2025-01-27T19:01:02.251Z <NUTController:INFO> NUTController#nut client ready after authentication
[latest-25016]2025-01-27T19:01:02.310Z <NUTController:INFO> NUTController#nut initial query succeeded with 1 items returned
[latest-25016]2025-01-27T19:01:02.367Z <NUTController:INFO> NUTController#nut initializing TrippLite
    Multi-System Reactor
  • Throttled problem
    wmarcolinW wmarcolin

    @toggledbits download and test now.

    Multi-System Reactor
  • Throttled problem
    wmarcolinW wmarcolin

    @toggledbits hi!

    This NUT UPS issue is something I've been unable to get to work perfectly for months, not to mention year. I even posted a message to you recently.

    I tried to use an old solution from the HE community instead of the MSR solution. The information it returns is much simpler, I had to add attributes to the drive, but the problem turns out to be the same, the NUT stops working, the communication between the UPS and the VM where the NUT is located is not stable. HE upsd drive result: Satale date.

    dev:1572025-01-24 08:21:16.586 PMinfo
connected to upsd on 192.168.50.8:3493 - monitoring TrippLite every 30 seconds
dev:1572025-01-24 08:21:01.183 PMinfo
connected to upsd on 192.168.50.8:3493 - monitoring TrippLite every 30 seconds
dev:1572025-01-24 08:20:31.149 PMerror
telnet connect error: java.net.ConnectException: Connection refused (Connection refused)
dev:1572025-01-24 08:20:01.110 PMinfo
disconnected from upsd
dev:1572025-01-24 08:20:00.082 PMerror
telnet status: send error: Broken pipe (Write failed)
dev:1572025-01-24 08:11:15.553 PMinfo
connected to upsd on 192.168.50.8:3493 - monitoring TrippLite every 30 seconds
dev:1572025-01-24 08:10:45.514 PMerror
telnet connect error: java.net.ConnectException: Connection refused (Connection refused)
dev:1572025-01-24 08:10:30.421 PMerror
telnet connect error: java.net.ConnectException: Connection refused (Connection refused)
dev:1572025-01-24 08:10:00.277 PMinfo
disconnected from upsd
dev:1572025-01-24 08:10:00.252 PMerror
telnet status: receive error: Stream is closed
dev:1572025-01-24 08:10:00.228 PMwarn
upsd: Stale data
dev:1572025-01-24 08:10:00.216 PMwarn
upsd: Stale data
dev:1572025-01-24 08:10:00.203 PMwarn
upsd: Stale data
dev:1572025-01-24 08:10:00.122 PMwarn
upsd: Stale data
dev:1572025-01-24 08:10:00.111 PMwarn
upsd: Stale data
dev:1572025-01-24 08:10:00.098 PMwarn
upsd: Stale data
dev:1572025-01-24 08:10:00.069 PMwarn
upsd: Stale data
dev:1572025-01-24 08:09:30.112 PMwarn
upsd: Stale data
dev:1572025-01-24 08:09:30.101 PMwarn
upsd: Stale data

    In other words, after switching from MSR to HE control, the problem continues, changing the error Throttled to ECONNREFUSED.

    Making a new test, returning to the MSR's NUTControl configuration below, with the same parameters as the HE drive.

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

    The error.log log on MSR is:

    [latest-25016]2025-01-25T02:10:03.776Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-25T02:10:05.800Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-25T02:10:07.807Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-25T02:10:07.815Z <Controller:ERR> Controller NUTController#nut is off-line!
[latest-25016]2025-01-25T02:10:09.907Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-25T02:10:11.924Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-25T02:10:13.927Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-25T02:10:15.939Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-25T02:10:18.124Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-25T02:10:20.128Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-25T02:10:22.150Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-25T02:10:24.172Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-25T02:10:26.182Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]

    IMPORTANT, even with this error log, the NUT control in the MSR does not stop working, it persists until it manages to communicate and collect the data, but this error scenario overloads the MSR.

    Perhaps the time solution indicated by @tunnus could help.

    In addition, parts of the ro reactor.log:

    [latest-25016]2025-01-25T02:06:46.777Z <Structure:INFO> Structure#1 loading controller interface nut (NUTController)
[latest-25016]2025-01-25T02:06:46.779Z <NUTController:null> Module NUTController v24303
[latest-25016]2025-01-25T02:06:46.779Z <Controller:INFO> Loaded NUTController version "0.1.24303"; Patrick Rigney/Kedron Holdings LLC <patrick@toggledbits.com> https://reactor.toggledbits.com/docs/NUTC>
[
.
.
[latest-25016]2025-01-25T02:06:46.847Z <Structure:INFO> Starting controller NUTController#nut
.
.
[latest-25016]2025-01-25T02:06:47.394Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "1/24/2025 9:06:47 PM" (TZ offset -300 mins from UTC)
[latest-25016]2025-01-25T02:06:47.395Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-25T02:06:47.397Z <HubitatController:NOTICE> HubitatController#hubitatC7 performing initial connection and inventory
[latest-25016]2025-01-25T02:06:47.398Z <HubitatController:NOTICE> HubitatController#hubitatC8 performing initial connection and inventory
[latest-25016]2025-01-25T02:06:47.405Z <NUTController:INFO> NUTController#nut connected
[latest-25016]2025-01-25T02:06:47.455Z <NUTController:INFO> NUTController#nut setting client username (Reactor) and password
[latest-25016]2025-01-25T02:06:47.460Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.50.9
[latest-25016]2025-01-25T02:06:47.511Z <Controller:NOTICE> Controller NUTController#nut is now online.
[latest-25016]2025-01-25T02:06:47.511Z <NUTController:INFO> NUTController#nut client ready
[latest-25016]2025-01-25T02:06:47.516Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.50.133
.
.
[latest-25016]2025-01-25T02:10:03.774Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-25T02:10:03.776Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-25T02:10:03.776Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (1 fails)
[latest-25016]2025-01-25T02:10:03.777Z <NUTController:NOTICE> NUTController#nut connection closed
[latest-25016]2025-01-25T02:10:03.777Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (1 fails)
.
.
[latest-25016]2025-01-25T02:10:05.799Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-25T02:10:05.800Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-25T02:10:05.801Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (2 fails)
[latest-25016]2025-01-25T02:10:05.801Z <NUTController:NOTICE> NUTController#nut connection closed
[latest-25016]2025-01-25T02:10:05.802Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (2 fails)
[latest-25016]2025-01-25T02:10:07.803Z <NUTController:NOTICE> NUTController#nut starting NUT client with "192.168.50.8":3493; waiting for ready...
[latest-25016]2025-01-25T02:10:07.807Z <NUTController:ERR> NUTController#nut unable to establish communication with "192.168.50.8":3493: [Error] connect ECONNREFUSED 192.168.50.8:3493 [-]
[latest-25016]2025-01-25T02:10:07.815Z <Controller:ERR> Controller NUTController#nut is off-line!
[latest-25016]2025-01-25T02:10:07.816Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (3 fails)
[latest-25016]2025-01-25T02:10:07.829Z <NUTController:NOTICE> NUTController#nut connection closed
[latest-25016]2025-01-25T02:10:07.830Z <NUTController:INFO> NUTController#nut recycling/reconnecting in 2000ms (3 fails)

    IN SUMMARY:

    • the connection parameters IP, login and password are correct, in the log you can see that it connects.
    • NUTControl works until it starts a sequence of failures.
    • In order to re-establish the service, I put a stop and start process in the crontab every 10 minutes, the problem is that it can remain idle all this time and fail.
    • I've tried changing all the synchronization and reading times in the NUT parameters, I've even increased them to 90 seconds for data collection(ie. POLLFREQALERT 30 // HOSTSYNC 30), and it doesn't change the scenario, at a certain point there's saturation and the UPS stops responding.2

    So I think the idea of making the MSR have a different collection time, longer than other devices, can at least reduce the error log, but it doesn't solve the problem.

    Thanks.

    Multi-System Reactor
  • Throttled problem
    wmarcolinW wmarcolin

    @tunnus hi!
    I like what I've read, I think it could be a solution, but it's still not very clear how to configure it, since I want to save various attributes of the device.
    I'll try it out and post the result here for you, but it could be a way forward.
    Thank you.

    Multi-System Reactor
  • Login
  • Don't have an account? Register
  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved