-
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. -
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. -
Hi,
@toggledbits do you have any plans to implement the missing endpoints of the REST API in near future? Especially the rule and ruleset functionality (list/enable/disable etc. as documented) would be really useful. I know there must tons of feature requests and the REST API isn't probably on the top of the backlog, so I'm not holding my breath. But if it's right around the corner on your roadmap, it would be nice to know.I'm asking this because I need a clean way to enable and disable certain rules from my custom home automation UI. I don't want to expose the MSR UI to the rest of my family to make sure they don't accidentally mess up with the rules and settings.
I could use a custom MQTT entity as a dynamic config object containing flags for different rules but it would be a lot cleaner to be toggle the rules thru the REST API.
br,
mgvraReactor (Multi-hub) latest-22310-a6da8097
MQTTController [0.1.22306] -
Hey Patrick, along with my request to have a back and restore button it would be nice to also have a update button. Not an urgent request, just would make updates quicker and easier.
-
The docs state "substituting your site's IP address and Authorization Key:" I have replaced the IP, np, but am uncertain what "Authorization Key" is expected here.
My Home Assistant setup is using zwaveJS UI (the new name for zwavejs2mqtt).
-
I'm trying to add dimming and color capabilities to an entity mapped via HASS (it's a Hue dimmable light - I have several I'm moving away from Vera and so I need APIs to integrate them in my existing scenes based on Vera's HTTP APIs - but I digress).
Here's what I have in terms of attributes:
power_switch.state=false x_hass.domain="light" x_hass.entity_id="light.luce_call" x_hass.services=["light"] x_hass.state="off" x_hass_attr.brightness=205 x_hass_attr.color_mode="xy" x_hass_attr.dynamics="none" x_hass_attr.friendly_name="Luce call" x_hass_attr.hs_color=[359.765,100] x_hass_attr.mode="normal" x_hass_attr.rgb_color=[255,0,1] x_hass_attr.supported_color_modes=["xy"] x_hass_attr.supported_features=40 x_hass_attr.xy_color=[0.7004,0.2993]I'm not sure how to proceed (I've already looked at docs).
The test I've done is to add this to local_hass_devices.yaml:
"hass>light_luce_call": service: - color_temperature - dimming - hs_color - rgb_colorBut this doesn't seem to have any effect. Thanks!
-
Is it by design that about page pops up after every update? Would be nice if verification was needed only once.
Screenshot 2022-10-19 at 22.54.08.png(Running on Synology Docker if that makes any difference.)
-
Hi @toggledbits !!
A query, we have the possibility in the Set Reaction to run a Run Reaction and a Stop Reaction. Is it possible some way something like the Reset Rule that you have in the rules panel?
01177be0-a33e-434f-a061-90d3a28b3018-image.png
Explain better, in the rule below the Motion Rule group is already armed, because the devices have already fulfilled the rule and the estimated time of 900 secs has elapsed.
ee9f6f77-6b6d-4b7e-99bf-1aa25ab9b35f-image.png
What I want to do with the Reset Rule, is to reset this counter.
Thanks!
-
Reactor 22240-3b3254d6; Raspian bare-metal (RPi4)
Is it possible to use an expression for “condition must sustained for”? I tried and no error but no result either. When collapsing condition options, the button remains yellow, but the content is no longer displayed when expanded.
Is this a bug or not possible to use an expression for this?
Question about triggers and rule state reset
-
Patrick I have a question if I may?
I have an MSR ruleset to turn on my lounge lights at "40 minutes before sunset".
The trigger for this rule is another rule that evaluates if its 40 minutes before sunset.
Looking at the summary card for the rule that turns on the lights and also for the reference rule for "40 minutes before sunset", they state they reset at 12:00am.
However if I manually turn off my lights before 12:00am or after 12:00am, they are not automatically turned back on again which is correct.
On the Ezlo Meshbot rules that have recently added being able to select one rules state as another rules trigger etc.
However on their current system when I manually turn my lights off, they automatically are turned back on again.
Seems their rule state just looks at "finished" aka its after 40 minutes before sunset.
So seems they are not resetting the referenced rules state for whenever its after "40 minutes before sunset" and that time event has already passed.
Please can you explain how this works in MSR?
Thanks
-
This is what I have in Meshbots trying to replicate the same functionality.
Reference rule to evaluate if its "40 minutes before sunset"
Schedule Rule to turn on my lights with the trigger being the first rules state etc.
-
A little help from the group here, because I'm really struggling with this one. Am I the only one who reads this as "Baker, I like your bread much better than the bread at the new Mega-bakery they are building across town. Can you give me your recipe so I can tell them how to make theirs better?
At the very least, this is a question for the Ezlo forums, not this category here.
-
I didn't mean to offend you Patrick if I have, I was just trying to work out why Meshbot rules weren't working as I expected, I like to keep an eye on what they are doing and test some of their functionality. But if you don't want to answer the question that's fine, I won't ask again.
