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

apocalypsehobby

@apocalypsehobby
Struggling to setup my first Tasmota device and MQTT
cw-kidC
Topic thumbnail image
Multi-System Reactor
Raspberry Pi 4 dual RAM variant introduced to mitigate RAM price increases
toggledbitsT
Article here that may be of interest to some: https://www.cnx-software.com/2026/02/05/raspberry-pi-4-dual-ram-variant-introduced-to-mitigate-ram-price-increases-and-supply-challenges/
SBC
Existing Rule stopped working HTTP command fetching IP address from website
cw-kidC
Topic thumbnail image
Multi-System Reactor
Condition for trend
T
Topic thumbnail image
Multi-System Reactor
Set reaction triggering wrong z-wave device
T
Topic thumbnail image
Multi-System Reactor
Can you run MSR on Home Assistant OS ?
cw-kidC
Looking at using Home Assistant for the first time, either on a Home Assistant Green, their own hardware or buying a cheap second hand mini PC. Sounds like Home Assistant OS is linux based using Docker for HA etc. Would I also be able to install things like MSR as well on their OS ? On the same box? Thanks.
Multi-System Reactor
RPi Alternative: Orange Pi 4 LTS (3GB RAM/16GB eMMC)
toggledbitsT
The last of four boards I'm trying in this batch is the Orange Pi 4 LTS. I purchased a 3GB RAM + 16GB eMMC model from Amazon for $83, making it the most costly of the four boards tried, but still well under my US$100 limit. This board is powered by a Rockchip RK3399-T processor, ARM-compatible with dual Cortex-A72 cores and quad Cortex-A53 cores at 1.6Ghz (1.8Ghz for the 4GB model); compare this to the RPi 3B+ with four Cortex-A53 and the RPi 4B with four Cortex-A72, this board is a hybrid that I would expect to stand in the performance middle between the two RPi models. It's available in 3GB and 4GB DDR4 RAM configurations, with and without 16GB eMMC storage. It has a MicroSDHC slot, gigabit Ethernet, WiFi and BT, two USB 2.0 type A ports, one USB 3.0 type C port, a mini PCIe ribbon-cable connector (requires add-on board for standard connector), two each RPi-compatible camera and LCD ports, HDMI type A, and can be powered (5VDC/3A) via USB-C or DC type C (3.8mm OD/1.1mm ID) jack (center-positive), an odd and perhaps unwelcome departure from the more common type A (5.5mm/2.1mm). A serial port for console/debug can be connected by using a (not included) USB-TTL adapter (3.3V) via pin headers like the Orange Pi Zero 2. The included dual-band antenna connects via U.FL connector to the board, so it's easy substituting for another if you prefer. The manufacturer recommends use of a heat sink (which was included in the box). A metal cooling case is also offered by the manufacturer (a bundle with the metal case and a power supply is sold on Amazon for $90 as of this writing). The Orange Pi 4 LTS is somewhat longer than the RPi 4B, and although the boards are the same width, the mounting hole placement is different both in length and (oddly) width. Between this and the differences in connector locations, neither board is a drop-in replacecment for the other and their respective cases are not interchangeable. The 26-pin header is a subset of the RPi 4B's 40-pin header, so some HATs for the RPi may work (although the mounting hole differences will make securing them "interesting"), and some HATs will surely not. Models with eMMC storage have an OS installed and boot immediately with SSH daemon running and ready for login. Mine was running Debian Bullseye, which would probably be fine for most users. It had clearly been on there a while, because it needed a lot of updates, but it's a current distro, so you're running out of the box with something that will last. A different OS can be installed by downloading an image (once again I chose Ubuntu Jammy) and writing it to a MicroSD card, then booting the system from the SD card. You can either leave the system in that state (running the OS from the SD card), or copy the OS from the SD card to the eMMC. The latter is done by a script; documentation for the process is best described in the downloadable PDF User Manual. This took about 10 minutes and went smoothly, and I was able to boot the system without the SD card after the process completed. I have lingering questions around the value of the eMMC storage. It's definitely faster than using MicroSD or USB-based storage (I got 311MB/s average on a 4GB write, compared to MicroSD performance around 15MB/s), but it would take a long-term test of this product to determine if the on-board eMMC option has the stamina to take the write counts typical of Linux systems, and if its wear-leveling and error correction are sufficient to assure a long, error-free life. Given the high premium apparently being paid for including eMMC on the board, it should be fast and durable, but only time and experience (perhaps painful) would tell the latter. A careful configuration with other Flash-friendly filesystems could be used to reduce wear, but this is an advanced configuration/cookbook topic and beyond the scope of this writing. This question is also not unique to eMMC — MicroSD cards are also known to fail with high write cycles, so the use of a "high endurance" product is recommended for any and all systems using MicroSD as primary storage. The board has Mini PCIe capability, and that may be a storage alternative, but read on... Also bear in mind that the eMMC storage is fixed-size forever; it cannot be expanded, and 16GB can run out pretty quickly these days. Users of MicroSD cards for primary storage can upgrade to bigger cards, but when users of eMMC primary storage outgrow it, the only choice is to add a MicroSD card or other "external" storage to the system, move part of the filesystem to it, and then manage both storage devices and deal with the limitations and risks of both. As I mentioned with the Orange Pi Zero 2, if you are going to use this board as a home automation controller/gateway or similar role, it should (IMO) have a battery-backed real time clock (RTC), and Orange Pi offers an add-on module that connects directly to the 26-pin header on the board. An available expansion board provides a standard Mini PCIe interface and SIM card slot (hmm...), but it connects to the main board via a short ribbon cable, and its mounting holes have no complement on the main board, so it seems like it would be a fragile dangly thing that's a nuisance to deal with. I want to like this board more, and it's very capable, but I'm concerned about value. The limited options for eMMC (16GB or none), the question mark of the eMMC's longevity vs cost, the strange DC power connector choice, the lack of 40-pin GPIO on a full-size (plus) board, the inconsistent hole placement, and the fragile Mini PCIe arrangement, are all "cons" that devalue this board in my view. The price point is clearly driven by the additional capabilities of the board (camera support, ports, six core CPU, extra RAM, on-board eMMC storage), but unfortunately, a great many of these features may not be useful for home automation, and therefore potentially a waste of money. In terms of overall value, I still believe the Libre "Le Potato" seems a better choice to me, and the Orange Pi Zero 2 (very) a close second, but I'll admit I'm focused on a particular application and your needs may be better suited to what this board offers than mine. Passmark Results: OrangePi 4 LTS Cortex-A72 (aarch64) 6 cores @ 1200 MHz | 2.9 GiB RAM Number of Processes: 6 | Test Iterations: 1 | Test Duration: Medium -------------------------------------------------------------------------- CPU Mark: 583 Integer Math 12037 Million Operations/s Floating Point Math 2542 Million Operations/s Prime Numbers 4.5 Million Primes/s Sorting 3141 Thousand Strings/s Encryption 153 MB/s Compression 4049 KB/s CPU Single Threaded 154 Million Operations/s Physics 80.5 Frames/s Extended Instructions (NEON) 244 Million Matrices/s Memory Mark: 498 Database Operations 551 Thousand Operations/s Memory Read Cached 2524 MB/s Memory Read Uncached 2602 MB/s Memory Write 3182 MB/s Available RAM 1947 Megabytes Memory Latency 119 Nanoseconds Memory Threaded 6243 MB/s --------------- eMMC storage write 311MB/s average for 4GB; MicroSD (Samsung 32GB class 10) storage write 15MB/s.
SBC
RPi Alternative: Orange Pi Zero 2 (1GB)
toggledbitsT
Topic thumbnail image
SBC
RPi Alternative: Libre Computer AML-S905X-CC "Le Potato" (2GB RAM)
toggledbitsT
With Raspberry Pi boards continuing to be relatively scarce, I've been trying a few alternatives to see what may be usable and good. I had previously written about the Jetson Nano 2GB, which is great, but a little pricey, so I'm trying to find sub-US$100 boards that will run Reactor. I've got four that I'm trying now, but one in particular goes right to work in the most predictable way and seems worth a mention immediately: the Libre Computer Board AML-S905X-CC 2GB (known as "Le Potato"). The form factor is very similar to that of the Raspberry Pi 3 B+, and has comparable CPU (ARM Cortex-A53, quad 64-bit cores at 1.5+GHz -- slightly higher clock speed). It's US$35 on Amazon and LoverPi in the (recommended) 2GB configuration, and easy to get. Startup is like RPi: download one of the available OS images (Ubuntu, Raspbian, Debian, ARMbian, etc.) from their site and write the image to a MicroSD card, insert into slot, power up, and off you go. I tried the Ubuntu 22.04 image first and it comes right up. No problem getting nodejs 18.12.1 installed and running (with Reactor). No WiFi on board, but I don't see that as a minus for use as a controller/hub (which should be hard-wired, IMO). The 40-pin GPIO connector is compatible with typical RPi HATs (PoE, breakouts, etc.). There is an available eMMC (solid state storage) module to use instead of MicroSD, which I would recommend for long-term use. It runs US$25 for 32GB (64GB and 128GB available). The module is scarcely larger than the chip it carries, and has the smallest board-to-board connector I've ever seen. Next up: ESPRESSObin 2GB (spoiler: it's... technical...)
SBC
HA and AI
CatmanV2C
Having hours of (actually quite fun) interaction with AI (Chat GPT) making up dashboards and sensors for HA. It's OK (well it's better than I am!) but it makes soooo many mistakes. Gets there in the end though, if you've half a clue (which I do half the time) C
Home Assistant
How to upgrade from an old version of MSR?
cw-kidC
Hello I haven't updated my installation of MSR in a very long time. Its a bare metal Linux install currently on version 24366-3de60836 I see the latest version is now latest-26011-c621bbc7 I assume I cannot just jump from a very old version to the latest version? Or can I? Thanks
Multi-System Reactor
This trigger no longer working - complaining about the operator needing changing
cw-kidC
Topic thumbnail image
Multi-System Reactor
Self test
CatmanV2C
Having been messing around with some stuff I worked a way to self trigger some tests that I wanted to do on the HA <> MSR integration This got me wondering if there's an entity that changes state / is exposed when a configured controller goes off line? I can't see one but thought it might be hidden or something? Cheers C
Multi-System Reactor
Access control - allowing anonymous user to dashboard
tunnusT
Using build 25328 and having the following users.yaml configuration: users: # This section defines your valid users. admin: ******* groups: # This section defines your user groups. Optionally, it defines application # and API access restrictions (ACLs) for the group. Users may belong to # more than one group. Again, no required or special groups here. admin_group: users: - admin applications: true # special form allows access to ALL applications guests: users: "*" applications: - dashboard api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin_group allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true session: timeout: 7200 # (seconds) rolling: true # activity extends timeout when true # If log_acls is true, the selected ACL for every API access is logged. log_acls: true # If debug_acls is true, even more information about ACL selection is logged. debug_acls: true My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
Multi-System Reactor
VEC Virtual Switch Auto Off
S
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules. I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds). Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off? With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches. Thanks Reactor (Multi-hub) latest-26011-c621bbc7 VirtualEntityController v25356 Synology Docker
Multi-System Reactor
Upcoming Storage Change -- Got Back-ups?
toggledbitsT
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future. In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level. Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way. I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption. A few other things to know: If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc. Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy). The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON. You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach). The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case. This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change. This thread is open for any questions or concerns.
Multi-System Reactor
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
Multi-System Reactor
About
Posts
24
Topics
4
Shares
0
Groups
0
Followers
0
Following
1

