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

Andr

@Andr
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
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
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
Genuinely impressed with Zigbee and HA / Reactor
CatmanV2C
Just for the record, in case anyone is following, I'm really rather impressed. I have installed one of these: https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 That's connected (physically) to the VM running on my Synology, with a 2m USB extension. The same host also runs Openluup, Mosquito, HA Bridge. Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions. Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA. https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so... https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt. And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one). A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....) Commended to the house. Thanks for everyone that got me on the right lines. C
Zigbee
About
Posts
54
Topics
12
Shares
0
Groups
0
Followers
0
Following
1

Posts

Recent Best Controversial
  • Need some advice how to fix a rule that throttles sometimes.
    A Andr

    I have got some warnings i reactor that a rule is throttled because it update rate is over 120/minute, happens now and when with a week or two in between.

    The rule monitors my house power consumption when charging my car, and if if consumption risks to kill a main fuse, it stops the charging.
    Thought I was clever when I in Constraints added that my car should be located at home and charging is active, but apparantly it wasn't clever enough...
    I had understand it that if Constraints isn't true, then the triggers isn't evaluated.

    I have a Shelly 3EM meter that measure three channel/phases and updates every second. So just for this three channels it is 180 updates per minute...
    And now when I start to take a closer look I can se in my logs that this rule is evaluated with every value change on any of the three phases...
    So ~11MB of logs only goes back in time around 16 hours...🙀

    So what is the best solution?
    Should move my "Constraints" in an new trigger group, before my existing triggers?

    Rule as it is now
    e5486a1b-7c3c-4ffc-b259-beed64948f2e-image.png

    Multi-System Reactor
  • Anyone having expience writing an ZHA quirk? Would love some pointers.
    A Andr

    Hi

    Bought a new ZB device, an EV charger.
    I was aware that there would one manufacturer specific cluster that wouldn't work out of the box, but several other clusters I hoped would work from start does not. Or at least there isn't any enteties for them.

    So I have tried to study how to write a local quirk, but it is a bit overwhelming for mt brain.
    Usually I can manage do get stuff moving with intense googling, finding guides or different solutions that I can start from, but here I find nothing that I can wrap my head around.
    My latest try was to chat with Gemini AI 😰 (programmers, rest assured that your job will be safe for the foreseeable future 😁 )

    I have gathered my device Diagnostic Info.
    I have manufacturers ZB documentation.
    A device support request is created on zigpy github (no response the last weeks)

    For now there is just two entities for my device, on/off switch and energy sensors.

    All non manufacture attributes and commands seems to be recognized in ZHA "Manage this Device"
    It would be great if I could get some entities out of them.
    For example the entity for manage charging power is expected to be presented as a dimmer slider.
    But why isn't there any entity created??

    The manufacture specific cluster is more of nice-to-have and could maybe be solved another day.

    Any help would be much appreciated. 🙏

    Home Assistant
  • Using Zooz ZEN32 Scene Controller as Trigger
    A Andr

    @Snowman
    I think my old thread could be helpful for you.
    Good luck 🙂
    Adding remotes, scene controllers as entities to MSR

    Multi-System Reactor
  • Integrate UPS with MSR
    A Andr

    @toggledbits
    No, I get how NutController works. So far at least...

    But when I got stuck several times trying to set up NUT I almost gave up. At the same time I remembered seeing some System Info in MSR and if could find data about battery level, charging and so on I would not even need the NUT Installation.
    And that would be a big bonus for me as I realize that when my NUT installation fails one day it would take me long time to figure it out and also one less process/config to handle.

    And from System Info I assume we could get info about temperatures, storage levels, fan speeds and so on?
    This could be used to send warning notifications from MSR.

    So yes, I was asking something else that come up in my head when I tried to find another way than using NUT. 🙂

    Multi-System Reactor
  • Integrate UPS with MSR
    A Andr

    @toggledbits
    Yep, that did it 😊
    Thanks once again @toggledbits

    Any thougts about getting more System Info into MSR by the way?
    This got me thinking on another possible solution. Reactor already monitors "System Memory" "Uptime" and so on, so maybe it also could monitor Powersource, Battery Level, Charging State? Then let Reactor react with its magic

    Multi-System Reactor
  • Integrate UPS with MSR
    A Andr

    @toggledbits
    So, back from vacation so time to take another shot at this 🙂

    npm list:

    C:\reactor\ext\NUTController>npm list
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
reactor-nutcontroller@0.1.22305 C:\reactor\ext\NUTController
`-- node-nut@1.0.3

    NutController config

    
  - id: nut
    implementation: NUTController
    enabled: true
    #name: Eddie UPS NUTController
    config:
      server: 22.33.44.11        # modify the IP address as needed
      port: 3493              # optional, default shown
      username: "***"      # optional, no user auth if not set
      password: "***"  # optional, must be specified if username is used
    Multi-System Reactor
  • Integrate UPS with MSR
    A Andr

    I rescued an Eaton Ellipse ups from work that come back to life with fresh batteries.👍

    Thought it would be easy to get some kind of system status or notification (from Windows) that somehow could be picked up in Reactor or at least in HA. Oh my... what a horror 😱

    After a long time following this guide I got NUT up and running on Windows @wmarcolin (Another VM is not a resonable option here)
    Monitor a UPS attached to a Windows machine

    Then I added the HA integration just to se if it worked and it actually did 😂

    So now I want over the finish line, and install NUTController in Reactor.
    It looked easy, but still, no luck.
    This got me thinking on another possible solution. Reactor already monitors "System Memory" "Uptime" and so on, so maybe it also could monitor Powersource, Battery Level, Charging State? Then let Reactor react with its magic @toggledbits ?
    For a Windows user that seems a lot easier and efficient as Windows just handle my UPS as the battery it actually is so it looked like "a laptop".

    Anyway, here is were I got stuck. No clue what more to try since the Nutserver is up and running and speaks with HA.
    reactor.log gives me two errors:

    [latest-23196]2023-07-28T19:34:28.862Z <Structure:CRIT> TypeError: self.nut.setUsername is not a function [-]
TypeError: self.nut.setUsername is not a function
    at NUTController.start_client (c:\reactor\ext\NUTController\NUTController.js:221:22)
    at NUTController.start (c:\reactor\ext\NUTController\NUTController.js:44:14)
    at Structure.start (c:\reactor\server\lib\Structure.js:362:56)
[latest-23196]2023-07-28T19:34:28.863Z <NUTController:CRIT> TypeError: Cannot read properties of undefined (reading 'end') [-]
TypeError: Cannot read properties of undefined (reading 'end')
    at Nut.close (c:\reactor\ext\NUTController\node_modules\node-nut\node-nut.js:65:15)
    at NUTController.stop (c:\reactor\ext\NUTController\NUTController.js:53:26)
    at c:\reactor\server\lib\Structure.js:366:48
[latest-23196]2023-07-28T19:34:28.864Z <Controller:NOTICE> NUTController#nut stopping

    NUTController.js:221:22 looks like this
    9b161b1b-c295-4bc0-8dcc-d3e5fd312ce5-image.png

    NUTController.js:44:14
    5dd6d92a-de87-4f01-8b8f-86ab5acdec8b-image.png

    Structure.js:362:56
    5a3aaa2e-f656-4592-a39b-0d8c74f9f091-image.png

    node-nut.js:65:15
    3be79aba-bf05-4849-96e6-5dd041c8a21c-image.png

    NUTController.js:53:26
    ebacb9f9-9cae-402d-a74c-b21d03c518ed-image.png

    Structure.js:366:48
    5a3aaa2e-f656-4592-a39b-0d8c74f9f091-image.png

    Multi-System Reactor
  • Update from 22240 to 22310 failed. New Install also failed. (Windows)
    A Andr

    @toggledbits said in Update from 22240 to 22310 failed. New Install also failed. (Windows):

    I built a bare-metal only build 22238; download that and try it. Follow the instructions exactly. Do not run npm audit on Windows, you'll break the node-windows package and the service will not be installed. You must use exactly the version specified in the installation instructions right now.

    Yes, that fixed it!
    Awesome support as always!

    Multi-System Reactor
  • Update from 22240 to 22310 failed. New Install also failed. (Windows)
    A Andr

    So it was time to update MSR (and then HA but I got stuck here)
    Can't figure out what I have missed.

    My installed version of MSR was 22240.
    Node.js is version 16.15.1

    First I tried to update, following online manual.

    ||Download a Reactor distribution ZIP from https://reactor.toggledbits.com/download/ and place it in the folder above your existing reactor (runtime) directory.
    Stop and remove any existing Reactor service:

    cd \path\to\reactor
    node tools\install_reactor_windows_service.js -u .
    Remove any existing package-lock.json file from your Reactor directory.

    Unzip the archive file and copy its contents over the contents of your existing Reactor install directory.
    From the Reactor install directory, re-install/upgrade all package dependencies:

    npm install --no-save --omit dev
    If you are running Reactor as a Windows service, repeat those steps above.

    Restart Reactor (restart the service).
    Hard-refresh all browsers that are displaying Reactor content.||

    I found several (maybe it was 3) package-lock.json and I deleted all I could search in reactor folder.
    Unzip the new version and replaced old existing files.

    Install the reactor service again by instructions.

    ||In a command prompt window, running as Administrator, change directory to your Reactor install directory.
    Install the node-windows package as a global package (it must be global or the service will not work, and you must install the specific version provided by the command below):

    npm uninstall node-windows
    npm uninstall -g node-windows
    npm install -g node-windows@1.0.0-beta.6
    npm link node-windows
    Run the script to install:

    node tools\install_reactor_windows_service.js -i .||

    So this failed. Service wont start.

    Tried again.

    Then deleted everything exept my config folder and did a new install.
    Also downloaded 22310 again, but from "latest" build instead of "stable"
    When running node app.js in command promt i get some kind of error message:

    c:\reactor>node app.js
Reactor latest-22310-a6da8097 app 22310 configuration from c:\reactor\config
NODE_PATH C:\reactor
[latest-22310]2022-11-23T22:18:43.030Z <app:null> Reactor build latest-22310-a6da8097 starting on v16.15.1
c:\reactor\app.js:277
log['always'](a0_0x3d42be(0x26a), BUILD_VERSION, process['version']), log['always']('Process\x20ID\x20%1\x20user/group\x20%2/%3;\x20%4;\x20platform\x20%5/%6\x20%7;\x20locale\x20%8', process['pid'], process[a0_0x3d42be(0x269)](), process[a0_0x3d42be(0x278)](), is_docker ? 'docker' : a0_0x3d42be(0x288), process[a0_0x3d42be(0x287)], process['arch'], os[a0_0x3d42be(0x263)](), sys_locale), log[a0_0x3d42be(0x28c)]('Basedir\x20%1;\x20data\x20in\x20%2', c[a0_0x3d42be(0x1f8)], c[a0_0x3d42be(0x27b)]), log[a0_0x3d42be(0x28c)](a0_0x3d42be(0x21b), process['env'][a0_0x3d42be(0x291)]);
                                                                                                                                                                                                                                 ^

TypeError: process[a0_0x3d42be(...)] is not a function
    at Object.<anonymous> (c:\reactor\app.js:277:226)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47

    But I can't figure out what TypeError means?

    Also, before I tried a new install, there apperd an warning when installing reactor service.

    c:\reactor>npm install -g node-windows@1.0.0-beta.6
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

added 5 packages, and audited 6 packages in 3s

2 vulnerabilities (1 moderate, 1 critical)

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

    Running npm audit fix --force seems to broke something, because I could not install service after that.

    c:\reactor>npm audit fix --force
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm WARN using --force Recommended protections disabled.

up to date, audited 89 packages in 826ms

12 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

c:\reactor>node tools\install_reactor_windows_service.js -i .
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'node-windows'
Require stack:
- c:\reactor\tools\install_reactor_windows_service.js
←[90m    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m
←[90m    at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m
←[90m    at Module.require (node:internal/modules/cjs/loader:1005:19)←[39m
←[90m    at require (node:internal/modules/cjs/helpers:102:18)←[39m
    at Object.<anonymous> (c:\reactor\tools\install_reactor_windows_service.js:102:15)
←[90m    at Module._compile (node:internal/modules/cjs/loader:1105:14)←[39m
←[90m    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)←[39m
←[90m    at Module.load (node:internal/modules/cjs/loader:981:32)←[39m
←[90m    at Function.Module._load (node:internal/modules/cjs/loader:822:12)←[39m
←[90m    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)←[39m {
  code: ←[32m'MODULE_NOT_FOUND'←[39m,
  requireStack: [ ←[32m'c:\\reactor\\tools\\install_reactor_windows_service.js'←[39m ]
}
    Multi-System Reactor
  • Quality of Life Request: Update Button
    A Andr

    Some input from a Windows user.
    An update button would of course be a nice to have feature, but I also agree with several other here. A "normal" update, aka don't need new dependencies, just take a short moment to install.
    Were I usually stumble is when an update of dependencies are needed. That have taken me hours of search-try--error-tryagain before getting that to work sometimes.

    My dream would be to have a "windows installer" for MSR, that checks dependencies, install a systemservice etc.
    Over time I think that would be a safer/more stable way, with fewer user errors.

    With this said, I can understand really understand that @toggledbits need to handle this "his way" to be able to support differen't enviroments (and users 😉 )

    Multi-System Reactor
  • Can't upgrade package dependencies [Windows10]
    A Andr

    @toggledbits said in Can't upgrade package dependencies [Windows10]:

    I trust the government more than I trust Windows. I'll leave it at that.

    Hard choice... 😁

    Multi-System Reactor
  • Can't upgrade package dependencies [Windows10]
    A Andr

    @toggledbits
    Any idea what could cause this?

    Multi-System Reactor
  • Can't upgrade package dependencies [Windows10]
    A Andr

    Finally!

    Tried out almost every google result I could find I found something that worked.

    Repair the nodejs install from windows control panel did the trick ✌

    c:\reactor>npm install --no-save --omit dev
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

added 1 package, removed 6 packages, changed 3 packages, and audited 91 packages in 6s

13 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
npm notice
npm notice New minor version of npm available! 8.11.0 -> 8.18.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.18.0
npm notice Run npm install -g npm@8.18.0 to update!
npm notice

c:\reactor>
    Multi-System Reactor
  • Can't upgrade package dependencies [Windows10]
    A Andr

    Preparing for an upgrade to latest msr build, and got stuck on upgrade package dependencies.
    Then I remembered that this was the case last time the upgrade package dependencies was required also. After a lot of trying i gave up and did a clean install of everything. But since this happens again I would love to get this sorted out.

    It might be that the manual regarding node js should be updated. Or more noob-proof? I have a vague memory that the very first install required som searching to get node js up and running.

    What I have done so far.
    Stop reactor service.
    Delete package-lock.json
    Uninstall reactor service. (command prompt with admin)

    c:\reactor>node tools\install_reactor_windows_service.js -u .
Uninstalling Reactor service c:\reactor
Reactor service uninstalled.

    Unzip new version.
    Delete package-lock.json (again)

    c:\reactor>npm install --no-save --omit dev
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'
←[90m    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m
←[90m    at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m
←[90m    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)←[39m
←[90m    at node:internal/main/run_main_module:17:47←[39m {
  code: ←[32m'MODULE_NOT_FOUND'←[39m,
  requireStack: []
}

    Going wild and testing command from new installations.

    c:\reactor>npm install --no-save --omit dev
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'
←[90m    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m
←[90m    at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m
←[90m    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)←[39m
←[90m    at node:internal/main/run_main_module:17:47←[39m {
  code: ←[32m'MODULE_NOT_FOUND'←[39m,
  requireStack: []
}

c:\reactor>npm install --loglevel error --no-save --omit dev
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'
←[90m    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m
←[90m    at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m
←[90m    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)←[39m
←[90m    at node:internal/main/run_main_module:17:47←[39m {
  code: ←[32m'MODULE_NOT_FOUND'←[39m,
  requireStack: []
}

    What module is needed?
    Were to find it?
    What to do with it?😕

    Multi-System Reactor
  • Can't MSR see my Hass groups /rooms?
    A Andr

    @toggledbits
    OK. Not so big deal at the moment, but in future versions of Reactor Dashboard i hope for a way to set up areas/groups in Reactor instead.

    Multi-System Reactor rooms group msr sorting
  • Can't MSR see my Hass groups /rooms?
    A Andr

    A low priority question, but still a question 🤔
    I have both a Vera Edge and Homeassistant connected to MSR, and all devices from my Vera is neatly grouped in MSR by my room names that are set up in Vera.

    But HA devices just have one group in MSR "Ha>controller all" and not the areas I set up in HA.

    Have I missed something in my config or is HA areas simply not supported in MSR?

    Multi-System Reactor rooms group msr sorting
  • Adding remotes, scene controllers as entities to MSR
    A Andr

    @christian_fabre
    Happy to hear that it come to use (and that myself learned a few things on the way)
    😁

    Multi-System Reactor
  • Constraints under triggers or under constraints, what is the difference?
    A Andr

    Need to ask, have thougth about this since the move from Rector to MSR I think.

    What is the difference between putting constraints under trigger groups, like this
    23b4a249-3292-41cd-9927-7f49c9bf1d07-image.png

    Compared to this similar rule, but the time limits is under contraints instead?
    ee596c9f-f52b-4a39-9605-f5932f3d9ed5-image.png

    I think the Constraints parts in manual is still to be done because I can only find in the chapter menu, but it is not mentioned anywhere else.

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

    Seems to work like a charm 😁

    Started out with a few rules to let him control a Sonos in his room.
    This one is for starting his favorite playlist, when it not is bedtime and that playlist isn't already playing.

    c9770192-464f-4eb0-854f-9348e4b5b494-image.png

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

    Anyway, some kinds of sucess the last nights 👍

    All buttons are configured and seems to work so far.

    The final reactor.yaml looks like this (just showing the first two buttons as it is just the entity name and 'property key' that differ )

    event_targets:    # this section starts the event-receiving entities
        "Keyfob_Fyrkant":      # Assign an ID to your entity; each entity must have a unique ID
          name: Lukas Keyfob Fyrkant   # This is optional but recommended, so you have a friendly name
          capabilities: ['button']  # define an array of capabilities to be modified by the event 
          events:  # define an array of events that modify capability attributes on the entity
            - event:  # start of an event; each element of the events array begins this way
                event_type: zwave_js_value_notification
                data:  # optional section, if further matching to the event data is required
                  node_id: 15
                  property: "scene" # Square button
                  property_key: "001"
              response:  # begin the (required) response section for handling the event
                "button.state":  # an attribute that the event modifies.
                  from: "event.data.value"  # dot-reference expression to pull value from event message
                  map:                    # optional, map to modify value
                    KeyPressed: 'single'   # if value is value_in, it is mapped to new_value
                    KeyPressed2x: 'double'
                    KeyPressed3x: 'tripple'
                    KeyHeldDown: 'hold'
                    KeyReleased: 'release'
                "button.since":  # an attribute that the event modifies.
                  from: "event.context.id"  # dot-reference expression to pull value from event message
        "Keyfob_Ring":      # Assign an ID to your entity; each entity must have a unique ID
          name: Lukas Keyfob Ring   # This is optional but recommended, so you have a friendly name
          capabilities: ['button']  # define an array of capabilities to be modified by the event 
          events:  # define an array of events that modify capability attributes on the entity
            - event:  # start of an event; each element of the events array begins this way
                event_type: zwave_js_value_notification
                data:  # optional section, if further matching to the event data is required
                  node_id: 15
                  property: "scene" # Circle button
                  property_key: "002"
              response:  # begin the (required) response section for handling the event
                "button.state":  # an attribute that the event modifies.
                  from: "event.data.value"  # dot-reference expression to pull value from event message
                  map:                    # optional, map to modify value
                    KeyPressed: 'single'   # if value is value_in, it is mapped to new_value
                    KeyPressed2x: 'double'
                    KeyPressed3x: 'triple'
                    KeyHeldDown: 'hold'
                    KeyReleased: 'release'
                "button.since":  # an attribute that the event modifies.
                  from: "event.context.id"  # dot-reference expression to pull value from event message

    A thought that crossed my mind recently, to maybe expand the functions of this little remote in the future.
    Fibaro have built in a possibilty for 6 extra scenes that activates after a sequence of button presses I specify. I have not activated this yet as I don't think I really need it, but what I realised is that it probably quite easy to add a lot of differnt button sequences in MSR as long or short that I want?

    Next part is to get some rules and actions set-up that can use the remote.

    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