Global Moderators group | Smart Home

toggledbits

Reactor only changes the entity name when the entity is first created. From there on, it sticks, no matter what the underlying hub does. To change the name, hit the "Rename" button on the entity in the detail pane (see your latest screen shots).

Also future note. When posting log snippets, please don't use grep or other filtering. Find the lines of interest, and post 20-25 of context before and as much context after as is relevant. Not all relevant log messages may contain the string you are searching for.

toggledbits

@tamorgen said in Set reaction triggering wrong z-wave device:

Here are some logs of me turning the entities on and off from HAAS.

You've shown here all stuff from ZWaveController, not HassController...? I don't think that would be helpful here anyway, because it would only show the HA entity IDs, and HA doesn't embed ZWave node numbers in their entity names. You would have to go look at the device in HA to confirm the node numbers. In HA's UI, go to Settings > Integrations > ZWave > Devices. Find the device you think is your Front Porch Lights switch, and click it. In the Device Info area, there's a Z-Wave Info heading with an arrow — click the arrow to expose the node number.

You said you updated ZWaveJSController, but it's still not showing me the expected log data. Can you confirm that in the startup messages for Reactor, ZWaveJSController reports it is version as 25304. If not, your update was not successful.

You can also go back to the ZWave-jS UI and command node 137 on from there, and see which device ZWave-JS switches. If it's the same device that Reactor switches, your Z-Wave nodes or HA devices are incorrectly identified.

What is clear in the Reactor logs so far is that ZWave node 137 is being told to do something, and ZWave node 137 responds back that it received the command its values changed. Nowhere along the way do the logs mention 136. If there was something wrong with what ZWaveJSController was commanding ZWaveJS to do, I would expect it log that it was performing an action on 137, but then gets update reports from 136, and that's not what is happening. I can also see in your Z-Wave data that node 137 is named "Front Porch Lights" at the node itself, which is consistent with the Reactor entity name, so Reactor/ZWaveJSController thinks it is doing the right thing.

I would start looking at the root, which is the ZWaveJS-UI, and make sure that node 137 is really your porch lights and you can command them on and off from there. If that's not the case, change the device name in Z-WaveJS UI, and then make sure the names in both HA and Reactor for nodes 136 and 137 match that data. Right now, it appears they do not.

toggledbits

OK. Everything checks out there. I would upgrade to the latest ZWaveJSController -- it looks like you are a release behind. That version added logging for what is actually sent to ZWaveJS, which may be instructive. But restarting for that update and rebuilding the state data may resolve the issue (you've probably done the former, I assume, but the latter is less obvious), so we're changing the conditions of the test. But let's see what happens when you upgrade, and then see what the log entries look like if the behavior is the same, because it sure looks like ZWaveJSController has it correct.

CatmanV2

Sounds like you all just defined steep learning curve

C

toggledbits

Please go to the Entities list, find entity zwavejs>137-0, open its detail panel, and copy-paste the output from the Copy Attributes button here (as text, no screen shots).

toggledbits

Have you looked at the logs to confirm your theory? Every device action is logged. I wrote this post a couple of months ago about how to find which Rule is manipulating a device.

toggledbits

@Pabla said in Can you run MSR on Home Assistant OS ?:

Had to edit entity config file recently to batch update entity names

You mean in the storage directory?

toggledbits

@Pabla said in Can you run MSR on Home Assistant OS ?:

occasionally you have to go into the container's directory to make changes and HA OS basically makes that impossible.

If you have to go into the container to make changes, something is wrong in the configuration. Nothing inside the container should ever need to be changed. Everything that is "mutable" and configurable by the user should be in the data directory external to the container. So... this comment has me puzzled...

And Docker can be made even easier with Portainer on top!

Not a fan, but I can see the utility. And there's a Portainer add-on for HA OS.

toggledbits

UPDATE (Jan 2026)

Orange Pi now offers a model 4A in 2GB or 4GB RAM configurations. The new model features an eight-core processor at 1.8Ghz, USB C power only (the DC barrel jack has been removed), an M.2 NVMe SSD (M-key 2280) slot, and eMMC interface (so no more onboard eMMC configurations, apparently, you have to buy an eMMC module separately). The 2GB model can be found for around US$55. eMMC modules are available in 32, 64, and 256GB (64GB is around US$32).

toggledbits

UPDATE (Jan 2026)

The Orange PI Zero 2 1GB is still available from that large, well-known online retailer; current pricing is $39.

I have one of these boards in service as my pool interface. Trouble-free, faithful service. The big plus for my particular use is that is has its WiFi on a UFL connector rather than traces-on-board, so I can use an external antenna for better range to the nearest AP in my home.

Again, don't confuse this board with the Orange Pi Zero or the Orange Pi Zero 2W, which are different boards.

Global Moderators

Posts

Member List