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.
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 ,
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
I have got some warnings i reactor that a rule is throttled because it update rate is over 120/minute, happens now and when with a week or two in between.
The rule monitors my house power consumption when charging my car, and if if consumption risks to kill a main fuse, it stops the charging.
Thought I was clever when I in Constraints added that my car should be located at home and charging is active, but apparantly it wasn't clever enough...
I had understand it that if Constraints isn't true, then the triggers isn't evaluated.
I have a Shelly 3EM meter that measure three channel/phases and updates every second. So just for this three channels it is 180 updates per minute...
And now when I start to take a closer look I can se in my logs that this rule is evaluated with every value change on any of the three phases...
So ~11MB of logs only goes back in time around 16 hours...🙀
So what is the best solution?
Should move my "Constraints" in an new trigger group, before my existing triggers?
Rule as it is now
e5486a1b-7c3c-4ffc-b259-beed64948f2e-image.png
Hi!
I'm wondering if it's possible now, or if it's something that can be solved in a future version, to be able to remove the entities that no longer exist and are crossed out all at once. Currently, you have to mark them one by one, which takes a lot of time. Is there any way to make this more efficient?
I'm on MSR version 24212-3ce15e25.
Thanks!
/Fanan
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/fluidicon.png)
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 🙂
Good morning,
I'm trying to figure out if there is a way to evaluate if a command was completed and retry if it did not complete.
I have 14 iBlinds 3.1 z-wave controllers in my home. 95% of the time, they work just fine. Occasionally, I'll get a blind that does not open on the first attempt. When I go into Home Assistant, and manually open or close the blind, it works.
I have 3 reactions set up for each room. One to open, one to close, and one partial open for sun glare. Each of them is set up as below.
5afc9924-4300-4718-9e23-8855c4a3a9fd-image.png
The reactions are set up to wait for 5 seconds before going onto the next blind, so the z-wave network doesn't get overwhelmed.
In addition, the set command to run the reactions has "Wait for completion" checked.
3919fc06-c1f1-4c49-bf95-716028d18a27-image.png
I also have a routine set up whenever a z-wave device reports as non-functional (dead), it'll get pinged to wake it up. This usually works to wake them up.
16df4bff-c733-4ec2-a55c-c964238ada3b-image.png
Appreciate any ideas to make this more reliable.
I'm running:
Reactor latest-24190-bd310acc, Bare-metal on Fedora WaveJSController [0.1.23326] Home Assistant: 2024.7.0[SOLVED] All Modes not visible in MSR 21337 from Hubitat
-
I updated to
latest-21337-b535732
last night before heading off to sleep. I have a ruleset that checks forphone charging
, modeevening
, and room-assistanthome
. The system then waits five minutes and flips to modenight
and announces it has done so via Echo devices.At 05:30 ET each morning the system shifts to mode
day
.However...
Last night MSR went thru the paces but mode
evening
never switched to modenight
. Multiple attempts including reboots of MSR and Hubitat, no change.This morning, instead of mode
day
it went back to modeevening
which isn't supposed to trigger until sunset. This is confirmed across MSR, H-A, and Hubitat.I'd missed the 21336 update and went from 21332 to 21337. I'll be log diving after coffee is ready.
Updated title to reflect what the issue seems to actually be.
-
@gwp1 This is interesting: can't have the house in mode
evening
so I hit thereset
icon on theday mode
rulesetRule ID: rule-kmfo3pz8
. It shows I took the action:...but I don't see any reference to that action in the log nor did the mode change to
day
.This is the log since 0529 ET.
[latest-21337]2021-12-04T15:05:29.018Z <Rule:NOTICE> Rule#rule-kmfo3pz8 resetting! [latest-21337]2021-12-04T15:05:29.020Z <Rule:NOTICE> Rule#rule-kmfo3pz8 stopping rule [latest-21337]2021-12-04T15:05:29.021Z <Rule:5:Rule.js:743> Rule#rule-kmfo3pz8 acquiring semaphore [latest-21337]2021-12-04T15:05:29.023Z <Rule:5:Rule.js:746> Rule#rule-kmfo3pz8 semaphore acquired; releasing timer [latest-21337]2021-12-04T15:05:29.024Z <Rule:5:Rule.js:746> Rule#rule-kmfo3pz8 semaphore acquired; unsubscribing from condition dependencies [latest-21337]2021-12-04T15:05:29.036Z <Rule:5:Rule.js:748> Rule#rule-kmfo3pz8 saving states [latest-21337]2021-12-04T15:05:29.041Z <Rule:5:Rule.js:752> Rule#rule-kmfo3pz8 stopped [latest-21337]2021-12-04T15:05:29.041Z <Rule:NOTICE> Rule Rule#rule-kmfo3pz8 stopped [latest-21337]2021-12-04T15:05:29.044Z <Rule:NOTICE> Rule#rule-kmfo3pz8 restarting after reset [latest-21337]2021-12-04T15:05:29.045Z <Rule:5:Rule.js:716> Rule#rule-kmfo3pz8 start(), awaiting semaphore [latest-21337]2021-12-04T15:05:29.051Z <Rule:5:Rule.js:724> Rule#rule-kmfo3pz8 restored states: trig=(null), rule=(null) [latest-21337]2021-12-04T15:05:29.052Z <Rule:5:Rule.js:724> Rule#rule-kmfo3pz8 subscribing to dependencies [latest-21337]2021-12-04T15:05:29.053Z <Rule:INFO> Rule#rule-kmfo3pz8 (Day mode: 05:30 ET) started [latest-21337]2021-12-04T15:05:29.054Z <Rule:5:Rule.js:728> Rule#rule-kmfo3pz8 start() dependencies resolved, performing initial evaluation [latest-21337]2021-12-04T15:05:29.055Z <Rule:5:Rule.js:1005> Rule#rule-kmfo3pz8 (Day mode: 05:30 ET) evaluate() acquiring mutex [latest-21337]2021-12-04T15:05:29.056Z <Rule:5:Rule.js:1009> Rule#rule-kmfo3pz8._evaluate() mutex acquired, evaluating [latest-21337]2021-12-04T15:05:29.057Z <Rule:5:Rule.js:1013> Rule#rule-kmfo3pz8 update rate is 0/min limit 60/min [latest-21337]2021-12-04T15:05:29.058Z <Rule:5:Rule.js:936> Rule#rule-kmfo3pz8 evaluateExpressions() with 0 expressions [latest-21337]2021-12-04T15:05:29.065Z <Rule:5:Rule.js:1689> cond cond6xza990 evaluation state (null)->false [latest-21337]2021-12-04T15:05:29.069Z <Rule:5:Rule.js:1689> cond condkmfo3pz8 evaluation state (null)->true [latest-21337]2021-12-04T15:05:29.074Z <Rule:5:Rule.js:1689> cond condeadfqgq evaluation state (null)->true [latest-21337]2021-12-04T15:05:29.075Z <Rule:5:Rule.js:1689> cond trig evaluation state (null)->false [latest-21337]2021-12-04T15:05:29.079Z <Rule:5:Rule.js:1033> Rule#rule-kmfo3pz8._evaluate() trigger state now false (was (null)) [latest-21337]2021-12-04T15:05:29.080Z <Rule:5:Rule.js:1035> Rule#rule-kmfo3pz8._evaluate() constraints state true [latest-21337]2021-12-04T15:05:29.081Z <Rule:5:Rule.js:1041> Rule#rule-kmfo3pz8 trigger conditions not met [latest-21337]2021-12-04T15:05:29.081Z <Rule:5:Rule.js:1042> Rule#rule-kmfo3pz8 rule state changed, was (undefined) now false [latest-21337]2021-12-04T15:05:29.082Z <Rule:INFO> Day mode: 05:30 ET (Rule#rule-kmfo3pz8) RESET! [latest-21337]2021-12-04T15:05:29.083Z <Rule:5:Rule.js:1044> Rule#rule-kmfo3pz8 rule state now false, changed true [latest-21337]2021-12-04T15:05:38.996Z <Rule:5:Rule.js:793> Rule#rule-grpoix7c2a Office On/Off requesting eval; entity-changed from Entity#hubitat>51 [latest-21337]2021-12-04T15:05:38.997Z <Rule:5:Rule.js:1005> Rule#rule-grpoix7c2a (Office On/Off) evaluate() acquiring mutex [latest-21337]2021-12-04T15:05:38.998Z <Rule:5:Rule.js:1009> Rule#rule-grpoix7c2a._evaluate() mutex acquired, evaluating [latest-21337]2021-12-04T15:05:38.999Z <Rule:5:Rule.js:1013> Rule#rule-grpoix7c2a update rate is 4/min limit 60/min [latest-21337]2021-12-04T15:05:39.000Z <Rule:5:Rule.js:936> Rule#rule-grpoix7c2a evaluateExpressions() with 0 expressions [latest-21337]2021-12-04T15:05:39.006Z <Rule:5:Rule.js:1033> Rule#rule-grpoix7c2a._evaluate() trigger state now false (was false) [latest-21337]2021-12-04T15:05:39.007Z <Rule:5:Rule.js:1035> Rule#rule-grpoix7c2a._evaluate() constraints state true [latest-21337]2021-12-04T15:05:39.008Z <Rule:5:Rule.js:1044> Rule#rule-grpoix7c2a rule state now false, changed no [latest-21337]2021-12-04T15:05:45.991Z <Rule:5:Rule.js:793> Rule#rule-grpoix7c2a Office On/Off requesting eval; entity-changed from Entity#hubitat>51 [latest-21337]2021-12-04T15:05:45.995Z <Rule:5:Rule.js:1005> Rule#rule-grpoix7c2a (Office On/Off) evaluate() acquiring mutex [latest-21337]2021-12-04T15:05:45.998Z <Rule:5:Rule.js:1009> Rule#rule-grpoix7c2a._evaluate() mutex acquired, evaluating [latest-21337]2021-12-04T15:05:46.000Z <Rule:5:Rule.js:1013> Rule#rule-grpoix7c2a update rate is 4/min limit 60/min [latest-21337]2021-12-04T15:05:46.002Z <Rule:5:Rule.js:936> Rule#rule-grpoix7c2a evaluateExpressions() with 0 expressions [latest-21337]2021-12-04T15:05:46.005Z <Rule:5:Rule.js:1033> Rule#rule-grpoix7c2a._evaluate() trigger state now false (was false) [latest-21337]2021-12-04T15:05:46.007Z <Rule:5:Rule.js:1035> Rule#rule-grpoix7c2a._evaluate() constraints state true [latest-21337]2021-12-04T15:05:46.009Z <Rule:5:Rule.js:1044> Rule#rule-grpoix7c2a rule state now false, changed no [latest-21337]2021-12-04T15:06:02.533Z <Rule:5:Rule.js:793> Rule#rule-kphozuch Upstairs bulb requesting eval; entity-changed from Entity#hubitat>55 [latest-21337]2021-12-04T15:06:02.534Z <Rule:5:Rule.js:793> Rule#rule-komaz8fr Upstairs motion requesting eval; entity-changed from Entity#hubitat>55 [latest-21337]2021-12-04T15:06:02.535Z <Rule:5:Rule.js:1005> Rule#rule-kphozuch (Upstairs bulb) evaluate() acquiring mutex [latest-21337]2021-12-04T15:06:02.535Z <Rule:5:Rule.js:1005> Rule#rule-komaz8fr (Upstairs motion) evaluate() acquiring mutex [latest-21337]2021-12-04T15:06:02.536Z <Rule:5:Rule.js:1009> Rule#rule-kphozuch._evaluate() mutex acquired, evaluating [latest-21337]2021-12-04T15:06:02.537Z <Rule:5:Rule.js:1013> Rule#rule-kphozuch update rate is 0/min limit 60/min [latest-21337]2021-12-04T15:06:02.538Z <Rule:5:Rule.js:936> Rule#rule-kphozuch evaluateExpressions() with 0 expressions [latest-21337]2021-12-04T15:06:02.540Z <Rule:5:Rule.js:1033> Rule#rule-kphozuch._evaluate() trigger state now false (was false) [latest-21337]2021-12-04T15:06:02.541Z <Rule:5:Rule.js:1035> Rule#rule-kphozuch._evaluate() constraints state true [latest-21337]2021-12-04T15:06:02.541Z <Rule:5:Rule.js:1044> Rule#rule-kphozuch rule state now false, changed no [latest-21337]2021-12-04T15:06:02.545Z <Rule:5:Rule.js:1009> Rule#rule-komaz8fr._evaluate() mutex acquired, evaluating [latest-21337]2021-12-04T15:06:02.545Z <Rule:5:Rule.js:1013> Rule#rule-komaz8fr update rate is 0/min limit 60/min [latest-21337]2021-12-04T15:06:02.546Z <Rule:5:Rule.js:936> Rule#rule-komaz8fr evaluateExpressions() with 0 expressions [latest-21337]2021-12-04T15:06:02.548Z <Rule:5:Rule.js:1033> Rule#rule-komaz8fr._evaluate() trigger state now false (was false) [latest-21337]2021-12-04T15:06:02.549Z <Rule:5:Rule.js:1035> Rule#rule-komaz8fr._evaluate() constraints state true [latest-21337]2021-12-04T15:06:02.549Z <Rule:5:Rule.js:1044> Rule#rule-komaz8fr rule state now false, changed no [latest-21337]2021-12-04T15:06:03.376Z <Rule:5:Rule.js:793> Rule#rule-grpoix7c2a Office On/Off requesting eval; timer-trigger from Timer#rule-grpoix7c2a [latest-21337]2021-12-04T15:06:03.377Z <Rule:5:Rule.js:1005> Rule#rule-grpoix7c2a (Office On/Off) evaluate() acquiring mutex [latest-21337]2021-12-04T15:06:03.378Z <Rule:5:Rule.js:1009> Rule#rule-grpoix7c2a._evaluate() mutex acquired, evaluating [latest-21337]2021-12-04T15:06:03.379Z <Rule:5:Rule.js:1013> Rule#rule-grpoix7c2a update rate is 3/min limit 60/min [latest-21337]2021-12-04T15:06:03.380Z <Rule:5:Rule.js:936> Rule#rule-grpoix7c2a evaluateExpressions() with 0 expressions [latest-21337]2021-12-04T15:06:03.381Z <Rule:5:Rule.js:1033> Rule#rule-grpoix7c2a._evaluate() trigger state now false (was false) [latest-21337]2021-12-04T15:06:03.382Z <Rule:5:Rule.js:1035> Rule#rule-grpoix7c2a._evaluate() constraints state true [latest-21337]2021-12-04T15:06:03.383Z <Rule:5:Rule.js:1044> Rule#rule-grpoix7c2a rule state now false, changed no
-
I just tested mode sensitivity, which I also had done before the build, and it's working as expected. So that part is fine. The log shows "Day mode" rule is going to Reset state, so unless your action is in the Reset reaction, I wouldn't expect it to log the change you seem to anticipate. You haven't shown the rules or reactions, so I have no way of judging what it will do or whether what I can see it doing is right. Show your work, please! Also check your host time zone settings. Logs are Zulu (UTC), not ET, and that would account for a five hour difference in host time vs log time, normally (standard time).
http://your-reactor-ip:8111/diag/sun
Also look at the rule detail panel any time you are troubleshooting logic. Your log snippets don't show any actions being run at all for
rule-kmfo3pz8
, just the rule eval/update to Reset state. Logging of actions in HubitatController is currently unconditional, so if any action was being sent, it would be in the logs (regardless of log level). -
@toggledbits
The host time is currently 12/4/2021, 10:41:24 AM offset -300 minutes from UTC
, which lines up to log timestamps of 15:xx:xx.This ruleset hasn't changed since MSR came online months ago so I'm loathe to point to that, esp since it's across multiple modes.
Searching the log for this ruleset shows it first appearing at that RESET! line.
I've rolled back to 21332 and retested. Mode
day
did not kick over as expected. Given this has worked flawlessly with this build I'm digging further. Right now it appears like the house never moved to modenight
even though all the actions (lights off, announcement made, unlocked locks locked) happened.How far back does MSR retain logs time-wise?
-
@gwp1 said in Modes not changing correctly since 21337:
How far back does MSR retain logs time-wise?
As far as your log rotation allows.
Can you go back to 21337 and show the result of the rule detail/status panel?
Also, make sure to check the case of all mode setting actions. Mode names are case-sensitive in Hubitat ( day =/= Day ), so if they don't match, the action won't work. When testing in conditions, make sure the test is case-insensitive (it is in the rule you've shown, so that's good).
-
@toggledbits I just moved back to 21337 a moment ago. I cannot seem to get the house into mode
night
atm. Troubleshooting this as my thinking now is that the house, though doing all the actions (and I repeated that just now), doesn't actually going into modenight
anymore. -
Try "Night" (capital N)... case matters to Hubitat
-
@toggledbits When it is time for the house to go into
night
there is an Alexa routine that flips a virtual switch. This is the sole trigger and the result is the running of a Reaction.This has been unchanged.
At the end of the reaction is a :10 delay and the virtual switch flips back off again (for next time.) That's it. Nothing fancy. All of these steps are working except for the mode actually changing to
night
.This has worked for MONTHS untouched. I'm literally watching it step thru here:
-
This post is deleted!
-
@toggledbits This is odd. Wouldn't I expect to see all the modes listed under
x_hubitat_sys_mode.modes={"Day":1}
?Tried setting
Night
from the Entities list actions. Nada.[latest-21337]2021-12-04T16:45:03.111Z <Rule:5:Rule.js:793> Rule#rule-kphozuch Upstairs bulb requesting eval; entity-changed from Entity#hubitat>55 [latest-21337]2021-12-04T16:45:03.112Z <Rule:5:Rule.js:793> Rule#rule-komaz8fr Upstairs motion requesting eval; entity-changed from Entity#hubitat>55 [latest-21337]2021-12-04T16:45:03.113Z <Rule:5:Rule.js:1005> Rule#rule-kphozuch (Upstairs bulb) evaluate() acquiring mutex [latest-21337]2021-12-04T16:45:03.114Z <Rule:5:Rule.js:1005> Rule#rule-komaz8fr (Upstairs motion) evaluate() acquiring mutex [latest-21337]2021-12-04T16:45:03.120Z <Rule:5:Rule.js:1009> Rule#rule-kphozuch._evaluate() mutex acquired, evaluating [latest-21337]2021-12-04T16:45:03.121Z <Rule:5:Rule.js:1013> Rule#rule-kphozuch update rate is 0/min limit 60/min [latest-21337]2021-12-04T16:45:03.122Z <Rule:5:Rule.js:936> Rule#rule-kphozuch evaluateExpressions() with 0 expressions [latest-21337]2021-12-04T16:45:03.124Z <Rule:5:Rule.js:1033> Rule#rule-kphozuch._evaluate() trigger state now false (was false) [latest-21337]2021-12-04T16:45:03.125Z <Rule:5:Rule.js:1035> Rule#rule-kphozuch._evaluate() constraints state true [latest-21337]2021-12-04T16:45:03.127Z <Rule:5:Rule.js:1044> Rule#rule-kphozuch rule state now false, changed no [latest-21337]2021-12-04T16:45:03.131Z <Rule:5:Rule.js:1009> Rule#rule-komaz8fr._evaluate() mutex acquired, evaluating [latest-21337]2021-12-04T16:45:03.133Z <Rule:5:Rule.js:1013> Rule#rule-komaz8fr update rate is 0/min limit 60/min [latest-21337]2021-12-04T16:45:03.134Z <Rule:5:Rule.js:936> Rule#rule-komaz8fr evaluateExpressions() with 0 expressions [latest-21337]2021-12-04T16:45:03.136Z <Rule:5:Rule.js:1033> Rule#rule-komaz8fr._evaluate() trigger state now false (was false) [latest-21337]2021-12-04T16:45:03.137Z <Rule:5:Rule.js:1035> Rule#rule-komaz8fr._evaluate() constraints state true [latest-21337]2021-12-04T16:45:03.139Z <Rule:5:Rule.js:1044> Rule#rule-komaz8fr rule state now false, changed no [latest-21337]2021-12-04T16:45:46.427Z <Rule:5:Rule.js:793> Rule#rule-grpoix7c2a Office On/Off requesting eval; entity-changed from Entity#hubitat>51 [latest-21337]2021-12-04T16:45:46.429Z <Rule:5:Rule.js:1005> Rule#rule-grpoix7c2a (Office On/Off) evaluate() acquiring mutex [latest-21337]2021-12-04T16:45:46.431Z <Rule:5:Rule.js:1009> Rule#rule-grpoix7c2a._evaluate() mutex acquired, evaluating [latest-21337]2021-12-04T16:45:46.432Z <Rule:5:Rule.js:1013> Rule#rule-grpoix7c2a update rate is 2/min limit 60/min [latest-21337]2021-12-04T16:45:46.433Z <Rule:5:Rule.js:936> Rule#rule-grpoix7c2a evaluateExpressions() with 0 expressions [latest-21337]2021-12-04T16:45:46.436Z <Rule:5:Rule.js:1033> Rule#rule-grpoix7c2a._evaluate() trigger state now false (was false) [latest-21337]2021-12-04T16:45:46.437Z <Rule:5:Rule.js:1035> Rule#rule-grpoix7c2a._evaluate() constraints state true [latest-21337]2021-12-04T16:45:46.439Z <Rule:5:Rule.js:1044> Rule#rule-grpoix7c2a rule state now false, changed no [latest-21337]2021-12-04T16:45:46.673Z <HubitatController:null> HubitatController#hubitat final action path for x_hubitat_sys_mode.set on Entity#hubitat>sys_mode: http://192.168.1.214/apps/api/14/modes/Night
-
According to the entity, the only mode that exists on the hub is Day. Log in to your hub and check the Modes screen. If that agrees, something happened to your hub (firmware upgrade to latest new version recently?).
-
Latest release to 2.3.0.115 on Hubitat. Rolling back to .113 to see what happens.
-
-
Are you on their latest firmware?
-
@toggledbits Well I was until apparently an hour ago lol Seems there's .116 out now. Also, rolling back apparently doesn't restore the old firmware to .113 like I thought it would. I'm still on .115. Guess I'll fail forward to .116.
-
@gwp1 On Hubitat's latest, .116. No change.
Following my Rule#1 of troubleshooting, "what changed?" I rolled back MSR to 21332 (because I'd just updated to 21337) just in case and now I see this:
Things are behaving as they should. Using the
Entities
menu I triggered modenight
and it flipped over (only to flip back today
as it should because it's day time - but I watched it three times visibly flip to the correct mode.) -
Yup, and I think I see the issue... stay tuned...
-
OK. 21338