-
Hello Everyone -
I have a peculiar situation that I'm hoping to get some help with.
Running Vera which is still handling my Zwave, MySensors, Zigbee, and still a balance of my Reactors.
However, I've also been running MSR for several months in preparation for an eventual move off of Vera.
Vera had one of its meltdowns this morning related to my Opensprinkler plug in.
After getting that straightened out, I added the OpenSprinkler plugin to HAAS and that's when I started having issues.
My existing MSR reactors (even simple ones) don't seem to fire their reactions. I can see the conditions go "true". If I manually fire the Reaction, it works fine.
I do see this a lot in the logs:
[1.0.2-21350]2022-05-16T19:02:44.518Z <Rule:INFO> Rule#rule-460 evaluation in progress; waiting for completion(Various rules - 460 is just an example)
Is there anything I can do to further troubleshoot?
-
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. -
My MSR has been working flawlessly until a couple of days ago when it stopped sending Telegram Messages (or should I say they stopped getting through!). I have updated to MSR version 22004. The reactor.log is updating and is showing no errors:
[latest-22004]2022-05-15T17:52:31.417Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
[latest-22004]2022-05-15T17:52:31.417Z Engine:INFO Message Test all actions completed.
[latest-22004]2022-05-15T17:52:31.704Z Engine:INFO Enqueueing "Message Test" (re-l37h2fkj)
[latest-22004]2022-05-15T17:52:31.735Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
[latest-22004]2022-05-15T17:52:31.736Z Engine:INFO Message Test all actions completed.
[latest-22004]2022-05-15T17:52:32.007Z Engine:INFO Enqueueing "Message Test" (re-l37h2fkj)
[latest-22004]2022-05-15T17:52:32.035Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
[latest-22004]2022-05-15T17:52:32.036Z Engine:INFO Message Test all actions completed.
[latest-22004]2022-05-15T17:52:41.324Z Engine:INFO Enqueueing "Variable Telegram Test" (re-kvnm57c3)If I use the following in my web browser the telegram message gets through:
https://api.telegram.org/botxxxxx......./sendMessage?chat_id=xxxxx......&text=Test Message HTTPS
I am running MSR on my QNAP network attached storage. Any assistance would be appreciated.
Just another question...... I would like to post in the HOME HARDWARE VERA section of Smarthome, but I do not have the option to set up a new post. Do I need to request access for this?
-
Details of runtime environment:
Reactor (Multi-hub) stable-22055-9b40e12 Running as a service on Windows Server 2022 Std 21H2 Connecting to HASS (HASSOS) Is a migration WIP from OpenLuup/ReactorA complete description of your objective:
Using LetsEncrypt, application "certifyTheWeb", retrieve and apply SSL certificate to Multi System ReactorA description of your approach/solution/implementation so far:
Reviewed Config files, can't seen mention of certificate files in thereActual Question:
How do I apply a certificate to whatever web server Reactor uses? I'm familiar with managing certificates on IIS and Apache but Reactor doesn't use either of these and I have not been able to locat ethe config file that Reactor uses for this. Which config file needs editing to apply a certificate? Does it use the computer certificate store or it's own store (e.g. pem files)The reason I want to achieve this, other than the general goodness of having everything I can in TLS is that I have Reactor as an IFRAME in my HASS console and as HASS is HTTPS and Reactor is HTTP then the iframe refuses to open.
Search for "certificate" or "ssl" did not reveal anything relevant in this forum.
-
@toggledbits
Hi Patrick,
Running HASS 2022.5.3
MSR zwavejs-22126-834c3e9Seeing weird behavior in MSR with regards to my Zen32's. Not sure how to capture info that might be relevent but will describe what I am seeing.
In the example below I pressed scene 001 4 times. It flashed and changed the primary value to "4". The remaining buttons were previously showing the PV as "double" I pushed each button one time and they flashed and displayed the PV as 4.
zen32.JPGIn the zwavejs2mqtt debug screen that sequence looks like this.
2022-05-10 09:38:44.078 INFO ZWAVE: Node 45: value notification: 91-0-scene-001 5 2022-05-10T16:38:44.081Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x898501" } 2022-05-10 09:38:45.982 INFO ZWAVE: Node 45: value notification: 91-0-scene-002 0 2022-05-10T16:38:45.984Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8a8002" } 2022-05-10 09:38:47.807 INFO ZWAVE: Node 45: value notification: 91-0-scene-003 0 2022-05-10T16:38:47.810Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8b8003" } 2022-05-10 09:38:48.858 INFO ZWAVE: Node 45: value notification: 91-0-scene-004 0 2022-05-10T16:38:48.861Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8c8004" }Let me know what other info you would like me to supply.
I have played around with a bunch of other key stroke combo's and it looks like buttons 2-5 display what ever button 1 is set to.
Have tested this on 4 different ZEN32's and it is same on all. -
Running zwavejs-22118-baab576 in MSR, HASSOS 2022.5.1
Due to an unreported issue in HASS, when I upgraded the 2022.5 yesterday, it dropped ZwaveJS2MQTT from my HASSOS build. Finally got it reinstalled and it appears to be working the way it was previously.
MSR is now showing zwavejs down and in entities, nothing is updating.Seeing this in the logs:
ZWaveJSController#zwavejs ws_open caught [Error]Error: connect ECONNREFUSED 192.168.0.16:3000Are there additional steps needed that are not mentioned in the manual?
At a loss to figure out what is causing issue. -
Hi!
After several tests, restarting the computer where the MSR is, and the MSR itself by Tools > Restart, I have a persistent error in the logs.
32d45bc3-51f8-4718-a113-3381e9d7edf2-image.png
Looking at the global expression (screen below), I see that it is highlighted as an error, however, if I look at two other expressions above that have the same structure, they do not present an error, so I do not think the problem is with the expression's code.
ca8a7867-4ac7-4f9a-9913-15a80da18f05-image.png
This expression uses a group, which validates 4 devices of type door sensor, whether the status is true or false, door open or closed.
"dgc_entrance_open": name: DGC Entrance Open select: - include_entity: - "hubitat>37" - "hubitat>38" - "hubitat>99" - "hubitat>130" filter_expression: > entity.attributes?.door_sensor?.state == trueI also compared it with other groups, the structure is identical.
Looking at the 4 devices in this group, I see that all are active in the MSR, have similar variables, are used in other groups and rules that do not present a problem.
52b099f4-b9c4-46cb-ad3d-c873b09b7e13-image.png
Looking at the log, I understand that it refers to some object that would be null, at which point I am lost on what to actually look at.
[latest-22118]2022-05-02T22:33:11.711Z <Engine:INFO> Reaction Engine starting [latest-22118]2022-05-02T22:33:11.719Z <Engine:INFO> Checking rule sets... [latest-22118]2022-05-02T22:33:11.746Z <Engine:INFO> Checking rules... [latest-22118]2022-05-02T22:33:11.748Z <Engine:INFO> Data check complete; no corrections. [latest-22118]2022-05-02T22:33:11.892Z <Engine:ERR> [Engine]Engine#1: error evaluating expression EntranceOPEN: [ReferenceError]ReferenceError: Invalid scope in reference to member attributes of (object)null [latest-22118]2022-05-02T22:33:11.893Z <Engine:ERR> [Engine]Engine#1: expression: sort(each id in ( getEntity('groups>dgc_entrance_open').attributes.sys_group.members ): getEntity(id).name) [latest-22118]2022-05-02T22:33:11.894Z <Engine:CRIT> ReferenceError: Invalid scope in reference to member attributes of (object)null ReferenceError: Invalid scope in reference to member attributes of (object)null at _run (C:\MSR\reactor\common\lexp.js:1449:31) at _run (C:\MSR\reactor\common\lexp.js:1443:33) at _run (C:\MSR\reactor\common\lexp.js:1443:33) at _run (C:\MSR\reactor\common\lexp.js:1536:38) at _run (C:\MSR\reactor\common\lexp.js:1480:33) at C:\MSR\reactor\common\lexp.js:1283:29 at Array.forEach (<anonymous>) at _run (C:\MSR\reactor\common\lexp.js:1282:28) at run (C:\MSR\reactor\common\lexp.js:1663:22) at Object.evaluate (C:\MSR\reactor\common\lexp.js:1699:20) [latest-22118]2022-05-02T22:33:12.232Z <Engine:NOTICE> Reaction Engine running! [latest-22118]2022-05-02T22:33:12.233Z <Rule:INFO> Rule#rule-kxjp2el2 (Mode DAY) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjp7kc8 (Mode EVENING) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjparz7 (Mode NIGHT) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjpd0d6 (Mode AWAY ∆) started [latest-22118]2022-05-02T22:33:12.235Z <Rule:INFO> Rule#rule-kxjqrcr9 (Mode PARTY) started [latest-22118]2022-05-02T22:33:12.235Z <Rule:INFO> Rule#rule-kxjqyhnu (Mode VACATION ∆) startedFinally, if I return the expression and press the Try This Expression button, it is executed and the error disappears.
102e5013-b9aa-4c26-98f5-1ae545f8897f-image.png
This situation started to occur on the latest version of Reactor 22118, on a Windows 10 Bare Metal installation. Does anyone have a similar scenario?
Sorry for the long post, I tried to document as best as possible to try to identify the problem.
Thanks.
-
Please can anyone give me advice on a cheap way to run MSR (both initial cost and ongoing electricity cost). I currently run it on my QNAP network drive (which works very well incidentally). However, this draws a constant 35Watts (£90/yr @ 30p/kWh) and given the recent rise in fuel costs I am evaluating the best way forwards. Note, I only really need to turn my QNAP on for an hour a week to back-up my computer data. I understand that MSR can run on a Raspberry PI, but I am not competent with Linux! Thanks.
-
I just noticed that the new hotness picked up the entities from when I added an integration temporarily to my Home Assistant and popped a lovely info notice into the Alerts pane.
I know the info is new - but when did MSR suddenly become more real-time with devices being added to hubs? This is great!
-
Noticed in the last few nights that my Global Reaction to turn on a mere six lights in the evenings the same two devices no longer turn on. One is a dimming smart bulb, the other is a wall outlet.
This has been running flawlessly for months - just in the last few nights I've noticed these two devices being left behind and yes, it's always these two devices only.
"What changed?"
No Hubitat firmware updates No new devices added to Hubitat list itemTwo MSR updates (the last two, I keep up with the latest) list itemHome Assistant releases (should have zero bearing, HA is nothing more than pretty dashboards) list itemAdded MQTT to MSRI did do a z-wave "repair" last night and am waiting to see if this helps.
Is there any maximum or cap on number of devices that should be included in a Global Reaction?
*Marked as solved as the question asked was answered. The issue persists but the question was answered.
-
I've borked my install of reactor-latest-22118-0f0772c.tar.gz for some reason and am retracing steps. Running npm i --no-save --omit dev prompted to update npm and I did (current version now 8.6.0). Currently, attempts to load via browser/s (Brave and Safari) result in "This site can’t be reached192.168.1.xxx refused to connect." I am still able to SSH into the RPi.
I haven't panicked yet but did just pull my config and storage directories - I believe I read where that's enough for a back-up if a clean install ends up being needed.
So the question of the day: which version of nmp should we be running on for the latest Reactor?
-
I’ve looked and can’t find the answer which concerns me that the answer is obvious and thats why I can't find the answer to this.
I’m new to MSR and this is my first post, so please bare with me 🙂
What I’m trying to do is have a global expression that contains the current time so I can use it in Global reactions as well as Rulesets as part of my syslog messages.
Example of what I’m experiencing:
In Expressions, create a global expression: gMyTOD = strftime("%T %D”)
In Rulesets, in a rule, create a local expression: MyTOD = strftime("%T %D”)In that same rule create a Notify type of Syslog.
Set syslog message to: gMyTOD time is ${{gMyTOD}} and MyTOD time is ${{MyTOD}}
Trigger the rule.The result is that the local expression (MyTOD) contains the correct time but the global expression (gMyTOD) does not update and reflects the wrong time in the final syslog message.
Is there a different approach I should be using?
Thank you in advance for any insight.
-bh
-
Hi!
What's the easiest and most effective way to make this work? Do I ping a few websites every ten minutes or so, or is there a better approch? If I'm going to ping, what URL is recommended?
Once a month or so, my internet access is lost, and I have to cut the power to the router, to restart it. When I'm away this become a problem, so I thought that if I got a zigbee switch (in Home Assistant), problem is solved. But how do I (MSR) know if it's offline?For information, I have a set up with Asus routers, Home Assistent with zigbee-, z-wave and wifi devices (a total of appr. 150) and every of my 60-70 automation is done by MSR.
I run MSR ver. 22080-ae7212f (docker on my Home Assistant blue). HA ver 2022.4.6.
Thanks in advance.
Take care, you all!
/Fanan -
-
So, I have a rule set that it's triggered when a local variable changes. Since it's tied to my solar production, it could change very frequently, so I've just added a reset delay to calm it down, but it's not working as intended.
What I really need is a way to, let's say, define a percentage and define a variable to understand if the new value has changed +/- 10% before going true.
I've tried a couple of ways, but I'm posting here anyway, in case anyone has found a better way to tackle this. Thanks!
-
Perhaps a dumb question. Can I check from Home Assistant that MSR is up and running? I would like to see that in a status page in HA. I can of course ping the other Pi but it doesn't say anything about the MSR status.
-
@toggledbits Is there a way to get Current Alerts as an entity so I could monitor those and send notifications if needed.
My usecase is sometimes openLuup crashes and MSR picks that up pretty quick, sending a pushover notification to me would get my attention to restart it.
Of course there are many ways to monitor connectivity but since MSR already is doing that it would be neat to take advantage of it. -
Hey @toggledbits.
From the docs:You cannot control the state of rules via MQTT. Rule state is driven exclusively by the result of its conditions.
And I'm OK when rules are triggered by something else, but I've built a couple of rules to be used by other rules, to streamline the logic, and it'll be useful to invoke a rule via MQTT. It's probably close to what rule/:id/restart is doing in the HTTP api.
Thanks!
-
I'm trying to create some automation so I can control my pool variable speed pump from reactor rather than iAqualink (which sucks). My controller is MQTT enabled so I created several scripts for my desired speeds. (I know reactor has MQTT ability but honestly I read the docs and could not make much sense of it and since I already have it set up in Home Assistant, I figured I would just leverage that instead)
So I created all of my scripts and tested them, they worked perfectly. The I created a rule in reactor and set running the script as the action. The problem is that reactor is telling me that I have to make a selection. I try to click the dropdown and there is nothing to select. I cant save the rule, the only option is to exit.
9e0a3147-5058-4893-9860-2f0d759dfe3c-image.png
Here is my script in Home Assistant. Any advice on how to get this to work? If I am looking at this the wrong way I am open to suggestions (I would rather be able to call a specific action and specify a speed value but I cannot figure out how to do that). Thanks in advance.
-
Hi, I've been using msr for a while now and haven't had timezone issues until today when I updated to latest docker image (latest-22080-ae7212f)
both docker date command and my local date command show the same time, same timezone, but for some reason MSR shows the host time as 2 hours in the past as a result all my timed rules run 2 hours late.
my locale is set correctly in the host machine and is bound into the container as well.
One possible hint I get is maybe this from the container startup log, but other than timezone stuff everything else seems to be working fine and all my settings loaded up just fine.
[latest-22080]2022-04-07T07:52:52.423Z <SystemController:null> Module SystemController v22080 root {} CommonJS loading [latest-22080]2022-04-07T07:52:57.236Z <Engine:CRIT> SyntaxError: Unexpected end of JSON input SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at IndividualFileStrategy.getDataObject (/opt/reactor/server/lib/IndividualFileStrategy.js:121:46) at Container.getDataObject (/opt/reactor/server/lib/Container.js:102:53) at new GlobalExpression (/opt/reactor/server/lib/GlobalExpression.js:105:179) at Function.getInstance (/opt/reactor/server/lib/GlobalExpression.js:123:89) at /opt/reactor/server/lib/Engine.js:1349:67 at Array.forEach (<anonymous>) at Engine.initializeGlobalExpressions (/opt/reactor/server/lib/Engine.js:1345:145) at Engine.start (/opt/reactor/server/lib/Engine.js:590:285) at /opt/reactor/app.js:362:103Let me know if I can provide further info to help debug this.
Thanks
MSR in Alpine Docker
-
I have a docker running smoothly now, thought i'd share it. (and BTW, it looks awesome, Patrick!)
So far i've only opened 8111, and /config as volume. Mabye the full /reactor folder should be exposed for easy updating?docker compose:
version: "3.9" services: MSR: container_name: MSR restart: always image: perhu/msr-alpine:latest ports: - "8111:8111" networks: HAnett: ipv4_address: 192.168.0.8 volumes: - type: bind source: /etc/localtime target: /etc/localtime - type: volume source: MSR-config target: /etc/reactor/config - type: volume source: MSR-storage target: /etc/reactor/storage logging: driver: "json-file" options: max-file: "5" max-size: 10m networks: HAnett: name: HAnett driver: bridge ipam: config: - subnet: 192.168.0.0/16 gateway: 192.168.0.254 volumes: MSR-config: name: MSR-config MSR-storage: name: MSR-storage
dockerfile for those who want to modify the image: (this works if you have unzipped MSR zip file to the same folder as the dockerfile)
FROM alpine:latest COPY /reactor/. /etc/reactor/ RUN apk add --update nodejs npm && cd /etc/reactor \ && npm install --loglevel error --no-save \ && cp dist-config/* config/ VOLUME ["/etc/reactor/config"] VOLUME ["/etc/reactor/storage"] EXPOSE 8111 CMD ["/bin/sh"] WORKDIR /etc/reactor CMD ["node", "/etc/reactor/app.js"]
EDIT: 20210307 - updated with localtime bind
-
Per, there's also a storage folder that should be a volume or bind mount.
-
Added. (havent uploaded new image to dockerhub yet though).
Thanks.
-
@LibraSun asked about MSR docker on synology in another thread. I don't know whats special on synology as i don't hvae one, but this is how you can do it on other linux systems (and please correct me if something's wrong in the write-up, im still learning here!):
Start by downloading reactor from the bugtracker place and unzip it to an appropriate folder on the NAS called "/.../reactor/"
Edit your /reactor/config/reactor.yaml with the appropriate settings
In the same folder you have the /reactor/ sub folder, create a textfile called "dockerfile" (no extension)
paste this in:FROM alpine:latest COPY /reactor/. /etc/reactor/ RUN apk add --update nodejs npm && cd /etc/reactor \ && npm install --loglevel error --no-save \ && cp dist-config/* config/ VOLUME ["/etc/reactor/config"] VOLUME ["/etc/reactor/storage"] EXPOSE 8111 CMD ["/bin/sh"] WORKDIR /etc/reactor CMD ["node", "/etc/reactor/app.js"]
save & close, and then type
docker build -t your/image:version .
Then you can make a docker-compose like mine in the above post, or you can use run command:
docker run -p 8111:8111 your/image:version
Note: @toggledbits prefers to keep control over MSR distribution through the alpha/beta testing, so publishing on dockerhub is not an option. You can have private repositories there as well in order to transfer an image between machines easily.
-
I'm just putting finishing touches on the first Synology container. I'm going with the approach that it can be configured and started from the UI, which helps with the var data and config. I had to add a way to redirect (or really, prefix) those directories, as well as some additional initializations (which I'm working on at this moment). I'll probably still make composer an option for folks that are OK with command line into their NAS. Once the container has been created, it's low-maintenance. My Dockerfile appears below, for your review (proof-read/code check, if you like, I'm new to docker).
FROM node:alpine # Where Reactor lives in the container ENV REACTOR_HOME="/opt/reactor" # Container stores all variable data under /var ENV REACTOR_DATA_PREFIX="/var/reactor" # ENV NODE_ENV=production # Default port ENV PORT=8111 # Creates directory if doesn't exist WORKDIR ${REACTOR_HOME} LABEL description="Reactor (Multi-System)" LABEL version="###BUILDVERSION###" LABEL copyright="Copyright (C) 2020,2021 Patrick H. Rigney, All Rights Reserved" LABEL cicd="reactor" COPY reactor/app.js ./ COPY reactor/client ./client/ COPY reactor/common ./common/ COPY reactor/dashboard ./dashboard/ COPY reactor/dist-config ./dist-config/ COPY reactor/INSTALL.md ./ COPY reactor/LICENSE.md ./ COPY reactor/package.json ./ COPY reactor/reactorui ./reactorui/ COPY reactor/server ./server/ WORKDIR ${REACTOR_HOME}/docs/html COPY reactor/docs/html ./ WORKDIR ${REACTOR_HOME} RUN rm -rf node_modules && npm install --loglevel error --no-save WORKDIR ${REACTOR_DATA_PREFIX} VOLUME ${REACTOR_DATA_PREFIX} EXPOSE ${PORT} STOPSIGNAL SIGTERM HEALTHCHECK --interval=5m --timeout=15s CMD curl -f http://localhost:${PORT}/api/v1/alive || exit 1 WORKDIR ${REACTOR_HOME} CMD ["node", "app.js"]
-
This post is deleted! -
OK. Let's see how this does in your hands. I've installed and uninstalled 3-4 times and it seems OK. In the bug tracker, go to #58, in the notes you'll find a download link and draft installation instructions. You can use the "monitor" function to follow that PR (emails you when things are posted--might get chatty with a lot of people in there, though). Please use that PR for reporting install-related issues.
-
@toggledbits said in MSR in Alpine Docker:
OK. Let's see how this does in your hands. I've installed and uninstalled 3-4 times and it seems OK. In the bug tracker, go to #58, in the notes you'll find a download link and draft installation instructions. You can use the "monitor" function to follow that PR (emails you when things are posted--might get chatty with a lot of people in there, though). Please use that PR for reporting install-related issues.
This loads up nicely. Running unconfigured right now. I will transfer over my configs later and test it out.
-
nice! i'll try this later. node:alpine should be a better staring image for sure.
Only question i have is if you should nest more of the commands together to reduce number of layers. This is said to reduce both build time and image size.
i think that can be done with the copying the full reactor folder in, and then distribute the files (like you do with the multiple COPY lines) with a RUN command having several nested "cp" commands. -
just have to mention for all non-synology docker users, Portainer is a very nice UI alternative for playing with dockers without the "dreaded" command line approach.
-
@kfxo said in MSR in Alpine Docker:
@toggledbits said in MSR in Alpine Docker:
OK. Let's see how this does in your hands. I've installed and uninstalled 3-4 times and it seems OK. In the bug tracker, go to #58, in the notes you'll find a download link and draft installation instructions. You can use the "monitor" function to follow that PR (emails you when things are posted--might get chatty with a lot of people in there, though). Please use that PR for reporting install-related issues.
This loads up nicely. Running unconfigured right now. I will transfer over my configs later and test it out.
Just an update, I copied over config and storage directories to the mounted docker volume and Reactor would not start until I also created a 'logs' directory in the mounted docker volume. All looked well after that but going to continue to run it on my Debian VM for now.
-
It's supposed to (a) notice those directories and missing and create them, and (b) if (and only if) it created the config directory, copy the contents of the containers dist-config into config as a starting point. Seems to be fine on Linux, somehow not working in the container, I guess. Time to go digging...
-
Quick note about base image, I've built my image using both
node:alpine
andalpine:latest
as base image, and the former ended up being approx. 50mb bigger.
I did however not do therm -rf node_modules
from your dockerfile (as i didn't see why it was there), that may be the difference? -
Hi, I’m keen to try the Docker version on my QNAP, but I can’t find the specific guide on https://reactor.toggledbits.com/docs/Installation/ , it suggests under the Raspberry Pi install section, “If you prefer to use Docker, see the separate procedure below.’ but nothing seems to be listed ?
-
There hasn't been published a docker for this yet, I think @toggledbits wants to go through the beta phase first, as there may be many updates in a short time-frame which would have to be maintained in the docker.
You can follow the procedure i posted 5 days ago (in this thread) to make your own docker.
-
I'm just starting to look at ways to migrate away from Vera and just started working on a Home Assistant setup so I'd also love to have a go at testing this out in Docker on a QNAP but I don't really want to have to SSH into the NAS to do the docker compose, etc. I have only ever used the docker hub to add docker images but it looks like it's possible to use the QNAP container station to create a docker image locally but the steps you posted a few days ago in the thread don't seem to be in the format that the GUI needs, or I'm doing something wrong. If there aren't any QNAP gurus around I'll wait for something to come up.
-
The code above is for dockerfile. That is for making images, while docker-compose sets up containers based on images you make, or is found on docker hub.
No idea how QNAP works, you say it has input for dockerfile code? if so, the code above should work (the dockerfile code, not the compose!), its very standardized.. But unless you make the image yourself i guess you'll have to wait with MSR in docker until there is an official MSR image. -
Hi @d868, other than creating our own image, we’ll have to wait until one’s approved and then published on Docker Hub.
If it helps you I’m planning to do the same thing with MSR as I did with Home Assistant, and create a Container Station API build guide.
-
@parkerc thanks. I'm trying to avoid doing anything by command line if I can, but if you do end up creating a guide I'll see how I go with it. In the meantime I'll have a bit of a play around with Container station to see if I can get the syntax right for creating it myself via the GUI.
-
Just updated the first post.
I just noticed that Reactor time wasn't correct, and its probably because of daylight savings time here in Norway.
I put a Bind mount for/etc/localtime
in the docker-compose, and noW it will follow the host machines time.