Navigation

    Discussion Forum to share and further the development of home control and automation, independent of platforms.

    SmartHome Community

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Unsolved
    (Last Updated: May 27, 2022)
    • Constraints under triggers or under constraints, what is the difference?

      A

      Need to ask, have thougth about this since the move from Rector to MSR I think.

      What is the difference between putting constraints under trigger groups, like this
      23b4a249-3292-41cd-9927-7f49c9bf1d07-image.png

      Compared to this similar rule, but the time limits is under contraints instead?
      ee596c9f-f52b-4a39-9605-f5932f3d9ed5-image.png

      I think the Constraints parts in manual is still to be done because I can only find in the chapter menu, but it is not mentioned anywhere else.

      Multi-System Reactor
    • Adding remotes, scene controllers as entities to MSR

      A

      EDIT: 2022.07.01

      So I will try to remake this thread to some kind of guide for future use, or in worst case a documentation of my failure. At least that could also be useful for letting someone know what didn't work...
      I have zero knowledge of programming, so every time I need to edit a config file in HomeAssistant or similar it requires a good portion of googletime and read, re-reading instructions.
      Also is english not my native language, so bear with me.

      Two goals!
      1: Get MSR to take notice (and then actions of course) of pressed buttons on remotes.
      2: Document what I do in hope I can help someone else in the future.

      I will use a Fibaro Keyfob as described below, but what I understand from Togglebits answers most type of remotes should work in similar ways.

      Original thread:
      Fibaro Keyfob support in MSR? (thru Hassio & Z-wave JS)
      Hi

      I just bought a Fibaro Keyfob FGKF-601 and plan to give this to my son so he can control some stuff in his own room. Primary some lightning and Sonos, maybe blinds in the future.

      As the noob I am it will, of course, not work as I expected.👶🏻

      The remote handle 1x, 2x, 3x clicks per button (six of them) and "release button"
      I thought that it would appear like some "scene controller" in HA and that I could make Rules in MSR depending on what scene-entety that was triggered.
      So is not the case, and if that is because of HA, Z-wave JS or MSR I have no idea.
      I found a HA Blueprint that works in HA, but of course I would prefer to keep all automation in MSR.
      I guess a workaround could be using HA virtual switches "Helpers" that I suppose will come up as an on/off trigger in MSR, but before going this way I would like to check with the wisdom of your guys if there is a better way of doing this.

      I am using:
      MSR 22168 on windows.
      Home Assistant Core 2022.6.7
      Home Assistant Supervisor 2022.05.3
      Home Assistant OS 7.6
      Z-Wave JS version: 0.1.64

      Multi-System Reactor
    • The Home Remote with MSR

      MikeReadington

      Did anyone do/start any work on a full integration with The Home Remote application yet?

      Multi-System Reactor
    • Condition must occur after -restriction not working

      tunnus

      Running MSR 22123 in Docker container and trying to use "condition must occur after" option. Will update to the latest build and log a PR if needed, but wanted to poll first if anyone is using this option successfully?

      I have the following rules:

      Screenshot 2022-06-28 at 15.18.50.png

      Notification activity connected to "Alarm disabled" rule did not trigger. I also did another test with quite simple rules and that didn't work either (FWIIW - when observing that test in "real-time", I didn't see any timer running on the second rule while the first rule was true).

      As said, before going further with debug/logs, nice to know if someone is using this option/restriction (successfully).

      Multi-System Reactor
    • Reactor (Multi-System/Multi-Hub) Announcements

      toggledbits

      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
    • [Solved] Changes in 22178 for HASS sensor no longer provide a value in topic "value", MQTTController echo capability

      Crille

      Before updating to 22178 there was a primary value echoed in MQTTControllers echo capability, can I tell the controller which value to put as primary from HASS sensors after this change as it now is null? or is it a bug?

      I have not changed the

      primary_attributes: true

      mqtt_value.PNG

      Reactor latest-22178 bare metal
      Hass 2022.6.7

      Edit: Solved in build 22179

      Multi-System Reactor
    • Using InfluxDB with MSR

      wmarcolin

      Hi!

      I have a system that I consider pretty stable, running in a VM Ubuntu 20.04, it has some communication failures, but I think more by HE than by the OS/MSR.

      I'm thinking of taking the next step to get more advantages from the system, and I'm thinking of using InfluxDB maybe for queries or to extend rules.

      The question is, I would like practical examples of what really helps to install InfluxDB? What would you be doing that really makes a difference with this installation? Can you post examples of features or information?

      Thanks

      Multi-System Reactor
    • git hub docker container not available?

      Black Cat

      @toggledbits - what now?

      Re: Cheapest platform on which to run MSR

      21aaf68e-c031-414d-847d-d8bec01d57e7-Clipboard01.jpg

      Multi-System Reactor
    • Synology NAS docker image replacement

      MikeReadington

      Hi Everyone,

      MSR had a docker image file naming convention change, and I am not exactly sure how to swap the image out. I'm sure it's not rocket science, I've just never done this before.

      I am using a Synology NAS, and under the environment tab there is a "REACTOR_IMAGE" variable. Can I just change the image name to the new image naming convention and clear the container, or should I launch a new container and populate the volume location from the previous reactor?

      Thanks in advance

      Multi-System Reactor
    • Cheapest platform on which to run MSR

      T

      Please can anyone give me advice on a cheap way to run MSR (both initial cost and ongoing electricity cost). I currently run it on my QNAP network drive (which works very well incidentally). However, this draws a constant 35Watts (£90/yr @ 30p/kWh) and given the recent rise in fuel costs I am evaluating the best way forwards. Note, I only really need to turn my QNAP on for an hour a week to back-up my computer data. I understand that MSR can run on a Raspberry PI, but I am not competent with Linux! Thanks.

      Multi-System Reactor
    • Copying configuraiton and rules from QNAP install to Raspberry PI 4 install

      T

      I have made good progress setting up a new Raspberry PI 4 with the latest OS (64bit) and latest Reactor images in Docker. However I am not able to copy my configuraiton files (.yml) and reactor reactions over. I am not yet that confident with linux commands, so I have tired to drag and drop the files from a USB drive to the working folders in my new Raspberry PI. I am getting a popup in the GUI stating 'The file operation was completed with errors.' and Errors occured: "rule-xxxxxx.json: Error opening file "/home/pi/reactor/....................................json":Permission denied.

      I suspect it's something to do with permissions?

      Is there an easier way to copy my configuration over??

      Multi-System Reactor
    • Alexa TTS via Home Assistant?

      T

      Hello All -

      I'm gradually moving away from Vera to Home Assistant. I've recently gotten the Alexa and Mini Media Player setup in Home Assistant and everything is working well.

      Is there a way to call this service from Reactor? My goal is to send TTS requests to HAAS upon certain events within Reactor (e.g. "Front Door Opened")

      Multi-System Reactor
    • Integrate UPS with MSR

      wmarcolin

      I have a Tripp-Lite UPS (https://www.tripplite.com/smartpro-lcd-120v-1500va-900w-line-interactive-ups-avr-tower-lcd-usb-10-outlets~smart1500lcdt) that connected by a USB cable to my computer, reports various power supply and failure information, as shown in the panel below.

      b9f0ea34-d654-4b26-b968-4f8cf0a4e0c1-image.png

      afa73913-5318-42c6-af9a-02d36e2e6ea1-image.png

      The application I installed runs Java and opens the console to send the information.

      Has anyone tried to bring the information into the MSR? Or even a VeraPlus?

      Thanks.

      Multi-System Reactor
    • Reactor as tab in Hass sidebar

      Matohl

      panel_iframe in configuration.yaml. If you access MSR with HTTP it works in HA with HTTP to Reactor and HTTPS to HTTPS obviously.

      configuration.yaml

      # ============ SIDEBAR ============ panel_iframe: reactor: title: "Reactor" url: "http://192.168.0.23:8111/reactor/sv-SE/"
      Multi-System Reactor
    • Documentation>Network Status

      S

      It appears that in the Manual, under Management>Network Status is for Reactor on Vera. Is the Internet check functionality available with MSR and if so is there updated instructions? I do see a variable reactor_system.internet.ok but the value is null.
      I am looking for a way to check for internet status with MSR before installing an extra app on a hub to get the information.

      Synology Docker latest-22149

      Multi-System Reactor
    • MSR Upgrade from 22119 to 22136 fails, service wont start

      W

      Windows Server 2022 Build 20348
      Nodejs v16.14.0
      Currently running Reactor (Multi-hub) stable-22119-ae7212f
      Linked to Hass 2022.0.5.4 (on a different box)
      Windows server is dedicated to MSR and doesn't do anything else.

      I'd like to upgrade to 22136 to take advantage of the SSL feature added recently, and also to bring my current version of Hass into the 'supported' column with MSR.

      Following the instructions here: link text, section "Upgrade Windows Bare Metal"

      Stop Reactor Service Extract the zip, overwriting the reactor folder in c:\reactor\reactor There is no package-lock.json file so I skip that. Run "npm install --no-save --omit dev"

      Next step is to start the service. I start the service and it immediately stops. "Windows could not start the Reactor service on Local Computer. Error 1067: The process terminated unexpectedly".

      Tried rebooting, service won't stay running.

      I suspect I'm missing something, it's probably obvious but I've not been able to figure it out.

      I rolled back the reactor folder version (Windows Shadow copies) and then the service starts fine.

      Anyone else running Windows and know what I'm missing?

      Tail of log file from running OK version, before upgrade attempt [stable-22119]2022-06-01T22:20:19.081Z <Rule:INFO> Lounge Billy Ambient Lighting - Turn On (Rule#rule-l0ki453b) evaluation complete [stable-22119]2022-06-01T22:20:19.082Z <httpapi:NOTICE> HTTP API v1 22021 base URL http://172.16.128.6:8111; listening [stable-22119]2022-06-01T22:20:19.228Z <app:NOTICE> HTTP server running; registering proxy endpoints. [stable-22119]2022-06-01T22:20:19.228Z <app:NOTICE> Starting WSAPI... [stable-22119]2022-06-01T22:20:19.229Z <wsapi:NOTICE> wsapi: starting version 21334 [stable-22119]2022-06-01T22:20:19.656Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "6/2/2022, 8:20:19 AM" (TZ offset 600 mins from UTC) [stable-22119]2022-06-01T22:27:54.788Z <wsapi:INFO> wsapi: connection from ::ffff:172.16.128.5 Tail of log file from failed to start after upgrade (is identical, ii.e. nothing has been appended to it) [stable-22119]2022-06-01T22:20:19.081Z <Rule:INFO> Lounge Billy Ambient Lighting - Turn On (Rule#rule-l0ki453b) evaluation complete [stable-22119]2022-06-01T22:20:19.082Z <httpapi:NOTICE> HTTP API v1 22021 base URL http://172.16.128.6:8111; listening [stable-22119]2022-06-01T22:20:19.228Z <app:NOTICE> HTTP server running; registering proxy endpoints. [stable-22119]2022-06-01T22:20:19.228Z <app:NOTICE> Starting WSAPI... [stable-22119]2022-06-01T22:20:19.229Z <wsapi:NOTICE> wsapi: starting version 21334 [stable-22119]2022-06-01T22:20:19.656Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "6/2/2022, 8:20:19 AM" (TZ offset 600 mins from UTC) [stable-22119]2022-06-01T22:27:54.788Z <wsapi:INFO> wsapi: connection from ::ffff:172.16.128.5 reactor.wrapper.log (log file the failed to start event points to) 2022-06-02 08:19:23 - Stopping reactor.exe 2022-06-02 08:19:23 - ProcessKill 3628 2022-06-02 08:19:25 - Shutdown exception Message:A system shutdown is in progress. Stacktrace: at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.ManagementScope.InitializeGuts(Object o) at System.Management.ManagementScope.Initialize() at System.Management.ManagementObjectSearcher.Initialize() at System.Management.ManagementObjectSearcher.Get() at winsw.WrapperService.GetChildPids(Int32 pid) at winsw.WrapperService.StopProcessAndChildren(Int32 pid) at winsw.WrapperService.StopIt() at winsw.WrapperService.OnShutdown() 2022-06-02 08:20:11 - Starting C:\Program Files\nodejs\node.exe C:\reactor\reactor\node_modules\node-windows\lib\wrapper.js --file C:\reactor\reactor\app.js --scriptoptions= --log "Reactor wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n --stopparentfirst undefined 2022-06-02 08:20:11 - Started 3272 2022-06-02 08:30:54 - Stopping reactor.exe 2022-06-02 08:30:54 - ProcessKill 3272 2022-06-02 08:30:54 - Found child process: 3280 Name: conhost.exe 2022-06-02 08:30:54 - Found child process: 3504 Name: node.exe 2022-06-02 08:30:54 - Stopping process 3280 2022-06-02 08:30:54 - Send SIGINT 3280 2022-06-02 08:30:54 - SIGINT to 3280 failed - Killing as fallback 2022-06-02 08:30:54 - Stopping process 3504 2022-06-02 08:30:54 - Send SIGINT 3504 2022-06-02 08:30:54 - SIGINT to 3504 failed - Killing as fallback 2022-06-02 08:30:54 - Stopping process 3272 2022-06-02 08:30:54 - Send SIGINT 3272 2022-06-02 08:30:54 - SIGINT to 3272 failed - Killing as fallback 2022-06-02 08:30:54 - Finished reactor.exe 2022-06-02 08:33:41 - Starting C:\Program Files\nodejs\node.exe C:\reactor\reactor\node_modules\node-windows\lib\wrapper.js --file C:\reactor\reactor\app.js --scriptoptions= --log "Reactor wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n --stopparentfirst undefined 2022-06-02 08:33:41 - Started 4184 2022-06-02 08:36:57 - Starting C:\Program Files\nodejs\node.exe C:\reactor\reactor\node_modules\node-windows\lib\wrapper.js --file C:\reactor\reactor\app.js --scriptoptions= --log "Reactor wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n --stopparentfirst undefined 2022-06-02 08:36:57 - Started 3100 Windows event log event: Child process [4184 - C:\Program Files\nodejs\node.exe C:\reactor\reactor\node_modules\node-windows\lib\wrapper.js --file C:\reactor\reactor\app.js --scriptoptions= --log "Reactor wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n --stopparentfirst undefined] finished with 1
      Multi-System Reactor
    • [Solved] suninfo.period "night" and rule trigger for sunset are at different times

      Crille

      I'm just curious, what's the difference between suninfo.period changing from "day" to "night" vs "after sunset" with no offset?
      suninfo.period changes to "night" 7 minutes and 33 seconds before "after sunset" is triggered in my latest-22149 bare metal setup.

      Multi-System Reactor
    • Status page rule history length.

      MikeReadington

      Hello Patrick,

      On the status page rule history is there any adjustably on length of the history shown? I had an occasion where it would have been helpful to go a few notches farther back than it does as currently configured.

      I don't know if this is a log parser or if it is a separate smaller data set. If it is a log parser, any chance for maybe something like a "more" button?

      Thanks,
      Mike

      Multi-System Reactor
    • [Solved] New device on Ezlo is not added in Reactor

      Crille

      I can't find any posts or reference in docs for this log message

      <EzloController:NOTICE> EzloController#ezlo received notice of new device, but auto-rediscover is OFF; ignoring

      I've restarted MSR and hard refreshed browser but the new entity is not added. Can I set auto-rediscover to ON or how do I get the new device added into Reactor?

      Edit:
      Bare metal latest-22142
      The device is a Xiaomi Mini Switch, it's publishing correct values in ezmqtt.

      Edit 2: The Xiaomi Aqara Mini Switch is now mapped in build 22149.

      Multi-System Reactor
    • Disk Warning on Multisystem Reactor

      S

      334ccd7a-9499-4dea-8a4a-2347609dce62-image.png

      For the life of me I cannot figure this out.
      when I run the du -hs command (from the host) for the mapped volume I get 25M
      (/home/seth/ReactorConfig maps to /var/reactor)

      Inside the container I ran du -hs for each of the folders that the ui is complaining about
      /opt/reactor = 71.2M
      /var/reactor/storage = 2.9M
      /var/reactor/logs = 17.6M

      If I run df on the docker container I get this. Disk space is not critical
      1f5d230c-0792-468b-b3b7-9f45e31581c5-image.png

      What gives?

      Multi-System Reactor
    For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used

    Up and running

    Multi-System Reactor
    3
    9
    80
    Loading More Posts
    • 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.
    • CatmanV2
      CatmanV2 last edited by

      After much (un-necessary) faffing on Debian 10 I got MSR up and running in about 10 minutes flat this morning, on the same box as AltUI

      As a warning, expect lots of stupid questions. 😉

      C

      The Ex-Vera abuser know as CatmanV2.....

      1 Reply Last reply Reply Quote 2
      • CatmanV2
        CatmanV2 last edited by CatmanV2

        Ummm, ok this is embarrassing....

        I'm actually stuck on creating the simplest rule set / reaction. I can't see anything in the manual that indicates my stupidity, and it's surely not a bug so here goes.

        Bare metal install on Debian 10
        Simple 'AND' test rule which I can see setting and resetting as the conditions change.

        I have tried putting a reaction in that rule set to turn on a light. So literally
        Entity action > Table Lamp > power_switch.on

        If I press the 'Try this action' button from within the reaction, the light goes on.
        If I press the 'Run Now' button from the Global reactions list:

        1.0.2-21350]2022-05-26T16:20:45.257Z <Engine:NOTICE> Starting reaction Test motion lights<SET> (rule-l3n662g0:S)
        [1.0.2-21350]2022-05-26T16:20:45.257Z <Engine:INFO> Test motion lights<SET> all actions completed.
        [1.0.2-21350]2022-05-26T16:20:59.510Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.70.64
        [1.0.2-21350]2022-05-26T16:21:13.051Z <wsapi:INFO> client "192.168.70.64#4" closed, code=1001, reason=
        [1.0.2-21350]2022-05-26T16:21:15.726Z <Rule:INFO> Test motion lights (Rule#rule-l3n662g0) RESET!
        [1.0.2-21350]2022-05-26T16:25:03.556Z <VeraController:ERR> VeraController#vera update request failed: [FetchError]FetchError: network timeout at: http://192.168.70.249:3480/data_request?id=status&DataVersion=938493960&Timeout=15&MinimumDe
        lay=50&output_format=json&_r=1653582285543
        [1.0.2-21350]2022-05-26T16:26:17.531Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:26:17.536Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:26:17.537Z <Engine:INFO> Simple Test Reaction all actions completed.
        [1.0.2-21350]2022-05-26T16:26:45.444Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20200 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20200, "id": "action", "serviceId": "urn
        :upnp-org:serviceId:SwitchPower1", "action": "SetTarget" }
        [1.0.2-21350]2022-05-26T16:26:49.094Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20200 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20200, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "SetTarget" }
        [1.0.2-21350]2022-05-26T16:26:59.543Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:26:59.543Z <Engine:NOTICE> Reaction re-l3n7rrij (Simple Test Reaction) is disabled; run aborted.
        [1.0.2-21350]2022-05-26T16:27:03.286Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:27:03.287Z <Engine:NOTICE> Reaction re-l3n7rrij (Simple Test Reaction) is disabled; run aborted.
        [1.0.2-21350]2022-05-26T16:27:20.861Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:27:20.861Z <Engine:NOTICE> Reaction re-l3n7rrij (Simple Test Reaction) is disabled; run aborted.
        [1.0.2-21350]2022-05-26T16:27:23.575Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:27:23.576Z <Engine:NOTICE> Reaction re-l3n7rrij (Simple Test Reaction) is disabled; run aborted.
        [1.0.2-21350]2022-05-26T16:27:47.538Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:27:47.542Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:27:47.543Z <Engine:INFO> Simple Test Reaction all actions completed.
        [1.0.2-21350]2022-05-26T16:28:14.393Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:28:14.397Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:28:14.397Z <Engine:INFO> Simple Test Reaction all actions completed.
        [1.0.2-21350]2022-05-26T16:28:24.225Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:28:24.228Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:28:24.229Z <Engine:INFO> Simple Test Reaction all actions completed.
        [1.0.2-21350]2022-05-26T16:28:35.395Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20200 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20200, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "SetTarget" }
        [1.0.2-21350]2022-05-26T16:29:12.974Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20160 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20160, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "SetTarget" }
        [1.0.2-21350]2022-05-26T16:29:25.885Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:29:25.889Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:29:25.889Z <Engine:INFO> Simple Test Reaction all actions completed.
        [1.0.2-21350]2022-05-26T16:29:50.139Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:29:50.143Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:29:50.143Z <Engine:INFO> Simple Test Reaction all actions completed.
        [1.0.2-21350]2022-05-26T16:33:05.815Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:33:05.825Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:33:05.826Z <Engine:INFO> Simple Test Reaction all actions completed.
        [1.0.2-21350]2022-05-26T16:35:15.688Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:35:15.692Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:35:15.692Z <Engine:INFO> Simple Test Reaction all actions completed.
        [1.0.2-21350]2022-05-26T16:37:17.185Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20160 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20160, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "SetTarget" }
        [1.0.2-21350]2022-05-26T16:37:44.912Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:37:44.916Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij)
        [1.0.2-21350]2022-05-26T16:37:44.917Z <Engine:INFO> Simple Test Reaction all actions completed.
        [1.0.2-21350]2022-05-26T16:38:39.696Z <Rule:INFO> Test motion lights (Rule#rule-l3n662g0) SET!
        [1.0.2-21350]2022-05-26T16:38:39.703Z <Engine:INFO> Enqueueing "Test motion lights<SET>" (rule-l3n662g0:S)
        [1.0.2-21350]2022-05-26T16:38:39.717Z <Engine:NOTICE> Starting reaction Test motion lights<SET> (rule-l3n662g0:S)
        [1.0.2-21350]2022-05-26T16:38:39.717Z <Engine:INFO> Test motion lights<SET> all actions completed.
        [1.0.2-21350]2022-05-26T16:39:10.418Z <Rule:INFO> Test motion lights (Rule#rule-l3n662g0) RESET!
        [1.0.2-21350]2022-05-26T16:41:56.241Z <VeraController:ERR> VeraController#vera update request failed: [FetchError]FetchError: network timeout at: http://192.168.70.249:3480/data_request?id=status&DataVersion=938494294&Timeout=15&MinimumDelay=50&output_format=json&_r=1653583298238
        
        

        But the light never comes on

        Similarly although the test Rule set is supposed to trigger 'Simple Test Reaction', the light never turns on.

        The reaction is enabled. The rule set is enabled.

        Time zone is BST (trying to conform to the log requests in the manual!)

        I'm sorry! It's going to be something really dumb but I've spent about an hour so far 😞

        C

        The Ex-Vera abuser know as CatmanV2.....

        1 Reply Last reply Reply Quote 0
        • G
          gwp1 last edited by

          Screenshot of the ruleset?

          Hubitat C-7 2.3.0.124, Home Assistant 2022.2.9, MSR on RPi4 bare metal Model B 2GBs latest-22168-5ab4d6c2

          CatmanV2 1 Reply Last reply Reply Quote 0
          • CatmanV2
            CatmanV2 @gwp1 last edited by

            @gwp1 said in Up and running:

            Screenshot of the ruleset?

            Of course, but given the Reaction doesn't do anything...
            Screenshot 2022-05-26 at 19.46.47.png

            It's crazy simple. Obviously the rule won't trigger under these circumstances as the motion sensor is not tripped, but even when it does....no reaction

            Cheers

            C

            The Ex-Vera abuser know as CatmanV2.....

            1 Reply Last reply Reply Quote 0
            • toggledbits
              toggledbits last edited by toggledbits

              Well, first, you're on an ancient build. I would start by getting on latest.

              After that, the log messages are telling you it can't talk to the Vera. Do you see those?

              [1.0.2-21350]2022-05-26T16:25:03.556Z <VeraController:ERR> VeraController#vera update request failed: [FetchError]FetchError: network timeout at: http://192.168.70.249:3480/data_request?id=status&DataVersion=938493960&Timeout=15&MinimumDe
              lay=50&output_format=json&_r=1653582285543
              

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

              CatmanV2 1 Reply Last reply Reply Quote 0
              • CatmanV2
                CatmanV2 @toggledbits last edited by

                @toggledbits Ahh, OK. I didn't check the version. I'll upgrade.

                Yes I did see it can't talk to Vera but given that I can run the action directly I figured that was looking at something else it was trying to do.....

                Clearly all the entities are in place, and updating in real time, as is the rule set so my takeaway was that it can talk to Vera (at least for these functions.

                Cheers

                C

                The Ex-Vera abuser know as CatmanV2.....

                1 Reply Last reply Reply Quote 0
                • CatmanV2
                  CatmanV2 last edited by

                  OK, updated and working.

                  Told you it would be something stupid, although it was only 2 months old 😉

                  Thanks, as ever

                  C

                  The Ex-Vera abuser know as CatmanV2.....

                  toggledbits 1 Reply Last reply Reply Quote 0
                  • toggledbits
                    toggledbits @CatmanV2 last edited by

                    @catmanv2 said in Up and running:

                    although it was only 2 months old

                    If you mean the release, the stamp 21350 means December 16, 2021, so that's more than five months ago. Things change fast around here!

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

                    CatmanV2 1 Reply Last reply Reply Quote 1
                    • CatmanV2
                      CatmanV2 @toggledbits last edited by

                      @toggledbits said in Up and running:

                      @catmanv2 said in Up and running:

                      although it was only 2 months old

                      If you mean the release, the stamp 21350 means December 16, 2021, so that's more than five months ago. Things change fast around here!

                      Ahh I was looking at the date stamp on the download. Thanks, as ever 🙂

                      C

                      The Ex-Vera abuser know as CatmanV2.....

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post

                      Welcome. If you’d like to participate in the discussion, rather than just read, then you can join the forum. As a member, you can interact with others here to share your experience and ask the questions you need answered.

                      Powered by NodeBB | Contributors
                      Hosted freely by PointPub Media Communications Inc. | Contact us