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

christian_fabre

@christian_fabre
Disaster recovery and virtualisation
CatmanV2C

Following on from my last thread, some progress has been made over the weekend.

With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system.

Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic.

Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work.

Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic.

Once that hurdle is sorted I'm torn between:

Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.)

Decisions, decisions.

C

General Discussion
Remote access of Zwave stick from Z-wave server
CatmanV2C

Afternoon, all.

In my continued attempts to virtualise my system, I'm in the last (I hope throes)

I don't fancy relying on Synology not to break more USB activities, so decided to set up ser2net on a Raspberry pi and plug in a spare Z-wave.me stick

So on the Raspberry pi: ser2net. yaml

catman@Zwave:/etc $ cat ser2net.yaml %YAML 1.1 --- # This is a ser2net configuration file, tailored to be rather # simple. # # Find detailed documentation in ser2net.yaml(5) # A fully featured configuration file is in # /usr/share/doc/ser2net/examples/ser2net.yaml.gz # # If you find your configuration more useful than this very simple # one, please submit it as a bugreport define: &banner \r\nser2net port \p device \d [\B] (Debian GNU/Linux)\r\n\r\n connection: &zwave0 # Bind to TCP port accepter: tcp,4000 enable: on options: kickolduser: true # Ensure mDNS is disabled mdns: false connector: serialdev, /dev/ttyACM0,115200N81,nobreak,local

And if I telnet to it from anywhere:

catman@ChrisMBP15-2018 ~ % telnet 192.168.70.128 4000 Trying 192.168.70.128... Connected to 192.168.70.128. Escape character is '^]'.

Which makes me think that ser2net is doing its thing.

Now in my virtualised Z-wave server I have this:

Screenshot 2025-04-10 at 17.36.52.png

(I've tried with a colon and a space between the ip and the port)

The result:

An unexpected error occurred during loading data. Try to reload the page. Please check 1.) if the controller is plugged in correctly, 2.) that in the app 'Z-Wave Network Access' the right port is entered (UZB: '/dev/ttyACM0', RaZberry shield: '/dev/ttyAMA0', UZB-Windows: '\\.\COM3', Z-Stick: '/dev/ttyUSB0', embedded boxes: '/dev/ttyS0' or '/dev/ttyS1') 3.) the app is aktiv. If not you could activate it under Menu > Apps > Active or add a new one under Menu > Apps > Local. The Setting 'Expert View' needs to be active under Menu > My Settings.

Any pointers as to what I'm doing wrong?

TIA!

C

Software
Organizing/ structuring rule sets and rules
R

Hi guys,

Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular.

Maybe there are better ways to organize my rule sets.

I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.

Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT

I have installed MSR on a RP5 bare metal and then copied the config and store files. Everything seems to be on the RP5 but I am missing all global expression and I don't see the controller time.

Screenshot 2025-04-06 201446.png

My browser is Microsoft Edge Version 135.0.3179.54 (Official build) (64-bit)

I have probably done something stupid or missed a step but I am stuck.

Thanks for any help.

Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M

Hi,
It seems that the widget deletion does not work. I tried to drag the widget to the left (as explained in here https://smarthome.community/topic/1071/deleting-widgets?_=1744037333660)
but it does not delete it. Anyone else experiencing the same problem?

Also the landing page after login is empty and seems be have some JS issues on the dev console:

Screenshot from 2025-04-07 18-06-19.png

fd7f0424-debb-49d3-86d8-9a3b09ad3868-image.png

Using dockerized version of Reactor (Multi-hub) latest-25082-3c348de6 on Chromium 135.0.7049.52 (Official Build) snap (64-bit)

br,
mgvra

Multi-System Reactor
Need help reducing false positive notifications
T

Good day all,
I have an notification set up for my washing machine to let me know when it's complete. I have a templete sensor set up in HAAS to let me know if it's Washing, in Standby, or off, based upon the power consumption (Shelly 1PM on outlets)

- name: "Washing Machine" state: > {% if states("sensor.washer_switch_0_power")|float == 0 %} Off {% elif states("sensor.washer_switch_0_power")|float <= 2.9 %} Standby {% else %} Washing {% endif %} icon: > {% if states("sensor.washer_switch_0_power") == "off" %} mdi:washing-machine-alert {% elif states("sensor.washer_switch_0_power")|float <= 2.9 %} mdi:washing-machine-off {% else %} mdi:washing-machine {% endif %} minutes: 2

The MSR code is relatively simple. I have a built in false positive attribute for if MSR gets rebooted, because I would suddenly get tons of notifications when I upgraded MSR.

6774565a-06cc-443f-99c1-e71301b33d83-image.png

What I'm trying to introduce, is a way to verify that I just didn't bump the knob on the washing machine when transferring loads from the washer to the dryer, which turns on the display and brings the power above the Standby threshold.

The power goes up to 3.7W for about 4 minutes if the selector knob is bumped/turned.

What would the best way to do this be? I have most of my MSR code set up for a couple of years now, and my coding logic is struggling a bit.

I think I need a power threshold to be substained for a minimum time period (say 2 or 3 minutes, above 10W), before the other triggers can act. What would the best way to do that be?

Running: latest-25082-3c348de6
Fedora 41 Server
HAAS:
Core
2025.3.4
Supervisor
2025.03.4
Operating System
15.1
Frontend
20250306.0

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

Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.

Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Deleting widgets
tunnusT

Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266

Multi-System Reactor
MQTT configuration question
tunnusT

I have the following yaml configuration in local_mqtt_devices file

x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }'

