DynamicGroupController updating members issue

[toggledbits]

If you look at the error messages being reported by HubitatController, you can see it is not able to talk to the hub. What do the startup messages for HubitatController look like? Something really does not seem right network-wise with either your host or your hub.

Let's clear a few baseline things out of the way.

1. Post the first 20 lines of Reactor startup messages.
2. Run npm ls in your Reactor directory and post the output.
3. From the Hubitat GUI, post the version number of your Hubitat firmware.
4. Post your HubitatController config

[wmarcolin]

1. Post the first 20 lines of Reactor startup messages

[latest-26177]2026-06-28T21:34:59.107Z <app:null> Reactor build latest-26177-3f86f4af starting on v24.17.0 /usr/bin/node
[latest-26177]2026-06-28T21:34:59.107Z <app:null> Process ID 1679 user/group 1000/1000; bare-metal; platform linux/x64 #124-Ubuntu SMP PREEMPT_DYNAMIC Tue May 26 13:00:45 UTC 2026; locale en_US>
[latest-26177]2026-06-28T21:34:59.107Z <app:null> Basedir /home/wilson/reactor; data in /home/wilson/reactor/storage
[latest-26177]2026-06-28T21:34:59.107Z <app:null> NODE_PATH=/home/wilson/reactor
[latest-26177]2026-06-28T21:34:59.127Z <app:null> Resolved timezone=America/Panama, environment TZ=(undefined); offset minutes from UTC=-300
[latest-26177]2026-06-28T21:34:59.128Z <default:null> Module i18n v26144
[latest-26177]2026-06-28T21:34:59.128Z <app:null> Configured locale (undefined); selected locale(s) en_US.UTF-8
[latest-26177]2026-06-28T21:34:59.137Z <app:null> Loaded locale en-US for en-US
[latest-26177]2026-06-28T21:34:59.137Z <app:null> Local date/time using configured timezone and locale formatting is "6/28/2026, 4:34:59 PM"
[latest-26177]2026-06-28T21:34:59.139Z <Structure:null> Module Structure v26094
[latest-26177]2026-06-28T21:34:59.140Z <Capabilities:null> Module Capabilities v24312
[latest-26177]2026-06-28T21:34:59.147Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 26146 revision 1
[latest-26177]2026-06-28T21:34:59.156Z <Plugin:null> Module Plugin v25141
[latest-26177]2026-06-28T21:34:59.174Z <Timer:null> Module Timer v25330
[latest-26177]2026-06-28T21:34:59.174Z <TimerBroker:null> Module TimerBroker v26164
[latest-26177]2026-06-28T21:34:59.175Z <Entity:null> Module Entity v26167
[latest-26177]2026-06-28T21:34:59.177Z <Controller:null> Module Controller v26150
[latest-26177]2026-06-28T21:34:59.178Z <AlertManager:null> Module AlertManager v26135
[latest-26177]2026-06-28T21:34:59.184Z <default:null> Module Ruleset v25283
[latest-26177]2026-06-28T21:34:59.185Z <default:null> Module Rulesets v25141
[latest-26177]2026-06-28T21:34:59.190Z <GlobalExpression:null> Module GlobalExpression v25341
[latest-26177]2026-06-28T21:34:59.199Z <Predicate:null> Module Predicate v26138
[latest-26177]2026-06-28T21:34:59.201Z <Rule:null> Module Rule v26144
[latest-26177]2026-06-28T21:34:59.202Z <GlobalReaction:null> Module GlobalReaction v25292
[latest-26177]2026-06-28T21:34:59.202Z <Engine:null> Module Engine v26149
[latest-26177]2026-06-28T21:34:59.208Z <httpapi:null> Module httpapi v26175
[latest-26177]2026-06-28T21:34:59.221Z <wsapi:null> Module wsapi v26175
[latest-26177]2026-06-28T21:34:59.222Z <app:NOTICE> Starting Structure...

2. npm ls

