Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
J

jaywll

@jaywll
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
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
Multi-System Reactor
[Reactor] Help with screne controller cycling logic
therealdbT
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.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
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?
Multi-System Reactor
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
Expose MSR entities
CatmanV2C
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
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
Multi-System Reactor
Little Bobby tables...
CatmanV2C
...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
General Discussion
Home Assistant Voice TTS is Easy
toggledbitsT
Topic thumbnail image
Home Assistant
Play Audio through Home Assistant Voice Unit
toggledbitsT
Topic thumbnail image
Home Assistant
Home Assistant Voice
CatmanV2C
Has anyone had a play with the local voice control for HA? I've got one on order because... https://www.home-assistant.io/voice-pe/ C
Home Assistant
Unofficial thread for compatibility
tunnusT
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.
Multi-System Reactor
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can't customize home page
G
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page. Once logged back in I can no longer remove errant panes nor is the + available to add new ones. Brave Browser v1.80.122 (Jul 16, 2025) What have I done?! Will check other browsers on my M1. UPDATE: Safari exhibits same behaviour. I've tried both sans last-four public key entry and with - no change.
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
About
Posts
4
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Ezlo Plus as Network Attached Zigee & Z-Wave Device
    J jaywll

    The Zooz stick and the Ezlo share a common Z-Wave chipset. In fact when I added the Ezlo to ZWave-JS it shows up with a product code of ZST10-700, which I believe is the Zooz stick.

    So, good news! I have both Z-Wave and Zigbee working in home assistant now, bypassing all the Ezlo software. The home assistant Zigbee integration connects directly to the Ezlo, and for Z-Wave I have ZWave-JS as an intermediary - but that's hass' recommended configuration anyway.

    I think I've figured out some initial stability issues I was having as a result of not setting socat up quite right, but don't quote me on that yet, and for some reason the status of the Z-Wave controller shows up as 'Dead' but it doesn't seem to matter? Not sure what that's about. Also if I start hass before the Ezlo is ready then it will never successfully connect - you have to run socat on the Ezlo first, then start Home Assistant. Other than that it seems to work well. Zigbee in particular is more stable and responsive in this configuration than it was on the sonoff zigbee bridge I was previously using in my setup.

    Here's how I did all this:

    • Using the instructions on the openWrt site, compile socat for the Allwinner H3 SoC (or, if you're feeling trusting, download the binary I already compiled).
    • Copy the .ipk to the Ezlo using whatever method you prefer. I used scp. Unfortunately you can't download the binary directly to the Ezlo because it doesn't support SSL and I don't have anywhere I can share the file from that doesn't enforce secure connections.
    • Install it:
      opkg install socat_1.7.3.3-1_arm_cortex-a7_neon-vfpv4.ipk
    • Kill the running ezlo processes: (One single error at the end about a process that can't be killed because it doesn't exist is expected).
      ps | grep "/ha-" | cut -b1-5 | xargs -t kill
    • Share the Z-Wave and Zigbee radios over the network using socat:
      socat /dev/ttyS1,raw,echo=0 tcp-listen:3333,reuseaddr,keepalive,fork &
      socat /dev/ttyS2,raw,echo=0 tcp-listen:3300,reuseaddr,keepalive,fork &
    • In Z-Wave JS' ZWave settings under serial port, ignore the choices in the dropdown menu and manually enter tcp://192.168.0.100:3333 (change the IP to that of your Ezlo)
    • In Home Assistant's Zigbee integration select a radio type of EZSP and for the serial port enter socket://192.168.0.100:3300
    • ...
    • Profit

    If you reboot the Ezlo it returns to its stock setup. I think my plan is to write a little script that checks whether the Ezlo processes are running and, if so, kills them and starts socat, then run that script as a cronjob. @rafale77, do you have any advice on a better approach based on your Nuke-Vera work? I don't want to nuke the Ezlo and do anything irreversible necessarily, but I'm also a little concerned that my plan might be leaving the thing functional enough to one day download a firmware update that breaks what I'm doing.

    If it's helpful to anyone, I also compiled binaries for ser2net (I never got it to work) and Nano.

    Vera

  • Ezlo Plus as Network Attached Zigee & Z-Wave Device
    J jaywll

    @rafale77 thanks! I've discovered something else encouraging too. At the top of the Ezlo Z-Wave log is a line that says
    Z-Wave stick based on EFR32ZG14 is supported

    A quick search reveals the EFR32ZG14 is a silicon labs Z-Wave 700 chip that seems to be pretty ubiquitous, and according to comments on a couple of closed github issues on the Z-Wave JS repo, it seems like it is already supported. That's at least enough motivation for me to want to keep going 😄

    I'm definitely going to play around with openLuup some more. I actually don't have any scenes or automations on the Vera, that's all in Home Assistant. HA automations have seen some big improvements recently, but you're right that they're playing catch-up in that regard. I've been considering taking Node-RED for a spin too.

    Vera

  • Ezlo Plus as Network Attached Zigee & Z-Wave Device
    J jaywll

    I don't have openLuup. I gave it a try this afternoon, running it in a docker container. I didn't need to set up anything with mqtt, I just used the home assistant Vera integration to connect to openLuup, then used the Vera bridge plugin to connect openLuup to my existing Vera edge, and the Ezlo bridge plugin to connect it to my new Ezlo. There was some odd behaviour with both bridge plugins running at once and the brightness sliders for my dimmer switches don't work quite right, but all my devices show up in Home Assistant with this setup and I'm sure with some tweaking I could get this working. This may be the way to go, so thanks for the recommendation @Elcid!

    In the meantime, I've been pursuing my original plan despite what I've got no doubt is excellent advice that you gave me, @rafale77. I started with Zigbee rather than Z-Wave, and it's been a frustrating afternoon. I took a look in /dev and the Ezlo folks have helpfully created descriptive symlinks to both the Z-Wave and Zigbee devices so it's obvious which is which right off the bat. I used lsof to identify what process was using the device and killed it. It came back to life, but I tracked down the script that was restarting it and killed that too. I found some logs that indicated the zigbee device uses the EZSP protocol and should therefore work with Home Assistant's zigbee integration. All promising stuff. Then I fired up ser2net and... nothing.

    After a couple of hours trying a bunch of different stuff with no joy I started to suspect that ser2net was the problem. It was listening on the port I'd specified just fine, but I couldn't find any evidence that it was connecting to the serial device. I have no idea if I somehow compiled it incorrectly, if I'm using it incorrectly, or if it's not me at all, but nothing I tried worked so instead I compiled and installed socat to try instead and...
    d4078319-fd3d-410e-92ee-53f9454063e9-image.png

    Working in home assistant!

    For anyone wishing to give it a try, the commands I ran on the Ezlo to kill it's build-in zigbee addon and share it over the network were:

    ps | grep "/ha-zig" | cut -b1-5 | xargs -t kill
    socat /dev/ttyS2,raw,echo=1 tcp-listen:3333,reuseaddr,fork
    

    I'll upload the socat .ipk that I compiled somewhere and share a link to it when I get a chance. Rebooting the Ezlo brings it back to stock functionality.

    I haven't tested the stability of all this yet - I haven't even paired any devices - so take it all with a healthy grain of salt, but I'm pleased with my progress so far.

    Home Assistant now recommends Z-Wave JS as the way to integrate Z-Wave networks. I've been trying to figure out if they support 700 series chips but I can't tell from the docs. I suspect not, but I'm hoping it will in the not too distant future, and then I'll try and get that working too 🙂

    Vera

  • Ezlo Plus as Network Attached Zigee & Z-Wave Device
    J jaywll

    Hello, all!

    For several years now I've had a Vera Edge at home providing all my z-wave needs. I only really use it as a mechanism to get all my devices integrated into home assistant, which is the brains of the operation.

    Recently I ordered a few new z-wave devices that have z-wave 700 chips. They work fine with the Vera (albeit with some more advanced features unavailable), but I figure the Vera's days are numbered are there was a really good pre-order deal available on an Ezlo Plus, so I bought one of those too expecting it would be a drop-in replacement for the aging Vera.

    It arrived yesterday, and how wrong I was. There isn't any local control at all as best as I can tell, I can't integrate it with Home Assistant, and doing anything at all requires a clunky app and the cloud. Not what I want.

    Googling around I found this post on the home assistant community from few years back from someone who killed the running Vera software on their Vera Edge and ran some software to expose the serial Z-Wave chip to the network so Home Assistant could work with it directly. It looks like that idea eventually evolved into a script that automates the process of nuking the Vera.

    Despite just barely knowing what I'm doing I'm giving the same approach a shot on the Ezlo Plus. The first barrier was that ser2net wasn't installed and wasn't available in the mios repo, so I've compiled it from source and I just got it running.

    So far that's as far as I've gotten, but I'm interested in hearing from the community - especially those of you with more knowledge and experience. I have home assistant running on a server in my basement so the goal of network-attached radios that can be better located in the house is an attractive one, but is there even merit to the approach I'm trying to take? Is there a simpler way to get the Ezlo Plus working with Home Assistant that I'm overlooking? Has anyone else already done this and I'm just reinventing the wheel for no good reason? Should I just chalk the Ezlo up as a poor purchasing decision and get on with my life?

    Looking forward to your responses!

    Vera
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved