If you already have them i a dynamic group you could perform power_switch.on on that group as an Entity action. Or if the devices should do different actions on/dimming etc, you could create a Global Reaction that does what you specify and simply run that as Set Reaction.

Edit: I confused Script action with Shell command and have not tried Script action but my guess would be performAction(entity_id, action, args) if you really want to do it in a script rather than directly on the group Entity.

@CatmanV2 My script requires Powershell, Pushover, static WAN IP or dynDNS on your router, remote access to router and preferably a static IP on the remote host running the script (to restrict router remote access to that IP). If that fits you I sure can share it.

Kids! They will let you know if internet is down

Joke aside I don't know any notification service that runs locally so I'm checking it from the outside (work) by a scheduled script that open/close a socket to my router every minute and send a pushover notification if it fails.

Thank you! toggle.toggle is back in business.

Sorry I missed that, it’s a bare metal install.

So the difference is the new serviceId urn:upnp-org:serviceId:DoorLock1 called by "super" vs the old urn:micasaverde-com:serviceId:DoorLock1.

I tried to manually use them both in a browser to openLuup, even though both calls get OK in response, the only one actually opens the lock is the old serviceId urn:micasaverde-com:serviceId:DoorLock1

Calling it in a browser directly to my Vera Secure (not openLuup) with serviceId urn:upnp-org:serviceId:DoorLock1 I get ERROR: Invalid Service

After upgrade from 24366 to 25016 toggle on Vera (openLuup) lock entity doesn't seem to work.

VeraController log level 5
24366:

[latest-24366]2025-01-20T20:26:49.724Z <VeraController:INFO> VeraController#vera perform action toggle.toggle on Lock#vera>device_10016 with [Object]{  }
[latest-24366]2025-01-20T20:26:49.725Z <VeraController:5:VeraController.js:514> [VeraController:verarequest] requesting http://127.0.0.1:3480/data_request?id=action&serviceId=urn%3Amicasaverde-com%3AserviceId%3ADoorLock1&action=SetTarget&newTargetValue=0&DeviceNum=10016&output_format=json&_r=1737404809725 ([Object]{  })

25016:

[latest-25016]2025-01-20T20:30:25.457Z <VeraController:INFO> VeraController#vera perform action toggle.toggle on Lock#vera>device_10016 with [Object]{  }
[latest-25016]2025-01-20T20:30:25.458Z <VeraController:5:VeraController.js:1210> VeraController#vera no configured implementation for toggle.toggle on Lock#vera>device_10016; calling super
[latest-25016]2025-01-20T20:30:25.458Z <VeraController:INFO> VeraController#vera perform action lock.set on Lock#vera>device_10016 with [Object]{ "state": false }
[latest-25016]2025-01-20T20:30:25.461Z <VeraController:5:VeraController.js:1255> VeraController#vera sending action request [Object]{ "newTargetValue": "0", "DeviceNum": 10016, "id": "action", "serviceId": "urn:upnp-org:serviceId:DoorLock1", "action": "SetTarget" }
[latest-25016]2025-01-20T20:30:25.461Z <VeraController:5:VeraController.js:515> [VeraController:verarequest] requesting http://127.0.0.1:3480/data_request?newTargetValue=0&DeviceNum=10016&id=action&serviceId=urn%3Aupnp-org%3AserviceId%3ADoorLock1&action=SetTarget&output_format=json&_r=1737405025461 ([Object]{  })
[latest-25016]2025-01-20T20:30:25.463Z <VeraController:NOTICE> VeraController#vera action lock.set([Object]{ "state": false }) on Lock#vera>device_10016 succeeded

I tried to log an issue in Mantis Bug Tracker but I can't log in anymore?

Have you considered Reactor - Multi-hub Automation version?
If not I strongly recommend this path for your automations as it has controllers for both Home Assistant and Vera.
You can still use HA as UI but do all logic in Reactor Multi-hub, no learning curve when you are familiar with Reactor for Vera, you can import your Reactor for Vera into Reactor Multi-hub and set sensor data and variables directly to HA entities.

I'm getting the same on Ubuntu bare metal latest- 24366, both in chrome and edge on Windows.
TypeError: this.editReaction is not a function
at HTMLButtonElement.<anonymous> (http://[ip]:8111/reactor/en-US/lib/js/reactor-ui-reactions.js:445:22)

Yes, that did it! Thanks

I can't find any package-lock.json and this is the output of npm ls

reactor-multi-system@1.3.0-24293 /home/homebridge/reactor
├── @influxdata/influxdb-client@1.22.0
├── @mdi/font@7.4.47
├── @popperjs/core@2.11.6
├── body-parser@1.20.1
├── bootstrap-icons@1.11.3
├── bootstrap@5.2.0
├── digest-fetch@2.0.3
├── diskusage-ng@1.0.2
├── express@4.17.2
├── feather-icons@4.28.0
├── font-awesome@4.7.0
├── gridstack@10.3.1
├── jquery-ui@1.14.0
├── jquery@3.7.1
├── js-yaml@4.1.0
├── node-fetch@2.6.7
├── node-stream-zip@1.15.0
├── nodemailer@6.8.0
├── serve-static@1.15.0
├── uuid@10.0.0
└── ws@7.5.9

@toggledbits said in Dark Mode not Working - 24293:

bootstrap.Tooltip.VERSION — the browser should answer 5.3.3

Hm I'm getting 5.2.0 in both newly updated browsers.

I'm getting the same issue even after running npm i --no-save --no-package-lock --omit dev, also tried npm run deps
Bare metal 24293 running on Ubuntu Server 22.04.5 LTS
Hard refreshed browser Chrome/Edge on Windows

What am I missing here?

I have a Sonoff NSPanel connected to HASS via NSPanel_HA_Blueprint in the hallway where the physical buttons are remapped from the relays to just publish MQTT messages to left or right garage door, appreciated by the whole family. Weather and QR code for guest WiFi also used by some but the rest is just for fun and as @toggledbits said, more of a dashboard rather than a scene controller but it was mentioned

We have Xiaomi Aqara Mini Switches in each bathroom/toilet for manual override of the extraction fan if needed.

My only Shelly i3 is connected to a cheap dumb twilight switch so Reactor can control which lights to turn on/off rather than the actual relay.

We have some IKEA Tradfri wireless dimmers, I had an idea to use one for manual start/stop of our Wallbox charger but it never happened as we found ourself use Siri for that when needed.

It's the same for dimming.set and power_switch.set all .set, an entity rebuild solves those too with 24162.

(@toggledbits Mantis ID 372)

Yep, all warnings gone! Thank you for all your work!

Ah yes, one for openLuup and one for Mosquitto

Strange! I wonder what’s causing that in my setup then as it’s the integrated templates as well.

Looks like MQTTController 24159 solved it. I don't see any errors or warnings in the log after a restart, except all of these but I quess that's normal?

<MQTTController:WARN> MQTTController#mqtt file /home/homebridge/reactor/config/ext/MQTTController/templates/tasmota.yaml overrides existing template definition tasmota_generic_relay from /home/homebridge/reactor/config/ext/MQTTController/templates/tasmota.yaml

Available in zigbee2mqtt_test.zip