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.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Added IP camera to Ezlo, what is causing this
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
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
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
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
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor

Added IP camera to Ezlo, what is causing this

Scheduled Pinned Locked Moved Multi-System Reactor
5 Posts 2 Posters 245 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • CrilleC Offline
    CrilleC Offline
    Crille
    wrote on last edited by
    #1

    @toggledbits I added an IP camera to my Ezlo for testing and my global variable for Ezlo devices that are not responding randomly do a quick toggle from empty to "IP camera" then back to empty.
    Is it the controller interface not supporting IP cameras or something else causing this?
    @2021-10-19T23:24:07.826Z

    [latest-21292]2021-10-19T23:10:00.043Z <Engine:NOTICE> Resuming reaction Schema - Dräneringspump<SET> (rule-ktd8obiy:S) from step 2
    [latest-21292]2021-10-19T23:10:00.043Z <Engine:5:Engine.js:1504> Engine#1 reaction rule-ktd8obiy:S step 2 perform { "entity": "vera>device_53", "action": "power_switch.off" }
    [latest-21292]2021-10-19T23:10:00.043Z <Engine:5:Engine.js:1407> _process_reaction_queue() task returned, new status 3; task 29
    [latest-21292]2021-10-19T23:10:00.044Z <VeraController:null> VeraController#vera enqueue task for Entity#vera>device_53 action power_switch.off: task { "newTargetValue": "0", "DeviceNum": 53, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "SetTarget" }
    [latest-21292]2021-10-19T23:10:00.044Z <Engine:5:Engine.js:1442> _process_reaction_queue ending with 1 in queue; none delayed/ready; waiting
    [latest-21292]2021-10-19T23:10:00.048Z <Engine:5:Engine.js:1442> _process_reaction_queue() wake-up!
    [latest-21292]2021-10-19T23:10:00.049Z <Engine:5:Engine.js:1403> _process_reaction_queue() running task 29 { "tid": 29, "id": "rule-ktd8obiy:S", "rule": "rule-ktd8obiy", "__reaction": [RuleReaction#rule-ktd8obiy:S], "next_step": 3, "status": 1, "ts": 1634684400015, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 3 }
    [latest-21292]2021-10-19T23:10:00.049Z <Engine:NOTICE> Resuming reaction Schema - Dräneringspump<SET> (rule-ktd8obiy:S) from step 3
    [latest-21292]2021-10-19T23:10:00.049Z <Engine:INFO> Schema - Dräneringspump<SET> all actions completed.
    [latest-21292]2021-10-19T23:10:00.049Z <Engine:5:Engine.js:1407> _process_reaction_queue() task returned, new status -1; task 29
    [latest-21292]2021-10-19T23:10:00.050Z <Engine:5:Engine.js:1442> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting
    [latest-21292]2021-10-19T23:17:00.724Z <VeraController:ERR> VeraController#vera update request failed: FetchError: network timeout at: http://127.0.0.1:3480/data_request?id=status&DataVersion=574966431&Timeout=15&MinimumDelay=100&output_format=json&_r=1634685402721
    [latest-21292]2021-10-19T23:24:07.826Z <EzloController:WARN> EzloController#ezlo warning: update parameter serviceNotification for Entity#ezlo>device_615e11a7129e071220cb5f8d not previously defined! (value now (boolean)false)
    [latest-21292]2021-10-19T23:24:07.826Z <EzloController:WARN> EzloController#ezlo warning: update parameter syncNotification for Entity#ezlo>device_615e11a7129e071220cb5f8d not previously defined! (value now (boolean)false)
    [latest-21292]2021-10-19T23:24:07.828Z <Rule:INFO> Rule#rule-ku32xyj5 evaluation in progress; waiting for completion
    [latest-21292]2021-10-19T23:24:07.828Z <Rule:INFO> Rule#rule-kue8adhf evaluation in progress; waiting for completion
    [latest-21292]2021-10-19T23:24:07.828Z <Engine:5:Engine.js:981> Engine#1 set global EzloDevicesNotResponding; value=(string)IP Camera
    [latest-21292]2021-10-19T23:24:12.474Z <Rule:INFO> Rule#rule-ku32xyj5 evaluation in progress; waiting for completion
    [latest-21292]2021-10-19T23:24:12.475Z <Rule:INFO> Rule#rule-kue8adhf evaluation in progress; waiting for completion
    [latest-21292]2021-10-19T23:24:12.476Z <Engine:5:Engine.js:981> Engine#1 set global EzloDevicesNotResponding; value=(string)
    [latest-21292]2021-10-19T23:24:12.482Z <Rule:INFO> Notifiering - Ezlo devices OK (Rule#rule-kue8adhf) SET!
    [latest-21292]2021-10-19T23:24:12.483Z <Engine:5:Engine.js:1442> _process_reaction_queue() wake-up!
    [latest-21292]2021-10-19T23:24:12.487Z <Rule:INFO> Notifiering - Ezlo devices OK (Rule#rule-kue8adhf) RESET!
    
    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by toggledbits
      #2

      I need a more complete picture than this. Show the rule(s) involved and the global variables, please. There is a rule toggling at the end of the log snippet, but since you haven't really given me any context to know what is what, what it's doing or not doing, and why, I have no context for what I'm looking at.

      And actually, now that I look at it, am I even looking at the rules, or are you just asking about the two log entries at the timestamp you gave? Not clear what your question/problem is....?

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      CrilleC 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        I need a more complete picture than this. Show the rule(s) involved and the global variables, please. There is a rule toggling at the end of the log snippet, but since you haven't really given me any context to know what is what, what it's doing or not doing, and why, I have no context for what I'm looking at.

        And actually, now that I look at it, am I even looking at the rules, or are you just asking about the two log entries at the timestamp you gave? Not clear what your question/problem is....?

        CrilleC Offline
        CrilleC Offline
        Crille
        wrote on last edited by
        #3

        @toggledbits Sorry for not giving the whole picture. My question is if you know why "IP Camera" is added and removed from the variable within seconds.
        Looking at it further myself though it seems like the Ezlo actually is reporting this device as "not reachable" for a few seconds, I misread the log and thought it was within ms and the WARN of "not previously defined" made me curious.

        The rule is just sending me a notification and triggers if the variable changes from anything to anything AND variable == string"", Pulse for 1 second.
        rule.PNG

        The global expression is
        expression.PNG

        Sorry to bother unnecessary 🙂
        I guess I'll just remove the camera or filter it out in the expression as it's sending me notifications that all devices are responding again when my other rule that notifies me of devices not responding haven't had the chance to pick up the quick toggle.

        1 Reply Last reply
        0
        • toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by toggledbits
          #4

          The logs are showing that the eZLO is sending updates, and apparently that value changed state twice in about 5 seconds: you can see at 24:07 where the global variable changes, so it has gotten one update and handled it, and then at 24:12 it has gotten another and changed it back. It would be an eZLO-side mystery to unravel why it's sending not-reachable followed by reachable so quickly, maybe a bug in their firmware, maybe just the way it works. It seems possible, even likely, that during any restart of the hub, devices would be marked down until they are known up, and some will just be left in the last known state until a new state is established, and given that the Vera engineering team is still present for the eZLO firmware, I'm sure they are still up to their old tricks and there is some inconsistency in which is chosen for which device or device class/type. I would not be at all surprised if IP-driven devices (like cameras) are marked for failure immediately when any request to the device fails, even on the first try, so lapses in network/wifi or the camera itself may lead to spurious marking of the device as failed followed by a quick recovery. These are all very real risks of the problem being solved.

          So, probably something to mention in the other thread on this general (device error) subject: you may need to add a "sustained for" to your rule to dampen response, to allow for such momentary lapses, which are probably more common than we've ever realized, but will be on full display now that people are implementing rules like this.

          The logged warnings... since eZLO is such a great unfinished unknown, and there are many inconsistencies and undocumented behaviors of their system and API, when an update for a device from the API arrives with a value that was not in the first device inventory, the warning is issued. Reactor then just adds the value to the device and carries on as if it was always there. So that's largely debug/notice of a surprise, but nothing harmful. And I'm not sure the values involved are even documented; I'll have to look (serviceNotification is known according to the API docs, and seems to be an internal value; syncNotification is undocumented). But in any case, the warnings are advisory only and harmless and irrelevant to behavior here.

          Thanks for posting the screen shots in English! 🙂

          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

          CrilleC 1 Reply Last reply
          1
          • toggledbitsT toggledbits

            The logs are showing that the eZLO is sending updates, and apparently that value changed state twice in about 5 seconds: you can see at 24:07 where the global variable changes, so it has gotten one update and handled it, and then at 24:12 it has gotten another and changed it back. It would be an eZLO-side mystery to unravel why it's sending not-reachable followed by reachable so quickly, maybe a bug in their firmware, maybe just the way it works. It seems possible, even likely, that during any restart of the hub, devices would be marked down until they are known up, and some will just be left in the last known state until a new state is established, and given that the Vera engineering team is still present for the eZLO firmware, I'm sure they are still up to their old tricks and there is some inconsistency in which is chosen for which device or device class/type. I would not be at all surprised if IP-driven devices (like cameras) are marked for failure immediately when any request to the device fails, even on the first try, so lapses in network/wifi or the camera itself may lead to spurious marking of the device as failed followed by a quick recovery. These are all very real risks of the problem being solved.

            So, probably something to mention in the other thread on this general (device error) subject: you may need to add a "sustained for" to your rule to dampen response, to allow for such momentary lapses, which are probably more common than we've ever realized, but will be on full display now that people are implementing rules like this.

            The logged warnings... since eZLO is such a great unfinished unknown, and there are many inconsistencies and undocumented behaviors of their system and API, when an update for a device from the API arrives with a value that was not in the first device inventory, the warning is issued. Reactor then just adds the value to the device and carries on as if it was always there. So that's largely debug/notice of a surprise, but nothing harmful. And I'm not sure the values involved are even documented; I'll have to look (serviceNotification is known according to the API docs, and seems to be an internal value; syncNotification is undocumented). But in any case, the warnings are advisory only and harmless and irrelevant to behavior here.

            Thanks for posting the screen shots in English! 🙂

            CrilleC Offline
            CrilleC Offline
            Crille
            wrote on last edited by
            #5

            @toggledbits Sustained for is the way to go here, thank you for your advice.

            I can say that for Zigbee devices their firmware is a mess, a reboot of the controller marks all devices unreachable until they are physically toggled or reporting new sensor values, so rebooting means going around the house like a fool toggling lights and blowing on temp/humidity sensors, and if you don't do it fast enough you have to reboot again to give the devices a new chance to phone home in time. 🙂

            1 Reply Last reply
            0
            • toggledbitsT toggledbits locked this topic on
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            Recent Topics

            • Gradually turn on lights.
              G
              gwp1
              0
              4
              132

            • Stop the MSR by an external switch on Hubitat.
              wmarcolinW
              wmarcolin
              0
              1
              31

            • Error After Upgrade
              G
              gwp1
              0
              4
              104

            • Reset attribute value of entity in event handler
              R
              RHCPNG
              0
              5
              203

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

            • Way to search for rules (rule state) in other rules
              T
              tamorgen
              0
              3
              99

            • Links to MSR from HA
              Tom_DT
              Tom_D
              0
              1
              90

            • Set Reaction > Script Action
              wmarcolinW
              wmarcolin
              0
              11
              433

            • Wiring Samotech SM308-S into light fitting
              akbooerA
              akbooer
              0
              2
              148

            • Errors after updating to MQTTController build 25139
              toggledbitsT
              toggledbits
              0
              6
              238

            • 🎉 My very first MSR controller: OpenSprinkler
              therealdbT
              therealdb
              5
              13
              918

            • Advice reqeusted to migrate MSR from Bare Metal to Container
              T
              tamorgen
              0
              5
              260
            Powered by NodeBB | Contributors
            Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
            • Login

            • Don't have an account? Register

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