@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) ``Not sure that it is the same issue but just got this on built 24302 when running a reaction for testing purpose. Despite the error message, the reaction ran properly.
Error: Command timeout (195 start_reaction)
at _ClientAPI._commandTimeout (http://192.168.2.163:8111/client/ClientAPI.js:552:136)
1a3422eb-d760-4609-a740-a40d04a6bab2-Screenshot 2024-12-29 231851.png
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
MSR “Unexpected end of JSON input” after container update
-
Hi,
I’m running MSR in a docker container on my Synology Nas. The container is automatically updated using watchtower weekly.
It was working. Now, after the update, Reactor webpage is able to load, and all indications on the webpage suggests that it is working fine. However, the updated statuses from Home Assistant and Vera are not being detected.
The container logs show the following error
Reactor stable-23344-5aad7754 app 23344 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [stable-23344]2024-02-28T21:57:49.516Z <app:null> Reactor build stable-23344-5aad7754 starting on v16.15.1 [stable-23344]2024-02-28T21:57:49.517Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #69057 SMP Fri Jan 12 17:02:28 CST 2024; locale (undefined) [stable-23344]2024-02-28T21:57:49.517Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [stable-23344]2024-02-28T21:57:49.517Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [stable-23344]2024-02-28T21:57:49.696Z <Structure:null> Module Structure v23172 [stable-23344]2024-02-28T21:57:49.698Z <Capabilities:null> Module Capabilities v23331 [stable-23344]2024-02-28T21:57:49.780Z <Plugin:null> Module Plugin v22300 [stable-23344]2024-02-28T21:57:49.790Z <TimerBroker:null> Module TimerBroker v22283 [stable-23344]2024-02-28T21:57:49.794Z <Entity:null> Module Entity v22353 [stable-23344]2024-02-28T21:57:49.866Z <Controller:null> Module Controller v23069 [stable-23344]2024-02-28T21:57:50.030Z <default:null> Module Ruleset v22293 [stable-23344]2024-02-28T21:57:50.031Z <default:null> Module Rulesets v22146 [stable-23344]2024-02-28T21:57:50.066Z <GlobalExpression:null> Module GlobalExpression v23211 [stable-23344]2024-02-28T21:57:50.581Z <Predicate:null> Module Predicate v23093 [stable-23344]2024-02-28T21:57:50.595Z <AlertManager:null> Module AlertManager v22283 [stable-23344]2024-02-28T21:57:50.600Z <Rule:null> Module Rule v23107 [stable-23344]2024-02-28T21:57:50.614Z <GlobalReaction:null> Module GlobalReaction v22324 [stable-23344]2024-02-28T21:57:50.617Z <Engine:null> Module Engine v23339 [stable-23344]2024-02-28T21:57:50.635Z <httpapi:null> Module httpapi v23058 [stable-23344]2024-02-28T21:57:50.680Z <wsapi:null> Module wsapi v23172 [stable-23344]2024-02-28T21:57:50.789Z <TaskQueue:null> Module TaskQueue 21351 [stable-23344]2024-02-28T21:57:50.790Z <VeraController:null> Module VeraController v23109 [stable-23344]2024-02-28T21:57:50.971Z <HassController:null> Module HassController v23344 [stable-23344]2024-02-28T21:57:51.716Z <DynamicGroupController:null> Module DynamicGroupController v22313 [stable-23344]2024-02-28T21:57:52.253Z <SystemController:null> Module SystemController v23331 i18n: missing en-US language string: The version of nodejs you are using ({0}) is now end-of-life, and so is deprecated for use with Reactor. Please upgrade nodejs to {2}.{3} or higher as soon as possible; the current LTS version is recommended. Releases of Reactor produced after {1} will not run under this version of nodejs at all. [stable-23344]2024-02-28T21:57:52.256Z <Controller:CRIT> SyntaxError: Unexpected end of JSON input [-] SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at /opt/reactor/server/lib/Controller.js:464:51 at Array.forEach (<anonymous>) at SystemController._restoreEntities (/opt/reactor/server/lib/Controller.js:458:36) at new Controller (/opt/reactor/server/lib/Controller.js:45:42) at new SystemController (/opt/reactor/server/lib/SystemController.js:29:9) at /opt/reactor/server/lib/Controller.js:101:37 Trace: The version of nodejs you are using ({0}) is now end-of-life, and so is deprecated for use with Reactor. Please upgrade nodejs to {2}.{3} or higher as soon as possible; the current LTS version is recommended. Releases of Reactor produced after {1} will not run under this version of nodejs at all. at _T (/opt/reactor/server/lib/i18n.js:468:37) at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:126:25) at /opt/reactor/app.js:381:140 [stable-23344]2024-02-28T21:57:59.313Z <app:CRIT> SyntaxError: Unexpected end of JSON input [-] SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at IndividualFileStrategy.getDataObject (/opt/reactor/server/lib/IndividualFileStrategy.js:114:54) at DelayWriteCacheStrategy.getDataObject (/opt/reactor/server/lib/DelayWriteCacheStrategy.js:87:50) at Container.getDataObject (/opt/reactor/server/lib/Container.js:69:67) at Function.getInstance (/opt/reactor/server/lib/Data.js:37:179) at Rule.getRuleStates (/opt/reactor/server/lib/Rule.js:507:100) at Rule.getConditionState (/opt/reactor/server/lib/Rule.js:538:47) at new Rule (/opt/reactor/server/lib/Rule.js:378:47) at Function.getInstance (/opt/reactor/server/lib/Rule.js:387:36) at /opt/reactor/server/lib/Engine.js:263:53 i18n: missing en-US language string: HomeAssistant on {0:q} may be an unsupported version. The reported version ({1}) has not been certified/tested with this version of Reactor and may cause errors. You must either modify your HomeAssistant install, or see if an update to Reactor has been made available. Trace: HomeAssistant on {0:q} may be an unsupported version. The reported version ({1}) has not been certified/tested with this version of Reactor and may cause errors. You must either modify your HomeAssistant install, or see if an update to Reactor has been made available. at _T (/opt/reactor/server/lib/i18n.js:468:37) at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:126:25) at HassController.sendWarning (/opt/reactor/server/lib/Controller.js:197:36) at /opt/reactor/server/lib/HassController.js:1117:370 at processTicksAndRejections (node:internal/process/task_queues:96:5)I’ve tried using “latest-amd64” and it does not work either. The logs show similar json input error.
Reactor latest-24057-e9add9f5 app 24052 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-24057]2024-02-28T22:27:30.466Z <app:null> Reactor build latest-24057-e9add9f5 starting on v20.10.0 [latest-24057]2024-02-28T22:27:30.522Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #69057 SMP Fri Jan 12 17:02:28 CST 2024; locale (undefined) [latest-24057]2024-02-28T22:27:30.522Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-24057]2024-02-28T22:27:30.522Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-24057]2024-02-28T22:27:30.667Z <Structure:null> Module Structure v23172 [latest-24057]2024-02-28T22:27:30.673Z <Capabilities:null> Module Capabilities v23331 [latest-24057]2024-02-28T22:27:30.780Z <Plugin:null> Module Plugin v22300 [latest-24057]2024-02-28T22:27:30.787Z <TimerBroker:null> Module TimerBroker v22283 [latest-24057]2024-02-28T22:27:30.791Z <Entity:null> Module Entity v22353 [latest-24057]2024-02-28T22:27:30.796Z <Controller:null> Module Controller v23069 [latest-24057]2024-02-28T22:27:30.811Z <default:null> Module Ruleset v22293 [latest-24057]2024-02-28T22:27:30.811Z <default:null> Module Rulesets v22146 [latest-24057]2024-02-28T22:27:30.821Z <GlobalExpression:null> Module GlobalExpression v23211 [latest-24057]2024-02-28T22:27:30.890Z <Predicate:null> Module Predicate v23093 [latest-24057]2024-02-28T22:27:30.958Z <AlertManager:null> Module AlertManager v22283 [latest-24057]2024-02-28T22:27:31.027Z <Rule:null> Module Rule v24057 [latest-24057]2024-02-28T22:27:31.033Z <GlobalReaction:null> Module GlobalReaction v22324 [latest-24057]2024-02-28T22:27:31.036Z <Engine:null> Module Engine v24023 [latest-24057]2024-02-28T22:27:31.042Z <httpapi:null> Module httpapi v24057 [latest-24057]2024-02-28T22:27:31.216Z <wsapi:null> Module wsapi v24057 [latest-24057]2024-02-28T22:27:31.296Z <TaskQueue:null> Module TaskQueue 21351 [latest-24057]2024-02-28T22:27:31.297Z <VeraController:null> Module VeraController v24050 [latest-24057]2024-02-28T22:27:31.365Z <HassController:null> Module HassController v24048 [latest-24057]2024-02-28T22:27:31.659Z <DynamicGroupController:null> Module DynamicGroupController v22313 [latest-24057]2024-02-28T22:27:31.668Z <SystemController:null> Module SystemController v23331 [latest-24057]2024-02-28T22:27:31.673Z <Controller:CRIT> SyntaxError: Unexpected end of JSON input [-] SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at /opt/reactor/server/lib/Controller.js:464:51 at Array.forEach (<anonymous>) at SystemController._restoreEntities (/opt/reactor/server/lib/Controller.js:458:36) at new Controller (/opt/reactor/server/lib/Controller.js:45:43) at new SystemController (/opt/reactor/server/lib/SystemController.js:237:9) at /opt/reactor/server/lib/Controller.js:101:37 [latest-24057]2024-02-28T22:27:38.845Z <app:CRIT> SyntaxError: Unexpected end of JSON input [-] SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at IndividualFileStrategy.getDataObject (/opt/reactor/server/lib/IndividualFileStrategy.js:51:45) at DelayWriteCacheStrategy.getDataObject (/opt/reactor/server/lib/DelayWriteCacheStrategy.js:89:49) at Container.getDataObject (/opt/reactor/server/lib/Container.js:69:65) at Data.getInstance (/opt/reactor/server/lib/Data.js:45:179) at Rule.getRuleStates (/opt/reactor/server/lib/Rule.js:515:101) at Rule.getConditionState (/opt/reactor/server/lib/Rule.js:546:47) at new Rule (/opt/reactor/server/lib/Rule.js:371:47) at Rule.getInstance (/opt/reactor/server/lib/Rule.js:380:36) at /opt/reactor/server/lib/Engine.js:828:53 i18n: missing en-US language string: HomeAssistant on {0:q} may be an unsupported version. The reported version ({1}) has not been certified/tested with this version of Reactor and may cause errors. You must either modify your HomeAssistant install, or see if an update to Reactor has been made available. Trace: HomeAssistant on {0:q} may be an unsupported version. The reported version ({1}) has not been certified/tested with this version of Reactor and may cause errors. You must either modify your HomeAssistant install, or see if an update to Reactor has been made available. at _T (/opt/reactor/server/lib/i18n.js:614:37) at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:128:25) at HassController.sendWarning (/opt/reactor/server/lib/Controller.js:197:36) at /opt/reactor/server/lib/HassController.js:1133:374 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)How do I fix this?
-
This can happen if the container has a disorderly shutdown, or when you get a disk full condition. It looks like you have at least one broken entity metadata file, and possibly a broken rule.
To fix the state file, stop the Reactor container and remove the entire
storage/entities/reactor_systemsubdirectory. This data will simply be rebuilt, and it's harmless.The rule is another matter. Go into
storage/rulesand look for zero-length files. If you find any, delete them.Then restart Reactor. That should get you up and running again, but, you'll need to restore the damaged (now deleted) rules from a backup.
Edit: also, the messages are not entirely the expected rhythm, and I'm thinking you've redacted some messages. Please don't do that. For any and every error, I see to several lines (a dozen or more is good) in front of the error, without redaction. It seems a few messages that should accompany the error are missing, and these should have vital details that would make this process easier to interpret and let me give you much more concise instructions.
-
Thank you for the quick reply. I didn’t intentionally remove any logs. I copied whatever was showing as the container logs in portainer (100 lines?) without realising that there is a reactor log file. I’ve now included the logs from the log file for the latest restart below.
[latest-24057]2024-02-28T23:56:27.199Z <app:null> Reactor build latest-24057-e9add9f5 starting on v20.10.0 [latest-24057]2024-02-28T23:56:27.200Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #69057 SMP Fri Jan 12 17:02:28 CST 2024; locale (undefined) [latest-24057]2024-02-28T23:56:27.201Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-24057]2024-02-28T23:56:27.201Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-24057]2024-02-28T23:56:27.204Z <app:INFO> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-24057]2024-02-28T23:56:27.265Z <app:INFO> Loaded locale en-US for en-US [latest-24057]2024-02-28T23:56:27.269Z <Structure:null> Module Structure v23172 [latest-24057]2024-02-28T23:56:27.271Z <Capabilities:null> Module Capabilities v23331 [latest-24057]2024-02-28T23:56:27.301Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 24004 revision 1 [latest-24057]2024-02-28T23:56:27.337Z <Plugin:null> Module Plugin v22300 [latest-24057]2024-02-28T23:56:27.344Z <TimerBroker:null> Module TimerBroker v22283 [latest-24057]2024-02-28T23:56:27.347Z <Entity:null> Module Entity v22353 [latest-24057]2024-02-28T23:56:27.351Z <Controller:null> Module Controller v23069 [latest-24057]2024-02-28T23:56:27.368Z <default:null> Module Ruleset v22293 [latest-24057]2024-02-28T23:56:27.368Z <default:null> Module Rulesets v22146 [latest-24057]2024-02-28T23:56:27.376Z <GlobalExpression:null> Module GlobalExpression v23211 [latest-24057]2024-02-28T23:56:27.392Z <Predicate:null> Module Predicate v23093 [latest-24057]2024-02-28T23:56:27.396Z <AlertManager:null> Module AlertManager v22283 [latest-24057]2024-02-28T23:56:27.399Z <Rule:null> Module Rule v24057 [latest-24057]2024-02-28T23:56:27.402Z <GlobalReaction:null> Module GlobalReaction v22324 [latest-24057]2024-02-28T23:56:27.405Z <Engine:null> Module Engine v24023 [latest-24057]2024-02-28T23:56:27.422Z <httpapi:null> Module httpapi v24057 [latest-24057]2024-02-28T23:56:27.439Z <wsapi:null> Module wsapi v24057 [latest-24057]2024-02-28T23:56:27.440Z <app:NOTICE> Starting Structure... [latest-24057]2024-02-28T23:56:27.445Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping [latest-24057]2024-02-28T23:56:27.447Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController) [latest-24057]2024-02-28T23:56:27.494Z <TaskQueue:null> Module TaskQueue 21351 [latest-24057]2024-02-28T23:56:27.495Z <VeraController:null> Module VeraController v24050 [latest-24057]2024-02-28T23:56:27.545Z <Structure:INFO> Structure#1 loading controller interface hass (HassController) [latest-24057]2024-02-28T23:56:27.558Z <HassController:null> Module HassController v24048 [latest-24057]2024-02-28T23:56:27.799Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-24057]2024-02-28T23:56:27.804Z <DynamicGroupController:null> Module DynamicGroupController v22313 [latest-24057]2024-02-28T23:56:27.808Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-24057]2024-02-28T23:56:27.815Z <SystemController:null> Module SystemController v23331 [latest-24057]2024-02-28T23:56:28.493Z <SystemController:NOTICE> SystemController#reactor_system resetting (reactor_system capability updated) [latest-24057]2024-02-28T23:56:28.497Z <Structure:INFO> Starting controller VeraController#vera [latest-24057]2024-02-28T23:56:28.497Z <VeraController:NOTICE> VeraController#vera starting... [latest-24057]2024-02-28T23:56:28.506Z <Controller:INFO> VeraController#vera loaded vera capabilities ver 22253 rev 1 format 1 [latest-24057]2024-02-28T23:56:28.532Z <Controller:INFO> VeraController#vera loaded implementation data ver 23109 rev 1 format 1 [latest-24057]2024-02-28T23:56:28.532Z <Structure:INFO> Starting controller HassController#hass [latest-24057]2024-02-28T23:56:28.532Z <HassController:NOTICE> HassController#hass starting... [latest-24057]2024-02-28T23:56:28.535Z <Controller:INFO> HassController#hass loaded hass capabilities ver 23289 rev 1 format 1 [latest-24057]2024-02-28T23:56:28.555Z <Controller:INFO> HassController#hass loaded implementation data ver 24004 rev 3 format 1 [latest-24057]2024-02-28T23:56:28.555Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-24057]2024-02-28T23:56:28.564Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online. [latest-24057]2024-02-28T23:56:28.565Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-24057]2024-02-28T23:56:28.569Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. [latest-24057]2024-02-28T23:56:28.698Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members [latest-24057]2024-02-28T23:56:28.698Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty [latest-24057]2024-02-28T23:56:28.700Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [latest-24057]2024-02-28T23:56:28.700Z <HassController:WARN> HassController: implementation of capability battery_maintenance does not provide attribute state [latest-24057]2024-02-28T23:56:28.701Z <HassController:WARN> HassController: implementation of capability input_select.selector does not provide attribute values [latest-24057]2024-02-28T23:56:28.707Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.20.230:8123/api/websocket [latest-24057]2024-02-28T23:56:28.711Z <app:NOTICE> Starting HTTP server and API... [latest-24057]2024-02-28T23:56:28.714Z <httpapi:NOTICE> httpapi: starting HTTP service on port "8111" [latest-24057]2024-02-28T23:56:28.717Z <app:NOTICE> Starting Reaction Engine... [latest-24057]2024-02-28T23:56:28.717Z <Engine:INFO> Reaction Engine starting [latest-24057]2024-02-28T23:56:28.718Z <Engine:INFO> Checking rule sets... [latest-24057]2024-02-28T23:56:28.721Z <Engine:INFO> Checking rules... [latest-24057]2024-02-28T23:56:28.806Z <IndividualFileStrategy:ERR> [IndividualFileStrategy][IndividualFileStrategy#/var/reactor/storage/states] failed to read cs-rule-ll4rewlj in /var/reactor/storage/states/cs-rule-ll4rewlj.json: [SyntaxError] Unexpected end of JSON input [-] [latest-24057]2024-02-28T23:56:28.806Z <app:ERR> Failed to start engine: [SyntaxError] Unexpected end of JSON input [-] [latest-24057]2024-02-28T23:56:28.806Z <app:CRIT> SyntaxError: Unexpected end of JSON input [-] SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at IndividualFileStrategy.getDataObject (/opt/reactor/server/lib/IndividualFileStrategy.js:51:45) at DelayWriteCacheStrategy.getDataObject (/opt/reactor/server/lib/DelayWriteCacheStrategy.js:89:49) at Container.getDataObject (/opt/reactor/server/lib/Container.js:69:65) at Data.getInstance (/opt/reactor/server/lib/Data.js:45:179) at Rule.getRuleStates (/opt/reactor/server/lib/Rule.js:515:101) at Rule.getConditionState (/opt/reactor/server/lib/Rule.js:546:47) at new Rule (/opt/reactor/server/lib/Rule.js:371:47) at Rule.getInstance (/opt/reactor/server/lib/Rule.js:380:36) at /opt/reactor/server/lib/Engine.js:828:53 [latest-24057]2024-02-28T23:56:28.813Z <httpapi:NOTICE> httpapi: listening [latest-24057]2024-02-28T23:56:28.824Z <app:NOTICE> Starting WSAPI... [latest-24057]2024-02-28T23:56:28.824Z <wsapi:NOTICE> wsapi: starting version 24057 [latest-24057]2024-02-28T23:56:28.946Z <HassController:NOTICE> HassController#hass connected, starting protocol [latest-24057]2024-02-28T23:56:28.950Z <HassController:INFO> HassController#hass successful authentication with ws://192.168.20.230:8123; fetching initial data... [latest-24057]2024-02-28T23:56:28.955Z <HassController:INFO> HassController#hass Hass reports version "2024.2.5" location Home timezone Asia/Singapore state RUNNING safe_mode false [latest-24057]2024-02-28T23:56:28.960Z <HassController:ERR> HassController#hass reported Hass version "2024.2.5" is not supported! [latest-24057]2024-02-28T23:56:29.000Z <HassController:NOTICE> HassController#hass no signature match for sun.sun [latest-24057]2024-02-28T23:56:29.065Z <HassController:NOTICE> HassController#hass no signature match for fan.living_rm_fan [latest-24057]2024-02-28T23:56:29.066Z <HassController:NOTICE> HassController#hass no signature match for fan.dining_rm_fan [latest-24057]2024-02-28T23:56:29.066Z <HassController:NOTICE> HassController#hass no signature match for fan.mbr_fan [latest-24057]2024-02-28T23:56:29.066Z <HassController:NOTICE> HassController#hass no signature match for fan.br2_fan [latest-24057]2024-02-28T23:56:29.067Z <HassController:NOTICE> HassController#hass no signature match for fan.br3_fan [latest-24057]2024-02-28T23:56:29.076Z <HassController:NOTICE> HassController#hass no signature match for remote.rm_mini3_d5 [latest-24057]2024-02-28T23:56:29.077Z <HassController:NOTICE> HassController#hass no signature match for remote.rm_pro_f5 [latest-24057]2024-02-28T23:56:29.077Z <HassController:NOTICE> HassController#hass no signature match for remote.rm_mini3_b3 [latest-24057]2024-02-28T23:56:29.077Z <HassController:NOTICE> HassController#hass no signature match for remote.rm_pro_15 [latest-24057]2024-02-28T23:56:29.142Z <HassController:NOTICE> HassController#hass no signature match for update.us_8_60w [latest-24057]2024-02-28T23:56:29.143Z <HassController:NOTICE> HassController#hass no signature match for update.uap_nanohd [latest-24057]2024-02-28T23:56:29.156Z <HassController:NOTICE> HassController#hass no signature match for update.uap_ac_lite [latest-24057]2024-02-28T23:56:29.179Z <HassController:NOTICE> HassController#hass no signature match for fan.smartmi_2s_fan [latest-24057]2024-02-28T23:56:29.200Z <HassController:NOTICE> HassController#hass no signature match for update.eap615_wall_firmware_update [latest-24057]2024-02-28T23:56:29.207Z <HassController:NOTICE> HassController#hass no signature match for update.eap615_mbr_firmware_update [latest-24057]2024-02-28T23:56:29.213Z <Controller:INFO> HassController#hass 0 dead entities older than 86400000s purged [latest-24057]2024-02-28T23:56:29.220Z <Controller:NOTICE> Controller HassController#hass is now online. [latest-24057]2024-02-28T23:56:29.298Z <Controller:INFO> VeraController#vera 0 dead entities older than 86400000s purged [latest-24057]2024-02-28T23:56:29.301Z <Controller:NOTICE> Controller VeraController#vera is now online. [latest-24057]2024-02-28T23:56:29.302Z <DynamicGroupController:INFO> All controllers ready, setting up dynamic groups [latest-24057]2024-02-29T00:01:25.492Z <httpapi:INFO> httpapi: API request from ::ffff:127.0.0.1: GET /api/v1/alive [latest-24057]2024-02-29T00:05:32.389Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.20.220: GET /api/v1/lang [latest-24057]2024-02-29T00:05:32.590Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:05:34.507Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.20.220: GET /api/v1/systime [latest-24057]2024-02-29T00:06:10.134Z <wsapi:INFO> client "192.168.20.220#1" closed, code=1006, reason= [latest-24057]2024-02-29T00:06:20.158Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:06:26.166Z <httpapi:INFO> httpapi: API request from ::ffff:127.0.0.1: GET /api/v1/alive [latest-24057]2024-02-29T00:07:34.988Z <wsapi:INFO> client "192.168.20.220#2" closed, code=1006, reason= [latest-24057]2024-02-29T00:07:46.603Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:08:18.063Z <wsapi:INFO> client "192.168.20.220#3" closed, code=1006, reason= [latest-24057]2024-02-29T00:09:14.411Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:10:35.124Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.20.220: GET /api/v1/systime [latest-24057]2024-02-29T00:11:16.348Z <wsapi:INFO> client "192.168.20.220#4" closed, code=1006, reason= [latest-24057]2024-02-29T00:11:26.971Z <httpapi:INFO> httpapi: API request from ::ffff:127.0.0.1: GET /api/v1/alive [latest-24057]2024-02-29T00:16:27.973Z <httpapi:INFO> httpapi: API request from ::ffff:127.0.0.1: GET /api/v1/alive [latest-24057]2024-02-29T00:21:03.150Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.20.220: GET /api/v1/systime [latest-24057]2024-02-29T00:21:03.318Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:21:26.486Z <wsapi:INFO> client "192.168.20.220#5" closed, code=1006, reason= [latest-24057]2024-02-29T00:21:29.616Z <httpapi:INFO> httpapi: API request from ::ffff:127.0.0.1: GET /api/v1/alive [latest-24057]2024-02-29T00:24:53.554Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:25:03.217Z <wsapi:INFO> client "192.168.20.220#6" closed, code=1006, reason= [latest-24057]2024-02-29T00:25:58.102Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:26:03.789Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.20.220: GET /api/v1/systime [latest-24057]2024-02-29T00:26:03.902Z <wsapi:INFO> client "192.168.20.220#7" closed, code=1001, reason= [latest-24057]2024-02-29T00:26:04.461Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.20.220: GET /api/v1/lang [latest-24057]2024-02-29T00:26:04.669Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:26:07.368Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.20.220: GET /api/v1/systime [latest-24057]2024-02-29T00:26:32.453Z <httpapi:INFO> httpapi: API request from ::ffff:127.0.0.1: GET /api/v1/alive [latest-24057]2024-02-29T00:28:13.706Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:28:13.953Z <wsapi:INFO> client "192.168.20.220#8" closed, code=1006, reason= [latest-24057]2024-02-29T00:28:34.125Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:28:39.981Z <wsapi:INFO> client "192.168.20.220#9" closed, code=1006, reason= [latest-24057]2024-02-29T00:28:47.556Z <wsapi:INFO> client "192.168.20.220#10" closed, code=1006, reason= [latest-24057]2024-02-29T00:28:52.218Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:29:23.273Z <Notifier:null> Module Notifier v22283 [latest-24057]2024-02-29T00:29:23.314Z <default:null> Module NotifyAlert v21092 [latest-24057]2024-02-29T00:29:23.384Z <default:null> Module NotifySMTP v21083 [latest-24057]2024-02-29T00:29:23.393Z <default:null> Module NotifyProwl v21195 [latest-24057]2024-02-29T00:29:23.397Z <default:null> Module NotifyPushover v21195 [latest-24057]2024-02-29T00:29:23.402Z <default:null> Module NotifySyslog v21083 [latest-24057]2024-02-29T00:29:23.407Z <default:null> Module NotifyCallMeBot v21195 [latest-24057]2024-02-29T00:29:23.412Z <default:null> Module NotifyTelegram v21221 [latest-24057]2024-02-29T00:31:12.183Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.20.220: GET /api/v1/systime [latest-24057]2024-02-29T00:31:32.546Z <wsapi:WARN> wsapi: timed out waiting for ping reply (pong) from client "192.168.20.220#11" [latest-24057]2024-02-29T00:31:32.547Z <wsapi:INFO> client "192.168.20.220#11" closed, code=1006, reason= [latest-24057]2024-02-29T00:31:33.457Z <httpapi:INFO> httpapi: API request from ::ffff:127.0.0.1: GET /api/v1/alive [latest-24057]2024-02-29T00:31:39.848Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:32:31.496Z <wsapi:INFO> client "192.168.20.220#12" closed, code=1006, reason= [latest-24057]2024-02-29T00:33:34.831Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:36:13.198Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.20.220: GET /api/v1/systime [latest-24057]2024-02-29T00:36:34.075Z <httpapi:INFO> httpapi: API request from ::ffff:127.0.0.1: GET /api/v1/alive [latest-24057]2024-02-29T00:38:26.909Z <wsapi:INFO> client "192.168.20.220#13" closed, code=1001, reason= [latest-24057]2024-02-29T00:38:27.833Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.20.220: GET /api/v1/lang [latest-24057]2024-02-29T00:38:28.403Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:38:31.988Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.20.220: GET /api/v1/systime [latest-24057]2024-02-29T00:41:35.501Z <httpapi:INFO> httpapi: API request from ::ffff:127.0.0.1: GET /api/v1/alive [latest-24057]2024-02-29T00:42:57.382Z <wsapi:INFO> client "192.168.20.220#14" closed, code=1006, reason= [latest-24057]2024-02-29T00:43:13.705Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:43:32.393Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.20.220: GET /api/v1/systime [latest-24057]2024-02-29T00:44:00.527Z <wsapi:INFO> client "192.168.20.220#15" closed, code=1006, reason= [latest-24057]2024-02-29T00:44:35.635Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:45:46.136Z <wsapi:INFO> client "192.168.20.220#16" closed, code=1006, reason= [latest-24057]2024-02-29T00:46:36.540Z <httpapi:INFO> httpapi: API request from ::ffff:127.0.0.1: GET /api/v1/alive [latest-24057]2024-02-29T00:47:18.038Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:47:33.185Z <wsapi:INFO> client "192.168.20.220#17" closed, code=1005, reason= [latest-24057]2024-02-29T00:48:00.759Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:48:33.177Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.20.220: GET /api/v1/systime [latest-24057]2024-02-29T00:49:01.074Z <wsapi:INFO> client "192.168.20.220#18" closed, code=1006, reason= [latest-24057]2024-02-29T00:49:33.746Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.20.220 [latest-24057]2024-02-29T00:50:04.365Z <wsapi:INFO> client "192.168.20.220#19" closed, code=1006, reason=I deleted the “storage/entities/reactor_system” folder and restarted Reactor. The entity states are updated when viewing “entities”. But the states are not updated when viewing via the rules.
There were no 0 kb sized file in the rules folder for me to delete. I did find a zero sized file in states “cs-rule-ll4rewlj.json” but that corresponding rule “rule-ll4rewlj.json” was last modified in 2023. Should I delete the entire rules folder?
To restore the rules from a backup, do I just copy the files in?
-
I noticed the filename in the log. This file is indeed also 0kb. I deleted it and rector is now working fine.
[latest-24057]2024-02-28T23:56:28.806Z IndividualFileStrategy:ERR [IndividualFileStrategy][IndividualFileStrategy#/var/reactor/storage/states] failed to read cs-rule-ll4rewlj in /var/reactor/storage/states/cs-rule-ll4rewlj.json: [SyntaxError] Unexpected end of JSON input [-]
-
Thank you! That really helps. The zero-sized
storage/states/cs-rule-ll4rewlj.jsonis the only file you need to remove. Just stop the container, remove the file, and restart. That should clear it. The data in that file will be rebuilt. -
T toggledbits locked this topic on