• Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
MSR UI on a mobile browser
tunnusT

I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.

Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.

( *Drag & drop of rule conditions have never worked on a mobile)

Multi-System Reactor
[Reactor] Assignment to alarm ignored -- expression-driven global cannot be set by assignment
therealdbT

Hi @toggledbits,

I have lots of logs with this:

<Engine:ERR> Assignment to alarm ignored -- expression-driven global cannot be set by assignment

Any hints to where look at to avoid this? Thanks.

Multi-System Reactor
[Reactor] [Dev] Clarifications/Docs for refreshCapabilities and Entity action implementations return types
therealdbT

Hi @toggledbits

I'd like to update my controllers with these new features, but I'm struggling to find any guidance in the docs - and in general to understand the context.

Could you please elaborate more? Thanks.

Multi-System Reactor
Access to log file viewer denied
tunnusT

I have the following ACL defined:

groups: admin: users: - admin applications: true api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true

And I have authenticated to MSR as "admin" user. However, I'm getting "access denied" when trying to access http://*******:8111/api/v1/log

So what I'm missing, is my ACL incorrectly defined?

Using build 24302 on Docker.

Multi-System Reactor
Darker Reactor style
therealdbT

Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.

Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce

A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.

Multi-System Reactor
TTS in MSR?
F

Hi!

In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
Thanks!
/Fanan

Multi-System Reactor
Should MSR import this device type from an Ezlo controller?
cw-kidC

Hi

I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.

They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.

This is how that device looks in the Ezlo API.

Devices Info:

_id: "10696001" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "level_sensor" subcategory: "" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Digital" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"

Items Info:

_id: "20696001" deviceId: "10696001" hasGetter: true hasSetter: false name: "smoke_density" show: true valueType: "substance_amount" scale: "parts_per_million" value: 2.7472610473632812 valueFormatted: "2.75" status: "idle"

There is also an Analog Gas sensor that one did import in to MSR OK.

68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png

Devices Info:

_id: "10696000" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "security_sensor" subcategory: "gas" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Analog" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"

Items Info:

_id: "20696000" deviceId: "10696000" hasGetter: true hasSetter: false name: "gas_alarm" show: true valueType: "token" enum: 0: "no_gas" 1: "combustible_gas_detected" 2: "toxic_gas_detected" 3: "unknown" valueFormatted: "no_gas" value: "no_gas" status: "idle"

And this is how this MQ2 Gas Sensor looks like on their dashboard:

Digital
cb77dfa3-4af5-4d06-9635-89207a716a89-image.png

Analog
4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png

They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!

And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.

THANKS.

Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT

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.
Multi-System Reactor
A couple of things about Reactor 24293
therealdbT

A couple of things for you @toggledbits, since you mentioned that this release has new features and some tweaks are expected.

Local expressions cannot be deleted. Pushing the X button has no effect for me.

When cloning an entity action, the result is strange (first is cloned one, second is the original action):
a92ea094-9e2c-4aaa-bf47-2d07a6ffdbd0-image.png

When changing the action on the cloned element, the params are added to the original one. See screenshot:
92ac3011-83c8-466b-bd23-47d483ad7a52-image.png

Dark theme has a couple of strange contrasts. One is visible in the previous screenshots (white text on yellow background). Another one is in groups (blue text on blue background):
9b3c4988-53ef-44e6-9672-30e744cacb75-image.png Overall, I found blue, yellow, red and green (in buttons and forms) to be too bright.

On the bright side:

I love the new script action: thank you! The dark theme is a great start to avoid getting blinded at night I promise I'll try very soon the new features around actions. Thanks!
Multi-System Reactor
Error on start for MSR after update to 24293
T

@toggledbits
I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:

TypeError: Cannot read properties of undefined (reading 'value') at Rulesets.getRulesets (https://*************************/client/Rulesets.js:111:38) at async StatusTab.updateSetRules (https://*************************/reactor/en-US/lib/js/reactor-ui-status.js:276:28) at async StatusTab.drawSetRules (https://*************************/reactor/en-US/lib/js/reactor-ui-status.js:270:13) You may report this error, but do not screen shot it. Copy-paste the text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.

I followed the new directions about npm

npm i --no-save --no-package-lock --omit dev

Any idea what the issue is?

Multi-System Reactor
Dark Mode not Working - 24293
PablaP

Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)

