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

SweetGenius

@SweetGenius
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
97
Topics
24
Shares
0
Groups
0
Followers
0
Following
1

Posts

Recent Best Controversial
  • VEC Virtual Switch Auto Off
    S SweetGenius

    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
  • Reactor Loading Screen Safari
    S SweetGenius

    @toggledbits I tried the Clear Local Storage and a hard-refresh and still have the same result. I am attaching a new screenshot of the web inspector where I saw some errors just in case it means something to you. Screenshot 2025-12-10 at 5.47.00 PM.png

    I don't know why it works for some on Safari but seems work for all with other browsers. Is there anything else you can think of for me to check?

    Thank you for responding with your experiences @CatmanV2 @therealdb and @gwp1 !

    Multi-System Reactor
  • Constraints states visually do not match actual
    S SweetGenius

    I guess I never noticed before as I thought they used to update.
    The rules function so just visual.
    Thank You for the information.

    Multi-System Reactor
  • Reactor Loading Screen Safari
    S SweetGenius

    @CatmanV2 Can you try Safari on a Mac Desktop or the IOS. It does it on both on my setup.
    Screenshot 2025-12-10 at 6.38.18 AM.png

    Thanks

    Multi-System Reactor
  • Reactor Loading Screen Safari
    S SweetGenius

    @toggledbits Confirming that is while the Loading Reactor screen. See Screenshot:
    Screenshot 2025-12-10 at 6.27.38 AM.png And two more screenshots of the web inspector.
    Screenshot 2025-12-10 at 6.28.24 AM.png

    Screenshot 2025-12-10 at 6.28.53 AM.png Understand you not having apple products, So Thank You!

    Multi-System Reactor
  • Reactor Loading Screen Safari
    S SweetGenius

    When starting MSR, I started getting “Loading Reactor” Screen everytime. Pressing refresh multiple times the page will load or click on any of the menu links and the status page will then display and everything will work normally. It appears to be a safari only issue as it loads fine in chrome. I don’t know exactly when it stared, if it was updating to one of the newer builds or updating the Mac to 26.1. This is probably not a MSR problem but I thought I would share in case. Cleared cache, hard reset browser, private window and restarted MSR. Below is a screenshot of the web console while stuck. The error that says Object does not exist, the rule is there and functioning.
    Screenshot 2025-12-09 at 7.24.48 PM.png

    Thanks,

    Synology Docker
    latest-25325-2c235fbb
    Mac Safari 26.1

    Multi-System Reactor
  • Constraints states visually do not match actual
    S SweetGenius

    When viewing a rule, the constraints conditions do not match the current state of the entities. After the rule runs then they will display what the state of the entity was when the rule fired but otherwise they do not update to show the current state. While editing the rule the entities show the correct state and they will change state in the editor window. The rule functions but visually does not look correct. I believe they used to show the current value when viewing the rule. I have tried Safari and Chrome browsers, hard refreshed the browsers, restarted MSR.
    Screenshot showing that Motion Overide constraint is false but actual state is true. (Rule has not executed yet.)
    Screenshot 2025-12-09 at 6.38.30 PM.png Screenshot 2025-12-09 at 6.39.36 PM.png Screenshot after rule execution:
    Screenshot 2025-12-09 at 7.05.16 PM.png

    Is this the intended behavior?
    Thanks

    Synology Docker
    latest-25325-2c235fbb
    Mac Safari 26.1
    Chrome 143.0.7499.41

    Multi-System Reactor
  • [Solved] Runtime error when exiting global reaction that contains a group
    S SweetGenius

    Fixed in Reactor build 25067.
    Thank You!

    Multi-System Reactor
  • [Solved] Runtime error when exiting global reaction that contains a group
    S SweetGenius

    No hurry sir, Just reporting.

    Multi-System Reactor
  • [Solved] Runtime error when exiting global reaction that contains a group
    S SweetGenius

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

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

    @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44

You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.

    Google Chrome 133.0.6943.142

    TypeError: self.editor.isModified is not a function
    at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34)

