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

vezinpi

@vezinpi
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Wiring Samotech SM308-S into light fitting
F
Hi Smart Home Community. I have used a Sonos inline WiFi switch to make one of my light fittings smart, but it requires a hard reset for WiFi changes, plus it isn't zigbee compatible, which means I can't use the Hue app to control it with the rest of the lights. To that end I bought a Samotech SM308-S as it is recommended as the better than the Sonos equivalent. I am however not exactly sure how to wire it in. The manual is available here Can anyone help me by clarifying which ports I need to use, and whether I should be using the live or switched live line for live etc. I will be keeping using standard switches for a while, although hope to upgrade to tap dials once I have all the fittings upgraded. Thanks
Hardware
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Z-Wave Future....
DesTD
https://forum.z-wave.me/viewtopic.php?f=3417&t=36140 That's not a good thing I think Time to switch again?
Z-Wave.me
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Disaster recovery and virtualisation
CatmanV2C
Following on from my last thread, some progress has been made over the weekend. With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system. Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic. Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work. Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic. Once that hurdle is sorted I'm torn between: Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.) Decisions, decisions. C
General Discussion
Remote access of Zwave stick from Z-wave server
CatmanV2C
Topic thumbnail image
Software
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
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
About
Posts
65
Topics
18
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial
  • [SOLVED]Logs permissions for Docker Install
    V vezinpi

    Super, it worked as expected.

    My MSR installation date from all the way back at the begining of this treck. I do recollect adjusting the # of logs and size but not adding the "mode". In any case, I see from the dist-config/logging.yaml that the default is 0644 (which would work just fine) and that it is commented out. That is probably what everybody have and the reason why I was the lone woolf out there. I think I will follow the pack and comment it out.

    EDIT: I did add the "mode" back in dec 2021 to fix a similar issue. Things have changed/evolved since causing the issue to show up again.

    Many thanks

    Multi-System Reactor
  • [SOLVED]Logs permissions for Docker Install
    V vezinpi

    All my docker applications, including reactor, have a volume in my "automation" folder on the host.

    vezinpi@RPI8G:~/automation $ ls -l
total 32
drwxr-xr-x  2 vezinpi vezinpi 4096 May 28  2023 docker-compose
drwxrwxrwx  4 vezinpi vezinpi 4096 Jan 14 13:41 esphome
drwxrwxrwx  8     472     472 4096 Feb  8 07:45 grafana
drwxrwxrwx 12 vezinpi vezinpi 4096 Feb  6 15:25 homeassistant
drwx------  3 vezinpi root    4096 Feb 22  2023 influxdb2
drwxrwxrwx  6 vezinpi vezinpi 4096 Jun 20  2024 reactor
drwxr-xr-x  9 vezinpi root    4096 Feb  8 03:28 ssl
drwxrwxrwx 11 vezinpi vezinpi 4096 Feb  8 07:52 zwave-js-ui

    Here is the reactor folder:

    vezinpi@RPI8G:~/automation $ ls -l reactor
total 64
drwxrwxrwx 2 vezinpi vezinpi  4096 Feb  5 21:38 config
drwxrwxr-x 2 root    root     4096 Feb  6 14:07 dist-config
drwxrwxrwx 2 vezinpi vezinpi  4096 Feb  8 06:23 logs
-rwxrw-rw- 1 vezinpi vezinpi 45473 Jan  3  2022 reactor-config-backup.json
drwxrwxrwx 7 vezinpi vezinpi  4096 Jun 20  2024 storage
vezinpi@RPI8G:~/automation $

    Here is the log folder. Please note that some files still have read/write permissions for "other" . This is me changing the permission on the host to grant me access from my PC. The most recent one are back to write only (222). As the log rotation progresses they will all become 222.

    vezinpi@RPI8G:~/automation/reactor $ ls -l logs
