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
[Reactor] Help with screne controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
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
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
Expose MSR entities
CatmanV2C
Probably a really dumb question. Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great. Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly. Any thoughts? Apologies if the ask is not clear/ TIA C
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
Multi-System Reactor
Little Bobby tables...
CatmanV2C
...is back.... https://arstechnica.com/google/2025/08/researchers-use-calendar-events-to-hack-gemini-control-smart-home-gadgets/?utm_source=facebook&utm_medium=social&utm_campaign=dhfacebook&utm_content=null&fbclid=IwY2xjawMBq-pleHRuA2FlbQIxMQABHlSqIalzbz1IxcJFzlw8GBE6nC3FwvxcHgR370nJhogU6JjqbmRxG-lysqgh_aem_lx9XboYFKw9tpHnedGQKUA C
General Discussion
Home Assistant Voice TTS is Easy
toggledbitsT
Topic thumbnail image
Home Assistant
Play Audio through Home Assistant Voice Unit
toggledbitsT
Topic thumbnail image
Home Assistant
Home Assistant Voice
CatmanV2C
Has anyone had a play with the local voice control for HA? I've got one on order because... https://www.home-assistant.io/voice-pe/ C
Home Assistant
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API.
Multi-System Reactor
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can't customize home page
G
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page. Once logged back in I can no longer remove errant panes nor is the + available to add new ones. Brave Browser v1.80.122 (Jul 16, 2025) What have I done?! Will check other browsers on my M1. UPDATE: Safari exhibits same behaviour. I've tried both sans last-four public key entry and with - no change.
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Wiring Samotech SM308-S into light fitting
F
Hi Smart Home Community. I have used a Sonos inline WiFi switch to make one of my light fittings smart, but it requires a hard reset for WiFi changes, plus it isn't zigbee compatible, which means I can't use the Hue app to control it with the rest of the lights. To that end I bought a Samotech SM308-S as it is recommended as the better than the Sonos equivalent. I am however not exactly sure how to wire it in. The manual is available here Can anyone help me by clarifying which ports I need to use, and whether I should be using the live or switched live line for live etc. I will be keeping using standard switches for a while, although hope to upgrade to tap dials once I have all the fittings upgraded. Thanks
Hardware
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