You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.

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

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

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

    Multi-System Reactor
  • Any interest in a Homebridge adapter for Reactor?
    S SweetGenius

    Yes, I would be interested.

    Multi-System Reactor
  • Have reactor shut off a light with no motion unless I turned it on manually
    S SweetGenius

    @sethlampman I use multiple rules and a global expression to hold the current state of the light that I set when different events happen. When motion triggers the light I set the global expression to “auto”. When the light comes on with no motion then it must of been turned on manually so that rule sets the expression to “man” I then have rules to to shut the light off for when motion happend and another rule for when it was turned on manually with different delays. When the light is off I set the global expression to idle. Does this give you any ideas for your situation?
    Screenshot 2023-12-05 at 7.07.05 PM.png Screenshot 2023-12-05 at 7.07.31 PM.png Screenshot 2023-12-05 at 7.07.58 PM.png Screenshot 2023-12-05 at 7.08.21 PM.png Screenshot 2023-12-05 at 7.10.59 PM.png

    Multi-System Reactor
  • Home Assistant push notification for Reactor version update possible?
    S SweetGenius

    @tamorgen If I understand what you are asking correctly, Look under the reactor_system for reactor_system.update_available=true and use that as a rule trigger to send a notification.

    Multi-System Reactor
  • [Solved] Hubitat Hub Information Driver v3 and probe device
    S SweetGenius

    Installation of Reactor build 23049 and configuring a virtual switch as a probe device appears to be working well.
    FYI, The "Manual" link in the Reactor UI doesn't have the updated docs that are linked to in the Release notes thread. Hubitat Controller, Other Configuration, probe_device section. I have tried a hard reset in safari and Firefox browsers but the documentation is not the updated instructions. Thank You.
    Synology Docker
    latest-23049

    Multi-System Reactor
  • [Solved] Hubitat Hub Information Driver v3 and probe device
    S SweetGenius

    With all due respect and I do mean that and without beating this to death, I am only seeing the attributes that update when MSR probes are the baseData attributes witch per the Hub information driver’s documentation are (attributes: firmwareVersionString, hardwareID, id, latitude, localIP, localSrvPortTCP, locationId, locationName, longitude, name, temperatureScale, timeZone, type, uptime, zigbeeChannel, zigbeeEui, zigbeeId, zigbeeStatus, zipCode). I can find these attributes updating in the logs every time. Some examples of attributes that are not updating are publicIP and hubUpdateVersion among others. I use those attributes in rules and they do not update. I can not find evidence of these being updated in the logs or driver unless you set the poll time for these to very fast interval as I tried to document in the previous post. I do believe the next scheduled poll time is accurate and the attributes associated with the polls will not update until that time. Probably the best thing to do is to revert to the v2 driver.

    Multi-System Reactor
  • [Solved] Hubitat Hub Information Driver v3 and probe device
    S SweetGenius

    It looks like when MSR probes the device, it then resets the next scheduled poll times to the time of the probe + whatever time you have set to poll in the device preferences. If you have small poll times then the polls might fire between MSR polls. Here is the filtered Hubitat log showing which polls run. lastPoll: baseData is when MSR does the probe. The first part of the log is with the poll:1 time is set at 9 minutes. If the time elapsed since a MSR probe > than 9 minutes then the poll:1 will run. It ran once at 06:45:15. I then changed the poll1 time from 9 mins to 3 mins at 8:00pm to test. You can see it ran more often but I don't know why the baseData slowed way down also.

    dev:4812023-02-13 08:39:50.352 PMinfolastPoll : baseData
