Following on from my last thread, some progress has been made over the weekend.
With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system.
Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic.
Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work.
Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic.
Once that hurdle is sorted I'm torn between:
Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.)Decisions, decisions.
C
Afternoon, all.
In my continued attempts to virtualise my system, I'm in the last (I hope throes)
I don't fancy relying on Synology not to break more USB activities, so decided to set up ser2net on a Raspberry pi and plug in a spare Z-wave.me stick
So on the Raspberry pi: ser2net. yaml
catman@Zwave:/etc $ cat ser2net.yaml %YAML 1.1 --- # This is a ser2net configuration file, tailored to be rather # simple. # # Find detailed documentation in ser2net.yaml(5) # A fully featured configuration file is in # /usr/share/doc/ser2net/examples/ser2net.yaml.gz # # If you find your configuration more useful than this very simple # one, please submit it as a bugreport define: &banner \r\nser2net port \p device \d [\B] (Debian GNU/Linux)\r\n\r\n connection: &zwave0 # Bind to TCP port accepter: tcp,4000 enable: on options: kickolduser: true # Ensure mDNS is disabled mdns: false connector: serialdev, /dev/ttyACM0,115200N81,nobreak,localAnd if I telnet to it from anywhere:
catman@ChrisMBP15-2018 ~ % telnet 192.168.70.128 4000 Trying 192.168.70.128... Connected to 192.168.70.128. Escape character is '^]'.Which makes me think that ser2net is doing its thing.
Now in my virtualised Z-wave server I have this:
Screenshot 2025-04-10 at 17.36.52.png
(I've tried with a colon and a space between the ip and the port)
The result:
An unexpected error occurred during loading data. Try to reload the page. Please check 1.) if the controller is plugged in correctly, 2.) that in the app 'Z-Wave Network Access' the right port is entered (UZB: '/dev/ttyACM0', RaZberry shield: '/dev/ttyAMA0', UZB-Windows: '\\.\COM3', Z-Stick: '/dev/ttyUSB0', embedded boxes: '/dev/ttyS0' or '/dev/ttyS1') 3.) the app is aktiv. If not you could activate it under Menu > Apps > Active or add a new one under Menu > Apps > Local. The Setting 'Expert View' needs to be active under Menu > My Settings.Any pointers as to what I'm doing wrong?
TIA!
C
Hi guys,
Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular.
Maybe there are better ways to organize my rule sets.
I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
I have installed MSR on a RP5 bare metal and then copied the config and store files. Everything seems to be on the RP5 but I am missing all global expression and I don't see the controller time.
Screenshot 2025-04-06 201446.png
My browser is Microsoft Edge Version 135.0.3179.54 (Official build) (64-bit)
I have probably done something stupid or missed a step but I am stuck.
Thanks for any help.
Hi,
It seems that the widget deletion does not work. I tried to drag the widget to the left (as explained in here https://smarthome.community/topic/1071/deleting-widgets?_=1744037333660)
but it does not delete it. Anyone else experiencing the same problem?
Also the landing page after login is empty and seems be have some JS issues on the dev console:
Screenshot from 2025-04-07 18-06-19.png
fd7f0424-debb-49d3-86d8-9a3b09ad3868-image.png
Using dockerized version of Reactor (Multi-hub) latest-25082-3c348de6 on Chromium 135.0.7049.52 (Official Build) snap (64-bit)
br,
mgvra
Good day all,
I have an notification set up for my washing machine to let me know when it's complete. I have a templete sensor set up in HAAS to let me know if it's Washing, in Standby, or off, based upon the power consumption (Shelly 1PM on outlets)
The MSR code is relatively simple. I have a built in false positive attribute for if MSR gets rebooted, because I would suddenly get tons of notifications when I upgraded MSR.
6774565a-06cc-443f-99c1-e71301b33d83-image.png
What I'm trying to introduce, is a way to verify that I just didn't bump the knob on the washing machine when transferring loads from the washer to the dryer, which turns on the display and brings the power above the Standby threshold.
The power goes up to 3.7W for about 4 minutes if the selector knob is bumped/turned.
What would the best way to do this be? I have most of my MSR code set up for a couple of years now, and my coding logic is struggling a bit.
I think I need a power threshold to be substained for a minimum time period (say 2 or 3 minutes, above 10W), before the other triggers can act. What would the best way to do that be?
Running: latest-25082-3c348de6
Fedora 41 Server
HAAS:
Core
2025.3.4
Supervisor
2025.03.4
Operating System
15.1
Frontend
20250306.0
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.I have the following yaml configuration in local_mqtt_devices file
x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }'While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Hi!
I get this message when I'm on the status tab:
System Configuration Check
The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds.
I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6.
HA versions are:
Core 2025.3.4
Supervisor 2025.03.4
Operating System 15.1
I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version.
Do anyone know what I can try?
Thanks in advance!
Let's Be Careful Out There (Hill Street reference...) 🙂
/Fanan
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB.
While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed.
So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response.
While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits
Thanks!
Hi ,
I'm on
-Reactor (Multi-hub) latest-25067-62e21a2d
-Docker on Synology NAS
-ZWaveJSUI 9.31.0.6c80945
Problem with ZwaveJSUI:
When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white.
I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui.
I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb".
After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color.
This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite.
x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33}The "cold white" and "warm white" settings interfer with the rgb color settings.
Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white
are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white.
So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have
x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColorIn zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set.
x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this?
x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33}Thanks in advance.
Good day all,
I have a reaction set up, that I use for both troubleshooting and changing home modes when one of my family members either arrive or are leaving. I use the companion app for HAAS on our iPhones, and HAAS reports if the person associated with the iPhone enters or leaves the geofenced area around my home. I'm sure most MSR and HAAS users are familiar with this.
I use this rule set mainly as a condition for other rules, however, as part of troubleshooting, a notification is sent through HAAS to the companion app when the rule becomes true. The problem is that I'm getting notifications now for both arriving and departing simultaneously.
96b3f7db-ba09-499e-a78c-86903b603857-image.png
36903cdd-a87f-473b-82ef-af9ef96d3c44-image.png It used to work fine as intended. I'm not sure exactly when it changed, but now I'm getting two notifications when either of these conditions change.
Any idea what could be happening?
Edit:
Running: latest-25082-3c348de6, bare-metal Linux
ZWaveJSControllerr [0.1.25082]
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem?
I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Similarly as for local expressions, global expressions evaluate and update fine when getEntity(...) structure is used. However, at least when certain functions are in use, expressions do not update.
Consider the following test case:
Screenshot 2025-03-13 at 16.29.42.png
Even though auto-evaluation is active, value does not change (it changes only if that expression is manually run). MSR restarts do not help.
Screenshot 2025-03-13 at 16.31.43.png
Note: Tested using build 25067 on Docker. I have also a PR open (but couldn't now get details or PR number as my Mantis account was somehow expired?).
Trying to understand what cause a local expresssion to be evaluated. I have read the manual but I am still not clear about it. Using the test rule below, I can see in the log that the rule is being automatically evaluated every time the temperature entity is changing. That is great...
What I am trying to understand is why the expression is not evaluated based on time as well since the "case" statement has time dependencies.
Any help would be appreciated
I have the following test rule:
eba6a3ea-ff61-4610-88c9-9b9864f11ff8-Screenshot 2025-01-21 095244.png
2d9c1ff5-7b73-4005-b324-9029c2709db9-Screenshot 2025-01-21 095302.png
Here is the expressioncode:
vFrom1 = "09:25:00", vFrom2 = "09:30:00", vFrom3 = "09:41:00", vTo = "10:55:00", # Get current time (format HH:MM:SS) vToDay = strftime("%H:%M:%S"), #Get current house temperature CurrentHouseTemp = getEntity( "hass>Thermostat2 " ).attributes.temperature_sensor.value, case when CurrentHouseTemp <= 19 and vToDay >= vFrom1 && vToDay <= vTo: "true1" # From1 when CurrentHouseTemp <= 20 and vToDay >= vFrom2 && vToDay <= vTo: "true2" # From2 when CurrentHouseTemp < 26 and vToDay >= vFrom3 && vToDay <= vTo: "true3" # From3 else "false" endI am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved.
The Runtime Error is different in the two browsers
Safari v18.3
Google Chrome 133.0.6943.142
TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.Steps to reproduce:
Click the pencil to edit a global reaction with a group.
Click the Exit button.
Runtime error appears.
or
Click Create Reaction
Click Add Action
Select Group
Add Condition such as Entity Attribute.
Add an Action.
Click Save
Click Exit
Runtime error appears.
I don’t know how long the error has been there as I haven’t edited the global reaction in a long time.
Reactor (Multi-hub) latest-25060-f32eaa46
Docker
Mac OS: 15.3.1
Thanks
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons.
I have not created a global expression for some times and just noticed this while doing some clean-up.
I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success.
Here's what the log shows.
[latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" }Reactor latest-25067-62e21a2d
Docker on Synology NAS
Hello all, after seeing Catman's posts about their disaster recovery and move to Docker I took that as a sign to migrate everything (aside from HA) to Docker. After a small learning curve I had Docker+Portainer up and running in a few days.
Instead of using named Volumes I opted to use Bind Mounts so I can easily edit conf files and any other file needed. I do understand the nuances that come with bind mounts, such as migration to a different host may require changing file structures, the possibility of someone editing the bind mount files and permissions but to me those aren't too big of a deal.
My question is what is the best way to keep a back up of these bind mounts? I currently have them stored in the /etc directory in another directory named on a per container basis. I was thinking to move it all to a /home/user/docker/ directory so that I can use a simple cp command to my mounted SMB share to backup all the container data files. Anyone else do it differently?
Side note: I finally got to flex the benefits of Docker with updating Reactor.. it was dead simple. I had no idea what I was missing out on lol!
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method.
This was prompted by yesterday's fun and games with my ISP.
I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone)
I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions?
TIA
C
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 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?
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?
Hi,
Took me a while to realise the issue here. Just want to share to save others the time of trying to figure out what's wrong.
Home Assistant integration with non-admin user (access token) will caused the Home Assistant status in Reactor to show as down. Entity info from Home Assistant, however, is being updated. But Reactor is unable to execute any reactions.
If the user is changed to an admin user in Home Assistant, the status is changed to up and reactions work.