Hi-

I have an android media player entity publishing from HA. I watch for changes in transport state and media title to trigger some actions.

Though those attributes report as expected, the set rule is being throttled for possible flapping.

There is an attribute for media position that continually updates, I suspect it is causing the evaluations to run constantly.

The workaround I am seeking is to ignore those attributes in HA or MSR. Anyone know how, or have a better idea??

Thx
Btw- this problem has spanned versions of HA and reactor, but I am current on both. Too current on HA for transparency, but the issue has survived several updates.

Hi- looking for a hint in where to start. My goal is to set a PIN code in a zwave kwikset lock triggered in a rule.

The device isn’t exposing methods to help. The x-hass.call-service looks promising, but what would the service name be?

Plan b would be send the zwave controller a config command- I don’t see any way to explicitly send a command through JS Zwave in my environment.

Running reactor bare metal. JS Zwave is running as an add on inside HASS OS.

Any tips are appreciated.

Update ot anyone trying to SSH from Multihub Reactor...

I went to a linux bare metal install. Installing through the Add On store reset the docker image with every HASS restart. This means openSSH and the shared keys would disappear.

Also - at time of writting the AddOn store version is out of date with no appearant activty. Likely to change, but I moved on to give more flexability to MSR.

I look forward to the unintended consequences

Hi (fourth draft to simplify as I solve problems...)

My MSR is installed from the HASS add on store.

The Docker container did not have SSH client installed.

I was able to get SSH installed and setup keys on a remote worker server for password free SSH logins.

I now have a shell command that sends commands to the remote worker server. It renders content to a tidbyt LED matrix display.

Does anyone know if this will survive an update of the Reactor addon? Will the updated docker image wipe SSH and the private keys stored in the Reactor Docker Container?

Also - is it better to just move Reactor over to the worker server and manage my own updates?

I am using HAOS - Core-2024.1.2, Supervisor 2023.12.0, OS 11.3

Thanks - I referred to that post and a predesseor in my original post. I also went through the API documentation, still unable to trap events as a button.

HI -

Direct question-

• is there anything obvious wrong with my configuration below
• since the ZEN32 scene controller really has no on/off state (for btn 1-4), and I am using it as a toggle without concern for long press or multi press - am I better off just looking for any change to x_hass.state in a rule condition to trap a toggle?

Detailed Use case -
A-Use ZEN32 scene controller to group and control sonos players
B-Keep ZEN32 lights sync'd with real world sonos states. [B is alread working in my implementation by controlling the always on/always off led parms on the ZEN32]

Environment
Reactor - latest-23063-c464b68
hass - 2023.12.3 core / 2023.12.0 Supervisor
Zwave JS UI - 9.3.2

• the add ons are running on the hass instance in a virtualbox vm

prior reading:
Using Zooz ZEN32 Scene Controller as Trigger
Adding remotes, scene controllers as entities to MSR
MSR Manual - Handling Home Assistant Events

**Current ZEN32 zwave description to MSR - reactor.yaml **

      event_targets:
        "event.sonos_scene_controller_scene_001":
          name: "ZEN32 Button 1"
          capabilities:
            - button
          events:
            - event:
                event_type: zwave_js_value_notification
                data:
                  node_id: 008 # Put your ZWaveJS node ID here
                  property: scene
                  property_key: "001" #  001=button 1, 002=button 2, etc.
              response:
                button.since:
                  from: event.context.id
                button.state:
                  from: event.data.value
                  map:
                    KeyHeldDown: hold
                    KeyPressed: single
                    KeyPressed2x: double
                    KeyPressed3x: triple
                    KeyReleased: release
        "event.sonos_scene_controller_scene_002":
          name: "ZEN32 Button 2"
          capabilities:
            - button
          events:
            - event:
                event_type: zwave_js_value_notification
                data:
                  node_id: 008 # Put your ZWaveJS node ID here
                  property: scene
                  property_key: "002" #  001=button 1, 002=button 2, etc.
              response:
                button.since:
                  from: event.context.id
                button.state:
                  from: event.data.value
                  map:
                    KeyHeldDown: hold
                    KeyPressed: single
                    KeyPressed2x: double
                    KeyPressed3x: triple
                    KeyReleased: release
                    #
                    # dump_all_states - This is for troubleshooting. Do not enable unless asked.
                    #dump_all_states: false

Findings-
-The Hass logbook is seeing the events - also seen in the screenshot below

• no update to the MSR created "ZEN32 Button 1"
• The MSR manual indicates my HASS version is newer than supported (2023.11.3). I am assuming the issue is in my config.

Area of interest:

• Is my cannonical names correct in the Reactor.YAML code above - I took it from the Reactor entity dialog screenshoted below i.e. event.sonos_scene_controller_scene_001

Nice- very flexible.

Great- thanks, it works

Hi - hoping someone can share the url syntax to force MSR to run a specific set or reset action of a Rule.

Use case=
-use MSR actions to set a scene
-fire the reaction from a homebridge system on same LAN to manage voice commands

I have done this in Vera, can't find the correct syntax for MSR.

The command I tried from research is:
http://192.168.1.243:8111/api/v1/reaction/re-lq8bnkvf/run

I received "Not Found" using chrome No log entry - so I must be off on the URL.

Reactor = latest-23063-c464b685
MSR and Hass run on same ip addr
Reactor port =8111
HASS port=8123 (I tried this too)
screen shot attached

This is now resolved. There were a few issues.

1- The Envisalink hardware EVL3 only sends alerts to a single listener (TPI). It needed a reboot
2-My Backup Restore resulted in the incorrect IP address in Reactor.YAML contributed.

Thanks/Sorry

HI /Thanks. The rule is attached as asked.

