All good - much appreciated.
P
powisquare
@powisquare
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
-
Z-way token Expiration -
openLuup: MQTT serverSorry - my bad. Device that's working does not have a password. I'll have another go.
Boom - all working
-
openLuup: MQTT serverYes I have - on all of them. I seem to recall, when setting up the first one, that openLuup recognised a button press. Perhaps that's how it worked. These sensors wake up on an hourly basis, but when you wake them up manually they are awake for a minute or so (it seems).
-
openLuup: MQTT serverShould have looked first ! Red highlights a win here; am seeing this ... (is there a proper way of copying and pasting?)
2021-06-12 11:10:01.904 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=492370363&Timeout=60&MinimumDelay=1500&_=1623492371898 HTTP/1.1 tcp{client}: 0x1e96db0
2021-06-12 11:10:19.108 openLuup.io.server:: MQTT:1883 connection from 192.168.1.156 tcp{client}: 0x1d97790
2021-06-12 11:10:19.152 openLuup.mqtt:: shellyht-E01A8B SUBSCRIBE to shellies/command tcp{client}: 0x1d97790
2021-06-12 11:10:19.153 openLuup.mqtt:: shellyht-E01A8B SUBSCRIBE to shellies/shellyht-E01A8B/command tcp{client}: 0x1d97790
2021-06-12 11:10:19.156 luup.shelly:83: New Shelly announced: shellyht-E01A8B
2021-06-12 11:10:19.279 openLuup.context_switch:: ERROR: [dev #83] ./openLuup/client.lua:96: missing realm or nonce in received WWW-Authenticate header
2021-06-12 11:10:19.280 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/announce : ./openLuup/client.lua:96: missing realm or nonce in received WWW-Authenticate header
2021-06-12 11:10:19.393 openLuup.server:: request completed (1891 bytes, 1 chunks, 17488 ms) tcp{client}: 0x1e96db0 -
Z-way token ExpirationUpdated openLuup to v. 21.6.8 yesterday. I notice the z-way bridge has lost connection. and requires login. When I go to device/actions there is no way to enter credentials - only a login button.
-
openLuup: MQTT serverThe first Shelly I tried worked with the bridge created and device created in the Shellies room. The next ones also appear in openLuup/Servers/Received Connections list but don't appear as devices. Have I missed a step?
-
openLuup: MQTT serverOMG. Genius. Many thanks indeed! Note to self - for Shelly .. Internet & Security/Advanced - Developer Settings/Enable MQTT
-
openLuup: MQTT serverWill I need to set ports or do anything in Lua Startup still?
-
openLuup: MQTT serverHi guys - just received some Shelly H & Ts. Is there any documentation on how to connect these to mqtt (in novice speak
)? Have read the thread but am getting slightly confused - do I need just the openluup mqtt server or another plugin also? -
ubiquiti breachDid you ever get a certificate on to your controller? Would love to get Let's Encrypt on but I wonder if they are making it difficult so people go for their cloud solution.
-
Secure/Horstmann thermostat/zwayNot using the button - don't really know what it does.
-
Secure/Horstmann thermostat/zwayThanks, only difference is Brand; I have Horstman (Secure), all versions and command classes are the same. I get the same error using openLuup interface too. Think this is the part where setpoint is accepted. Do you use the button for anything?
[2021-03-22 09:05:40.517] [D] [zway] SETDATA devices.42.data.lastReceived = 0 (0x00000000)
[2021-03-22 09:05:40.517] [I] [zway] Node 42:0 CC Wakeup: Wakeup notification
[2021-03-22 09:05:40.517] [D] [zway] SETDATA devices.42.instances.0.commandClasses.132.data.lastWakeup = 1616403940 (0x60585de4)
[2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.data.isAwake = True
[2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.data.lastSendInternal = **********
[2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.data.lastNonceGet = 47091702 (0x02ce8ff6)
[2021-03-22 09:05:40.518] [D] [zway] Running wakeup handler for node 42
[2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.instances.0.commandClasses.132.data.lastSleep = 1616403940 (0x60585de4)
[2021-03-22 09:05:40.518] [I] [zway] Node 42:0 CC Wakeup: Send node to sleep
[2021-03-22 09:05:40.518] [I] [zway] Adding job: Wakeup Sleep
[2021-03-22 09:05:40.518] [D] [zway] SENDING (cb 0xfc): ( 01 0D 00 13 2A 06 43 01 01 22 00 6E 05 FC 3B )
[2021-03-22 09:05:40.525] [D] [zway] RECEIVED ACK
[2021-03-22 09:05:40.527] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2021-03-22 09:05:40.528] [D] [zway] SENT ACK
[2021-03-22 09:05:40.528] [D] [zway] Delivered to Z-Wave stack
[2021-03-22 09:05:40.548] [D] [zway] RECEIVED: ( 01 18 00 13 FC 00 00 02 00 B0 7F 7F 7F 7F 01 01 03 00 00 00 00 02 01 00 00 BA )
[2021-03-22 09:05:40.548] [D] [zway] SENT ACK
[2021-03-22 09:05:40.548] [I] [zway] Job 0x13 (ThermostatSetPoint Set): Delivered
[2021-03-22 09:05:40.549] [D] [zway] SendData Response with callback 0xfc received: received by recipient
[2021-03-22 09:05:40.549] [D] [zway] SETDATA devices.42.data.lastSendInternal = **********
[2021-03-22 09:05:40.549] [D] [zway] SETDATA devices.42.data.lastSend = 47092706 (0x02ce93e2)
[2021-03-22 09:05:40.549] [D] [zway] Job 0x13 (ThermostatSetPoint Set): success
[2021-03-22 09:05:40.549] [I] [zway] Removing job: ThermostatSetPoint Set -
Secure/Horstmann thermostat/zwayThanks - yes from zway basic interface.
-
Secure/Horstmann thermostat/zwaySeems to be working fine except I get an error notification via email 'Error during perform command execution: Error: Invalid argument' every time setpoint is changed from controller. Also does anyone know if the 'Button' child is useful?
[2021-03-22 09:00:03.113] [I] [core] --- ZWayVDev_zway_42-0-67-1 performCommand processing: {"0":"exact","1":{"level":"11"}}
[2021-03-22 09:00:03.113] [D] [zway] SETDATA devices.42.instances.0.commandClasses.67.data.1.setVal = 11.000000
[2021-03-22 09:00:03.114] [I] [zway] Adding job: ThermostatSetPoint Set
[2021-03-22 09:00:03.114] [I] [zway] Adding job: ThermostatSetPoint Get
[2021-03-22 09:00:03.114] [I] [zway] Node 42:0 CC ThermostatMode: Thermostat Mode 1 is not supported by device (modemask 0x0)
[2021-03-22 09:00:03.117] [I] [core] Notification: error (module): Error during perform command execution: Error: Invalid argument
[2021-03-22 09:00:03.125] [I] [core] Error: Invalid argument
at Error (native)
at t_vDev.(anonymous function).self.controller.devices.create.handler (automation/modules/ZWave/index.js:5540:62)
at .extend.performCommand (automation/classes/VirtualDevice.js:365:25)
at ZAutomationAPIWebRequest..extend.performVDevCommandFunc (automation/ZAutomationAPIProvider.js:442:51)
at ZAutomationAPIWebRequest.handlerFunc (automation/ZAutomationAPIProvider.js:3976:30)
at ZAutomationAPIWebRequest.ZAutomationWebRequest.handleRequest (automation/WebserverRequestRouter.js:250:35)
at automation/WebserverRequestRouter.js:32:29
at WebServer.document_root (automation/Webserver.js:40:31)
[2021-03-22 09:00:03.130] [I] [core] HK: updated ZWayVDev_zway_42-0-67-1
[2021-03-22 09:00:03.137] [D] [zway] RECEIVED: ( 01 18 00 13 F0 00 00 05 01 C4 7F 7F 7F 7F 00 00 03 2E 00 00 00 03 01 00 00 EB ) -
Why Migrate to Z-way from vera and how?+1 for zway
-
altUIMay well be different machines, differing firmwares. Frustrating nevertheless. Here's a stab at displaying variables.
-
altUIThanks - will have to try tomorrow - can't risk sending vera in to a tiz with guests staying.
-
altUICan i set them to (0,0) as the (5,1) misbehaves?
-
altUISorry I was conflating issues. I have (a) two thermostats on separate veras that have different jsons and (b) one of those thermostats is shown above has the same json as another thermostat (on zway) but different functionality. Kinda got that muddled.
-
altUISeems odd that it's two different jsons for the same thermostat on separate veras. Perhaps the issue is inherently an altui one anyway. When I use the up down arrows for temp setpoint it starts from the cooling setting ie in this case 0 so its a lot of clicking to get to 20.
The same model thermostat paired to zway displays and behaves correctly with no cooling temps.
But they have the same json?