total 44688
-rwxrw-rw- 1 vezinpi vezinpi    6572 Feb  6 14:07 hass_config.json
-rwxrw-rw- 1 vezinpi vezinpi  288139 Feb  6 14:07 hass_services.json
-rwxrw-rw- 1 vezinpi vezinpi  308677 Feb  6 14:07 hass_states.json
--w--w--w- 1 root    root    1802037 Feb  8 08:02 reactor.log
--w--w--w- 1 root    root    4194194 Feb  8 06:23 reactor.log.1
--w--w-rw- 1 root    root    4194347 Feb  7 06:16 reactor.log.10
--w--w-rw- 1 root    root    4194366 Feb  8 02:48 reactor.log.2
--w--w-rw- 1 root    root    4193980 Feb  7 21:59 reactor.log.3
--w--w-rw- 1 root    root    4194236 Feb  7 19:04 reactor.log.4
--w--w-rw- 1 root    root    4194260 Feb  7 17:18 reactor.log.5
--w--w-rw- 1 root    root    4194318 Feb  7 15:13 reactor.log.6
--w--w-rw- 1 root    root    4194256 Feb  7 12:39 reactor.log.7
--w--w-rw- 1 root    root    4193917 Feb  7 10:39 reactor.log.8
--w--w-rw- 1 root    root    4194228 Feb  7 09:10 reactor.log.9
-rw-r--r-- 1 root    root      11755 Feb  5 19:45 unhandled.json
-rwxrw-rw- 1 vezinpi vezinpi   24164 Feb 28  2022 vera-status-initial.json
-rwxrw-rw- 1 vezinpi vezinpi   48401 Feb 28  2022 vera-user_data-initial.json
-rwxrw-rw- 1 vezinpi vezinpi 1263301 Nov  6  2022 zwavejs_devices_initial.json
vezinpi@RPI8G:~/automation/reactor $

    config/logging.yaml

    vezinpi@RPI8G:~/automation/reactor/config $ more logging.yaml
---
logging:
  default:
    level: 4
    streams:
      - type: console
        level: 0
      - type: file
        name: "reactor.log"
        mode: 0666
        maxsize: 4  # megabytes max size
        keep: 10     # copies of old logs
        #
        # capture_console: if true, (most) console output will be captured to
        #                  this stream (if you have multiple streams, this
        #                  feature can only be used by ONE of them). If you
        #                  turn this on (true), set the "console" type stream
        #                  (above) log level to 0 to avoid duplicate logging
        #                  entries. The default is false, console not captured.
        #capture_console: true
  app:
    level: 4
  httpapi:
    level: 4
  httpproxy:
    level: 4
  wsapi:
    level: 4
  Structure:
    level: 4
  Controller:
    level: 4
  OWMWeatherController:
    level: 4
  VeraController:
    level: 4
  HubitatController:
    level: 4
  HassController:
    level: 4
  Rule:
    level: 5
  Engine:
    level: 5