Things I have tried:

Hard refresh
Different browser
Different computer
Restarting Reactor

Failed troubleshooting attempts:

No errors in Chrome console
No relevant errors in Reactor log (can still PM the full log file)

Reactor version: latest-24293-ea42a81d
Hardware: Odroid N2+
Linux version: Ubuntu 24.04.1 LTS

3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled

ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled

Multi-System Reactor
Is there a way to restart an add-on in HAAS from MSR?
T

Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.

What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?

Running:

Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]

HAAS:

RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0
Multi-System Reactor
Log files
wmarcolinW

Hi!

Is it possible to generate two additional log files, the first being the replica of what is displayed on screen by the Rule History widgets and the other with Recently Changed Entities?

And could I configure the generation of one file per day, and delete the older ones? For example, store the last 5 days?

And being more ambitious, does Windget have an icon to open these TXT files in the navigated?

Well, we're approaching Christmas, so here's my request to Santa Claus @toggledbits 🙂

Multi-System Reactor
[Reactor] Services with sync response
therealdbT

Hi @toggledbits

I'm working on a controller to generate llm response from a prompt in reactor. I have http response coming thru an http request action at the moment, capturing the response inside a local variable. So, it's practically sync.

I want to create a controller, so I don't have to rely on a proxy (and have a simpler architecture), and duplicate absurd http actions, but AFAIK in the current implementation, actions are async only. But if I have multiple requests going on, I cannot be sure what it's really inside an attribute. I also thought that something like a correlation id when sending the request could be used to identity multiple responses, but I wanted to double check with you before starting with something too complicated. I also noticed that some actions in home assistant (ie forecast) are sync and I'm wondering if you have any plan or hint to address this situation. Thanks.

Thanks.

Multi-System Reactor
TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL
SnowmanS

@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

