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.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. [Solved] Hubitat Hub Information Driver v3 and probe device
UI not loading after upgrading to 26318
tunnusT
Sorry for a hasty post, will update some details later, but the scenario is that I managed to type a wrong password for too many times and had the following users.yaml section: authtrack: max_attempts: 4 within_minutes: 180 # 180 minutes = 3 hrs block_expiration_minutes: 10080 # 7 days At this time I used build 26298. Then noticed there's a new build with a bypass blocking feature (and yes, it said it won't remove existing block). Anyway, went ahead and upgraded to 26318, but the problem now is that UI is not loading at all (page does not answer). This also means that I cannot use "http://reactor_host:port/diag/clear_authtrack?askauth" command to clear the block (or use any other source IP for login). Docker container stays up & running and does not exit. I'll try to dig up some logs, but anything that I could immediately try out (could I delete a particular file for example)? EDIT: some logs [latest-26318]2026-11-17T20:42:32.337Z <Rule:INFO> MSR startup (rule-lculfnhm in Miscellaneous) started [latest-26318]2026-11-17T20:42:32.343Z <httpapi:NOTICE> httpapi#1 HTTP server listening on :::8111 [latest-26318]2026-11-17T20:42:32.347Z <httpapi:INFO> httpapi#1 local docs found in /opt/reactor/docs/html; setting up static service [latest-26318]2026-11-17T20:42:32.354Z <app:NOTICE> Starting WSAPI... [latest-26318]2026-11-17T20:42:32.355Z <wsapi:NOTICE> wsapi: starting version 26298 protocol [latest-26318]2026-11-17T20:42:32.523Z <Engine:INFO> Engine#1 master timer tick, local time "17/11/2026 22:42:32" (TZ offset 120 mins from UTC) [latest-26318]2026-11-17T20:42:32.542Z <Engine:NOTICE> Starting reaction MSR startup<SET> (rule-lculfnhm:S) [latest-26318]2026-11-17T20:42:32.545Z <Notifier:null> Module Notifier v26186 [latest-26318]2026-11-17T20:42:32.545Z <Engine:INFO> MSR startup<SET> all actions completed. [latest-26318]2026-11-17T20:42:32.557Z <Rule:INFO> Rule#rule-lculfnhm reaction rule-lculfnhm:S completed [latest-26318]2026-11-17T20:42:32.558Z <default:null> Module NotifyTelegram v26177
Multi-System Reactor
[Resolved] Hubitat upgrade 2.5.3.123 may have broken login
3
Topic thumbnail image
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
Reactor Inspect - a small read-only helper panel for MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Reverse proxy & API ACL
tunnusT
I'm trying to allow anonymous access from a local network to /api/v1/log, but the problem now with the reverse proxy configuration is that this access is open via proxy to the internet. At least I wasn't able to configure ACL so that only an access from a local network would be permitted. reactor.yaml: baseurl: "http://192.168.1.12:8111" proxy_baseurl: "https://external.com:30000" trusted_proxy: "192.168.1.12" Local traffic would originate from 192.168.1.0/24 network. Synology is acting as a reverse proxy and hosting MSR as a docker container (which has its own network and IP 172.18.0.5). MSR build is latest-26298-fbb75fb8 users.yaml: - url: "/api/v1/log" method: "GET" source_ip: 172.18.0.0/24 allow: true Using the above ACL works, but it enables access via proxy also. If I use source_ip: 192.168.1.0/24, then it doesn't work either locally or remotely. So I'm kinda lost what should I use as source_ip in this case?
Multi-System Reactor
MFA
T
Topic thumbnail image
Multi-System Reactor
Grouped devices
G
I've seen many of you using Dynamic Group Controller. I'm using it myself for monitoring device battery levels. I've read and re-read the Dynamic Group Controller docs and still cannot come to an answer for my question so let me paint my scenario: I've migrated from EchoSpeaks in Hubitat ('cause borked and seemingly unmaintained) to Alexa Devices in Home Assistant ('cause not borked in 2026.11.0) to be able to send TTS to my Echo devices. In EchoSpeaks I could create groups. Sweet. In Alexa Devices I don't seem to be able to do so. As such, my thought was "wait - isn't there a way in MSR?" Is this an effective scenario that Dynamic Group Controller can be used for?
Multi-System Reactor
Login protections
tunnusT
Topic thumbnail image
Multi-System Reactor
Reactor Build 26284 stuck at Loading Reactor UI
T
Topic thumbnail image
Multi-System Reactor
MSR with reverse proxy
tunnusT
I'm trying to use MSR via reserve proxy in Synology DSM, but MSR page does not load https://<public ip>:30000/reactor/en-US/ At the same time logging page loads normally https://<public ip>:30000/api/v1/log I thought maybe authentication was messing it up, but there was no deny entries in the log, and also disabling authentication did not make any difference. For this use case VPN is not an option (that works, but as said not an option for this particular use case). Any ideas what could cause this? MSR build latest-26242-28d69aa8, Chrome browser
Multi-System Reactor
Missing attribute after upgrade
3
Topic thumbnail image
Multi-System Reactor
[MSR] Native fan capabilty
therealdbT
Nothing more to add. I see we have hvac_blower, but, anyway, maybe a native fan on the same assumptions of the fan from HASS could be reasonable. I have a couple of them. ie, this is from ESPHome via HASS. x_hass.domain="fan" x_hass.entity_id="fan.kitchen_seashell_hood_ventilation_fan" x_hass.floor_id=null x_hass.services=["fan","esphome"] x_hass.source="esphome" x_hass.state="off" x_hass_attr.friendly_name="Seashell Hood Ventilation Fan" x_hass_attr.percentage=50 x_hass_attr.percentage_step=25 x_hass_attr.preset_mode="" x_hass_attr.preset_modes=[] x_hass_attr.supported_features=49 Thanks.
Multi-System Reactor
[MSR] Rule do not fire
therealdbT
Topic thumbnail image
Multi-System Reactor
Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
N
Build: latest-26221-b25bb3e3, Docker on Synology. Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing. Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries. Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart. Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either. Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart? Thanks in advance
Multi-System Reactor
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
Multi-System Reactor
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
Ooops - Deleted Reactor Ex Machina II
R
I accidentally deleted Reactor Ex Machina II (REM II) from my Reactor rules. I tried to recover it by deleting the .json and .dval in the Rules subdirectory and then recreating it from Togglebits original posting, but that did not work. Does anyone know how to recover REM ll ?
Multi-System Reactor
Bail out of failed reaction?
T
Topic thumbnail image
Multi-System Reactor
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Multi-System Reactor

