When portainer is installed on HassOS, this is considered as a not supported HA install. This could give some trouble updating in the future.
Since you are using proxmox, I would make 2 virtual machines.
One to install HA using the HassOS script you have. And the other to install docker and portainer on which you can install MSR as explained by toggledbits.
This way you can also use docker for all other sort of projects which are not related to HA without interfering with it.
@ArcherS
That can be done by adding the following lines to your openluup.service file:
[Unit]
Description=openLuup and AltUI Server
Wants=network.target
After=network.target
At the moment I'm one of the lucky few where Vera geofencing works most of the time. In fact, that's the only function I'm using actively with my plus.
I most certainly would by interested in a local geofencing solution. I probably will be using a VPN or maybe setup a separate internal network or vlan with NAT for it.
Was planning on trying tasker or owntracks, but that's still in the idea fase in my head. 
Always good to know a new UZB is coming.
Thanks for the information.
Hopefully this will also solve the debacle of bad stick production batches which makes firmware updating a nightmare.
Other than that, to me it looks like we will have to wait for nodes which use the same LR chip to be able to fully benefit it's potential.
I'm guessing you mean the zwave.me uzb1.
No, that's still a 500 series chip.
If it's suppose to be around 65F° then it it could be a notation error. Mixing up decimal points and decimal comma
US notation 65.5 would result in 655 when the notation is not set to imperial. E.g. EU notation is 65,5.
Still doesn't explain why it changes all of the sudden though.
Happy Birthday to openLuup!
@rafale77 Thanks for these instructions.
The part I never got working properly was that libcurl4 issue.
Now it's clear to me how to address this, I will most certainly try again.
Thanks again for your work!
Had the same libcurl problems with my Ubuntu server 18.04 VM.
Ended up downloading the "Fresh Pi" image (https://razberry.z-wave.me/z-way-server/razberry.img.zip) and was up and running within a hour.
At the moment I suggest to spare yourself all that frustration and do the same.
Just wandering if a wait on network should be added.
With a pi this is done using raspi-config, but any other Linux distribution doesn't have that.
Maybe add?
[Unit]
Wants=network-online.target
After=network-online.target
That is very strange, but has nothing to do with openLuup as far as I know. I think you must look for what is causing this in your Debian or network.
Looks like you have something in your network that is redirecting your local network through the internet since 217.3.79.1 is not a private but public ip-address
I'm expecting the experts will chime in soon.
But to get you started, I will try to help with what I know.
You need to "link" the Z-Way plugin to your Z-Way "server". Because both of them run on the same RPi you only need to enter the credentials you use to login to your Z-Way. This should be the message you see on the plugin in openLuup.
Entering the credentials can be done in the plugin under actions. Enter your username and password and click on the login button.
Hope this helps.
@therealdb That's an amazing price!
Bought my UZB1 including license for 80 EUR just a couple of weeks ago.
You are being to hard on yourself. You are already doing great work!
And easier would be nice to see, but that's a work in progress.
Even I was able to get it up and running, that's best advertising you can get 
It's working.
Thanks to @akbooer and @rafale77 for helping!
After experimenting again this morning it's working.
The CGI is showing information now and the Greenwave is including power monitoring in openLuup.
Basically I did what was follow the instructions from last night and this morning.
Deleted the ZWay plugin and removed the CGI and L_ZWay files, checked all child devices are deleted also and checked room 101.
After installing the ZWay plugin the CGI file is missing in /etc/cmh-ludl/cgi.
I retried several times using the appstore from both ALTUI and openLuup console.
To make sure its not some linux or user rights problem I even set /etc/cmh-ludl to 777.
I just set my VM back from a snapshot and will be trying again tomorrow. Time to go to bed now
Ok, will delete the ZWay plugin and go from there.
@rafale77 Hopefully this is what you need
Just to be sure I checked the openLuup version. Was running v2020.04.17 but now I'm updated to 2020.05.01
Pretty sure that's the latest version 
