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 🙂
Constraints (no data) rule actions have never run
-
@toggledbits OK think that makes sense.
Not sure why my rules action is not running then.
This is the trigger
I have pressed the Play button in the Set Reaction area and it does actually turn off the light OK.
I've had this rule setup for maybe 3 days and my Festoon lights have never turned off and have been left on all night.
-
Have you looked in the log at around the time the rule would be expected to trigger? There may be something logged. Remember to adjust for time zone if your host's configured time zone is different from your browser/desktop (i.e. it's not unusual to have a Pi, for example, default to UTC, so all times logged will be UTC and thus maybe different from your local time).
-
I have other Schedules in MSR for certain times in the morning to open window coverings they are now all working fine and open on the time I set in their triggers.
If I use the command "date" on the Pi in putty it does say the correct time as of now:
Fri 26 Feb 13:15:22 GMT 2021
I'll have a look in the Reactor logs
Thanks
-
Looking in reactor.log I searched this rules ID code kljc5802:
2021-02-25T19:00:05.003Z <Engine:INFO> Engine#1 master timer tick, local time "2/25/2021, 19:00:05" (TZ offset 0 mins from UTC) false false2021-02-25T19:34:00.006Z <Rule:5:Rule.js:635> Rule#rule-kljc5802 launching eval from timer-trigger notification by Timer#cond57lqecd false false2021-02-25T19:34:00.009Z <Rule:5:Rule.js:697> Rule#rule-kljc5802 (Schedule - Festoon Lights OFF) evaluate() acquiring mutex false false2021-02-25T19:34:00.012Z <Rule:5:Rule.js:635> Rule#rule-kljbrk9g launching eval from timer-trigger notification by Timer#cond57lqecd false false2021-02-25T19:34:00.014Z <Rule:5:Rule.js:697> Rule#rule-kljbrk9g (Schedule - Lawn Lights OFF) evaluate() acquiring mutex false false2021-02-25T19:34:00.017Z <Rule:5:Rule.js:700> Rule#rule-kljc5802.evaluate() mutex acquired, evaluating false false2021-02-25T19:34:00.021Z <Rule:5:Rule.js:704> Rule#rule-kljc5802 update rate is 0/min limit 60/min false false2021-02-25T19:34:00.023Z <Rule:5:Rule.js:654> Rule#rule-kljc5802 evaluateExpressions() with 0 expressions false false2021-02-25T19:34:00.025Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd trange after sdt=2/25/2021, 23:55:00 edt=2/25/2021, 19:34:00 now=2/25/2021, 19:34:00 false false2021-02-25T19:34:00.028Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd timer now scheduled for 2/25/2021, 23:55:00, 15659 secs from now false false2021-02-25T19:34:00.030Z <Rule:5:Rule.js:714> Rule#rule-kljc5802.evaluate() trigger state false (was false) false false2021-02-25T20:13:27.338Z <Engine:5:Engine.js:550> Engine#1 (re-)starting rule Rule#rule-kljc5802 (Schedule - Festoon Lights OFF) 2021-02-25T20:13:27.340Z <Rule:5:Rule.js:555> Rule#rule-kljc5802 start(), awaiting mutex2021-02-25T20:13:27.513Z <Rule:5:Rule.js:563> Rule#rule-kljc5802 restored states: trig=false, rule=false 2021-02-25T20:13:27.515Z <Rule:5:Rule.js:563> Rule#rule-kljc5802 subscribing to dependencies 2021-02-25T20:13:27.517Z <Rule:INFO> Rule#rule-kljc5802 (Schedule - Festoon Lights OFF) started2021-02-25T20:13:27.761Z <Rule:5:Rule.js:700> Rule#rule-kljc5802.evaluate() mutex acquired, evaluating 2021-02-25T20:13:27.762Z <Rule:5:Rule.js:704> Rule#rule-kljc5802 update rate is 0/min limit 60/min 2021-02-25T20:13:27.765Z <Rule:5:Rule.js:654> Rule#rule-kljc5802 evaluateExpressions() with 0 expressions 2021-02-25T20:13:27.767Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd trange after sdt=2/25/2021, 23:55:00 edt=2/25/2021, 20:13:00 now=2/25/2021, 20:13:27 2021-02-25T20:13:27.771Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd timer now scheduled for 2/25/2021, 23:55:00, 13292 secs from now 2021-02-25T20:13:27.774Z <Rule:5:Rule.js:714> Rule#rule-kljc5802.evaluate() trigger state false (was false)2021-02-26T00:00:00.129Z <Rule:5:Rule.js:635> Rule#rule-kljc5802 launching eval from timer-trigger notification by Timer#cond57lqecd 2021-02-26T00:00:00.131Z <Rule:5:Rule.js:697> Rule#rule-kljc5802 (Schedule - Festoon Lights OFF) evaluate() acquiring mutex 2021-02-26T00:00:00.136Z <Rule:5:Rule.js:635> Rule#rule-kljbrk9g launching eval from timer-trigger notification by Timer#cond57lqecd 2021-02-26T00:00:00.139Z <Rule:5:Rule.js:697> Rule#rule-kljbrk9g (Schedule - Lawn Lights OFF) evaluate() acquiring mutex 2021-02-26T00:00:00.141Z <Rule:5:Rule.js:700> Rule#rule-kljc5802.evaluate() mutex acquired, evaluating 2021-02-26T00:00:00.145Z <Rule:5:Rule.js:704> Rule#rule-kljc5802 update rate is 0/min limit 60/min 2021-02-26T00:00:00.147Z <Rule:5:Rule.js:654> Rule#rule-kljc5802 evaluateExpressions() with 0 expressions 2021-02-26T00:00:00.150Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd trange after sdt=2/26/2021, 23:55:00 edt=2/26/2021, 00:00:00 now=2/26/2021, 00:00:00 2021-02-26T00:00:00.152Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd timer now scheduled for 2/26/2021, 23:55:00, 86099 secs from now 2021-02-26T00:00:00.154Z <Rule:5:Rule.js:714> Rule#rule-kljc5802.evaluate() trigger state false (was false)2021-02-26T11:02:14.128Z <Rule:NOTICE> Rule#rule-kljc5802 configuration changed; reloading 2021-02-26T11:02:14.147Z <Rule:5:Rule.js:600> Rule#rule-kljc5802 reloading with new data 2021-02-26T11:02:14.150Z <Rule:NOTICE> Rule#rule-kljc5802 stopping rule 2021-02-26T11:02:14.152Z <Rule:5:Rule.js:581> Rule#rule-kljc5802 acquiring mutex 2021-02-26T11:02:14.157Z <Rule:5:Rule.js:584> Rule#rule-kljc5802 mutex acquired; unsubscribing from condition dependencies 2021-02-26T11:02:14.169Z <Rule:5:Rule.js:586> Rule#rule-kljc5802 saving states 2021-02-26T11:02:14.176Z <Rule:5:Rule.js:590> Rule#rule-kljc5802 stopped 2021-02-26T11:02:14.178Z <Rule:NOTICE> Rule Rule#rule-kljc5802 stopped 2021-02-26T11:02:14.180Z <Rule:5:Rule.js:555> Rule#rule-kljc5802 start(), awaiting mutex 2021-02-26T11:02:14.183Z <Rule:5:Rule.js:563> Rule#rule-kljc5802 restored states: trig=false, rule=false 2021-02-26T11:02:14.185Z <Rule:5:Rule.js:563> Rule#rule-kljc5802 subscribing to dependencies 2021-02-26T11:02:14.378Z <Rule:INFO> Rule#rule-kljc5802 (Schedule - Festoon Lights OFF) started 2021-02-26T11:02:14.381Z <Rule:5:Rule.js:567> Rule#rule-kljc5802 start() dependencies resolved, performing initial evaluation 2021-02-26T11:02:14.509Z <Rule:5:Rule.js:697> Rule#rule-kljc5802 (Schedule - Festoon Lights OFF) evaluate() acquiring mutex 2021-02-26T11:02:14.511Z <Rule:5:Rule.js:700> Rule#rule-kljc5802.evaluate() mutex acquired, evaluating 2021-02-26T11:02:14.518Z <Rule:5:Rule.js:704> Rule#rule-kljc5802 update rate is 0/min limit 60/min 2021-02-26T11:02:14.520Z <Rule:5:Rule.js:654> Rule#rule-kljc5802 evaluateExpressions() with 0 expressions 2021-02-26T11:02:14.523Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd trange after sdt=2/26/2021, 23:55:00 edt=2/26/2021, 11:02:00 now=2/26/2021, 11:02:14 2021-02-26T11:02:14.527Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd timer now scheduled for 2/26/2021, 23:55:00, 46365 secs from now 2021-02-26T11:02:14.529Z <Rule:5:Rule.js:714> Rule#rule-kljc5802.evaluate() trigger state false (was false) 2021-02-26T11:02:52.786Z <Rule:NOTICE> Rule#rule-kljc5802 configuration changed; reloading 2021-02-26T11:02:52.792Z <Rule:5:Rule.js:600> Rule#rule-kljc5802 reloading with new data 2021-02-26T11:02:52.794Z <Rule:NOTICE> Rule#rule-kljc5802 stopping rule 2021-02-26T11:02:52.797Z <Rule:5:Rule.js:581> Rule#rule-kljc5802 acquiring mutex 2021-02-26T11:02:52.803Z <Rule:5:Rule.js:584> Rule#rule-kljc5802 mutex acquired; unsubscribing from condition dependencies 2021-02-26T11:02:52.816Z <Rule:5:Rule.js:586> Rule#rule-kljc5802 saving states 2021-02-26T11:02:52.823Z <Rule:5:Rule.js:590> Rule#rule-kljc5802 stopped 2021-02-26T11:02:52.824Z <Rule:NOTICE> Rule Rule#rule-kljc5802 stopped 2021-02-26T11:02:52.828Z <Rule:5:Rule.js:555> Rule#rule-kljc5802 start(), awaiting mutex 2021-02-26T11:02:52.831Z <Rule:5:Rule.js:563> Rule#rule-kljc5802 restored states: trig=false, rule=false 2021-02-26T11:02:52.833Z <Rule:5:Rule.js:563> Rule#rule-kljc5802 subscribing to dependencies 2021-02-26T11:02:52.835Z <Rule:INFO> Rule#rule-kljc5802 (Schedule - Festoon Lights OFF) started 2021-02-26T11:02:52.838Z <Rule:5:Rule.js:567> Rule#rule-kljc5802 start() dependencies resolved, performing initial evaluation 2021-02-26T11:02:52.840Z <Rule:5:Rule.js:697> Rule#rule-kljc5802 (Schedule - Festoon Lights OFF) evaluate() acquiring mutex 2021-02-26T11:02:52.844Z <Rule:5:Rule.js:700> Rule#rule-kljc5802.evaluate() mutex acquired, evaluating 2021-02-26T11:02:52.846Z <Rule:5:Rule.js:704> Rule#rule-kljc5802 update rate is 1/min limit 60/min 2021-02-26T11:02:52.848Z <Rule:5:Rule.js:654> Rule#rule-kljc5802 evaluateExpressions() with 0 expressions 2021-02-26T11:02:52.850Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd trange after sdt=2/26/2021, 23:55:00 edt=2/26/2021, 11:02:00 now=2/26/2021, 11:02:52 2021-02-26T11:02:52.852Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd timer now scheduled for 2/26/2021, 23:55:00, 46327 secs from now 2021-02-26T11:02:52.854Z <Rule:5:Rule.js:714> Rule#rule-kljc5802.evaluate() trigger state false (was false) 2021-02-26T11:03:25.898Z <Rule:NOTICE> Rule#rule-kljc5802 configuration changed; reloading 2021-02-26T11:03:25.904Z <Rule:5:Rule.js:600> Rule#rule-kljc5802 reloading with new data 2021-02-26T11:03:25.905Z <Rule:NOTICE> Rule#rule-kljc5802 stopping rule 2021-02-26T11:03:25.908Z <Rule:5:Rule.js:581> Rule#rule-kljc5802 acquiring mutex 2021-02-26T11:03:25.913Z <Rule:5:Rule.js:584> Rule#rule-kljc5802 mutex acquired; unsubscribing from condition dependencies 2021-02-26T11:03:25.922Z <Rule:5:Rule.js:586> Rule#rule-kljc5802 saving states 2021-02-26T11:03:25.929Z <Rule:5:Rule.js:590> Rule#rule-kljc5802 stopped 2021-02-26T11:03:25.930Z <Rule:NOTICE> Rule Rule#rule-kljc5802 stopped 2021-02-26T11:03:25.933Z <Rule:5:Rule.js:555> Rule#rule-kljc5802 start(), awaiting mutex 2021-02-26T11:03:25.935Z <Rule:5:Rule.js:563> Rule#rule-kljc5802 restored states: trig=false, rule=false 2021-02-26T11:03:25.937Z <Rule:5:Rule.js:563> Rule#rule-kljc5802 subscribing to dependencies 2021-02-26T11:03:25.938Z <Rule:INFO> Rule#rule-kljc5802 (Schedule - Festoon Lights OFF) started 2021-02-26T11:03:25.940Z <Rule:5:Rule.js:567> Rule#rule-kljc5802 start() dependencies resolved, performing initial evaluation 2021-02-26T11:03:25.942Z <Rule:5:Rule.js:697> Rule#rule-kljc5802 (Schedule - Festoon Lights OFF) evaluate() acquiring mutex 2021-02-26T11:03:25.944Z <Rule:5:Rule.js:700> Rule#rule-kljc5802.evaluate() mutex acquired, evaluating 2021-02-26T11:03:25.945Z <Rule:5:Rule.js:704> Rule#rule-kljc5802 update rate is 1/min limit 60/min 2021-02-26T11:03:25.948Z <Rule:5:Rule.js:654> Rule#rule-kljc5802 evaluateExpressions() with 0 expressions 2021-02-26T11:03:25.950Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd trange after sdt=2/26/2021, 23:55:00 edt=2/26/2021, 11:03:00 now=2/26/2021, 11:03:25 2021-02-26T11:03:25.952Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd timer now scheduled for 2/26/2021, 23:55:00, 46294 secs from now 2021-02-26T11:03:25.954Z <Rule:5:Rule.js:714> Rule#rule-kljc5802.evaluate() trigger state false (was false) 2021-02-26T11:03:52.673Z <Rule:NOTICE> Rule#rule-kljc5802 configuration changed; reloading 2021-02-26T11:03:52.677Z <Rule:5:Rule.js:600> Rule#rule-kljc5802 reloading with new data 2021-02-26T11:03:52.693Z <Rule:NOTICE> Rule#rule-kljc5802 stopping rule 2021-02-26T11:03:52.695Z <Rule:5:Rule.js:581> Rule#rule-kljc5802 acquiring mutex 2021-02-26T11:03:52.701Z <Rule:5:Rule.js:584> Rule#rule-kljc5802 mutex acquired; unsubscribing from condition dependencies 2021-02-26T11:03:52.721Z <Rule:5:Rule.js:586> Rule#rule-kljc5802 saving states 2021-02-26T11:03:52.729Z <Rule:5:Rule.js:590> Rule#rule-kljc5802 stopped 2021-02-26T11:03:52.731Z <Rule:NOTICE> Rule Rule#rule-kljc5802 stopped 2021-02-26T11:03:52.733Z <Rule:5:Rule.js:555> Rule#rule-kljc5802 start(), awaiting mutex 2021-02-26T11:03:52.736Z <Rule:5:Rule.js:563> Rule#rule-kljc5802 restored states: trig=false, rule=false 2021-02-26T11:03:52.738Z <Rule:5:Rule.js:563> Rule#rule-kljc5802 subscribing to dependencies 2021-02-26T11:03:52.740Z <Rule:INFO> Rule#rule-kljc5802 (Schedule - Festoon Lights OFF) started 2021-02-26T11:03:52.742Z <Rule:5:Rule.js:567> Rule#rule-kljc5802 start() dependencies resolved, performing initial evaluation 2021-02-26T11:03:52.744Z <Rule:5:Rule.js:697> Rule#rule-kljc5802 (Schedule - Festoon Lights OFF) evaluate() acquiring mutex 2021-02-26T11:03:52.747Z <Rule:5:Rule.js:700> Rule#rule-kljc5802.evaluate() mutex acquired, evaluating 2021-02-26T11:03:52.749Z <Rule:5:Rule.js:704> Rule#rule-kljc5802 update rate is 1/min limit 60/min 2021-02-26T11:03:52.754Z <Rule:5:Rule.js:654> Rule#rule-kljc5802 evaluateExpressions() with 0 expressions 2021-02-26T11:03:52.757Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd trange after sdt=2/26/2021, 23:55:00 edt=2/26/2021, 11:03:00 now=2/26/2021, 11:03:52 2021-02-26T11:03:52.759Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd timer now scheduled for 2/26/2021, 23:55:00, 46267 secs from now 2021-02-26T11:03:52.761Z <Rule:5:Rule.js:714> Rule#rule-kljc5802.evaluate() trigger state false (was false) 2021-02-26T11:04:13.259Z <Rule:NOTICE> Rule#rule-kljc5802 configuration changed; reloading 2021-02-26T11:04:13.264Z <Rule:5:Rule.js:600> Rule#rule-kljc5802 reloading with new data 2021-02-26T11:04:13.265Z <Rule:NOTICE> Rule#rule-kljc5802 stopping rule 2021-02-26T11:04:13.266Z <Rule:5:Rule.js:581> Rule#rule-kljc5802 acquiring mutex 2021-02-26T11:04:13.271Z <Rule:5:Rule.js:584> Rule#rule-kljc5802 mutex acquired; unsubscribing from condition dependencies 2021-02-26T11:04:13.274Z <Rule:5:Rule.js:586> Rule#rule-kljc5802 saving states 2021-02-26T11:04:13.281Z <Rule:5:Rule.js:590> Rule#rule-kljc5802 stopped 2021-02-26T11:04:13.282Z <Rule:NOTICE> Rule Rule#rule-kljc5802 stopped 2021-02-26T11:04:13.284Z <Rule:5:Rule.js:555> Rule#rule-kljc5802 start(), awaiting mutex 2021-02-26T11:04:13.286Z <Rule:5:Rule.js:563> Rule#rule-kljc5802 restored states: trig=false, rule=false 2021-02-26T11:04:13.287Z <Rule:5:Rule.js:563> Rule#rule-kljc5802 subscribing to dependencies 2021-02-26T11:04:13.289Z <Rule:INFO> Rule#rule-kljc5802 (Schedule - Festoon Lights OFF) started 2021-02-26T11:04:13.290Z <Rule:5:Rule.js:567> Rule#rule-kljc5802 start() dependencies resolved, performing initial evaluation 2021-02-26T11:04:13.292Z <Rule:5:Rule.js:697> Rule#rule-kljc5802 (Schedule - Festoon Lights OFF) evaluate() acquiring mutex 2021-02-26T11:04:13.293Z <Rule:5:Rule.js:700> Rule#rule-kljc5802.evaluate() mutex acquired, evaluating 2021-02-26T11:04:13.295Z <Rule:5:Rule.js:704> Rule#rule-kljc5802 update rate is 2/min limit 60/min 2021-02-26T11:04:13.297Z <Rule:5:Rule.js:654> Rule#rule-kljc5802 evaluateExpressions() with 0 expressions 2021-02-26T11:04:13.299Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd trange after sdt=2/26/2021, 23:55:00 edt=2/26/2021, 11:04:00 now=2/26/2021, 11:04:13 2021-02-26T11:04:13.300Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd timer now scheduled for 2/26/2021, 23:55:00, 46246 secs from now 2021-02-26T11:04:13.302Z <Rule:5:Rule.js:714> Rule#rule-kljc5802.evaluate() trigger state false (was false)2021-02-26T11:04:15.369Z <Rule:5:Rule.js:700> Rule#rule-kljc5802.evaluate() mutex acquired, evaluating 2021-02-26T11:04:15.371Z <Rule:5:Rule.js:704> Rule#rule-kljc5802 update rate is 3/min limit 60/min 2021-02-26T11:04:15.373Z <Rule:5:Rule.js:654> Rule#rule-kljc5802 evaluateExpressions() with 0 expressions 2021-02-26T11:04:15.375Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd trange after sdt=2/26/2021, 23:55:00 edt=2/26/2021, 11:04:00 now=2/26/2021, 11:04:15 2021-02-26T11:04:15.377Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd timer now scheduled for 2/26/2021, 23:55:00, 46244 secs from now 2021-02-26T11:04:15.379Z <Rule:5:Rule.js:714> Rule#rule-kljc5802.evaluate() trigger state false (was false)2021-02-26T11:18:29.114Z <Rule:5:Rule.js:680> Rule#rule-kljc5802.evaluate() mutex acquired, evaluating 2021-02-26T11:18:29.117Z <Rule:5:Rule.js:684> Rule#rule-kljc5802 update rate is 1/min limit 60/min 2021-02-26T11:18:29.119Z <Rule:5:Rule.js:634> Rule#rule-kljc5802 evaluateExpressions() with 0 expressions 2021-02-26T11:18:29.124Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd trange after sdt=2/26/2021, 23:55:00 edt=2/26/2021, 11:18:00 now=2/26/2021, 11:18:29 2021-02-26T11:18:29.127Z <Rule:null> Rule#rule-kljc5802 cond cond57lqecd timer now scheduled for 2/26/2021, 23:55:00, 45390 secs from now 2021-02-26T11:18:29.130Z <Rule:5:Rule.js:694> Rule#rule-kljc5802.evaluate() trigger state false (was false) -
Grep'ing out specific lines of the log isn't really a productive thing to do, as there are other lines surrounding in context that may not contain the search string but are needed to show the full activity. It would not, for example, show an exception thrown. Just gzip the log and email it to me at the address given in the "SUPPORT" section of the about page; I'll take a look later this morning.
-
Not related but I am seeing these errors in the log:
Expression compilation error for deviceclass heatonly_thermostat hvac_control.mode: Error: Parse error on line 1: ...tochangeover:'auto'}[lower(value)] ?? vaDevice 190 is the Secure Boiler Relay Switch related to the Secure Thermostat device.
2021-02-25T18:03:47.240Z <VeraController:ERR> Exception/error while updating Entity#vera>device_190 2021-02-25T18:03:47.242Z <VeraController:CRIT> ReferenceError: expr is not defined ReferenceError: expr is not defined -
Are you in 21056?
-
@toggledbits Yes
Two more rules here both are set to run at 9am
One worked this morning OK and did its action, the other rule the bottom one in the screen shot, that didn't run its action.
This is the rule that didn't run, have I done something wrong ?
I've just updated to the latest version of MSR (reactor-0.1.21057-f143fd3-generic.tar) and now that rule that didn't run this morning looks like this:
-
I have created a lot of other rules, some of them also with Constraints and none of those rules say null or no data in the Constraints in the rules summary card.
I've gone through them all now again looking and it seems I only have two rules which I have highlighted above that don't run and they say or have said null or no data in Constraints.
All my other garden lights have turned on and off OK, but they are using a sunset offset not a specific set time.
But that rule to turn off the Festoon lights at 23:55pm has never run since I created it.
I also have rules for the window coverings setup for specific times in the morning and generally they have all run at their set times OK.
I will see what happens tomorrow at 9am with this "Lounge Blind Slats" one ?
Thanks
-
The 11:55pm rule that never worked since I created it, I deleted it. I then created it again exactly the same as I did before. Looking at its Summary card the Constraints stated no data / null etc. I then edited the rule and changed its time to 9:00am and saved. I then edited the rule again and set it back to 11:55pm and saved.
The rule now runs and turns off my lights at 11:55pm or it did last night at least anyway. So assume it will work every night now.
I created another new rule not related to run every night at 10:30pm and that one worked first time no problems, so not sure why I have had issues with a few rules.
The 9am rule to open the Lounge Blind Slats didn't run this morning again, so I've deleted it and recreated it, see what happens with that tomorrow morning ?
-
Remember two things:
- Log files are pretty good at telling what's going on, and really good at help me determine what's going on;
- Open PRs are my highest priority.
-
OK. Not seeing an email yet... you used the address in the "Support" section of the About page?
-
This post is deleted!
-
@cw-kid I removed your post just for my own anti-spam/scraping reduction, no other reason. The address you showed is fine. If you know how to reach me in my primary domain, that's fine too. I just point out the About page because it will always be there.
