@toggledbits I understand that you do not perform testing on Mac computers but thought I'd share the following with you in case something can be done.
I started seeing these errors with version 24302. I thought that upgrading to 24343 would have fixed the issue but unfortunately not. I either have to close the browser or clear the cache for the errors to stop popping-up but they slowly come back.
I see these errors on the following browsers:
Safari 16.6.1 on macOS Big Sur Safari 18.1.1 on MacOS Sonoma DuckDuckGo 1.118.0 on macOS Big Sur and Sonoma Firefox 133.0.3 on macOS Big Sur Chrome 131.0.6778 on macOS Big SurHere are the errors
Safari while creating/updating an expression
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:21 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:29 reindexExpressions@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:32 @http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:608:40 dispatch@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:40040DuckDuckGo while clicking on status
http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:789:44 asyncFunctionResume@[native code] saveGridLayout@[native code] dispatchEvent@[native code] _triggerEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1401:30 _triggerAddEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1383:31 makeWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:968:30 addWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:388:24 placeWidgetAdder@http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:183:44Firefox while updating a rule
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:82:21 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:47:26 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1460:39 forEach@[native code] @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1459:58Chrome while creating/updating an expression
TypeError: Cannot read properties of undefined (reading 'getEditor') at RuleEditor.makeExprMenu (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:1788:86) at Object.handler (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:2174:54) at http://192.168.0.13:8111/client/MessageBus.js:98:44 at Array.forEach (<anonymous>) at MessageBus._sendToBus (http://192.168.0.13:8111/client/MessageBus.js:95:54) at MessageBus.send (http://192.168.0.13:8111/client/MessageBus.js:106:44) at ExpressionEditor.publish (http://192.168.0.13:8111/client/Observable.js:78:28) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:14) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:15) at ExpressionEditor.reindexExpressions (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:18) ``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.0Multi-System Reactor Developer Preview AVAILABLE
-
@elcid said in Multi-System Reactor Developer Preview AVAILABLE:
Some error in start up console log
Known error, it already has a PR, and is already fixed for the next build. That's just the preloader that I use to pull in data for testing. I'm usually looking at the end of the log, not the beginning, so I missed it before packaging the release.
-
Some first impressions. Having all home assistant and openluup entities together in a Reactor interface is a game changer. Install was super easy and went smoothly following the directions. Installed on a Debian10 VM. Looks like just about every entity from both systems were discovered. Performed a couple test rules with a HA entity being controlled based the state of an openluup entity and it was very responsive. Having trouble with the import tool, keep getting a syntax error. Definitely going to miss Run_Lua actions. Is there plans for anything to replace that? All and all looking great.
-
@black-cat said in Multi-System Reactor Developer Preview AVAILABLE:
Uploaded and expanded OK...but there is no config/reactor.yaml file to edit.
If you're using a Pi, you should have run the install script in the tools directory, which copies the files from dist-config to config. If you are installing on other Linux, there's a step in the instructions to do the copy manually. But that's all you need to do:
cp dist-config/* config/
-
@kfxo said in Multi-System Reactor Developer Preview AVAILABLE:
Having trouble with the import tool,
Can you paste some output? Let's have a look at that...
-
@toggledbits said in Multi-System Reactor Developer Preview AVAILABLE:
@kfxo said in Multi-System Reactor Developer Preview AVAILABLE:
Having trouble with the import tool,
Can you paste some output? Let's have a look at that...
I posted an issue on MantisBT but maybe I did it wrong. Should I try there again?
-
@kfxo said in Multi-System Reactor Developer Preview AVAILABLE:
I posted an issue on MantisBT but maybe I did it wrong. Should I try there again?
Good on ya! I see it...
OK. Easy enough. Not sure how that snuck by... Probably the easiest is to have you just open it in a text editor, find the line (192) that says
case 'interval': {
and just remove that curly brace from the end of it. Save, and try again. -
@toggledbits said in Multi-System Reactor Developer Preview AVAILABLE:
Nice. Any issues with the install?
Yes, but only due to myself. Following your instructions it went well Will continue the testing later today ...
-
Linux Neanderthal here, I tried to install it on my Raspberry Pi2.
I got this output not sure what it means, it says I need to commit some file?
The version of nodejs currently installed is v12.20.1 (compatible). Checking dependencies... > bufferutil@4.0.3 install /home/pi/Documents/reactor/node_modules/bufferutil > node-gyp-build > utf-8-validate@5.0.4 install /home/pi/Documents/reactor/node_modules/utf-8-validate > node-gyp-build > core-js@3.9.0 postinstall /home/pi/Documents/reactor/node_modules/core-js > node -e "try{require('./postinstall')}catch(e){}" Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library! The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: > https://opencollective.com/core-js > https://www.patreon.com/zloirock Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -) npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN bootstrap@4.5.3 requires a peer of popper.js@^1.16.1 but none is installed. You must install peer dependencies yourself. added 86 packages from 68 contributors and audited 87 packages in 46.342s 4 packages are looking for funding run `npm fund` for details found 0 vulnerabilities OK. Now please LOG OUT, then log back in and continue the installation procedure (see docs/markdown/Installation.md or docs/html/Installation/index.html).
The installation Guide here then says to:
"Edit the file config/reactor.yaml and, on the line beginning baseurl:, replace the IP address with the actual primary IP address of your system."
There is a "config" folder present but it is empty.
There is a folder called /home/pi/Documents/reactor/dist-config and the reactor.yaml file was in there, so I edited that one and added my Pi's IP address.
I actually didn't even have a "Documents" folder to begin with, I had to create that folder first in this path: /home/pi/Documents
It then says to:
"Start up Reactor: node app.js"
Looks like there were some errors during startup.
pi@raspberrypi:~/Documents/reactor $ node app.js 2021-02-19T09:18:37.424Z <app:null> Reactor application v21047 starting on v12.20.2 2021-02-19T09:18:37.641Z <Controller:null> Module Controller v21046 2021-02-19T09:18:37.643Z <default:null> Module Structure v21025 2021-02-19T09:18:37.692Z <default:null> Module Ruleset v21041 2021-02-19T09:18:37.694Z <default:null> Module Rulesets v21041 2021-02-19T09:18:37.825Z <default:null> Module Rule v21047 2021-02-19T09:18:37.868Z <default:null> Module Engine v21047 2021-02-19T09:18:37.910Z <default:null> Module httpapi v21041 2021-02-19T09:18:37.924Z <default:null> Module httpproxy v20350 2021-02-19T09:18:38.093Z <default:null> Module wsapi v21041 2021-02-19T09:18:38.246Z <default:CRIT> Error: ENOENT: no such file or directory, open './server/struct_data.json' Error: ENOENT: no such file or directory, open './server/struct_data.json' at Object.openSync (fs.js:462:3) at Object.readFileSync (fs.js:364:35) at Structure.start (/home/pi/Documents/reactor/server/lib/Structure.js:184:49) at /home/pi/Documents/reactor/app.js:141:72 at processTicksAndRejections (internal/process/task_queues.js:97:5) Error: ENOENT: no such file or directory, open './server/struct_data.json' at Object.openSync (fs.js:462:3) at Object.readFileSync (fs.js:364:35) at Structure.start (/home/pi/Documents/reactor/server/lib/Structure.js:184:49) at /home/pi/Documents/reactor/app.js:141:72 at processTicksAndRejections (internal/process/task_queues.js:97:5) { errno: -2, syscall: 'open', code: 'ENOENT', path: './server/struct_data.json' } 2021-02-19T09:18:38.479Z <default:null> Module SystemController v21025 2021-02-19T09:18:38.537Z <app:null> Waiting 10 seconds before starting Engine
Will Reactor be started automatically after you reboot the Pi ?
Answer = NO
"I haven't fully daemon-ized Reactor yet while still in test mode, but eventually it will, of course, be available for startup at boot time."
Anyway I have the Reactor up and running it seems, I can access it in the web browser.
I then edited the reactor.yaml file and added my location details and the IP for my Vera hub. However after restarting MSR I had nothing listed in Entities other than Reactor System.
I had to copy the reator.yaml file from this folder to this folder and then it worked.
/home/pi/Documents/reactor/dist-config
to
/home/pi/Documents/reactor/config
I can now see my Vera device and scenes listed under Entities
Thanks
cw
-
@cw-kid said in Multi-System Reactor Developer Preview AVAILABLE:
There is a "config" folder present but it is empty.
Just copy the files from
dist-config
toconfig
manually. Reactor won't read config files unless they are inconfig
.The startup error can be ignored; it's for loading test data, which isn't present.
-
@cw-kid said in Multi-System Reactor Developer Preview AVAILABLE:
Vera is not in either Away mode (2) or in Vacation mode (4)
Reactor's "House Mode" entity uses words:
home
,away
,night
,vacation
. Note what is showing for "Current value" underneath the condition. You can also see this in the Entities list.EDIT: Also, can we please start threading discussions in this category? It's going to get unruly fast if everyone is talking about everything as replies to one thread.
-
Hi
Thanks for the reply.
I have used the words "away" and "vacation". However when I see this summary it says null or no data for the house mode triggers (conditions).
So don't think its working.
EDIT:
Using "Does not contain" rather than "not in" looks better ?
-
That's an unexpected difference. Equals and not equals would also be applicable here.
-
@toggledbits In PLEG not equals is != I'm assuming <> is not equals in MSR. I'll change it to that as its better than "does not contain".
-
Congrats on the release. If you want to install on a x64 machine, just edit rpi-install.sh and replace arm7 with x64. I have mine on Windows Subsystem for Linux under Windows and it's running OK.
Can't wait for guidance on apdaters/plugins to contribute with Shelly and MQTT
-
@therealdb said in Multi-System Reactor Developer Preview AVAILABLE:
Can't wait for guidance on apdaters/plugins to contribute with Shelly and MQTT
MQTT will be huge.
-
On my list of hubs/controllers to tackle next are Homey and OpenHAB, but I am also interested in MQTT, so I'm hearing a bump in priority coming, at least for investigation.