(END)

    Hope this help

    Multi-System Reactor
  • [SOLVED]Logs permissions for Docker Install
    V vezinpi

    Ok, I guess that I did not put enough information to be clear. I skipped the intro and went directely into what I beleive to be the issue. I should stick with the issue not the solution. My bad.

    I do not go in the container to access the logs or change permissions but I did looked at them, trying understand how that works. Docker volumes, map the /var/reactor of the container to a directory on the host with read/write premissions. From the host it is then, via samba, shared to my PC where I would like to access the logs.

    Because of the permissions of the files, I cannot access the files directely from my PC. I have to change the permissions on the Host before I can access them (It can however, be access from the hosts by using "sudo" ).

    What I was trying to say in my initial post is that the permission are set to 222 in the container that get mapped to the the hosts and eventually to my PC. Changing the permissions on the host is only temporary until Reactor do a log rotation where the files changed back to 222. If the logfiles in the container were created with something like 226 the "read" permission for "other" would ripple all the way to the hosts a then to the PC.

    Like I said in my first post, I am not a Docker specialist but I thought that the only way to permanentely change the logs permissions would be by the application at the container level where they are created.

    That being said, I have been wrong before!

    Again, not a big deal just convenience.

    Multi-System Reactor
  • [SOLVED]Logs permissions for Docker Install
    V vezinpi

    Not a big issue simply a request if easily doable.

    The MSR logs files inside the container are owned by root witch is fine however, the permissions are very restrictive. I do not know if there is something wrong with my installation but the logs permission are set to 222 (write only). Even if the docker volume is set for Read/Write the log files are retaining these values.

    I go around the problem by doing a chmod 777 on all reactor logs but every time there is an MSR log rotation the permissions are set back to 222. So unless the permission are implemented in the container there is no permanent solution to this (that I know of).

    I do not know much about Docker container so I do not know what is involved here.

    Can the logfiles permission be simply chaged in the container to at least allow "other" read permission?

    Could the MSR log rotation routine implement a chmod to set the permission?

    Just a small anoyance

    Thanks

    Multi-System Reactor
  • [SOLVED]Hass websocket falsely reporting ready on boot??
    V vezinpi

    @mrFarmer said in [SOLVED]Hass websocket falsely reporting ready on boot??:

    Yes, clear status messages. Click reload. Wait until I see Connected and then go to the status page to see them in alerts.

    When you say reload do you mean "Restart Reactor" from the "Tool" menu? If so, the alarm will show right back until you refresh the page or restart your browser again. In my case the messages are only transitory following a "Restart Reactor" and are gone after I refresh the page.

    Multi-System Reactor
  • [SOLVED]Hass websocket falsely reporting ready on boot??
    V vezinpi

    Roger that.

    Again many thanks for your patience.

    Multi-System Reactor
  • [SOLVED]Hass websocket falsely reporting ready on boot??
    V vezinpi

    All right, that did the trick.

    I can clearly see in the log where it is waiting for the connection to be stable and sending the request only after. This is great!

    The 3 alarm are still showing when I use the "reboot reactor" from the Tools menu. It seems that it is only transitory since a screen refresh or re-starting the browser clears it. This is also fine.

    Just making sure that I understand the process. Please correct me where I am wrong.

    • without adding wait_all_controllers: true to the engine subsection, there is no delay

    • with the wait_all_controllers: true the default delay is 60 second

    • If the default delay is not enough then we can use startup_wait: xxxx to change the default delay

    • In all cases the delay is only the maximum delay and the wait will be terminated when the connections is made.

    • If I have 5 controllers, are they all treated individually or the slowest one need to be up before anything happen?

    @toggledbits said in Hass websocket falsely reporting ready on boot??:

    The controllers section is an array. Make sure DynamicGroupController and SystemController are the last two entries in the array.

    I am not sure I understand this one. I never played with the reactor.yaml file, I simply took the template and fill it up. I fail to see why these 2 controller need to be last. In my case I had 2 unused one between the two like it is in the template. I did move them but I am not sure that it really did anything.

    Many thanks for your support

    Multi-System Reactor
  • [SOLVED]Hass websocket falsely reporting ready on boot??
    V vezinpi

    With startup_wait: 120000 I have the same result as before.

    -Rule set to trigger at 00:55z
    -Shutdown down completed at 00:54:27z
    -First log entry after power up at 00:58:06
    -Socket connection with Hass at 00:58:12z

    [latest-25016]2025-02-06T00:54:27.398Z <Structure:NOTICE> Structure Structure#1 stopped
[latest-25016]2025-02-06T00:54:27.398Z <app:NOTICE> Closing APIs...
[latest-25016]2025-02-06T00:54:27.398Z <wsapi:NOTICE> wsapi: closing...
[latest-25016]2025-02-06T00:54:27.399Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.2.33#1" (1001 service closing)
[latest-25016]2025-02-06T00:54:27.401Z <httpapi:NOTICE> HTTP API closing...
[latest-25016]2025-02-06T00:54:27.403Z <wsapi:NOTICE> wsapi: server closed
[latest-25016]2025-02-06T00:54:27.405Z <wsapi:WARN> client close from unknown connection? "192.168.2.33#1"

