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
    1. Home
    2. tbully

    • [Solved] Expressions - predefining a variable type

      PerH

      I have a use case where I need to have a boolean variable that will be set to true/false by reactions.

      I see that i can define a local variable by giving it a name and leaving the definition empty. This leaves it at state "null" until a reaction tells it that its a boolean.

      Is there a way to tell it that it should start out as "false" (i.e when reactor has restarted), and not null?

      Am i going about this the wrong way?

      -- The use case is that I have a sensor on my fireplace, and the following logic is for notifying when its time to get up en refill with firewood.. I also want to reset the MaxInInterval to CurrentTemp when notification is sent..

      1fd2951f-cb6b-4a2f-b957-1e0698171f4d-image.png dd99634e-f0ad-4878-bb87-0284c2df5535-image.png

      Edit: better screenhots. Reactor version 23010-7dd2c9e9

      Multi-System Reactor

    • Trying to add second Hubitat controller

      R

      Converting from Vera Plus to Hubitat at two different locations. The two sites are interconnected via a router-to-router VPN. I currently have a Hubitat C7 running at Site One and a Vera Plus at Site Two. The MSR Raspberry Pi is co-located with the Vera Plus at Site Two. I "activated" a Hubitat C8 (ethernet connected) at Site Two including the installation of Hub Information Driver and its associated device. I also installed a single zwave outlet module (GE ZW4202). I restarted MSR. The C8 and its associated devices appear on both the Entities page and the MSR Dashboard, but the C8 reports as down on the MSR Status page and the GE outlet does not respond when "clicked". I am not sure where to look to try to find the source of the problem and will greatly appreciate any suggestions.

      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

    • Home assistant addon: Import Vera/Openluup backup

      R

      Hi guys,

      I want to import my reactor sensors in the MSR addon for Home Assistant, but I can't find the app.js file anywhere. So now I don't know where to put the backup file.

      I have not tried to put it in the main directory (config/reactor) yet. Wanted to know if I'm the only one with the problem.

      Reactor addon: v0.0.8
      MSR: 23063-c464b685
      Home Assistant 2023.3.3
      Supervisor 2023.03.1
      Operating System 9.5
      Frontend 20230202.0 - latest

      I started with v0.0.7, have just updated everything. Still no file.

      Multi-System Reactor

    • Logic Programming

      akbooer

      Home Automation means you have to have a way of describing the logical steps you want your home to implement automatically.

      Whilst I've always been a fan of the Lua language, as used in Vera (and openLuup) for scenes and plugins, it's perhaps not ideal. For this reason, there has been a long development history of plugins with their own "language" to help define the automation logic: PLEG (for those with a long memory), AltUI workflows, Rules Engine, Reactor, MSR, ...

      It's always seemed to me that the 'best' way of describing logic would be a language designed for that purpose – a "logic programming language". Perhaps one of the most famous, and venerable, is Prolog, which had its fiftieth birthday last year in 2022.

      Thanks to some relatively recent research A Hitchhiker’s Guide to Reinventing a Prolog Machine, Paul Tarau (2017) it's become possible to implement a very efficient Prolog engine in a reasonably concise way. So, just for fun, I'm developing a CGI plugin for describing openLuup actions in Prolog.

      I have an early prototype running (written in Lua, of course). It presents a web page which looks like a fairly typical Interactive Development Environment (IDE) and contains some primitives which allow basic access to the Luup engine.

      Screenshot 2023-03-10 at 18.27.33.png

      In a subsequent post, I'll give a glimpse of its capabilities...

      Vera/openLuup plugins

    • MQTT Controller and extended capabilities

      M

      I'm a little bit confused how to configure extended capabilities for the entities in the MQTTController.

      mqtt_cababilities.yaml states that: "...You can add your own capabilities by adding a "capabilities" section to your own local_mqtt_capabilities.yaml file in your config directory."

      So I did this in my local_mqtt_capabilities.yaml in the config directory:

      version: 22353 revision: 1 format: 1 capabilities: x_my_config: attributes: partyMode: type: bool actions: some_action: topic: '%topic/write' payload: "some value"

      And in my reactor.yaml I have following configuration entry:

      my-config: name: 'My custom configuration' topic: 'my-config' query: "%topic%/read" init: "%topic%/read" capabilities: - x_my_config primary_attribute: x_my_config.partyMode events: "%topic%/status": "x_my_config.partyMode": json_payload: true expr: "payload.partyMode"

      This sort of works but not quite. The partyMode attribute gets updated when messages arrive for that specific topic, so that's fine. But I don't see x_my_config capability in the Capabilities list in the UI and also the some_action is missing.

      Screenshot from 2023-03-09 19-42-49.png

      Addition to that the primary value is not set and I'm getting the following error:
      Screenshot from 2023-03-09 19-30-42.png

      Have I completely misunderstood the idea behind the capability extension and the attributes? If so, could someone point me to the right direction with few explanatory example configs.

      What I'm trying to achieve is a set of configuration options that could be updated thru the MQTT, and also provide some actions that the rules could invoke.

      Reactor (Multi-hub) latest-23063-c464b685 + MQTTController [0.1.23010]

      br,
      mgvra

      Multi-System Reactor

    • localization settings

      tunnus

      Using the following localization settings in reactor.yaml:

      units: metric locale: fi-FI time_format: "%H:%M:%S" date_format: "%d/%m/%Y"

      But still I'm getting US date & time formatting, so settings do not seem to override defaults? Using 23049 on Synology Docker

      Multi-System Reactor

    • Separate switching bulb in one ceiling light

      P

      Hello guys,

      I would like to achieve two different things with lights, but I am not sure it could be done. I am starting with smart things, and I am far from any electrician knowledge, wo any help is really appreciated.

      I have dumb switches in my hall, controlled from 3 places. I understood that installing one smart module before first switch will make them "hybrid", both smart controlled and dumb controlled.

      I would like to buy ceiling light with two bulb sockets. What I would like to achieve is I would like to have one bulb for normal daily usage (lets say cold white full brightness), and second for night time (aprox from 10pm till morning) with some red/orange - minimum brightness.

      So question are:

      Is there a way to keep both bulbs turning-on separated? So only one will be on during day, and then only second during night?

      And could that be done with pressing dumb switch? What would I need to achieve it? (maybe another module into the ceiling lights)

      Thank you in advance

      General Discussion

    • Installing MQTTController on Home Assistant Core when Reactor is installed as an Add-In (VirtualBox)

      W

      Running Home Assistant Core under VirtualBox (on Windows) and Reactor is installed and working fine as an add-in. What I can't figure out is how to install MQTTController in this situation. I can upload the files and unzip them, but I can't run install.sh in a terminal window because npm is not a part of the Core installation.

      It does appear that somewhere in the stack there is a version of docker there between VirtualBox and HA, (I see some references go by in the VirtualBox startup log) but it appears minimal and will not execute the install via the docker technique in your documentation from the VB console.

      Is there a way to do this?

      Thanks.

      Multi-System Reactor

    • Home Assistant add-on

      M

      I've done a bit of repackaging of MSR to make it work as an add-on under Home Assistant mostly for my own purposes but hopefully it makes it a bit easier to install and get going.

      GitHub - mrw298/hassio-reactor-addon GitHub - mrw298/hassio-reactor-addon

      Contribute to mrw298/hassio-reactor-addon development by creating an account on GitHub.

      Multi-System Reactor

    • When turning off the dimmer, set the LoadLevelLast to 100%

      E

      I have the following issue: In my Vera, I have created a dimmer using the Switchboard plugin. I want this light always turn on at 100% brightness when turn the light on. By default, the dimmer remembers its last used setting. I have created the following scene: when the light is turned off, the LoadLevelLast should be 100.

      9937e326-2453-43bd-bd32-917803b38e90-image.png

      Manually, this works through the test Luup code (Lua), but not through the scene's action by execute the following Luup code.

      I also tried in MSR, but no result

      Does anyone know the solution to this?

      Vera/openLuup plugins

    • Console view: - No Live refreshes via :3480/console?page=devices

      parkerc

      Hi @akbooer

      Just bringing this over as suggested..

      I’ve started to use the console view a lot more, mainly for it’s look and simplicity , but I noticed it does not do any live updates compared to ALTUI, you have to do a full browser reload. Is that by design, or is mine not working?

      Also if I want to go strait to the console view, rather than into ALTUI, I recall seeing something abut altering that in the guide by for the life of me I can’t find it. Is it possible to do, if so how would I do that..

      You suggested this was something you were looking at ? Also you said You don't need a "full browser reload", just click on the display menu item to refresh the screen. - what do you mean by `display menu?

      openLuup

    • Does order matter in Reactions Set/Reset

      G

      @toggledbits somewhere I thought I read that MSR goes thru the items in set reaction and reset reaction in stack order, ie from top to bottom/first to last.

      Am I mistaken?

      Multi-System Reactor

    • Reactor: How to call Hass service for noob

      W

      Reactor 23063 running on Windows Bare Metal.
      Home assistant 2023.3.1
      ESPHome 2023.2.4

      I've been trying a few ways using some results from search to call a Hass service as a reaction in a Reactor rule.

      Specifically, when the PIR in the room senses motion, wake the NsPanel screen.

      My Reactions otherwise so far are basic If this then that so I'm way behind what others are doing.

      What I want to call as a Reaction:
      Capture1.PNG

      What I've tried (a few variations on):
      Capture2.PNG

      What happens:

      [latest-23063]2023-03-07T07:45:21.688Z <wsapi:ERR> wsapi: error thrown handling client message [Object]{ "command": "perform", "entity": "WOKHASS1>system", "action": "x_hass_system.call_service", "parameters": { "service": "ESPHome: nspensuite_send_command_printf", "data": "page home" }, "qid": 75 } [latest-23063]2023-03-07T07:45:21.688Z <wsapi:CRIT> TypeError: Cannot read properties of null (reading '1') [-] TypeError: Cannot read properties of null (reading '1') at HassController.performOnEntity (C:\reactor\reactor\server\lib\HassController.js:584:108) at System.perform (C:\reactor\reactor\server\lib\Entity.js:707:56) at WSAPI.clientMessage (C:\reactor\reactor\server\wsapi\wsapi.js:499:48) at WebSocket.<anonymous> (C:\reactor\reactor\server\wsapi\wsapi.js:290:158) at WebSocket.emit (node:events:520:28) at WebSocket.emit (node:domain:475:12) at Receiver.receiverOnMessage (C:\reactor\reactor\node_modules\ws\lib\websocket.js:1059:20) at Receiver.emit (node:events:520:28) at Receiver.emit (node:domain:475:12) at Receiver.dataMessage (C:\reactor\reactor\node_modules\ws\lib\receiver.js:517:14)

      If someone can convert the 'call service' to a 'reaction' for me, or share their own similar thing I think that's what I need to achieve this goal.

      I suspect if I'm even close to being on the right track, my problems are probably formatting like curly braces etc and lack thereof.

      Thanks in advance.

      Multi-System Reactor

    • Razberry firmware upgrade from 5.04 to 5.27

      S

      I have a Razberry v2 with firmware v5.04, and Bootloader v8aaa with CRC 35498 (I did manage to upgrade to this version using the "ZMESerialUpdater" tool ). I want to upgrade the firmware to v5.27, which Z-Wave.me Support say is the newest version that my hardware can handle without bricking it. Firmware v5.27 introduces the Analytics tab, according to Poltos, which is what I want.

      I have been studying the firmware map (https://service.z-wave.me/expertui/uzb-stats/versions-graph.html?with_hidden) which I sort-of understand. I have also got the "ZMESerialUpdater" tool to do the update, and could use it if I knew which binaries to use.

      My question is, what firmware update route do I use to get from v5.04 to v5.27? What exactly are the URLs of the binaries (as in "UPD_FIRMWARE_Razberry500_from_05_04_to_05_07.bin")?

      Somewhat confused!

      ScotsDon

      Z-Wave.me

    • Netatmo – Oath2 login

      akbooer

      Just seen notification to Netatmo developers that the current password-based login is being disabled as from October.

      Oath2 is now a requirement for apps needing access to Netatmo. This will require some changes to my venerable plug-in. I’m not sure how easy this will be with the current libraries in use.

      Does anyone out there use the Netatmo plug-in?

      Does anyone have any advice on using Oath2?

      Vera/openLuup plugins

    • Reactor Ex Machina

      G

      @toggledbits was looking thru rule sets and updating which (new) lights I wanted REMII to impact and saw that this...

      4711b0df-5e98-4992-bb25-d0e53203f0e8-image.png

      ...is showing as (missing) in the rule Deactivatedand looking in the dropdown of Variables it appears I cannot select that local expression (only Global) as I did when originally building this out back in 2021.

      27f7025c-057e-441a-88ea-dc4bdf39614d-image.png

      In looking at the rule Active Period I'm seeing:
      487074ef-3bfa-4a84-b03d-ed6d920c118c-image.png which appears to be pointing to setting a variable in a rule?

      It's admittedly been a couple years since this was built and it's def not fresh in my memory.

      Multi-System Reactor

    • No drop-down list on Entity Attribute in "Creation Rule Sets" interface

      C

      New installation of Reactor version 23063-c464b685 on a Raspberry PI4 with Portainer/Docker.
      Report :
      No drop-down list on Entity Attribute in "Creation Rule Sets" interface
      I can however visualize the entities.
      I have configured HomeAssistant and all entities are coming up fine.
      I have an unsupported Hass version 2023.3.0b5.
      I'm new to Docker and can someone guide me to a solution?
      Christian FABRE

      Alert:
      reactor_20230305_01.png Rule :
      reactor_20230305_02.png Entities:
      reactor_20230305_03.png log Reactor :

      [latest-23063]2023-03-05T09:51:49.575Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/arm64 #1595 SMP PREEMPT Wed Oct 26 11:07:24 BST 2022; locale (undefined) [latest-23063]2023-03-05T09:51:49.576Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-23063]2023-03-05T09:51:49.577Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-23063]2023-03-05T09:51:49.584Z <app:INFO> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-23063]2023-03-05T09:51:49.708Z <app:INFO> Loaded locale en-US for en-US [latest-23063]2023-03-05T09:51:49.725Z <Structure:null> Module Structure v22323 [latest-23063]2023-03-05T09:51:49.729Z <Capabilities:null> Module Capabilities v22356 [latest-23063]2023-03-05T09:51:49.806Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 23058 revision 1 [latest-23063]2023-03-05T09:51:49.849Z <Plugin:null> Module Plugin v22300 [latest-23063]2023-03-05T09:51:49.869Z <TimerBroker:null> Module TimerBroker v22283 [latest-23063]2023-03-05T09:51:49.878Z <Entity:null> Module Entity v22353 [latest-23063]2023-03-05T09:51:49.889Z <Controller:null> Module Controller v23044 [latest-23063]2023-03-05T09:51:49.926Z <default:null> Module Ruleset v22293 [latest-23063]2023-03-05T09:51:49.928Z <default:null> Module Rulesets v22146 [latest-23063]2023-03-05T09:51:49.943Z <GlobalExpression:null> Module GlobalExpression v22146 [latest-23063]2023-03-05T09:51:49.977Z <Predicate:null> Module Predicate v22345 [latest-23063]2023-03-05T09:51:49.987Z <AlertManager:null> Module AlertManager v22283 [latest-23063]2023-03-05T09:51:49.995Z <Rule:null> Module Rule v22345 [latest-23063]2023-03-05T09:51:50.004Z <GlobalReaction:null> Module GlobalReaction v22324 [latest-23063]2023-03-05T09:51:50.008Z <Engine:null> Module Engine v23001 [latest-23063]2023-03-05T09:51:50.019Z <httpapi:null> Module httpapi v23058 [latest-23063]2023-03-05T09:51:50.078Z <wsapi:null> Module wsapi v23053 [latest-23063]2023-03-05T09:51:50.080Z <app:NOTICE> Starting Structure... [latest-23063]2023-03-05T09:51:50.100Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping [latest-23063]2023-03-05T09:51:50.106Z <Structure:INFO> Structure#1 loading controller interface hass (HassController) [latest-23063]2023-03-05T09:51:50.210Z <HassController:null> Module HassController v23060 [latest-23063]2023-03-05T09:51:50.639Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-23063]2023-03-05T09:51:50.649Z <DynamicGroupController:null> Module DynamicGroupController v22313 [latest-23063]2023-03-05T09:51:50.659Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-23063]2023-03-05T09:51:50.672Z <SystemController:null> Module SystemController v22306 [latest-23063]2023-03-05T09:51:50.680Z <Structure:INFO> Starting controller HassController#hass [latest-23063]2023-03-05T09:51:50.682Z <HassController:NOTICE> HassController#hass starting... [latest-23063]2023-03-05T09:51:50.691Z <Controller:INFO> HassController#hass loaded hass capabilities ver 22312 rev 2 format 1 [latest-23063]2023-03-05T09:51:50.715Z <Controller:INFO> HassController#hass loaded implementation data ver 23058 rev 1 format 1 [latest-23063]2023-03-05T09:51:50.715Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-23063]2023-03-05T09:51:50.728Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online. [latest-23063]2023-03-05T09:51:50.728Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-23063]2023-03-05T09:51:50.733Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. [latest-23063]2023-03-05T09:51:50.877Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [latest-23063]2023-03-05T09:51:50.881Z <HassController:WARN> HassController: implementation of capability input_select.selector does not provide attribute values [latest-23063]2023-03-05T09:51:50.884Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.31:8123/api/websocket [latest-23063]2023-03-05T09:51:50.894Z <app:NOTICE> Starting HTTP server and API... [latest-23063]2023-03-05T09:51:50.901Z <httpapi:NOTICE> httpapi: starting HTTP service on port "8111" [latest-23063]2023-03-05T09:51:50.909Z <app:NOTICE> Starting Reaction Engine... [latest-23063]2023-03-05T09:51:50.910Z <Engine:INFO> Reaction Engine starting [latest-23063]2023-03-05T09:51:50.911Z <Engine:INFO> Checking rule sets... [latest-23063]2023-03-05T09:51:50.916Z <Engine:INFO> Checking rules... [latest-23063]2023-03-05T09:51:50.923Z <Engine:INFO> Data check complete; no corrections. [latest-23063]2023-03-05T09:51:50.938Z <Rule:NOTICE> rule-leu8xfe4 (rule-leu8xfe4 in First Rule Set) starting [latest-23063]2023-03-05T09:51:50.939Z <Engine:NOTICE> Reaction Engine running! [latest-23063]2023-03-05T09:51:50.939Z <Rule:NOTICE> rule-leu8xfe4 (rule-leu8xfe4 in First Rule Set) can't start -- rule is disabled [latest-23063]2023-03-05T09:51:50.952Z <httpapi:NOTICE> httpapi: listening [latest-23063]2023-03-05T09:51:50.981Z <app:NOTICE> Starting WSAPI... [latest-23063]2023-03-05T09:51:50.983Z <wsapi:NOTICE> wsapi: starting version 23053 [latest-23063]2023-03-05T09:51:51.080Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "3/5/2023 10:51:51 AM" (TZ offset 60 mins from UTC) [latest-23063]2023-03-05T09:51:51.119Z <HassController:NOTICE> HassController#hass connected, starting protocol [latest-23063]2023-03-05T09:51:51.127Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.1.42: GET /api/v1/systime [latest-23063]2023-03-05T09:51:51.145Z <HassController:INFO> HassController#hass successful authentication with ws://192.168.1.31:8123; fetching initial data... [latest-23063]2023-03-05T09:51:51.155Z <HassController:INFO> HassController#hass Hass reports version "2023.3.0b5" location Maison timezone Europe/Paris state RUNNING safe_mode false [latest-23063]2023-03-05T09:51:51.245Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_supervisor_update [latest-23063]2023-03-05T09:51:51.248Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_core_update [latest-23063]2023-03-05T09:51:51.249Z <HassController:NOTICE> HassController#hass no signature match for update.terminal_ssh_update [latest-23063]2023-03-05T09:51:51.250Z <HassController:NOTICE> HassController#hass no signature match for update.file_editor_update [latest-23063]2023-03-05T09:51:51.251Z <HassController:NOTICE> HassController#hass no signature match for update.samba_backup_update [latest-23063]2023-03-05T09:51:51.252Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_operating_system_update [latest-23063]2023-03-05T09:51:51.253Z <HassController:NOTICE> HassController#hass no signature match for sun.sun [latest-23063]2023-03-05T09:51:51.285Z <HassController:NOTICE> HassController#hass no signature match for calendar.calendrier [latest-23063]2023-03-05T09:51:51.413Z <HassController:NOTICE> HassController#hass no signature match for siren.piscine_siren [latest-23063]2023-03-05T09:51:51.419Z <HassController:NOTICE> HassController#hass no signature match for camera.portillon [latest-23063]2023-03-05T09:51:51.607Z <Controller:INFO> HassController#hass 0 dead entities older than 86400000s purged [latest-23063]2023-03-05T09:51:51.633Z <Controller:NOTICE> Controller HassController#hass is now online. [latest-23063]2023-03-05T09:51:51.634Z <DynamicGroupController:INFO> All controllers ready, setting up dynamic groups [latest-23063]2023-03-05T09:51:51.726Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.1.42 [latest-23063]2023-03-05T09:51:55.510Z <wsapi:INFO> client "192.168.1.42#1" closed, code=1001, reason= [latest-23063]2023-03-05T09:51:55.815Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.1.42: GET /api/v1/lang [latest-23063]2023-03-05T09:51:55.843Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.1.42 [latest-23063]2023-03-05T09:51:56.849Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.1.42: GET /api/v1/systime [latest-23063]2023-03-05T09:52:07.392Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.1.42: GET /api/v1/systime---

      Log Portainer:

      NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-23063]2023-03-05T08:55:17.734Z <app:null> Reactor build latest-23063-c464b685 starting on v16.15.1 [latest-23063]2023-03-05T08:55:17.736Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/arm64 #1595 SMP PREEMPT Wed Oct 26 11:07:24 BST 2022; locale (undefined) [latest-23063]2023-03-05T08:55:17.737Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-23063]2023-03-05T08:55:17.738Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-23063]2023-03-05T08:55:17.875Z <Structure:null> Module Structure v22323 [latest-23063]2023-03-05T08:55:17.879Z <Capabilities:null> Module Capabilities v22356 [latest-23063]2023-03-05T08:55:18.004Z <Plugin:null> Module Plugin v22300 [latest-23063]2023-03-05T08:55:18.023Z <TimerBroker:null> Module TimerBroker v22283 [latest-23063]2023-03-05T08:55:18.032Z <Entity:null> Module Entity v22353 [latest-23063]2023-03-05T08:55:18.042Z <Controller:null> Module Controller v23044 [latest-23063]2023-03-05T08:55:18.079Z <default:null> Module Ruleset v22293 [latest-23063]2023-03-05T08:55:18.080Z <default:null> Module Rulesets v22146 [latest-23063]2023-03-05T08:55:18.096Z <GlobalExpression:null> Module GlobalExpression v22146 [latest-23063]2023-03-05T08:55:18.129Z <Predicate:null> Module Predicate v22345 [latest-23063]2023-03-05T08:55:18.139Z <AlertManager:null> Module AlertManager v22283 [latest-23063]2023-03-05T08:55:18.146Z <Rule:null> Module Rule v22345 [latest-23063]2023-03-05T08:55:18.156Z <GlobalReaction:null> Module GlobalReaction v22324 [latest-23063]2023-03-05T08:55:18.159Z <Engine:null> Module Engine v23001 [latest-23063]2023-03-05T08:55:18.171Z <httpapi:null> Module httpapi v23058 [latest-23063]2023-03-05T08:55:18.232Z <wsapi:null> Module wsapi v23053 [latest-23063]2023-03-05T08:55:18.358Z <HassController:null> Module HassController v23060 [latest-23063]2023-03-05T08:55:18.780Z <DynamicGroupController:null> Module DynamicGroupController v22313 [latest-23063]2023-03-05T08:55:18.803Z <SystemController:null> Module SystemController v22306```
      Multi-System Reactor

    • chine version of homeypro to convert 433 to IR,wifi,Bluetooth,866,..?/

      C

      hello

      i am searching for a universal hub that takes my 433 remotes signals and repeats them 433mhz or converts them into bluetooth, wifi, IR, z-wave etc…basically into all the other signals. so my 433mhz remote becomes a universal remote.

      it should have an app to configurate, maybe a learning function as well

      i belive the homey pro can do that but it costs like 400$ …right?

      so is there a cheap “china” product that works like that for at least 433 into IR, bluetooth, wifi

      there are so many chinaproducts and i cant figure out which can do which trick !/ this for example https://de.trck.one/redir/clickGate.php?u=Ha2Rd3xX&m=1&p=9yUI69TI8b&t=kLf5673Z&st=&s=&url=https%3A%2F%2Fwww.techpunt.nl%2Fde%2Fhomey-bridge.html%3Fgclid%3DCj0KCQiA9YugBhCZARIsAACXxeJvViv59ieDen9zOXTP1jhc_OisKQxPlCZOJsPGX20nWo7UROROuJcaAix5EALw_wcB&r=https%3A%2F%2Fwww.hardwareluxx.de%2Fcommunity%2Fthreads%2Fbillige-chinaversion-von-homey-pro-gesucht.1333803%2F

      i am working with 433mhz intertechno protokoll remotes .

      please help

      thanks, christoph

      Hardware
    For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used
    T
    • Profile
    • Following 0
    • Followers 0
    • Topics 9
    • Posts 41
    • Best 7
    • Controversial 0
    • Groups 0

    tbully

    @tbully

    12
    Reputation
    12
    Profile views
    41
    Posts
    0
    Followers
    0
    Following
    Joined Last Online
    tbully Unfollow Follow

    Best posts made by tbully

    • RE: Schlage Lock - Alert when PIN Entered

      Latest build gets rid of the extra notifications on reload. Thanks for doing this instead of me having to figure out another hack. It's a shame we have to do any of this but I suppose we've beat that horse to death over the years.

      Update on my weird variable issue: I was noting that the sl_User_code (and even the sl_User_code_updated) variables were only sporadically updating. After a lot of head-scratching, I noted that the servo was moving a little slow even though the batteries were showing 66%. I decided to replace them just in case. I noted much faster servo response but, more importantly, the variable writes stabilized. Very strange but I'm happy it's better.

      Many thanks, @toggledbits , for your workarounds and your forum advice. My system has been mostly stable for a few years so I'm a little rusty.

      posted in Multi-System Reactor
      T
      tbully
    • RE: Reactor Start - System Crash/Restart

      In my exhaustion (anger? Lol), I mistyped. I’m at 22.04. 🙂

      I do fire an email just before the reboot. I took a break to check emails and wrap up for the day and this is what triggered it for me. If it wasn’t for this, I think I’d still be digging. I send lots of emails, perhaps too many, when different things happen. This is a great idea!

      I have to go look at the rule today. I thought I set a variable on reboot which would only allow one event/reboot. At least I thought about this possibility but I clearly missed something.

      Thanks for the consoling, gents. I’ve appreciated both of your support over the past year as I’ve slowly moved away from Vera to HASS with Reactor being the central rules engine.

      posted in Multi-System Reactor
      T
      tbully
    • RE: MSR No longer Setting Reactions

      Thank you. For some reason I was thinking/reading that the 1.0 branch was the latest. I updated as you suggested which fixed my issue. Much appreciated.

      posted in Multi-System Reactor
      T
      tbully
    • RE: Schlage Lock - Alert when PIN Entered

      @toggledbits Understood.

      I'll test more when I get free from work. So far I'm seeing inconsistent variable updates but nice to see it worked for @MikeReadington .

      One thing I've noticed is that when Vera reloads (which, let's face it, happens often), the last PIN triggers because the sl_User_code_updated gets updated to the reload epoch time.

      Wondering of ways around this. I think one way could be to use a local expression that gets the current time (in epoch) and add a reasonable buffer (few minutes)? I'm not familiar with expressions but maybe something like that?

      Something easier?

      posted in Multi-System Reactor
      T
      tbully
    • RE: Vera -> HASS Migration Strategy (question)

      @toggledbits read through the noise and got it. I'm depending on Vera (and their app) to manually execute certain scenes (which I think should be converted MSR Reactions or Rules) until I can fully get off the platform. I'm also trying to figure out how to do the same from a Hass dashboard. I agree that I'm sure it's possible. I just need to dig a little more.

      The virtual switch idea is interesting. Basically using them as a variable. But I think a direct call from the Vera scene may work. I'll look in to the wget function.

      Thanks for the feedback, both.

      posted in Multi-System Reactor
      T
      tbully
    • RE: Home Assistant Service Call - JSON/Formatting Question

      @Pabla - Thanks again for your help. This was finally the answer (for anyone searching later)....

      {
    "recirculation_minutes" : 5,
    "entity_id": "water_heater.bully_house_water_heater"
}
      posted in Multi-System Reactor
      T
      tbully
    • RE: Where Used Functionality?

      I have the rules migrated and running on the external Reactor (doing some tweaking as you mentioned). That's not my issue.

      My issue is I'm now starting to exclude some devices from Vera and adding them to HASS. For the most part, I've been successful in knowing where the device is used in my ruleset. However, on a few occasions, I've forgotten / missed some rules.

      It would be great to look up an entity in MSR and see where it's used (either in rules or reactions) so I can account for the myriad places some devices exist.

      posted in Multi-System Reactor
      T
      tbully

    Latest posts made by tbully

    • RE: Reactor Start - System Crash/Restart

      In my exhaustion (anger? Lol), I mistyped. I’m at 22.04. 🙂

      I do fire an email just before the reboot. I took a break to check emails and wrap up for the day and this is what triggered it for me. If it wasn’t for this, I think I’d still be digging. I send lots of emails, perhaps too many, when different things happen. This is a great idea!

      I have to go look at the rule today. I thought I set a variable on reboot which would only allow one event/reboot. At least I thought about this possibility but I clearly missed something.

      Thanks for the consoling, gents. I’ve appreciated both of your support over the past year as I’ve slowly moved away from Vera to HASS with Reactor being the central rules engine.

      posted in Multi-System Reactor
      T
      tbully
    • RE: Reactor Start - System Crash/Restart

      I could delete these posts but I won't. In short, I'm an idiot.

      I remembered I have a rule which reboots my Linux host when my weather station goes in to error. Reactor lives on that host. (sigh)

      My fix was to temporarily rename the "reboot" command in the filesystem to something else. Start Reactor (imagine that, no reboot!). Disable the rule. Fix the command back to "reboot" in the FS.

      Happy New Year! (ugh)

      posted in Multi-System Reactor
      T
      tbully
    • RE: Reactor Start - System Crash/Restart

      Sorry for talking to myself. Just trying to relay what I know.

      I tried running it manually and got the following:

      tbully@homeauto03:~/reactor$ npm run deps
