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. Home Assistant, ReferenceError: auth is not defined
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
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
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
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

Home Assistant, ReferenceError: auth is not defined

Scheduled Pinned Locked Moved Multi-System Reactor
14 Posts 3 Posters 847 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.
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #2

    Looks like you are using the wrong kind of access token. The instructions specify that you have to use a long-lived access token, and these are usually very long on Hass. Yours is very short (at least, much shorter than the LLATs I've seen on my own system). Did you use a Long-Lived Access Token?

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

    A 1 Reply Last reply
    0
    • toggledbitsT toggledbits

      Looks like you are using the wrong kind of access token. The instructions specify that you have to use a long-lived access token, and these are usually very long on Hass. Yours is very short (at least, much shorter than the LLATs I've seen on my own system). Did you use a Long-Lived Access Token?

      A Offline
      A Offline
      Andr
      wrote on last edited by Andr
      #3

      @toggledbits said in Home Assistant, ReferenceError: auth is not defined:

      Looks like you are using the wrong kind of access token. The instructions specify that you have to use a long-lived access token, and these are usually very long on Hass. Yours is very short (at least, much shorter than the LLATs I've seen on my own system). Did you use a Long-Lived Access Token?

      The lengts seems random I think.
      I did 3 tokens, first one super long.
      When it didn't work i created another one, in first post.
      Now I created the third one, and this became super long, and it works.

      No idea why, long-lived tokens is the only I can create...
      50d5ecea-25ff-49d6-a78d-84f13feafef5-image.png

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

        Hi! My HA does not connect either. I get a "websocket error" over and over again. This is my reactor.yaml:

          - id: hass
    enabled: true
    implementation: HassController
    name: Home Assistant
    config:
      source: 'ws://192.168.50.167:8123'
      access_token: "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI0ZDg4MzVjZmJkMjQ0ODYwODZhYzc1ZTExZDk2MGU1OSIsImlhdCI6MTYxNTczMzMyMSwiZXhwIjoxOTMxMDkzMzIxfQ.eMGyHpM"
        1 Reply Last reply
        0
        • F Offline
          F Offline
          Fanan
          wrote on last edited by
          #5

          In CMD it looks like this:
          2021-03-14T15:20:27.492Z HassController:NOTICE HassController#hass attempting reconnection to ws://192.168.50.167:8123/api/websocket
          2021-03-14T15:20:27.492Z HassController:NOTICE HassController#hass connecting to ws://192.168.50.167:8123/api/websocket
          2021-03-14T15:20:27.501Z HassController:WARN HassController#hass socket error during open: Error: socket hang up
          2021-03-14T15:20:27.502Z HassController:NOTICE HassController#hass socket to ws://192.168.50.167:8123/api/websocket closed during open
          2021-03-14T15:20:27.505Z HassController:ERR HassController#hass connect error with ws://192.168.50.167:8123/api/websocket: websocket error
          2021-03-14T15:20:27.505Z HassController:WARN HassController#hass failed to connect/initialize communication: websocket error

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

            Make sure you have the websocket API enabled in your Hass configuration.

            Home Assistant

            Home Assistant WebSocket API

            Home Assistant WebSocket API

            Instructions on how to setup the WebSocket API within Home Assistant.

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

              Thanks. I stupid newbie question... I guess I should add this line to configuration.yaml:
              websocket_api:

              But what else?

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

                That's all that's necessary. I also add the documented sensor lines so I can see how many connections are active, but it's not strictly necessary to functionality.

                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
                • F Offline
                  F Offline
                  Fanan
                  wrote on last edited by
                  #9

                  I'm afraid it doesn't work @toggledbits. Shouldn't there be anything after the ":", an IP-adress or something?

                  toggledbitsT 1 Reply Last reply
                  0
                  • F Fanan

                    I'm afraid it doesn't work @toggledbits. Shouldn't there be anything after the ":", an IP-adress or something?

                    toggledbitsT Offline
                    toggledbitsT Offline
                    toggledbits
                    wrote on last edited by toggledbits
                    #10

                    @fanan said in Home Assistant, ReferenceError: auth is not defined:

                    Shouldn't there be anything after the ":", an IP-adress or something?

                    If you are referring to the "websocket-api:" line in your Home Assistant configuration, no, that line stands by itself. It needs to be properly formatted and placed in your HomeAssistant configuration file. Check your HomeAssistant log for any errors related to its configuration file.

                    Oh, and just to make sure I've asked, are you keeping up with the builds? Are you testing on the latest build?

                    Ref: https://www.home-assistant.io/integrations/websocket_api/

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

                      Ah - I didn't understand that I had to install the websocket_api. I thought it was enough to edit the configuration.yaml-file.
                      Now I'm going to figure out how to install...

                      1 Reply Last reply
                      0
                      • F Offline
                        F Offline
                        Fanan
                        wrote on last edited by
                        #12

                        @toggledbits ; Just a stupid question, since I´m kind of new to this.... Do I have to install the websocket api? I have HACS installed and have tried to add it to the custom resporitories. I tried to add the URL:

                        core/homeassistant/components/websocket_api at dev · home-assistant/core

                        core/homeassistant/components/websocket_api at dev · home-assistant/core

                        :house_with_garden: Open source home automation that puts local control and privacy first. - home-assistant/core

                        and a few more URL as well... But I only get: "Repostitory structure for 2021.3.4 is not compliant", or something else if I try other URL:s.
                        I don't want to waste your time with these newbie questions, but after hours and days of failure, I´m becoming desperate... 🥴

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

                          I just installed Hass via docker, and all I needed to do was add that line to my Hass config and generate the Long-Lived Access Token and everything connected right up. I've never had a problem connecting to Hass, and I didn't have to install anything additional. This is what my configuration file looks like:

                          # Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

http:
  server_host: 0.0.0.0

websocket_api:

sensor:
  platform: websocket_api

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

                          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
                          • F Offline
                            F Offline
                            Fanan
                            wrote on last edited by
                            #14

                            @toggledbits. My HA installation is on a VM (VirtualBox) on Windows 10. That shouldn't be problem I guess?

                            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

                            • Advice reqeusted to migrate MSR from Bare Metal to Container
                              T
                              tamorgen
                              0
                              5
                              37
                            • Reactor (Multi-System/Multi-Hub) Announcements
                              toggledbitsT
                              toggledbits
                              5
                              122
                              35.4k
                            • Z-Wave Future....
                              CatmanV2C
                              CatmanV2
                              0
                              5
                              130
                            • Can´t restart or upgrade/deploy MSR
                              toggledbitsT
                              toggledbits
                              0
                              4
                              85
                            • [Solved] Limit HA Entity in MSR
                              wmarcolinW
                              wmarcolin
                              0
                              7
                              191
                            • Disaster recovery and virtualisation
                              CatmanV2C
                              CatmanV2
                              0
                              5
                              659
                            • Remote access of Zwave stick from Z-wave server
                              CatmanV2C
                              CatmanV2
                              0
                              3
                              383
                            • Organizing/ structuring rule sets and rules
                              G
                              gwp1
                              0
                              5
                              374
                            • Moving MSR from a QNAP container to RP 5 - some issues
                              G
                              gwp1
                              0
                              5
                              345
                            • Widget deletion does not work and landing page (status) is empy
                              G
                              gwp1
                              0
                              4
                              338
                            • Need help reducing false positive notifications
                              T
                              tamorgen
                              0
                              7
                              520
                            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