I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.
Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.
( *Drag & drop of rule conditions have never worked on a mobile)
Hi @toggledbits,
I have lots of logs with this:
<Engine:ERR> Assignment to alarm ignored -- expression-driven global cannot be set by assignmentAny hints to where look at to avoid this? Thanks.
Hi @toggledbits
I'd like to update my controllers with these new features, but I'm struggling to find any guidance in the docs - and in general to understand the context.
Could you please elaborate more? Thanks.
I have the following ACL defined:
groups: admin: users: - admin applications: true api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: trueAnd I have authenticated to MSR as "admin" user. However, I'm getting "access denied" when trying to access http://*******:8111/api/v1/log
So what I'm missing, is my ACL incorrectly defined?
Using build 24302 on Docker.
Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.
Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce
A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.
Hi!
In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
Thanks!
/Fanan
Hi
I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.
They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.
This is how that device looks in the Ezlo API.
Devices Info:
_id: "10696001" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "level_sensor" subcategory: "" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Digital" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696001" deviceId: "10696001" hasGetter: true hasSetter: false name: "smoke_density" show: true valueType: "substance_amount" scale: "parts_per_million" value: 2.7472610473632812 valueFormatted: "2.75" status: "idle"There is also an Analog Gas sensor that one did import in to MSR OK.
68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png
Devices Info:
_id: "10696000" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "security_sensor" subcategory: "gas" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Analog" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696000" deviceId: "10696000" hasGetter: true hasSetter: false name: "gas_alarm" show: true valueType: "token" enum: 0: "no_gas" 1: "combustible_gas_detected" 2: "toxic_gas_detected" 3: "unknown" valueFormatted: "no_gas" value: "no_gas" status: "idle"And this is how this MQ2 Gas Sensor looks like on their dashboard:
Digital
cb77dfa3-4af5-4d06-9635-89207a716a89-image.png
Analog
4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png
They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!
And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.
THANKS.
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.A couple of things for you @toggledbits, since you mentioned that this release has new features and some tweaks are expected.
Local expressions cannot be deleted. Pushing the X button has no effect for me.
When cloning an entity action, the result is strange (first is cloned one, second is the original action):
a92ea094-9e2c-4aaa-bf47-2d07a6ffdbd0-image.png
When changing the action on the cloned element, the params are added to the original one. See screenshot:
92ac3011-83c8-466b-bd23-47d483ad7a52-image.png
Dark theme has a couple of strange contrasts. One is visible in the previous screenshots (white text on yellow background). Another one is in groups (blue text on blue background):
9b3c4988-53ef-44e6-9672-30e744cacb75-image.png
Overall, I found blue, yellow, red and green (in buttons and forms) to be too bright.
On the bright side:
I love the new script action: thank you! The dark theme is a great start to avoid getting blinded at night I promise I'll try very soon the new features around actions. Thanks!@toggledbits
I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:
I followed the new directions about npm
npm i --no-save --no-package-lock --omit dev
Any idea what the issue is?
Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)
Things I have tried:
Hard refresh
Different browser
Different computer
Restarting Reactor
Failed troubleshooting attempts:
No errors in Chrome console
No relevant errors in Reactor log (can still PM the full log file)
Reactor version: latest-24293-ea42a81d
Hardware: Odroid N2+
Linux version: Ubuntu 24.04.1 LTS
3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled
ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled
Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.
What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?
Running:
Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]HAAS:
RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0
Hi!
Is it possible to generate two additional log files, the first being the replica of what is displayed on screen by the Rule History widgets and the other with Recently Changed Entities?
And could I configure the generation of one file per day, and delete the older ones? For example, store the last 5 days?
And being more ambitious, does Windget have an icon to open these TXT files in the navigated?
Well, we're approaching Christmas, so here's my request to Santa Claus @toggledbits 🙂
Hi @toggledbits
I'm working on a controller to generate llm response from a prompt in reactor. I have http response coming thru an http request action at the moment, capturing the response inside a local variable. So, it's practically sync.
I want to create a controller, so I don't have to rely on a proxy (and have a simpler architecture), and duplicate absurd http actions, but AFAIK in the current implementation, actions are async only. But if I have multiple requests going on, I cannot be sure what it's really inside an attribute. I also thought that something like a correlation id when sending the request could be used to identity multiple responses, but I wanted to double check with you before starting with something too complicated. I also noticed that some actions in home assistant (ie forecast) are sync and I'm wondering if you have any plan or hint to address this situation. Thanks.
Thanks.
@togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.
Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.
Thanks in advance.
Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3
@toggledbits I have noticed after upgrading both Reactor and ZWaveJSController to version 24257 that two of my devices/entities, TILT-ZWAVE2.5-ECO and Zooz ZSE18, had their entity re-named in an unusual way and also appears to be duplicated.
Reactor version 24257
ZWaveJSController version 24257
Z-Wave JS UI version 9.18.1
zwave-js version 13.2.0
Vestibule Motion Sensor State attributes/partial screenshot of entities it created. All entities have the same attributes.
motion_sensor.state=true x_zwave_values.Notification_Home_Security_Motion_sensor_status=8 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=23 zwave_device.valueId=[113,"Notification","Home Security","Home Security","Motion sensor status","Motion sensor status"] zwave_device.version_info=nullTilt Sensor Door State and Tilt Sensor Door State Simple attributes/partial screenshot of entities it created. All entities have similar attributes with exception of x_zwave_values.Notification_Access_Control_Door_State = 22 or 23.
tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state_simple=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state_simple=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=nullI'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor
GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests 🙂
Reactor Start - System Crash/Restart
-
Hello All -
I upgraded my OS to Ubuntu 20.04 today and have been regretting it for several hours. I have most of my system up. However, I've found that, when I start Reactor, it panics / reboots my OS. I've included the syslog during startup below. There's a benign message about not finding a Vera device just before the reboot but that's it.Needless to say, I've learned my lesson regarding OS upgrades.
Bare metal Linux / Ubuntu 20.04 (Running inside VirtualBox)
Reactor Version: stable-22337-1a0a685fDec 30 19:33:46 homeauto03 systemd[1]: Started Multi System Reactor. Dec 30 19:33:46 homeauto03 weewx[6592] INFO weewx.restx: Wunderground-RF: Published record 2022-12-30 19:33:46 EST (1672446826) Dec 30 19:33:46 homeauto03 node[7240]: Reactor stable-22337-1a0a685f app 22328 configuration from /home/tbully/reactor/config Dec 30 19:33:46 homeauto03 node[7240]: NODE_PATH /home/tbully/reactor Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.745Z <app:null> Reactor build stable-22337-1a0a685f starting on v17.9.0 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.746Z <app:null> Process ID 7240 user/group 1000/1000; bare-metal; platform linux/x64 #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022; locale en_CA.UTF-8 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.746Z <app:null> Basedir /home/tbully/reactor; data in /home/tbully/reactor/storage Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.747Z <app:null> NODE_PATH=/home/tbully/reactor Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.764Z <Structure:null> Module Structure v22323 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.765Z <Capabilities:null> Module Capabilities v22283 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.819Z <Plugin:null> Module Plugin v22300 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.827Z <TimerBroker:null> Module TimerBroker v22283 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.831Z <Entity:null> Module Entity v22314 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.835Z <Controller:null> Module Controller v22323 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.847Z <default:null> Module Ruleset v22293 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.848Z <default:null> Module Rulesets v21096 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.854Z <GlobalExpression:null> Module GlobalExpression v21333 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.864Z <Predicate:null> Module Predicate v22305 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.867Z <AlertManager:null> Module AlertManager v22283 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.869Z <Rule:null> Module Rule v22335 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.872Z <GlobalReaction:null> Module GlobalReaction v22320 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.873Z <Engine:null> Module Engine v22320 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.877Z <httpapi:null> Module httpapi v22337 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.886Z <wsapi:null> Module wsapi v22320 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.949Z <TaskQueue:null> Module TaskQueue 21351 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.950Z <VeraController:null> Module VeraController v22325 Dec 30 19:33:47 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:47.200Z <HassController:null> Module HassController v22334 Dec 30 19:33:48 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:48.294Z <SystemController:null> Module SystemController v22306 Dec 30 19:33:48 homeauto03 weewx[6592] INFO weewx.restx: Wunderground-RF: Published record 2022-12-30 19:33:48 EST (1672446828) Dec 30 19:33:49 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:49.110Z <Rule:CRIT> ReferenceError: Can't find entity "vera>device_368" [-] Dec 30 19:33:49 homeauto03 node[7240]: ReferenceError: Can't find entity "vera>device_368" Dec 30 19:33:49 homeauto03 node[7240]: at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:366:27) Dec 30 19:33:49 homeauto03 node[7240]: at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106) Dec 30 19:33:49 homeauto03 node[7240]: at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47) Dec 30 19:33:49 homeauto03 node[7240]: at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37) Dec 30 19:33:49 homeauto03 node[7240]: at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54) Dec 30 19:33:49 homeauto03 node[7240]: at async /home/tbully/reactor/server/lib/Rule.js:830:17 Dec 30 19:33:49 homeauto03 systemd[1]: Stopping Session 14 of User tbully... -
I have the logs but can't find a way to upload them. I don't have permissions to upload a file and if I paste it in here it says the post is too large.
Here's a few pieces:
[stable-22337]2022-12-31T00:33:46.745Z <app:null> Reactor build stable-22337-1a0a685f starting on v17.9.0 [stable-22337]2022-12-31T00:33:46.746Z <app:null> Process ID 7240 user/group 1000/1000; bare-metal; platform linux/x64 #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022; locale en_CA.UTF-8 [stable-22337]2022-12-31T00:33:46.746Z <app:null> Basedir /home/tbully/reactor; data in /home/tbully/reactor/storage [stable-22337]2022-12-31T00:33:46.747Z <app:null> NODE_PATH=/home/tbully/reactor [stable-22337]2022-12-31T00:33:46.750Z <app:INFO> Configured locale (undefined); selected locale(s) en_CA.UTF-8 [stable-22337]2022-12-31T00:33:46.761Z <app:INFO> Loaded locale en-US [stable-22337]2022-12-31T00:33:46.764Z <Structure:null> Module Structure v22323 [stable-22337]2022-12-31T00:33:46.765Z <Capabilities:null> Module Capabilities v22283 [stable-22337]2022-12-31T00:33:46.819Z <Plugin:null> Module Plugin v22300 [stable-22337]2022-12-31T00:33:46.827Z <TimerBroker:null> Module TimerBroker v22283 [stable-22337]2022-12-31T00:33:46.831Z <Entity:null> Module Entity v22314 [stable-22337]2022-12-31T00:33:46.835Z <Controller:null> Module Controller v22323 [stable-22337]2022-12-31T00:33:46.847Z <default:null> Module Ruleset v22293 [stable-22337]2022-12-31T00:33:46.848Z <default:null> Module Rulesets v21096 [stable-22337]2022-12-31T00:33:46.854Z <GlobalExpression:null> Module GlobalExpression v21333 [stable-22337]2022-12-31T00:33:46.864Z <Predicate:null> Module Predicate v22305 [stable-22337]2022-12-31T00:33:46.867Z <AlertManager:null> Module AlertManager v22283 [stable-22337]2022-12-31T00:33:46.869Z <Rule:null> Module Rule v22335 [stable-22337]2022-12-31T00:33:46.872Z <GlobalReaction:null> Module GlobalReaction v22320 [stable-22337]2022-12-31T00:33:46.873Z <Engine:null> Module Engine v22320 [stable-22337]2022-12-31T00:33:46.877Z <httpapi:null> Module httpapi v22337 [stable-22337]2022-12-31T00:33:46.886Z <wsapi:null> Module wsapi v22320 [stable-22337]2022-12-31T00:33:46.887Z <app:NOTICE> Starting Structure... [stable-22337]2022-12-31T00:33:46.890Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping [stable-22337]2022-12-31T00:33:46.892Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController) [stable-22337]2022-12-31T00:33:46.949Z <TaskQueue:null> Module TaskQueue 21351 [stable-22337]2022-12-31T00:33:46.950Z <VeraController:null> Module VeraController v22325 [stable-22337]2022-12-31T00:33:47.193Z <Structure:INFO> Structure#1 loading controller interface hass (HassController) [stable-22337]2022-12-31T00:33:47.200Z <HassController:null> Module HassController v22334 [stable-22337]2022-12-31T00:33:48.290Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [stable-22337]2022-12-31T00:33:48.294Z <SystemController:null> Module SystemController v22306 [stable-22337]2022-12-31T00:33:48.297Z <Structure:INFO> Starting controller VeraController#vera [stable-22337]2022-12-31T00:33:48.298Z <VeraController:NOTICE> VeraController#vera starting... [stable-22337]2022-12-31T00:33:48.304Z <Controller:INFO> VeraController#vera loaded vera capabilities ver 22253 rev 1 format 1 [stable-22337]2022-12-31T00:33:48.341Z <Controller:INFO> VeraController#vera loaded implementation data ver 22280 rev 8 format 1 [stable-22337]2022-12-31T00:33:48.341Z <Structure:INFO> Starting controller HassController#hass [stable-22337]2022-12-31T00:33:48.341Z <HassController:NOTICE> HassController#hass starting... [stable-22337]2022-12-31T00:33:48.343Z <Controller:INFO> HassController#hass loaded hass capabilities ver 22312 rev 2 format 1 [stable-22337]2022-12-31T00:33:48.354Z <Controller:INFO> HassController#hass loaded implementation data ver 22335 rev 1 format 1 [stable-22337]2022-12-31T00:33:48.354Z <Structure:INFO> Starting controller SystemController#reactor_system [stable-22337]2022-12-31T00:33:48.359Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. [stable-22337]2022-12-31T00:33:48.518Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members [stable-22337]2022-12-31T00:33:48.518Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty [stable-22337]2022-12-31T00:33:48.519Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [stable-22337]2022-12-31T00:33:48.520Z <VeraController:NOTICE> VeraController#vera updating capabilities for system entity System#vera>system [stable-22337]2022-12-31T00:33:48.525Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.34.17:8123/api/websocket [stable-22337]2022-12-31T00:33:48.529Z <app:NOTICE> Starting HTTP server and API... [stable-22337]2022-12-31T00:33:48.530Z <httpapi:NOTICE> Starting HTTP API v1 22337 on http://192.168.34.:8111 [stable-22337]2022-12-31T00:33:48.533Z <app:NOTICE> Starting Reaction Engine... [stable-22337]2022-12-31T00:33:48.534Z <Engine:INFO> Reaction Engine starting [stable-22337]2022-12-31T00:33:48.534Z <Engine:INFO> Checking rule sets... [stable-22337]2022-12-31T00:33:48.539Z <Engine:INFO> Checking rules...```[stable-22337]2022-12-31T00:33:49.745Z Rule:INFO Master Closet Motion Battery Low (rule-grp17k28ehz in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.761Z Rule:ERR Rule#rule-grp17k28qlp trigger evaluation failed: [ReferenceError] Can't find entity "vera>device_368" [-]
[stable-22337]2022-12-31T00:33:49.762Z Rule:CRIT ReferenceError: Can't find entity "vera>device_368" [-]
ReferenceError: Can't find entity "vera>device_368"
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:366:27)
at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106)
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47)
at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37)
at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54)
at async /home/tbully/reactor/server/lib/Rule.js:830:17
[stable-22337]2022-12-31T00:33:49.762Z Rule:INFO Panic Button Battery Low (rule-grp17k28qlp in Battery Checks) evaluated; trigger state changed ((null)), but rule state remains NULL
[stable-22337]2022-12-31T00:33:49.762Z Rule:INFO Panic Button Battery Low (rule-grp17k28qlp in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Office Motion Battery Low (rule-grp17k28znh in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Office Motion Battery Low (rule-grp17k28znh in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Door Battery Low (rule-grp17k29vsx in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Door Battery Low (rule-grp17k29vsx in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Motion Battery Low (rule-grp17k2abok in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Motion Battery Low (rule-grp17k2abok in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Flood Battery Low (rule-grp17k2am7t in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.764Z Rule:INFO Upstairs Bath Flood Battery Low (rule-grp17k2am7t in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.764Z Rule:INFO Upstairs Hall Motion Battery Low (rule-grp17k2b0ha in Battery Checks) evaluated; trigger state unchanged (true); rule state remains SET
[stable-22337]2022-12-31T00:33:49.764Z Rule:INFO Upstairs Hall Motion Battery Low (rule-grp17k2b0ha in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.773Z Rule:ERR Rule#rule-grp17k2iotv trigger evaluation failed: [ReferenceError] Can't find entity "vera>device_543" [-]
[stable-22337]2022-12-31T00:33:49.773Z Rule:CRIT ReferenceError: Can't find entity "vera>device_543" [-]
ReferenceError: Can't find entity "vera>device_543"
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:366:27)
at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106)
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47)
at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37)
at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54)
at async /home/tbully/reactor/server/lib/Rule.js:830:17
[stable-22337]2022-12-31T00:33:49.773Z Rule:INFO Home Button Battery Low (rule-grp17k2iotv in Battery Checks) evaluated; trigger state changed ((null)), but rule state remains NULL
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Home Button Battery Low (rule-grp17k2iotv in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Sump Pump Flood Detected (rule-grp17k301y1 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Sump Pump Flood Detected (rule-grp17k301y1 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Rec Room Flood Detected (rule-grp17k30cm0 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Rec Room Flood Detected (rule-grp17k30cm0 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Office Flood Detected (rule-grp17k30mqa in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Office Flood Detected (rule-grp17k30mqa in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Laundry Flood Detected (rule-grp17k31kf1 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Laundry Flood Detected (rule-grp17k31kf1 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Half-Bath Flood Detected (rule-grp17k31z13 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Half-Bath Flood Detected (rule-grp17k31z13 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Upstairs Bath Flood Detected (rule-grp17k327c0 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.776Z Rule:INFO Upstairs Bath Flood Detected (rule-grp17k327c0 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.776Z Rule:INFO Garage Tilt Sensor Battery Low (rule-grp17k3frdb in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.776Z Rule:INFO Garage Tilt Sensor Battery Low (rule-grp17k3frdb in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.782Z Rule:ERR Rule#rule-grp17k3ui8q trigger evaluation failed: [ReferenceError] Entity Vera (vera>system) has no attribute "x_vera_sys.reloads" [-]
[stable-22337]2022-12-31T00:33:49.782Z Rule:CRIT ReferenceError: Entity Vera (vera>system) has no attribute "x_vera_sys.reloads" [-]
ReferenceError: Entity Vera (vera>system) has no attribute "x_vera_sys.reloads"
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:373:27)
at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106)
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47)
at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37)
at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54)
at async /home/tbully/reactor/server/lib/Rule.js:830:17
[stable-22337]2022-12-31T00:33:49.782Z Rule:INFO LuupReload (rule-grp17k3ui8q in House Reactor) evaluated; trigger state changed ((null)), but rule state remains NULL
[stable-22337]2022-12-31T00:33:49.783Z Rule:INFO LuupReload (rule-grp17k3ui8q in House Reactor) started
[stable-22337]2022-12-31T00:33:49.783Z Rule:INFO VeraSecureTriggered (rule-grplg89w7x in House Reactor) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.783Z Rule:INFO VeraSecureTriggered (rule-grplg89w7x in House Reactor) started
[stable-22337]2022-12-31T00:33:49.783Z Rule:INFO TurnOffPantryLights (rule-grplt8fpma in Basement Reactor) evaluated; trigger state unchanged (false); rule state remains RESET[stable-22337]2022-12-31T00:33:49.902Z <Rule:INFO> Garage Lights Off - After Auto On (rule-grpp2yoxfg in Garage Reactor) evaluated; trigger state unchanged (false); rule state remains RESET [stable-22337]2022-12-31T00:33:49.902Z <Rule:INFO> Garage Reactor (rule-492 in Garage Reactor) evaluation complete [stable-22337]2022-12-31T00:33:49.902Z <Rule:INFO> Garage Lights Off - After Auto On (rule-grpp2yoxfg in Garage Reactor) evaluation complete [stable-22337]2022-12-31T00:33:49.907Z <httpapi:NOTICE> httpapi: listening [stable-22337]2022-12-31T00:33:49.921Z <app:NOTICE> Starting WSAPI... [stable-22337]2022-12-31T00:33:49.922Z <wsapi:NOTICE> wsapi: starting version 22320 [stable-22337]2022-12-31T00:33:50.112Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "12/30/2022, 7:33:50 PM" (TZ offset -300 mins from UTC) [stable-22337]2022-12-31T00:33:50.120Z <app:NOTICE> Shutdown signal (SIGTERM) received. Stopping Reaction Engine... [stable-22337]2022-12-31T00:33:50.121Z <app:NOTICE> Closing APIs... [stable-22337]2022-12-31T00:33:50.121Z <wsapi:NOTICE> wsapi: closing... [stable-22337]2022-12-31T00:33:50.121Z <httpapi:NOTICE> HTTP API closing... [stable-22337]2022-12-31T00:33:50.121Z <app:NOTICE> Stopping Engine... [stable-22337]2022-12-31T00:33:50.128Z <Rule:NOTICE> Turn Off Upstairs Hall Light (rule-grprsxsoqm in UpstairsHall Reactor) stopping [stable-22337]2022-12-31T00:33:50.129Z <Rule:NOTICE> Run Hot Water Recirculation (rule-l7ey8s4w in House Reactor) stopping [stable-22337]2022-12-31T00:33:50.130Z <Rule:NOTICE> Run Fans (rule-l6pi77c2 in House Reactor) stopping [stable-22337]2022-12-31T00:33:50.130Z <Rule:NOTICE> VeraSecureTriggered (rule-grplg89w7x in House Reactor) stopping[stable-22337]2022-12-31T00:33:50.329Z <Rule:NOTICE> Half-Bath Flood Detected (rule-grp17k31z13 in Flood Checks) stopped [stable-22337]2022-12-31T00:33:50.330Z <Rule:NOTICE> Upstairs Bath Flood Detected (rule-grp17k327c0 in Flood Checks) stopped [stable-22337]2022-12-31T00:33:50.417Z <Engine:NOTICE> [Engine]Engine#1 has shut down. [stable-22337]2022-12-31T00:33:50.417Z <app:NOTICE> Closing Structure... [stable-22337]2022-12-31T00:33:50.418Z <Structure:INFO> Structure#1 Stopping controllers... [stable-22337]2022-12-31T00:33:50.418Z <Controller:NOTICE> VeraController#vera stopping [stable-22337]2022-12-31T00:33:50.524Z <HassController:NOTICE> HassController#hass stopping [stable-22337]2022-12-31T00:33:50.526Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error] WebSocket was closed before the connection was established [-] [stable-22337]2022-12-31T00:33:50.526Z <HassController:WARN> HassController#hass ws error code (undefined) [stable-22337]2022-12-31T00:33:50.526Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error] WebSocket was closed before the connection was established [-] [stable-22337]2022-12-31T00:33:50.527Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.34.17:8123/api/websocket closed during open/negotiation [stable-22337]2022-12-31T00:33:50.527Z <Controller:NOTICE> HassController#hass stopping [stable-22337]2022-12-31T00:33:50.803Z <Controller:NOTICE> SystemController#reactor_system stopping [stable-22337]2022-12-31T00:33:50.811Z <Controller:ERR> Controller SystemController#reactor_system is off-line! [stable-22337]2022-12-31T00:33:50.814Z <Structure:INFO> Structure#1 Final data sync... [stable-22337]2022-12-31T00:33:50.838Z <Structure:NOTICE> Structure Structure#1 stopped [stable-22337]2022-12-31T00:33:50.839Z <app:NOTICE> Stopping timers... [stable-22337]2022-12-31T00:33:50.840Z <app:NOTICE> Shutdown complete, process ID 7240 -
Sorry for talking to myself. Just trying to relay what I know.
I tried running it manually and got the following:
tbully@homeauto03:~/reactor$ npm run deps npm ERR! Missing script: "deps" npm ERR! npm ERR! To see a list of scripts, run: npm ERR! npm run npm ERR! A complete log of this run can be found in: npm ERR! /home/tbully/.npm/_logs/2022-12-31T01_15_30_113Z-debug-0.log tbully@homeauto03:~/reactor$ NODE_PATH=$(pwd) node app.js Reactor stable-22337-1a0a685f app 22328 configuration from /home/tbully/reactor/config NODE_PATH /home/tbully/reactor [stable-22337]2022-12-31T01:15:55.631Z <app:null> Reactor build stable-22337-1a0a685f starting on v17.9.0 [stable-22337]2022-12-31T01:15:55.632Z <app:null> Process ID 2239 user/group 1000/1000; bare-metal; platform linux/x64 #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022; locale en_CA.UTF-8 [stable-22337]2022-12-31T01:15:55.633Z <app:null> Basedir /home/tbully/reactor; data in /home/tbully/reactor/storage [stable-22337]2022-12-31T01:15:55.633Z <app:null> NODE_PATH=/home/tbully/reactor [stable-22337]2022-12-31T01:15:55.651Z <Structure:null> Module Structure v22323 [stable-22337]2022-12-31T01:15:55.652Z <Capabilities:null> Module Capabilities v22283 [stable-22337]2022-12-31T01:15:55.709Z <Plugin:null> Module Plugin v22300 [stable-22337]2022-12-31T01:15:55.716Z <TimerBroker:null> Module TimerBroker v22283 [stable-22337]2022-12-31T01:15:55.720Z <Entity:null> Module Entity v22314 [stable-22337]2022-12-31T01:15:55.724Z <Controller:null> Module Controller v22323 [stable-22337]2022-12-31T01:15:55.734Z <default:null> Module Ruleset v22293 [stable-22337]2022-12-31T01:15:55.735Z <default:null> Module Rulesets v21096 [stable-22337]2022-12-31T01:15:55.743Z <GlobalExpression:null> Module GlobalExpression v21333 [stable-22337]2022-12-31T01:15:55.753Z <Predicate:null> Module Predicate v22305 [stable-22337]2022-12-31T01:15:55.757Z <AlertManager:null> Module AlertManager v22283 [stable-22337]2022-12-31T01:15:55.759Z <Rule:null> Module Rule v22335 [stable-22337]2022-12-31T01:15:55.763Z <GlobalReaction:null> Module GlobalReaction v22320 [stable-22337]2022-12-31T01:15:55.765Z <Engine:null> Module Engine v22320 [stable-22337]2022-12-31T01:15:55.769Z <httpapi:null> Module httpapi v22337 [stable-22337]2022-12-31T01:15:55.783Z <wsapi:null> Module wsapi v22320 [stable-22337]2022-12-31T01:15:55.845Z <TaskQueue:null> Module TaskQueue 21351 [stable-22337]2022-12-31T01:15:55.846Z <VeraController:null> Module VeraController v22325 [stable-22337]2022-12-31T01:15:56.133Z <HassController:null> Module HassController v22334 [stable-22337]2022-12-31T01:15:57.494Z <SystemController:null> Module SystemController v22306 -
I could delete these posts but I won't. In short, I'm an idiot.
I remembered I have a rule which reboots my Linux host when my weather station goes in to error. Reactor lives on that host. (sigh)
My fix was to temporarily rename the "reboot" command in the filesystem to something else. Start Reactor (imagine that, no reboot!). Disable the rule. Fix the command back to "reboot" in the FS.
Happy New Year! (ugh)
-
These things happen. It's easy to forget stuff like this sometimes. A couple of suggestions:
- Send yourself a notification before you reboot the entire system (with the reason for doing it). Alert, email, cloud service... doesn't matter... just leave yourself a trail of crumbs to follow. It's a good idea to do this before any kind of automatically-triggered aggression against a process or system.
- Delay the reboot command by a minute or two in the reaction after that notification. That will give you time to (a) notice the notification and (b) cancel the reaction in the Running Reactions Status panel. You can then go and fix the rule or whatever is triggering it.
Is there a reason you went to 20.04 instead of 22.04 LTS? The latter will have support through April 2027. If you want to take that step, you can just use
do-release-upgradefrom 20.04. -
Been there, done that. I agree with @toggledbits about alerts. I prefer more alerts (I could always ignore them) than black magic routines.
-
In my exhaustion (anger? Lol), I mistyped. I’m at 22.04.
I do fire an email just before the reboot. I took a break to check emails and wrap up for the day and this is what triggered it for me. If it wasn’t for this, I think I’d still be digging. I send lots of emails, perhaps too many, when different things happen. This is a great idea!
I have to go look at the rule today. I thought I set a variable on reboot which would only allow one event/reboot. At least I thought about this possibility but I clearly missed something.
Thanks for the consoling, gents. I’ve appreciated both of your support over the past year as I’ve slowly moved away from Vera to HASS with Reactor being the central rules engine.
-
T toggledbits locked this topic on
