@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
I
iRobot
@iRobot
I don't know if you guys are into dashboards, but I am.
For a second home I tried the Shelly Wall Display 2, and while not so big, it worked well over the summer.
Since we're remodeling our house, I just swapped my old Fire Tablet (with its own problems) with two new Shelly Wall Display XL. I just removed the standard firmware, and I added mine (https://github.com/dbochicchio/ShellyElevate), forked from https://github.com/RapierXbox/ShellyElevate
I just managed to support buttons (this thing has 4 of them) and it's all auto-discovered by Home Assistant and accessible via Reactor.
I also have a new build in the works with support for buttons inside HA.
I added a bonus Javascript interface sending events (screen/screensaver status, buttons, motion) to automatically drive the dashboard (all doing in HTML+Javascript and monitoring Reactor's variable).
This specifical thing excluded, go get one of them, the device has a decent CPU for HA dashboards and blends wonderfully in the decor.
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down.
I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor).
My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long
I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
https://github.com/dbochicchio/reactor-mqtt-contrib
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me.
While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users.
I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do.
Just an idea
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically.
That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button.
Example: Light 1 ON → OFF, then Light 2 ON → OFF.
The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule.
Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Use case:
When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled.
To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work.
Then another situation: the water pump system and garden irrigation, another switch.
In short, I had to create several virtual switches in Hubitat to disable rules in MSR.
Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR.
If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR.
Would it be possible to do something like this? Any recommendations from the experts?
Probably a really dumb question.
Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great.
Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly.
Any thoughts?
Apologies if the ask is not clear/
TIA
C
...is back....
https://arstechnica.com/google/2025/08/researchers-use-calendar-events-to-hack-gemini-control-smart-home-gadgets/?utm_source=facebook&utm_medium=social&utm_campaign=dhfacebook&utm_content=null&fbclid=IwY2xjawMBq-pleHRuA2FlbQIxMQABHlSqIalzbz1IxcJFzlw8GBE6nC3FwvxcHgR370nJhogU6JjqbmRxG-lysqgh_aem_lx9XboYFKw9tpHnedGQKUA
C
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well.
As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API.
Updates: (the latest versions first in the list)
OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Posts
-
Luup reload required after server reboot -
Z-Way electric meter devices not in openLuupIt'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.
- Deleting the ZWay plugin and all of it's children.
- Deleting the /etc/cmh-ludl/cgi/zway_cgi.lua and /etc/cmh-ludl/L_ZWay.lua and L_ZWay2.lua files.
- Reloading the Luup engine (this I probably forgot to do last night)
- Setting ownership on folder /cmh-ludl/cgi and all it's children to my username instead of root (not sure this is necessary)
- Installed the plugin from AltAppStore
- Downloaded the ZWay_cgi.lua from github and placed is in /etc/cmh-ludl/cgi
- Reloading the Luup engine
- Configured the IP and logon information of my ZWay
- Reloading the Luup engine
-
Auto Start z-way-serverJust 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 -
OpenLuup IP AddressThat 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
-
First post to say helloHi guys,
I just got word of this new community by community forum. Guess I'm a bit late to the party
At the moment I'm in transition from VeraPlus to a openLuup/Z-Way system.
Now I will be looking for the setting to change to darkmode
-
Adding Z-way as secondary controller to vera zwave network@therealdb That's an amazing price!
Bought my UZB1 including license for 80 EUR just a couple of weeks ago. -
Happy Birthday openLuup!Happy Birthday to openLuup!
-
Z-Way electric meter devices not in openLuupYes I do, I had to use the dev branch to get it installed in my Ubuntu VM
-
Help. Installing Reactor on Home Assistant.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.
-
z-way-server ubuntu install@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!
-
Z-Way electric meter devices not in openLuupJust 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 -
Z-Way electric meter devices not in openLuupYou 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
-
Help with Z-Way pluginI'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.