-
This is an old, well-established rule. It controls the ceiling fan in the LR. I don't want the fan running between the hours of 19:00 and 23:55 each evening so I have this condition:
66427999-2bf7-4deb-9f13-96806489750d-image.png
It's part of the larger:
397a1bf8-5c6b-4a4c-aee9-b7cfc2999ad0-image.pngIf you look closely at the timebox rule you'll see it's set to not between and the time is definitely "between".
Is it me or is MSR ignoring the NOT in not between?
-
Hass: 2022.11.4
Hardware: Container
MSR: stable-22310-3006e85cHi,
I have a number of rules where the reactions change the brightness of lights....that have been working for months. I upgraded MSR recently however I don't think that is issue as I spun up the old container and the the issue remains.
This image illustrates the problem.
bfe42fd7-e038-4aba-bd5a-9892946f7d33-image.png
This what is now available in the dropdown menu
8ec17afc-c23c-413d-956a-fc992881b0e7-image.png
I can turn the light on/off from MSR and Hass however in Hass I can also control the dimming (saturation, colours, effects and so on).
It seems MSR is no longer 'seeing' a number of 'attribute'. At a loss as to what has changed.
Any suggestions most welcome.
Thanks
-
Solution: An update to openLuups MQTT implementation on handling acknowledge packets for QoS > 0 solved this issue.
EDIT: Seems related to any restart without any configuration changes. If I revert to 22310 I can restart Reactor from UI and with systemd within seconds, but with 22328 it fails to restart., both from UI and systemd. I have to stop the service and then start again.
I tested to comment out my http (not https) baseurl in the config on my bare metal Ubuntu install latest-22328 and triggered a restart from the UI but Reactor would not start after that.
If I uncomment the key and restart the service, Reactor comes back to life.
Is my setup an exceptional circumstance or is this only applicable on new installs? -
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've noticed lately (at least with build 22328) that in some cases these yellow warning / alert icons in front of rules are missing, although errors are otherwise visible:
-
Hello @toggledbits I have a strange issue with the HTTP request that i send to Reactor.
I have two reactors one on a Unraid server and one on Ubuntu server installed as a docker, when i send http get request to the Unraid server to control home assistant entity everything is going ok, but when i send the same request to the ubuntu modified accordingly it says "Request failed" but when i try to run reaction via http request it works.When i go to entities and try to control the entity manually its working.
Any idea's?
Best regards
-
I probably messed things up trying to work around the shutdown timeout for Reactor 22328 when connected to openLuup MQTT server.
I got a Reaction from a rule stuck in Running Reactions.
"Stop this reaction" unfortunately does nothing and in my attempt to get rid of them I deleted the rule but they were still there. I downgraded to 22310 to do a clean restart of Reactor, no success. I even tried to rename/edit/delete reaction_queue.json but they are recreated after each restart and I can't get those orphan Reactions to disappear.
I need some advice from the guru, please.
-
Hey Patrick, noticed a bug running latest-22328-bb674d9c on my Rpi. When I go to the entities tab I can see the entity that is no longer available has a line through the text and a question mark, but say if I try adding the entity to a rule set it no longer shows as unavailable. See the screenshots for more clarity.
7d0593a9-c983-4a9f-abad-776a53b1dfe9-image.png
Entity is correctly shown that is unavailable in the entities tab.
1743d7e5-06d2-42b6-a774-2740f4eaee1a-image.png
When I go to choose an entity in a rule set it no longer has a line through and a question mark showing that it is unavailable.
PS: I am using the word unavailable in the context that it was deleted from my HA controller
-
Hello,
I am using MS-Reactor with a Home Assistant hub running on a Synoogy NAS as well as a VERA Plus hub. So far MS-R works AMAZING! However I have one rule I use when cleaning the house that essentially turns all the lights on to 100% (25+ lights) and it takes sometime for the action to take effect. I noticed it worked slighlty faster when I had the items in a scene on the vera controller Vs. a rule triggered by a virtual switch in MS-R.I suspect I could address the issue by increasing the action pace value per the documentation however, I do not know where to edit this setting? Do I just add a line in the MS-R reactor.yaml config file below the VERA controller info that states: "ActionPace: 00500"?
Please let me know where and how I can adjust he aforementioned setting.
All the best,
Phil
-
So it was time to update MSR (and then HA but I got stuck here)
Can't figure out what I have missed.My installed version of MSR was 22240.
Node.js is version 16.15.1First I tried to update, following online manual.
Spoiler
Download a Reactor distribution ZIP from https://reactor.toggledbits.com/download/ and place it in the folder above your existing reactor (runtime) directory.
Stop and remove any existing Reactor service:cd \path\to\reactor
node tools\install_reactor_windows_service.js -u .
Remove any existing package-lock.json file from your Reactor directory.Unzip the archive file and copy its contents over the contents of your existing Reactor install directory.
From the Reactor install directory, re-install/upgrade all package dependencies:npm install --no-save --omit dev
If you are running Reactor as a Windows service, repeat those steps above.Restart Reactor (restart the service).
Hard-refresh all browsers that are displaying Reactor content.I found several (maybe it was 3) package-lock.json and I deleted all I could search in reactor folder.
Unzip the new version and replaced old existing files.Install the reactor service again by instructions.
Spoiler
In a command prompt window, running as Administrator, change directory to your Reactor install directory.
Install the node-windows package as a global package (it must be global or the service will not work, and you must install the specific version provided by the command below):npm uninstall node-windows
npm uninstall -g node-windows
npm install -g node-windows@1.0.0-beta.6
npm link node-windows
Run the script to install:node tools\install_reactor_windows_service.js -i .
So this failed. Service wont start.
Tried again.
Then deleted everything exept my config folder and did a new install.
c:\reactor>node app.js Reactor latest-22310-a6da8097 app 22310 configuration from c:\reactor\config NODE_PATH C:\reactor [latest-22310]2022-11-23T22:18:43.030Z <app:null> Reactor build latest-22310-a6da8097 starting on v16.15.1 c:\reactor\app.js:277 log['always'](a0_0x3d42be(0x26a), BUILD_VERSION, process['version']), log['always']('Process\x20ID\x20%1\x20user/group\x20%2/%3;\x20%4;\x20platform\x20%5/%6\x20%7;\x20locale\x20%8', process['pid'], process[a0_0x3d42be(0x269)](), process[a0_0x3d42be(0x278)](), is_docker ? 'docker' : a0_0x3d42be(0x288), process[a0_0x3d42be(0x287)], process['arch'], os[a0_0x3d42be(0x263)](), sys_locale), log[a0_0x3d42be(0x28c)]('Basedir\x20%1;\x20data\x20in\x20%2', c[a0_0x3d42be(0x1f8)], c[a0_0x3d42be(0x27b)]), log[a0_0x3d42be(0x28c)](a0_0x3d42be(0x21b), process['env'][a0_0x3d42be(0x291)]); ^ TypeError: process[a0_0x3d42be(...)] is not a function at Object.<anonymous> (c:\reactor\app.js:277:226) at Module._compile (node:internal/modules/cjs/loader:1105:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) at node:internal/main/run_main_module:17:47
Also downloaded 22310 again, but from "latest" build instead of "stable"
When running node app.js in command promt i get some kind of error message:But I can't figure out what TypeError means?
Also, before I tried a new install, there apperd an warning when installing reactor service.
c:\reactor>npm install -g node-windows@1.0.0-beta.6 npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. added 5 packages, and audited 6 packages in 3s 2 vulnerabilities (1 moderate, 1 critical) To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details.Running npm audit fix --force seems to broke something, because I could not install service after that.
c:\reactor>npm audit fix --force npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. npm WARN using --force Recommended protections disabled. up to date, audited 89 packages in 826ms 12 packages are looking for funding run `npm fund` for details found 0 vulnerabilities c:\reactor>node tools\install_reactor_windows_service.js -i . node:internal/modules/cjs/loader:936 throw err; ^ Error: Cannot find module 'node-windows' Require stack: - c:\reactor\tools\install_reactor_windows_service.js ←[90m at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m ←[90m at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m ←[90m at Module.require (node:internal/modules/cjs/loader:1005:19)←[39m ←[90m at require (node:internal/modules/cjs/helpers:102:18)←[39m at Object.<anonymous> (c:\reactor\tools\install_reactor_windows_service.js:102:15) ←[90m at Module._compile (node:internal/modules/cjs/loader:1105:14)←[39m ←[90m at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)←[39m ←[90m at Module.load (node:internal/modules/cjs/loader:981:32)←[39m ←[90m at Function.Module._load (node:internal/modules/cjs/loader:822:12)←[39m ←[90m at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)←[39m { code: ←[32m'MODULE_NOT_FOUND'←[39m, requireStack: [ ←[32m'c:\\reactor\\tools\\install_reactor_windows_service.js'←[39m ] } -
Hello All -
I'm still working on moving dozens of devices from Vera (internal Reactor) to HASS and (external - bare metal) Reactor.
One thing I've noticed is sometimes I move a few ZWave/Vera devices and find myself digging through rules finding where a device was used. Has anyone found a good way to do this?
I plan on digging in to this thread but thought I'd check to see if there's anything more recent.
https://smarthome.community/topic/483/entities-where-used-and-what-triggered-it?_=1669137134654
-
Hass: 2022.11.3
Hardware: Pi
MSR: latest-22310-a6da8097I'm trying to use MSR in automations to change the page displayed on a wall tablet (Windows and Edge in Kiosk mode)
Example use would be motion detected will change to the security dashboard, or heating turns on, shows the heating dashboard.Screenshot_20221122_193138.png I have Browser Mod installed and working and the entities are present in MSR. My only option for the entity which controls the page/dashboard displayed is "x_hass.call_service"
What I need to change is the state of the entity
state.png state2.pngIs this possible in MSR? Despite much searching i'm unsure what service to call to set the state?
I have tried using service: browser_mod.navigate but get an error
(this service detailed here https://smarthomescene.com/guides/how-to-setup-browser-mod-2-0-in-home-assistant/ )
error1.pngAlso trying to lay the data out like this with/out quotes and other variations has not helped
{ "/home-overview/heating" } -
Here's my second attempt at a Reactor Controller, this time to integrate LG TVs:
GitHub - dbochicchio/reactor-lgtv: Reactor controller for LG TV (webos) GitHub - dbochicchio/reactor-lgtv: Reactor controller for LG TV (webos)Reactor controller for LG TV (webos). Contribute to dbochicchio/reactor-lgtv development by creating an account on GitHub.
Standard capabilities are provided and TV volume, mute and switch status are controllable.
There's also an action to send toast notifications on your TV.webos 5+ is required.
-
I've moved many of my MQTT devices to Reactor, so I've coded a couple of templates and I'm publishing them for anyone in the same boat:
GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for ReactorContrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
I'll add more in the future, since I still have a couple of things running in my own bridge that I'll eventually move to Reactor with dedicated templates.
Let me know if you need other templates, I'll probably add a couple more for Shellies (button as scene controller and i3/i4 as scene controller).
-
Before I'll open a feature request, I want a reality check, because this is maybe achievable in other ways.
Long story short: I want to react to a device in quasi-real time, but 15 or 30 secs are enough (and will prevent the rule from throttling). Right now, I've moved to 1 min, but it's obviously too late to catch all the variations. 15 secs or 30 are OK, so my first reaction to circumvent this limitation was to host the timer myself and send it via MQTT, but it's obviously a not welcome complication.
So, @toggledbits, is there any reason the minimum interval is 1 min and/or do you have any suggestion for my use case? Thanks Patrick!
-
I'm still trying to fully wrap my brain around Pulsing. Let's see if I have it:
2a1da895-5170-499f-a1ff-708d3ded1f5c-image.png
I believe this to indicate that this will wait five minutes, do the thing, wait five seconds and repeat.
Backstory: this is a reset ruleset for my HVAC. Sometimes Honeywell is finicky about taking the original commands so this should follow along and submit a retry after five minutes... continuing until the setting is accepted.
-
Hi @toggledbits !!
Would it be possible to improve the error messages, and instead of showing the "technical name", show the name we assigned to the rule?
a8298689-0c7b-43ef-a582-16baece4e4d1-image.png
In the above case, I have no idea what rule is causing the problem.
Thanks.
-
MSR latest-22310, Raspberry Pi 4 / Docker
While troubleshooting another issue, I deleted and recreated the hub information device on one of my Hubitat hubs. Reactor had been logging the old device information to InfluxDB, but it doesn't appear to have detected the new device. I made sure to enable the new device in Maker API, I've restarted reactor and done a 'docker-compose down' / 'docker-compose up - d'. Still no new data going to influxdb.
My recollection is that the Hubitat hub device is baken into MSR and is auto-detected, and that it isn't manually configured anywhere. I checked the docs and searched the forum without success.
Any advice on how I can get MSR to start logging the info from the new device?
-
Hi!
I can't find the original post where it's stated that it's possible to make a shortcut i HA to MSR, but I remember trying it out, and it failed, probably because I have duckdns, and a https address, and not a http address, which give us the wss: instead of ws:. Maybe not, but that was my understanding. I finally gave it up, but now I want to try it again. Anyway, is there anyone with duckdns and https that have been able to set this up? How?
Thanks in advance!
/Fanan -
MSR has a parameter called "http_request_action_maxresponse" that can be updated within the properties. There is a good section describing this in the manual. However, the installation config file doesn't include the parameter out of the box. I was able to add the parameter (see below) and eventually got it to work after searching for a while.
Suggestions:
Include the parameter in the initial config file (or) Update the manual to state that the parameter should be added to the fileAdditional suggestion:
engine: # # enabled - Whether or not the rules engine runs. Change only when directed. enabled: true http_request_action_maxresponse: 10000
I understand that it is potentially unsafe to have a large limit overall. However, some API calls unfortunately return large sizes which aren't necessarily problematic. The additional suggestion is to include a configurable max size within each HTTP Reaction in the UI. If it isn't populated then MSR could default to the config file like it does today. This way, we could have a reasonable default limit while allowing larger limit for certain HTTP calls.
[Solved] suninfo.sun_angle usage: showing -218.7 mid-day
-
I just stumbled across this last evening in the manual and it piqued my interest in possibly using this to trigger from/by:
"Sun Information" entity (capability suninfo, canonical ID reactor_system>sun) with data about today's sunrise/sunset, day length (in hours), solar noon (transit) time, and current sun angle (-90 at sunrise, 0 at solar noon, 90 at sunset).
I immediately added the
entityto a dummy/test ruleset last night and see that the value currently shown forsuninfo.sun_anglehasn't budged from "-218.7", even though it's now mid-day (expectation being something between "-90" and "90" being the current value.
I read and reread the manual and don't see where there's any config required for this
entity- am I missing something? Has anyone else made use of this?Hubitat C-7 2.3.4.114, Home Assistant 2022.11.5 running ZST10-700 fw 7.17.2, MSR on RPi4 bare metal Model B 2GBs latest-22337-1a0a685f
-
@gwp1 I've tried it just right not out of curiosity and it's showing -228.3 for me (and it's 20:15 here in Italy, so it should have been 90).
-
Can you both report the results of
http://your-reactor-host-ip:8111/diag/sunplease? VIA PM TO ME -
Based on what @gwp1 sent, it looks correct, but like it's not updating (stale data). I'm going with that for now. Fixed for next build.
-
This did it, @toggledbits - thanks very much for the prompt turnaround! This will lead to some interesting blinds automation, methinks....
-
It’s fixed for me as well.
-
Seems odd but this
stopped refreshingstopped matching my location last night at 22:49 ET. The difference, however, this time is that the results of the URL are what's not refreshing. @toggledbits I've sent you the results of the URL from this morning.Currently it is updating but the sun angle doesn't match the location of the MSR host location setting. All other data seems to match. Lat/Long, date/time, etc.
-
@gwp1 I'm going to respond to your second PM here, because I think it's useful public info...
The only thing that would change in the sun data on multiple requests is the sun angle, and that is changed in your two (DM) examples. The timing of astro events and the length of the day remain the same all day (i.e. sunset happens at the same time on 12/11 whether you ask at 9am or 3pm), so don't expect any change from those parts. And this is a feature; it's a Very Good Thing that these computed times are stable.
The sun angle, having single-decimal-digit resolution as presented, would for this time of year at your location not be expected to change more than once every 20 seconds. That is, the sun traverses an arc of 180 degrees in about 10 hours (again, at your location), or 36000 seconds, so a degree every 200 seconds, or 1/10th of a degree every 20 seconds. It may be a little more, allowing for round-off and precision limits.
-
@toggledbits Totally understand.
And I'm an idiot who apparently cannot do maths this morning.
The expectation per the docs is -90 = sunrise, 0 = solar noon, 90 = sunset. The sun_angle is showing as a negative number currently, WHICH IT SHOULD BECAUSE IT'S NOT NOON YET. <smh>
Sincere apologies for wasting your time. I just installed smart blinds last evening and am very anxious to see if sun_angle will be a solid means by which to angle the blinds as the sun shifts across the back of the house - kinda let my excitement/curiosity run away with me.
-
All good. I anticipated this kind of application, and it makes me realize that you probably would want azimuth as well, because the effect of the sun on your windows is a function not only of its height relative to the horizon, but its angle left-right relative to the plane of your windows. That may be a bit more than you are thinking, but I think eventually you'd come to that conclusion, because the sun does change its position in the sky laterally as well as in elevation (the former is just more gradual over the course of months, while the latter is a daily traversal). So, azimuth coming next...
-
@toggledbits Spot on, that's exactly what happens here with dramatic impact, esp on my home office. Sadly, the blinds in there are too small to automate at this time (by a mere 1 1/2", too.) The back of the house, however - totally fair game for automation.
-
OK. In playing with this a bit more, I'm going to make
suninfo.sun_anglego away (eventually; after a deprecation period), and it's replacement will be a soon-to-comesuninfo.elevation. Theelevationis the true angle of the sun above the horizon. Unless you live on the equator, the sun is not really at 0 degrees at solar noon, assun_angleindicates. For example, right now for me in the Atlanta area at this time, solar noon gives me an elevation of just 33.5 degrees (summer solstice about 80 degrees). I think the true elevation will be a better metric for solar energy calculations, and in combination withazimuth, you should easily be able to compute ray angles/exposure to solar panels and good things like that.The other things I'm fixing is that our friends in Prudhoe Bay and Tromsø are getting incorrect day lengths, etc., right now because the sun never rises at this time of year. The sunrise/sunset times are null as expected, but the day length is 24 when, IMO, it should be zero, and the
sun_angleis null which is again not as useful as having a real elevation.