[latest-25016]2025-02-06T00:58:06.180Z <app:null> Reactor build latest-25016-d47fea38 starting on v20.10.0 /usr/local/bin/node
[latest-25016]2025-02-06T00:58:06.198Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/arm64 #1 SMP PREEMPT Debian 1:6.6.74-1+rpt1 (2025-01-27); locale (undefined)
[latest-25016]2025-02-06T00:58:06.203Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage
[latest-25016]2025-02-06T00:58:06.207Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules
[latest-25016]2025-02-06T00:58:06.278Z <app:null> Resolved timezone=America/Toronto, environment TZ=America/Toronto; offset minutes from UTC=-300
[latest-25016]2025-02-06T00:58:06.337Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8
[latest-25016]2025-02-06T00:58:06.532Z <app:null> Loaded locale en-US for en-US
[latest-25016]2025-02-06T00:58:06.534Z <app:null> Local date/time using configured timezone and locale formatting is "2/5/2025, 7:58:06 PM"
[latest-25016]2025-02-06T00:58:07.077Z <Structure:null> Module Structure v24287
[latest-25016]2025-02-06T00:58:07.086Z <Capabilities:null> Module Capabilities v24312
[latest-25016]2025-02-06T00:58:07.289Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 25004 revision 1
[latest-25016]2025-02-06T00:58:07.784Z <Plugin:null> Module Plugin v22300
[latest-25016]2025-02-06T00:58:08.260Z <TimerBroker:null> Module TimerBroker v22283
[latest-25016]2025-02-06T00:58:08.284Z <Entity:null> Module Entity v25014
[latest-25016]2025-02-06T00:58:08.455Z <Controller:null> Module Controller v25014
[latest-25016]2025-02-06T00:58:08.786Z <default:null> Module Ruleset v24288
[latest-25016]2025-02-06T00:58:08.789Z <default:null> Module Rulesets v24220
[latest-25016]2025-02-06T00:58:09.072Z <GlobalExpression:null> Module GlobalExpression v24209
[latest-25016]2025-02-06T00:58:09.216Z <Predicate:null> Module Predicate v24350
[latest-25016]2025-02-06T00:58:09.274Z <AlertManager:null> Module AlertManager v24099
[latest-25016]2025-02-06T00:58:09.310Z <Rule:null> Module Rule v24329
[latest-25016]2025-02-06T00:58:09.348Z <GlobalReaction:null> Module GlobalReaction v24220
[latest-25016]2025-02-06T00:58:09.368Z <Engine:null> Module Engine v24344
[latest-25016]2025-02-06T00:58:09.422Z <httpapi:null> Module httpapi v24298
[latest-25016]2025-02-06T00:58:09.517Z <wsapi:null> Module wsapi v25016
[latest-25016]2025-02-06T00:58:09.520Z <app:NOTICE> Starting Structure...
[latest-25016]2025-02-06T00:58:09.548Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping
[latest-25016]2025-02-06T00:58:09.553Z <Structure:INFO> Structure#1 loading controller interface hass (HassController)
[latest-25016]2025-02-06T00:58:09.796Z <HassController:null> Module HassController v25010
[latest-25016]2025-02-06T00:58:12.086Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController)
[latest-25016]2025-02-06T00:58:12.119Z <DynamicGroupController:null> Module DynamicGroupController v24279
[latest-25016]2025-02-06T00:58:12.157Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController)
[latest-25016]2025-02-06T00:58:12.177Z <SystemController:null> Module SystemController v24279
[latest-25016]2025-02-06T00:58:12.202Z <Structure:INFO> Starting controller HassController#hass
[latest-25016]2025-02-06T00:58:12.203Z <HassController:NOTICE> HassController#hass starting...
[latest-25016]2025-02-06T00:58:12.205Z <Structure:INFO> Starting controller DynamicGroupController#groups
[latest-25016]2025-02-06T00:58:12.218Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online.
[latest-25016]2025-02-06T00:58:12.218Z <Structure:INFO> Starting controller SystemController#reactor_system
[latest-25016]2025-02-06T00:58:12.226Z <Controller:NOTICE> Controller SystemController#reactor_system is now online.
[latest-25016]2025-02-06T00:58:12.515Z <Engine:null> [Engine]Engine#1 config [Object]{ "enabled": true, "startup_wait": 120000, "monitored_entities": [ "vera>device_XXX" ] }
[latest-25016]2025-02-06T00:58:12.563Z <HassController:INFO> HassController#hass performing one-time initialization for HassController class
[latest-25016]2025-02-06T00:58:12.598Z <Controller:INFO> HassController#hass loaded hass capabilities ver 25004 rev 1 format 1 
[latest-25016]2025-02-06T00:58:12.686Z <Controller:INFO> HassController#hass loaded implementation data ver 25004 rev 2 format 1 
[latest-25016]2025-02-06T00:58:12.715Z <HassController:INFO> HassController#hass device mapping data loaded; checking...
[latest-25016]2025-02-06T00:58:12.752Z <HassController:NOTICE> HassController#hass connecting to wss://192.168.2.163:8123/api/websocket
[latest-25016]2025-02-06T00:58:12.818Z <app:NOTICE> Starting HTTP server and API...
[latest-25016]2025-02-06T00:58:12.861Z <httpapi:NOTICE> [HTTPAPI]#1 starting HTTP service on port 8111
[latest-25016]2025-02-06T00:58:12.874Z <app:NOTICE> Starting Reaction Engine...
[latest-25016]2025-02-06T00:58:12.876Z <Engine:INFO> Reaction Engine starting
[latest-25016]2025-02-06T00:58:12.878Z <Engine:INFO> Checking rule sets...
[latest-25016]2025-02-06T00:58:12.907Z <Engine:INFO> Checking rules...
[latest-25016]2025-02-06T00:58:12.921Z <Rule:5:Rule.js:209> Rule#rule-134 cleaning loaded condition states
[latest-25016]2025-02-06T00:58:12.931Z <Rule:5:Rule.js:209> Rule#rule-136 cleaning loaded condition states

    At 00:58:15z Sending reaction request to hass failed

    [latest-25016]2025-02-06T00:58:15.289Z <Engine:5:Engine.js:1786> [Engine]Engine#1 reaction rule-m6rz6ol1:S step 0 perform [Object]{ "entity": "hass>switch_plug_in_outlet_floater", "action": "power_switch.on" }