dev:4812023-02-13 08:37:48.478 PMinfolastPoll : poll1
dev:4812023-02-13 08:34:48.349 PMinfolastPoll : poll1
dev:4812023-02-13 08:31:48.207 PMinfolastPoll : poll1
dev:4812023-02-13 08:28:48.062 PMinfolastPoll : poll1
dev:4812023-02-13 08:25:48.076 PMinfolastPoll : baseData
dev:4812023-02-13 08:23:46.117 PMinfolastPoll : poll1
dev:4812023-02-13 08:20:45.974 PMinfolastPoll : poll1
dev:4812023-02-13 08:17:45.811 PMinfolastPoll : poll1
dev:4812023-02-13 08:14:45.676 PMinfolastPoll : poll1
dev:4812023-02-13 08:11:45.509 PMinfolastPoll : poll1
dev:4812023-02-13 08:08:45.408 PMinfolastPoll : poll1
dev:4812023-02-13 08:05:45.460 PMinfolastPoll : baseData
dev:4812023-02-13 08:03:43.698 PMinfolastPoll : poll1
dev:4812023-02-13 08:00:43.644 PMinfolastPoll : baseData
dev:4812023-02-13 07:56:18.977 PMinfolastPoll : baseData
dev:4812023-02-13 07:54:17.207 PMinfolastPoll : baseData
dev:4812023-02-13 07:50:52.589 PMinfolastPoll : baseData
dev:4812023-02-13 07:44:17.322 PMinfolastPoll : baseData
dev:4812023-02-13 07:39:17.057 PMinfolastPoll : baseData
dev:4812023-02-13 07:36:18.474 PMinfolastPoll : baseData
dev:4812023-02-13 07:34:16.720 PMinfolastPoll : baseData
dev:4812023-02-13 07:26:27.444 PMinfolastPoll : baseData
dev:4812023-02-13 07:24:16.188 PMinfolastPoll : baseData
dev:4812023-02-13 07:21:27.225 PMinfolastPoll : baseData
dev:4812023-02-13 07:14:58.542 PMinfolastPoll : baseData
dev:4812023-02-13 07:09:15.465 PMinfolastPoll : baseData
dev:4812023-02-13 07:04:15.275 PMinfolastPoll : baseData
dev:4812023-02-13 07:01:16.758 PMinfolastPoll : baseData
dev:4812023-02-13 06:59:14.981 PMinfolastPoll : baseData
dev:4812023-02-13 06:54:14.847 PMinfolastPoll : baseData
dev:4812023-02-13 06:45:15.886 PMinfolastPoll : poll1
dev:4812023-02-13 06:36:15.792 PMinfolastPoll : baseData
dev:4812023-02-13 06:34:14.031 PMinfolastPoll : baseData
dev:4812023-02-13 06:29:52.364 PMinfolastPoll : baseData
dev:4812023-02-13 06:26:15.479 PMinfolastPoll : baseData
dev:4812023-02-13 06:24:13.706 PMinfolastPoll : baseData
dev:4812023-02-13 06:19:41.211 PMinfolastPoll : poll1

    I am not looking for an immediate fix or change, Just trying to communicate to you what I am seeing.

    Would it be an option to write your own virtual device driver for Hubitat so you could probe that device and return the data you want for the health check?

    Multi-System Reactor
  • [Solved] Hubitat Hub Information Driver v3 and probe device
    S SweetGenius

    I am running the latest version of the driver: v3.0.14.
    It appears to me when MSR probes the device or if you press configure in the driver, all the new scheduled poll times increase causing them never to run. I have my poll times set as follows: poll1: 9 mins, poll2: 119 mins, poll3: 241 mins, poll4: 12 hours.
    Screen Shot 2023-02-12 at 2.31.24 PM.png Here is a screenshot showing the scheduled poll times to start:
    Screen Shot 2023-02-12 at 2.29.39 PM.png

    After MSR polls the scheduled poll times:
    Screen Shot 2023-02-12 at 2.40.38 PM.png

    Poll3 and poll2 are not running.
    Here is what I'm polling in the driver.
    Screen Shot 2023-02-12 at 3.13.54 PM.png

    I know this is not your driver but I'm encouraged if you are not seeing a problem. I must have something configured wrong. Would you mind checking your driver and see if your scheduled times increase also?

    Multi-System Reactor
  • [Solved] Hubitat Hub Information Driver v3 and probe device
    S SweetGenius

    I have upgraded my Hubitat Hub Information Driver to v3 and after the latest MSR update latest-23028 MSR is working ok. The problem is when MSR probes the device it appears to affect the polling in the new Hub Information Device and its data does not update the data fields in Hubitat. If I remove the Hub Information Device from Maker API so MSR can't see it, The Hub information driver updates the data as expected in Hubitat. I added the device back into Maker API the same problem returns in Hubitat. I have tried to have MSR probe a different device by adding a different probe device and probe action in the reactor.yaml per the documentation but it appears then it still uses the Hub Information Device as the probe device instead of the one specified in the reactor.yaml. See Logs below. Is this the intended behavior to always use the Hub Information Driver if found and not use the device in the reactor.yaml file? Any recommendations on how to get MSR and the v3 of the driver to work correctly or can you see what I am doing wrong?

    [latest-23028]2023-02-11T23:27:50.471Z <Controller:NOTICE> Controller HassController#hass is now online.