There are some relevant facts that "might" be at the root-
A) I moved this HA via backup/restore. The IP Addr of HA changed. It was in a HyperV VM previously, I don't know if the attributes were updating in that enviro, but the entity history view indicate it was wired up at some point. It 'may' have broken in the restore - but I am also unsure if history comes over in a restore...

My environment seems to be rubbish. In HASS I have the Vera integration, exposing the devices/scenes. In MSR (AddOn under HASS) I have a pointer to the external Vera. I think MSR wants to live in its own environment, and be the overwatch marrying Vera and HASS, i.e. I can lose the Vera integration in HASS. As long as you are reviewing the issue I will leave all as is, but the plan is to seperate these components.

c) Between your last response and now, considering "A" above. The new HASS instance has a new IP Addr, I updated Reactor.YAML in the controllers section as below. After restarting, I can confirm Reactor is wired to Lutron devices connected direct to HASS through an integration (not through Vera). The Envisalink Alarm is still not wired to MSR.

Reactor.YAML changes made are below

• id: hass
  enabled: true
  implementation: HassController
  name: This Home Assistant
  config:
  source: "ws://192.168.1.243:8123"
  access_token:
  

Versions…
Core
2023.12.3
Supervisor
2023.11.6
Operating System
11.2
Frontend
20231208.2

Reactor 0.0.8

I lack the privileges to upload logs, sorry for the paste…

2023-12-18 02:11:24,170 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2023-12-18 02:11:24,204 INFO RPC interface 'supervisor' initialized
2023-12-18 02:11:24,206 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2023-12-18 02:11:24,207 INFO supervisord started with pid 1
2023-12-18 02:11:25,218 INFO spawned: 'nginx' with pid 8
2023-12-18 02:11:25,224 INFO spawned: 'reactor' with pid 9
Using existing set-up
Reactor Token is set, updating config
symlink does not exist, create it
2023-12-18 02:11:26,683 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-12-18 02:11:26,684 INFO success: reactor entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Reactor latest-23063-c464b685 app 22364 configuration from /config/reactor
NODE_PATH /opt/reactor:/opt/reactor/node_modules
[latest-23063]2023-12-18T02:11:27.249Z app:null Reactor build latest-23063-c464b685 starting on v16.15.1
[latest-23063]2023-12-18T02:11:27.254Z app:null Process ID 24 user/group 0/0; docker; platform linux/x64 #1 SMP PREEMPT_DYNAMIC Mon Dec 4 15:31:27 UTC 2023; locale (undefined)
[latest-23063]2023-12-18T02:11:27.256Z app:null Basedir /opt/reactor; data in /var/reactor/storage
[latest-23063]2023-12-18T02:11:27.257Z app:null NODE_PATH=/opt/reactor:/opt/reactor/node_modules
[latest-23063]2023-12-18T02:11:27.725Z Structure:null Module Structure v22323
[latest-23063]2023-12-18T02:11:27.730Z Capabilities:null Module Capabilities v22356
[latest-23063]2023-12-18T02:11:28.213Z Plugin:null Module Plugin v22300
[latest-23063]2023-12-18T02:11:28.230Z TimerBroker:null Module TimerBroker v22283
[latest-23063]2023-12-18T02:11:28.243Z Entity:null Module Entity v22353
[latest-23063]2023-12-18T02:11:28.253Z Controller:null Module Controller v23044
[latest-23063]2023-12-18T02:11:28.287Z default:null Module Ruleset v22293
[latest-23063]2023-12-18T02:11:28.294Z default:null Module Rulesets v22146
[latest-23063]2023-12-18T02:11:28.323Z GlobalExpression:null Module GlobalExpression v22146
[latest-23063]2023-12-18T02:11:28.363Z Predicate:null Module Predicate v22345
[latest-23063]2023-12-18T02:11:28.400Z AlertManager:null Module AlertManager v22283
[latest-23063]2023-12-18T02:11:28.407Z Rule:null Module Rule v22345
[latest-23063]2023-12-18T02:11:28.420Z GlobalReaction:null Module GlobalReaction v22324
[latest-23063]2023-12-18T02:11:28.425Z Engine:null Module Engine v23001
[latest-23063]2023-12-18T02:11:28.434Z httpapi:null Module httpapi v23058
[latest-23063]2023-12-18T02:11:28.593Z wsapi:null Module wsapi v23053
[latest-23063]2023-12-18T02:11:28.910Z TaskQueue:null Module TaskQueue 21351
[latest-23063]2023-12-18T02:11:28.912Z VeraController:null Module VeraController v22325
[latest-23063]2023-12-18T02:11:29.355Z HassController:null Module HassController v23060
[latest-23063]2023-12-18T02:11:29.958Z DynamicGroupController:null Module DynamicGroupController v22313
[latest-23063]2023-12-18T02:11:29.974Z SystemController:null Module SystemController v22306

I am ~6hrs into a Vera to HA migration. Lots to learn - and I will never make 5 steps to hit a light switch..

This example is exploratory - not the end workflow I am looking for. This is not a logic concern, the issue is I may not be reading attributes on entities correctly.

End Goal -
Dim/control on lights based on alarm states

Environment-
HA running in Virtualbox
MSR running as Addon in HA
Alarm connected to Envisalink EVL 3 card in a DSC alarm panel

Functionality that works
I can arm/disarm the house from the HA dash
I can read attribute status in entity viewer attribute pull down
I have working rule sets for other devices (lutron) on network

Problem-
As I "Arm" the house using a button on the HA Dashboard, I see attributes update in realtime.

In MSR, the attributes are not updating. In the MSR entity viewr, I can see updates were observed much earlier in the day.

I fear I cannot articulate the issue as I am so new to HA. I used Reactor in Vera, but very new to MSR and HA. The attached screenshot will show the side by side dialogs that are not staying in sync.

Thanks in advance for any insight.