Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. MSR “Unexpected end of JSON input” after container update
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
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.
Multi-System Reactor
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor

MSR “Unexpected end of JSON input” after container update

Scheduled Pinned Locked Moved Multi-System Reactor
5 Posts 2 Posters 786 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    sykong
    wrote on last edited by
    #1

    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?

    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by toggledbits
      #2

      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_system subdirectory. This data will simply be rebuilt, and it's harmless.

      The rule is another matter. Go into storage/rules and 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.

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      S 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        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_system subdirectory. This data will simply be rebuilt, and it's harmless.

        The rule is another matter. Go into storage/rules and 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.

        S Offline
        S Offline
        sykong
        wrote on last edited by
        #3

        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?

        1 Reply Last reply
        0
        • S Offline
          S Offline
          sykong
          wrote on last edited by
          #4

          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 [-]

          1 Reply Last reply
          0
          • toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            wrote on last edited by
            #5

            Thank you! That really helps. The zero-sized storage/states/cs-rule-ll4rewlj.json is 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.

            Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

            1 Reply Last reply
            0
            • toggledbitsT toggledbits locked this topic on
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            Recent Topics

            • Copying a global reaction
              toggledbitsT
              toggledbits
              0
              3
              78

            • [HowTo] Using HABridge with Reactor
              CatmanV2C
              CatmanV2
              0
              9
              385

            • [Reactor] Bug when sending MQTT boolean payloads
              toggledbitsT
              toggledbits
              0
              4
              130

            • Genuinely impressed with Zigbee and HA / Reactor
              therealdbT
              therealdb
              1
              8
              297

            • Difficulty defining repeating annual period
              G
              gwp1
              0
              5
              97

            • Need help with sequence
              therealdbT
              therealdb
              0
              3
              61

            • Possible feature request?
              therealdbT
              therealdb
              0
              5
              161

            • Logic Assistance: Exterior Lights on when Illuminance Below Threshold
              CatmanV2C
              CatmanV2
              0
              11
              337

            • Time series documentation
              tunnusT
              tunnus
              0
              11
              389

            • MQTT templates for ZIgbee scene controller, or a better way?
              CatmanV2C
              CatmanV2
              0
              3
              158

            • Reset a delay
              CatmanV2C
              CatmanV2
              0
              8
              218
            Powered by NodeBB | Contributors
            Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Unsolved