npm ERR! Missing script: "deps"
npm ERR!
npm ERR! To see a list of scripts, run:
npm ERR!   npm run

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/tbully/.npm/_logs/2022-12-31T01_15_30_113Z-debug-0.log
tbully@homeauto03:~/reactor$ NODE_PATH=$(pwd) node app.js
Reactor stable-22337-1a0a685f app 22328 configuration from /home/tbully/reactor/config
NODE_PATH /home/tbully/reactor
[stable-22337]2022-12-31T01:15:55.631Z <app:null> Reactor build stable-22337-1a0a685f starting on v17.9.0
[stable-22337]2022-12-31T01:15:55.632Z <app:null> Process ID 2239 user/group 1000/1000; bare-metal; platform linux/x64 #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022; locale en_CA.UTF-8
[stable-22337]2022-12-31T01:15:55.633Z <app:null> Basedir /home/tbully/reactor; data in /home/tbully/reactor/storage
[stable-22337]2022-12-31T01:15:55.633Z <app:null> NODE_PATH=/home/tbully/reactor
[stable-22337]2022-12-31T01:15:55.651Z <Structure:null> Module Structure v22323
[stable-22337]2022-12-31T01:15:55.652Z <Capabilities:null> Module Capabilities v22283
[stable-22337]2022-12-31T01:15:55.709Z <Plugin:null> Module Plugin v22300
[stable-22337]2022-12-31T01:15:55.716Z <TimerBroker:null> Module TimerBroker v22283
[stable-22337]2022-12-31T01:15:55.720Z <Entity:null> Module Entity v22314
[stable-22337]2022-12-31T01:15:55.724Z <Controller:null> Module Controller v22323
[stable-22337]2022-12-31T01:15:55.734Z <default:null> Module Ruleset v22293
[stable-22337]2022-12-31T01:15:55.735Z <default:null> Module Rulesets v21096
[stable-22337]2022-12-31T01:15:55.743Z <GlobalExpression:null> Module GlobalExpression v21333
[stable-22337]2022-12-31T01:15:55.753Z <Predicate:null> Module Predicate v22305
[stable-22337]2022-12-31T01:15:55.757Z <AlertManager:null> Module AlertManager v22283
[stable-22337]2022-12-31T01:15:55.759Z <Rule:null> Module Rule v22335
[stable-22337]2022-12-31T01:15:55.763Z <GlobalReaction:null> Module GlobalReaction v22320
[stable-22337]2022-12-31T01:15:55.765Z <Engine:null> Module Engine v22320
[stable-22337]2022-12-31T01:15:55.769Z <httpapi:null> Module httpapi v22337
[stable-22337]2022-12-31T01:15:55.783Z <wsapi:null> Module wsapi v22320
[stable-22337]2022-12-31T01:15:55.845Z <TaskQueue:null> Module TaskQueue 21351
[stable-22337]2022-12-31T01:15:55.846Z <VeraController:null> Module VeraController v22325
[stable-22337]2022-12-31T01:15:56.133Z <HassController:null> Module HassController v22334
[stable-22337]2022-12-31T01:15:57.494Z <SystemController:null> Module SystemController v22306
      posted in Multi-System Reactor
      T
      tbully
    • RE: Reactor Start - System Crash/Restart

      I have the logs but can't find a way to upload them. I don't have permissions to upload a file and if I paste it in here it says the post is too large.

      Here's a few pieces:

      [stable-22337]2022-12-31T00:33:46.745Z <app:null> Reactor build stable-22337-1a0a685f starting on v17.9.0