Posts

Recent Best Controversial
  • MSR's "rgb_color.set" isn't correctly sending RGB values to bulb in Home Assistant
    A apocalypsehobby

    Good call

    From MSR's reactor.log file:

    [stable-23242]2024-03-10T21:17:49.485Z <HassController:INFO> HassController#hass action rgb_color.set([Object]{ "value": "75,0,255" }) on Light#hass>light_garage_light_l succeeded

    I need to grab logs from HA as well

    Also - I noticed that when I save the rule in MSR, it doesn't save everything. Instead of saving as '75, 0, 255' it just saves as '75'.
    f16d6c16-f48e-4ee2-9c58-cde903f9732a-image.png

    Multi-System Reactor
  • MSR's "rgb_color.set" isn't correctly sending RGB values to bulb in Home Assistant
    A apocalypsehobby

    Hey crew, I'm trying to use MSR to control the RGB values of a Z-Wave bulb in Home Assistant.

    Problem I'm running into - I would like to use 'rgb_color.set' to control this, but it doesn't work, instead it always passes the values '255,255,255' to HA no matter what values I enter within MSR.

    More notes and examples below - I'm wondering if this is a formatting issue that I'm missing? Thanks for any help!

    NOTES FROM TROUBLESHOOTING:

    • 'rgb_color.set_rgb' works successfully, which seems strange. You'd think they would both be affected
    • I've tried a couple different formats, like adding quotes, adding/removing spaces between the RGB values, nothing has fixed it.

    EXAMPLES:
    When I use 'rgb_color.set_rgb', the values successfully carry over to Home Assistant:
    f0f4befc-a642-428e-8923-e5f856ca7e2b-image.png 0af0a4f8-50b9-4100-b1e8-52a0de4cbcbb-image.png

    But when I use 'rgb_color.set', the values DO NOT successfully carry over to Home Assistant:

    9e2d7004-8085-4b70-bb3e-45614b7260a0-image.png 0d630228-c74b-4db8-89bd-2572a08608a3-image.png

    DETAILS:

    • Bulb is LZW42 by Inovelli
    • MSR version: stable-23242-5ee8e1d4

    HA DETAILS

    • Core 2024.2.5
    • Supervisor 2024.02.1
    • Operating System 12.0
    Multi-System Reactor
  • Adding remotes, scene controllers as entities to MSR
    A apocalypsehobby

    @toggledbits Thank you for helping, and that's more than fair.

    I was pressing a button on the remote while viewing the Entity section of MSR, and the virtual device showed no change (the values stayed at "null"). I was expecting them to report on/off and to report the time change.

    For others' reference, it is now working with the following code:

          event_targets: 
        "RGBG-Remote-Button-1": 
          name: "RGBG Remote Button 1"
          capabilities: 
            - button
          events: 
            - event: 
                event_type: zha_event
                data: 
                  unique_id: "60:a4:23:ff:fe:65:a3:fb:1:0x0006"
              response: 
                button.since: 
                  expr: time()
                button.state: 
                  from: event.data.command
                  map: 
                    "on": true
                    "off": false

    Same goes for buttons 2-5, just tweak the value of "unique_id". Button 1 it ends with "1:0x0006" and button 2 would end with "2:0x0006", etc.

    A caveat to this device is the on/off buttons at the very top send the same signal to HA as the "device 1 on/off" buttons (1:0x0006).

    Here's a link to the device: https://rgbgenie.com/?product=rgbgenie-5-zone-remote-and-dimmer-zigbee

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

    Hey friends - I'm trying this again with another remote, this time the ZB-5001 from RGB Genie.

    It's not working yet, but I feel like I'm close. The device is successfully populating into MSR as an Entity, but when I press a button on the remote it does not report any changes to MSR.

    Could you help me check my work?

    DATA FROM HASSIO_EVENTS.LOG

    • "endpoint_id" tells which button has been pressed (1-5)
    • "cluster_id" seems to always stay at 6
    • "command" shows whether you've pressed the "on" or "off" side of buttons 1-5
    zha_event {
	"id": 1676585189844,
	"type": "event",
	"event": {
		"event_type": "zha_event",
		"data": {
			"device_ieee": "60:a4:23:ff:fe:65:a3:fb",
			"unique_id": "60:a4:23:ff:fe:65:a3:fb:2:0x0006",
			"device_id": "516aaf4459a4f4f319a178de36a28dfd",
			"endpoint_id": 1,
			"cluster_id": 6,
			"command": "on",
			"args": [],
			"params": {}
		},
		"origin": "LOCAL",
		"time_fired": "2023-02-16T22:07:24.518489+00:00",
		"context": {
			"id": "01GSE495V6J686X0RGXYZ046CG",
			"parent_id": null,
			"user_id": null
		}
	}

    MY BEST ATTEMPT AT THE CODE FOR REACTOR.YAML

          event_targets: 
        "RGBG-Remote-Button-1": 
          name: "RGBG Remote Button 1"
          capabilities: 
            - button
          events: 
            - event: 
                event_type: zha_event
                data: 
                  device_id: "516aaf4459a4f4f319a178de36a28dfd"
                  endpoint_id: "1"
              response: 
                button.since: 
                  from: event.data.time_fired
                button.state: 
                  from: event.data.command
                  map: 
                    on: on
                    off: off
    Multi-System Reactor
  • Adding remotes, scene controllers as entities to MSR
    A apocalypsehobby

    @toggledbits wow, thank you.

    I've successfully added the Hank devices to the reactor.yaml file, along with a couple other remotes. Here are my notes for anyone else on this endeavor.

    • Hank HKZW-SCN04 has 4 buttons, and from my tests they do not support 2x or 3x clicks/presses.

    • Minoston MR40Z V1.0 has 4 buttons, and supports all of the presses that you mapped.

    • Zooz ZEN34 Ver. 1.0 has 2 buttons and supports all the presses that you mapped PLUS it has 4x and 5x presses as well.

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

    @christian_fabre said in Adding remotes, scene controllers as entities to MSR:

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

    @christian_fabre Do you mind sharing the code you used? I have two of the HANK SCN04 as well, and am trying to do the same thing

    Multi-System Reactor
  • MSR actions aren't running anymore-- can't find what's broken
    A apocalypsehobby

    Of course, that fixed it. Thank you both!

    Multi-System Reactor
  • MSR actions aren't running anymore-- can't find what's broken
    A apocalypsehobby

    @sweetgenius yeah I should— I can probably do that tomorrow.

    Multi-System Reactor
  • MSR actions aren't running anymore-- can't find what's broken
    A apocalypsehobby

    Hey crew,
    I'm running into an issue where MSR's reactions aren't successfully running, and I can't figure out what's gone wrong.

    Backstory-- we had a big thunderstorm roll through the other day, we lost internet and the storm got bad so I unplugged most items in my homelab, including the Pi that's running MSR.

    Now that everything is powered back up, the reactions aren't running correctly. Most of my MSR automations are to use motion sensors to turn lights on/off, and I immediately noticed that even when a motion sensor is tripped, the light doesn't turn on like it's supposed to.

    I've tested a bunch of things to see what's broken, here's what I've observed:
    -I can successfully flip lights on/off manually within Vera
    -I can successfully flip lights on/off manually within MSR's Entities section
    -the motion motion sensors are correctly reporting to Vera and MSR (I can see when they're sensing motion)
    -the rules within MSR are working correctly, I can see when they flip to 'true' when I walk by a motion sensor
    -I can successfully run the Reaction within MSR (by hitting the 'play' button)

    But for whatever reason, when everything needs to work together, it doesn't successfully run the action. IE: the motion sensor trips, reports it to MSR, I can see MSR going "true" but the light does not turn on. Open to any suggestions, thank you!

    SYSTEM
    Vera has all my devices
    MSR is running bare metal on Rpi "Reactor (Multi-hub) stable-22004-6d6c6b7"

    Multi-System Reactor
  • Who are my Home Assistant + ZWave-JS users?
    A apocalypsehobby

    @vezinpi said in Who are my Home Assistant + ZWave-JS users?:

    I don't, but I could if that's the way you want to communicate.

    Same

    Multi-System Reactor zwavejs
  • [SOLVED] Trying to nest logic within Expression
    A apocalypsehobby

    @toggledbits & @tunnus thank you both, your suggestions both worked beautifully. I especially like the spacing & newlines... much clearer

    Pat, I will say on a side note, I thought the transition from Vera/Reactor to HA/MSR would take FOREVER but it's been moving along pretty quickly so far, partially due to the Import tool. Thanks for making that. I still have a long way to go, but I'm making good progress.

    Multi-System Reactor expressions solved
  • [SOLVED] Trying to nest logic within Expression
    A apocalypsehobby

    I'm working on moving from Reactor to MSR, but I'm having a hard time converting this expression.

    (For context, this expression is a part of my thermostat automation, and is designed to convert the outdoor temperature into a standard value from 1-6, which in turn tells the thermostat if we should be heating or cooling and to what degree)

    Within Vera, this is my expression that's working perfectly:

    if(TodayAvg<=33, 1, if(TodayAvg>33 and TodayAvg<=55, 2, if(TodayAvg>55 and TodayAvg<=65, 3, if(TodayAvg>65 and TodayAvg<=74, 4, if(TodayAvg>74 and TodayAvg<=80, 5, if(TodayAvg>80, 6, null))))))

    I've successfully converted the first piece of that expression within MSR, with both of these configurations running successfully:

    if TodayAvg <= 33 then 1 endif

    TodayAvg <= 33 ? 1 : null

    But as soon as I try to nest the logic, it breaks. (This code is not successful)

    if TodayAvg <= 33 then 1 else if TodayAvg > 33 and TodayAvg <= 55 then 2 endif

    Would love some advice on how to successfully convert this into a format that MSR accepts.

    Thanks all!

    Multi-System Reactor expressions solved
  • Who are my Home Assistant + ZWave-JS users?
    A apocalypsehobby

    Sign me up 👍

    Multi-System Reactor zwavejs
  • Trouble connecting Vera to MSR
    A apocalypsehobby

    I just let it run with the 14.17

    Multi-System Reactor
  • Trouble connecting Vera to MSR
    A apocalypsehobby

    @toggledbits Oh jeez, I followed the wrong set of instructions from the get-go. When you asked about the install script, I retraced my steps and realized what happened.

    I followed the "Linux (various) Bare Metal" instructions because I did not read that the 4B instructions also worked for the 3B+.

    So I just started fresh and followed the correct instructions, and everything seems to be working. Thank you for your help!

    Multi-System Reactor
  • Trouble connecting Vera to MSR
    A apocalypsehobby

    @toggledbits Sorry, I should have been more specific, it’s running Raspberry Pi OS Lite. Are you saying it should be the regular Raspberry Pi OS?

    Multi-System Reactor
  • Trouble connecting Vera to MSR
    A apocalypsehobby

    @toggledbits
    Vera Firmware: 1.7.5186 (7.31)
    Pi: Raspberry Pi 3 Model B Plus Rev 1.3, and the Debian version is 10.10

    The response was immediate from the web browser, and from when I used wget within the Pi.

    Multi-System Reactor
  • Trouble connecting Vera to MSR
    A apocalypsehobby

    @toggledbits A ton 😕

    pi@MSR-raspberrypi:~/reactor $ node app.js
basedir /home/pi/reactor
confdir /home/pi/reactor/config
datadir /home/pi/reactor/storage
logsdir /home/pi/reactor/logs
plugindir /home/pi/reactor/ext
module.paths [
  '/home/pi/reactor/node_modules',
  '/home/pi/node_modules',
  '/home/node_modules',
  '/node_modules'
]
NODE_PATH undefined
2021-09-25T18:29:17.047Z <app:null> Reactor "1.0.1-21243-83a87ba" starting on v14.17.6
2021-09-25T18:29:17.051Z <app:INFO> Process ID 3194; platform linux/arm #1449 SMP Wed Aug 25 15:00:01 BST 2021; locale [ "en-GB", "UTF-8" ]
2021-09-25T18:29:17.053Z <app:INFO> Basedir /home/pi/reactor; data in /home/pi/reactor/storage
2021-09-25T18:29:17.054Z <app:INFO> NODE_PATH (undefined); module paths [ "/home/pi/reactor/node_modules", "/home/pi/node_modules", "/home/node_modules", "/node_modules" ]
2021-09-25T18:29:17.245Z <Plugin:null> Module Plugin v21173
2021-09-25T18:29:17.270Z <default:INFO> Module Entity v21177
2021-09-25T18:29:17.280Z <Controller:null> Module Controller v21226
2021-09-25T18:29:17.281Z <default:null> Module Structure v21229
2021-09-25T18:29:17.303Z <default:null> Module Ruleset v21096
2021-09-25T18:29:17.304Z <default:null> Module Rulesets v21096
2021-09-25T18:29:17.373Z <default:null> Module Rule v21224
2021-09-25T18:29:17.388Z <default:null> Module Engine v21213
2021-09-25T18:29:17.390Z <default:null> Module httpapi v21238
2021-09-25T18:29:17.396Z <default:null> Module httpproxy v21054
2021-09-25T18:29:17.443Z <default:null> Module wsapi v21196
2021-09-25T18:29:17.447Z <app:NOTICE> Starting Structure...
2021-09-25T18:29:17.455Z <default:NOTICE> Structure#1 plugin ID influx disabled; skipping
2021-09-25T18:29:17.459Z <default:INFO> Structure#1 starting controller interface vera (VeraController)
2021-09-25T18:29:17.470Z <default:INFO> Structure#1 starting controller interface hass (HassController)
2021-09-25T18:29:17.473Z <default:INFO> Structure#1 starting controller interface reactor_system (SystemController)
2021-09-25T18:29:17.614Z <default:null> Module VeraController v21236
2021-09-25T18:29:17.625Z <default:null> Module HassController v21243
2021-09-25T18:29:17.630Z <default:null> Module SystemController v21102
2021-09-25T18:29:17.641Z <VeraController:NOTICE> VeraController#vera starting
2021-09-25T18:29:17.809Z <VeraController:INFO> VeraController#vera loaded mapping ver 21236 rev 1 format 1 notice
2021-09-25T18:29:17.812Z <VeraController:INFO> VeraController: deviceclass vera_system_object capability sys_system does not provide attribute state
2021-09-25T18:29:17.926Z <HassController:INFO> HassController#hass device mapping data loaded; checking...
2021-09-25T18:29:17.997Z <HassController:NOTICE> HassController#hass attempting reconnection to ws://10.0.0.108:8123/api/websocket
2021-09-25T18:29:18.002Z <HassController:NOTICE> HassController#hass connecting via WS to ws://10.0.0.108:8123/api/websocket
2021-09-25T18:29:18.018Z <default:NOTICE> Controller SystemController#reactor_system is now online.
2021-09-25T18:29:18.192Z <app:INFO> Structure running; pausing for controllers' initial ready
2021-09-25T18:29:18.261Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594557823 failed, reason: socket hang up
2021-09-25T18:29:18.285Z <HassController:NOTICE> HassController#hass connected, starting protocol
2021-09-25T18:29:18.304Z <HassController:INFO> HassController#hass successful authentication with ws://10.0.0.108:8123; fetching initial data...
2021-09-25T18:29:18.317Z <HassController:INFO> HassController#hass Hass reports version "2021.8.6" location Home timezone America/Detroit state RUNNING safe_mode false
2021-09-25T18:29:18.553Z <HassController:NOTICE> Controller HassController#hass is now online.
2021-09-25T18:29:23.290Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594563265 failed, reason: socket hang up
2021-09-25T18:29:28.312Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594568291 failed, reason: socket hang up
2021-09-25T18:29:33.339Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594573317 failed, reason: socket hang up
2021-09-25T18:29:39.363Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594579344 failed, reason: socket hang up
2021-09-25T18:29:46.392Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594586368 failed, reason: socket hang up
2021-09-25T18:29:54.420Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594594399 failed, reason: socket hang up
2021-09-25T18:30:03.448Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594603429 failed, reason: socket hang up
2021-09-25T18:30:13.468Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594613450 failed, reason: socket hang up
2021-09-25T18:30:18.265Z <app:NOTICE> Starting Reaction Engine...
2021-09-25T18:30:18.269Z <Engine:INFO> Reaction Engine starting
2021-09-25T18:30:18.273Z <Engine:INFO> Checking rule sets...
2021-09-25T18:30:18.285Z <Engine:INFO> Checking rules...
2021-09-25T18:30:18.287Z <Engine:INFO> Data check complete; no corrections.
2021-09-25T18:30:18.296Z <Engine:NOTICE> Reaction Engine running!
2021-09-25T18:30:18.297Z <app:NOTICE> Starting HTTP server and API...
2021-09-25T18:30:18.314Z <app:NOTICE> Startup complete
2021-09-25T18:30:18.323Z <app:NOTICE> HTTP API v1 21238 base URL http://10.0.0.5:8111; listening
2021-09-25T18:30:18.362Z <app:NOTICE> HTTP server running; registering proxy endpoints.
2021-09-25T18:30:18.365Z <app:NOTICE> Starting WSAPI...
2021-09-25T18:30:18.368Z <app:NOTICE> wsapi: starting version 21196
2021-09-25T18:30:18.405Z <Engine:INFO> Engine#1 master timer tick, local time "25/09/2021, 14:30:18" (TZ offset -240 mins from UTC)
2021-09-25T18:30:18.687Z <app:INFO> wsapi: connection from ::ffff:10.0.0.91
2021-09-25T18:30:24.490Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594624469 failed, reason: socket hang up
2021-09-25T18:30:36.518Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594636500 failed, reason: socket hang up
2021-09-25T18:30:49.536Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594649518 failed, reason: socket hang up
2021-09-25T18:31:03.567Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594663549 failed, reason: socket hang up
2021-09-25T18:31:18.580Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594678567 failed, reason: socket hang up
2021-09-25T18:31:34.607Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632594694590 failed, reason: socket hang up
    Multi-System Reactor
  • Trouble connecting Vera to MSR
    A apocalypsehobby

    Thank you both. @Buxton I followed these directions and commented out "auth" in both files, restarted Vera, still got the same error messages.

    What's strange is-- I took one of the request URLs (like http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632187568275) and pasted it into my laptop's web browser, and I got a huge output file. So it seems like Vera is working.

    Maybe it's a network configuration problem like you suggested, @toggledbits ? So I went to my Raspberry Pi that's running MSR, and I used wget then it successfully downloaded the output file to the pi as well. So I'm not sure why it's not working within MSR!

    Multi-System Reactor
  • Trouble connecting Vera to MSR
    A apocalypsehobby

    @toggledbits Do you mind helping me understand why the "socket hang up" & "ECONNREFUSED" messages mean that Vera is reloading a lot?

    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