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: Use of multiple Hubitat hubs with MSR
[Solved] Limit HA Entity in MSR
wmarcolinW
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
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
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
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
Multi-System Reactor
Custom capabilities in MQTT templates
M
Hi, I'm trying to integrate the sonos-mqtt (https://sonos2mqtt.svrooij.io/) with the MSR and it's coming along nicely so far. But cannot wrap my head around how to define custom capabilities in MQTT templates. I need this for the TTS announcements and similarly for the notification sounds where I would pass the sound file as parameter. So this is what I have in the local_mqtt_devices.yaml capabilities: x_sonos_announcement: attributes: actions: speak: arguments: text: type: string volume: type: int delay: type: int And this is the template: templates: sonos-announcement: capabilities: - x_sonos_announcement actions: x_sonos_announcement: speak: topic: "sonos/cmd/speak" payload: expr: > { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" } type: json So the speak action should send something like this to topic sonos/cmd/speak { "text": "message goes here", "volume": 50, "delayMs": 100, "onlyWhenPlaying": false, "engine": "neural" } At startup the MSR seems to be quite unhappy with my configuration: reactor | [latest-25016]2025-02-09T08:19:59.029Z <MQTTController:WARN> MQTTController#mqtt entity Entity#mqtt>sonos-announcement unable to configure capabilities [Array][ "x_sonos_announcement" ] reactor | i18n: missing fi-FI language string: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | i18n: missing fi-FI language string: Configuration for {0:q} has unrecognized capability {1:q} in actions reactor | Trace: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | at _T (/opt/reactor/server/lib/i18n.js:611:28) reactor | at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:125:25) reactor | at MQTTController.sendWarning (/opt/reactor/server/lib/Controller.js:627:30) reactor | at MQTTController.start (/var/reactor/ext/MQTTController/MQTTController.js:268:26) reactor | at async Promise.allSettled (index 0) Configuration for "sonos-announcement" has unrecognized capability "x_sonos_announcement" in actions Controller: MQTTController#mqtt Last 10:21:37 AM Configuration for "sonos-announcement" is incomplete because the following requested capabilities are undefined: x_sonos_announcement Controller: MQTTController#mqtt Last 10:21:37 AM This is probably a pretty stupid question and the approach may not even work at all, but maybe someone or @toggledbits for sure, could point me to the right direction. Basically the idea is to be able to send TTS messages from reactions using entity actions. I've previously used HTTP requests to Sonos HTTP API (https://hub.docker.com/r/chrisns/docker-node-sonos-http-api/) for the same functionality, but since moving to sonos-mqtt, I need a way to send the TTS notifications using MQTTController. Along with the actual message, volume and delay must also be parameterizable. br, mgvra MSR latest-25016-d47fea38 / MQTTController [0.2.24293]
Multi-System Reactor
[SOLVED]Hass websocket falsely reporting ready on boot??
V
Hi, @toggledbits I just noticed that following a reboot of my raspberry pi, some of the rules, that I was expecting to recover, are not catching up following a reboot. I have made a simple test rule (rule-m6rz6ol1) with only "after Date/time" as trigger and "turn on a lamp" as a set reaction. All my infrastructure is on the same board so Reactor, Hass, Zwavejs, ... are all rebooting. Here is the sequence of the test case (All time converted to Zulu to match logs): Rule "after Date/Time" set to 14:05:00z Shutdown on Raspberry Pi at 14:04:00z Power back up at 14:08:00z Rule overview shows true as of 14:08:14z waiting for 00:00:00 in GUI From the log I can see that MSR is picking up the rule and knows that the state of the rule has changed from false to true and tries to send the update to HASS but failed with websocket error. Here is what I see from the log: 14:04:04z shutdown complete 14:08:08z Power up 14:08:13.111z websocket connection 14:08:15:323z Reaction to the light failed, Websocket not opened After there is a series of websocket connection attempt until 14:08:51z where it seemed to be really ready. Back in 2021 we had a discussion (https://smarthome.community/topic/700/solved-start-up?_=1738766986566) and you proposed to add a startup_delay:xxxx and startup_wait:xxxx parameter in the engine section of "reactor.yaml". When I try the startup_delay (this used to be a hard delay), the engine failed to start (I think). I then try the startup_wait:xxxx without any success. Since it wait for the connection status to be up to cancel the delay, it does not do anyting since Hass is reporting the socket up without really being up ( I think...). Questions: Did I figured it all wrong? should the startup_delay:xxxxx have worked? Any ideas? Here is the log: OK now I am stuck. I did add the log but when I submit the editor complained saying that I am limited to 32767 characters. The log from the shutdown to the time the websocket is stable is about 300000 character long. What are my options?
Multi-System Reactor

SOLVED: Use of multiple Hubitat hubs with MSR

Scheduled Pinned Locked Moved Multi-System Reactor
13 Posts 3 Posters 653 Views 3 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.
  • MikeReadingtonM Offline
    MikeReadingtonM Offline
    MikeReadington
    wrote on last edited by MikeReadington
    #1

    Hello Everyone,

    I currently use two Vera units in two structures, but am I able to use multiple Hubitat units with MSR as well?

    I added a second Hubitat in another building, set it up as I setup up the first Hubitat, but I cannot seem to get it to connect. I have verified many times the correct URL and token is populated. Any ideas?

    [latest-22069]2022-03-18T21:41:39.108Z <HubitatController:NOTICE> HubitatController#hubitatshop not ready; performing initial connect/query
    [latest-22069]2022-03-18T21:41:39.185Z <HubitatController:ERR> HubitatController#hubitatshop failed to connect/query http://10.10.10.86/apps/api/1: [FetchError]FetchError: request to https://10.10.10.86:5001/?access_token=798a073c-4021-43e3-9da7-c5c4ac4f141a failed, reason: certificate has expired
    [latest-22069]2022-03-18T21:41:39.186Z <HubitatController:CRIT> FetchError: request to https://10.10.10.86:5001/?access_token=798a073c-4021-43e3-9da7-c5c4ac4f141a failed, reason: certificate has expired
    FetchError: request to https://10.10.10.86:5001/?access_token=798a073c-4021-43e3-9da7-c5c4ac4f141a failed, reason: certificate has expired
    
    

    Thanks!

    G 1 Reply Last reply
    0
    • MikeReadingtonM MikeReadington

      Hello Everyone,

      I currently use two Vera units in two structures, but am I able to use multiple Hubitat units with MSR as well?

      I added a second Hubitat in another building, set it up as I setup up the first Hubitat, but I cannot seem to get it to connect. I have verified many times the correct URL and token is populated. Any ideas?

      [latest-22069]2022-03-18T21:41:39.108Z <HubitatController:NOTICE> HubitatController#hubitatshop not ready; performing initial connect/query
      [latest-22069]2022-03-18T21:41:39.185Z <HubitatController:ERR> HubitatController#hubitatshop failed to connect/query http://10.10.10.86/apps/api/1: [FetchError]FetchError: request to https://10.10.10.86:5001/?access_token=798a073c-4021-43e3-9da7-c5c4ac4f141a failed, reason: certificate has expired
      [latest-22069]2022-03-18T21:41:39.186Z <HubitatController:CRIT> FetchError: request to https://10.10.10.86:5001/?access_token=798a073c-4021-43e3-9da7-c5c4ac4f141a failed, reason: certificate has expired
      FetchError: request to https://10.10.10.86:5001/?access_token=798a073c-4021-43e3-9da7-c5c4ac4f141a failed, reason: certificate has expired
      
      

      Thanks!

      G Offline
      G Offline
      gwp1
      wrote on last edited by
      #2

      @mikereadington I could be reading that wrong, but it looks like it's unhappy with the token. Have you tried recreating the token on the second Hubitat?

      I'm using two Hubitats on one MSR and it works without a hitch. I did do the original recommendation of a second Maker API instance but @toggledbits advised that's no longer really necessary.

      What does your configuration look like in reactor.yaml?

      *Hubitat C-7 2.4.1.151
      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

      *HASS 2025.3.4
      w/ ZST10-700 fw 7.18.3

      *Prod MSR in docker/portainer
      MSR: latest-25082-3c348de6
      MQTTController: 24257
      ZWave Controller: 25082

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

        Url should not be https

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

        G MikeReadingtonM 2 Replies Last reply
        0
        • toggledbitsT toggledbits

          Url should not be https

          G Offline
          G Offline
          gwp1
          wrote on last edited by
          #4

          @toggledbits Totally missed that. 😕

          *Hubitat C-7 2.4.1.151
          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

          *HASS 2025.3.4
          w/ ZST10-700 fw 7.18.3

          *Prod MSR in docker/portainer
          MSR: latest-25082-3c348de6
          MQTTController: 24257
          ZWave Controller: 25082

          1 Reply Last reply
          0
          • toggledbitsT toggledbits

            Url should not be https

            MikeReadingtonM Offline
            MikeReadingtonM Offline
            MikeReadington
            wrote on last edited by MikeReadington
            #5

            @toggledbits I get that, but I don't have HTTPS populated in the config. It looks like it checks HTTP, fails, then tries HTTPS.

            Here is my config.

              - id: hubitat
                enabled: true
                implementation: HubitatController
                name: A Hubitat Elevation system
                config:
                  # Copy the entire URL from the Maker API app page on your Hubitat UI. A quick, easy way is to
                  # right-click the "Get All Devices" link and choose "Copy link location", the paste it below.
                  source: "http://10.10.10.85/apps/api/3/devices?access_token=1afd6778-a2ed-4323-9e81-f4e570d20082"
                  #
                  # dump_all_devices - This is for troubleshooting. Do not enable unless asked.
                  dump_all_devices: false
                  
              - id: hubitatshop
                enabled: true
                implementation: HubitatController
                name: Hubitat Elevation system
                config:
                  # Copy the entire URL from the Maker API app page on your Hubitat UI. A quick, easy way is to
                  # right-click the "Get All Devices" link and choose "Copy link location", the paste it below.
                  source: "http://10.10.10.86/apps/api/1/devices?access_token=798a073c-4021-43e3-9da7-c5c4ac4f141a"
                  #
                  # dump_all_devices - This is for troubleshooting. Do not enable unless asked.
                  dump_all_devices: false
            
            
            1 Reply Last reply
            0
            • toggledbitsT Offline
              toggledbitsT Offline
              toggledbits
              wrote on last edited by toggledbits
              #6

              None of this is adding up for me. You log previously shows that an attempt to connect on HTTPS is being made, and at that to the very unusual port 5001, yet your config (at least, what you've shown, which is only partial -- the error is for the controller config you have not shown us), shows HTTP and no port number. HubitatController handles the source URL very simply, and it contains no insertion of a port number (and 5001 specifically) anywhere in the code. Nor does HubitatController attempt both HTTP and HTTPS; it uses what you give it (and it expects HTTP only). So unless this is coming from hidden config, I have no idea where it's coming from. There's something more to your environment that you've disclosed here; I don't have enough information to provide you any further guidance, but based on what you've shown, in a normal (LAN, everything directly connected on the same network segment) environment this should just work as presented. But again, this isn't a complete picture, as the most vital information (config for the hub that actually is causing the error message you posted) isn't here.

              EDIT: Apologies! I could not see the scroll bar on the config (off screen) on the device I'm using. I see the config for that second unit. Still, no port number. No idea where https or 5001 is coming from; these are not things HubitatController does. This isn't adding up. Hmm... is the hub redirecting? Do you have some app or setting that is forcing a redirect to HTTPS?

              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
              • MikeReadingtonM Offline
                MikeReadingtonM Offline
                MikeReadington
                wrote on last edited by
                #7

                Thanks Patrick,

                Apologies are never necessary with me. You're on vaca, and this stuff isn't exactly running a nuclear power plant. 🙂

                The MSR installation is about as vanilla as it could be. Docker on Synology, latest version, standard ports, with nothing optional added to it. The config file contains 3 Vera units (2 production, 1 test), 1 Hubitat (hopefully 2 at some point), and a weather subscription.

                The network topology is also straightforward. MSR and this Hubitat are connected to the same physical switch with no VLANs in this segment. The range of 10.10.10.8X is what I use for automation devices, all devices are "on device" statically assigned, and those IPs are not within the range of the DHCP server. (I did also verify there is no duplication of IPs)

                The first Hubitat (2.3.0.124) works with no issues. That unit is in service with devices and whatnot. (the Hub Information driver/device is installed)

                The second Hubitat was taken out of the box, updated to 2.3.0.124, and I installed the Hub Information driver/device and the Maker API. I changed the MSR config to reflect the second unit as posted above, and here we are. I changed nothing else in this unit from out of the box, and I am 100% sure the token is accurate. When I browse to the hub over HTTP, it does not redirect to HTTPS. These two units are NOT meshed together, and if you remember back, I was the guy who had my Vera units bridged, which caused me some unexpected issues in the beginnings of MSR.

                Anything I can think of that would affect the second hub should also affect the first hub, and I can't see why anything anywhere would redirect a request to HTTPS let alone an alternative port. I thought that might have been a failure model to retry with a secure connection if a failure occurred.

                I know it's not magic, so something somewhere has to be doing this. @gwp1 confirmed he is using two with no issues, so it has to be something unique to me. I have been jammed up today, but I am going to take the first unit .85 out of the config and see if second one connects alone when the first is removed. If it does not, then it has to be something with that unit specifically.

                Thanks again for trying to look at this, and thanks again for all you do with MSR.

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

                  OK, so let's back up to the beginning. Can you a screen shot of the local access URLs from the Maker API on the new hub?

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

                  MikeReadingtonM 1 Reply Last reply
                  0
                  • toggledbitsT toggledbits

                    OK, so let's back up to the beginning. Can you a screen shot of the local access URLs from the Maker API on the new hub?

                    MikeReadingtonM Offline
                    MikeReadingtonM Offline
                    MikeReadington
                    wrote on last edited by
                    #9

                    @toggledbits Sure

                    I really hope I am not missing something stupid here

                    Screen Shot 2022-03-19 at 8.21.23 PM.png

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

                      Sigh. I have a suspicion. And this is why I made the posting guidelines (which you didn't follow, and I didn't catch/stop until followed)...

                      Are you running on a Synology NAS, or at least, you have a Synology NAS in your network?

                      Edit: And yes, indeed you did say that in a follow-up post (7 posts in, but really need to have the info in the head post, up front), but in any case, there's the answer: your NAS is answering on that IP address. I don't know if that's a duplication of the IP (you said you didn't, but it can happen), or maybe a misconfig of the container somehow, no idea how, but the redirect URL is exactly what/how the NAS would respond if you sent the Maker API query URL to the NAS IP address (I was able to confirm exactly that by doing it to my own Synology NAS). Double-check the configuration of everything. The NAS should not be answering on that IP if that's really your new hub (or maybe, your new hub should not be on that address...?).

                      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
                      • MikeReadingtonM Offline
                        MikeReadingtonM Offline
                        MikeReadington
                        wrote on last edited by
                        #11

                        Thanks Patrick,

                        I am sorry I did not include everything in the first post. I know better, and for that I apologize.

                        There is 1 Synology NAS on site with only 1 connected network interface (10G copper) and that has a static set of IP address of 10.10.10.30. There were some test containers that were deleted from the system, but I don't know if there could still be something that could exist after a container is deleted. When I get in there tomorrow I will dig around and see what I find.

                        Thanks again

                        1 Reply Last reply
                        0
                        • MikeReadingtonM Offline
                          MikeReadingtonM Offline
                          MikeReadington
                          wrote on last edited by
                          #12

                          I did not have time to get into this until today, and this is something Synology owners should know.

                          I had two test containers that were shutdown, and one of them was a test Home Assistant on .86. After deleting the container, the issue persisted. I stopped and restarted the docker service, and it worked after that. I am a little puzzled by this because the contain was in the shutdown state, but for sure that container was the issue.

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

                            Good sleuthing. That's an interesting resolution. In a way it makes sense, because I could see docker reserving the resource (a network interface and its desired address) whether the container is running or not, but it's not the obvious thing for it to do (IMO), especially given that the side-effect is to let the host OS handle requests when the guest is down. That actually seems like is has potential security implications...

                            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

                            • [Solved] Limit HA Entity in MSR
                              wmarcolinW
                              wmarcolin
                              0
                              7
                              63

                            • Reactor (Multi-System/Multi-Hub) Announcements
                              toggledbitsT
                              toggledbits
                              5
                              121
                              35.2k

                            • Disaster recovery and virtualisation
                              CatmanV2C
                              CatmanV2
                              0
                              5
                              584

                            • Remote access of Zwave stick from Z-wave server
                              CatmanV2C
                              CatmanV2
                              0
                              3
                              308

                            • Organizing/ structuring rule sets and rules
                              G
                              gwp1
                              0
                              5
                              348

                            • Moving MSR from a QNAP container to RP 5 - some issues
                              G
                              gwp1
                              0
                              5
                              298

                            • Widget deletion does not work and landing page (status) is empy
                              G
                              gwp1
                              0
                              4
                              268

                            • Need help reducing false positive notifications
                              T
                              tamorgen
                              0
                              7
                              463

                            • Deleting widgets
                              toggledbitsT
                              toggledbits
                              0
                              4
                              440

                            • MQTT configuration question
                              tunnusT
                              tunnus
                              0
                              11
                              595
                            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