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.
Can't Restart Reactor - Corrupted SD Card?
-
Hey Patrick, I recently have been noticing that MSR has been acting up ie. it's been needing restarts and has been slow. I began trouble shooting by looking at the logs and have noticed the following errors for a lot of entities. I thought maybe a simple reboot of RPi was needed and I kept seeing the same errors in the system logs. I am oddly enough not seeing these same errors in the MSR logs.
Where things started getting weird is whenever I rebooted MSR it wouldn't come back online .I would have to restart the RPi then it would come back online.I just restarted MSR again to capture logs and it restarted fine, so I guess its good for now? I think this is more or so a corrupted SD card issue rather a MSR issue but well being troubleshooting from here. The SD card is about 1-2 years old.Apologies if this post is everywhere, I cannot consistently recreate any oddities that are happening, that's what is leading me to believe my SD is going bad.
PS: If anyone knows how to diagnose a corrupt SD card please chime in.
MSR latest-24057-e9add9f5
Home Assistant 2024.4.3
Raspberry Pi 3b+2024-04-15T18:06:22.077587-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.077788-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.077950-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.078100-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.078258-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.078416-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.078580-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.078727-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.078865-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.079010-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.079158-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.080399-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.080Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.080755-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.080962-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.081128-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.081279-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.081432-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.081589-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.081743-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.081934-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.082077-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.082219-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.082398-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.083768-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.083Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.084179-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.084393-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.084559-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.084710-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.084863-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.085020-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.085177-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.085328-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.085466-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.085607-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.085756-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.086975-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.086Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.087274-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.087460-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.087619-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.087767-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.087920-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.088080-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.088239-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.088387-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.088525-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.088668-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.088855-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.090050-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.089Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.090402-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.090604-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.090766-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.090917-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.091072-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.091229-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.091386-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.091538-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.091676-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.091821-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.091970-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.093138-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.092Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.093521-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.093795-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.093976-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.094130-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.094290-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.094448-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.094607-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.094757-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.094896-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.095038-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.095184-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.096390-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.096Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.096721-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.096926-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.097092-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.097261-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.097435-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.097593-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.097749-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.097895-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.098034-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.098177-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.098321-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.099477-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.099Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.099986-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.100210-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.100376-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.100536-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.100693-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.100847-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.100993-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.101134-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.101280-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.101426-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.101576-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.102597-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.102Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.102928-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.103196-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.103423-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.103636-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.103826-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.103990-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.104146-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.104293-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.104433-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.104575-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.104719-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.105897-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.105Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.106218-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.106419-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.106578-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.106729-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.106884-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.107041-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.107200-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.107353-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.107537-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.107688-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.107835-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.108945-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.108Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.109303-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.109504-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.109668-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.109882-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.110050-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.110214-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.110369-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.110513-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.110651-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.110794-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.110940-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.112050-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.111Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.112332-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.112525-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.112684-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.112838-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.113024-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.113262-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.113461-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.113657-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.113803-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.113954-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.114102-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.115323-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.114Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.115652-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.115852-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.116013-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.116165-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.116320-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.116476-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.116631-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.116777-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.116914-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.117058-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.117204-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.118359-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.118Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.118646-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.118838-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.118999-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.119157-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.119317-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.119477-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.119636-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.119954-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.120116-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.120268-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.120421-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.121491-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.121Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.121775-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.121967-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.122128-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.122277-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.122430-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.122584-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.122741-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.122891-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.123045-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.123226-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.123407-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.124708-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.124Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.125034-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.125234-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.125400-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.125550-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.125700-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.125853-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.126009-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.126159-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.126300-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.126439-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.126583-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.127825-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.127Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.128177-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.128381-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.128544-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.128696-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.128852-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.129016-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.129181-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.129380-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.129547-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.129752-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.129934-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.218665-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.218Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.219103-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.219321-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.219495-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.219664-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.219884-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.220048-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.220194-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.220340-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.220483-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.220632-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.220785-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T18:06:22.221868-07:00 raspberrypi node[3744]: [latest-24057]2024-04-16T01:06:22.221Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T18:06:22.222302-07:00 raspberrypi node[3744]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T18:06:22.222522-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T18:06:22.222685-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.222845-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T18:06:22.223040-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.223275-07:00 raspberrypi node[3744]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T18:06:22.223481-07:00 raspberrypi node[3744]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T18:06:22.223682-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T18:06:22.223852-07:00 raspberrypi node[3744]: at Array.forEach (<anonymous>) 2024-04-15T18:06:22.224014-07:00 raspberrypi node[3744]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T18:06:22.224163-07:00 raspberrypi node[3744]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
-
P Pabla deleted this topic on
-
P Pabla restored this topic on
-
This may be another change in Hass 2024.4, which is not yet officially supported. Can you check your
hass_services.json
log file and see if you find this:"selector": { "number": null <--- search for this }
If you find an example of these three lines together, capture that file. I'm going to ask you to send it to me.
Also, can you post just ONE of the messages above, with the 20 lines or so before that I always ask for. I'd rather see one copy with context than 20 copies of the same thing without it.
-
@toggledbits said in Can't Restart Reactor - Corrupted SD Card?:
This may be another change in Hass 2024.4, which is not yet officially supported. Can you check your
hass_services.json
log file and see if you find this:"selector": { "number": null <--- search for this }
Searched and nothing came up in the
hass_services.json
If you find an example of these three lines together, capture that file. I'm going to ask you to send it to me.
Also, can you post just ONE of the messages above, with the 20 lines or so before that I always ask for. I'd rather see one copy with context than 20 copies of the same thing without it.
2024-04-15T14:12:03.340678-07:00 raspberrypi node[531]: [latest-24057]2024-04-15T21:12:03.339Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T14:12:03.341046-07:00 raspberrypi node[531]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T14:12:03.341211-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T14:12:03.341362-07:00 raspberrypi node[531]: at Array.forEach (<anonymous>) 2024-04-15T14:12:03.341511-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T14:12:03.341659-07:00 raspberrypi node[531]: at Array.forEach (<anonymous>) 2024-04-15T14:12:03.341809-07:00 raspberrypi node[531]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T14:12:03.341961-07:00 raspberrypi node[531]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T14:12:03.342110-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T14:12:03.342258-07:00 raspberrypi node[531]: at Array.forEach (<anonymous>) 2024-04-15T14:12:03.342407-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T14:12:03.342557-07:00 raspberrypi node[531]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T14:12:03.351442-07:00 raspberrypi node[531]: [latest-24057]2024-04-15T21:12:03.350Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T14:12:03.351839-07:00 raspberrypi node[531]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T14:12:03.352002-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T14:12:03.352151-07:00 raspberrypi node[531]: at Array.forEach (<anonymous>) 2024-04-15T14:12:03.352302-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T14:12:03.352450-07:00 raspberrypi node[531]: at Array.forEach (<anonymous>) 2024-04-15T14:12:03.352601-07:00 raspberrypi node[531]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T14:12:03.352757-07:00 raspberrypi node[531]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T14:12:03.352907-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T14:12:03.353055-07:00 raspberrypi node[531]: at Array.forEach (<anonymous>) 2024-04-15T14:12:03.353204-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T14:12:03.353354-07:00 raspberrypi node[531]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T14:12:03.361968-07:00 raspberrypi node[531]: [latest-24057]2024-04-15T21:12:03.361Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T14:12:03.362323-07:00 raspberrypi node[531]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T14:12:03.362482-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T14:12:03.362631-07:00 raspberrypi node[531]: at Array.forEach (<anonymous>) 2024-04-15T14:12:03.362780-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T14:12:03.362930-07:00 raspberrypi node[531]: at Array.forEach (<anonymous>) 2024-04-15T14:12:03.363079-07:00 raspberrypi node[531]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T14:12:03.363230-07:00 raspberrypi node[531]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T14:12:03.363379-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T14:12:03.363526-07:00 raspberrypi node[531]: at Array.forEach (<anonymous>) 2024-04-15T14:12:03.363674-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T14:12:03.363823-07:00 raspberrypi node[531]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-04-15T14:12:03.371382-07:00 raspberrypi node[531]: [latest-24057]2024-04-15T21:12:03.370Z <HassController:CRIT> TypeError: Cannot read properties of null (reading 'min') [-] 2024-04-15T14:12:03.371778-07:00 raspberrypi node[531]: TypeError: Cannot read properties of null (reading 'min') 2024-04-15T14:12:03.371938-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1067:207 2024-04-15T14:12:03.372087-07:00 raspberrypi node[531]: at Array.forEach (<anonymous>) 2024-04-15T14:12:03.372236-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1044:279 2024-04-15T14:12:03.372383-07:00 raspberrypi node[531]: at Array.forEach (<anonymous>) 2024-04-15T14:12:03.372532-07:00 raspberrypi node[531]: at HassController._register_service (/home/arman/Documents/reactor/server/lib/HassController.js:1037:60) 2024-04-15T14:12:03.372683-07:00 raspberrypi node[531]: at HassController._update_entity (/home/arman/Documents/reactor/server/lib/HassController.js:873:43) 2024-04-15T14:12:03.372834-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1196:67 2024-04-15T14:12:03.372982-07:00 raspberrypi node[531]: at Array.forEach (<anonymous>) 2024-04-15T14:12:03.373131-07:00 raspberrypi node[531]: at /home/arman/Documents/reactor/server/lib/HassController.js:1191:247 2024-04-15T14:12:03.373281-07:00 raspberrypi node[531]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
-
@Pabla said in Can't Restart Reactor - Corrupted SD Card?:
Searched and nothing came up in the hass_services.json
OK, not finding the search string and the sequence and type of messages suggests to me that (a) it's not a Hass change at fault, and (b) there's corruption, may or may not be SD, could be RAM. That message should be accompanied by another, and not logged the way you Pi is logging it. I can prove that on my own systems. If you can't find that null in the data, it also suggests that the place that's throwing the error should not be throwing an error, because the error can only occur if that data is null. Lots to unpack.
Odd, random problems with Pi's can indeed be caused by SD failure, but the fact that it appears we have an in-memory data corruption suggests RAM. Other culprits in RPi slowdowns are overheating (you may need a heat sink, at least, on your CPU, and possibly a fan; if you're overclocking it, don't), but perhaps more commonly, a failing power supply. If the PS can't deliver stable voltage at the current the Pi demands, it will slow the clock for sure, but all kinds of other strange things can happen as well. It can be very quiet and subtle, and random with increasing frequency at the start. Voltage warnings show in the desktop UI but can be very hard to detect/confirm if you don't have that open all the time to see it. If you're using a "wall wart" power supply, swap it out for something newer/better and see if the system improves. Make sure it's rated for the Pi's full power (3B+ is 5V/2.5A so a 15W or higher PS is recommended). If you're using a USB cable connection for power, also change out the cable; make sure the new one is rated for the power.
If you log in to your Pi, you should be able to run
sudo vcgencmd get_throttled
. If there has been any power or heat event since the Pi last rebooted, there will be a non-zero value reported.Generally speaking, the 3B+ isn't the best choice these days. While I have tested Reactor on a 3B+ and it runs, it's under-powered and light on RAM, so if you're trying to run much else with it (Mosquitto, ZWaveJS, etc), you're asking for trouble. It's also holding you back on an aging OS. The fact that you're still running on an SD card is playing with fire; there are only two kinds of MicroSD cards: those that have failed, and those that are about to. Even if a PS swap fixes your issue, I'd make a plan to replace/upgrade that unit some day soon to a modern Pi, or one of the alternative units. I'm still a big fan of the Raspberri Pi Compute Module 4 with eMMC (like on-board SSD but better) mounted on the RPi CM4 I/O Board; I even made a 3D-printable case for it. It's one of the easiest ways to get to a non-MicroSD Pi configuration. You could also go to Pi 5 with an M.2 HAT and M.2 SSD. But in any case, I'd start planning an upgrade for the long-term.
-
The response i got
throttled=0x80000
means soft temp throttle. I did notice that the unit was running really hot recently too.Either way I know I was playing with fire with running a 3+ with a SD card. Thankfully I do backup the Reactor directory every day so if I did lose the Pi it wouldn't be catastrophic.
I do however have an Odroid N2+ handy which will be more than enough to run MSR and anything else with a lot of power to spare. I will likely run it with a SSD though since that currently uses a SD card as well. It does however have 64gb of Emmc storage, not sure if that is is suitable for MSR.