I'm still not excluded, but I think it's a matter of time until he sees the same profile picture.
I was hoping to be able to test the eZLO plus some more, but given the temperature, i'd rather stay with the "Rafael group".

Utterly flabberghasting!

Edit: And there, i'm out too. Should we count how many eZLO plus beta testers he threw out? I have one.

I finally made the Domoticz link work, and then ported all Zigbee devices to the much better zigate plugin there. No change in latency at all, very sharp responses to door and motion sensors. Happy!

This plugin has its own GUI, and is almost structurally standalone. I've contacted the developers to ask if its possible with a direct API and to run it as a service to cut domoticz out of the chain..

I can now confirm that TRADFRI and Aqara will work together just fine, with repeaters helping for both systems:

The answer was offcourse logs. I didn't put in any limit to it, so everything is stored!

Found the solution here, update the docker compose files, and on we go.

Contact!

Had to make a new token to make it work, theres no expiry of them, i hope?

Now i have to learn how to send "special" characters, it didnt even like "!".. But i don't intend to yell in my notifications anyway.

Sent one from reactor too Patrick.

To all you developer guys; Awesome job! thankyou for making this great HA system! Hope to join in on making some contributions myself.

So, the resolution to the recent errors was that the UZB Stick was set up with "Bridge" firmware! to fix, go to ExpertUI - Network - Control - Firmware - Switch to "Normal" Firmware.
I may have been blinded by the "F**k, nothing i try works", but i think this detail could be more visible to beginners in some way, i.e. a small pop-up message when you try to add sensors in a-way (which requires normal mode FW).. I will pitch this to the z-way guys.

Onwards!

Cool! I'm currently on the Docker path, so i'll be setting up one for this. Ubuntu or debian? mabye Alipne, as VWout used for Openluup?

Found the branch selection in altappstore.

Now i have scene variables too, and it works fine. thanks.

I suggest that you buy a xiaomi mi vacuum as well!

(good job!)

Did this:
@rafale77 said in z-way-server ubuntu install:

@PerH

The problem is that libcurl3 is not in the standard repo you have listed.
assuming you are on ubuntu download it from here:

Ubuntu – Details of package libcurl3 in bionic

You need to pick from the correct platform.
wget --url you can paste from the link above--

i.e

wget http://no.archive.ubuntu.com/ubuntu/pool/universe/c/curl3/libcurl3_7.58.0-2ubuntu2_amd64.deb

downloading from the norwegian mirror for x64

Then run

dpkg -i libcurl3_7.58.0-2ubuntu2_amd64.deb

might need sudo authority to install.

Edit: Another idiot way to do it is to not install libcurl3 at all and instead create a symbolic link for libcurl3 to call libcurl4 (That's how I am running mine )

sudo ln -s /usr/local/x86_64-linux-gnu/libcurl-gnutls.so.4 /usr/local/x86_64-linux-gnu/libcurl-gnutls.so.3

sudo ln -s /usr/local/x86_64-linux-gnu/libcurl.so.4 /usr/local/x86_64-linux-gnu/libcurl.so.3

Note that you will need to find where your libcurl library was installed. I just gave you the ubuntu location.

and

apt install curl
systemctl disable openluup.service
systemctl enable openluup.service
systemctl start openluup.service

up and running again. Now the appstore is OK too, commencing attempt 2 on z-way bridge.

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

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!

And I'm not fully versed in what a request handler encompasses, that may be a solution?

How about making some sort of MSR implementation in openLuup? As in having its own tab that embed's the web page? No idea about the scope of that myself, but it would definately be cool..

Not sure which category to use, but it's about external access..

I'm using Dataplicity to connect from the web to openluup, and i'd like a similar connection for MSR. Thats not something i would use on a phone, but from a laptop situated elsewhere in the world (faulty logic always appears when i'm far away from home!)

I could offcourse do the same procedure (described in the lower part of this ) for MSR, but if I colud put a link somewhere in Openluup that would take me there (like the openluup console link?) that would be easier?

Don't know if it will work to connect to a different port?

Any ideas?

Really like this app, would love to see a version for android phones too.

Forgot about the lua startup, it was there all along.
Changed it to a different number, and all is in order. Thanks.

I'm setting up an openluup system (again) at my cabin, and this time i also added the dataplicity wormhole for external access..

I still use Imperihome to handle these on my phone, but ran into trouble when trying to add another "88800000" system, which seems to be the standard ID for openluup?

Any way to change the 88800000?

Haven't been keeping track with the releases for a while, still on 096.

Is there any risk in using savedata from this old version on the newest, or can i just go ahead and update to the new docker?

Just thinking if there's any changes in savedata format or handling?

I think the main advantage of volumes is that location is controlled by docker, and these locations aren't as easy to screw up if you mess around with the folder structure.. It also puts all volumes in a common folder (var/lib/docker/volumes) that can be copied to a tar or backup folder using one line, but thats just as easy if you organize bind folders the same way.. Let me know if you find other advatages.

I have no sunrise/sunset rules, i use light sensors for i.e. outside lighting.. I think about 90% of my "MSR bugs" have been PEBCAC, so check your logic.

I'm happy to see an official docker image for MSR!

Just thought i'd share my docker-compose.yaml, which is only different in that i use docker volume instead of bind to host folder

Not sure if it's better, but i've done this to all dockers in my system.

This came up working well immediately, next is to stop the container and add my storage and config data.

version: "3.9"

services: 
  MSR:
    container_name: MSReactor 
    restart: always 
    image: toggledbits/reactor:latest-generic-amd64 
    ports:
      - "8111:8111" 
    networks:                            # Optional for use of static IP inside the docker network. 
      HAnett:                            # You could replace this and the subsequent lines with " network_mode: "bridge" "
        ipv4_address: 192.168.0.8 
    volumes:
      - type: volume 
        source: MSR 
        target: /var/reactor
      - "/etc/localtime:/etc/localtime:ro" 
    environment:
      - TZ=Europe/Oslo
      - REACTOR_DATA_PREFIX=/var/reactor
    tmpfs: /tmp
    logging:
        driver: "json-file"
        options: 
          max-file: "5" 
          max-size: 2m
networks:    #Optional
    HAnett: 
        name: HAnett
        driver: bridge
        ipam: 
            config:
                - subnet: 192.168.0.0/16 
                  gateway: 192.168.0.254 
volumes: 
  MSR: 
    name: MSR

Done !