root@reactor:/home/wilson/reactor# npm ls
reactor-multi-system@1.6.3-26177 /home/wilson/reactor
├── @eslint/js@10.0.1
├── @fontsource/open-sans@5.2.7
├── @influxdata/influxdb-client@1.35.0
├── @popperjs/core@2.11.8
├── body-parser@2.2.2
├── bootstrap-icons@1.13.1
├── bootstrap@5.3.8
├── devalue@5.8.1
├── digest-fetch@2.0.3
├── diskusage-ng@1.0.4
├── eslint@10.4.1
├── express@5.2.1
├── form-data@4.0.5
├── globals@17.6.0
├── gridstack@12.6.0
├── javascript-obfuscator@4.2.2
├── jquery-ui@1.14.2
├── jquery@3.7.1
├── js-yaml@4.2.0
├── node-fetch@2.7.0
├── node-stream-zip@1.15.0
├── nodemailer@7.0.13
├── ping@1.0.0
├── serve-static@2.2.1
├── showdown@2.1.0
├── uuid@11.1.1
└── ws@7.5.11

3. Hubitat version

4. HubitratController

  - id: hubitat
    enabled: true
    implementation: HubitatController
    name: Hubitat Elevation System
    config:
      # Copy the entire URL from the Maker API app page on your Hubitat UI. A quick, easy way is to
      # right-click the "Get All Devices" link and choose "Copy link location", the paste it below.
      source: "http://192.168.1.15/apps/api/8/devices?access_token=e6d0afa6-caad-4f01-a0f3-e27bb8098221"
      #
      # dump_all_devices - This is for troubleshooting. Do not enable unless asked.
      dump_all_devices: false
      # OPCIONAL TEMPORIZADOR ENTRE ACOES - 0,500s entre acoes - ou 2 acoes por segundo
      action_pace: 500
      warn_unresponsive: true
      probe_device: 7
      probe_action: x_hubitat_Refresh.refresh

Thanks.

[toggledbits]

OK. That all looks good. I upgraded my hub to 2.5.0.159, and it works fine. I'm just not seeing any of the issues you are having here. The only things I can suggest at this point:

1. Reboot your hub
2. If that doesn't resolve it, delete your Maker API instance on the hub and create a new one; update Reactor's configuration to reflect the new app ID and access token.

[toggledbits]

I'VE GOT IT!!!! Stand by... don't do anything more yet...

[toggledbits]

OK. Here it is... I switched my nodejs to the same v24.17 you are using... and my system broke! Same behavior as yours.

Upgrade your nodejs to v24.18. Whatever was broken in 17 seems to have been fixed for 18.

[wmarcolin]

Upgrade DONE

root@reactor:/home/wilson# node -v
v24.18.0
root@reactor:/home/wilson# npm -v
11.16.0
root@reactor:/home/wilson#

New roboot... all ok

New sequence stop start

root@reactor:/home/wilson# systemctl stop reactor
root@reactor:/home/wilson# systemctl start reactor

PERFECT!!!!!!

Additional test perfect too!!!

[toggledbits]

Ha!

And... it's a known regression, with a specific fix applied to v24.18, so confirms all.

Onward!!!

[wmarcolin]

Shouldn't there be a release note for this update to version 26177 regarding the Node.js version?

Because when I performed the update, that’s when I noticed this Mode issue—actually, it was already happening before, I’m sure, when I updated Hubitat—but it became more apparent because, as I showed in this and other posts (like the one about the HTTP query), I started getting various communication errors with Hubitat, such as loss of connection and timeouts.

And now everything has disappeared.

I’m still dealing with an issue involving Telegram, which I reported in the other dedicated chat.

[toggledbits]

@wmarcolin I'm still looking at your Telegram issue. Now that I know nodejs v24.17 is a problem, I will post a note for it. Apparently the same change that broke v24 was also made to v22, so I'm trying to identify/confirm that version as well.

[wmarcolin]

Wow, what a headache. I don't know if this is also related to the Node.js issue, but I just added another scenario that I'm now seeing in the log—an INFO warning for a device that doesn't exist. I don't know if it's related. I'm going through the entire error log and reactor.log to see if I can spot anything else unusual in the information.