[SOLVED] New iblind and zwaveJScontroller/MSR not communicating

[toggledbits]

Well, it's July 19th, and as previously advertised, Reactor (Multi-System, aka MSR) has been published at release 1.0.0.

Docker images are on DockerHub, and download package for bare-metal installs is available at https://reactor.toggledbits.com/download/

Those of you with access to the Mantis Bug Tracker for the project, please continue to use it, particularly if you stick with the "latest" docker image tag (which will continue to be updated periodically, as will the bare-metal tarball). Feel free to open issues there on behalf of other users who do not have accounts if it seems appropriate.

[PerH]

Haven't been able to do much helping on this for a while, but after installing the release docker, and moving the rest my automation to MSR i feel the need to say:
GOOD JOB!
Especially to Patrick, but also to all contributors.

Automation is now very fast and intuitive to set up, and I still havent found anything i can't do with this. No bugs as far as i've seen yet either!

[toggledbits]

Thanks, @PerH , and indeed, a lot of effort by many went to get it this far. And miles to go before (we) sleep...

[gwp1]

@toggledbits +1 for the Robert Frost reference.

[Buxton]

@toggledbits I was able to install the container through compose, however, I had to make some changes to get it working. See below for my compose file:

 MSR:
  container_name: reactor
  image: toggledbits/reactor:latest-generic-amd64
  restart: "on-failure"
  environment:
   REACTOR_DATA_PREFIX: /var/reactor
   TZ: America/Los_Angeles
  expose:
   - 8111
  ports:
   - 8111:8111
  volumes:
   - /home/username/reactor:/var/reactor
   - /etc/localtime:/etc/localtime:ro
  tmpfs: /tmp
#  logging:
#   driver: "json-file"
#   options:
#    max-file: 5
#    max-size: 2m

The changes I made are:
1.) substitute "MSR" for "web" for the service name. This was just a precaution against a generic service name interfering with container management programs I use, and was not a needed/critical change to get things working.
2.) simplify the volume syntax for binding a data volume. The syntax you have on your website caused a yaml compile error with version: '3.7' compose.
3.) comment out the logging options. These options compiled, but threw a runtime JSON error that stopped the container from coming up:

ERROR: for MSR  Cannot create container for service MSR: json: cannot unmarshal number into Go struct field LogConfig.HostConfig.LogConfig.Config of type string
ERROR: Encountered errors while bringing up the project.

I hope to cut out some time next week to start forming some logic. The web UI looks great.

[PerH]

There will be some syntax differences for different versions of compose, but I would suggest that you reinstate the logging options in order to control/restrict the storage space the container uses for logs.

[tunnus]

Just installed 1.0.0 (21200), which seems to run fine on Debian chroot. Didn't find "reactor.service-example" file that was supposed to be included in the installation package?

EDIT: found an example from documentation, but it turned out that you cannot run systemctl under chroot

@toggledbits or anyone, any advice on running sysinit style startup script?

[noelab]

Hi everybody!
I was following this web site as non-member. Finally I have a new Synology Nas to try the new @toggledbits 's reactor project and this post is first of all to thank @toggledbits for his effort and passion to share his projects and to make them accessible even for those who are not a programmer. I know many of you reading the posts from the vera community and would like to express my gratitude for the advice you give to understand things. So a big Thanks and congratulations to Patrick for this new project !!!
I just installed MSR and I am excited to try it out!

[Buxton]

@buxton Just a follow-up to the docker compose file I listed above. The error I received for the logging option occurred because I used an integer for the "max-file" field. The proper notation should be:

  logging:
    driver: "json-file"
    options:
      max-file: "5"
      max-size: 2m

Also note that for the logging section only, there are two spaces for the indents instead of one . YAML is unforgiving with formatting, so this too was corrected in my YAML file