While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?

Multi-System Reactor
System Configuration Check - time is offset
F

Hi!

I get this message when I'm on the status tab:

System Configuration Check
The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds.

I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6.
HA versions are:
Core 2025.3.4
Supervisor 2025.03.4
Operating System 15.1

I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version.
Do anyone know what I can try?
Thanks in advance!
Let's Be Careful Out There (Hill Street reference...) 🙂
/Fanan

Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT

I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB.

While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed.

So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response.

While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits

Thanks!

Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N

Hi ,
I'm on
-Reactor (Multi-hub) latest-25067-62e21a2d
-Docker on Synology NAS
-ZWaveJSUI 9.31.0.6c80945

Problem with ZwaveJSUI:
When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white.
I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui.

I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb".
After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color.

This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite.

x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33}

The "cold white" and "warm white" settings interfer with the rgb color settings.

Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white
are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white.

So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have

x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor

In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set.

x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33

Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this?

x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33}

Thanks in advance.

Multi-System Reactor
Problem with simultaneous notifications.
T

Good day all,
I have a reaction set up, that I use for both troubleshooting and changing home modes when one of my family members either arrive or are leaving. I use the companion app for HAAS on our iPhones, and HAAS reports if the person associated with the iPhone enters or leaves the geofenced area around my home. I'm sure most MSR and HAAS users are familiar with this.

I use this rule set mainly as a condition for other rules, however, as part of troubleshooting, a notification is sent through HAAS to the companion app when the rule becomes true. The problem is that I'm getting notifications now for both arriving and departing simultaneously.

96b3f7db-ba09-499e-a78c-86903b603857-image.png

36903cdd-a87f-473b-82ef-af9ef96d3c44-image.png It used to work fine as intended. I'm not sure exactly when it changed, but now I'm getting two notifications when either of these conditions change.

Any idea what could be happening?

Edit:
Running: latest-25082-3c348de6, bare-metal Linux
ZWaveJSControllerr [0.1.25082]

Multi-System Reactor
Problem after upgrading to 25067
R

MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem?
I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.

Multi-System Reactor
Global expressions not always evaluated
tunnusT

Similarly as for local expressions, global expressions evaluate and update fine when getEntity(...) structure is used. However, at least when certain functions are in use, expressions do not update.

Consider the following test case:

Screenshot 2025-03-13 at 16.29.42.png

Even though auto-evaluation is active, value does not change (it changes only if that expression is manually run). MSR restarts do not help.

Screenshot 2025-03-13 at 16.31.43.png

