I'll check out Telegram and Pushover. Thanks for the suggestions.

If anyone else is running Dockers on unRaid and wants instructions for Installing Reactor, see below.

Installing Multi-system Reactor in a unRaid Docker Notes. 01/22/22

unRaid Version 6.9.2

Preparation:

Based on Generic Notes from:

Installation - Reactor - Multi-Hub Automation

Typically for Generic (modify with username below):

docker run --name reactor -d --restart on-failure -p 8111:8111
-v /home/username/reactor:/var/reactor
--mount type=bind,src=/etc/localtime,target=/etc/localtime
toggledbits/reactor:latest-generic-amd64

Create a Share called "reactor" and use "Prefer Cache" if cache drive is available.
Under SMB settings - Export = Yes so that you can edit config files. Set security per your needs.

Go to the Docker tab click Add Container and click Advanced View for additional settings.

Enter:
Name = reactor

Overview = Reactor (Multi-system, aka MSR) is an automation engine for multiple home automation systems. It allows you to develop automations that respond to and control devices across platforms. For example, you could have a motion sensor on a Hubitat controller used as a trigger for set of lights, some of which are connected through a VeraPlus and some through HomeAssistant.

Please see https://reactor.toggledbits.com/docs for more information.

Repository = toggledbits/reactor:latest-generic-amd64
For Latest otherwise choose a specific version

Docker Hub URL = https://hub.docker.com/r/toggledbits/reactor

No icon path has been found

WebUI = http://[IP]:[PORT:8111]/

CPU Pinning as you see fit.

Network Type = Bridge
Console shell command = Shell

WebGUI = http://[IP]:[PORT:8111]/

Extra Parameters = --restart=on-failure

Click Add another Path, Port, Variable, Label or Device.
Choose Path -
Name = data
Container Path = /var/reactor
Host Path = /mnt/user/reactor (previous share path)
Access = Read/Write
Display = Always
Required = No
Password Mask = No

Click Add another Path, Port, Variable, Label or Device.
Choose Port -
Name = Host Port 1
Container Port = 8111
Host Port = 8111
Default Value = 8111
Type = TCP
Description will auto populate with "Container Port: 8111" once Saved
Display = Yes
Required = Yes
Password Mask = No
Save

Click Add another Path, Port, Variable, Label or Device.
Choose Variable -
Name Key 1
Key = UMASK
Val and Default = 100
Description will auto populate
Display = Yes
Required = No
Password Mask = No
Save and repeat adding Variables for below:
Key 2: Container Variable: PUID = 99
Key 3: Container Variable: PGID = 100

Click Apply

Script should look similar to:

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='reactor' --net='bridge' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8111:8111/tcp' -v '/mnt/user/reactor/':'/var/reactor':'rw' --restart=on-failure 'toggledbits/reactor:latest-generic-amd64'

The command finished successfully!

Notes:

• The docker manager script will add the Time Zone based on unRaid's config.
• If variables (uid/gid <> 99/100) then you must run the "New Permissions" script under Tools
  and select the User Share reactor otherwise the Reactor files will be R/O except for the Docker container.
• WebUI Access = "http://[your NAS IP]:8111"
• Follow the reactor configuration documentation for your Hub(s).

Regards

Greetings,

I’m researching a migration from Vera+ to Hubitat C7 and want to know if anyone has successfully connected the Hubitat to the “HA Bridge” for local Alexia calls.
The HA Bridge does not callout Hubitat natively from what I see.

Thanks for your assistance.

Thanks for the quick reply.
I have facebook blocked (not a fan) and I see google.com so that must be the back up.
I don't see any option to change under the main reactor variables tab but I can live with google getting pinged.

Yes, decoupled and loving it. I'm running Syslog now and have the VERA logs and backups ftp'd locally now so many thanks. I had no idea how busy the VERA device was until you look at the logs. Actually its sad to see it checking to rotate logs every minute and scanning for network devices... but I digress.
I'll go back to the docs. I do recall you writing about it, thanks again.

Wild guess but I wonder of MSR is looking for the "Hub Information" app that is tied to a virtual device in Hubitat. MSR uses that to check the connection heath of the Hubitat Controller.

@3rdstng Thanks for the feedback and link to an icon. I'll save that off and put it local.
One note - I try to avoid “privileged” mode for containers. It allows it to run containers with (almost) all the capabilities of their host machine, regarding kernel features and device access.

Regards

It was the latest version (22021). It was running fine but doing "npm audit fix --force" and the command you requested broke it.
To get it running again I reinstalled node.js and ran the Reactor setup scripts but I didn't like having the audit issues so I'm off of Windows now, deleted the Service and moved to a Docker.

Thanks for your quick replies but you can pass on my Windows install issue.

If anyone else is running Dockers on unRaid and wants instructions for Installing Reactor, see below.

Installing Multi-system Reactor in a unRaid Docker Notes. 01/22/22

unRaid Version 6.9.2

Preparation:

Based on Generic Notes from:

Installation - Reactor - Multi-Hub Automation

Typically for Generic (modify with username below):

docker run --name reactor -d --restart on-failure -p 8111:8111
-v /home/username/reactor:/var/reactor
--mount type=bind,src=/etc/localtime,target=/etc/localtime
toggledbits/reactor:latest-generic-amd64

Create a Share called "reactor" and use "Prefer Cache" if cache drive is available.
Under SMB settings - Export = Yes so that you can edit config files. Set security per your needs.

Go to the Docker tab click Add Container and click Advanced View for additional settings.

Enter:
Name = reactor

Overview = Reactor (Multi-system, aka MSR) is an automation engine for multiple home automation systems. It allows you to develop automations that respond to and control devices across platforms. For example, you could have a motion sensor on a Hubitat controller used as a trigger for set of lights, some of which are connected through a VeraPlus and some through HomeAssistant.

Please see https://reactor.toggledbits.com/docs for more information.

Repository = toggledbits/reactor:latest-generic-amd64
For Latest otherwise choose a specific version

Docker Hub URL = https://hub.docker.com/r/toggledbits/reactor

No icon path has been found

WebUI = http://[IP]:[PORT:8111]/

CPU Pinning as you see fit.

Network Type = Bridge
Console shell command = Shell

WebGUI = http://[IP]:[PORT:8111]/

Extra Parameters = --restart=on-failure

Click Add another Path, Port, Variable, Label or Device.
Choose Path -
Name = data
Container Path = /var/reactor
Host Path = /mnt/user/reactor (previous share path)
Access = Read/Write
Display = Always
Required = No
Password Mask = No

Click Add another Path, Port, Variable, Label or Device.
Choose Port -
Name = Host Port 1
Container Port = 8111
Host Port = 8111
Default Value = 8111
Type = TCP
Description will auto populate with "Container Port: 8111" once Saved
Display = Yes
Required = Yes
Password Mask = No
Save

Click Add another Path, Port, Variable, Label or Device.
Choose Variable -
Name Key 1
Key = UMASK
Val and Default = 100
Description will auto populate
Display = Yes
Required = No
Password Mask = No
Save and repeat adding Variables for below:
Key 2: Container Variable: PUID = 99
Key 3: Container Variable: PGID = 100

Click Apply

Script should look similar to:

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='reactor' --net='bridge' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8111:8111/tcp' -v '/mnt/user/reactor/':'/var/reactor':'rw' --restart=on-failure 'toggledbits/reactor:latest-generic-amd64'

The command finished successfully!

Notes:

• The docker manager script will add the Time Zone based on unRaid's config.
• If variables (uid/gid <> 99/100) then you must run the "New Permissions" script under Tools
  and select the User Share reactor otherwise the Reactor files will be R/O except for the Docker container.
• WebUI Access = "http://[your NAS IP]:8111"
• Follow the reactor configuration documentation for your Hub(s).

Regards

I ran that and now the Reactor Windows Service Terminates unexpectedly.

*** I was able to install MSR in a Docker on unRaid so the details below are for your reference only as I plan on uninstalling Reactor in Windows. ***

Event Log Shows - ''Child process [7664 - C:\Program Files\nodejs\node.exe C:\reactor\node_modules\node-windows\lib\wrapper.js --file C:\reactor\app.js --scriptoptions= --log "Reactor wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n --stopparentfirst undefined] finished with 1''

''C:\reactor>npm i --no-save --omit dev
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'jsdoc@0.0.0',
npm WARN EBADENGINE required: { node: '~v0.4.10' },
npm WARN EBADENGINE current: { node: 'v16.13.1', npm: '8.1.2' }
npm WARN EBADENGINE }

removed 5 packages, and audited 90 packages in 1s

12 packages are looking for funding
run npm fund for details

1 high severity vulnerability

To address all issues (including breaking changes), run:
npm audit fix --force

Run npm audit for details.''

Greetings,

I'm not a Docker expert hence the choice of using unRaid but I would like to install MSR in a Docker and I'm looking for details on the settings used as I have not installed one manually yet.

I have installed MSR on Windows Server 2019 but I'm receiving (3 vulnerabilities (1 low, 2 high)) error messages with 'npm' and the audit fix breaks it ('npm').

Thanks for any help you can provide.

David

@therealdb Good point, I'll look into Hubitat's interfacing option more closely. I know that MSR is using a Hubitat "Maker" API to call device changes.

Thanks for the responses but I was hoping to keep the system local (not Amazon cloud) by using the HA Bridge like I have connected to Vera (https://www.bwssystems.com/#/habridge).
The developers of the HA-Bridge added Hubs such as Vera and Home Assistant + others but left out Hubitat.
I have it running on a Pi 3B and it acts as a bridge between to Alexia exposing the devices on Vera and making calls to the Hub based on voice commands.

Greetings,

I’m researching a migration from Vera+ to Hubitat C7 and want to know if anyone has successfully connected the Hubitat to the “HA Bridge” for local Alexia calls.
The HA Bridge does not callout Hubitat natively from what I see.

Thanks for your assistance.

Yes, decoupled and loving it. I'm running Syslog now and have the VERA logs and backups ftp'd locally now so many thanks. I had no idea how busy the VERA device was until you look at the logs. Actually its sad to see it checking to rotate logs every minute and scanning for network devices... but I digress.
I'll go back to the docs. I do recall you writing about it, thanks again.