@togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.
Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.
Thanks in advance.
Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3
@toggledbits I have noticed after upgrading both Reactor and ZWaveJSController to version 24257 that two of my devices/entities, TILT-ZWAVE2.5-ECO and Zooz ZSE18, had their entity re-named in an unusual way and also appears to be duplicated.
Reactor version 24257
ZWaveJSController version 24257
Z-Wave JS UI version 9.18.1
zwave-js version 13.2.0
Vestibule Motion Sensor State attributes/partial screenshot of entities it created. All entities have the same attributes.
motion_sensor.state=true x_zwave_values.Notification_Home_Security_Motion_sensor_status=8 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=23 zwave_device.valueId=[113,"Notification","Home Security","Home Security","Motion sensor status","Motion sensor status"] zwave_device.version_info=nullTilt Sensor Door State and Tilt Sensor Door State Simple attributes/partial screenshot of entities it created. All entities have similar attributes with exception of x_zwave_values.Notification_Access_Control_Door_State = 22 or 23.
tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state_simple=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state_simple=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=nullI'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:
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
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 🙂
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.Hi @toggledbits.
After a couple of weeks, I noticed that my Remotec zrc90 isn't working as expected.
Scenes are working in ZWaveJS, but this device has a strange behavior: the scene change, but then it's set again to null. In Reactor, this remains null:
battery_power.level=0.7 battery_power.since=1725817957361 x_debug.dt={"description":"Scene master 8 button remote","model":"BW8510/ZRC-90US","default_name":"Scene master 8 button remote","manufacturerId":21076,"productType":0,"productId":34064} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=70 x_zwave_values.Central_Scene_scene_001=null x_zwave_values.Central_Scene_scene_002=null x_zwave_values.Central_Scene_scene_003=null x_zwave_values.Central_Scene_scene_004=null x_zwave_values.Central_Scene_scene_005=null x_zwave_values.Central_Scene_scene_006=null x_zwave_values.Central_Scene_scene_007=null x_zwave_values.Central_Scene_scene_008=null x_zwave_values.Central_Scene_slowRefresh=null x_zwave_values.Manufacturer_Specific_manufacturerId=21076 x_zwave_values.Manufacturer_Specific_productId=34064 x_zwave_values.Manufacturer_Specific_productType=1 x_zwave_values.Version_firmwareVersions=["1.1","1.1"] x_zwave_values.Version_hardwareVersion=3 x_zwave_values.Version_libraryType=2 x_zwave_values.Version_protocolVersion="4.5" x_zwave_values.Wake_Up_controllerNodeId=1 x_zwave_values.Wake_Up_wakeUpInterval=0 zwave_device.capabilities=[91,114,128,132,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Remote Controller" zwave_device.impl_sig="24242:1:22315:1" zwave_device.is_beaming=false zwave_device.is_listening=false zwave_device.is_routing=false zwave_device.is_secure=false zwave_device.manufacturer_info=[21076,1,34064] zwave_device.max_data_rate=null zwave_device.node_id=154 zwave_device.specific_class="Simple Remote Control" zwave_device.status=2 zwave_device.status_text="awake" zwave_device.version_info=[null,"1.1"] zwave_device.wakeup_interval=0Anything I could look at? Thanks.
Hi, @toggledbits!
I have a question about the execution behavior. See the code below, and I'll explain the situation.
12957c3e-ff06-46c9-929d-b53f936665df-image.png
This is a routine that, at a certain point, determines that the desktop on which the VM hosting the Reactor is located receives an instruction to perform a shutdown (Shell Command).
When this happens, the desktop is turned off, and then Hubitat detects by a "ping" that the VM has been down, waits 15 seconds, turns off the power to this desktop, and then 15 seconds later turns on the desktop with the Reactor VM again.
After restarting the desktop, the VM is loaded, and the Reactor is triggered. Still, the following problem occurs: I expected that when the rule was continued to be executed again, the next step would be executed, that of the 900-second delay after shutdown, but the Shell command is executed again, and then it goes into a loop, the rule does not advance.
To break the loop, I first have to make the VM not load, change the desktop password, and then start the VM. In this case, Reactor generates an error when trying to execute the Shell Command because of the invalid password and then finishes the routine following the 900 delay step.
b58b0d4a-d6c1-4fe3-bab7-4222acea9607-image.png
Is my interpretation that when it returns, the routine should continue to the next step that has not yet been executed incorrectly? Or does Reactor, through the shutdown command, interpret that it hasn't finished this step and keep trying, which is the correct reaction?
Thanks for clarifying.
Hi @toggledbits ,
I'm slowly moving my ZWave network from Vera to ZWaveJS. I successfully cloned my ZWave network using a spare Vera Edge (a new post for the community later when I'll be fully back from vacation) and I'm testing a couple of things before moving everything to ZWaveJS.
In the meanwhile, I have a couple of venetian blinds connected to Fibaro Roller Shutters 2 (FGR222) and I'm using some proprietary ZWave commands to control the tilt position, that right now I'm sending via Vera (with some code from the old place, messing with this):
af7f883c-f49e-419c-a2fe-8669572e3792-image.png
The ZWaveJS values are reported via this:
x_zwave_values.Manufacturer_Proprietary_fibaro_venetianBlindsPosition=0 x_zwave_values.Manufacturer_Proprietary_fibaro_venetianBlindsTilt=0I hope there's a way to expose a separate device to control the tilt position directly, without doing the mess I'm doing now. Let me know if you need some files. Thanks.
As per @toggledbits request, new topic.
Position and cover commands not working and position/cover attributes are incorrect. Dimming is OK.
cover.state=null dimming.level=1 dimming.step=0.1 energy_sensor.units="kWh" energy_sensor.value=0.41 position.value=null power_sensor.units="W" power_sensor.value=0 power_switch.state=true x_debug.dt={"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=6","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state"} x_zwave_values.Meter_reset=null x_zwave_values.Meter_value_65537=0.41 x_zwave_values.Meter_value_66049=0 x_zwave_values.Multilevel_Switch_Down=null x_zwave_values.Multilevel_Switch_Up=null x_zwave_values.Multilevel_Switch_currentValue=99 x_zwave_values.Multilevel_Switch_duration="unknown" x_zwave_values.Multilevel_Switch_restorePrevious=null x_zwave_values.Multilevel_Switch_targetValue=99 x_zwave_values.Notification_Power_Management_Over_current_status=0 x_zwave_values.Notification_System_Hardware_status=0 x_zwave_values.Notification_alarmLevel=null x_zwave_values.Notification_alarmType=null zwave_device.capabilities=[38,50,113] zwave_device.endpoint=1 zwave_device.failed=null zwave_device.impl_sig="24225:1:22315:1" zwave_device.manufacturer_info=null zwave_device.node_id=148 zwave_device.version_info=nullThanks!
Another one for you, @toggledbits.
I have two water sensors (same device, NAS-WS01Z), but one is reporting leak_detector.state=true even if no alarm is detected (I double checked from ZWaveJS UI):
battery_power.level=0.86 battery_power.since=null leak_detector.state=true x_debug.dt={"entity_class":"Notification Sensor","match":"deviceClass.generic.key=7"} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=86 x_zwave_values.Binary_Sensor_Water=false x_zwave_values.Configuration_Alarm_Activity_Duration=5 x_zwave_values.Configuration_Alarm_Beep=1 x_zwave_values.Configuration_Alarm_Duration=120 x_zwave_values.Configuration_Alarm_Interval=null x_zwave_values.Configuration_Basic_Set_Level=255 x_zwave_values.Configuration_First_Alarm_Activity_Duration=null x_zwave_values.Configuration_Water_Detection=1 x_zwave_values.Manufacturer_Specific_manufacturerId=600 x_zwave_values.Manufacturer_Specific_productId=4229 x_zwave_values.Manufacturer_Specific_productType=3 x_zwave_values.Notification_Water_Alarm_Sensor_status=null x_zwave_values.Notification_alarmLevel=0 x_zwave_values.Notification_alarmType=0 x_zwave_values.Version_firmwareVersions=null x_zwave_values.Version_hardwareVersion=null x_zwave_values.Version_libraryType=null x_zwave_values.Version_protocolVersion=null x_zwave_values.Wake_Up_controllerNodeId=1 x_zwave_values.Wake_Up_wakeUpInterval=43200 zwave_device.capabilities=[48,112,113,114,128,132,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Notification Sensor" zwave_device.impl_sig="24225:1:22315:1" zwave_device.is_beaming=false zwave_device.is_listening=false zwave_device.is_routing=true zwave_device.is_secure=false zwave_device.last_wakeup=1724143899220 zwave_device.manufacturer_info=[600,3,4229] zwave_device.max_data_rate=null zwave_device.node_id=114 zwave_device.specific_class="Notification Sensor" zwave_device.status=1 zwave_device.status_text="asleep" zwave_device.version_info=[null,null] zwave_device.wakeup_interval=43200here's the other one, correctly report the leak status:
battery_power.level=1 battery_power.since=null leak_detector.state=false x_debug.dt={"entity_class":"Notification Sensor","match":"deviceClass.generic.key=7"} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=100 x_zwave_values.Binary_Sensor_Water=false x_zwave_values.Configuration_Alarm_Activity_Duration=5 x_zwave_values.Configuration_Alarm_Beep=1 x_zwave_values.Configuration_Alarm_Duration=120 x_zwave_values.Configuration_Alarm_Interval=1 x_zwave_values.Configuration_Basic_Set_Level=255 x_zwave_values.Configuration_First_Alarm_Activity_Duration=60 x_zwave_values.Configuration_Water_Detection=1 x_zwave_values.Manufacturer_Specific_manufacturerId=600 x_zwave_values.Manufacturer_Specific_productId=4229 x_zwave_values.Manufacturer_Specific_productType=3 x_zwave_values.Notification_Water_Alarm_Sensor_status=0 x_zwave_values.Notification_alarmLevel=null x_zwave_values.Notification_alarmType=null x_zwave_values.Version_firmwareVersions=["2.54"] x_zwave_values.Version_hardwareVersion=48 x_zwave_values.Version_libraryType=6 x_zwave_values.Version_protocolVersion="4.5" x_zwave_values.Wake_Up_controllerNodeId=1 x_zwave_values.Wake_Up_wakeUpInterval=43200 zwave_device.capabilities=[48,112,113,114,128,132,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Notification Sensor" zwave_device.impl_sig="24225:1:22315:1" zwave_device.is_beaming=false zwave_device.is_listening=false zwave_device.is_routing=true zwave_device.is_secure=false zwave_device.last_wakeup=1724105239533 zwave_device.manufacturer_info=[600,3,4229] zwave_device.max_data_rate=null zwave_device.node_id=113 zwave_device.specific_class="Notification Sensor" zwave_device.status=1 zwave_device.status_text="asleep" zwave_device.version_info=[null,"2.54"] zwave_device.wakeup_interval=43200Also, both seems to have no primary value. Thanks.
Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.
What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?
Running:
Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]HAAS:
RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0Hi-
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.
Referencing an expression inside a reaction is in the form of ${{ expression }}. When referenced inside my shell command to set the watering delay duration for my Rachio sprinkler system, it just does not work.
If I enter "86400" instead of referencing the expression lWateringDelayDuration, it works. Either I am doing something wrong or referencing an expression inside a shell command is not supported.
Reactor version: 24212
Local Expression
lWateringDelayDuration =
Setting Reaction using Shell command
curl -X PUT -H "Content-Type: application/json" -H "Authorization: Bearer xxxxxxxxxx -d '{ "id" : "xxxxxxxxxx", "duration" : ${{ lWateringDelayDuration}} }' https://api.rach.io/1/public/device/rain_delayThanks in advance
As per @toggledbits request, here's a new topic.
My Fibaro Door Window Sensor 2 (FGDW002) is always reporting as open, even if
x_zwave_values.Notification_Access_Control_Door_state=23 x_zwave_values.Notification_Access_Control_Door_state_simple=23which means that the door is closed. It was working before and I could downgrade to test, if necessary. Thanks.
Hi @toggledbits,
I'm not sure if it's a bug or something, but I have a lot of Fibaro Double Switch (FGS223) as follows.
In the example, it's zwavejs>65-2:
energy_sensor.units="kWh" energy_sensor.value=0.21 power_sensor.units="W" power_sensor.value=0 power_switch.state=false x_debug.dt={"entity_class":"Switch","match":"deviceClass.generic.key=16","capabilities":["power_switch","toggle"],"primary_attribute":"power_switch.state"} x_zwave_values.Binary_Switch_currentValue=false x_zwave_values.Binary_Switch_targetValue=false x_zwave_values.Meter_reset=null x_zwave_values.Meter_value_65537=0.21 x_zwave_values.Meter_value_66049=0 zwave_device.capabilities=[37,50] zwave_device.endpoint=2 zwave_device.failed=null zwave_device.impl_sig="23326:1:22315:1" zwave_device.manufacturer_info=null zwave_device.node_id=65 zwave_device.version_info=nullWhen operating endpoint 2, it's triggered endpoint 1. Endpoint 1 is fine. This is causing a lot of troubles, as you may imagine.
Also, endpoint 0 is not really a switch, and the associated actions are not doing anything at all. Maybe these could be removed. Also, I see battery_maintenance and power_source capabilities, all with null values.
battery_maintenance.charging=null battery_maintenance.rechargeable=false battery_maintenance.replace=false battery_maintenance.state=null heat_detector.state=false power_source.source=null power_switch.state=null x_debug.dt={"entity_class":"Switch","match":"deviceClass.generic.key=16","capabilities":["power_switch","toggle"],"primary_attribute":"power_switch.state","description":"Double Switch 2","model":"FGS223","default_name":"Double Switch 2","manufacturerId":271,"productType":515,"productId":4096} x_zwave_values.Central_Scene_scene_001=null x_zwave_values.Central_Scene_scene_002=null x_zwave_values.Central_Scene_slowRefresh=null x_zwave_values.Configuration_First_Channel_Energy_Reports_Threshold=100 x_zwave_values.Configuration_First_Channel_Operating_Mode=0 x_zwave_values.Configuration_First_Channel_Power_Reports_Minimum_Time_Between_Reports=10 x_zwave_values.Configuration_First_Channel_Power_Reports_Threshold=20 x_zwave_values.Configuration_First_Channel_Pulse_Time_for_Blink_Mode=5 x_zwave_values.Configuration_First_Channel_Reaction_to_Key_S1_for_Delay_Auto_ON_OFF_Modes=0 x_zwave_values.Configuration_First_Channel_Time_Parameter_for_Delay_Auto_ON_OFF_Modes=50 x_zwave_values.Configuration_General_Purpose_Alarm_Response=3 x_zwave_values.Configuration_Include_Consumption_By_Device_Itself_in_Reports=0 x_zwave_values.Configuration_Input_Button_Switch_Configuration=2 x_zwave_values.Configuration_Key_S1_Associations_Double_Click_Value_Sent=99 x_zwave_values.Configuration_Key_S1_Associations_Send_OFF_With_Single_Click_2=0 x_zwave_values.Configuration_Key_S1_Associations_Send_ON_With_Single_Click_1=0 x_zwave_values.Configuration_Key_S1_Associations_Send_When_Double_Clicking_8=0 x_zwave_values.Configuration_Key_S1_Associations_Send_When_Holding_and_Releasing_4=0 x_zwave_values.Configuration_Key_S1_Associations_Switch_OFF_Value_Sent=0 x_zwave_values.Configuration_Key_S1_Associations_Switch_ON_Value_Sent=255 x_zwave_values.Configuration_Key_S1_Send_Scenes_When_Held_Down_and_Released_8=1 x_zwave_values.Configuration_Key_S1_Send_Scenes_When_Pressed_1_Time_1=1 x_zwave_values.Configuration_Key_S1_Send_Scenes_When_Pressed_2_Times_2=1 x_zwave_values.Configuration_Key_S1_Send_Scenes_When_Pressed_3_Times_4=1 x_zwave_values.Configuration_Key_S2_Associations_Double_Click_Value_Sent=99 x_zwave_values.Configuration_Key_S2_Associations_Send_OFF_With_Single_Click_2=0 x_zwave_values.Configuration_Key_S2_Associations_Send_ON_With_Single_Click_1=0 x_zwave_values.Configuration_Key_S2_Associations_Send_When_Double_Clicking_8=0 x_zwave_values.Configuration_Key_S2_Associations_Send_When_Holding_and_Releasing_4=0 x_zwave_values.Configuration_Key_S2_Associations_Switch_OFF_Value_Sent=0 x_zwave_values.Configuration_Key_S2_Associations_Switch_ON_Value_Sent=255 x_zwave_values.Configuration_Key_S2_Send_Scenes_When_Held_Down_and_Released_8=1 x_zwave_values.Configuration_Key_S2_Send_Scenes_When_Pressed_1_Time_1=1 x_zwave_values.Configuration_Key_S2_Send_Scenes_When_Pressed_2_Times_2=1 x_zwave_values.Configuration_Key_S2_Send_Scenes_When_Pressed_3_Times_4=1 x_zwave_values.Configuration_Periodic_Active_Power_Reports=3600 x_zwave_values.Configuration_Periodic_Energy_Reports=3600 x_zwave_values.Configuration_Report_During_Blink_Mode=0 x_zwave_values.Configuration_Second_Channel_Energy_Reports_Threshold=100 x_zwave_values.Configuration_Second_Channel_Operating_Mode=0 x_zwave_values.Configuration_Second_Channel_Power_Reports_Minimum_Time_Between_Reports=10 x_zwave_values.Configuration_Second_Channel_Power_Reports_Threshold=20 x_zwave_values.Configuration_Second_Channel_Pulse_Time_for_Blink_Mode=5 x_zwave_values.Configuration_Second_Channel_Reaction_to_Key_S2_for_Delay_Auto_ON_OFF_Modes=0 x_zwave_values.Configuration_Second_Channel_Time_Parameter_for_Delay_Auto_ON_OFF_Modes=50 x_zwave_values.Configuration_Send_Secure_Commands_to_2nd_Association_Group_1=1 x_zwave_values.Configuration_Send_Secure_Commands_to_3rd_Association_Group_2=1 x_zwave_values.Configuration_Send_Secure_Commands_to_4th_Association_Group_4=1 x_zwave_values.Configuration_Send_Secure_Commands_to_5th_Association_Group_8=1 x_zwave_values.Configuration_Smoke_CO_or_CO2_Alarm_Response=3 x_zwave_values.Configuration_State_After_Power_Failure=1 x_zwave_values.Configuration_Temperature_Alarm_Response=1 x_zwave_values.Configuration_Time_of_Alarm_State=600 x_zwave_values.Configuration_Water_Flood_Alarm_Response=2 x_zwave_values.Manufacturer_Specific_manufacturerId=271 x_zwave_values.Manufacturer_Specific_productId=4096 x_zwave_values.Manufacturer_Specific_productType=515 x_zwave_values.Notification_Heat_Alarm_Heat_sensor_status=0 x_zwave_values.Notification_Power_Management_Over_current_status=0 x_zwave_values.Notification_alarmLevel=null x_zwave_values.Notification_alarmType=null x_zwave_values.Protection_exclusiveControlNodeId=null x_zwave_values.Protection_local=0 x_zwave_values.Protection_rf=0 x_zwave_values.Protection_timeout=null x_zwave_values.Version_firmwareVersions=["3.2"] x_zwave_values.Version_hardwareVersion=3 x_zwave_values.Version_libraryType=3 x_zwave_values.Version_protocolVersion="4.5" zwave_device.capabilities=[91,112,113,114,117,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Binary Switch" zwave_device.impl_sig="23326:1:22315:1" zwave_device.is_beaming=false zwave_device.is_listening=true zwave_device.is_routing=true zwave_device.is_secure=false zwave_device.manufacturer_info=[271,515,4096] zwave_device.max_data_rate=null zwave_device.node_id=65 zwave_device.specific_class="Binary Power Switch" zwave_device.status=4 zwave_device.status_text="alive" zwave_device.version_info=[null,"3.2"]Thanks.
Good morning,
I'm having an issue with controlling my Zooz Zen14 outdoor double outlet. I should be able to control each outlet individually, and this does work when use Home Assistant (haas) from Reactor.
When I use zwavejs, I see 3 entries:
8305eccf-a99e-421f-ad18-1f08da9c8c9c-image.png
The first entry is for the overall device. I can turn both outlets on and off (in theory) by setting the power_switch state to on or off. This does turn them on and off when using zwavejs.
When I go to the individual outlets, performing the power_switch.on or power_switch.off actions turns them all (main, 1 and 2) on or off, and not just the individual outlets. When I perform the same action from haas, turning on outlet 1 will turn on the main switch and 1, but not 2.
I reviewed the logs for that node and I'm not seeing anything obvious.
:~/reactor/logs$ cat reactor.log.1 | grep ZWaveJSController#zwavejs | grep "node 216" [latest-24212]2024-08-07T00:19:00.233Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "endpoint": 0, "property": "targetValue", "newValue": true, "prevValue": false, "propertyName": "targetValue" } } [latest-24212]2024-08-07T00:19:00.235Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 0, "newValue": true, "prevValue": false, "propertyName": "currentValue" } } [latest-24212]2024-08-07T00:19:00.321Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 0, "newValue": true, "prevValue": true, "propertyName": "currentValue" } } [latest-24212]2024-08-07T00:19:00.322Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "targetValue", "endpoint": 0, "newValue": true, "prevValue": true, "propertyName": "targetValue" } } [latest-24212]2024-08-07T00:19:00.323Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:duration:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "duration", "endpoint": 0, "newValue": { "value": 0, "unit": "seconds" }, "prevValue": { "value": 0, "unit": "seconds" }, "propertyName": "duration" } } [latest-24212]2024-08-07T00:19:02.189Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 1, "newValue": true, "prevValue": false, "propertyName": "currentValue" } } [latest-24212]2024-08-07T00:19:02.192Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "targetValue", "endpoint": 1, "newValue": true, "prevValue": false, "propertyName": "targetValue" } } [latest-24212]2024-08-07T00:19:02.193Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:duration:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "duration", "endpoint": 1, "newValue": { "value": 0, "unit": "seconds" }, "prevValue": { "value": 0, "unit": "seconds" }, "propertyName": "duration" } } [latest-24212]2024-08-07T05:32:30.127Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 216 endpoint 0 (entity "216-0") [latest-24212]2024-08-07T05:32:30.127Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 216 endpoint 1 (entity "216-1") [latest-24212]2024-08-07T05:32:30.128Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 216 endpoint 2 (entity "216-2")I'm running:
Reactor (Multi-hub) latest-24212-3ce15e25
ZWaveJSController [0.1.23326] (with zwavejs_data from 7/25/2024)
HA:
Core 2024.7.3
Supervisor 2024.08.0
Operating System 12.3
Frontend 20240710.0
I think this feature request could be accomplished with the use of two or more rules, but it would be great if there was a way to wait for an event or trigger to occur before continuing on in the reactions.
For example, I have a rule that will turn on some exterior lights if you arrive home after the porch lights have been turned off. Right now this rule randomly will turn off between 5-10 minutes after the person has entered the geofence. On some occasions this 5-10 minutes isn't long enough, say if you are unloading the car or something. I would like to kick off the reaction, but pause it part way through and wait for the door to close and lock, then continue it on. Hubitat Rule Machine has a "Wait for event" option, but I really want to keep all my logic within MSR.
Hi,
Running the latest version 24212 on docker.
I want to run some appliances when my solar panels deliver over 1200 watts to the net. In this example the dryer. So when the dryer is turned on, the rule starts (SET). There first is a 3 min delay in case the dryer is turned on manually, that is group "Check if auto start is needed". If the dryer is not running, the status is set to waiting, and the shown Repeat Until should wait as long the power delivered is higher than -1200 for at least 120 seconds and the status is still waiting. Higher as the value is negative. For some reason that repeat until "DR Wait for solar high or manual start" looks skipped. Nothing in the logs. What am I missing?
Reactor Automation.png (g_DryerStatus should have been "waiting" and not "running" the moment the log was captured, so that should not be the issue. Unless it takes some time for a variable to actually change?)
Cheers Rene
Having issues with a shell command
-
You can map a value from one to another using a simple map object, like this:
mappedStatus =
( { '200': 'On', '620': 'Off' } )?[ ps4wakerparse.statusCode ] ?? "unknown"
Here, we create an object on the fly (the
( { ... } )
part), dereference through it using the?[
coalesce operator, which will return null if the value ofstatusCode
doesn't match anything in the object, and then use a final??
coalesce operator to change an unmapped/null to the wordunknown
-
@toggledbits said in Having issues with a shell command:
The ?. and ?[ operators
That fixes it the red alerts don't appear any more when Resetting the rule.
Thanks
-
Finished device in Vera:
Home Remote dashboard tile:
Had to just add an additional ? to this code to stop the red alert appearing again.
( { '200': 'On', '620': 'Off' } )?[ ps4wakerparse?.statusCode ] ?? "unknown"
And now the alert doesn't come back again when resetting the rule.
So I think everything is all working fine now, at least while the PS4 is turned ON.
Thanks
-
So everything last night was working OK when the PS4 was turned ON.
I am now testing when the PS4 is OFF.
Some issues the shell command doesn't seem to be populating the ps4wakercheck variable for some reason and its null.
Vera device when PS4 is OFF
If I run the "ps4-waker check" command in terminal it outputs correctly as expected.
root@HP-Thin01:/home/stuart# ps4-waker check { "type": "device", "statusLine": "620 Server Standby", "statusCode": "620", "status": "Standby", "host-id": "C863F1400EF1", "host-type": "PS4", "host-name": "PS4-806", "host-request-port": "997", "device-discovery-protocol-version": "00020020", "system-version": "08520011", "address": "192.168.0.201" }
Log file:
2021-08-02T10:51:27.077Z <Engine:NOTICE> Starting reaction PS4 Waker Check<SET> (rule-krq612qx:S) 2021-08-02T10:51:27.077Z <Engine:5:Engine.js:1378> Engine#1 reaction rule-krq612qx:S step 1 shell command { "command": "ps4-waker check", "rule": "rule-krq612qx", "rvar": "ps4wakercheck", "ignore_exit": true } 2021-08-02T10:51:27.094Z <Engine:5:Engine.js:1105> _process_reaction_queue() task returned, new status 3; task 19 2021-08-02T10:51:27.098Z <Engine:5:Engine.js:1140> _process_reaction_queue ending with 1 in queue; none delayed/ready; waiting 2021-08-02T10:51:27.617Z <Engine:ERR> Engine#1 reaction PS4 Waker Check<SET> step 1 error executing shell `ps4-waker check': Error: Command failed: ps4-waker check 2021-08-02T10:51:27.620Z <Rule:5:Rule.js:674> Rule#rule-krq612qx rule set variable ps4wakercheck = (object) (null) 2021-08-02T10:51:27.621Z <Engine:5:Engine.js:940> Engine#1 set variable rule rule-krq612qx ps4wakercheck=(null), requesting re-eval 2021-08-02T10:51:27.624Z <Rule:5:Rule.js:962> Rule#rule-krq612qx (PS4 Waker Check) evaluate() acquiring mutex 2021-08-02T10:51:27.625Z <Engine:5:Engine.js:1140> _process_reaction_queue() wake-up! 2021-08-02T10:51:27.625Z <Rule:5:Rule.js:966> Rule#rule-krq612qx._evaluate() mutex acquired, evaluating 2021-08-02T10:51:27.626Z <Rule:5:Rule.js:970> Rule#rule-krq612qx update rate is 2/min limit 60/min 2021-08-02T10:51:27.627Z <Rule:5:Rule.js:892> Rule#rule-krq612qx evaluateExpressions() with 3 expressions 2021-08-02T10:51:27.628Z <Rule:5:Rule.js:982> Rule#rule-krq612qx._evaluate() trigger state now false (was false) 2021-08-02T10:51:27.629Z <Rule:5:Rule.js:984> Rule#rule-krq612qx._evaluate() constraints state true 2021-08-02T10:51:27.629Z <Rule:5:Rule.js:993> Rule#rule-krq612qx rule state now false, changed no 2021-08-02T10:51:27.631Z <Engine:5:Engine.js:1101> _process_reaction_queue() running task 19 { "tid": 19, "id": "rule-krq612qx:S", "rule": "rule-krq612qx", "__reaction": [RuleReaction#rule-krq612qx:S], "next_step": 2, "status": 1, "ts": 1627901487069, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 1 } 2021-08-02T10:51:27.632Z <Engine:NOTICE> Resuming reaction PS4 Waker Check<SET> (rule-krq612qx:S) from step 2 2021-08-02T10:51:27.632Z <Engine:NOTICE> PS4 Waker Check<SET> delaying until 1627901492632<02/08/2021, 11:51:32> 2021-08-02T10:51:27.633Z <Engine:5:Engine.js:1105> _process_reaction_queue() task returned, new status 2; task 19 2021-08-02T10:51:27.636Z <Engine:5:Engine.js:1140> _process_reaction_queue() ending with 1 in queue; waiting for 1 (next delayed task)
If I turn ON the PS4 it starts working again and the variable is populated with data via the shell command.
-
Make sure you restarted Reactor after installing the update. The ignore flag is in the action data (so the UI has done the right thing), but the log file content looks like an older version of the Engine running.
-
Any update on this?
-
Sorry for the delay.
Yes its working now after restarting MSR.
So when the PS4 is OFF its now reporting the status correctly from the ps4-waker check variables.
So its working when its on and off now.
However I am still getting some alert errors sometimes occasionally.
This seems to happen if the shell command doesn't return any response on the first go, but maybe on the second attempt it works and then populates the variables OK.
When this happens these alerts remain in the MSR gui etc.
-
Use your coalesce operators on those expressions to suppress the reference errors and just yield a null result.
-
The actions in the Reaction that send the data to the Vera MutliString device, didn't have "?" in their expressions.
I have just added them like this:
EDIT:
It doesn't like the first one " mappedstatuscode? " I've removed the question mark for that one.
-
I've also now added a virtual switch in Vera, this works with two new MSR rules (#3 and #4).
First rule (#4), that when the virtual switch it turned on or off manually in Vera / Home Remote app, it will send the appropriate power command to the ps4 via shell command:
ON = ps4-waker
OFF = ps4-waker standby
The second rule (#3) updates the state of the Vera virtual switch, if the PS4's power is controlled by some other outside means.
This rule monitors the "mappedstatuscode" expression variable, which will either say "On" or "Off" and then it adjusts the Vera virtual switch accordingly to match that current actual state of the PS4, so the virtual switch doesn't get out of sync.I am still experimenting with this, but my thinking was to have an additional "switch" in Vera / Home Remote app, to be able to manually / directly control the PS4's power (outside of a Harmony activity) as a backup switch. Say if the PS4 didn't turn on when the Harmony Activity for it was started and the other MSR rule (#1) didn't work with its attempt and didn't turn on the PS4.
Although having said that, I guess some kind of test and retry (in rule #1) to attempt to turn on the PS4 power again, might be a better way of doing it, if it failed to do so initially.
So in total I currently have four rules.
- "Lounge - Harmony PS4 Activity Start - Wake PS4 Shell Command"
Turns on PS4 when Harmony Activity is starting.
- "PS4 Waker Check"
This is the rule with all the expressions in it for the MultiString Vera device. Displays the PS4's current status etc
- "Playstation 4 Virtual Switch Status from PS4-Waker"
Controls the virtual switch in Vera based on the actual state of the PS4 power, info as coming from ps4-waker check and rule #2
- "Playstation 4 Virtual Switch ON / OFF"
Sends either the on or off shell commands to the PS4 based on the virtual switch in Vera / Home Remote app being manually operated.
Home Remote tiles:
I am sure there must be better / easier ways of doing all this.
-
This seems to happen if the shell command doesn't return any response on the first go
Have you figured out what
ps4-waker
does when it doesn't get the device turned on? Does it return a particular exit code that isn't used by the on/off status result? Or does it just give an empty reply? Either way, you might write a wrapper script to detect that and retry (Reactor would then start the wrapper script instead ofps4-waker
directly.Issues like this are how you bring your shell scripting and system administration skills up a notch.
-
@toggledbits said in Having issues with a shell command:
Have you figured out what ps4-waker does when it doesn't get the device turned on?
I'm not sure, I will look out for when it happens again.
I think it makes MSR error when it tries to send the "ps4-waker" command to turn ON the games console but fails to connect for whatever reason.
Most times it works and the console does turn on but sometimes it doesn't.
Thanks
-
Actually I have five MSR rules for the Playstation. I have another one that is also monitoring for the Harmony Activity starting, this rule closes the lounge blind and curtains if its daytime.
Would having two rules monitoring for the same trigger event, the Harmony Activity starting, have any affect on things?
Maybe one rule hi-jacks the other from triggering sometimes ?
-
@cw-kid said in Having issues with a shell command:
I'm not sure, I will look out for when it happens again.
The goal I propose is to write a script that runs
ps4-waker
itself, and retries if it fails to connect. MSR would then run that script instead of runningps4-waker
directly. If, for example, theps4-waker
script simply returns no data (empty) result, then something like this would work:#!/bin/sh while true; do # Run command and capture its output and exit status output=`ps4-waker $*` status=$? # If output was produced, stop looping. if [ -n "$output" ]; then break; fi sleep 1 # slow retries down a little done # Echo back the command output and exit with its exit status. echo "$output" exit $status
Save this as
ps4-wrapper.sh
in the Reactor install directory (or somewhere along the path, like whereps4-waker
currently is), and give it execute permissions (chmod 755 ps4-wrapper.sh
).The wrapper script can be run in place of
ps4-waker
, with the same arguments (e.g.ps4-wrapper.sh status
). If a request fails and produces no output, it is simply re-run until output is produced (or until the command times out in Reactor, when it is killed). -
@cw-kid said in Having issues with a shell command:
Maybe one rule hi-jacks the other from triggering sometimes ?
No, each rule has its own supervision of its entities of interest, etc. You'd be able to quickly confirm this by looking in the logs and seeing that the SET reactions for both rules run.
-
@toggledbits said in Having issues with a shell command:
The goal I propose is to write a script
Great thanks I will try this approach instead then.
But first I will leave things as is and see what happens? when it doesn't turn on the PS4 on first attempt.
It might just return no data in the response as you suggest, or it may as I seem to think, return something else, which I haven't documented here in this thread yet. But I can't remember off the top of my head what it was doing.
-
This isn't related to when the PS4 doesn't turn on.
When the PS4 is OFF / sleep mode, I am seeing this error alert appearing, to do with the parsing of the output to JSON.
I assume this alert occurs if the "ps4-waker check" command hasn't worked and initially pulled in the data ?
Maybe I need two wrapper scripts then, one for turning on the power and one for the check command also.
-
Regarding the power on issue and maybe using a wrapper script.
When I manually run the "ps4-waker" command in terminal this is the output I get back:
WAKEUP sent to device... 192.168.0.201
I don't see any alert in MSR gui when it fails to turn on the PS4 on its first and currently only attempt to do so.
Looking in the log I can't see anything there either as to why the command didn't turn on the PS4 ?
2021-08-04T13:08:32.530Z <Rule:5:Rule.js:660> Rule#rule-krpft5eh rule set variable ps4waker = (string) 2021-08-04T13:08:32.533Z <Engine:5:Engine.js:945> Engine#1 set variable rule rule-krpft5eh ps4waker=, requesting re-eval 2021-08-04T13:08:32.534Z <Rule:5:Rule.js:956> Rule#rule-krpft5eh (Lounge - Harmony PS4 Activity Start - Wake PS4 Shell Command) evaluate() acquiring mutex 2021-08-04T13:08:32.535Z <Engine:5:Engine.js:1145> _process_reaction_queue() wake-up! 2021-08-04T13:08:32.536Z <Rule:5:Rule.js:960> Rule#rule-krpft5eh._evaluate() mutex acquired, evaluating 2021-08-04T13:08:32.537Z <Rule:5:Rule.js:964> Rule#rule-krpft5eh update rate is 6/min limit 60/min 2021-08-04T13:08:32.537Z <Rule:5:Rule.js:887> Rule#rule-krpft5eh evaluateExpressions() with 1 expressions 2021-08-04T13:08:32.538Z <Rule:5:Rule.js:976> Rule#rule-krpft5eh._evaluate() trigger state now true (was true) 2021-08-04T13:08:32.539Z <Rule:5:Rule.js:978> Rule#rule-krpft5eh._evaluate() constraints state true 2021-08-04T13:08:32.540Z <Rule:5:Rule.js:987> Rule#rule-krpft5eh rule state now true, changed no 2021-08-04T13:08:32.541Z <Engine:5:Engine.js:1106> _process_reaction_queue() running task 2261 { "tid": 2261, "id": "rule-krpft5eh:S", "rule": "rule-krpft5eh", "__reaction": [RuleReaction#rule-krpft5eh:S], "next_step": 3, "status": 1, "ts": 1628082499978, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 2 } 2021-08-04T13:08:32.542Z <Engine:NOTICE> Resuming reaction Lounge - Harmony PS4 Activity Start - Wake PS4 Shell Command<SET> (rule-krpft5eh:S) from step 3 2021-08-04T13:08:32.542Z <Engine:INFO> Lounge - Harmony PS4 Activity Start - Wake PS4 Shell Command<SET> all actions completed. 2021-08-04T13:08:32.543Z <Engine:5:Engine.js:1110> _process_reaction_queue() task returned, new status -1; task 2261 2021-08-04T13:08:32.545Z <Engine:5:Engine.js:1145> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting 2021-08-04T13:08:32.832Z <Rule:5:Rule.js:748> Rule#rule-knn2os0h dependency notification entity-changed Entity#vera>device_184 from Entity#vera>device_184 2021-08-04T13:08:32.834Z <Rule:5:Rule.js:754> Rule#rule-knn2os0h requesting eval; entity-changed Entity#vera>device_184 2021-08-04T13:08:32.836Z <Rule:5:Rule.js:748> Rule#rule-klkppx0h dependency notification entity-changed Entity#vera>device_184 from Entity#vera>device_184 2021-08-04T13:08:32.837Z <Rule:5:Rule.js:754> Rule#rule-klkppx0h requesting eval; entity-changed Entity#vera>device_184 2021-08-04T13:08:32.838Z <Rule:5:Rule.js:748> Rule#rule-krpft5eh dependency notification entity-changed Entity#vera>device_184 from Entity#vera>device_184 2021-08-04T13:08:32.839Z <Rule:5:Rule.js:754> Rule#rule-krpft5eh requesting eval; entity-changed Entity#vera>device_184 2021-08-04T13:08:32.839Z <Rule:5:Rule.js:956> Rule#rule-knn2os0h (Lounge - Harmony XBOX Activity Start - Close Window Coverings (Day)) evaluate() acquiring mutex 2021-08-04T13:08:32.840Z <Rule:5:Rule.js:956> Rule#rule-klkppx0h (Lounge - Harmony Powered OFF - Turn OFF LED strips) evaluate() acquiring mutex 2021-08-04T13:08:32.841Z <Rule:5:Rule.js:956> Rule#rule-krpft5eh (Lounge - Harmony PS4 Activity Start - Wake PS4 Shell Command) evaluate() acquiring mutex 2021-08-04T13:08:32.841Z <Rule:5:Rule.js:960> Rule#rule-knn2os0h._evaluate() mutex acquired, evaluating 2021-08-04T13:08:32.842Z <Rule:5:Rule.js:964> Rule#rule-knn2os0h update rate is 6/min limit 60/min 2021-08-04T13:08:32.843Z <Rule:5:Rule.js:887> Rule#rule-knn2os0h evaluateExpressions() with 0 expressions 2021-08-04T13:08:32.844Z <Rule:5:Rule.js:976> Rule#rule-knn2os0h._evaluate() trigger state now false (was false) 2021-08-04T13:08:32.846Z <Rule:5:Rule.js:978> Rule#rule-knn2os0h._evaluate() constraints state false 2021-08-04T13:08:32.847Z <Rule:5:Rule.js:987> Rule#rule-knn2os0h rule state now false, changed no 2021-08-04T13:08:32.847Z <Rule:5:Rule.js:960> Rule#rule-klkppx0h._evaluate() mutex acquired, evaluating 2021-08-04T13:08:32.848Z <Rule:5:Rule.js:964> Rule#rule-klkppx0h update rate is 6/min limit 60/min 2021-08-04T13:08:32.848Z <Rule:5:Rule.js:887> Rule#rule-klkppx0h evaluateExpressions() with 0 expressions 2021-08-04T13:08:32.849Z <Rule:5:Rule.js:976> Rule#rule-klkppx0h._evaluate() trigger state now true (was true) 2021-08-04T13:08:32.850Z <Rule:5:Rule.js:978> Rule#rule-klkppx0h._evaluate() constraints state false 2021-08-04T13:08:32.851Z <Rule:5:Rule.js:987> Rule#rule-klkppx0h rule state now false, changed no 2021-08-04T13:08:32.851Z <Rule:5:Rule.js:960> Rule#rule-krpft5eh._evaluate() mutex acquired, evaluating 2021-08-04T13:08:32.852Z <Rule:5:Rule.js:964> Rule#rule-krpft5eh update rate is 7/min limit 60/min 2021-08-04T13:08:32.853Z <Rule:5:Rule.js:887> Rule#rule-krpft5eh evaluateExpressions() with 1 expressions 2021-08-04T13:08:32.854Z <Rule:5:Rule.js:976> Rule#rule-krpft5eh._evaluate() trigger state now true (was true) 2021-08-04T13:08:32.854Z <Rule:5:Rule.js:978> Rule#rule-krpft5eh._evaluate() constraints state true 2021-08-04T13:08:32.856Z <Rule:5:Rule.js:987> Rule#rule-krpft5eh rule state now true, changed no 2021-08-04T13:08:33.082Z <Rule:5:Rule.js:748> Rule#rule-knn2os0h dependency notification entity-changed Entity#vera>device_184 from Entity#vera>device_184 2021-08-04T13:08:33.083Z <Rule:5:Rule.js:754> Rule#rule-knn2os0h requesting eval; entity-changed Entity#vera>device_184 2021-08-04T13:08:33.084Z <Rule:5:Rule.js:748> Rule#rule-klkppx0h dependency notification entity-changed Entity#vera>device_184 from Entity#vera>device_184 2021-08-04T13:08:33.085Z <Rule:5:Rule.js:754> Rule#rule-klkppx0h requesting eval; entity-changed Entity#vera>device_184 2021-08-04T13:08:33.086Z <Rule:5:Rule.js:748> Rule#rule-krpft5eh dependency notification entity-changed Entity#vera>device_184 from Entity#vera>device_184 2021-08-04T13:08:33.087Z <Rule:5:Rule.js:754> Rule#rule-krpft5eh requesting eval; entity-changed Entity#vera>device_184 2021-08-04T13:08:33.088Z <Rule:5:Rule.js:956> Rule#rule-knn2os0h (Lounge - Harmony XBOX Activity Start - Close Window Coverings (Day)) evaluate() acquiring mutex 2021-08-04T13:08:33.089Z <Rule:5:Rule.js:956> Rule#rule-klkppx0h (Lounge - Harmony Powered OFF - Turn OFF LED strips) evaluate() acquiring mutex 2021-08-04T13:08:33.090Z <Rule:5:Rule.js:956> Rule#rule-krpft5eh (Lounge - Harmony PS4 Activity Start - Wake PS4 Shell Command) evaluate() acquiring mutex 2021-08-04T13:08:33.090Z <Rule:5:Rule.js:960> Rule#rule-knn2os0h._evaluate() mutex acquired, evaluating 2021-08-04T13:08:33.091Z <Rule:5:Rule.js:964> Rule#rule-knn2os0h update rate is 7/min limit 60/min 2021-08-04T13:08:33.091Z <Rule:5:Rule.js:887> Rule#rule-knn2os0h evaluateExpressions() with 0 expressions 2021-08-04T13:08:33.092Z <Rule:5:Rule.js:976> Rule#rule-knn2os0h._evaluate() trigger state now false (was false) 2021-08-04T13:08:33.093Z <Rule:5:Rule.js:978> Rule#rule-knn2os0h._evaluate() constraints state false 2021-08-04T13:08:33.094Z <Rule:5:Rule.js:987> Rule#rule-knn2os0h rule state now false, changed no 2021-08-04T13:08:33.095Z <Rule:5:Rule.js:960> Rule#rule-klkppx0h._evaluate() mutex acquired, evaluating 2021-08-04T13:08:33.095Z <Rule:5:Rule.js:964> Rule#rule-klkppx0h update rate is 7/min limit 60/min 2021-08-04T13:08:33.096Z <Rule:5:Rule.js:887> Rule#rule-klkppx0h evaluateExpressions() with 0 expressions 2021-08-04T13:08:33.097Z <Rule:5:Rule.js:1595> cond cond58zlosr evaluation state true->false 2021-08-04T13:08:33.098Z <Rule:5:Rule.js:1595> cond trig evaluation state true->false 2021-08-04T13:08:33.098Z <Rule:5:Rule.js:976> Rule#rule-klkppx0h._evaluate() trigger state now false (was true) 2021-08-04T13:08:33.099Z <Rule:5:Rule.js:978> Rule#rule-klkppx0h._evaluate() constraints state false 2021-08-04T13:08:33.100Z <Rule:5:Rule.js:984> Rule#rule-klkppx0h trigger conditions not met 2021-08-04T13:08:33.100Z <Rule:5:Rule.js:987> Rule#rule-klkppx0h rule state now false, changed no 2021-08-04T13:08:33.102Z <Rule:5:Rule.js:960> Rule#rule-krpft5eh._evaluate() mutex acquired, evaluating 2021-08-04T13:08:33.103Z <Rule:5:Rule.js:964> Rule#rule-krpft5eh update rate is 8/min limit 60/min 2021-08-04T13:08:33.103Z <Rule:5:Rule.js:887> Rule#rule-krpft5eh evaluateExpressions() with 1 expressions 2021-08-04T13:08:33.104Z <Rule:5:Rule.js:976> Rule#rule-krpft5eh._evaluate() trigger state now true (was true) 2021-08-04T13:08:33.105Z <Rule:5:Rule.js:978> Rule#rule-krpft5eh._evaluate() constraints state true 2021-08-04T13:08:33.105Z <Rule:5:Rule.js:987> Rule#rule-krpft5eh rule state now true, changed no
I will try and implement the script now.
-
I've created the ps4-wrapper.sh file and made it executable and placed it in to the Reactor root directory as I cannot find where the actual ps4-waker utility is installed / located on the system.
When I try to run the script in terminal I get errors:
root@HP-Thin01:/home/stuart/reactor# bash ps4-wrapper.sh ps4-wrapper.sh: line 15: syntax error: unexpected end of file root@HP-Thin01:/home/stuart/reactor# sh ps4-wrapper.sh ps4-wrapper.sh: 14: ps4-wrapper.sh: Syntax error: end of file unexpected (expecting "then") root@HP-Thin01:/home/stuart/reactor#
Also how do I modify the MSR rules to run the script instead of the command directly ?
I tried this:
Thanks
EDIT:
Seems it didn't like me creating the script in Notepad++ on Windows and copying it over to the Debian machine.
So I deleted the script and created it again using nano editor on Debian and now I can run the script OK from the terminal window and the PS4 did turn ON.
However I cannot run the script from the MSR rule still, nothing seems to happen when I play the reaction.
I can't see any errors related to ps4-wrapper.sh
2021-08-04T14:14:30.725Z <Engine:5:Engine.js:1145> _process_reaction_queue() wake-up! 2021-08-04T14:14:30.731Z <Engine:5:Engine.js:1106> _process_reaction_queue() running task 2373 { "tid": 2373, "id": "rule-krpft5eh:S", "rule": "rule-krpft5eh", "__reaction": [RuleReaction#rule-krpft5eh:S], "next_step": 1, "status": 0, "ts": 1628086468720, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 1 } 2021-08-04T14:14:30.731Z <Engine:NOTICE> Resuming reaction Lounge - Harmony PS4 Activity Start - Wake PS4 Shell Command<SET> (rule-krpft5eh:S) from step 1 2021-08-04T14:14:30.732Z <Engine:INFO> Engine#1 reaction Lounge - Harmony PS4 Activity Start - Wake PS4 Shell Command<SET> (rule-krpft5eh:S) step 2 shell command: ps4-wrapper.sh 2021-08-04T14:14:30.733Z <Engine:5:Engine.js:1382> Engine#1 action data { "command": "ps4-wrapper.sh", "rule": "rule-krpft5eh", "rvar": "ps4waker", "ignore_exit": true } 2021-08-04T14:14:30.749Z <Engine:5:Engine.js:1110> _process_reaction_queue() task returned, new status 3; task 2373 2021-08-04T14:14:30.751Z <Engine:5:Engine.js:1145> _process_reaction_queue ending with 1 in queue; none delayed/ready; waiting 2021-08-04T14:14:30.755Z <Rule:5:Rule.js:660> Rule#rule-krpft5eh rule set variable ps4waker = (string) 2021-08-04T14:14:30.755Z <Engine:5:Engine.js:945> Engine#1 set variable rule rule-krpft5eh ps4waker=, requesting re-eval 2021-08-04T14:14:30.756Z <Rule:5:Rule.js:956> Rule#rule-krpft5eh (Lounge - Harmony PS4 Activity Start - Wake PS4 Shell Command) evaluate() acquiring mutex 2021-08-04T14:14:30.757Z <Engine:5:Engine.js:1145> _process_reaction_queue() wake-up! 2021-08-04T14:14:30.758Z <Rule:5:Rule.js:960> Rule#rule-krpft5eh._evaluate() mutex acquired, evaluating 2021-08-04T14:14:30.758Z <Rule:5:Rule.js:964> Rule#rule-krpft5eh update rate is 1/min limit 60/min 2021-08-04T14:14:30.759Z <Rule:5:Rule.js:887> Rule#rule-krpft5eh evaluateExpressions() with 1 expressions 2021-08-04T14:14:30.760Z <Rule:5:Rule.js:976> Rule#rule-krpft5eh._evaluate() trigger state now true (was true) 2021-08-04T14:14:30.761Z <Rule:5:Rule.js:978> Rule#rule-krpft5eh._evaluate() constraints state true 2021-08-04T14:14:30.762Z <Rule:5:Rule.js:987> Rule#rule-krpft5eh rule state now true, changed no 2021-08-04T14:14:30.763Z <Engine:5:Engine.js:1106> _process_reaction_queue() running task 2373 { "tid": 2373, "id": "rule-krpft5eh:S", "rule": "rule-krpft5eh", "__reaction": [RuleReaction#rule-krpft5eh:S], "next_step": 3, "status": 1, "ts": 1628086468720, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 2 } 2021-08-04T14:14:30.764Z <Engine:NOTICE> Resuming reaction Lounge - Harmony PS4 Activity Start - Wake PS4 Shell Command<SET> (rule-krpft5eh:S) from step 3 2021-08-04T14:14:30.764Z <Engine:INFO> Lounge - Harmony PS4 Activity Start - Wake PS4 Shell Command<SET> all actions completed. 2021-08-04T14:14:30.765Z <Engine:5:Engine.js:1110> _process_reaction_queue() task returned, new status -1; task 2373 2021-08-04T14:14:30.767Z <Engine:5:Engine.js:1145> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting 2021-08-04T14:14:34.579Z <EzloController:5:EzloController.js:1069> EzloController#ezlo-plus received message 485 bytes
Just seen an unrelated error in the logs
<EzloController:ERR> EzloController#ezlo-plus no implementation mapping for attributes from match * cap x_ezlo_object
-
When you create the file on Windows in Notepad++, it will get Windows line endings (CR+LF) instead of Unix line endings (LF alone) and that confuses the shell. You can select the right line endings under the Edit > EOL Conversion in Notepad++.
If you modified the
ps4-waker
command to be anything other thanps4-waker $*
put it back the way I gave it to you. That lets you run the wrapper script with arguments on the command line that will get passed through, like this:./ps4-wrapper.sh status
or./ps4-wrapper.sh somethingelse
In the MSR rule, you should use
/full/path/to/ps4-wrapper.sh arguments