[Solved] Hubitat Hub Information Driver v3 and probe device

Scheduled Pinned Locked Moved Multi-System Reactor
9 Posts 2 Posters 2.4k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    SweetGenius
    wrote on last edited by SweetGenius
    #1

    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

    Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #2

      I am not able to duplicate the behavior you describe (Hub Info stops polling). I suggest you check your polling interval in your Hub Information device configuration and make sure it's a sensible number (and specifically not 0). There also have been several bug fix releases of that driver; the current version is 3.0.14 and that's what you should be on.

      The documentation describes the probe_device config as an integer; that's not what you have shown. It should be the device number only. It doesn't need to know which controller because you are in configuration for a controller. The Hub Information driver, if present, is still the preferred device and will override.

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      S 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        I am not able to duplicate the behavior you describe (Hub Info stops polling). I suggest you check your polling interval in your Hub Information device configuration and make sure it's a sensible number (and specifically not 0). There also have been several bug fix releases of that driver; the current version is 3.0.14 and that's what you should be on.

        The documentation describes the probe_device config as an integer; that's not what you have shown. It should be the device number only. It doesn't need to know which controller because you are in configuration for a controller. The Hub Information driver, if present, is still the preferred device and will override.

        S Offline
        S Offline
        SweetGenius
        wrote on last edited by SweetGenius
        #3

        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?

        Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

        1 Reply Last reply
        0
        • toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by
          #4

          They do. I use much a much shorter interval (actually, the default 300). It behaves the same way just using a simple refresh action.

          That's going to make Hub Information Driver v3 unusable for this purpose, and send me back to the drawing board on the detection and probe for quiet channel. I'll look into it, but it may be a few days before I have time. I'm on other projects.

          In your post/screen shots, I don't see any evidence, however, that the polls are not running. If they are scheduled, they are running. It's just a change in the interval caused by the Configure or Refresh. From what I can see, every attribute is being updated when the probe occurs. I am not seeing that the updates stop. So that just means things are being updated probably more frequently than you've scheduled -- pretty much opposite what you're reporting here. Are you seeing things that should be updated not be, or are you just assuming they haven't updated because of timing change?

          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

          S 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            They do. I use much a much shorter interval (actually, the default 300). It behaves the same way just using a simple refresh action.

            That's going to make Hub Information Driver v3 unusable for this purpose, and send me back to the drawing board on the detection and probe for quiet channel. I'll look into it, but it may be a few days before I have time. I'm on other projects.

            In your post/screen shots, I don't see any evidence, however, that the polls are not running. If they are scheduled, they are running. It's just a change in the interval caused by the Configure or Refresh. From what I can see, every attribute is being updated when the probe occurs. I am not seeing that the updates stop. So that just means things are being updated probably more frequently than you've scheduled -- pretty much opposite what you're reporting here. Are you seeing things that should be updated not be, or are you just assuming they haven't updated because of timing change?

            S Offline
            S Offline
            SweetGenius
            wrote on last edited by
            #5

            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?

            Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

            1 Reply Last reply
            0
            • toggledbitsT Offline
              toggledbitsT Offline
              toggledbits
              wrote on last edited by
              #6

              That is all clear to me. What I am trying to convey to you is that the rescheduling of the polls does not mean that the Hub Information Driver v3 is not updating its attributes (in effect, doing the polls). When Reactor causes the probe (if it needs to), the driver does its poll at the time of the request, updates all of the attributes, and then reschedules for the next poll. So the attributes are still being updated, as I said, just sometimes earlier than the driver itself would do. I could leave it that way and most users would never know or care.

              Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

              S 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                That is all clear to me. What I am trying to convey to you is that the rescheduling of the polls does not mean that the Hub Information Driver v3 is not updating its attributes (in effect, doing the polls). When Reactor causes the probe (if it needs to), the driver does its poll at the time of the request, updates all of the attributes, and then reschedules for the next poll. So the attributes are still being updated, as I said, just sometimes earlier than the driver itself would do. I could leave it that way and most users would never know or care.

                S Offline
                S Offline
                SweetGenius
                wrote on last edited by
                #7

                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.

                Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

                1 Reply Last reply
                0
                • S Offline
                  S Offline
                  SweetGenius
                  wrote on last edited by
                  #8

                  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

                  Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

                  1 Reply Last reply
                  1
                  • toggledbitsT Offline
                    toggledbitsT Offline
                    toggledbits
                    wrote on last edited by
                    #9

                    Great. Thanks for letting me know.

                    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                    1 Reply Last reply
                    0
                    • toggledbitsT toggledbits locked this topic on
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                    Recent Topics

                    • UI not loading after upgrading to 26318
                      toggledbitsT
                      toggledbits
                      0
                      6
                      156

                    • [Resolved] Hubitat upgrade 2.5.3.123 may have broken login
                      toggledbitsT
                      toggledbits
                      0
                      8
                      307

                    • Reactor (Multi-System/Multi-Hub) Announcements
                      toggledbitsT
                      toggledbits
                      5
                      153
                      163.6k

                    • Reactor Inspect - a small read-only helper panel for MSR
                      G
                      gwp1
                      2
                      8
                      627

                    • Reverse proxy & API ACL
                      tunnusT
                      tunnus
                      0
                      9
                      533

                    • MFA
                      T
                      tamorgen
                      0
                      28
                      1.5k

                    • Grouped devices
                      G
                      gwp1
                      0
                      3
                      205

                    • Login protections
                      toggledbitsT
                      toggledbits
                      0
                      2
                      244

                    • Reactor Build 26284 stuck at Loading Reactor UI
                      T
                      tamorgen
                      0
                      16
                      1.8k

                    • MSR with reverse proxy
                      tunnusT
                      tunnus
                      0
                      12
                      914

                    • Missing attribute after upgrade
                      3
                      3rdStng
                      0
                      3
                      700

                    • Use of Google Gemini as an MSR and Hubitat configuration aid
                      therealdbT
                      therealdb
                      0
                      2
                      340
                    Powered by NodeBB | Contributors
                    Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                    • Login

                    • Don't have an account? Register

                    • Login or register to search.
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • Unsolved