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.
cw-kidC

cw-kid

@cw-kid
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
Topic thumbnail image
Multi-System Reactor
Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
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
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor
Notice to Docker + ARM Users (RPi 3/4/5 and others)
toggledbitsT
This post does not apply to users of Intel/AMD-based systems. If you are using a Reactor image tagged latest-amd64 or stable-amd64, then this post does not apply to you. It also does not apply to bare-metal installs; it's for users of docker images on ARM-based systems only (principally Raspberry Pi hosts, but could be others). After January 15, 2026, I will no longer produce the aarch64-tagged docker image for Reactor. The ARM images will be arm64 for 64-bit operating systems, and armv7l for 32-bit operating systems. For those of you running a container from the aarch64 image today, this will be a relatively simple change: you just need to switch the image used for your docker container to a differently-tagged image. If you are using docker-compose, then this is a relatively simple matter of changing the image line in your docker-compose.yaml file and then stopping (docker-compose down) and restarting (docker-compose up -d) your Reactor daemon. But there's a catch... not all of you can safely just switch from the aarch64 image to the arm64 image. And, you can't just trust the output of uname -m, for example, because this exposes the CPU architecture, but not the word size of the OS running on that CPU. For Raspberry Pi systems, the transition to 64-bit operating systems was long (starting in 2016) and not always obvious — although there was a first "official" 64-bit OS for RPis in 2020, it did not become a default recommendation in the Raspberry Pi Imager until 2021, and then that was only the default for Pi 3/4 systems with >4GB RAM; it was 2022 before it was universally recommended for all 64-bit CPUs regardless of RAM size. Depending on when you first imaged your RPi system and what default you may have been offered/chosen, you could today easily have a 64-bit CPU Raspberry Pi running a 32-bit version of the operating system. Upgrades along the way would not change this; changing it to fully 64-bit requires a full reimage of the system. To establish if your OS is 64- or 32-bit, log in to your Pi and run: sudo dpkg-architecture -q DEB_HOST_ARCH. If the response is arm64 or aarch64, then you are running a 64-bit OS and you should use the arm64-tagged image. If it's anything else, you are running a 32-bit OS, and you should use the armv7l-tagged image. pi@rpi4-1:~ $ sudo dpkg-architecture -q DEB_HOST_ARCH armhf pi@rpi4-1:~ $ uname -m aarch64 pi@rpi4-1:~ $ In the example above, the uname command reports that the CPU is 64-bit architecture (aarch64), which is true for the host on which I ran these commands, but the DEB_HOST_ARCH value is armhf, indicating a 32-bit operating system. This system has to use the armv7l-tagged image. Other systems will have their own ways of determining the word size of the running OS. Since the majority of Reactor users running ARM systems are on Raspberry Pis, I am able to supply the above instructions, but if you happen to have a different ARM system, you'll need to do some web searching to figure out how to expose that information. Or, you can just try the arm64 image, and if it doesn't start up, try the armv7l image. Remember to always back up your system before making any changes. For everyone, please make this change as soon as possible, and if you have any trouble finding a working image, please (1) go back to the current aarch64 image; and (2) let me know in this thread along with as much detail about your host system as you can offer (including the output of the dpkg-architecture command mentioned above).
Multi-System Reactor
Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
M
Hi, I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available. None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5. Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image? Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way: docker buildx build --push \ -t <localrepo>/<project>:<tag> \ --platform=linux/arm64,linux/amd64 \ --file ./apps/<project>/Dockerfile . This produces both the AMD64 and ARM64/v8 variants automatically. Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications. @toggledbits - tagging you in case you missed this. Thanks, mgvra
Multi-System Reactor
Script action and custom timers
therealdbT
Sorry to write here without trying, but I’m flying today. Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes? That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Multi-System Reactor
Help resolve change in behaviour post update
CatmanV2C
Topic thumbnail image
Multi-System Reactor
There is an alternative to homebridge-mqttthing
CrilleC
Just throwing out a general hint to the people running Homebridge and MQTT. Homebridge MQTT-Thing hasn't been updated in almost 2 years and it falls behind on compatibility with the development of Homebridge. I was looking for a replacement and found Homebridge Easy MQTT and I think it's a good replacement for MQTT-Thing. I particularly find Easy MQTT Value tranformers easier to to understand and use compared to MQTT-Thing Apply function. It took a while to migrate everything but I'm pleased and can recommend.
Software
Reactor w/HA 2025.11 error on set_datetime service call setting only time
CrilleC
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1? [latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } } [latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed! [latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320} [latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1 [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } } [latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed! [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323} [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2 [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Multi-System Reactor
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
P
Hello, I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light? Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ Please help, P.S Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Multi-System Reactor
Shelly Wall Display XL
therealdbT
I don't know if you guys are into dashboards, but I am. For a second home I tried the Shelly Wall Display 2, and while not so big, it worked well over the summer. Since we're remodeling our house, I just swapped my old Fire Tablet (with its own problems) with two new Shelly Wall Display XL. I just removed the standard firmware, and I added mine (https://github.com/dbochicchio/ShellyElevate), forked from https://github.com/RapierXbox/ShellyElevate I just managed to support buttons (this thing has 4 of them) and it's all auto-discovered by Home Assistant and accessible via Reactor. I also have a new build in the works with support for buttons inside HA. I added a bonus Javascript interface sending events (screen/screensaver status, buttons, motion) to automatically drive the dashboard (all doing in HTML+Javascript and monitoring Reactor's variable). This specifical thing excluded, go get one of them, the device has a decent CPU for HA dashboards and blends wonderfully in the decor.
Hardware
[Solved] alarm() in global expression throws error in log.
CrilleC
Topic thumbnail image
Multi-System Reactor
[Solved] Define function issue in latest-25304
CrilleC
Topic thumbnail image
Multi-System Reactor
No Upgrade Notification for Build 25308?
CatmanV2C
FWIW I'm no longer getting a notification from MSR that there's an update. Just thought I'd mention it C
Multi-System Reactor
Strange behavior in MSR latest-25304 with disabled groups in Reaction
therealdbT
Topic thumbnail image
Multi-System Reactor
Do you Matter?
akbooerA
Is anyone using the Matter protocol to connect devices?
General Discussion
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
About
Posts
829
Topics
103
Shares
0
Groups
0
Followers
1
Following
0

Posts

Recent Best Controversial

  • Has something changed with the "Changes" operator in Constraint groups ?
    cw-kidC cw-kid

    OK thanks, I think that works!

    So I have two rules now the main 1st rule that detects Motion on the IP Camera and also a Virtual Switch must be True, those are the two triggers, this is the rule with the Actions in it.

    In the Constraints I am referencing the "Rule State" of the 2nd new rule and that must be False.

    ffb990d2-5b0f-419f-88e3-4cde28ed51b0-image.png

    This is the new 2nd rule and I have just used the Triggers with the "Changes" operator.

    So if any of these devices change their state within the X number of Seconds the OR group will be True thus the 1st main rule would NOT run its Actions in that case.

    But if none of these devices have changed their state within the X number of Seconds the OR group will be False thus the 1st main rule would run its Actions.

    e972131c-82e8-44b6-819f-dfe9a217692a-image.png

    Multi-System Reactor

  • Has something changed with the "Changes" operator in Constraint groups ?
    cw-kidC cw-kid

    OK thanks for the heads up.

    So anyway to do this now ? I only want the rules Actions to run if the devices listed in the Constraints haven't changed their state within the last number of X seconds etc.

    Multi-System Reactor

  • Has something changed with the "Changes" operator in Constraint groups ?
    cw-kidC cw-kid

    Hi

    I was looking at an old rule and I wanted to edit it, to add another Constraint, however I cannot seem to do it.

    On this screen shot you can see an existing entry in the Constraints and on its pull down menu the "Changes" option is available.

    09735de3-8e92-4e12-bfa2-5191f48924a7-image.png

    However on the new line I just added I have no changes option in its pull down menu.

    d85c4067-880e-4281-a12b-dac4d316a4da-image.png

    Here is the original now locked post about this topic.

    https://smarthome.community/topic/395/contact-sensor-opened-1-minute-ago-how?_=1736354690742

    If you look on the old screen shots on that post, I was using the "changes" operator. Like this:

    a1262e01-d3fd-4723-872f-872f1f6d9899-image.png

    However today when I edited this rule the operators are showing as == and not as changes on all the entries in the Constraints area.

    Also the old entries now say -- and the value is blank. But on the new line I just added it says that is not valid, so not sure how the old lines are like that.
    a458d52d-214d-4862-a2b7-d31009f89cde-image.png

    So I am a bit confused what happened.

    Thanks

    Multi-System Reactor

  • Which user to install nodejs as ? Debian Linux
    cw-kidC cw-kid

    It seems nodesource is just out of date and does not have the latest versions of nodejs

    I tried this command instead and it still only wants to get version v20.18.1 as the latest one.

    curl -fsSL https://deb.nodesource.com/setup_current.x | -E bash -

    apt-get install -y nodejs

    And when I run a "Which node" command its put it in this directory which I don't think is ideal?

    /usr/bin/node

    So now sure now the best way to update nodejs.

    Multi-System Reactor

  • Which user to install nodejs as ? Debian Linux
    cw-kidC cw-kid

    Think I have got it working now!
    95101eda-401d-4f99-99b3-73b9a97acf55-image.png

    I ran these commands again logged in as me.

    cd /home/stuart
    pkill -QUIT node
    tar xzvf /home/stuart/reactor-latest-24302-751a06b6.tar.gz
    sudo systemctl start reactor

    cd /home/stuart/reactor
    npm i --no-save --omit dev

    Will try and figure out how to update nodejs now from 20.x to 22.x.

    Multi-System Reactor

  • Which user to install nodejs as ? Debian Linux
    cw-kidC cw-kid

    Not sure how I ended up with a reactor folder in the reactor folder. I deleted it.
    It now looks correct and I ran the commands again for the permssions.

    be37bb7d-dfb8-4b60-957d-e543e8ea78d4-image.png

    46bbf45c-a84e-42b7-b45e-fcef80a5d13b-image.png

    However every time I copy the expression file from the PC to the Linux box its 9k in file size. But when I restart MSR it changes that file to be 1k and wipes out all its contents.

    2144a076-86e5-4c08-9017-d253e9881581-image.png

    Multi-System Reactor

  • Which user to install nodejs as ? Debian Linux
    cw-kidC cw-kid

    OK I ran these commands in the home/stuart/reactor folder where the app.js file is located. That appears to have worked and changed some of the folders and files from root to my name now.

    Also after restarting MSR the expressions.json file is no longer changing from 9k to 1k in size and I can open the file from the Linux machine and see its contents are still all intact. It wasn't doing that before.

    However in the MSR GUI in Expressions its still empty.

    image.png

    88bf0fe7-c1e1-4437-a3c9-21232af71bf5-image.png

    Edit I seem to have ballsed something up, i have a path now of /home/stuart/reactor/reactor hang on let me try and fix that.

    Multi-System Reactor

  • Which user to install nodejs as ? Debian Linux
    cw-kidC cw-kid

    @toggledbits

    I used WINSCP to copy the file from my Windows PC to the Linux box.

    00936b30-dc96-4b99-b184-32534269c217-image.png

    It says rw-r--r-- next to the expressions file and has me as the owner of the file.

    29861561-54e2-4f54-93b4-d5c92e0625df-image.png

    Regarding nodejs installed via apt it says its version v20.18.1 I think version 22.x is the latest. Maybe I can upgrade it somehow later.

    Multi-System Reactor

  • Which user to install nodejs as ? Debian Linux
    cw-kidC cw-kid

    @toggledbits said in Which user to install nodejs as ? Debian Linux:

    When backing up and restoring, the entire storage folder should always go as a unit. No cherry-picking

    Understood now thanks.

    I uploaded the file to your dropbox. Cheers for the help!

    Btw I formatted everything and started again earlier, no longer using NVM to install node.js I installed it globally instead with apt via the command from this webpage here. That seems to have fixed my Node-Red service file issues anyways. Both MSR and Node-Red are auto starting at boot now.

    Multi-System Reactor

  • Which user to install nodejs as ? Debian Linux
    cw-kidC cw-kid

    @therealdb said in Which user to install nodejs as ? Debian Linux:

    Copy everything. You’ll also get states.

    I just tried this but my Global Expressions are still missing.

    Multi-System Reactor

  • Which user to install nodejs as ? Debian Linux
    cw-kidC cw-kid

    @therealdb said in Which user to install nodejs as ? Debian Linux:

    Copy everything. You’ll also get states

    I might have to try that then.

    I was just trying to get my node-red to run as a service with systemd, however its not working and I think its because I installed nodejs using NVM.

    Several pages I have read say node-red will not run as a service if you used NVM like this one here:

    "Using nvm
    nvm is a tool that can help manage Node.js installations.

    It is convenient when running Node-RED as an individual user, but it is not recommended if you want to run Node-RED as a system-level service. This is because nvm uses scripts in a user’s profile to setup its environment. When running as a service, those scripts do not get used."

    I am now thinking I might have to format the SSD and start from the beginning again and use a different method to install nodejs other than NVM.

    I think when I first setup this Debian box years ago I installed nodejs a different way as described in this article here in the section of the article titled "Installing Node.js with Apt Using a NodeSource PPA".

    Multi-System Reactor

  • Which user to install nodejs as ? Debian Linux
    cw-kidC cw-kid

    @toggledbits I have managed to get MSR up and running again as my none root username.

    I have copied the rules / rulesets / reactions back into the installation from a backup copy of all the reactor files I had on my PC. Those have now reappeared in MSR.

    I am missing my Global Expressions however. Is there a file or folder I need to copy back for those?

    Thanks.

    EDIT: I just copied over the expressions.json file from the storage folder and restarted MSR but there are still no expressions showing in MSR.

    I just copied the file over again and then looked at the file on the Linux machine and I could see stuff in there. However after restarting MSR and then looking at the file again, its seems to wipe out all the files contents and now it just has {} in the file nothing else.

    Multi-System Reactor

  • Which user to install nodejs as ? Debian Linux
    cw-kidC cw-kid

    @toggledbits said in Which user to install nodejs as ? Debian Linux:

    nvm is a per-user tool and installs node on a per-user basis. You need to run it logged in as the non-root user that will run Reactor and the other things you want to install. Be sure to install an LTS version of node, not just the highest-numbered version (e.g. nvm install --lts).

    Great thanks I will try that today. I already removed what I installed yesterday as the root user.

    Multi-System Reactor

  • Which user to install nodejs as ? Debian Linux
    cw-kidC cw-kid

    I also need to install node-red and HA-Bridge for other stuff, looks like I need nodejs installed first before I can install node-red. I use node-red to send TTS announcements to my Google Home speakers.
    e2276969-37a8-4442-ac78-8a3d0ac22930-image.png

    Multi-System Reactor

  • Which user to install nodejs as ? Debian Linux
    cw-kidC cw-kid

    Hi

    Having to rebuild my Linux Debian box as the SSD failed. And I have forgotten exactly what I did the first time to get it all setup.

    I have Debian 12 up and running on the new SSD, I only have console no Desktop GUI.

    I am trying to do the bare metal install for MSR. However I am not sure if I am meant to install nodejs whlist logged in as the root user or as the none root user with my name ?

    I used putty and connected via SSH and logged in as root and I installed nodejs but I think this was wrong as when logged in as my user name and I do a node -v command it says node is not installed or doesn't show any version number anyway.

    But when logged in as root and I do a node -v command it does show me its installed and displays the version number. maybe its a path issue for my username and he can't see node is installed?

    So now I am thinking I should of installed node whilst logged in as my user name and not as the root user.

    This is how I installed nodejs as whilst logged in as root

    ac7bf6c3-23ad-46fc-8ada-44af6704e63e-image.png

    Thanks in advance.

    Multi-System Reactor

  • Should MSR import this device type from an Ezlo controller?
    cw-kidC cw-kid

    As for your other comments Gentlemen, I don't disagree with them..

    Multi-System Reactor

  • Should MSR import this device type from an Ezlo controller?
    cw-kidC cw-kid

    @toggledbits said in Should MSR import this device type from an Ezlo controller?:

    value for subcategory that should be assigned

    Thanks, I didn't notice that. I will tell them to fix it.

    Cheers.

    Multi-System Reactor

  • Should MSR import this device type from an Ezlo controller?
    cw-kidC cw-kid

    Hi

    I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.

    They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.

    This is how that device looks in the Ezlo API.

    Devices Info:

    _id: "10696001"
    deviceTypeId: "ezlopi"
    parentDeviceId: "10696000"
    category: "level_sensor"
    subcategory: ""
    gatewayId: "457a5069"
    batteryPowered: false
    name: "Gas Sensor Digital"
    type: "sensor"
    reachable: true
    persistent: true
    serviceNotification: false
    armed: false
    roomId: ""
    security: "no"
    ready: true
    status: "idle"
    parentRoom: true
    protectConfig: "default"
    

    Items Info:

    _id: "20696001"
    deviceId: "10696001"
    hasGetter: true
    hasSetter: false
    name: "smoke_density"
    show: true
    valueType: "substance_amount"
    scale: "parts_per_million"
    value: 2.7472610473632812
    valueFormatted: "2.75"
    status: "idle"
    

    There is also an Analog Gas sensor that one did import in to MSR OK.

    68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png

    Devices Info:

    _id: "10696000"
    deviceTypeId: "ezlopi"
    parentDeviceId: "10696000"
    category: "security_sensor"
    subcategory: "gas"
    gatewayId: "457a5069"
    batteryPowered: false
    name: "Gas Sensor Analog"
    type: "sensor"
    reachable: true
    persistent: true
    serviceNotification: false
    armed: false
    roomId: ""
    security: "no"
    ready: true
    status: "idle"
    parentRoom: true
    protectConfig: "default"
    

    Items Info:

    _id: "20696000"
    deviceId: "10696000"
    hasGetter: true
    hasSetter: false
    name: "gas_alarm"
    show: true
    valueType: "token"
    enum:
    0: "no_gas"
    1: "combustible_gas_detected"
    2: "toxic_gas_detected"
    3: "unknown"
    valueFormatted: "no_gas"
    value: "no_gas"
    status: "idle"
    

    And this is how this MQ2 Gas Sensor looks like on their dashboard:

    Digital
    cb77dfa3-4af5-4d06-9635-89207a716a89-image.png

    Analog
    4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png

    They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!

    And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.

    THANKS.

    Multi-System Reactor

  • x_vera_sys.runlua with VeraScenes.lua stopped working now ?
    cw-kidC cw-kid

    That setting is in Users & Account Info - Security - Enable potentially unsafe lua code, like wget and RunLua.

    It was unchecked. I checked it again and Reloaded the engine and it started working again. I am not sure how that setting got turned OFF as I didn't do it.

    But thanks anyway for pointing me in the right direction !

    Multi-System Reactor

  • x_vera_sys.runlua with VeraScenes.lua stopped working now ?
    cw-kidC cw-kid

    I was using this method here by @therealdb to run Lua Code from MSR on my Vera Plus but it seems to have stopped working now.

    Its the one where you uploaded a file called VeraScenes.lua to your Vera hub and then you could call functions of that file to run particular bits of Lua code from an MSR reaction etc.

    9233b0a7-ec07-4ae5-99c0-cdf9c709d57c-image.png

    This was working well for a long time but I noticed today its not working now.

    Looking in the MSR log after I ran a reaction in one of my rules I just saw this:

    [latest-23338]2024-02-19T18:41:35.650Z <Engine:INFO> Enqueueing "Front Cam Motion Detection ON or OFF Old Method<RESET>" (rule-klten9w9:R)
    [latest-23338]2024-02-19T18:41:35.653Z <Engine:5:Engine.js:1466> [Engine]Engine#1 enqueued reaction rule-klten9w9:R as 22989
    [latest-23338]2024-02-19T18:41:35.654Z <Engine:5:Engine.js:1624> _process_reaction_queue() wake-up!
    [latest-23338]2024-02-19T18:41:35.655Z <Engine:5:Engine.js:1563> _process_reaction_queue() running task 22989: [Object]{ "tid": 22989, "id": "rule-klten9w9:R", "rule": "rule-klten9w9", "__reaction": [RuleReaction#rule-klten9w9:R], "next_step": 0, "status": 0, "ts": 1708368095651, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] }
    [latest-23338]2024-02-19T18:41:35.657Z <Engine:NOTICE> Starting reaction Front Cam Motion Detection ON or OFF Old Method<RESET> (rule-klten9w9:R)
    [latest-23338]2024-02-19T18:41:35.659Z <Engine:5:Engine.js:1701> [Engine]Engine#1 reaction rule-klten9w9:R step 1 perform [Object]{ "entity": "vera>system", "action": "x_vera_sys.runlua", "args": { "lua": "VeraScenes.FrontCamMotionDetectionOff()" } }
    [latest-23338]2024-02-19T18:41:35.660Z <Engine:5:Engine.js:1577> _process_reaction_queue() task returned, new status 3; task 22989, history 1629572
    [latest-23338]2024-02-19T18:41:35.663Z <Engine:5:Engine.js:1624> _process_reaction_queue ending with 1 in queue; none delayed/ready; waiting
    [latest-23338]2024-02-19T18:41:35.671Z <VeraController:ERR> [VeraController:performOnEntity] action request failed
    [latest-23338]2024-02-19T18:41:35.672Z <VeraController:CRIT> Error: Request failed: 401 Error [-]
    Error: Request failed: 401 Error
        at /home/stuart/reactor/server/lib/Controller.js:886:37
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    [latest-23338]2024-02-19T18:41:35.673Z <Engine:ERR> [Engine]Engine#1 reaction rule-klten9w9:R step 1 perform x_vera_sys.runlua failed: [Error] Request failed: 401 Error [-]
    [latest-23338]2024-02-19T18:41:35.673Z <Engine:INFO> [Engine]Engine#1 action args: [Object]{ "lua": "VeraScenes.FrontCamMotionDetectionOff()" }
    [latest-23338]2024-02-19T18:41:35.674Z <Engine:5:Engine.js:1624> _process_reaction_queue() wake-up!
    [latest-23338]2024-02-19T18:41:35.675Z <Engine:5:Engine.js:1563> _process_reaction_queue() running task 22989: [Object]{ "tid": 22989, "id": "rule-klten9w9:R", "rule": "rule-klten9w9", "__reaction": [RuleReaction#rule-klten9w9:R], "next_step": 2, "status": 1, "ts": 1708368095651, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 0, "history_id": 1629572 }
    [latest-23338]2024-02-19T18:41:35.676Z <Engine:INFO> Resuming reaction Front Cam Motion Detection ON or OFF Old Method<RESET> (rule-klten9w9:R) from step 2
    [latest-23338]2024-02-19T18:41:35.678Z <Engine:5:Engine.js:1753> [Engine]Engine#1 reaction rule-klten9w9:R step 3 notify Telegram with [Object]{ "message": "Front Garden CAM Motion Detection Off", "profile": "default" }
    [latest-23338]2024-02-19T18:41:35.685Z <Engine:INFO> Front Cam Motion Detection ON or OFF Old Method<RESET> all actions completed.
    [
    

    Was anyone else using this method to have Lua code run on your Vera hub being called via an MSR reaction ? Does it still work for you?

    Thanks

    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