Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off
Cheers
C
C
CatmanV2
@CatmanV2
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
-
HA 2025.9.4 Supported Yet? -
[Reactor] Variables not updating correctly in latest-25201-2aa18550 -
[Reactor] Variables not updating correctly in latest-25201-2aa18550Fabulous effort here by @toggledbits We owe a great deal!
C
-
Expose MSR entities -
Expose MSR entities@toggledbits this is precisely what it is, yes
C
-
Expose MSR entitiesSorry I tried to make it clear. For the avoidance of doubt the original post should (and shortly will) read
'Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great.'C
-
Expose MSR entitiesYes that was stupid of me! Sorry!
said in Expose MSR entities:
Currently I am using the owntracks_sensor for tracking phones being in region in
MSR! Not HA!
So the owntracks_sensor exists in MSR and works great. I'm wondering if there's an easy way to expose to HA
What a buffoon
C
-
Expose MSR entitiesProbably 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
-
Little Bobby tables... -
Home Assistant Voice TTS is Easy -
Home Assistant Voice TTS is EasyI must have missed something in the Voice preview set up then as I can't get TTS working (at least from the test situation)
I might try from your stateC
-
Little Bobby tables......is back....
Researchers design “promptware” attack with Google Calendar to turn Gemini evil
The team behind the research has worked with Google to mitigate the attack, but what comes next?
C
-
Home Assistant Voice -
Home Assistant Voice@akbooer I just don't get it. I guess it's less effort to make a video than actually write down the instructions. Sure, for somethings they can be useful but a 15 minute video for a 5 minute config. Grrr!
C
-
Home Assistant VoiceOK, so digging through stuff. Definite progress. I've got an OpenAI integration running, but just been told that 'Max output tokens reached' which seems a little odd as I've used precisely $0.01
Must go out now!
C
-
Home Assistant Voice -
Home Assistant VoiceCheers! I shall try and make some time
(Is it just me that hates having to watch videos? Can't we just have instructions written down? )C
-
Home Assistant VoiceGiven I'm starting from zero on this particular path it would be interestting to see how you set it up. Took me about 90 minutes to get a light to turn on! The documentation I've found so far is, well, poor
TIA
C
-
Home Assistant Voice@akbooer I have Alexa that works really well for most voice control, but doesn't interact with HA. I have virtual switches in OpenLuup that are exposed HA bridge, so effectively I simply ask to flip a switch and the automation follows.
The exception is my Logitech Elite hubs which integrate with Alexa directly (and also work really well)
@toggledbits that would be awesome. I'm keen on the more interactive stuff (i.e. where the VA prompts for activity)
Certainly I can make Alexa speak, but a simple 'yes' or 'no' response isn't going to get anything from her.
C
-
Home Assistant VoiceWell, so far so 'OK' Took a fair while to set up. One of the wake phrases absolutely does not work for me 'Hey Jarvis'
I think getting all the devices I have decent aliases so it knows what to control may take some time.
Local processing on a VM with 2 CPUs and 4G of RAM is pretty slow. Takes about 10 seconds to action an switch and fails to understand about 20% of the time. Hybrid is much faster.
Audio quality of the voice response is really not great. There are plenty voices to chose from, but none of them as polished as Alexa (so far)I think I have much to learn so not writing it off just yet.
C