P
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.
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!
Found the branch selection in altappstore.
Now i have scene variables too, and it works fine. thanks.
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.
Did this:
@rafale77 said in z-way-server ubuntu install:
The problem is that libcurl3 is not in the standard repo you have listed.
assuming you are on ubuntu download it from here: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.debdownloading from the norwegian mirror for x64
Then run
dpkg -i libcurl3_7.58.0-2ubuntu2_amd64.debmight 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.3Note that you will need to find where your libcurl library was installed. I just gave you the ubuntu location.
and
Good luck with Hass, and not in the ironic way.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.
There is an additional license for the Z-Way software, but I would say it is well worth it. My experience is that it's extremely stable (haven't crashed once in the years i've had it), and the control of the network through the expert panel is probably the best you can find.
The "Smart Home" UI is not great, but it doesn't matter much if you're using openLuup.
I finally reached the finishline for the move-to-docker project!
All applications are now inside dockers, communicating on the internal docker network.
This makes updates easy - just update to a newer docker image. (or update in the app, in the openLuup case)
Backup is done by copying the docker volumes to an SSD along with the indluxDB.
Restore to any machine running docker is in principle just attaching the USB devices - install ser2net, and running one docker-compose file. Everything is set up and ready to go. Tested on an Ubuntu installed machine, and it works!
This will offcourse take a bit more disk-space, havent summed it up yet.. But i have no plans on running this on machines with tiny storage anyway.
One thing i'd like to improve is to get the UZB into Ser2net as well, with the advantage of accessing it from my test-system as well. Z-Way unfortunately can't take IP-serial without Socat? mabye in later updates.
I made this sketch to keep track of the system in progress, it might be usefull to others?
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?
After about 7 years in the Vera/openLuup world i've now moved on to a home assistant installation. This was rather reluctantly, as openLuup has served me well with very few issues (other than ones I created myself off course!). A big thanks to @akbooer and all contributors for all the good work with this software!
The main reason for jumping the fence to HASS was in short all the integrations and UI possibilities. The device handling for Zigbee and RFXtrx is also developing to be really good, and is still maintained.
There is still plenty of annoying bugs/imperfections with HASS, but the maturity is at a level where most of what I need works well enough.
My system is now:
So far so good!
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
@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 think so, yes. As simple as possible, unless we loose functionality, which i don't think is the case here?
Isn't the vera updates based on polling? if so, it will only be updated at that interval.. I think the approach used in domoticz bridge is better, with some script on the host (domoticz in that case) yelling to the bridge on changes..
Haven't touched my system for a while (or read updates here), busy with other projects..
Just have to mention that I updated to the latest today and found the new entity selector tool... LOVE it! That has been my only nagging thing about reactor since vera reactor, all that scrolling..
Thanks, @toggledbits, this is really turning into something VERY good!
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!
I just gave up waiting for the HASS Z-wave.me integration to finish, and set up Zwave JS UI instead. In the same operation, all zigbee and 433 devices was moved from openluup to HASS as well, so all devices now have a new address.
I thought I saw some "replace device" function in MSR earlier, but now I didnt find it?
I've done a lot of the changes manually now, and removed openluup as a system, but at every restart I still get the warning/errors about the old units. I assume it's because rules ask for them? This is where that "replace this with this" would come in handy..
Right now, my problem is that the rules i did update doesn't pull any levers in HASS. If I go in and run the action line in the rule manually, it works, but only with the arrow button on the actual action, not the common arrow button in "set reaction".
Any tips/hints on making this transition easier is much appreciated.