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.0I 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.
Good morning,
I'm going through my ruleset this morning, trying to get away from haas>blahblablah entries and completely migrate them all to zwavejs>xx-0 entries where possible.
I have 3 Aeon MultiSensor 6 devices in my home, all USB powered.
When using Haas entries, I see an entry for hass>binary_sensor_guest_bedroom_multisensor_home_security_motion_detection, and motion_sensor.state (primary)
Screenshot 2024-07-25 at 8.25.53 AM.png
Under ZwaveJS, this entry appears to be missing.
Screenshot 2024-07-25 at 8.26.51 AM.png
From the Entities page:
battery_power.level=1
battery_power.since=1721910337433
binary_sensor.state=false
humidity_sensor.units="%"
humidity_sensor.value=46
light_sensor.units="Lux"
light_sensor.value=5
tamper.state=false
temperature_sensor.units="°F"
temperature_sensor.value=73.8
x_debug.dt={}
x_zwave_values.Basic_currentValue=0
x_zwave_values.Battery_isLow=false
x_zwave_values.Battery_level=100
x_zwave_values.Binary_Sensor_Any=false
x_zwave_values.Configuration_Automatic_Report_Group_1_Battery_1=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Humidity_64=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Luminance_128=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Temperature_32=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Ultraviolet_16=1
x_zwave_values.Configuration_Automatic_Report_Group_2_Battery_1=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Humidity_64=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Luminance_128=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Temperature_32=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Ultraviolet_16=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Battery_1=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Humidity_64=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Luminance_128=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Temperature_32=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Ultraviolet_16=0
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_1=3600
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_2=3600
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_3=3600
x_zwave_values.Configuration_Automatic_Temperature_Reporting_Unit=2
x_zwave_values.Configuration_Battery_Level_Threshold=10
x_zwave_values.Configuration_Current_Power_Mode_65280=0
x_zwave_values.Configuration_Humidity_Above_Lower_Limit_32=0
x_zwave_values.Configuration_Humidity_Below_Lower_Limit_2=0
x_zwave_values.Configuration_Humidity_Change_Threshold=10
x_zwave_values.Configuration_Humidity_Recover_Limit=5
x_zwave_values.Configuration_Humidity_Sensor_Calibration=0
x_zwave_values.Configuration_LED_Blinking=0
x_zwave_values.Configuration_Lighting_Recover_Limit=10
x_zwave_values.Configuration_Lock_Configuration=0
x_zwave_values.Configuration_Low_Battery_Threshold=20
x_zwave_values.Configuration_Low_Temperature_Alarm_15_C=0
x_zwave_values.Configuration_Lower_Humidity_Limit=50
x_zwave_values.Configuration_Lower_Lighting_Limit=100
x_zwave_values.Configuration_Lower_Temperature_Limit_4294901760=320
x_zwave_values.Configuration_Lower_Temperature_Limit_Unit_3840=2
x_zwave_values.Configuration_Lower_Ultraviolet_Limit=4
x_zwave_values.Configuration_Luminance_Above_Lower_Limit_64=0
x_zwave_values.Configuration_Luminance_Below_Lower_Limit_4=0
x_zwave_values.Configuration_Luminance_Change_Threshold=100
x_zwave_values.Configuration_Luminance_Sensor_Calibration=0
x_zwave_values.Configuration_Motion_Sensor_Report_Type_to_Send=2
x_zwave_values.Configuration_PIR_Sensitivity=3
x_zwave_values.Configuration_PIR_Sensor_Timeout=20
x_zwave_values.Configuration_Recover_Limit_Temperature_Unit_255=2
x_zwave_values.Configuration_Report_Above_Humidity_Threshold_32=0
x_zwave_values.Configuration_Report_Above_Luminance_Threshold_64=0
x_zwave_values.Configuration_Report_Above_Temperature_Threshold_16=0
x_zwave_values.Configuration_Report_Above_Ultraviolet_Threshold_128=0
x_zwave_values.Configuration_Report_Below_Humidity_Threshold_2=0
x_zwave_values.Configuration_Report_Below_Luminance_Threshold_4=0
x_zwave_values.Configuration_Report_Below_Temperature_Threshold_1=0
x_zwave_values.Configuration_Report_Below_Ultraviolet_Threshold_8=0
x_zwave_values.Configuration_Reset_Parameters_101_103_to_Default_Values=null
x_zwave_values.Configuration_Reset_Parameters_111_113_to_Default_Values=null
x_zwave_values.Configuration_Reset_to_Factory_Default_Setting=null
x_zwave_values.Configuration_Selective_Reporting=0
x_zwave_values.Configuration_Sleep_State_255=2
x_zwave_values.Configuration_Temperature_Above_Lower_Limit_16=0
x_zwave_values.Configuration_Temperature_Below_Lower_Limit_1=0
x_zwave_values.Configuration_Temperature_Calibration_Offset_65280=0
x_zwave_values.Configuration_Temperature_Calibration_Unit_255=2
x_zwave_values.Configuration_Temperature_Change_Threshold_4294901760=20
x_zwave_values.Configuration_Temperature_Recover_Limit_65280=20
x_zwave_values.Configuration_Temperature_Threshold_Unit_3840=2
x_zwave_values.Configuration_Ultraviolet_Above_Lower_Limit_128=0
x_zwave_values.Configuration_Ultraviolet_Below_Lower_Limit_8=0
x_zwave_values.Configuration_Ultraviolet_Change_Threshold=2
x_zwave_values.Configuration_Ultraviolet_Recover_Limit=2
x_zwave_values.Configuration_Ultraviolet_Sensor_Calibration=0
x_zwave_values.Configuration_Upper_Humidity_Limit=60
x_zwave_values.Configuration_Upper_Lighting_Limit=1000
x_zwave_values.Configuration_Upper_Temperature_Limit_4294901760=824
x_zwave_values.Configuration_Upper_Temperature_Limit_Unit_3840=2
x_zwave_values.Configuration_Upper_Ultraviolet_Limit=8
x_zwave_values.Configuration_Wake_Device_for_10_minutes_After_Power_On=1
x_zwave_values.Configuration_Wake_Up_Timeout=15
x_zwave_values.Manufacturer_Specific_manufacturerId=134
x_zwave_values.Manufacturer_Specific_productId=100
x_zwave_values.Manufacturer_Specific_productType=258
x_zwave_values.Multilevel_Sensor_Air_temperature=73.8
x_zwave_values.Multilevel_Sensor_Humidity=46
x_zwave_values.Multilevel_Sensor_Illuminance=5
x_zwave_values.Multilevel_Sensor_Ultraviolet=0
x_zwave_values.Notification_Home_Security_Cover_status=0
x_zwave_values.Notification_Home_Security_Motion_sensor_status=0
x_zwave_values.Notification_alarmLevel=0
x_zwave_values.Notification_alarmType=0
x_zwave_values.Version_firmwareVersions=["1.17"]
x_zwave_values.Version_hardwareVersion=100
x_zwave_values.Version_libraryType=3
x_zwave_values.Version_protocolVersion="4.54"
x_zwave_values.Wake_Up_controllerNodeId=1
x_zwave_values.Wake_Up_wakeUpInterval=3600
zwave_device.capabilities=[32,48,49,112,113,114,128,132,134]
zwave_device.endpoint=0
zwave_device.failed=false
zwave_device.generic_class="Multilevel Sensor"
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=[134,258,100]
zwave_device.max_data_rate=null
zwave_device.node_id=53
zwave_device.specific_class="Routing Multilevel Sensor"
zwave_device.status=4
zwave_device.status_text="alive"
zwave_device.version_info=[null,"1.17"]
zwave_device.wakeup_interval=3600
I'm running:
Reactor latest-24190-bd310acc, Bare-metal on Fedora
WaveJSController [0.1.23326]
Home Assistant: 2024.7.0
I'm fetching certain data five past every hour, but I would like to do it closer to the hour, e.g. 1 or 2 past (but not at the hour).
I experimented with the following rule that almost works (triggers also at the hour which is not the intention). Any advice for a solution?
It would be nice to have an ability to bookmark a direct link to a dashboard item. In my case I would use this feature to access a virtual switch directly.
Hi @toggledbits
Would you please consider adding an extra sublevel in the rulesets?
I have grouped my rules in rooms/ areas. This works great for me, but I would also like to group rules for the same functionality (in a room). This would make the rules easier to find and name.
Please let me know if this is an option. Thanks!
@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 this device attached to my system, but use a DSC panel. If you need testers to move forward, I'm happy to help.
I'm curious what your thinking the use case is for this. I currently have it integrated into HomeAssistant, and it works fine for the most part. The one thing I can't do is bypass zones, which I would like to have the ability to do.
Are you looking at more direct control for the panel, as opposed to having to jump through HA (or another system) first?
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.I have the following ruleset which I though had been working well until this morning when I noticed it's not.
I've put four weather conditions in an in array and one of them is the current weather condition - but the rule is not true. Now the cloud cover percentage is not yet met but this is an or rule so as long as the "Current Conditions" are met then it should go true.
What's the obvious thing I'm missing here? (I've tried spaces/no spaces in the in and no difference.)
Hi,
Running the latest MSR latest-24152-3455578a with the latest HA 2024.6.1. When trying to call a service I get the following in the MSR logs. Is this a version mismatch? I am not seeing anything in the HA logs.
[latest-24152]2024-06-11T10:29:56.162Z <Rule:INFO> rule-Monitor-DHW (rule-lsvq5k3x in Central Heating) started [latest-24152]2024-06-11T10:29:58.625Z <HassController:WARN> HassController#hass unknown service opentherm_gw.set_hot_water_setpoint in x_hass.call_service action on Thermostat#hass>climate_living_room_otgw [latest-24152]2024-06-11T10:29:58.626Z <HassController:INFO> HassController#hass: sending payload for x_hass.call_service on Thermostat#hass>climate_living_room_otgw action: [Object]{ "type": "call_service", "service_data": { "gateway_id": "living_room_otgw", "temperature": 65 }, "domain": "opentherm_gw", "service": "set_hot_water_setpoint", "target": { "entity_id": "climate.living_room_otgw" } } [latest-24152]2024-06-11T10:29:58.627Z <HassController:ERR> HassController#hass request 1718101798626<6/11/2024, 12:29:58 PM> (call_service) failed: [Object]{ "id": 1718101798626, "type": "result", "success": false, "error": { "code": "invalid_format", "message": "extra keys not allowed @ data['entity_id']" } } [latest-24152]2024-06-11T10:29:58.627Z <HassController:WARN> HassController#hass action x_hass.call_service([Object]{ "service": "opentherm_gw.set_hot_water_setpoint", "data": "{ \"gateway_id\": \"living_room_otgw\", \"temperature\": 65 }" }) on Thermostat#hass>climate_living_room_otgw failed!Cheers Rene
Some background
I'm trying to integrate a Zigbee device into the MSR using zigbee2mqtt bridge and MQTTController. The device in question is a cheap mood light that has following properties that I'd like to control:
I'v already managed to get the switch part working and can toggle the light on/off. Also the brightness value is mapped back to MSR. In zigbee2mqtt it has a value range from 0 to 254, so this the reason for the expression:
expr: 'payload.brightness / 254'Here's the entity definition (don't know whether the type should be something else than the Switch)
zigbee-lidl-mood-light: name: 'Lidl Mood Light' friendly_name: 'Mood Light' type: Switch uses_template: lidl-moodlightAnd the corresponding template (NOTE: rgb_color has not been defined in this example):
lidl-moodlight: init: "zigbee2mqtt/%friendly_name%/get/state" query: "zigbee2mqtt/%friendly_name%/get/state" capabilities: - power_switch - toggle - dimming primary_attribute: power_switch.state events: "zigbee2mqtt/%friendly_name%": "power_switch.state": json_payload: true expr: 'upper(payload.state) == "ON"' "dimming.level": json_payload: true expr: 'payload.brightness / 254' actions: power_switch: "on": topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'ON' "off": topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'OFF' set: topic: "zigbee2mqtt/%friendly_name%/set/state" payload: expr: "parameters.state ? 'ON' : 'OFF'" type: raw toggle: topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'TOGGLE'The problem
In order to control the brightness or the RGB color values, I would have send a JSON payload in corresponding actions. But I have no idea how to define it in the template. The reason why the switch part is working is that the zigbee2mqtt accepts also plain ON / OFF / TOGGLE string payloads in that case.
But the brightness should be controlled with the following payload:
{"brightness": 196}And the RGB color like:
{"color":{"rgb":"46,102,150"}}Here's the link for the documentation (the Exposes part defines the messages).
So how should I define the JSON payload for example for the dimming action? It definitely should be some sort of expressions since I have to map the MSR real value (0...1) to (0...254) for the zigbee2mqtt.
actions: dimming: set: topic: "zigbee2mqtt/%friendly_name%/set" payload: expr: ????? type: jsonAnother problem is the RGB value. I could use the rgb_color capability for the setting but the problem is that the zigbee2mqtt only reports the current color in hue/saturation or xy coordinates.
Here's an example of published message after setting the color:
Topic: zigbee2mqtt/Mood Light QoS: 0 { "brightness":254, "color":{ "hue":240, "saturation":100, "x":0.1355, "y":0.0399 }, "color_mode":"xy", "color_temp":574, "linkquality":96, "state":"ON" }I would have to map those values back to RGB, but is it even possible with existing constructs in MQTTController's templates?
Help would be appreciated @toggledbits
br,
mgvra
That's probably more appropriate to post on Mantis for @toggledbits, but since I know there's at least @Crille publishing templates, my intent with this post is to open a broader discussion.
Long story short: I'm starting to slowly add new template for Shelly Plus and I noticed I'll end up with a dozen more templates, all similar but simply different in trivial details, all sharing a large amount of code and all needing special cares when fixing bugs/adding features (as the latest wifi_status addition).
So, I'm wondering if it's time to start thinking of some sort of inheritance in templates, where I could just create a generic shelly_gen1 and use it as a base for shelly_relay, and this be used as the base for shelly_relay_power and so on.
I could probably achieve this with some sort of scripting on my side to generate templates via code, but maybe there's a better way of doing this, or it's already on the radar.
I need a handful of victims volunteers to help test previews of the next build of Reactor. A long-standing request was for "a simple login mechanism," but in practice, adding user authentication and competent access control turned out to be a pretty big project with a lot of big changes on both server and client sides. It's a bit more than I'm comfortable testing myself and springing out to everyone at once, so I'd like to work with a small group to put it through "sea trials."
Major changes/features include:
User authentication with hashed password storage; User group configuration with application restriction (admin, dashboard, API); Detailed control over API access, with user- and token-based authentication/authorization; Improvements to the HTTPS service; Improvements to UI coordination with the core for Rules and Reactions.If this sounds like something you'd like to help with, drop me a reply here in this thread or privately.
[Solution: Reactor 24115 is not compatible with MQTTController > 24120]
Reactor latest-24115 bare metal.
All MQTT entities stop working after updating MQTTController to 24142, downgrade to 24120 and they are back. Templates and configured entities has not been changed between versions.
I'm not sure if uses_template should be replaced by ìnclude in entity configuration in reactor.yaml but I guess not, I've tried it and it did not do any difference.
I have not tried to update Reactor to userauth version.
Example entity in reactor.yaml that uses MQTTController included template:
entities: "takflakt_kallare": name: "Takfläkt källare" topic: "Källartemp" unit: "" uses_template: tasmota_generic_relay init: "cmnd/%topic%/POWER%unit%"Any hints? Do you need more info, please let me know.
Log from startup:
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 🙂
Is the following config correct?
- id: time_series name: "Out temp" capabilities: temperature_sensor: attributes: value: model: time series entity: "hass>sensor_outdoor_temperature" attribute: "temperature_sensor.value" interval: 5 # minutes retention: 20 # minutes aggregate: wma primary_attribute: temperature_sensor.value type: ValueSensorSpecifically, is "depth" directive needed/mandatory here? Reason I'm asking is that I'm not getting a "final" value in MSR, only debug values are shown:
temperature_sensor.units=null temperature_sensor.value=null x_virtualentity.last_request_time=null x_virtualentity.request_failures=null x_virtualentity.template=null x_virtualentity.timeseries_debug=[{"time":1716537360000,"value":22.1},{"time":1716537660000,"value":22},{"time":1716537960000,"value":22},{"time":1716538260000,"value":21.9},{"time":1716538560000,"value":22}]Good morning,
I apologize if this subject has been covered. I did try the search, but I'm not coming up with any topics on my issue.
I'm running userauth-24137-57b41335, bare metal installation on Fedora 39 Server.
I have a rule set up to turn the Eco mode off on my Nest Thermostat when the thermostat is set to Away (Rule State: Away Mode), the user (Driver) presence in my car changes to true, and the destination is set to home.
93804f7c-62d6-42c0-ae04-ff602011a6fd-image.png
This works fine for most days, where I'm headed home from work (commute is about 45 minutes). What I don't want it to do is set change it to Eco mode if my ETA is more than an hour.
There is a sensor/entity for Time to Arrival when the Destination is set. What it appears to provide is the Time OF arrival/ETA, not time until arrival. If it was Time until Arrival, and it was a numeric value, I could simply test if the value is less than 60 and be done with it.
I pulled up the history through Home Assistant for my morning commute and this appears to be what it is providing.
c2a32739-c84f-4a05-95d9-73793ed818f5-image.png
So what I need to do is to do a calculation of the the ETA from the sensor value and subtract the current time, and get a value in minutes that I can determine if it's less than 60.
I believe I can do this with the local expression, but I don't see anything for the system time, or local time. Also, do the local expressions update themselves if the sensors do?
Good morning,
I'm running userauth-24137-57b41335 on Fedora 39, bare metal installation.
ZWaveJSController 0.1.23254
Home Assistant:
Core, 2024.5.3 Supervisor, 2024.05.1 Operating System, 12.3 Frontend, 20240501.1I'm trying to troubleshoot a Dynamic Group Controller and notification alert that I've set up for low battery level.
In my Reactor.config, I have the following lines:
name: "Dynamic Group Controller" implementation: DynamicGroupController config: groups: "zwavejs_dead": select: - include_group: "zwavejs" filter_expression: "entity?.attributes?.zwave_device?.status == 3" group_actions: true "low_battery": select: - include_capability: battery_power filter_expression: > entity.attributes.battery_power.level < 0.35The idea here is that I should only have members of this group that have a battery level below 35%. When I go into Entities, I show a whole slew of devices, none of which have a battery level below the threshold.
a77e445b-ab78-4752-a624-3c4117f34f90-image.png
I also tried setting up a rule to generate a push notification once a day, but with all of the group members, I've had to disable the rule. I believe I have it set up correctly, but I'm not 100% sure. I want the notification to tell me the battery level for that device as well.
289b4f68-03ba-49c0-8275-f0f197d13a3a-image.png
ce24a76e-6865-40bd-bd85-632e54d315a8-image.png dc837424-deb5-4ef7-8f0d-3676f1769535-image.png
Can anyone point to me what I may have misconfigured to get these results?
I should also note I'm only interested in ZWaveJS devices. It's showing me battery status for my iPad and car as well, which I don't need it to send me.
Reactor Start - System Crash/Restart
-
Hello All -
I upgraded my OS to Ubuntu 20.04 today and have been regretting it for several hours. I have most of my system up. However, I've found that, when I start Reactor, it panics / reboots my OS. I've included the syslog during startup below. There's a benign message about not finding a Vera device just before the reboot but that's it.Needless to say, I've learned my lesson regarding OS upgrades.
Bare metal Linux / Ubuntu 20.04 (Running inside VirtualBox)
Reactor Version: stable-22337-1a0a685fDec 30 19:33:46 homeauto03 systemd[1]: Started Multi System Reactor. Dec 30 19:33:46 homeauto03 weewx[6592] INFO weewx.restx: Wunderground-RF: Published record 2022-12-30 19:33:46 EST (1672446826) Dec 30 19:33:46 homeauto03 node[7240]: Reactor stable-22337-1a0a685f app 22328 configuration from /home/tbully/reactor/config Dec 30 19:33:46 homeauto03 node[7240]: NODE_PATH /home/tbully/reactor Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.745Z <app:null> Reactor build stable-22337-1a0a685f starting on v17.9.0 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.746Z <app:null> Process ID 7240 user/group 1000/1000; bare-metal; platform linux/x64 #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022; locale en_CA.UTF-8 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.746Z <app:null> Basedir /home/tbully/reactor; data in /home/tbully/reactor/storage Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.747Z <app:null> NODE_PATH=/home/tbully/reactor Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.764Z <Structure:null> Module Structure v22323 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.765Z <Capabilities:null> Module Capabilities v22283 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.819Z <Plugin:null> Module Plugin v22300 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.827Z <TimerBroker:null> Module TimerBroker v22283 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.831Z <Entity:null> Module Entity v22314 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.835Z <Controller:null> Module Controller v22323 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.847Z <default:null> Module Ruleset v22293 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.848Z <default:null> Module Rulesets v21096 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.854Z <GlobalExpression:null> Module GlobalExpression v21333 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.864Z <Predicate:null> Module Predicate v22305 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.867Z <AlertManager:null> Module AlertManager v22283 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.869Z <Rule:null> Module Rule v22335 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.872Z <GlobalReaction:null> Module GlobalReaction v22320 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.873Z <Engine:null> Module Engine v22320 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.877Z <httpapi:null> Module httpapi v22337 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.886Z <wsapi:null> Module wsapi v22320 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.949Z <TaskQueue:null> Module TaskQueue 21351 Dec 30 19:33:46 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:46.950Z <VeraController:null> Module VeraController v22325 Dec 30 19:33:47 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:47.200Z <HassController:null> Module HassController v22334 Dec 30 19:33:48 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:48.294Z <SystemController:null> Module SystemController v22306 Dec 30 19:33:48 homeauto03 weewx[6592] INFO weewx.restx: Wunderground-RF: Published record 2022-12-30 19:33:48 EST (1672446828) Dec 30 19:33:49 homeauto03 node[7240]: [stable-22337]2022-12-31T00:33:49.110Z <Rule:CRIT> ReferenceError: Can't find entity "vera>device_368" [-] Dec 30 19:33:49 homeauto03 node[7240]: ReferenceError: Can't find entity "vera>device_368" Dec 30 19:33:49 homeauto03 node[7240]: at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:366:27) Dec 30 19:33:49 homeauto03 node[7240]: at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106) Dec 30 19:33:49 homeauto03 node[7240]: at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47) Dec 30 19:33:49 homeauto03 node[7240]: at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37) Dec 30 19:33:49 homeauto03 node[7240]: at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54) Dec 30 19:33:49 homeauto03 node[7240]: at async /home/tbully/reactor/server/lib/Rule.js:830:17 Dec 30 19:33:49 homeauto03 systemd[1]: Stopping Session 14 of User tbully...
-
I have the logs but can't find a way to upload them. I don't have permissions to upload a file and if I paste it in here it says the post is too large.
Here's a few pieces:
[stable-22337]2022-12-31T00:33:46.745Z <app:null> Reactor build stable-22337-1a0a685f starting on v17.9.0 [stable-22337]2022-12-31T00:33:46.746Z <app:null> Process ID 7240 user/group 1000/1000; bare-metal; platform linux/x64 #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022; locale en_CA.UTF-8 [stable-22337]2022-12-31T00:33:46.746Z <app:null> Basedir /home/tbully/reactor; data in /home/tbully/reactor/storage [stable-22337]2022-12-31T00:33:46.747Z <app:null> NODE_PATH=/home/tbully/reactor [stable-22337]2022-12-31T00:33:46.750Z <app:INFO> Configured locale (undefined); selected locale(s) en_CA.UTF-8 [stable-22337]2022-12-31T00:33:46.761Z <app:INFO> Loaded locale en-US [stable-22337]2022-12-31T00:33:46.764Z <Structure:null> Module Structure v22323 [stable-22337]2022-12-31T00:33:46.765Z <Capabilities:null> Module Capabilities v22283 [stable-22337]2022-12-31T00:33:46.819Z <Plugin:null> Module Plugin v22300 [stable-22337]2022-12-31T00:33:46.827Z <TimerBroker:null> Module TimerBroker v22283 [stable-22337]2022-12-31T00:33:46.831Z <Entity:null> Module Entity v22314 [stable-22337]2022-12-31T00:33:46.835Z <Controller:null> Module Controller v22323 [stable-22337]2022-12-31T00:33:46.847Z <default:null> Module Ruleset v22293 [stable-22337]2022-12-31T00:33:46.848Z <default:null> Module Rulesets v21096 [stable-22337]2022-12-31T00:33:46.854Z <GlobalExpression:null> Module GlobalExpression v21333 [stable-22337]2022-12-31T00:33:46.864Z <Predicate:null> Module Predicate v22305 [stable-22337]2022-12-31T00:33:46.867Z <AlertManager:null> Module AlertManager v22283 [stable-22337]2022-12-31T00:33:46.869Z <Rule:null> Module Rule v22335 [stable-22337]2022-12-31T00:33:46.872Z <GlobalReaction:null> Module GlobalReaction v22320 [stable-22337]2022-12-31T00:33:46.873Z <Engine:null> Module Engine v22320 [stable-22337]2022-12-31T00:33:46.877Z <httpapi:null> Module httpapi v22337 [stable-22337]2022-12-31T00:33:46.886Z <wsapi:null> Module wsapi v22320 [stable-22337]2022-12-31T00:33:46.887Z <app:NOTICE> Starting Structure... [stable-22337]2022-12-31T00:33:46.890Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping [stable-22337]2022-12-31T00:33:46.892Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController) [stable-22337]2022-12-31T00:33:46.949Z <TaskQueue:null> Module TaskQueue 21351 [stable-22337]2022-12-31T00:33:46.950Z <VeraController:null> Module VeraController v22325 [stable-22337]2022-12-31T00:33:47.193Z <Structure:INFO> Structure#1 loading controller interface hass (HassController) [stable-22337]2022-12-31T00:33:47.200Z <HassController:null> Module HassController v22334 [stable-22337]2022-12-31T00:33:48.290Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [stable-22337]2022-12-31T00:33:48.294Z <SystemController:null> Module SystemController v22306 [stable-22337]2022-12-31T00:33:48.297Z <Structure:INFO> Starting controller VeraController#vera [stable-22337]2022-12-31T00:33:48.298Z <VeraController:NOTICE> VeraController#vera starting... [stable-22337]2022-12-31T00:33:48.304Z <Controller:INFO> VeraController#vera loaded vera capabilities ver 22253 rev 1 format 1 [stable-22337]2022-12-31T00:33:48.341Z <Controller:INFO> VeraController#vera loaded implementation data ver 22280 rev 8 format 1 [stable-22337]2022-12-31T00:33:48.341Z <Structure:INFO> Starting controller HassController#hass [stable-22337]2022-12-31T00:33:48.341Z <HassController:NOTICE> HassController#hass starting... [stable-22337]2022-12-31T00:33:48.343Z <Controller:INFO> HassController#hass loaded hass capabilities ver 22312 rev 2 format 1 [stable-22337]2022-12-31T00:33:48.354Z <Controller:INFO> HassController#hass loaded implementation data ver 22335 rev 1 format 1 [stable-22337]2022-12-31T00:33:48.354Z <Structure:INFO> Starting controller SystemController#reactor_system [stable-22337]2022-12-31T00:33:48.359Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. [stable-22337]2022-12-31T00:33:48.518Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members [stable-22337]2022-12-31T00:33:48.518Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty [stable-22337]2022-12-31T00:33:48.519Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [stable-22337]2022-12-31T00:33:48.520Z <VeraController:NOTICE> VeraController#vera updating capabilities for system entity System#vera>system [stable-22337]2022-12-31T00:33:48.525Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.34.17:8123/api/websocket [stable-22337]2022-12-31T00:33:48.529Z <app:NOTICE> Starting HTTP server and API... [stable-22337]2022-12-31T00:33:48.530Z <httpapi:NOTICE> Starting HTTP API v1 22337 on http://192.168.34.:8111 [stable-22337]2022-12-31T00:33:48.533Z <app:NOTICE> Starting Reaction Engine... [stable-22337]2022-12-31T00:33:48.534Z <Engine:INFO> Reaction Engine starting [stable-22337]2022-12-31T00:33:48.534Z <Engine:INFO> Checking rule sets... [stable-22337]2022-12-31T00:33:48.539Z <Engine:INFO> Checking rules...```
[stable-22337]2022-12-31T00:33:49.745Z Rule:INFO Master Closet Motion Battery Low (rule-grp17k28ehz in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.761Z Rule:ERR Rule#rule-grp17k28qlp trigger evaluation failed: [ReferenceError] Can't find entity "vera>device_368" [-]
[stable-22337]2022-12-31T00:33:49.762Z Rule:CRIT ReferenceError: Can't find entity "vera>device_368" [-]
ReferenceError: Can't find entity "vera>device_368"
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:366:27)
at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106)
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47)
at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37)
at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54)
at async /home/tbully/reactor/server/lib/Rule.js:830:17
[stable-22337]2022-12-31T00:33:49.762Z Rule:INFO Panic Button Battery Low (rule-grp17k28qlp in Battery Checks) evaluated; trigger state changed ((null)), but rule state remains NULL
[stable-22337]2022-12-31T00:33:49.762Z Rule:INFO Panic Button Battery Low (rule-grp17k28qlp in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Office Motion Battery Low (rule-grp17k28znh in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Office Motion Battery Low (rule-grp17k28znh in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Door Battery Low (rule-grp17k29vsx in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Door Battery Low (rule-grp17k29vsx in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Motion Battery Low (rule-grp17k2abok in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Motion Battery Low (rule-grp17k2abok in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.763Z Rule:INFO Upstairs Bath Flood Battery Low (rule-grp17k2am7t in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.764Z Rule:INFO Upstairs Bath Flood Battery Low (rule-grp17k2am7t in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.764Z Rule:INFO Upstairs Hall Motion Battery Low (rule-grp17k2b0ha in Battery Checks) evaluated; trigger state unchanged (true); rule state remains SET
[stable-22337]2022-12-31T00:33:49.764Z Rule:INFO Upstairs Hall Motion Battery Low (rule-grp17k2b0ha in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.773Z Rule:ERR Rule#rule-grp17k2iotv trigger evaluation failed: [ReferenceError] Can't find entity "vera>device_543" [-]
[stable-22337]2022-12-31T00:33:49.773Z Rule:CRIT ReferenceError: Can't find entity "vera>device_543" [-]
ReferenceError: Can't find entity "vera>device_543"
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:366:27)
at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106)
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47)
at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37)
at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54)
at async /home/tbully/reactor/server/lib/Rule.js:830:17
[stable-22337]2022-12-31T00:33:49.773Z Rule:INFO Home Button Battery Low (rule-grp17k2iotv in Battery Checks) evaluated; trigger state changed ((null)), but rule state remains NULL
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Home Button Battery Low (rule-grp17k2iotv in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Sump Pump Flood Detected (rule-grp17k301y1 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Sump Pump Flood Detected (rule-grp17k301y1 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Rec Room Flood Detected (rule-grp17k30cm0 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.774Z Rule:INFO Rec Room Flood Detected (rule-grp17k30cm0 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Office Flood Detected (rule-grp17k30mqa in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Office Flood Detected (rule-grp17k30mqa in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Laundry Flood Detected (rule-grp17k31kf1 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Laundry Flood Detected (rule-grp17k31kf1 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Half-Bath Flood Detected (rule-grp17k31z13 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Half-Bath Flood Detected (rule-grp17k31z13 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.775Z Rule:INFO Upstairs Bath Flood Detected (rule-grp17k327c0 in Flood Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.776Z Rule:INFO Upstairs Bath Flood Detected (rule-grp17k327c0 in Flood Checks) started
[stable-22337]2022-12-31T00:33:49.776Z Rule:INFO Garage Tilt Sensor Battery Low (rule-grp17k3frdb in Battery Checks) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.776Z Rule:INFO Garage Tilt Sensor Battery Low (rule-grp17k3frdb in Battery Checks) started
[stable-22337]2022-12-31T00:33:49.782Z Rule:ERR Rule#rule-grp17k3ui8q trigger evaluation failed: [ReferenceError] Entity Vera (vera>system) has no attribute "x_vera_sys.reloads" [-]
[stable-22337]2022-12-31T00:33:49.782Z Rule:CRIT ReferenceError: Entity Vera (vera>system) has no attribute "x_vera_sys.reloads" [-]
ReferenceError: Entity Vera (vera>system) has no attribute "x_vera_sys.reloads"
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:373:27)
at Predicate._evaluateGroup (/home/tbully/reactor/server/lib/Predicate.js:748:106)
at Predicate._evaluateCondition (/home/tbully/reactor/server/lib/Predicate.js:354:47)
at Predicate.evaluate (/home/tbully/reactor/server/lib/Predicate.js:60:37)
at Rule._evaluate (/home/tbully/reactor/server/lib/Rule.js:875:54)
at async /home/tbully/reactor/server/lib/Rule.js:830:17
[stable-22337]2022-12-31T00:33:49.782Z Rule:INFO LuupReload (rule-grp17k3ui8q in House Reactor) evaluated; trigger state changed ((null)), but rule state remains NULL
[stable-22337]2022-12-31T00:33:49.783Z Rule:INFO LuupReload (rule-grp17k3ui8q in House Reactor) started
[stable-22337]2022-12-31T00:33:49.783Z Rule:INFO VeraSecureTriggered (rule-grplg89w7x in House Reactor) evaluated; trigger state unchanged (false); rule state remains RESET
[stable-22337]2022-12-31T00:33:49.783Z Rule:INFO VeraSecureTriggered (rule-grplg89w7x in House Reactor) started
[stable-22337]2022-12-31T00:33:49.783Z Rule:INFO TurnOffPantryLights (rule-grplt8fpma in Basement Reactor) evaluated; trigger state unchanged (false); rule state remains RESET[stable-22337]2022-12-31T00:33:49.902Z <Rule:INFO> Garage Lights Off - After Auto On (rule-grpp2yoxfg in Garage Reactor) evaluated; trigger state unchanged (false); rule state remains RESET [stable-22337]2022-12-31T00:33:49.902Z <Rule:INFO> Garage Reactor (rule-492 in Garage Reactor) evaluation complete [stable-22337]2022-12-31T00:33:49.902Z <Rule:INFO> Garage Lights Off - After Auto On (rule-grpp2yoxfg in Garage Reactor) evaluation complete [stable-22337]2022-12-31T00:33:49.907Z <httpapi:NOTICE> httpapi: listening [stable-22337]2022-12-31T00:33:49.921Z <app:NOTICE> Starting WSAPI... [stable-22337]2022-12-31T00:33:49.922Z <wsapi:NOTICE> wsapi: starting version 22320 [stable-22337]2022-12-31T00:33:50.112Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "12/30/2022, 7:33:50 PM" (TZ offset -300 mins from UTC) [stable-22337]2022-12-31T00:33:50.120Z <app:NOTICE> Shutdown signal (SIGTERM) received. Stopping Reaction Engine... [stable-22337]2022-12-31T00:33:50.121Z <app:NOTICE> Closing APIs... [stable-22337]2022-12-31T00:33:50.121Z <wsapi:NOTICE> wsapi: closing... [stable-22337]2022-12-31T00:33:50.121Z <httpapi:NOTICE> HTTP API closing... [stable-22337]2022-12-31T00:33:50.121Z <app:NOTICE> Stopping Engine... [stable-22337]2022-12-31T00:33:50.128Z <Rule:NOTICE> Turn Off Upstairs Hall Light (rule-grprsxsoqm in UpstairsHall Reactor) stopping [stable-22337]2022-12-31T00:33:50.129Z <Rule:NOTICE> Run Hot Water Recirculation (rule-l7ey8s4w in House Reactor) stopping [stable-22337]2022-12-31T00:33:50.130Z <Rule:NOTICE> Run Fans (rule-l6pi77c2 in House Reactor) stopping [stable-22337]2022-12-31T00:33:50.130Z <Rule:NOTICE> VeraSecureTriggered (rule-grplg89w7x in House Reactor) stopping
[stable-22337]2022-12-31T00:33:50.329Z <Rule:NOTICE> Half-Bath Flood Detected (rule-grp17k31z13 in Flood Checks) stopped [stable-22337]2022-12-31T00:33:50.330Z <Rule:NOTICE> Upstairs Bath Flood Detected (rule-grp17k327c0 in Flood Checks) stopped [stable-22337]2022-12-31T00:33:50.417Z <Engine:NOTICE> [Engine]Engine#1 has shut down. [stable-22337]2022-12-31T00:33:50.417Z <app:NOTICE> Closing Structure... [stable-22337]2022-12-31T00:33:50.418Z <Structure:INFO> Structure#1 Stopping controllers... [stable-22337]2022-12-31T00:33:50.418Z <Controller:NOTICE> VeraController#vera stopping [stable-22337]2022-12-31T00:33:50.524Z <HassController:NOTICE> HassController#hass stopping [stable-22337]2022-12-31T00:33:50.526Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error] WebSocket was closed before the connection was established [-] [stable-22337]2022-12-31T00:33:50.526Z <HassController:WARN> HassController#hass ws error code (undefined) [stable-22337]2022-12-31T00:33:50.526Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error] WebSocket was closed before the connection was established [-] [stable-22337]2022-12-31T00:33:50.527Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.34.17:8123/api/websocket closed during open/negotiation [stable-22337]2022-12-31T00:33:50.527Z <Controller:NOTICE> HassController#hass stopping [stable-22337]2022-12-31T00:33:50.803Z <Controller:NOTICE> SystemController#reactor_system stopping [stable-22337]2022-12-31T00:33:50.811Z <Controller:ERR> Controller SystemController#reactor_system is off-line! [stable-22337]2022-12-31T00:33:50.814Z <Structure:INFO> Structure#1 Final data sync... [stable-22337]2022-12-31T00:33:50.838Z <Structure:NOTICE> Structure Structure#1 stopped [stable-22337]2022-12-31T00:33:50.839Z <app:NOTICE> Stopping timers... [stable-22337]2022-12-31T00:33:50.840Z <app:NOTICE> Shutdown complete, process ID 7240
-
Sorry for talking to myself. Just trying to relay what I know.
I tried running it manually and got the following:
tbully@homeauto03:~/reactor$ npm run deps npm ERR! Missing script: "deps" npm ERR! npm ERR! To see a list of scripts, run: npm ERR! npm run npm ERR! A complete log of this run can be found in: npm ERR! /home/tbully/.npm/_logs/2022-12-31T01_15_30_113Z-debug-0.log tbully@homeauto03:~/reactor$ NODE_PATH=$(pwd) node app.js Reactor stable-22337-1a0a685f app 22328 configuration from /home/tbully/reactor/config NODE_PATH /home/tbully/reactor [stable-22337]2022-12-31T01:15:55.631Z <app:null> Reactor build stable-22337-1a0a685f starting on v17.9.0 [stable-22337]2022-12-31T01:15:55.632Z <app:null> Process ID 2239 user/group 1000/1000; bare-metal; platform linux/x64 #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022; locale en_CA.UTF-8 [stable-22337]2022-12-31T01:15:55.633Z <app:null> Basedir /home/tbully/reactor; data in /home/tbully/reactor/storage [stable-22337]2022-12-31T01:15:55.633Z <app:null> NODE_PATH=/home/tbully/reactor [stable-22337]2022-12-31T01:15:55.651Z <Structure:null> Module Structure v22323 [stable-22337]2022-12-31T01:15:55.652Z <Capabilities:null> Module Capabilities v22283 [stable-22337]2022-12-31T01:15:55.709Z <Plugin:null> Module Plugin v22300 [stable-22337]2022-12-31T01:15:55.716Z <TimerBroker:null> Module TimerBroker v22283 [stable-22337]2022-12-31T01:15:55.720Z <Entity:null> Module Entity v22314 [stable-22337]2022-12-31T01:15:55.724Z <Controller:null> Module Controller v22323 [stable-22337]2022-12-31T01:15:55.734Z <default:null> Module Ruleset v22293 [stable-22337]2022-12-31T01:15:55.735Z <default:null> Module Rulesets v21096 [stable-22337]2022-12-31T01:15:55.743Z <GlobalExpression:null> Module GlobalExpression v21333 [stable-22337]2022-12-31T01:15:55.753Z <Predicate:null> Module Predicate v22305 [stable-22337]2022-12-31T01:15:55.757Z <AlertManager:null> Module AlertManager v22283 [stable-22337]2022-12-31T01:15:55.759Z <Rule:null> Module Rule v22335 [stable-22337]2022-12-31T01:15:55.763Z <GlobalReaction:null> Module GlobalReaction v22320 [stable-22337]2022-12-31T01:15:55.765Z <Engine:null> Module Engine v22320 [stable-22337]2022-12-31T01:15:55.769Z <httpapi:null> Module httpapi v22337 [stable-22337]2022-12-31T01:15:55.783Z <wsapi:null> Module wsapi v22320 [stable-22337]2022-12-31T01:15:55.845Z <TaskQueue:null> Module TaskQueue 21351 [stable-22337]2022-12-31T01:15:55.846Z <VeraController:null> Module VeraController v22325 [stable-22337]2022-12-31T01:15:56.133Z <HassController:null> Module HassController v22334 [stable-22337]2022-12-31T01:15:57.494Z <SystemController:null> Module SystemController v22306
-
I could delete these posts but I won't. In short, I'm an idiot.
I remembered I have a rule which reboots my Linux host when my weather station goes in to error. Reactor lives on that host. (sigh)
My fix was to temporarily rename the "reboot" command in the filesystem to something else. Start Reactor (imagine that, no reboot!). Disable the rule. Fix the command back to "reboot" in the FS.
Happy New Year! (ugh)
-
These things happen. It's easy to forget stuff like this sometimes. A couple of suggestions:
- Send yourself a notification before you reboot the entire system (with the reason for doing it). Alert, email, cloud service... doesn't matter... just leave yourself a trail of crumbs to follow. It's a good idea to do this before any kind of automatically-triggered aggression against a process or system.
- Delay the reboot command by a minute or two in the reaction after that notification. That will give you time to (a) notice the notification and (b) cancel the reaction in the Running Reactions Status panel. You can then go and fix the rule or whatever is triggering it.
Is there a reason you went to 20.04 instead of 22.04 LTS? The latter will have support through April 2027. If you want to take that step, you can just use
do-release-upgrade
from 20.04. -
Been there, done that. I agree with @toggledbits about alerts. I prefer more alerts (I could always ignore them) than black magic routines.
-
In my exhaustion (anger? Lol), I mistyped. I’m at 22.04.
I do fire an email just before the reboot. I took a break to check emails and wrap up for the day and this is what triggered it for me. If it wasn’t for this, I think I’d still be digging. I send lots of emails, perhaps too many, when different things happen. This is a great idea!
I have to go look at the rule today. I thought I set a variable on reboot which would only allow one event/reboot. At least I thought about this possibility but I clearly missed something.
Thanks for the consoling, gents. I’ve appreciated both of your support over the past year as I’ve slowly moved away from Vera to HASS with Reactor being the central rules engine.
-
T toggledbits locked this topic on