[latest-23028]2023-02-11T23:27:50.471Z <Rule:INFO> Internet Check (rule-l44qss4f in Home) starting evaluation; because entity-changed System#reactor_system>system
[latest-23028]2023-02-11T23:27:50.471Z <Rule:INFO> MSR Update Version Available (rule-labweim2 in Notify) starting evaluation; because entity-changed System#reactor_system>system
[latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> Internet Check (rule-l44qss4f in Home) trigger evaluation result is false (previously false)
[latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> Internet Check (rule-l44qss4f in Home) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> MSR Update Version Available (rule-labweim2 in Notify) trigger evaluation result is false (previously false)
[latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> MSR Update Version Available (rule-labweim2 in Notify) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> Internet Check (rule-l44qss4f in Home) evaluation complete
[latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> MSR Update Version Available (rule-labweim2 in Notify) evaluation complete
[latest-23028]2023-02-11T23:27:50.673Z <HubitatController:INFO> HubitatController#hubitat Maker API responded with 91 devices
[latest-23028]2023-02-11T23:27:50.766Z <HubitatController:INFO> HubitatController#hubitat found 'Hub Information Driver v3' device #"481"; using for probe/health checks.
[latest-23028]2023-02-11T23:27:50.780Z <Controller:INFO> HubitatController#hubitat 0 dead entities older than 86400000s purged
[latest-23028]2023-02-11T23:27:50.780Z <Rule:INFO> Roku Pause (rule-l3nlrzu9 in Home) starting evaluation; because entity-changed BinarySensor#hubitat>519
[latest-23028]2023-02-11T23:27:50.780Z <Rule:INFO> Stairs Light Low Light (rule-kulslls9 in Living Room) starting evaluation; because entity-changed BinarySensor#hubitat>519
[latest-23028]2023-02-11T23:27:50.780Z <Rule:INFO> Porch Motion Extended check (rule-l3kr45m8 in Porch) starting evaluation; because entity-changed BinarySensor#hubitat>519
[latest-23028]2023-02-11T23:27:50.780Z <Rule:INFO> Porch Light Manual On (rule-kmtxw155 in Porch) starting evaluation; because entity-changed BinarySensor#hubitat>519

    Snippet from the reactor.yaml:

     # action_pace: 100
      # warn_unresponsive: true
      # probe_device: hubitat>132 (not needed if Hub Information app installed)
      probe_device: hubitat>2
      # probe_action: x_hubitat_Configuration.configure (not needed if Hub Information app installed)
      probe_action: x_hubitat_Configuration.configure
      # probe_action: x_hubitat_Refresh.refresh

    Synology Docker latest-23028
    Hubitat v2.3.4.139
    Hub Information Driver v3

    Multi-System Reactor
  • [Resolved] Determining if button is pushed
    S SweetGenius

    @3rdStng I do not have the same device but I had to overcome this with my minimotes. Have you tried to set the x_hubitat_pushableButton.push back to 0 after your intended reaction. I cannot post images either for some reason or I would post an image of my Rule.

    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