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.
G

gwp1

@gwp1
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
580
Topics
61
Shares
0
Groups
0
Followers
0
Following
1

Posts

Recent Best Controversial

  • Gradually turn on lights.
    G gwp1

    @Tom_D I've implemented this as it's much slicker than what I'd been previously doing. Of course, now with longer days and Daylight Saving Time in full effect it doesn't get called on very much so I can't confirm success lol

    Multi-System Reactor

  • Error After Upgrade
    G gwp1

    @tbully thanks for putting a smile on my face today. Much needed. Much appreciated.

    Multi-System Reactor

  • Need help figuring out how to delay a reset on reaction
    G gwp1

    @therealdb I use those as well. As you see in my AWAY rule there's a catch there using a virtual switch for my calendar integration. If a calendar entry has a specific keyword it turns the switch on. If the switch is on, AWAY knows not to fire.... VACA has it covered.

    @toggledbits beat me to it: comments, comments, comments. I've lost too many years off my life trying to remember why this rule does what it does and how.

    Multi-System Reactor

  • Need help figuring out how to delay a reset on reaction
    G gwp1

    @tamorgen said in Need help figuring out how to delay a reset on reaction:

    Thanks to @gwp1 for reminding me to keep it simple

    The thanks goes to @toggledbits who has long endured my questions on things only to have him say "wow... pare this down to smaller bits". Essentially, don't try to do things with "one big beautiful ruleset". 😁

    Multi-System Reactor

  • Need help figuring out how to delay a reset on reaction
    G gwp1

    @tamorgen said in Need help figuring out how to delay a reset on reaction:

    In the new "Go to Away Mode" rule, I added a condition that the mode needs to "Phones Home" rule needs to be sustained for 60 seconds.

    Doesn't the result of that mean the system waits for someone to be home for 60 seconds before flipping mode to HOME?

    Multi-System Reactor

  • Need help figuring out how to delay a reset on reaction
    G gwp1

    @tamorgen You're falling into the same pitfalls I did. Notice my Mode SETs don't have resets. No need. The next appropriate rule SETs so there's no reason to reset. Any resets (like from GUEST back to AWAY or VACA) are done via their own SET rulesets.

    I don't want to reset... I want to move on to another Mode - even if that mode happens to be the last mode I was in. Make sense?

    One thing I have done: every time I change mode I write it to an expression called previous_mode. This let's me do things like "if the previous mode was AWAY, return to AWAY - but if the previous mode was VACA, return to VAC" -- again, these being sep SET rulesets and not RESETs.

    Every time I tried to make use of RESETs I got buried as I had too many "what ifs" in my Conditions.

    Multi-System Reactor

  • Need help figuring out how to delay a reset on reaction
    G gwp1

    @tamorgen reading thru this twice (and I may go back again and slow down even more) it sounds like there's no "link" between your rulesets. ie, the conditions for AWAY is being met even though the conditions for GUEST are, too.

    What does your AWAY ruleset look like?

    Here is my GUEST from AWAY ruleset (I don't have the luxury of surfacing the individual user code so I'm stuck being a bit more generic, ie "lock unlocked". As HOME requires my presence, this has been doing the trick.) My only issue: sometimes the lock is slow to report it's state so I've asked my authorized guests to enter their code, count to 10, the open the door. That let's Hubitat Safety Monitor to disarm.

    d06a8909-4d4f-4aab-a9d5-acde0a00b60e-image.png

    Here is my Change to AWAY for comparison sake.

    4f9fc608-61b8-4571-b649-a00aef491ac9-image.png 8c63571e-40b5-4fa4-b7d1-5d44759e44a0-image.png

    @toggledbits gave me very sound advise early on as I was prone to making my rulesets "do too much" in addition to waaaaaay overthinking/overcomplicating things.

    Instead of trying to make a ruleset that determines presence AND tries to set mode, just have it determine presence. Have one for your immediate family and one for your guests. Then use the TRUE FALSE state of them in your mode rules. (Saves you countless hours later, too, when you add/remove people from either presence ruleset.)

    Multi-System Reactor

  • Need help figuring out how to delay a reset on reaction
    G gwp1

    @tamorgen check the edit to my original post.

    EDIT:

    SO here's how mine is set up. I don't have reset anywhere in mine. I only Set Reaction for the various modes.

    c077b708-fef5-4a99-bb6f-4b09fe4052b9-image.png

    Cracking open my Away config

    1a835b92-f3a2-4dcb-af6a-fe0656c30ab9-image.png

    It's similar to yours except I just do a Set Reaction

    2d6de1c6-98f9-49c7-a66c-b324fdd4868b-image.png

    Each of my modes is this way.

    Multi-System Reactor

  • Need help figuring out how to delay a reset on reaction
    G gwp1

    @tamorgen Your conditions for each inhabitant are collapsed. What's in those?

    I do a TON based on presence so if you can show all your work I can dig in a bit.

    Edit: gonna assume all of the other inhabitants are like Tim. Your current rule says "If Tim=home OR Jen=home OR mom=home OR Nana=home OR Joshua = home OR mode=Guest then".... nothing. You have nothing indicated for it to do. Set Reaction is empty.

    But then you have a Reset Reaction which is what will play out when all of the conditions above aren't met, ie no one is home mode=Away, ie undoing the Set Reaction. Since you have no Set the Reset is confused and just flip/flopping around.

    I think your goal here is to have the house state flip to away when no one is home. As such, you should have Set Reaction be what mode you want the house mode to be when at least one of those people is home. I don't even know that you need that condition for House mode=Guest. The basic goal here is "no one home, set to away", correct?

    Now if you want the house to flip to mode=Away when no one is home, put that in your Reset Reaction. That's not how I've done it personally, but it would get you there if I'm understanding your goal.

    Multi-System Reactor

  • Organizing/ structuring rule sets and rules
    G gwp1

    @RHCPNG As @toggledbits notes, I've found myself bouncing around a bit. I've settled on what I call Shared Rules - those that impact all things potentially, at a base level. Wx stuff, HVAC stuff, etc.

    I kinda branch out from there. Interior lighting, Outdoor lighting, Presence, etc. Sorta using "topics" and then rulesets under them.

    I'm also linked to our local community center via site-to-site VPN and am using my home MSR instance to control the Hubitat C7 over there for lighting and outdoor fans 🙂

    Multi-System Reactor

  • Moving MSR from a QNAP container to RP 5 - some issues
    G gwp1

    @Tom_D please mark issue thread as solved

    Multi-System Reactor

  • Widget deletion does not work and landing page (status) is empy
    G gwp1

    @mgvra the landing page issue was addressed here as a side note in another issue thread: https://smarthome.community/post/16764

    Multi-System Reactor

  • System Configuration Check - time is offset
    G gwp1

    @toggledbits I have indeed used the code... and no, this isn't critical. Once I saw MSR was running and working as intended I moved on. Release AYC.

    @Fanan Re time sync: I did a apt-get install systemd-timesyncd on the Proxmox host. I've not seen the warning since.

    Multi-System Reactor

  • System Configuration Check - time is offset
    G gwp1

    @toggledbits @Fanan Oddly, I have this same issue running MSR in Portainer on Proxmox logging in from multiple workstations and have since I updated to the latest version. I did some time sync work and the alert has gone away... but the host time doesn't show for me, oddly. Also, when first loading the MSR page after login it's blank until I click on STATUS.

    Brave browser. Will try Vivaldi here shortly. Sorry, haven't had two seconds to even look at logs yet.

    image.png

    66c44f34-cd27-4dc1-bd4e-a2b2f8ebc26f-image.png

    Multi-System Reactor

  • [Solved] Runtime error when exiting global reaction that contains a group
    G gwp1

    @toggledbits Confirmed.

    Multi-System Reactor

  • [Solved] Runtime error when exiting global reaction that contains a group
    G gwp1

    @toggledbits not that you need it but I can confirm this behaviour.

    Multi-System Reactor

  • Catch-all lights rule
    G gwp1

    @toggledbits sorry for the delay, day job has a rude habit of interfering in fun.

    This solution worked perfectly for this need. It's actually quite similar to how I control the outdoor garden fountain, HVAC, and some other things. As usual, I tried to over-complicate things.

    EDIT: in fact, I find I am using this EXACT method for my outdoor LIFX lights. sigh

    I am still looking for that context. Will provide when I locate it.

    Multi-System Reactor

  • Catch-all lights rule
    G gwp1

    And then I tried a different approach...

    c5337edc-4416-4b76-957a-358f249d7efa-image.png 3fb6d0a8-5865-414a-a866-111ce6992831-image.png

    This may be another case of me making things more complicated than they need to be...

    Multi-System Reactor

  • Catch-all lights rule
    G gwp1

    @toggledbits I did, however, deconstruct and reconstruct the Catch-All rule last night.

    16c862f3-89a9-46ee-8f36-0f80c068996d-image.png

    99108e45-e9f2-4abc-989f-0868a9a37545-image.png 95e6c0ee-65d0-4f37-9c14-bf0955cc32f3-image.png

    Multi-System Reactor

  • Catch-all lights rule
    G gwp1

    @toggledbits Interesting. Once upon a time you told me to add even a random comment as a placeholder for reset reaction if I had no actually reset action. That's what is in each of these.

    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