Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.
Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce
A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.
Hi
Having to rebuild my Linux Debian box as the SSD failed. And I have forgotten exactly what I did the first time to get it all setup.
I have Debian 12 up and running on the new SSD, I only have console no Desktop GUI.
I am trying to do the bare metal install for MSR. However I am not sure if I am meant to install nodejs whlist logged in as the root user or as the none root user with my name ?
I used putty and connected via SSH and logged in as root and I installed nodejs but I think this was wrong as when logged in as my user name and I do a node -v command it says node is not installed or doesn't show any version number anyway.
But when logged in as root and I do a node -v command it does show me its installed and displays the version number. maybe its a path issue for my username and he can't see node is installed?
So now I am thinking I should of installed node whilst logged in as my user name and not as the root user.
This is how I installed nodejs as whilst logged in as root
ac7bf6c3-23ad-46fc-8ada-44af6704e63e-image.png
Thanks in advance.
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.As the title says, here's my OpenAI Controller for Reactor:
OpenAI Controller per Reactor. Contribute to dbochicchio/reactor-openai development by creating an account on GitHub.
It supports both OpenAI and Azure OpenAI endpoints. You'll need keys/endpoints, according to each service.
The controller supports multiple models, and each one could be mapped as an entity.
It's quite easy to use, and responses can be stored in variables, for easy access. Or sent to another action (Text To Speech, another endpoint, etc).
9013ae50-fd68-42a2-87c3-97479132e465-image.png
80a88eec-7c89-464a-8196-690b4b72d044-image.png
Have fun with LLM into your scenes!
In Home Assistant I have an integration that if I add entities to it, I will get the following error in MSR as certain entity values I'm using in expressions are null for a moment. This is more or less cosmetic issue and happens very rarely as I rarely modify that integration on the hass side.
Screenshot 2024-11-28 at 22.20.41.png
And the expression is
Screenshot 2024-11-28 at 22.38.19.png
Could I "wrap" hass-entity shown above somewhat differently to prevent this error from happening? Using build 24302.
Hello
I am trying to set up Multi System Reactor to automate routines across multiple smart home devices & platforms (e.g., Home Assistant, SmartThings, and Hubitat). While I have successfully linked the systems; I am facing issues with:
-Delays in triggering actions on secondary devices.
-Inconsistent execution of complex logic conditions.
-Synchronization of states between devices when one system updates.
Is there a recommended way to optimize performance & confirm seamless state sharing across systems?
I have checked https://smarthome.community/category/22/multi-system-reactor-msbi guide for reference but still need advice.
Any tips on debugging or log analysis to pinpoint where the issue arises would also be appreciated.
Thank you !
I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.
Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.
( *Drag & drop of rule conditions have never worked on a mobile)
@toggledbits Since I have upgraded ZWaveJSController to 24293 from 24257 I am seeing entries related to registering action set_volume, but action is not defined by the capability 143 every time I restart Reactor.
The Siren seems to be doing what it is supposed to do. The volume levels are fine. Should I worry about it?
Reactor version 24302
ZWaveJSController version 24293
Z-Wave JS UI version 9.27.4
zwave-js version 14.3.4
I have the following ACL defined:
groups: admin: users: - admin applications: true api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: trueAnd I have authenticated to MSR as "admin" user. However, I'm getting "access denied" when trying to access http://*******:8111/api/v1/log
So what I'm missing, is my ACL incorrectly defined?
Using build 24302 on Docker.
Hi
I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.
They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.
This is how that device looks in the Ezlo API.
Devices Info:
_id: "10696001" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "level_sensor" subcategory: "" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Digital" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696001" deviceId: "10696001" hasGetter: true hasSetter: false name: "smoke_density" show: true valueType: "substance_amount" scale: "parts_per_million" value: 2.7472610473632812 valueFormatted: "2.75" status: "idle"There is also an Analog Gas sensor that one did import in to MSR OK.
68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png
Devices Info:
_id: "10696000" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "security_sensor" subcategory: "gas" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Analog" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696000" deviceId: "10696000" hasGetter: true hasSetter: false name: "gas_alarm" show: true valueType: "token" enum: 0: "no_gas" 1: "combustible_gas_detected" 2: "toxic_gas_detected" 3: "unknown" valueFormatted: "no_gas" value: "no_gas" status: "idle"And this is how this MQ2 Gas Sensor looks like on their dashboard:
Digital
cb77dfa3-4af5-4d06-9635-89207a716a89-image.png
Analog
4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png
They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!
And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.
THANKS.
A couple of things for you @toggledbits, since you mentioned that this release has new features and some tweaks are expected.
Local expressions cannot be deleted. Pushing the X button has no effect for me.
When cloning an entity action, the result is strange (first is cloned one, second is the original action):
a92ea094-9e2c-4aaa-bf47-2d07a6ffdbd0-image.png
When changing the action on the cloned element, the params are added to the original one. See screenshot:
92ac3011-83c8-466b-bd23-47d483ad7a52-image.png
Dark theme has a couple of strange contrasts. One is visible in the previous screenshots (white text on yellow background). Another one is in groups (blue text on blue background):
9b3c4988-53ef-44e6-9672-30e744cacb75-image.png
Overall, I found blue, yellow, red and green (in buttons and forms) to be too bright.
On the bright side:
I love the new script action: thank you! The dark theme is a great start to avoid getting blinded at night I promise I'll try very soon the new features around actions. Thanks!@toggledbits
I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:
I followed the new directions about npm
npm i --no-save --no-package-lock --omit dev
Any idea what the issue is?
Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)
Things I have tried:
Hard refresh
Different browser
Different computer
Restarting Reactor
Failed troubleshooting attempts:
No errors in Chrome console
No relevant errors in Reactor log (can still PM the full log file)
Reactor version: latest-24293-ea42a81d
Hardware: Odroid N2+
Linux version: Ubuntu 24.04.1 LTS
3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled
ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled
Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.
What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?
Running:
Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]HAAS:
RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0Hi!
Is it possible to generate two additional log files, the first being the replica of what is displayed on screen by the Rule History widgets and the other with Recently Changed Entities?
And could I configure the generation of one file per day, and delete the older ones? For example, store the last 5 days?
And being more ambitious, does Windget have an icon to open these TXT files in the navigated?
Well, we're approaching Christmas, so here's my request to Santa Claus @toggledbits 🙂
Hi @toggledbits
I'm working on a controller to generate llm response from a prompt in reactor. I have http response coming thru an http request action at the moment, capturing the response inside a local variable. So, it's practically sync.
I want to create a controller, so I don't have to rely on a proxy (and have a simpler architecture), and duplicate absurd http actions, but AFAIK in the current implementation, actions are async only. But if I have multiple requests going on, I cannot be sure what it's really inside an attribute. I also thought that something like a correlation id when sending the request could be used to identity multiple responses, but I wanted to double check with you before starting with something too complicated. I also noticed that some actions in home assistant (ie forecast) are sync and I'm wondering if you have any plan or hint to address this situation. Thanks.
Thanks.
Reactor Ex Machina II (2023-July Update)
-
Here is an updated Reactor Ex Machina that works with new features of Reactor that have been added since the earlier post. It now can be done a single rule, thanks to the Repeat...While action in reactions.
The easiest way to get this new version is to grab the rule data (bottom of this post) and save it with the name
rule-reactorexmachina.json
(exactly this; no changes) in yourstorage/rules/
subdirectory. Then restart Reactor. After restart, you will find the Reactor Ex Machina II rule in a Recovered Rules rule set. You can move it to whatever other rule set you like. You may see an error for theREM_lights
variable (global) missing; don't worry about that right now, we'll handle that in a moment.To configure it, you need to do two things (and maybe a third optional thing):
- Create a global variable/expression called
REM_lights
that defines an array containing the canonical IDs of the lights you want it to manipulate. This is as it was for the previous version of REM, so you may already have that, and what you have is probably fine. If you don't have it, your expression should look like this to define the array of lights:
-
You need to configure the conditions in the Triggers of the new rule to be true when you want lights to randomly cycle. This is called the active period, and the default configuration is from 30 minutes before sunset to 23:30 (just as a placeholder).
-
(OPTIONAL) Change the timing by modifying the two Delay actions. The Delay action in the Set Reaction is for when lights are being toggled while in the active period. In the Reset Reaction, the delay controls the timing of lights shutting off at the end of the active period (i.e. to simulate going to bed, which may be more rapid). The formula for computing the delay is
random()*range + minimum
(seconds). As an example,random()*840 + 60
would give a random delay of 60 to 900 (840+60=900) seconds (which is 1 to 15 minutes) between actions.
Operation is pretty straightforward and greatly simplified by the new Reactor features. When the rule is SET (i.e. triggers true, in the active period), the Set Reaction starts an infinite loop that picks a random light from
REM_lights
and toggles it, then delays a random amount of time. That continues until the triggers are no longer true and the rule RESETs. The Reset Reaction then runs (automatically cancelling the Set Reaction task), turning off a light that is currently on (from among those inREM_lights
again) and then delaying, repeating until all lights are off.Here's the rule JSON data:
{ "id": "rule-reactorexmachina", "container": "rules", "value": { "id": "rule-reactorexmachina", "serial": 44, "triggers": { "type": "group", "id": "trig", "op": "or", "conditions": [ { "type": "group", "id": "grp13uaq1lz", "op": "and", "conditions": [ { "id": "cond13uaq1m0", "type": "comment", "data": { "comment": "Here, put in the rules for when random lights should cycle... time of day, house mode, virtual switch/input boolean state, etc." } }, { "id": "cond13uaq1m2", "type": "sun", "data": { "tzo": 240, "op": "after", "start": "sunset", "start_offset": -30 } }, { "id": "cond13uaq1m3", "type": "trange", "data": { "op": "before", "start": { "hr": 18, "min": 45 }, "tzo": 240, "end": {} } } ], "editor_version": 23130, "name": "Active Period" } ], "editor_version": 23130, "disabled": true }, "constraints": { "type": "group", "id": "cons", "op": "and", "conditions": [] }, "expressions": { "dummy": { "name": "dummy", "expr": "", "index": 0 }, "lights_on": { "name": "lights_on", "expr": "each light in REM_lights: do e=getEntity( light ), e.attributes.power_switch.state ? e.canonical_id : null done", "index": 1 } }, "name": "Reactor Ex Machina II", "react_set": { "id": "rule-reactorexmachina:S", "actions": [ { "id": "rule-reactorexmachina:S-13ua1p95", "type": "while", "actions": [ { "id": "13u9qo3b", "type": "comment", "data": { "comment": "Toggle a random light in the list of lights" } }, { "id": "8wul3as", "type": "setvar", "data": { "var": "dummy", "rule": "rule-reactorexmachina", "value": "${{ performAction( REM_lights[ floor( random() * len( REM_lights ) ) ], 'toggle.toggle', {} ) }}", "reeval": false } }, { "id": "13u9py8u", "type": "comment", "data": { "comment": "Delay random to next light toggle" } }, { "id": "8wul3ew", "type": "delay", "data": { "delay": "${{ random()*840 + 60 }}" } } ], "constraints": { "id": "13ua1p95-cons", "name": "Active", "type": "group", "op": "and", "conditions": [ { "id": "cond13uaycbu", "type": "comment", "data": { "comment": "The below is a dummy condition that's always true if your REM is configured (i.e. it has lights to operate on)" } }, { "id": "cond13ua1smv", "type": "var", "data": { "var": "REM_lights", "op": "notempty" } } ], "editor_version": 23130 } } ], "rule": "rule-reactorexmachina", "editor_version": 23130 }, "react_reset": { "id": "rule-reactorexmachina:R", "actions": [ { "id": "rule-reactorexmachina:R-13uagam7", "type": "while", "actions": [ { "id": "13uagcg8", "type": "comment", "data": { "comment": "Turn off a light that's on. Then delay random to next light off. This continues until all lights are off (condition above)." } }, { "id": "13uagut5", "type": "setvar", "data": { "var": "dummy", "rule": "rule-reactorexmachina", "value": "${{ performAction( lights_on[0], \"power_switch.off\" ) }}", "reeval": false } }, { "id": "13uah4lh", "type": "delay", "data": { "delay": "${{ random()*270 + 30 }}" } } ], "constraints": { "id": "13uagam7-cons", "name": "Shutdown", "type": "group", "op": "and", "conditions": [ { "id": "cond13uagex0", "type": "var", "data": { "rule": "rule-reactorexmachina", "var": "lights_on", "op": "notempty" } } ], "editor_version": 23130 } } ], "rule": "rule-reactorexmachina", "editor_version": 23130 }, "ruleset": "rs-remII" }, "tss": 1689548165797, "tsc": 1689548165797 }
- Create a global variable/expression called
-
@toggledbits Being the impetus for recreating this from the old days of Vera I love this "REM: TNG".
-