[stable-22337]2022-12-31T00:33:46.746Z <app:null> Process ID 7240 user/group 1000/1000; bare-metal; platform linux/x64 #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022; locale en_CA.UTF-8
[stable-22337]2022-12-31T00:33:46.746Z <app:null> Basedir /home/tbully/reactor; data in /home/tbully/reactor/storage
[stable-22337]2022-12-31T00:33:46.747Z <app:null> NODE_PATH=/home/tbully/reactor
[stable-22337]2022-12-31T00:33:46.750Z <app:INFO> Configured locale (undefined); selected locale(s) en_CA.UTF-8
[stable-22337]2022-12-31T00:33:46.761Z <app:INFO> Loaded locale en-US
[stable-22337]2022-12-31T00:33:46.764Z <Structure:null> Module Structure v22323
[stable-22337]2022-12-31T00:33:46.765Z <Capabilities:null> Module Capabilities v22283
[stable-22337]2022-12-31T00:33:46.819Z <Plugin:null> Module Plugin v22300
[stable-22337]2022-12-31T00:33:46.827Z <TimerBroker:null> Module TimerBroker v22283
[stable-22337]2022-12-31T00:33:46.831Z <Entity:null> Module Entity v22314
[stable-22337]2022-12-31T00:33:46.835Z <Controller:null> Module Controller v22323
[stable-22337]2022-12-31T00:33:46.847Z <default:null> Module Ruleset v22293
[stable-22337]2022-12-31T00:33:46.848Z <default:null> Module Rulesets v21096
[stable-22337]2022-12-31T00:33:46.854Z <GlobalExpression:null> Module GlobalExpression v21333
[stable-22337]2022-12-31T00:33:46.864Z <Predicate:null> Module Predicate v22305
[stable-22337]2022-12-31T00:33:46.867Z <AlertManager:null> Module AlertManager v22283
[stable-22337]2022-12-31T00:33:46.869Z <Rule:null> Module Rule v22335
[stable-22337]2022-12-31T00:33:46.872Z <GlobalReaction:null> Module GlobalReaction v22320
[stable-22337]2022-12-31T00:33:46.873Z <Engine:null> Module Engine v22320
[stable-22337]2022-12-31T00:33:46.877Z <httpapi:null> Module httpapi v22337
[stable-22337]2022-12-31T00:33:46.886Z <wsapi:null> Module wsapi v22320
[stable-22337]2022-12-31T00:33:46.887Z <app:NOTICE> Starting Structure...
[stable-22337]2022-12-31T00:33:46.890Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping
[stable-22337]2022-12-31T00:33:46.892Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController)
[stable-22337]2022-12-31T00:33:46.949Z <TaskQueue:null> Module TaskQueue 21351
[stable-22337]2022-12-31T00:33:46.950Z <VeraController:null> Module VeraController v22325
[stable-22337]2022-12-31T00:33:47.193Z <Structure:INFO> Structure#1 loading controller interface hass (HassController)
[stable-22337]2022-12-31T00:33:47.200Z <HassController:null> Module HassController v22334
[stable-22337]2022-12-31T00:33:48.290Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController)
[stable-22337]2022-12-31T00:33:48.294Z <SystemController:null> Module SystemController v22306
[stable-22337]2022-12-31T00:33:48.297Z <Structure:INFO> Starting controller VeraController#vera
[stable-22337]2022-12-31T00:33:48.298Z <VeraController:NOTICE> VeraController#vera starting...
[stable-22337]2022-12-31T00:33:48.304Z <Controller:INFO> VeraController#vera loaded vera capabilities ver 22253 rev 1 format 1 
[stable-22337]2022-12-31T00:33:48.341Z <Controller:INFO> VeraController#vera loaded implementation data ver 22280 rev 8 format 1 
[stable-22337]2022-12-31T00:33:48.341Z <Structure:INFO> Starting controller HassController#hass
[stable-22337]2022-12-31T00:33:48.341Z <HassController:NOTICE> HassController#hass starting...
[stable-22337]2022-12-31T00:33:48.343Z <Controller:INFO> HassController#hass loaded hass capabilities ver 22312 rev 2 format 1 
[stable-22337]2022-12-31T00:33:48.354Z <Controller:INFO> HassController#hass loaded implementation data ver 22335 rev 1 format 1 
[stable-22337]2022-12-31T00:33:48.354Z <Structure:INFO> Starting controller SystemController#reactor_system
[stable-22337]2022-12-31T00:33:48.359Z <Controller:NOTICE> Controller SystemController#reactor_system is now online.
[stable-22337]2022-12-31T00:33:48.518Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members
[stable-22337]2022-12-31T00:33:48.518Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty
[stable-22337]2022-12-31T00:33:48.519Z <HassController:INFO> HassController#hass device mapping data loaded; checking...
[stable-22337]2022-12-31T00:33:48.520Z <VeraController:NOTICE> VeraController#vera updating capabilities for system entity System#vera>system
[stable-22337]2022-12-31T00:33:48.525Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.34.17:8123/api/websocket
[stable-22337]2022-12-31T00:33:48.529Z <app:NOTICE> Starting HTTP server and API...
[stable-22337]2022-12-31T00:33:48.530Z <httpapi:NOTICE> Starting HTTP API v1 22337 on http://192.168.34.:8111
[stable-22337]2022-12-31T00:33:48.533Z <app:NOTICE> Starting Reaction Engine...
[stable-22337]2022-12-31T00:33:48.534Z <Engine:INFO> Reaction Engine starting
[stable-22337]2022-12-31T00:33:48.534Z <Engine:INFO> Checking rule sets...
[stable-22337]2022-12-31T00:33:48.539Z <Engine:INFO> Checking rules...```

      [stable-22337]2022-12-31T00:33:49.745Z Rule:INFO Master Closet Motion Battery Low (rule-grp17k28ehz in Battery Checks) started
      [stable-22337]2022-12-31T00:33:49.761Z Rule:ERR Rule#rule-grp17k28qlp trigger evaluation failed: [ReferenceError] Can't find entity "vera>device_368" [-]
      [stable-22337]2022-12-31T00:33:49.762Z Rule:CRIT ReferenceError: Can't find entity "vera>device_368" [-]
      ReferenceError: Can't find entity "vera>device_368"
      at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:366:27)
      at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106)
      at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47)
      at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37)
      at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54)
      at async /home/tbully/reactor/server/lib/Rule.js:830:17
      [stable-22337]2022-12-31T00:33:49.762Z Rule:INFO Panic Button Battery Low (rule-grp17k28qlp in Battery Checks) evaluated; trigger state changed ((null)), but rule state remains NULL
      [stable-22337]2022-12-31T00:33:49.762Z Rule:INFO Panic Button Battery Low (rule-grp17k28qlp in Battery Checks) started
      [stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Office Motion Battery Low (rule-grp17k28znh in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
      [stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Office Motion Battery Low (rule-grp17k28znh in Battery Checks) started
      [stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Door Battery Low (rule-grp17k29vsx in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
      [stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Door Battery Low (rule-grp17k29vsx in Battery Checks) started
      [stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Motion Battery Low (rule-grp17k2abok in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
      [stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Motion Battery Low (rule-grp17k2abok in Battery Checks) started
      [stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Flood Battery Low (rule-grp17k2am7t in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
      [stable-22337]2022-12-31T00:33:49.764Z Rule:INFO Upstairs Bath Flood Battery Low (rule-grp17k2am7t in Battery Checks) started
      [stable-22337]2022-12-31T00:33:49.764Z Rule:INFO Upstairs Hall Motion Battery Low (rule-grp17k2b0ha in Battery Checks) evaluated; trigger state unchanged (true); rule state remains SET
      [stable-22337]2022-12-31T00:33:49.764Z Rule:INFO Upstairs Hall Motion Battery Low (rule-grp17k2b0ha in Battery Checks) started
      [stable-22337]2022-12-31T00:33:49.773Z Rule:ERR Rule#rule-grp17k2iotv trigger evaluation failed: [ReferenceError] Can't find entity "vera>device_543" [-]
      [stable-22337]2022-12-31T00:33:49.773Z Rule:CRIT ReferenceError: Can't find entity "vera>device_543" [-]
      ReferenceError: Can't find entity "vera>device_543"
      at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:366:27)
      at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106)
      at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47)
      at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37)
      at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54)
      at async /home/tbully/reactor/server/lib/Rule.js:830:17
      [stable-22337]2022-12-31T00:33:49.773Z Rule:INFO Home Button Battery Low (rule-grp17k2iotv in Battery Checks) evaluated; trigger state changed ((null)), but rule state remains NULL
      [stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Home Button Battery Low (rule-grp17k2iotv in Battery Checks) started
      [stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Sump Pump Flood Detected (rule-grp17k301y1 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
      [stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Sump Pump Flood Detected (rule-grp17k301y1 in Flood Checks) started
      [stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Rec Room Flood Detected (rule-grp17k30cm0 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
      [stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Rec Room Flood Detected (rule-grp17k30cm0 in Flood Checks) started
      [stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Office Flood Detected (rule-grp17k30mqa in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
      [stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Office Flood Detected (rule-grp17k30mqa in Flood Checks) started
      [stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Laundry Flood Detected (rule-grp17k31kf1 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
      [stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Laundry Flood Detected (rule-grp17k31kf1 in Flood Checks) started
      [stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Half-Bath Flood Detected (rule-grp17k31z13 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
      [stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Half-Bath Flood Detected (rule-grp17k31z13 in Flood Checks) started
      [stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Upstairs Bath Flood Detected (rule-grp17k327c0 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
      [stable-22337]2022-12-31T00:33:49.776Z Rule:INFO Upstairs Bath Flood Detected (rule-grp17k327c0 in Flood Checks) started
      [stable-22337]2022-12-31T00:33:49.776Z Rule:INFO Garage Tilt Sensor Battery Low (rule-grp17k3frdb in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
      [stable-22337]2022-12-31T00:33:49.776Z Rule:INFO Garage Tilt Sensor Battery Low (rule-grp17k3frdb in Battery Checks) started
      [stable-22337]2022-12-31T00:33:49.782Z Rule:ERR Rule#rule-grp17k3ui8q trigger evaluation failed: [ReferenceError] Entity Vera (vera>system) has no attribute "x_vera_sys.reloads" [-]
      [stable-22337]2022-12-31T00:33:49.782Z Rule:CRIT ReferenceError: Entity Vera (vera>system) has no attribute "x_vera_sys.reloads" [-]
      ReferenceError: Entity Vera (vera>system) has no attribute "x_vera_sys.reloads"
      at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:373:27)
      at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106)
      at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47)
      at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37)
      at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54)
      at async /home/tbully/reactor/server/lib/Rule.js:830:17
      [stable-22337]2022-12-31T00:33:49.782Z Rule:INFO LuupReload (rule-grp17k3ui8q in House Reactor) evaluated; trigger state changed ((null)), but rule state remains NULL
      [stable-22337]2022-12-31T00:33:49.783Z Rule:INFO LuupReload (rule-grp17k3ui8q in House Reactor) started
      [stable-22337]2022-12-31T00:33:49.783Z Rule:INFO VeraSecureTriggered (rule-grplg89w7x in House Reactor) evaluated; trigger state unchanged (false); rule state remains RESET
      [stable-22337]2022-12-31T00:33:49.783Z Rule:INFO VeraSecureTriggered (rule-grplg89w7x in House Reactor) started
      [stable-22337]2022-12-31T00:33:49.783Z Rule:INFO TurnOffPantryLights (rule-grplt8fpma in Basement Reactor) evaluated; trigger state unchanged (false); rule state remains RESET

      [stable-22337]2022-12-31T00:33:49.902Z <Rule:INFO> Garage Lights Off - After Auto On (rule-grpp2yoxfg in Garage Reactor) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.902Z <Rule:INFO> Garage Reactor (rule-492 in Garage Reactor) evaluation complete
[stable-22337]2022-12-31T00:33:49.902Z <Rule:INFO> Garage Lights Off - After Auto On (rule-grpp2yoxfg in Garage Reactor) evaluation complete
[stable-22337]2022-12-31T00:33:49.907Z <httpapi:NOTICE> httpapi: listening
[stable-22337]2022-12-31T00:33:49.921Z <app:NOTICE> Starting WSAPI...
[stable-22337]2022-12-31T00:33:49.922Z <wsapi:NOTICE> wsapi: starting version 22320
[stable-22337]2022-12-31T00:33:50.112Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "12/30/2022, 7:33:50 PM" (TZ offset -300 mins from UTC)
[stable-22337]2022-12-31T00:33:50.120Z <app:NOTICE> Shutdown signal (SIGTERM) received. Stopping Reaction Engine...
[stable-22337]2022-12-31T00:33:50.121Z <app:NOTICE> Closing APIs...
[stable-22337]2022-12-31T00:33:50.121Z <wsapi:NOTICE> wsapi: closing...
[stable-22337]2022-12-31T00:33:50.121Z <httpapi:NOTICE> HTTP API closing...
[stable-22337]2022-12-31T00:33:50.121Z <app:NOTICE> Stopping Engine...
[stable-22337]2022-12-31T00:33:50.128Z <Rule:NOTICE> Turn Off Upstairs Hall Light (rule-grprsxsoqm in UpstairsHall Reactor) stopping
[stable-22337]2022-12-31T00:33:50.129Z <Rule:NOTICE> Run Hot Water Recirculation (rule-l7ey8s4w in House Reactor) stopping
[stable-22337]2022-12-31T00:33:50.130Z <Rule:NOTICE> Run Fans (rule-l6pi77c2 in House Reactor) stopping
[stable-22337]2022-12-31T00:33:50.130Z <Rule:NOTICE> VeraSecureTriggered (rule-grplg89w7x in House Reactor) stopping

      [stable-22337]2022-12-31T00:33:50.329Z <Rule:NOTICE> Half-Bath Flood Detected (rule-grp17k31z13 in Flood Checks) stopped
[stable-22337]2022-12-31T00:33:50.330Z <Rule:NOTICE> Upstairs Bath Flood Detected (rule-grp17k327c0 in Flood Checks) stopped
[stable-22337]2022-12-31T00:33:50.417Z <Engine:NOTICE> [Engine]Engine#1 has shut down.
[stable-22337]2022-12-31T00:33:50.417Z <app:NOTICE> Closing Structure...
[stable-22337]2022-12-31T00:33:50.418Z <Structure:INFO> Structure#1 Stopping controllers...
[stable-22337]2022-12-31T00:33:50.418Z <Controller:NOTICE> VeraController#vera stopping
[stable-22337]2022-12-31T00:33:50.524Z <HassController:NOTICE> HassController#hass stopping
[stable-22337]2022-12-31T00:33:50.526Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error] WebSocket was closed before the connection was established [-]
[stable-22337]2022-12-31T00:33:50.526Z <HassController:WARN> HassController#hass ws error code (undefined)
[stable-22337]2022-12-31T00:33:50.526Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error] WebSocket was closed before the connection was established [-]
[stable-22337]2022-12-31T00:33:50.527Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.34.17:8123/api/websocket closed during open/negotiation
[stable-22337]2022-12-31T00:33:50.527Z <Controller:NOTICE> HassController#hass stopping
[stable-22337]2022-12-31T00:33:50.803Z <Controller:NOTICE> SystemController#reactor_system stopping
[stable-22337]2022-12-31T00:33:50.811Z <Controller:ERR> Controller SystemController#reactor_system is off-line!
[stable-22337]2022-12-31T00:33:50.814Z <Structure:INFO> Structure#1 Final data sync...
[stable-22337]2022-12-31T00:33:50.838Z <Structure:NOTICE> Structure Structure#1 stopped
[stable-22337]2022-12-31T00:33:50.839Z <app:NOTICE> Stopping timers...
[stable-22337]2022-12-31T00:33:50.840Z <app:NOTICE> Shutdown complete, process ID 7240
      posted in Multi-System Reactor
      T
      tbully
    • Reactor Start - System Crash/Restart

      Hello All -
      I upgraded my OS to Ubuntu 20.04 today and have been regretting it for several hours. I have most of my system up. However, I've found that, when I start Reactor, it panics / reboots my OS. I've included the syslog during startup below. There's a benign message about not finding a Vera device just before the reboot but that's it.

      Needless to say, I've learned my lesson regarding OS upgrades.

      Bare metal Linux / Ubuntu 20.04 (Running inside VirtualBox)
      Reactor Version: stable-22337-1a0a685f

      Dec 30 19:33:46 homeauto03 systemd[1]: Started Multi System Reactor.
Dec 30 19:33:46 homeauto03 weewx[6592] INFO weewx.restx: Wunderground-RF: Published record 2022-12-30 19:33:46 EST (1672446826)
Dec 30 19:33:46 homeauto03 node[7240]: Reactor stable-22337-1a0a685f app 22328 configuration from /home/tbully/reactor/config
Dec 30 19:33:46 homeauto03 node[7240]: NODE_PATH /home/tbully/reactor
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.745Z <app:null> Reactor build stable-22337-1a0a685f starting on v17.9.0
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.746Z <app:null> Process ID 7240 user/group 1000/1000; bare-metal; platform linux/x64 #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022; locale en_CA.UTF-8
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.746Z <app:null> Basedir /home/tbully/reactor; data in /home/tbully/reactor/storage
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.747Z <app:null> NODE_PATH=/home/tbully/reactor
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.764Z <Structure:null> Module Structure v22323
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.765Z <Capabilities:null> Module Capabilities v22283
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.819Z <Plugin:null> Module Plugin v22300
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.827Z <TimerBroker:null> Module TimerBroker v22283
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.831Z <Entity:null> Module Entity v22314
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.835Z <Controller:null> Module Controller v22323
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.847Z <default:null> Module Ruleset v22293
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.848Z <default:null> Module Rulesets v21096
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.854Z <GlobalExpression:null> Module GlobalExpression v21333
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.864Z <Predicate:null> Module Predicate v22305
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.867Z <AlertManager:null> Module AlertManager v22283
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.869Z <Rule:null> Module Rule v22335
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.872Z <GlobalReaction:null> Module GlobalReaction v22320
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.873Z <Engine:null> Module Engine v22320
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.877Z <httpapi:null> Module httpapi v22337
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.886Z <wsapi:null> Module wsapi v22320
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.949Z <TaskQueue:null> Module TaskQueue 21351
Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.950Z <VeraController:null> Module VeraController v22325
Dec 30 19:33:47 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:47.200Z <HassController:null> Module HassController v22334
Dec 30 19:33:48 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:48.294Z <SystemController:null> Module SystemController v22306
Dec 30 19:33:48 homeauto03 weewx[6592] INFO weewx.restx: Wunderground-RF: Published record 2022-12-30 19:33:48 EST (1672446828)
Dec 30 19:33:49 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:49.110Z <Rule:CRIT> ReferenceError: Can't find entity "vera>device_368" [-]
Dec 30 19:33:49 homeauto03 node[7240]: ReferenceError: Can't find entity "vera>device_368"
Dec 30 19:33:49 homeauto03 node[7240]:     at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:366:27)
Dec 30 19:33:49 homeauto03 node[7240]:     at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106)
Dec 30 19:33:49 homeauto03 node[7240]:     at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47)
Dec 30 19:33:49 homeauto03 node[7240]:     at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37)
Dec 30 19:33:49 homeauto03 node[7240]:     at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54)
Dec 30 19:33:49 homeauto03 node[7240]:     at async /home/tbully/reactor/server/lib/Rule.js:830:17
Dec 30 19:33:49 homeauto03 systemd[1]: Stopping Session 14 of User tbully...
      posted in Multi-System Reactor
      T
      tbully
    • RE: Where Used Functionality?

      I have the rules migrated and running on the external Reactor (doing some tweaking as you mentioned). That's not my issue.

      My issue is I'm now starting to exclude some devices from Vera and adding them to HASS. For the most part, I've been successful in knowing where the device is used in my ruleset. However, on a few occasions, I've forgotten / missed some rules.

      It would be great to look up an entity in MSR and see where it's used (either in rules or reactions) so I can account for the myriad places some devices exist.

      posted in Multi-System Reactor
      T
      tbully
    • Where Used Functionality?

      Hello All -

      I'm still working on moving dozens of devices from Vera (internal Reactor) to HASS and (external - bare metal) Reactor.

      One thing I've noticed is sometimes I move a few ZWave/Vera devices and find myself digging through rules finding where a device was used. Has anyone found a good way to do this?

      I plan on digging in to this thread but thought I'd check to see if there's anything more recent.

      https://smarthome.community/topic/483/entities-where-used-and-what-triggered-it?_=1669137134654

      posted in Multi-System Reactor
      T
      tbully
    • RE: Hot Water Recirc - Global Date/Time Variable

      All -

      I took a different approach. I didn't feel like asking the forum a bunch of stupid questions.

      1. Setup a global variable ("ReadyForRecirc") which will contain a true or false
      2. Utilize my global "Start Hot Water Recirculation" reaction. After starting the reaction, wait for 60 minutes before "ReadyForRecirc" is set to TRUE.
      3. Where I have logic to run recirculation, call the "Start Hot Water Recirculation" reaction, wait 5 seconds, set "ReadyForRecirc" to FALSE.

      Seems to work OK.

      p.s. I don't know why I have to manually enter true/false for my motions but seems to be OK.

      8ce5ebe2-aa54-4b33-97bc-eaa0163cabcd-image.png

      af1ddc30-dc5a-48f2-9dc7-f56bcf2822b1-image.png

      posted in Multi-System Reactor
      T
      tbully
    • RE: Hot Water Recirc - Global Date/Time Variable

      Interesting on the time() eval. Makes sense. I have to rethink this as I want it to be rather responsive without MSR constantly running the function. In other words, I don't want to wait a minute (as an example) for recirc to start when someone enters the bathroom.

      Also agree on boolean vs. string and thought it was weird that it wanted a string. Because it was a test (and that part worked), I didn't put much thought in to it.

      The time piece is really the issue at the moment.

      posted in Multi-System Reactor
      T
      tbully
    • RE: Hot Water Recirc - Global Date/Time Variable

      @crille
      Argh. Thanks. I meant time and clearly saw it in the manual. I was caught up on the function / call and syntax so this was helpful.

      Can someone check me on my logic? As a test, I'm looking for recirc to be ran 10 minutes or later and motion in the workshop.

      395805a6-5db6-4e1c-819b-8d521499786f-image.png

      posted in Multi-System Reactor
      T
      tbully