battery_power.level=0.99 battery_power.since=1699401727360 binary_sensor.state=false tamper.state=true tilt_sensor.state=null x_debug.dt={"entity_class":"Binary Sensor","match":"deviceClass.generic.key=7","description":"Z-Wave Plus Tilt Sensor","default_name":"Tilt Sensor","model":"TILTZWAVE2.5-ECO","capabilities":["tilt_sensor"],"primary_attribute":"tilt_sensor.state","values":[{"valueId":"32:currentValue:","capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}}],"manufacturerId":330,"productType":4,"productId":3} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=99 x_zwave_values.Binary_Sensor_Any=false x_zwave_values.Configuration_Basic_Sets_for_Association_Group_2=0 x_zwave_values.Configuration_Send_Reports=0 x_zwave_values.Manufacturer_Specific_manufacturerId=330 x_zwave_values.Manufacturer_Specific_productId=3 x_zwave_values.Manufacturer_Specific_productType=4 x_zwave_values.Notification_Access_Control_Door_state=23 x_zwave_values.Notification_Access_Control_Door_state_simple=23 x_zwave_values.Notification_Home_Security_Cover_status=3 x_zwave_values.Notification_Power_Management_Battery_maintenance_status=0 x_zwave_values.Notification_UNKNOWN_0x46=23 x_zwave_values.Notification_alarmLevel=0 x_zwave_values.Notification_alarmType=0 x_zwave_values.Version_firmwareVersions=["10.1"] x_zwave_values.Version_hardwareVersion=2 x_zwave_values.Version_libraryType=6 x_zwave_values.Version_protocolVersion="4.5" x_zwave_values.Wake_Up_controllerNodeId=1 x_zwave_values.Wake_Up_wakeUpInterval=14400 zwave_device.capabilities=[48,112,113,114,128,132,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Notification Sensor" zwave_device.impl_sig="23305:1:22057:1" zwave_device.is_beaming=false zwave_device.is_listening=false zwave_device.is_routing=true zwave_device.is_secure=false zwave_device.last_wakeup=1699563172708 zwave_device.manufacturer_info=[330,4,3] zwave_device.max_data_rate=null zwave_device.node_id=24 zwave_device.specific_class="Notification Sensor" zwave_device.status=1 zwave_device.status_text="asleep" zwave_device.version_info=[null,"10.1"] zwave_device.wakeup_interval=14400
Multi-System Reactor
Unusual zwavejs entity naming convention
SnowmanS

@toggledbits I have noticed after upgrading both Reactor and ZWaveJSController to version 24257 that two of my devices/entities, TILT-ZWAVE2.5-ECO and Zooz ZSE18, had their entity re-named in an unusual way and also appears to be duplicated.

Reactor version 24257
ZWaveJSController version 24257
Z-Wave JS UI version 9.18.1
zwave-js version 13.2.0

Vestibule Motion Sensor State attributes/partial screenshot of entities it created. All entities have the same attributes.

motion_sensor.state=true x_zwave_values.Notification_Home_Security_Motion_sensor_status=8 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=23 zwave_device.valueId=[113,"Notification","Home Security","Home Security","Motion sensor status","Motion sensor status"] zwave_device.version_info=null

Zooz ZSE18 Motion Sensor.jpg

Tilt Sensor Door State and Tilt Sensor Door State Simple attributes/partial screenshot of entities it created. All entities have similar attributes with exception of x_zwave_values.Notification_Access_Control_Door_State = 22 or 23.

tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state_simple=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state_simple=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null

TILT-ZWAVE2.5-ECO.jpg

Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT

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:

GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor

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 🙂

Multi-System Reactor

Urgent Help MSR stopped running

Scheduled Pinned Locked Moved Multi-System Reactor
38 Posts 3 Posters 1.1k Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #5

    This is the reactor.service file I haven't changed anything in there.

    [Unit]
Description=Multi System Reactor
After=network.target

[Service]
Type=simple
User=stuart
Environment=NODE_PATH=/home/stuart/reactor
WorkingDirectory=/home/stuart/reactor
ExecStart=/usr/bin/node app -p
Restart=on-failure
RestartSec=5s

[Install]
WantedBy=multi-user.target

    If I run these commands:

    sudo systemctl stop reactor

    and then

    sudo systemctl start reactor

    and then

    systemctl --type=service

    It still says that the reactor service is "activating"

    reactor.service loaded activating auto-restart Multi System Reactor
    1 Reply Last reply
    0
  • K Offline
    K Offline
    kfxo
    wrote on last edited by
    #6

    The logs dont say anything else? If not I dont know and you might have to wait for @toggledbits

    1 Reply Last reply
    0
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #7

    The timestamps in the logs don't seem to match the actual time here now, so I am having issues working out what is new or not in the logs.

    1 Reply Last reply
    0
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by cw-kid
    #8

    I guess MSR is not currently logging as its down. The last line in the log is this at 16:16 pm which was 4 hours ago.

    [latest-22053]2022-03-18T16:16:32.655Z InfluxFeed:ERR [InfluxFeed]InfluxFeed#influx write failed (data lost): [Error]Er

    And there was lost of these lines:

    [latest-22053]2022-03-18T16:16:29.947Z InfluxFeed:ERR [InfluxFeed]InfluxFeed#influx write failed (data lost): [Error]Error: connect ECONNREFUSED 192.168.0.36:8086

    But I don't know when the Pi went down? and the InfluxDB so may or may not be related.

    1 Reply Last reply
    0
  • K Offline
    K Offline
    kfxo
    wrote on last edited by
    #9

    Not sure what else to try as you already commented out the Influx. Maybe back up your MSR files and try a fresh install.

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #10

    Troubleshooting section of the manual.

    My guess is (a) some hub isn't connecting and you didn't wait long enough for retries to time out (most common, but not only reason), and then you damaged the config file trying to edit out InfluxDB, which won't get in the way, it's just chatty. Follow the steps in the docs. Also, If you installed node-red after MSR, there is a bug in their install script that can corrupt your nodejs install system-wide. Hopefully it's not that. Back on Monday. Good luck!

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    1 Reply Last reply
    0
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #11

    Initially I commented out all the plugin lines in the reactor.yaml file. After that didn't work I just deleted the entire plugins section from the file and that didn't work either.

    1 Reply Last reply
    0
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #12

    Can't remember if I installed Node-Red or MSR first. Node-Red has been on this Linux Debian box along with MSR since day 1 when I first set it up.

    1 Reply Last reply
    0
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #13

    I took a copy of the reactor.yaml file before I edited it, I just restored that and reboot and its still down in the browser.

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #14

    Again, follow the steps in the Troubleshooting section of the docs.

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    cw-kidC 1 Reply Last reply
    0
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    replied to toggledbits on last edited by cw-kid
    #15

    @toggledbits

    I am trying to download the log files from the /var/log folder now.

    Is this bad ?

    a4bc78de-fe0a-4e6c-bc24-385d2efb8e02-image.png

    EDIT:

    Was in the wrong directory, this looks better.

    cd4c0199-cb1b-435e-a3a8-9c284050d59e-image.png

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #16

    You should not be running npm as root.

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    1 Reply Last reply
    0
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #17

    I normally login as root. When I run it under my name I get this:

    6e9f7719-3c40-4cc2-8734-0ca46735779a-image.png

    1 Reply Last reply
    0
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by cw-kid
    #18

    Am I running out of disk space?

    60ed2dd0-3caa-48a2-a853-0d1551a8d583-image.png

    b9196386-d224-4470-b1a1-2144150f361e-image.png

    1 Reply Last reply
    0
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #19

    The syslog is massive and I am not sure what I am looking for, however I just saw this:

    Mar 18 18:03:33 HP-Thin01 node[407]: NODE_PATH /home/stuart/reactor
Mar 18 18:03:33 HP-Thin01 node[407]: node:internal/fs/utils:344
Mar 18 18:03:33 HP-Thin01 node[407]:     throw err;
Mar 18 18:03:33 HP-Thin01 node[407]:     ^
Mar 18 18:03:33 HP-Thin01 node[407]: Error: ENOSPC: no space left on device, write
Mar 18 18:03:33 HP-Thin01 node[407]:     at Object.writeSync (node:fs:884:3)
Mar 18 18:03:33 HP-Thin01 node[407]:     at Object.writeFileSync (node:fs:2159:26)
Mar 18 18:03:33 HP-Thin01 node[407]:     at Object.<anonymous> (/home/stuart/reactor/app.js:236:133)
Mar 18 18:03:33 HP-Thin01 node[407]:     at Module._compile (node:internal/modules/cjs/loader:1101:14)
Mar 18 18:03:33 HP-Thin01 node[407]:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
Mar 18 18:03:33 HP-Thin01 node[407]:     at Module.load (node:internal/modules/cjs/loader:981:32)
Mar 18 18:03:33 HP-Thin01 node[407]:     at Function.Module._load (node:internal/modules/cjs/loader:822:12)
Mar 18 18:03:33 HP-Thin01 node[407]:     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
Mar 18 18:03:33 HP-Thin01 node[407]:     at node:internal/main/run_main_module:17:47 {
Mar 18 18:03:33 HP-Thin01 node[407]:   errno: -28,
Mar 18 18:03:33 HP-Thin01 node[407]:   syscall: 'write',
Mar 18 18:03:33 HP-Thin01 node[407]:   code: 'ENOSPC'
Mar 18 18:03:33 HP-Thin01 node[407]: }
Mar 18 18:03:33 HP-Thin01 systemd[1]: reactor.service: Main process exited, code=exited, status=1/FAILURE
Mar 18 18:03:33 HP-Thin01 systemd[1]: reactor.service: Failed with result 'exit-code'.

    If I am running out of disk space, I am not sure really how and where to find out what is talking up all the space and how to clear it.

    I am only running MSR, Node-Red and HA Bridge nothing else on this box.

    Thanks

    1 Reply Last reply
    0
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #20

    OK I have deleted some log files and got some free space back

    e079a286-3275-4367-a297-18fd5d9e0fc1-image.png

    /dev/sda2 is the main partition by the looks of it.

    However after a reboot MSR still isn't loading up.

    So my system is knackered currently as all my automation rules run on MSR.

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #21

    Ok, so now look at the logs again. Disk space problem hiding others, now you should be able to see them.

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    1 Reply Last reply
    0
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by cw-kid
    #22

    Don't know what's happened now but reactor.service is not even in the list at all anymore.

    5c811953-8e67-497a-a6e1-b048dc1f99db-image.png

    The service file is still in there

    58f2f4ef-6ec7-48d8-b572-21173ef31d44-image.png

    I'm downloading the syslog again now.

    1 Reply Last reply
    0
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by cw-kid
    #23

    @toggledbits

    OK these are the latest entries in the syslog to do with reactor

    Mar 18 22:07:48 HP-Thin01 node[522]: NODE_PATH /home/stuart/reactor
Mar 18 22:07:48 HP-Thin01 node[522]: FileLogStream { type: 'file', name: 'reactor.log', maxsize: 2, keep: 5 }
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.123Z <app:null> Reactor latest-22069-ebeefad starting on v16.13.1
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.126Z <app:INFO> Process ID 522; platform linux/x64 #1 SMP Debian 4.19.208-1 (2021-09-29); locale en_GB.UTF-8
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.127Z <app:INFO> Basedir /home/stuart/reactor; data in /home/stuart/reactor/storage
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.128Z <app:INFO> NODE_PATH=/home/stuart/reactor
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.135Z <app:INFO> Configured locale (undefined); selected locale(s) en_GB.UTF-8
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.195Z <app:INFO> Loaded locale en-US
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.223Z <Capabilities:null> Module Capabilities v21333
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.354Z <Plugin:null> Module Plugin v21186
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.369Z <TimerBroker:null> Module TimerBroker v21333
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.381Z <default:INFO> Module Entity v22042
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.391Z <Controller:null> Module Controller v22003
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.392Z <default:null> Module Structure v22047
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.413Z <default:null> Module Ruleset v21096
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.414Z <default:null> Module Rulesets v21096
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.433Z <GlobalExpression:null> Module GlobalExpression v21333
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.474Z <Predicate:null> Module Predicate v22067
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.484Z <AlertManager:null> Module AlertManager v21355
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.490Z <default:null> Module Rule v22043
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.500Z <GlobalReaction:null> Module GlobalReaction v21333
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.504Z <default:null> Module Engine v22053
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.505Z <default:null> Module httpapi v22021
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.510Z <default:null> Module httpproxy v21333
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.554Z <default:null> Module wsapi v21334
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.558Z <app:NOTICE> Starting Structure...
ar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.558Z <app:NOTICE> Starting Structure...
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.567Z <IndividualFileStrategy:ERR> [IndividualFileStrategy][IndividualFileStrategy#/home/stuart/reactor/storage] failed to read sys_alerts in /home/stuart/reactor/storage/states/sys_alerts.json: [SyntaxError]SyntaxError: Unexpected end of JSON input
Mar 18 22:07:48 HP-Thin01 node[522]: Trapped unhandled Promise rejection SyntaxError: Unexpected end of JSON input
Mar 18 22:07:48 HP-Thin01 node[522]:     at JSON.parse (<anonymous>)
Mar 18 22:07:48 HP-Thin01 node[522]:     at IndividualFileStrategy.getDataObject (/home/stuart/reactor/server/lib/IndividualFileStrategy.js:123:47)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Container.getDataObject (/home/stuart/reactor/server/lib/Container.js:98:51)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Structure.start (/home/stuart/reactor/server/lib/Structure.js:280:631)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Object.<anonymous> (/home/stuart/reactor/app.js:288:80)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Module._compile (node:internal/modules/cjs/loader:1101:14)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Module.load (node:internal/modules/cjs/loader:981:32)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Function.Module._load (node:internal/modules/cjs/loader:822:12)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
Mar 18 22:07:48 HP-Thin01 node[522]: SyntaxError: Unexpected end of JSON input
Mar 18 22:07:48 HP-Thin01 node[522]:     at JSON.parse (<anonymous>)
Mar 18 22:07:48 HP-Thin01 node[522]:     at IndividualFileStrategy.getDataObject (/home/stuart/reactor/server/lib/IndividualFileStrategy.js:123:47)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Container.getDataObject (/home/stuart/reactor/server/lib/Container.js:98:51)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Structure.start (/home/stuart/reactor/server/lib/Structure.js:280:631)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Object.<anonymous> (/home/stuart/reactor/app.js:288:80)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Module._compile (node:internal/modules/cjs/loader:1101:14)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Module.load (node:internal/modules/cjs/loader:981:32)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Function.Module._load (node:internal/modules/cjs/loader:822:12)
Mar 18 22:07:48 HP-Thin01 node[522]:     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
Mar 18 22:07:48 HP-Thin01 node[522]: Promise {
Mar 18 22:07:48 HP-Thin01 node[522]:   <rejected> SyntaxError: Unexpected end of JSON input
Mar 18 22:07:48 HP-Thin01 node[522]:       at JSON.parse (<anonymous>)
Mar 18 22:07:48 HP-Thin01 node[522]:       at IndividualFileStrategy.getDataObject (/home/stuart/reactor/server/lib/IndividualFileStrategy.js:123:47)
Mar 18 22:07:48 HP-Thin01 node[522]:       at Container.getDataObject (/home/stuart/reactor/server/lib/Container.js:98:51)
Mar 18 22:07:48 HP-Thin01 node[522]:       at Structure.start (/home/stuart/reactor/server/lib/Structure.js:280:631)
Mar 18 22:07:48 HP-Thin01 node[522]:       at Object.<anonymous> (/home/stuart/reactor/app.js:288:80)
Mar 18 22:07:48 HP-Thin01 node[522]:       at Module._compile (node:internal/modules/cjs/loader:1101:14)
Mar 18 22:07:48 HP-Thin01 node[522]:       at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
Mar 18 22:07:48 HP-Thin01 node[522]:       at Module.load (node:internal/modules/cjs/loader:981:32)
Mar 18 22:07:48 HP-Thin01 node[522]:       at Function.Module._load (node:internal/modules/cjs/loader:822:12)
Mar 18 22:07:48 HP-Thin01 node[522]:       at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
Mar 18 22:07:48 HP-Thin01 node[522]: }
Mar 18 22:07:48 HP-Thin01 node[522]: Trace
Mar 18 22:07:48 HP-Thin01 node[522]:     at process.<anonymous> (/home/stuart/reactor/app.js:271:162)
Mar 18 22:07:48 HP-Thin01 node[522]:     at process.emit (node:events:390:28)
Mar 18 22:07:48 HP-Thin01 node[522]:     at process.emit (node:domain:475:12)
Mar 18 22:07:48 HP-Thin01 node[522]:     at emit (node:internal/process/promises:136:22)
Mar 18 22:07:48 HP-Thin01 node[522]:     at processPromiseRejections (node:internal/process/promises:242:25)
Mar 18 22:07:48 HP-Thin01 node[522]:     at processTicksAndRejections (node:internal/process/task_queues:97:32)
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.582Z <app:ERR> Trapped unhandled Promise rejection: [SyntaxError]SyntaxError: Unexpected end of JSON input
Mar 18 22:07:48 HP-Thin01 node[522]: [latest-22069]2022-03-18T22:07:48.582Z <app:ERR> Please refer to the console log for trace
Mar 18 22:07:48 HP-Thin01 systemd[1]: reactor.service: Succeeded.

    Mar 18 22:05:28 HP-Thin01 node[402]: [latest-22069]2022-03-18T22:05:28.048Z <IndividualFileStrategy:ERR> [IndividualFileStrategy][IndividualFileStrategy#/home/stuart/reactor/storage] failed to read sys_alerts in /home/stuart/reactor/storage/states/sys_alerts.json: [SyntaxError]SyntaxError: Unexpected end of JSON input
Mar 18 22:05:28 HP-Thin01 node[402]: Trapped unhandled Promise rejection SyntaxError: Unexpected end of JSON input
Mar 18 22:05:28 HP-Thin01 node[402]:     at JSON.parse (<anonymous>)
Mar 18 22:05:28 HP-Thin01 node[402]:     at IndividualFileStrategy.getDataObject (/home/stuart/reactor/server/lib/IndividualFileStrategy.js:123:47)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Container.getDataObject (/home/stuart/reactor/server/lib/Container.js:98:51)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Structure.start (/home/stuart/reactor/server/lib/Structure.js:280:631)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Object.<anonymous> (/home/stuart/reactor/app.js:288:80)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Module._compile (node:internal/modules/cjs/loader:1101:14)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Module.load (node:internal/modules/cjs/loader:981:32)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Function.Module._load (node:internal/modules/cjs/loader:822:12)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
Mar 18 22:05:28 HP-Thin01 node[402]: SyntaxError: Unexpected end of JSON input
Mar 18 22:05:28 HP-Thin01 node[402]:     at JSON.parse (<anonymous>)
Mar 18 22:05:28 HP-Thin01 node[402]:     at IndividualFileStrategy.getDataObject (/home/stuart/reactor/server/lib/IndividualFileStrategy.js:123:47)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Container.getDataObject (/home/stuart/reactor/server/lib/Container.js:98:51)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Structure.start (/home/stuart/reactor/server/lib/Structure.js:280:631)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Object.<anonymous> (/home/stuart/reactor/app.js:288:80)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Module._compile (node:internal/modules/cjs/loader:1101:14)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Module.load (node:internal/modules/cjs/loader:981:32)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Function.Module._load (node:internal/modules/cjs/loader:822:12)
Mar 18 22:05:28 HP-Thin01 node[402]:     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
Mar 18 22:05:28 HP-Thin01 node[402]: Promise {
Mar 18 22:05:28 HP-Thin01 node[402]:   <rejected> SyntaxError: Unexpected end of JSON input
Mar 18 22:05:28 HP-Thin01 node[402]:       at JSON.parse (<anonymous>)
Mar 18 22:05:28 HP-Thin01 node[402]:       at IndividualFileStrategy.getDataObject (/home/stuart/reactor/server/lib/IndividualFileStrategy.js:123:47)
Mar 18 22:05:28 HP-Thin01 node[402]:       at Container.getDataObject (/home/stuart/reactor/server/lib/Container.js:98:51)
Mar 18 22:05:28 HP-Thin01 node[402]:       at Structure.start (/home/stuart/reactor/server/lib/Structure.js:280:631)
Mar 18 22:05:28 HP-Thin01 node[402]:       at Object.<anonymous> (/home/stuart/reactor/app.js:288:80)
Mar 18 22:05:28 HP-Thin01 node[402]:       at Module._compile (node:internal/modules/cjs/loader:1101:14)
Mar 18 22:05:28 HP-Thin01 node[402]:       at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
Mar 18 22:05:28 HP-Thin01 node[402]:       at Module.load (node:internal/modules/cjs/loader:981:32)
Mar 18 22:05:28 HP-Thin01 node[402]:       at Function.Module._load (node:internal/modules/cjs/loader:822:12)
Mar 18 22:05:28 HP-Thin01 node[402]:       at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
Mar 18 22:05:28 HP-Thin01 node[402]: }
Mar 18 22:05:28 HP-Thin01 node[402]: Trace
Mar 18 22:05:28 HP-Thin01 node[402]:     at process.<anonymous> (/home/stuart/reactor/app.js:271:162)
Mar 18 22:05:28 HP-Thin01 node[402]:     at process.emit (node:events:390:28)
Mar 18 22:05:28 HP-Thin01 node[402]:     at process.emit (node:domain:475:12)
Mar 18 22:05:28 HP-Thin01 node[402]:     at emit (node:internal/process/promises:136:22)
Mar 18 22:05:28 HP-Thin01 node[402]:     at processPromiseRejections (node:internal/process/promises:242:25)
Mar 18 22:05:28 HP-Thin01 node[402]:     at processTicksAndRejections (node:internal/process/task_queues:97:32)
Mar 18 22:05:28 HP-Thin01 node[402]: [latest-22069]2022-03-18T22:05:28.097Z <app:ERR> Trapped unhandled Promise rejection: [SyntaxError]SyntaxError: Unexpected end of JSON input
    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #24

    The disk going full has resulted in the corruption of your storage folder. You will need to restore a backup.

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    cw-kidC 1 Reply Last reply
    0

Recent Topics

  • therealdbT
    MSR UI on a mobile browser
  • G
    New to Home Automation Looking for a Single app?
  • H
    UZB/RaZberry Firmwares - Update
  • therealdbT
    Sending data to a USB port to interface with a wireless switch
  • G
    Seeking Advice:
  • toggledbitsT
    [Reactor] Assignment to alarm ignored -- expression-driven global cannot be set by assignment
  • therealdbT
    [Reactor] [Dev] Clarifications/Docs for refreshCapabilities and Entity action implementations return types
  • akbooerA
    Looking for Remote Switch boxes that can also be used with a wireless Decora Style Switch.
  • parkercP
    Openluup - verabridge can not load devices.
  • toggledbitsT
    Access to log file viewer denied
  • akbooerA
    Why different types of Triggers within openLuup & ALTUI
  • R
    High temperature sensor for Zigbee
Powered by NodeBB | Contributors
Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
  • Login
  • Don't have an account? Register
  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved