@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.0Urgent Help MSR stopped running
-
I am trying to download the log files from the /var/log folder now.
Is this bad ?
EDIT:
Was in the wrong directory, this looks better.
-
You should not be running npm as root.
-
The syslog is massive and I am not sure what I am looking for, however I just saw this:
Mar 18 18:03:33 HP-Thin01 node[407]: NODE_PATH /home/stuart/reactor Mar 18 18:03:33 HP-Thin01 node[407]: node:internal/fs/utils:344 Mar 18 18:03:33 HP-Thin01 node[407]: throw err; Mar 18 18:03:33 HP-Thin01 node[407]: ^ Mar 18 18:03:33 HP-Thin01 node[407]: Error: ENOSPC: no space left on device, write Mar 18 18:03:33 HP-Thin01 node[407]: at Object.writeSync (node:fs:884:3) Mar 18 18:03:33 HP-Thin01 node[407]: at Object.writeFileSync (node:fs:2159:26) Mar 18 18:03:33 HP-Thin01 node[407]: at Object.<anonymous> (/home/stuart/reactor/app.js:236:133) Mar 18 18:03:33 HP-Thin01 node[407]: at Module._compile (node:internal/modules/cjs/loader:1101:14) Mar 18 18:03:33 HP-Thin01 node[407]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) Mar 18 18:03:33 HP-Thin01 node[407]: at Module.load (node:internal/modules/cjs/loader:981:32) Mar 18 18:03:33 HP-Thin01 node[407]: at Function.Module._load (node:internal/modules/cjs/loader:822:12) Mar 18 18:03:33 HP-Thin01 node[407]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) Mar 18 18:03:33 HP-Thin01 node[407]: at node:internal/main/run_main_module:17:47 { Mar 18 18:03:33 HP-Thin01 node[407]: errno: -28, Mar 18 18:03:33 HP-Thin01 node[407]: syscall: 'write', Mar 18 18:03:33 HP-Thin01 node[407]: code: 'ENOSPC' Mar 18 18:03:33 HP-Thin01 node[407]: } Mar 18 18:03:33 HP-Thin01 systemd[1]: reactor.service: Main process exited, code=exited, status=1/FAILURE Mar 18 18:03:33 HP-Thin01 systemd[1]: reactor.service: Failed with result 'exit-code'.If I am running out of disk space, I am not sure really how and where to find out what is talking up all the space and how to clear it.
I am only running MSR, Node-Red and HA Bridge nothing else on this box.
Thanks
-
Ok, so now look at the logs again. Disk space problem hiding others, now you should be able to see them.
-
OK these are the latest entries in the syslog to do with reactor
Mar 18 22:07:48 HP-Thin01 node[522]: NODE_PATH /home/stuart/reactor Mar 18 22:07:48 HP-Thin01 node[522]: FileLogStream { type: 'file', name: 'reactor.log', maxsize: 2, keep: 5 } Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.123Z <app:null> Reactor latest-22069-ebeefad starting on v16.13.1 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.126Z <app:INFO> Process ID 522; platform linux/x64 #1 SMP Debian 4.19.208-1 (2021-09-29); locale en_GB.UTF-8 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.127Z <app:INFO> Basedir /home/stuart/reactor; data in /home/stuart/reactor/storage Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.128Z <app:INFO> NODE_PATH=/home/stuart/reactor Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.135Z <app:INFO> Configured locale (undefined); selected locale(s) en_GB.UTF-8 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.195Z <app:INFO> Loaded locale en-US Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.223Z <Capabilities:null> Module Capabilities v21333 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.354Z <Plugin:null> Module Plugin v21186 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.369Z <TimerBroker:null> Module TimerBroker v21333 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.381Z <default:INFO> Module Entity v22042 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.391Z <Controller:null> Module Controller v22003 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.392Z <default:null> Module Structure v22047 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.413Z <default:null> Module Ruleset v21096 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.414Z <default:null> Module Rulesets v21096 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.433Z <GlobalExpression:null> Module GlobalExpression v21333 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.474Z <Predicate:null> Module Predicate v22067 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.484Z <AlertManager:null> Module AlertManager v21355 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.490Z <default:null> Module Rule v22043 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.500Z <GlobalReaction:null> Module GlobalReaction v21333 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.504Z <default:null> Module Engine v22053 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.505Z <default:null> Module httpapi v22021 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.510Z <default:null> Module httpproxy v21333 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.554Z <default:null> Module wsapi v21334 Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.558Z <app:NOTICE> Starting Structure... ar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.558Z <app:NOTICE> Starting Structure... Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.567Z <IndividualFileStrategy:ERR> [IndividualFileStrategy][IndividualFileStrategy#/home/stuart/reactor/storage] failed to read sys_alerts in /home/stuart/reactor/storage/states/sys_alerts.json: [SyntaxError]SyntaxError: Unexpected end of JSON input Mar 18 22:07:48 HP-Thin01 node[522]: Trapped unhandled Promise rejection SyntaxError: Unexpected end of JSON input Mar 18 22:07:48 HP-Thin01 node[522]: at JSON.parse (<anonymous>) Mar 18 22:07:48 HP-Thin01 node[522]: at IndividualFileStrategy.getDataObject (/home/stuart/reactor/server/lib/IndividualFileStrategy.js:123:47) Mar 18 22:07:48 HP-Thin01 node[522]: at Container.getDataObject (/home/stuart/reactor/server/lib/Container.js:98:51) Mar 18 22:07:48 HP-Thin01 node[522]: at Structure.start (/home/stuart/reactor/server/lib/Structure.js:280:631) Mar 18 22:07:48 HP-Thin01 node[522]: at Object.<anonymous> (/home/stuart/reactor/app.js:288:80) Mar 18 22:07:48 HP-Thin01 node[522]: at Module._compile (node:internal/modules/cjs/loader:1101:14) Mar 18 22:07:48 HP-Thin01 node[522]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) Mar 18 22:07:48 HP-Thin01 node[522]: at Module.load (node:internal/modules/cjs/loader:981:32) Mar 18 22:07:48 HP-Thin01 node[522]: at Function.Module._load (node:internal/modules/cjs/loader:822:12) Mar 18 22:07:48 HP-Thin01 node[522]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) Mar 18 22:07:48 HP-Thin01 node[522]: SyntaxError: Unexpected end of JSON input Mar 18 22:07:48 HP-Thin01 node[522]: at JSON.parse (<anonymous>) Mar 18 22:07:48 HP-Thin01 node[522]: at IndividualFileStrategy.getDataObject (/home/stuart/reactor/server/lib/IndividualFileStrategy.js:123:47) Mar 18 22:07:48 HP-Thin01 node[522]: at Container.getDataObject (/home/stuart/reactor/server/lib/Container.js:98:51) Mar 18 22:07:48 HP-Thin01 node[522]: at Structure.start (/home/stuart/reactor/server/lib/Structure.js:280:631) Mar 18 22:07:48 HP-Thin01 node[522]: at Object.<anonymous> (/home/stuart/reactor/app.js:288:80) Mar 18 22:07:48 HP-Thin01 node[522]: at Module._compile (node:internal/modules/cjs/loader:1101:14) Mar 18 22:07:48 HP-Thin01 node[522]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) Mar 18 22:07:48 HP-Thin01 node[522]: at Module.load (node:internal/modules/cjs/loader:981:32) Mar 18 22:07:48 HP-Thin01 node[522]: at Function.Module._load (node:internal/modules/cjs/loader:822:12) Mar 18 22:07:48 HP-Thin01 node[522]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) Mar 18 22:07:48 HP-Thin01 node[522]: Promise { Mar 18 22:07:48 HP-Thin01 node[522]: <rejected> SyntaxError: Unexpected end of JSON input Mar 18 22:07:48 HP-Thin01 node[522]: at JSON.parse (<anonymous>) Mar 18 22:07:48 HP-Thin01 node[522]: at IndividualFileStrategy.getDataObject (/home/stuart/reactor/server/lib/IndividualFileStrategy.js:123:47) Mar 18 22:07:48 HP-Thin01 node[522]: at Container.getDataObject (/home/stuart/reactor/server/lib/Container.js:98:51) Mar 18 22:07:48 HP-Thin01 node[522]: at Structure.start (/home/stuart/reactor/server/lib/Structure.js:280:631) Mar 18 22:07:48 HP-Thin01 node[522]: at Object.<anonymous> (/home/stuart/reactor/app.js:288:80) Mar 18 22:07:48 HP-Thin01 node[522]: at Module._compile (node:internal/modules/cjs/loader:1101:14) Mar 18 22:07:48 HP-Thin01 node[522]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) Mar 18 22:07:48 HP-Thin01 node[522]: at Module.load (node:internal/modules/cjs/loader:981:32) Mar 18 22:07:48 HP-Thin01 node[522]: at Function.Module._load (node:internal/modules/cjs/loader:822:12) Mar 18 22:07:48 HP-Thin01 node[522]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) Mar 18 22:07:48 HP-Thin01 node[522]: } Mar 18 22:07:48 HP-Thin01 node[522]: Trace Mar 18 22:07:48 HP-Thin01 node[522]: at process.<anonymous> (/home/stuart/reactor/app.js:271:162) Mar 18 22:07:48 HP-Thin01 node[522]: at process.emit (node:events:390:28) Mar 18 22:07:48 HP-Thin01 node[522]: at process.emit (node:domain:475:12) Mar 18 22:07:48 HP-Thin01 node[522]: at emit (node:internal/process/promises:136:22) Mar 18 22:07:48 HP-Thin01 node[522]: at processPromiseRejections (node:internal/process/promises:242:25) Mar 18 22:07:48 HP-Thin01 node[522]: at processTicksAndRejections (node:internal/process/task_queues:97:32) Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.582Z <app:ERR> Trapped unhandled Promise rejection: [SyntaxError]SyntaxError: Unexpected end of JSON input Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.582Z <app:ERR> Please refer to the console log for trace Mar 18 22:07:48 HP-Thin01 systemd[1]: reactor.service: Succeeded.Mar 18 22:05:28 HP-Thin01 node[402]: [latest-22069]2022-03-18T22:05:28.048Z <IndividualFileStrategy:ERR> [IndividualFileStrategy][IndividualFileStrategy#/home/stuart/reactor/storage] failed to read sys_alerts in /home/stuart/reactor/storage/states/sys_alerts.json: [SyntaxError]SyntaxError: Unexpected end of JSON input Mar 18 22:05:28 HP-Thin01 node[402]: Trapped unhandled Promise rejection SyntaxError: Unexpected end of JSON input Mar 18 22:05:28 HP-Thin01 node[402]: at JSON.parse (<anonymous>) Mar 18 22:05:28 HP-Thin01 node[402]: at IndividualFileStrategy.getDataObject (/home/stuart/reactor/server/lib/IndividualFileStrategy.js:123:47) Mar 18 22:05:28 HP-Thin01 node[402]: at Container.getDataObject (/home/stuart/reactor/server/lib/Container.js:98:51) Mar 18 22:05:28 HP-Thin01 node[402]: at Structure.start (/home/stuart/reactor/server/lib/Structure.js:280:631) Mar 18 22:05:28 HP-Thin01 node[402]: at Object.<anonymous> (/home/stuart/reactor/app.js:288:80) Mar 18 22:05:28 HP-Thin01 node[402]: at Module._compile (node:internal/modules/cjs/loader:1101:14) Mar 18 22:05:28 HP-Thin01 node[402]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) Mar 18 22:05:28 HP-Thin01 node[402]: at Module.load (node:internal/modules/cjs/loader:981:32) Mar 18 22:05:28 HP-Thin01 node[402]: at Function.Module._load (node:internal/modules/cjs/loader:822:12) Mar 18 22:05:28 HP-Thin01 node[402]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) Mar 18 22:05:28 HP-Thin01 node[402]: SyntaxError: Unexpected end of JSON input Mar 18 22:05:28 HP-Thin01 node[402]: at JSON.parse (<anonymous>) Mar 18 22:05:28 HP-Thin01 node[402]: at IndividualFileStrategy.getDataObject (/home/stuart/reactor/server/lib/IndividualFileStrategy.js:123:47) Mar 18 22:05:28 HP-Thin01 node[402]: at Container.getDataObject (/home/stuart/reactor/server/lib/Container.js:98:51) Mar 18 22:05:28 HP-Thin01 node[402]: at Structure.start (/home/stuart/reactor/server/lib/Structure.js:280:631) Mar 18 22:05:28 HP-Thin01 node[402]: at Object.<anonymous> (/home/stuart/reactor/app.js:288:80) Mar 18 22:05:28 HP-Thin01 node[402]: at Module._compile (node:internal/modules/cjs/loader:1101:14) Mar 18 22:05:28 HP-Thin01 node[402]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) Mar 18 22:05:28 HP-Thin01 node[402]: at Module.load (node:internal/modules/cjs/loader:981:32) Mar 18 22:05:28 HP-Thin01 node[402]: at Function.Module._load (node:internal/modules/cjs/loader:822:12) Mar 18 22:05:28 HP-Thin01 node[402]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) Mar 18 22:05:28 HP-Thin01 node[402]: Promise { Mar 18 22:05:28 HP-Thin01 node[402]: <rejected> SyntaxError: Unexpected end of JSON input Mar 18 22:05:28 HP-Thin01 node[402]: at JSON.parse (<anonymous>) Mar 18 22:05:28 HP-Thin01 node[402]: at IndividualFileStrategy.getDataObject (/home/stuart/reactor/server/lib/IndividualFileStrategy.js:123:47) Mar 18 22:05:28 HP-Thin01 node[402]: at Container.getDataObject (/home/stuart/reactor/server/lib/Container.js:98:51) Mar 18 22:05:28 HP-Thin01 node[402]: at Structure.start (/home/stuart/reactor/server/lib/Structure.js:280:631) Mar 18 22:05:28 HP-Thin01 node[402]: at Object.<anonymous> (/home/stuart/reactor/app.js:288:80) Mar 18 22:05:28 HP-Thin01 node[402]: at Module._compile (node:internal/modules/cjs/loader:1101:14) Mar 18 22:05:28 HP-Thin01 node[402]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) Mar 18 22:05:28 HP-Thin01 node[402]: at Module.load (node:internal/modules/cjs/loader:981:32) Mar 18 22:05:28 HP-Thin01 node[402]: at Function.Module._load (node:internal/modules/cjs/loader:822:12) Mar 18 22:05:28 HP-Thin01 node[402]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) Mar 18 22:05:28 HP-Thin01 node[402]: } Mar 18 22:05:28 HP-Thin01 node[402]: Trace Mar 18 22:05:28 HP-Thin01 node[402]: at process.<anonymous> (/home/stuart/reactor/app.js:271:162) Mar 18 22:05:28 HP-Thin01 node[402]: at process.emit (node:events:390:28) Mar 18 22:05:28 HP-Thin01 node[402]: at process.emit (node:domain:475:12) Mar 18 22:05:28 HP-Thin01 node[402]: at emit (node:internal/process/promises:136:22) Mar 18 22:05:28 HP-Thin01 node[402]: at processPromiseRejections (node:internal/process/promises:242:25) Mar 18 22:05:28 HP-Thin01 node[402]: at processTicksAndRejections (node:internal/process/task_queues:97:32) Mar 18 22:05:28 HP-Thin01 node[402]: [latest-22069]2022-03-18T22:05:28.097Z <app:ERR> Trapped unhandled Promise rejection: [SyntaxError]SyntaxError: Unexpected end of JSON input -
The disk going full has resulted in the corruption of your storage folder. You will need to restore a backup.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
-
@cw-kid it's the folder called
storagein your Reactor folder.Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Is that the folder with the rulesets in it ?
I have a backup of all the folders and files, but it's not very recent.Hope I am not going to lose the more recent changes to the rules.
-
-
That's good sleuthing and good work. Yes, the
statesfolder gets most of the I/O. If it looks like everything else is intact, that's fine. Rules and rule sets would only be damaged if you happened to edit them during the time the disk was full.On the Reactor master device, there are flags for warning you when disk space is becoming limited; rules with notifications may be a good idea, to avoid future unpleasant surprises.
-
I am assuming I have had a lucky escape here then, all my rules look to be present still, I am assuming "States" is just that as the name suggests the current state of the rules and that they will rebuild and repopulate themselves.
I didn't have any auto backup in place as not really sure how to do that in Linux command line, so I was just now and again manually copying the entire contents of the /reactor folder down on to my PC.
-
All correct.
-
In Entities under Reactor System I have all this information
reactor_system.alert_count=0 reactor_system.alert_last=1647657325518 reactor_system.alert_severity=null reactor_system.alerts=[] reactor_system.arch="x64" reactor_system.hostname="HP-Thin01" reactor_system.internet_ok=null reactor_system.platform="linux" reactor_system.reactor_memory_used=138702848 reactor_system.reactor_uptime=1082 reactor_system.system_load=[0.13,0.15,0.11] reactor_system.system_memory_free=2020356096 reactor_system.system_memory_size=3537993728 reactor_system.system_uptime=17002.98 reactor_system.volume_critical_reactor_base=false reactor_system.volume_critical_reactor_data=false reactor_system.volume_critical_reactor_logs=false reactor_system.volume_reactor_base=[5390756,13825496,0.389,"/home/stuart/reactor"] reactor_system.volume_reactor_data=[5390756,13825496,0.389,"/home/stuart/reactor/storage"] reactor_system.volume_reactor_logs=[5390756,13825496,0.389,"/home/stuart/reactor/logs"] sys_system.state=true Capabilities: reactor_system, sys_system Actions: reactor_system.clear_alert, reactor_system.clear_alerts, sys_system.restartMemory free is that disk or RAM ?
