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
[HowTo] Using HABridge with Reactor
therealdbT
If you’re like me and still running HABridge to control your devices locally via Alexa, you might need to tweak your endpoints to call Reactor via HTTP. Here’s the best way to do it, IMO: Insert the Reactor Canonical ID (e.g., zwavejs>71-1) into the MapID field, but make sure it’s URL-encoded like this: zwavejs%3E71-1. Then, configure these endpoints as needed: On: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.on Off: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.off Dim: For lights: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/dimming.set?level=${intensity.decimal_percent} For roller shutters: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/position.set?value=${intensity.decimal_percent} Color: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/rgb_color.set_rgb?red=${color.r}&green=${color.g}&blue=${color.b} Just replace [ReactorIP] with your actual IP address. By using these placeholders, you can standardize your endpoints across all devices, making maintenance easier. This setup works with any device mapped under MSR, regardless of the controller (ZWaveJS, Vera, HASS, OpenSprinkler, virtual, MQTT, DynamicEntities, etc.). If you need different calls, just go to the entities, get the action and parameters, and adjust accordingly. Enjoy super fast access to your devices via Alexa! If you're migrating from Vera, the endpoints are (URL-encoded) in a file called device.db, in JSON format, under your config. You'd write a script to align the new endpoints to the new one, if you prefer to do it automatically. YMMV.
How-To
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
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
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Zigbee2mqtt installed! sytemctl not happy :(
CatmanV2C
Hello oh great ones. After a couple of hours messing with ports and permissions I have Zigbee2mqtt installed and running on my virtual pi Can connect to the front end and everything Odd one though, simply cannot get systemctl to work and the error is, well, unhelpful. The service file is this: [Unit] Description=zigbee2mqtt After=network.target [Service] Environment=NODE_ENV=production Type=notify ExecStart=/usr/local/bin/node index.js WorkingDirectory=/opt/zigbee2mqtt StandardOutput=inherit # Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5) StandardError=inherit WatchdogSec=10s Restart=always RestartSec=10s User=pi [Install] WantedBy=multi-user.target Straight out of the docs with the change to point to my local node install (which we know works as it's the same as the very fine Reactor is using. Running manually pnpm start in /opt/zigbee2mqtt works fine However: catman@openluup:/etc/systemd/system$ sudo systemctl start zigbee2mqtt.service Job for zigbee2mqtt.service failed because the control process exited with error code. See "systemctl status zigbee2mqtt.service" and "journalctl -xe" for details. Which I have catman@openluup:/etc/systemd/system$ sudo systemctl status zigbee2mqtt.service ● zigbee2mqtt.service - zigbee2mqtt Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Tue 2025-12-16 12:32:42 GMT; 4s ago Process: 3093 ExecStart=/usr/local/bin/node index.js (code=exited, status=217/USER) Main PID: 3093 (code=exited, status=217/USER) and -- A start job for unit zigbee2mqtt.service has begun execution. -- -- The job identifier is 17477. Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed to determine user credentials: No such process Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed at step USER spawning /usr/local/bin/node: No such process -- Subject: Process /usr/local/bin/node could not be executed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The process /usr/local/bin/node could not be executed and failed. -- -- The error number returned by this process is ERRNO. Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=217/USER -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit zigbee2mqtt.service has exited. -- -- The process' exit code is 'exited' and its exit status is 217. Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit zigbee2mqtt.service has entered the 'failed' state with result 'exit-code'. Dec 16 12:35:16 openluup systemd[1]: Failed to start zigbee2mqtt. -- Subject: A start job for unit zigbee2mqtt.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit zigbee2mqtt.service has finished with a failure. Which strikes me as very odd. Any blindingly obvious things I'm missing? TIA! C
Zigbee
Any thoughts on which is better
CatmanV2C
Obviously a quiet forum, but perhaps it's time I'm looking at rolling Zigbee into my system, in large part for the Aqara FP300 presence sensors which seem to finally provide a solution to if the wasp is actually in the box. My current set up is as follows: One Debian VM on Synology NAS running: Z-wave Server Open Luup Multi system reactor HA bridge Mosquito MQQT broker This machine has a UZB Z-wave stick connected via the USB port on the NAS Another HAOS VM on the same NAS running HAOS I've got some older Z-wave stuff that I keep around until it fails. I have some Tuya stuff integrated in HA My thought was to get either a SMLIGHT SLZB-06M or an Aqara Hub M2 Integrate them via Zigbee2MQQT (running on the Debian machine) and then expose them in HA so I can continue to automate in MSR. Thoughts on which of those devices wold be preferable long term. Both are POE capable which is good. It also appears I could add a USB dongle to the NAS and expose it to the HAOS machine. Any thoughts from the assembled experts here? TIA C
Zigbee
Single protocol?
CatmanV2C
Another question to the hive mind. Prompted by the fact that I lost yet another z-wave device over the weekend due to a power issue. It looks like z-way server is reporting another device failed (although it's working fine) and message queue is far too long IMHO. Also the failed device has been removed in the expert interface, but still there in the 'normal' one. Sigh. Currently I have z-wave, Tuya, thinking about Zigbee.... Does anyone use one single protocol for everything? Right now I'm feeling that as the z-wave stuff dies, I'm just gonna replace it with something else.... C
General Discussion
HDMI oddness
CatmanV2C
Not really Smart Home stuff, but going to ask as we have smart people... Bear with me on this one. Asking here because of the font of knowledge! For many eek years I have had a Virgin V6 box and a Raspberry Pi running Kodi connected to my TV through a cheap *** HDMI switch. It all worked beautifully but the absolutely critical thing was that the TV remote passed the signals back to the Pi to allow remote control of Kodi. Couple of changes of late: Installed a soundbar on the TV using the ARC (audio return channel). That then turns the soundbar on and off when the TV turns on and off and the TV volume control controls the soundbar volume direct. Everything continues to work Upgraded the software of the Tivo box to Virgin 360. This is literally software only. You get sent a snacky new Bluetooth remote hit 'upgrade' on the screen and off it goes. Now, things are not playing well. Typically when I turn on to watch Kodi the soundbar comes on (as it should) but the TV either puts out sound through its own speakers and the soundbar, or just the soundbar. It's not possible to control the volume of the soundbar through the TV. Also it's not longer possible to control Kodi using the TV remote. If I turn the TV360 box off, i.e. power it down, before turning on to watch Kodi, everything is fine. This makes little to no sense to me. My assumption is that the cheap *** HDMI switch is getting something from the TV360 connection that it didn't used to get when the software was Tivo and that's screwing up the HDMI communications. I'm upgrading the switch to something a little less chap, but wondered if anyone could validate my theory at all? TIA C
General Discussion
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
Oh the joy of pairing
CatmanV2C
When I remember the old days Just added a new Tuya plug (OK so it's cloud) Start to finish, visible in HA and MSR < 30 seconds... C
Vera
Home Assistant Connect ZWA-2 & ZBT-2
therealdbT
Topic thumbnail image
Hardware
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
About
Posts
96
Topics
23
Shares
0
Groups
0
Followers
0
Following
1

Posts

Recent Best Controversial
  • 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
  • Quality of Life Request: Update Button
    S SweetGenius

    I personally do not think the update process on Synology docker is that bad. A few more clicks than an easy button but not horrible. All my other docker containers are updated the same way. I like the docker image though. I am not familiar with the other platforms so I can’t comment on those update processes.

    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