[latest-25016]2025-02-06T00:58:15.293Z <HassController:INFO> HassController#hass perform power_switch.on on Switch#hass>switch_plug_in_outlet_floater with [Object]{  }
[latest-25016]2025-02-06T00:58:15.296Z <HassController:WARN> HassController#hass unknown service homeassistant.turn_on in power_switch.on action on Switch#hass>switch_plug_in_outlet_floater
[latest-25016]2025-02-06T00:58:15.296Z <HassController:INFO> HassController#hass no entity/target for homeassistant.(undefined)
[latest-25016]2025-02-06T00:58:15.296Z <HassController:INFO> HassController#hass: sending payload for power_switch.on on Switch#hass>switch_plug_in_outlet_floater action: [Object]{ "type": "call_service", "service_data": {  }, "domain": "homeassistant", "service": "turn_on" }
[latest-25016]2025-02-06T00:58:15.301Z <Engine:5:Engine.js:1641> _process_reaction_queue() task returned, new status 3; task 1, history 86213
[latest-25016]2025-02-06T00:58:15.303Z <HassController:ERR> HassController#hass request 1738803495298<2/5/2025, 7:58:15 PM> (call_service) failed: [Error] WebSocket is not open: readyState 0 (CONNECTING) [-]
[latest-25016]2025-02-06T00:58:15.304Z <Engine:5:Engine.js:1688> _process_reaction_queue ending with 1 in queue; none delayed/ready; waiting
[latest-25016]2025-02-06T00:58:15.305Z <HassController:WARN> HassController#hass action power_switch.on([Object]{  }) on Switch#hass>switch_plug_in_outlet_floater failed!
[latest-25016]2025-02-06T00:58:15.306Z <HassController:INFO> Service call payload:
{"type":"call_service","service_data":{},"domain":"homeassistant","service":"turn_on","id":1738803495298}
[latest-25016]2025-02-06T00:58:15.307Z <HassController:INFO> Service data:
{}
[latest-25016]2025-02-06T00:58:15.309Z <Engine:ERR> [Engine]Engine#1 reaction rule-m6rz6ol1:S step 0 perform power_switch.on failed: [Error] WebSocket is not open: readyState 0 (CONNECTING) [-]
[latest-25016]2025-02-06T00:58:15.309Z <Engine:INFO> [Engine]Engine#1 action args: [Object]{  }
[latest-25016]2025-02-06T00:58:15.310Z <Engine:5:Engine.js:1688> _process_reaction_queue() wake-up!
[latest-25016]2025-02-06T00:58:15.311Z <Engine:5:Engine.js:1627> _process_reaction_queue() running task 1: [Object]{ "tid": 1, "id": "rule-m6rz6ol1:S", "rule": "rule-m6rz6ol1", "__reaction": [RuleReaction#rule-m6rz6ol1:S], "next_step": 1, "status": 1, "ts": 1738803495021, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 0, "history_id": 86213 }
[latest-25016]2025-02-06T00:58:15.313Z <Engine:INFO> Resuming reaction rule-m6rz6ol1<SET> (rule-m6rz6ol1:S) from step 1
[latest-25016]2025-02-06T00:58:15.313Z <Engine:INFO> rule-m6rz6ol1<SET> all actions completed.
[latest-25016]2025-02-06T00:58:15.314Z <Engine:5:Engine.js:1641> _process_reaction_queue() task returned, new status -1; task 1, history 86213
[latest-25016]2025-02-06T00:58:15.323Z <Engine:5:Engine.js:1688> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting

    After that I have several socket up and down message until 00:58:52z where it seemed to stabilised.

    Error: Hub reports it is starting but not yet ready
    at /opt/reactor/server/lib/HassController.js:1291:66
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[latest-25016]2025-02-06T00:58:30.573Z <HassController:NOTICE> HassController#hass websocket closing, 1006 
[latest-25016]2025-02-06T00:58:35.574Z <HassController:NOTICE> HassController#hass connecting to wss://192.168.2.163:8123/api/websocket
[latest-25016]2025-02-06T00:58:35.892Z <HassController:NOTICE> HassController#hass connected, starting protocol
[latest-25016]2025-02-06T00:58:35.900Z <HassController:INFO> HassController#hass successful authentication with wss://192.168.2.163:8123; fetching initial data...
[latest-25016]2025-02-06T00:58:35.908Z <HassController:INFO> HassController#hass Hass reports version "2025.1.0" location Maison timezone America/Toronto state NOT_RUNNING safe_mode false
[latest-25016]2025-02-06T00:58:35.909Z <HassController:ERR> HassController#hass failed to complete startup: [Error] Hub reports it is starting but not yet ready [-]
[latest-25016]2025-02-06T00:58:35.910Z <HassController:CRIT> Error: Hub reports it is starting but not yet ready [-]
Error: Hub reports it is starting but not yet ready
    at /opt/reactor/server/lib/HassController.js:1291:66
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[latest-25016]2025-02-06T00:58:35.912Z <HassController:NOTICE> HassController#hass websocket closing, 1006 
[latest-25016]2025-02-06T00:58:40.918Z <HassController:NOTICE> HassController#hass connecting to wss://192.168.2.163:8123/api/websocket
[latest-25016]2025-02-06T00:58:40.954Z <HassController:NOTICE> HassController#hass connected, starting protocol
[latest-25016]2025-02-06T00:58:40.959Z <HassController:INFO> HassController#hass successful authentication with wss://192.168.2.163:8123; fetching initial data...
[latest-25016]2025-02-06T00:58:40.963Z <HassController:INFO> HassController#hass Hass reports version "2025.1.0" location Maison timezone America/Toronto state NOT_RUNNING safe_mode false
[latest-25016]2025-02-06T00:58:40.964Z <HassController:ERR> HassController#hass failed to complete startup: [Error] Hub reports it is starting but not yet ready [-]
[latest-25016]2025-02-06T00:58:40.964Z <HassController:CRIT> Error: Hub reports it is starting but not yet ready [-]
Error: Hub reports it is starting but not yet ready
    at /opt/reactor/server/lib/HassController.js:1291:66
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[latest-25016]2025-02-06T00:58:40.966Z <HassController:NOTICE> HassController#hass websocket closing, 1006 
[latest-25016]2025-02-06T00:58:45.969Z <HassController:NOTICE> HassController#hass connecting to wss://192.168.2.163:8123/api/websocket
[latest-25016]2025-02-06T00:58:46.716Z <HassController:NOTICE> HassController#hass connected, starting protocol
[latest-25016]2025-02-06T00:58:46.735Z <HassController:INFO> HassController#hass successful authentication with wss://192.168.2.163:8123; fetching initial data...
[latest-25016]2025-02-06T00:58:46.747Z <HassController:INFO> HassController#hass Hass reports version "2025.1.0" location Maison timezone America/Toronto state NOT_RUNNING safe_mode false
[latest-25016]2025-02-06T00:58:46.748Z <HassController:ERR> HassController#hass failed to complete startup: [Error] Hub reports it is starting but not yet ready [-]
[latest-25016]2025-02-06T00:58:46.748Z <HassController:CRIT> Error: Hub reports it is starting but not yet ready [-]
Error: Hub reports it is starting but not yet ready
    at /opt/reactor/server/lib/HassController.js:1291:66
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[latest-25016]2025-02-06T00:58:46.750Z <HassController:NOTICE> HassController#hass websocket closing, 1006 
[latest-25016]2025-02-06T00:58:51.756Z <HassController:NOTICE> HassController#hass connecting to wss://192.168.2.163:8123/api/websocket
[latest-25016]2025-02-06T00:58:51.898Z <HassController:NOTICE> HassController#hass connected, starting protocol
[latest-25016]2025-02-06T00:58:51.930Z <HassController:INFO> HassController#hass successful authentication with wss://192.168.2.163:8123; fetching initial data...
[latest-25016]2025-02-06T00:58:52.055Z <HassController:INFO> HassController#hass Hass reports version "2025.1.0" location Maison timezone America/Toronto state RUNNING safe_mode false
[latest-25016]2025-02-06T00:58:52.935Z <Rule:5:Rule.js:366> Rule#rule-grpol1jp4l Summer Day At Home requesting eval; entity-changed from Entity#hass>input_select_house_mode
[latest-25016]2025-02-06T00:58:52.936Z <Rule:5:Rule.js:366> Rule#rule-grp15p0yq5k Summer Evening At Home requesting eval; entity-changed from Entity#hass>input_select_house_mode
[latest-25016]2025-02-06T00:58:52.936Z <Rule:5:Rule.js:366> Rule#rule-grpol67dc7 Summer Night At Home requesting eval; entity-chang
    Multi-System Reactor
  • [SOLVED]Hass websocket falsely reporting ready on boot??
    V vezinpi

    Well, I just added wait_all_controllers: true and got the following:

    81d0112f-8abe-48d4-aa9d-45dfb5898264-Screenshot 2025-02-05 194050.png

    Commented out the wait_all_controllers: true and change the startup_wait from 60000 to 120000. Will be re-testing my test case shortly.

    Standby

    Multi-System Reactor
  • [SOLVED]Hass websocket falsely reporting ready on boot??
    V vezinpi

    Hi, @toggledbits

    I just noticed that following a reboot of my raspberry pi, some of the rules, that I was expecting to recover, are not catching up following a reboot. I have made a simple test rule (rule-m6rz6ol1) with only "after Date/time" as trigger and "turn on a lamp" as a set reaction. All my infrastructure is on the same board so Reactor, Hass, Zwavejs, ... are all rebooting.

    Here is the sequence of the test case (All time converted to Zulu to match logs):

    • Rule "after Date/Time" set to 14:05:00z
    • Shutdown on Raspberry Pi at 14:04:00z
    • Power back up at 14:08:00z
    • Rule overview shows true as of 14:08:14z waiting for 00:00:00 in GUI

    From the log I can see that MSR is picking up the rule and knows that the state of the rule has changed from false to true and tries to send the update to HASS but failed with websocket error.

    Here is what I see from the log:

    • 14:04:04z shutdown complete
    • 14:08:08z Power up
    • 14:08:13.111z websocket connection
    • 14:08:15:323z Reaction to the light failed, Websocket not opened
    • After there is a series of websocket connection attempt until 14:08:51z where it seemed to be really ready.

    Back in 2021 we had a discussion (https://smarthome.community/topic/700/solved-start-up?_=1738766986566) and you proposed to add a startup_delay:xxxx and startup_wait:xxxx parameter in the engine section of "reactor.yaml". When I try the startup_delay (this used to be a hard delay), the engine failed to start (I think). I then try the startup_wait:xxxx without any success. Since it wait for the connection status to be up to cancel the delay, it does not do anyting since Hass is reporting the socket up without really being up ( I think...).

    Questions:

    • Did I figured it all wrong?
    • should the startup_delay:xxxxx have worked?
    • Any ideas?

    Here is the log:

    OK now I am stuck. I did add the log but when I submit the editor complained saying that I am limited to 32767 characters. The log from the shutdown to the time the websocket is stable is about 300000 character long. What are my options?

    Multi-System Reactor
  • [Solved] Local expression evaluation
    V vezinpi

    @tunnus @toggledbits Thank you both for all your explanation.

    Much appreciated.

    Multi-System Reactor
  • [Solved] Local expression evaluation
    V vezinpi

    @toggledbits said in [Solved] Local expression evaluation:

    Also: it's not correct to compare a time string to another time string. Basically, everything about this expression won't work.

    I understand that, as you explained, expression cannot auto evaluate based on time. However when manually trigger, the expression do work as intended with time and all.

    I Know that your not in the business of teaching others how to code but does it means that, inside an expression, we should never attempt to perform actions based on time like:

    if strftime("%H:%M:%S") < "08:00:00" then
    ...

    Thanks

    Multi-System Reactor
  • [Solved] Local expression evaluation
    V vezinpi

    Roger that. Up to this point I was really thinking that It would work like Date/Time.

    Thank you.

    Multi-System Reactor
  • [Solved] Local expression evaluation
    V vezinpi

    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
  • Reactor-Editor / Reactor-ui-Status Errors
    V vezinpi

    Thanks for the update and sorry about the timeout issue, I was not aware of it.

    Here is the requested rule:

    ac60b96d-b639-4baf-95d4-853332bc62be-image.png

    10cbe2e7-0af9-4ede-afa8-060b0f99befe-image.png

    f9282548-9462-4c52-a125-dc57fc9c3fa6-image.png

    Multi-System Reactor
  • Reactor-Editor / Reactor-ui-Status Errors
    V vezinpi

    @toggledbits Sorry about that. I wrote a second post following that one but probably never hit submit. My bad

    MSR Version 24302

    I simply push the play button for the "Set reaction" of a rule. The action performed as expected even with the error message. (since this happened yesterday, I am just re-typing the error from the screen capture for easy reading)

    EDIT 1: I noticed that the error message was showing 15 second after I push the play button. Since I have a delay in the "Set reaction", I try to remove it and this error is gone. Somehow the delay I am using prior to the "Entity Action" is causing this timeout error.

    Error: Command timeout (195 start_reaction) at _ClientAPI._commandTimeout (http://192.168.2.163:8111/client/clientAPI.js:552:136)

    Screenshot 2024-12-29 231851.png

    Here is a different one, more inline with this post, that I just did by editing a "Date/Time" trigger from 8:05h to 8:10h and save. The error message occured when I pushed the save button. The action (save) actually work despite the error message.

    TypeError: Cannot read properties of undefined (reading 'getEditor')
    at RuleEditor.makeExprMenu (http://192.168.2.163:8111/reactor/en-US/lib/js/rule-editor.js:1788:86)
    at Object.handler (http://192.168.2.163:8111/reactor/en-US/lib/js/rule-editor.js:2174:54)
    at http://192.168.2.163:8111/client/MessageBus.js:49:44
    at Array.forEach (<anonymous>)
    at MessageBus._sendToBus (http://192.168.2.163:8111/client/MessageBus.js:46:54)
    at MessageBus.send (http://192.168.2.163:8111/client/MessageBus.js:57:44)
    at ExpressionEditor.publish (http://192.168.2.163:8111/client/Observable.js:51:37)
    at ExpressionEditor.notifySaved (http://192.168.2.163:8111/reactor/en-US/lib/js/ee.js:82:14)
    at ExpressionEditor.notifySaved (http://192.168.2.163:8111/reactor/en-US/lib/js/expression-editor.js:47:15)
    at http://192.168.2.163:8111/reactor/en-US/lib/js/reactor-ui-rules.js:1459:28

    c362f2b0-9df3-4d0f-b20f-7c871a930c43-Screenshot 2024-12-30 130650.png

    Multi-System Reactor
  • [Solved] Error dialog running reaction in build 24302
    V vezinpi

    Not sure that it is the same issue but just got this on built 24302 when running a reaction for testing purpose. Despite the error message, the reaction ran properly.

    Error: Command timeout (195 start_reaction)
    at _ClientAPI._commandTimeout (http://192.168.2.163:8111/client/ClientAPI.js:552:136)

    1a3422eb-d760-4609-a740-a40d04a6bab2-Screenshot 2024-12-29 231851.png

    Multi-System Reactor
  • Reactor-Editor / Reactor-ui-Status Errors
    V vezinpi

    I do not think that this issue is limited to MAC computers. I also have seen similar errors with Chrome from a PC running Win 11.

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