Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
W

whyfseeguy

@whyfseeguy
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Wiring Samotech SM308-S into light fitting
F
Hi Smart Home Community. I have used a Sonos inline WiFi switch to make one of my light fittings smart, but it requires a hard reset for WiFi changes, plus it isn't zigbee compatible, which means I can't use the Hue app to control it with the rest of the lights. To that end I bought a Samotech SM308-S as it is recommended as the better than the Sonos equivalent. I am however not exactly sure how to wire it in. The manual is available here Can anyone help me by clarifying which ports I need to use, and whether I should be using the live or switched live line for live etc. I will be keeping using standard switches for a while, although hope to upgrade to tap dials once I have all the fittings upgraded. Thanks
Hardware
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
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.
Multi-System Reactor
Z-Wave Future....
DesTD
https://forum.z-wave.me/viewtopic.php?f=3417&t=36140 That's not a good thing I think Time to switch again?
Z-Wave.me
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Disaster recovery and virtualisation
CatmanV2C
Following on from my last thread, some progress has been made over the weekend. With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system. Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic. Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work. Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic. Once that hurdle is sorted I'm torn between: Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.) Decisions, decisions. C
General Discussion
Remote access of Zwave stick from Z-wave server
CatmanV2C
Topic thumbnail image
Software
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
About
Posts
10
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • TTS in MSR?
    W whyfseeguy

    It is working now with your recipe. I had too many "data" in data field. I was following the examples above and got confused.

    Multi-System Reactor

  • TTS in MSR?
    W whyfseeguy

    What did I do wrong?

    The service works in HA scripts but not in Reactor
    cf98e30f-bc95-4b3c-8e3f-60ea0d96d470-image.png

    Multi-System Reactor

  • Wait for http response before running the next http request
    W whyfseeguy

    In my work flow, I send a number of http requests to my device. Is it possible to wait for a http response of the current action before executing the next http request action?

    Thanks.

    Multi-System Reactor

  • Using Hikvision HTTP API request with MSR
    W whyfseeguy

    Here is an example of what I did with my Hikvision camera settings using MSR and ISAPI to change the scheduled switch (day/night) based on sunrise/sunset daily etc. Nearly all configurable options on the Hikvision can be changed with ISAPI.

    HTTP Request: PUT
    Request URL: http://user:pass@ipcamaddr:80/ISAPI/Image/channels/1/ISPMode
    Request Header: Content-Type: application/xml
    Request Body:

    <ISPMode xmlns="http://www.hikvision.com/ver20/XMLSchema" version="2.0">
    <mode>schedule</mode>
    <Schedule>
    <scheduleType>day</scheduleType>
    <TimeRange>
    <beginTime>${{hikvision_sunrise}}</beginTime>
    <endTime>${{hikvision_sunset}}</endTime>
    </TimeRange>
    </Schedule>
    </ISPMode>
    

    Capture response to:
    text_response

    set the following expressions:

    text_response=
    
    hikvision_sunrise=strftime( "%R" , ( getEntity( "reactor_system>sun" ).attributes.suninfo.sunrise + ( 30 * 60 * 1000 ) ) )
    
    hikvision_sunset=strftime( "%R", ( getEntity( "reactor_system>sun" ).attributes.suninfo.sunset - ( 30 * 60 * 1000 ) ) )
    

    I offset the sunrise and sunset time by 30 mins both ways (30 * 60 * 1000). You can use civil dusk and civil dawn too if that works better for you.

    For IRCut Filter, which is where the supplemental light setting is located, set it to ON then control it with the scheduled switch (there is no ISAPI to set it on/off unfortunately)

    Request:
    http://user:passipcamaddr:80/ISAPI/Image/channels/1/IrcutFilter
    Header is the same as above
    Body:

    <IrcutFilter xmlns="http://www.hikvision.com/ver20/XMLSchema" version="2.0">
    	<IrcutFilterType>schedule</IrcutFilterType>
    	<nightToDayFilterLevel>4</nightToDayFilterLevel>
    	<nightToDayFilterTime>5</nightToDayFilterTime>
    	<Schedule>
    		<scheduleType>day</scheduleType>
    		<TimeRange>
    			<beginTime>${{hikvision_sunrise}}</beginTime>
    			<endTime>${{hikvision_sunset}}</endTime>
    		</TimeRange>
    	</Schedule>
    </IrcutFilter>
    

    With ISAPI, there are many more things you can set on the camera without using the GUI.

    Multi-System Reactor

  • Error importing backup from vera
    W whyfseeguy

    I did a pull, now running 21257. Import seems to be working. The import tool created a bunch of rules from Vera Reactor. I will go through them 1 at a time to make the necessary changes. I will report back later if there are issues related to this.

    Thanks again.

    Multi-System Reactor

  • Error importing backup from vera
    W whyfseeguy

    Yes I am using Vera Geofencing.

    Multi-System Reactor

  • Error importing backup from vera
    W whyfseeguy

    Hi Patrick,

    Running MSR on docker.

    Trying to import the reactor config from Vera.

    My workflow is:

    1. docker exec -it reactor /bin/sh
    2. /opt/reactor # node tools/import_reactor_backup.js /var/reactor/reactor-config-backup.json vera

    Got the following error: (After restarting, no reactor config from Vera was imported)
    Fetching current rulesets...
    Pass 1: Translating...
    ReactorSensor 134 Auto (un)lock doors
    Creating ruleset for ReactorSensor 134 Auto (un)lock doors
    Creating rule rule-134
    ReactorSensor 139 Auto Lights
    Creating ruleset for ReactorSensor 139 Auto Lights
    Creating rule rule-139
    ReactorSensor 143 Somfy Control
    Creating ruleset for ReactorSensor 143 Somfy Control
    Creating rule rule-143
    ReactorSensor 167 Blue Iris Control
    Creating ruleset for ReactorSensor 167 Blue Iris Control
    Creating rule rule-167
    ReactorSensor 183 Towel and Heater Sch
    Creating ruleset for ReactorSensor 183 Towel and Heater Sch
    Creating rule rule-183
    ReactorSensor 208 Geofencing Action
    Creating ruleset for ReactorSensor 208 Geofencing Action
    Creating rule rule-208
    (node:639) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'split' of undefined
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:185:82)
    at /opt/reactor/tools/import_reactor_backup.js:44:13
    at Array.forEach (<anonymous>)
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
    at /opt/reactor/tools/import_reactor_backup.js:44:13
    at Array.forEach (<anonymous>)
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
    at /opt/reactor/tools/import_reactor_backup.js:438:13
    at Array.forEach (<anonymous>)
    at /opt/reactor/tools/import_reactor_backup.js:402:34
    (Use node --trace-warnings ... to show where the warning was created)
    (node:639) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
    (node:639) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

    Any help will be appreciated. The worst case scenario is to re-do all the triggers and conditions in MSR from the ground up.

    Multi-System Reactor

  • MSR http PUT error
    W whyfseeguy

    I updated to 21256 (docker). The http put is working for me now. Thank you for the quick fix to the issue.

    Multi-System Reactor

  • MSR http PUT error
    W whyfseeguy

    Hi Patrick,

    I got a 403 when the body is empty, indicating it has passed through the MSR, it got rejected by the camera. So I say it is working without the body as MSR did not throw an error.

    Thanks.

    Multi-System Reactor

  • MSR http PUT error
    W whyfseeguy

    Using MSR on Docker. The automation is to send xml body to my Hikvision camera to change the WDR based on the time of day. But getting the following error:

    TypeError: Cannot read property 'length' of undefined
    at Engine._resume_reaction (/opt/reactor/server/lib/Engine.js:1319:192)
    at Engine._process_reaction_queue (/opt/reactor/server/lib/Engine.js:1114:100)

    My MSR rule:

    HTTP Request: PUT

    HTTP Request: http://camipaddr/ISAPI/Image/channels/1/WDR/day
    HTTP Header: Content-Type: application/xml; charset="UTF-8"
    HTTP Body:
    <?xml version="1.0" encoding="UTF-8"?>
    <WDR version="2.0" xmlns="http://www.hikvision.com/ver20/XMLSchema">
    <mode>open</mode>
    <WDRLevel>40</WDRLevel>
    </WDR>

    Any idea why I am getting the above error?

    Thanks.

    Multi-System Reactor
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved