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.
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
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.
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.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.
@togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.
Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.
Thanks in advance.
Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3
[Solved] ZWaveJSController Add-on Install files
-
@toggledbits The documentation to install the ZWaveJSController Add-on step 5 says to run the install.sh or install.bat file. I do not see these files in the downloaded archives. Am I overlooking something or doing something wrong?
-
Apologies. That's a build error... this is the first time it's been packaged stand-alone. Please download the release archive again; the package has been updated but keeps the same version number.
-
@toggledbits After a fresh download and also since I am using docker, I ran the install.sh from inside the container,(the docs for this Add-on module does not note this) the logs show that it is missing module js-yaml.
[latest-22240]2022-09-05T14:24:58.996Z <GlobalReaction:null> Module GlobalReaction v21333 [latest-22240]2022-09-05T14:24:58.998Z <default:null> Module Engine v22209 [latest-22240]2022-09-05T14:24:58.998Z <default:null> Module httpapi v22141 [latest-22240]2022-09-05T14:24:59.012Z <default:null> Module wsapi v22104 [latest-22240]2022-09-05T14:24:59.015Z <app:NOTICE> Starting Structure... [latest-22240]2022-09-05T14:24:59.020Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping [latest-22240]2022-09-05T14:24:59.023Z <Structure:INFO> Structure#1 loading controller interface hass (HassController) [latest-22240]2022-09-05T14:24:59.071Z <HassController:null> Module HassController v22238 [latest-22240]2022-09-05T14:24:59.162Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [latest-22240]2022-09-05T14:24:59.182Z <Structure:INFO> Structure#1 loading controller interface hubitat (HubitatController) [latest-22240]2022-09-05T14:24:59.191Z <TaskQueue:null> Module TaskQueue 21351 [latest-22240]2022-09-05T14:24:59.191Z <HubitatController:null> Module HubitatController v22140 [latest-22240]2022-09-05T14:24:59.244Z <Structure:INFO> Structure#1 loading controller interface zwavejs (ZWaveJSController) [latest-22240]2022-09-05T14:24:59.257Z <Controller:CRIT> Controller: failed to load zwavejs implementation /var/reactor/ext/ZWaveJSController/ZWaveJSController.js: [Error]Error: Cannot find module 'js-yaml' Require stack: - /var/reactor/ext/ZWaveJSController/ZWaveJSController.js [latest-22240]2022-09-05T14:24:59.258Z <Controller:CRIT> Error: Cannot find module 'js-yaml' Require stack: - /var/reactor/ext/ZWaveJSController/ZWaveJSController.js Error: Cannot find module 'js-yaml' Require stack: - /var/reactor/ext/ZWaveJSController/ZWaveJSController.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15) at Function.Module._load (node:internal/modules/cjs/loader:778:27) at Module.require (node:internal/modules/cjs/loader:1005:19) at require (node:internal/modules/cjs/helpers:102:18) at Object.<anonymous> (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:529:88) at Module._compile (node:internal/modules/cjs/loader:1105:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:170:29) [latest-22240]2022-09-05T14:24:59.259Z <Structure:ERR> Structure#1 controller zwavejs ((undefined)) skipped, implementation could not be loaded. [latest-22240]2022-09-05T14:24:59.259Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-22240]2022-09-05T14:24:59.262Z <DynamicGroupController:null> Module DynamicGroupController v22123 [latest-22240]2022-09-05T14:24:59.266Z <Structure:INFO> Structure#1 loading controller interface weather (OWMWeatherController) [latest-22240]2022-09-05T14:24:59.270Z <OWMWeatherController:null> Module OWMWeatherController v22059 [latest-22240]2022-09-05T14:24:59.272Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-22240]2022-09-05T14:24:59.275Z <SystemController:null> Module SystemController v22080 [latest-22240]2022-09-05T14:24:59.278Z <Structure:INFO> Structure#1 loading controller interface mqtt (MQTTController) [latest-22240]2022-09-05T14:24:59.284Z <MQTTController:null> Module MQTTController v22144 [latest-22240]2022-09-05T14:24:59.329Z <MQTTController:INFO> instance topic ident is mqtt [latest-22240]2022-09-05T14:24:59.332Z <Structure:INFO> Structure#1 loading controller interface nut (NUTController) [latest-22240]2022-09-05T14:24:59.334Z <default:null> Module NUTController v22152 [latest-22240]2022-09-05T14:24:59.337Z <Structure:INFO> Starting controller HassController#hass [latest-22240]2022-09-05T14:24:59.337Z <HassController:NOTICE> HassController#hass starting... [latest-22240]2022-09-05T14:24:59.338Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.21:8123/api/websocket [latest-22240]2022-09-05T14:24:59.345Z <Structure:INFO> Starting controller HubitatController#hubitat [latest-22240]2022-09-05T14:24:59.370Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-22240]2022-09-05T14:24:59.374Z <DynamicGroupController:NOTICE> Controller DynamicGroupController#groups is now online. [latest-22240]2022-09-05T14:24:59.374Z <Structure:INFO> Starting controller OWMWeatherController#weather [latest-22240]2022-09-05T14:24:59.402Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-22240]2022-09-05T14:24:59.404Z <SystemController:NOTICE> Controller SystemController#reactor_system is now online. [latest-22240]2022-09-05T14:24:59.429Z <Structure:INFO> Starting controller MQTTController#mqtt [latest-22240]2022-09-05T14:24:59.430Z <MQTTController:NOTICE> Connecting to broker mqtt://192.168.1.21:1883/ [latest-22240]2022-09-05T14:24:59.476Z <Structure:INFO> Starting controller NUTController#nut [latest-22240]2022-09-05T14:24:59.478Z <NUTController:NOTICE> NUTController#nut connecting to NUT server at "192.168.1.20":3493 [latest-22240]2022-09-05T14:24:59.479Z <NUTController:INFO> NUTController#nut started NUT client connection; waiting for ready [latest-22240]2022-09-05T14:24:59.480Z <app:NOTICE> Starting HTTP server and API...``` Synology Docker MSR v latest-22240-3b3254d6
-
Please reread the install instructions. Nothing gets installed or run inside the docker container.
-
@toggledbits I did install per the instructions. Only after I got the error is when I tried running the install.sh from inside the container as I remembered from installing the MQTT and NUT add-ons had those instructions for docker. Everything was installed in the ext directory on the synology.
-
Make sure your
NODE_PATH
in your container configuration (Environment tab) reads/opt/reactor:/opt/reactor/node_modules
. The update mechanism on Synology may not update this value on an existing container (even if reset). -
That was it. It is working now. My NODE_PATH was /opt/reactor, Changed to/opt/reactor:/opt/reactor/node_modules. When did this change and is there something I should of done differently to have this update?
Thanks -
No, it's a limitation of the Synology container manager, apparently. It doesn't seem to apply updated values from the new image to existing containers. I'll make note of that on the next Reactor build (later today) as well. I've also updated the instructions to just eliminate the install scripts; they don't do anything meaningful (everything ZWaveJSController needs is already in the current Reactor environment).
When Reactor 22248 comes out later today, you will not need to upgrade to it unless you feel a need to get the one major new feature (ability to "wait for completion" when a reaction runs another reaction). If you don't need it, don't bother. But if you do decide to upgrade, you will also need to upgrade your ZWaveJSController to its 22248 build as well.
-