Note: Tested using build 25067 on Docker. I have also a PR open (but couldn't now get details or PR number as my Mantis account was somehow expired?).

Multi-System Reactor
[Solved] Local expression evaluation
V

Trying to understand what cause a local expresssion to be evaluated. I have read the manual but I am still not clear about it. Using the test rule below, I can see in the log that the rule is being automatically evaluated every time the temperature entity is changing. That is great...

What I am trying to understand is why the expression is not evaluated based on time as well since the "case" statement has time dependencies.

Any help would be appreciated

I have the following test rule:

eba6a3ea-ff61-4610-88c9-9b9864f11ff8-Screenshot 2025-01-21 095244.png

2d9c1ff5-7b73-4005-b324-9029c2709db9-Screenshot 2025-01-21 095302.png

Here is the expressioncode:

vFrom1 = "09:25:00", vFrom2 = "09:30:00", vFrom3 = "09:41:00", vTo = "10:55:00", # Get current time (format HH:MM:SS) vToDay = strftime("%H:%M:%S"), #Get current house temperature CurrentHouseTemp = getEntity( "hass>Thermostat2 " ).attributes.temperature_sensor.value, case when CurrentHouseTemp <= 19 and vToDay >= vFrom1 && vToDay <= vTo: "true1" # From1 when CurrentHouseTemp <= 20 and vToDay >= vFrom2 && vToDay <= vTo: "true2" # From2 when CurrentHouseTemp < 26  and vToDay >= vFrom3 && vToDay <= vTo: "true3" # From3 else "false" end
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S

I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved.

The Runtime Error is different in the two browsers
Safari v18.3

@http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.

Google Chrome 133.0.6943.142

TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.

Steps to reproduce:
Click the pencil to edit a global reaction with a group.
Click the Exit button.
Runtime error appears.
or
Click Create Reaction
Click Add Action
Select Group
Add Condition such as Entity Attribute.
Add an Action.
Click Save
Click Exit
Runtime error appears.

I don’t know how long the error has been there as I haven’t edited the global reaction in a long time.

Reactor (Multi-hub) latest-25060-f32eaa46
Docker
Mac OS: 15.3.1
Thanks

Multi-System Reactor
Cannot delete Global Expressions
SnowmanS

I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons.

I have not created a global expression for some times and just noticed this while doing some clean-up.

I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success.

Here's what the log shows.

[latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" }

Reactor latest-25067-62e21a2d
Docker on Synology NAS

Multi-System Reactor
Advice on Storing and Backing Up Bind Mounts - Docker
PablaP

Hello all, after seeing Catman's posts about their disaster recovery and move to Docker I took that as a sign to migrate everything (aside from HA) to Docker. After a small learning curve I had Docker+Portainer up and running in a few days.

Instead of using named Volumes I opted to use Bind Mounts so I can easily edit conf files and any other file needed. I do understand the nuances that come with bind mounts, such as migration to a different host may require changing file structures, the possibility of someone editing the bind mount files and permissions but to me those aren't too big of a deal.

My question is what is the best way to keep a back up of these bind mounts? I currently have them stored in the /etc directory in another directory named on a per container basis. I was thinking to move it all to a /home/user/docker/ directory so that I can use a simple cp command to my mounted SMB share to backup all the container data files. Anyone else do it differently?

Side note: I finally got to flex the benefits of Docker with updating Reactor.. it was dead simple. I had no idea what I was missing out on lol!

Software
Local notification methods?
CatmanV2C

Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method.

This was prompted by yesterday's fun and games with my ISP.

I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone)

I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions?

TIA

C

Multi-System Reactor
About
Posts
54
Topics
6
Groups
0
Followers
1
Following
2

Posts

Recent Best Controversial
  • New to Home Automation Looking for a Single app?
    C christian_fabre

    Ring doorbell is supported by Home Assistant.

    Home Assistant

    Ring

    Ring

    Instructions on how to integrate your Ring.com devices within Home Assistant.

  • looking for a light switch with presence sensor?
    C christian_fabre

    I am testing the following presence sensors:
    Sensor FP2 - AQARA
    Sensor SNZB-06P - SONOFF
    The Aqara detector can detect several areas, and several people, and seems to be very reliable.
    I'm starting to test the sonoff which only detects a presence and which costs much less.

  • MIOS - UI5 web login
    C christian_fabre
    MiOS
    click on the link(cp.mios.com/mysystems.php)
    mios.jpg

  • MIOS - UI5 web login
    C christian_fabre

    https://cp.mios.com/login.php```

    MiOS
  • MIOS - UI5 web login
    C christian_fabre
    MiOS
  • No drop-down list on Entity Attribute in "Creation Rule Sets" interface
    C christian_fabre

    Following the change of browser (Microsoft Edge) and the proper functioning of the entities dialog box, I modified my Google Chrome version
    from the beta version (Version 111.0.5563.50 (Official build) beta (64 bits))
    to the stable version (Version 110.0.5481.178 (Official Build) (64-bit))
    to see that it works fine.
    Thank you once again for your help which solved my problem which had been going on for several days...
    Cordially

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

    I'm using Google Chrome Version 111.0.5563.50 (Official Build) beta (64 bit)
    I refreshed the browser, but the click does not open the entities dialog
    I just found that I have the same problem on Global expressions, I can't display the entities list.
    I feel like the call function to open the entities dialog is not working.

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

    @toggledbits
    *
    Yes, but clicking does not open the dialog box: nothing happens....
    I already use a version of Reactor installed on another Raspberry pi4, installed without Docker and it works fine.

    I'm migrating to a new raspberry pi 4 where I installed Docker, Portainer, MQTT, Zigbee2Mqtt, Zwave-js-ui without issue.
    The installation of Reactor seems correct, the only problem is that no dialog box opens when clicking to select an entity.
    I restarted the installation several times and I have the same observation.
    Can you please give me some hint to try to solve this problem. Why does the click not call the entities dialog box?
    THANKS

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

    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```
  • Adding remotes, scene controllers as entities to MSR
    C christian_fabre 
    # If you have more than one of any type of controller, just copy the section for controller type
# and give it new (unique) "id". There is no limit on the number of controllers.
controllers:

  - id: hass
    enabled: true
    implementation: HassController
    name: A Home Assistant system
    config:
      source: 'wss://XX.XX.XX.XX:8123'
      access_token: "YYYYYYYYY"
      #
      event_targets:    # this section starts the event-receiving entities
              "Hank_SCN04_bp1":      # Assign an ID to your entity; each entity must have a unique ID
               name: Hank_bp1   # This is optional but recommended, so you have a friendly name
               capabilities: ['button']  # define an array of capabilities to be modified by the event 
               events:  # define an array of events that modify capability attributes on the entity
                 - event:  # start of an event; each element of the events array begins this way
                     event_type: zwave_js_value_notification
                     data:  # optional section, if further matching to the event data is required
                       node_id: 12
                       property: "scene" # Square button
                       property_key: "001"
                   response:  # begin the (required) response section for handling the event
                     "button.state":  # an attribute that the event modifies.
                       from: "event.data.value"  # dot-reference expression to pull value from event message
                       map:                    # optional, map to modify value
                         KeyPressed: 'appui_court'   # if value is value_in, it is mapped to new_value
                         KeyReleased: 'appui_relache'
                         KeyHeldDown: 'appui_maintenu'
                     "button.since":  # an attribute that the event modifies.
                       from: "event.context.id"  # dot-reference expression to pull value from event message		
              "Hank_SCN04_bp2":      # Assign an ID to your entity; each entity must have a unique ID
               name: Hank_bp2   # This is optional but recommended, so you have a friendly name
               capabilities: ['button']  # define an array of capabilities to be modified by the event 
               events:  # define an array of events that modify capability attributes on the entity
                 - event:  # start of an event; each element of the events array begins this way
                     event_type: zwave_js_value_notification
                     data:  # optional section, if further matching to the event data is required
                       node_id: 12
                       property: "scene" # Square button
                       property_key: "002"
                   response:  # begin the (required) response section for handling the event
                     "button.state":  # an attribute that the event modifies.
                       from: "event.data.value"  # dot-reference expression to pull value from event message
                       map:                    # optional, map to modify value
                         KeyPressed: 'appui_court'   # if value is value_in, it is mapped to new_value
                         KeyReleased: 'appui_relache'
                         KeyHeldDown: 'appui_maintenu'
                     "button.since":  # an attribute that the event modifies.
                       from: "event.context.id"  # dot-reference expression to pull value from event message
              "Hank_SCN04_bp3":      # Assign an ID to your entity; each entity must have a unique ID
               name: Hank_bp3   # This is optional but recommended, so you have a friendly name
               capabilities: ['button']  # define an array of capabilities to be modified by the event 
               events:  # define an array of events that modify capability attributes on the entity
                 - event:  # start of an event; each element of the events array begins this way
                     event_type: zwave_js_value_notification
                     data:  # optional section, if further matching to the event data is required
                       node_id: 12
                       property: "scene" # Square button
                       property_key: "003"
                   response:  # begin the (required) response section for handling the event
                     "button.state":  # an attribute that the event modifies.
                       from: "event.data.value"  # dot-reference expression to pull value from event message
                       map:                    # optional, map to modify value
                         KeyPressed: 'appui_court'   # if value is value_in, it is mapped to new_value
                         KeyReleased: 'appui_relache'
                         KeyHeldDown: 'appui_maintenu'
                     "button.since":  # an attribute that the event modifies.
                       from: "event.context.id"  # dot-reference expression to pull value from event message
              "Hank_SCN04_bp4":      # Assign an ID to your entity; each entity must have a unique ID
               name: Hank_bp4   # This is optional but recommended, so you have a friendly name
               capabilities: ['button']  # define an array of capabilities to be modified by the event 
               events:  # define an array of events that modify capability attributes on the entity
                 - event:  # start of an event; each element of the events array begins this way
                     event_type: zwave_js_value_notification
                     data:  # optional section, if further matching to the event data is required
                       node_id: 12
                       property: "scene" # Square button
                       property_key: "004"
                   response:  # begin the (required) response section for handling the event
                     "button.state":  # an attribute that the event modifies.
                       from: "event.data.value"  # dot-reference expression to pull value from event message
                       map:                    # optional, map to modify value
                         KeyPressed: 'appui_court'   # if value is value_in, it is mapped to new_value
                         KeyReleased: 'appui_relache'
                         KeyHeldDown: 'appui_maintenu'
                     "button.since":  # an attribute that the event modifies.
                       from: "event.context.id"  # dot-reference expression to pull value from event message
      #
      #

    I abruptly attach a copy of my file.
    I was inspired by the code given in the posts above
    It works correctly for me.

  • Rule corruption after sudden power outage
    C christian_fabre

    Thank you for your reply
    My system is a Raspberry Pi4 4GB with a 120GB SSD from stock.
    Which is weird, I had the same problem twice following power outages.
    I'm going to power it through my inverter to prevent this from happening again.

  • Rule corruption after sudden power outage
    C christian_fabre

    Context :

    • MSR version 22203 on Raspberry Pi4.
    • A new power outage due to a violent storm.
      when the electricity returns, I notice that some Rules do not work correctly.
      In fact all those that use "Run Reaction".
      It is missing in Set Reaction the entire part after the first Run Reaction and cannot be recreated.
      I was able to remount a backup to be able to find all my functionalities.
      FYI, I had the same problem 2 weeks ago.2022-08-17reactor_1.png 2022-08-17reactor_2.png 2022-08-17reactor_3.png
  • MSR actions aren't running anymore-- can't find what's broken
    C christian_fabre

    I had the same problem yesterday following a power outage.
    I saw that MSR reacted but there was no effective reaction.
    I didn't see anything in the logs
    I reinstalled MSR and the problem went away.

  • Adding remotes, scene controllers as entities to MSR
    C christian_fabre

    Thanks ...
    I followed this post and managed to successfully use my HANK SCN04 remote with Reactor and Home Assistant.

  • Smart door lock
    C christian_fabre

    I live in France.
    Personally, I have had a "The Keys" connected lock for 2 or 3 years with a WiFi Bridge, which I will surely change soon.
    It has an API, a smartphone application.
    I am interested in this lock currently:
    NUKI SMART LOCK 3.0 PRO (BLACK), BLUETOOTH/WI-FI CONNECTED LOCK

  • Summer Time : fonction interval
    C christian_fabre

    the previous example: for a recurrence of 2 weeks:
    even week number and Date/Time condition --> Action 1
    odd week number and Date/Time condition --> Action 2

  • Summer Time : fonction interval
    C christian_fabre

    tthank you.
    I had thought about it but I didn't want to use the interval function anymore.
    Could we also have a choice of week number?

  • Summer Time : fonction interval
    C christian_fabre

    Thank you for your answers.
    I modified as you suggest and it seems more coherent to me.
    On the other hand, I also have 2 recurrences every 2 weeks, in turn:
    Wednesday 1--> Action1,
    Wednesday 2--> Action2,
    Wednesday 3--> Action1,
    Wednesday 4--> Action2,
    etc...
    I don't see how to do...

  • Summer Time : fonction interval
    C christian_fabre

    reactor_01.png

    recactor02.png

  • Login
  • Don't have an account? Register
  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved