Hi guys,
Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular.
Maybe there are better ways to organize my rule sets.
I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
I have installed MSR on a RP5 bare metal and then copied the config and store files. Everything seems to be on the RP5 but I am missing all global expression and I don't see the controller time.
Screenshot 2025-04-06 201446.png
My browser is Microsoft Edge Version 135.0.3179.54 (Official build) (64-bit)
I have probably done something stupid or missed a step but I am stuck.
Thanks for any help.
Hi,
It seems that the widget deletion does not work. I tried to drag the widget to the left (as explained in here https://smarthome.community/topic/1071/deleting-widgets?_=1744037333660)
but it does not delete it. Anyone else experiencing the same problem?
Also the landing page after login is empty and seems be have some JS issues on the dev console:
Screenshot from 2025-04-07 18-06-19.png
fd7f0424-debb-49d3-86d8-9a3b09ad3868-image.png
Using dockerized version of Reactor (Multi-hub) latest-25082-3c348de6 on Chromium 135.0.7049.52 (Official Build) snap (64-bit)
br,
mgvra
Good day all,
I have an notification set up for my washing machine to let me know when it's complete. I have a templete sensor set up in HAAS to let me know if it's Washing, in Standby, or off, based upon the power consumption (Shelly 1PM on outlets)
The MSR code is relatively simple. I have a built in false positive attribute for if MSR gets rebooted, because I would suddenly get tons of notifications when I upgraded MSR.
6774565a-06cc-443f-99c1-e71301b33d83-image.png
What I'm trying to introduce, is a way to verify that I just didn't bump the knob on the washing machine when transferring loads from the washer to the dryer, which turns on the display and brings the power above the Standby threshold.
The power goes up to 3.7W for about 4 minutes if the selector knob is bumped/turned.
What would the best way to do this be? I have most of my MSR code set up for a couple of years now, and my coding logic is struggling a bit.
I think I need a power threshold to be substained for a minimum time period (say 2 or 3 minutes, above 10W), before the other triggers can act. What would the best way to do that be?
Running: latest-25082-3c348de6
Fedora 41 Server
HAAS:
Core
2025.3.4
Supervisor
2025.03.4
Operating System
15.1
Frontend
20250306.0
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 yaml configuration in local_mqtt_devices file
x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }'While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Hi!
I get this message when I'm on the status tab:
System Configuration Check
The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds.
I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6.
HA versions are:
Core 2025.3.4
Supervisor 2025.03.4
Operating System 15.1
I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version.
Do anyone know what I can try?
Thanks in advance!
Let's Be Careful Out There (Hill Street reference...) 🙂
/Fanan
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB.
While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed.
So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response.
While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits
Thanks!
Hi ,
I'm on
-Reactor (Multi-hub) latest-25067-62e21a2d
-Docker on Synology NAS
-ZWaveJSUI 9.31.0.6c80945
Problem with ZwaveJSUI:
When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white.
I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui.
I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb".
After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color.
This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite.
x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33}The "cold white" and "warm white" settings interfer with the rgb color settings.
Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white
are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white.
So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have
x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColorIn zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set.
x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this?
x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33}Thanks in advance.
Good day all,
I have a reaction set up, that I use for both troubleshooting and changing home modes when one of my family members either arrive or are leaving. I use the companion app for HAAS on our iPhones, and HAAS reports if the person associated with the iPhone enters or leaves the geofenced area around my home. I'm sure most MSR and HAAS users are familiar with this.
I use this rule set mainly as a condition for other rules, however, as part of troubleshooting, a notification is sent through HAAS to the companion app when the rule becomes true. The problem is that I'm getting notifications now for both arriving and departing simultaneously.
96b3f7db-ba09-499e-a78c-86903b603857-image.png
36903cdd-a87f-473b-82ef-af9ef96d3c44-image.png It used to work fine as intended. I'm not sure exactly when it changed, but now I'm getting two notifications when either of these conditions change.
Any idea what could be happening?
Edit:
Running: latest-25082-3c348de6, bare-metal Linux
ZWaveJSControllerr [0.1.25082]
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem?
I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Similarly as for local expressions, global expressions evaluate and update fine when getEntity(...) structure is used. However, at least when certain functions are in use, expressions do not update.
Consider the following test case:
Screenshot 2025-03-13 at 16.29.42.png
Even though auto-evaluation is active, value does not change (it changes only if that expression is manually run). MSR restarts do not help.
Screenshot 2025-03-13 at 16.31.43.png
Note: Tested using build 25067 on Docker. I have also a PR open (but couldn't now get details or PR number as my Mantis account was somehow expired?).
Trying to understand what cause a local expresssion to be evaluated. I have read the manual but I am still not clear about it. Using the test rule below, I can see in the log that the rule is being automatically evaluated every time the temperature entity is changing. That is great...
What I am trying to understand is why the expression is not evaluated based on time as well since the "case" statement has time dependencies.
Any help would be appreciated
I have the following test rule:
eba6a3ea-ff61-4610-88c9-9b9864f11ff8-Screenshot 2025-01-21 095244.png
2d9c1ff5-7b73-4005-b324-9029c2709db9-Screenshot 2025-01-21 095302.png
Here is the expressioncode:
vFrom1 = "09:25:00", vFrom2 = "09:30:00", vFrom3 = "09:41:00", vTo = "10:55:00", # Get current time (format HH:MM:SS) vToDay = strftime("%H:%M:%S"), #Get current house temperature CurrentHouseTemp = getEntity( "hass>Thermostat2 " ).attributes.temperature_sensor.value, case when CurrentHouseTemp <= 19 and vToDay >= vFrom1 && vToDay <= vTo: "true1" # From1 when CurrentHouseTemp <= 20 and vToDay >= vFrom2 && vToDay <= vTo: "true2" # From2 when CurrentHouseTemp < 26 and vToDay >= vFrom3 && vToDay <= vTo: "true3" # From3 else "false" endI am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved.
The Runtime Error is different in the two browsers
Safari v18.3
Google Chrome 133.0.6943.142
TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete 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.Steps to reproduce:
Click the pencil to edit a global reaction with a group.
Click the Exit button.
Runtime error appears.
or
Click Create Reaction
Click Add Action
Select Group
Add Condition such as Entity Attribute.
Add an Action.
Click Save
Click Exit
Runtime error appears.
I don’t know how long the error has been there as I haven’t edited the global reaction in a long time.
Reactor (Multi-hub) latest-25060-f32eaa46
Docker
Mac OS: 15.3.1
Thanks
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons.
I have not created a global expression for some times and just noticed this while doing some clean-up.
I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success.
Here's what the log shows.
[latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" }Reactor latest-25067-62e21a2d
Docker on Synology NAS
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method.
This was prompted by yesterday's fun and games with my ISP.
I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone)
I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions?
TIA
C
Hi,
I'm trying to integrate the sonos-mqtt (https://sonos2mqtt.svrooij.io/) with the MSR and it's coming along nicely so far.
But cannot wrap my head around how to define custom capabilities in MQTT templates. I need this for the TTS announcements and similarly for the notification sounds where I would pass the sound file as parameter.
So this is what I have in the local_mqtt_devices.yaml
capabilities: x_sonos_announcement: attributes: actions: speak: arguments: text: type: string volume: type: int delay: type: intAnd this is the template:
templates: sonos-announcement: capabilities: - x_sonos_announcement actions: x_sonos_announcement: speak: topic: "sonos/cmd/speak" payload: expr: > { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" } type: jsonSo the speak action should send something like this to topic sonos/cmd/speak
{ "text": "message goes here", "volume": 50, "delayMs": 100, "onlyWhenPlaying": false, "engine": "neural" }At startup the MSR seems to be quite unhappy with my configuration:
reactor | [latest-25016]2025-02-09T08:19:59.029Z <MQTTController:WARN> MQTTController#mqtt entity Entity#mqtt>sonos-announcement unable to configure capabilities [Array][ "x_sonos_announcement" ] reactor | i18n: missing fi-FI language string: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | i18n: missing fi-FI language string: Configuration for {0:q} has unrecognized capability {1:q} in actions reactor | Trace: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | at _T (/opt/reactor/server/lib/i18n.js:611:28) reactor | at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:125:25) reactor | at MQTTController.sendWarning (/opt/reactor/server/lib/Controller.js:627:30) reactor | at MQTTController.start (/var/reactor/ext/MQTTController/MQTTController.js:268:26) reactor | at async Promise.allSettled (index 0) Configuration for "sonos-announcement" has unrecognized capability "x_sonos_announcement" in actions Controller: MQTTController#mqtt Last 10:21:37 AM Configuration for "sonos-announcement" is incomplete because the following requested capabilities are undefined: x_sonos_announcement Controller: MQTTController#mqtt Last 10:21:37 AMThis is probably a pretty stupid question and the approach may not even work at all, but maybe someone or @toggledbits for sure, could point me to the right direction.
Basically the idea is to be able to send TTS messages from reactions using entity actions. I've previously used HTTP requests to Sonos HTTP API (https://hub.docker.com/r/chrisns/docker-node-sonos-http-api/) for the same functionality, but since moving to sonos-mqtt, I need a way to send the TTS notifications using MQTTController. Along with the actual message, volume and delay must also be parameterizable.
br,
mgvra
MSR latest-25016-d47fea38 / MQTTController [0.2.24293]
Hi, @toggledbits
I just noticed that following a reboot of my raspberry pi, some of the rules, that I was expecting to recover, are not catching up following a reboot. I have made a simple test rule (rule-m6rz6ol1) with only "after Date/time" as trigger and "turn on a lamp" as a set reaction. All my infrastructure is on the same board so Reactor, Hass, Zwavejs, ... are all rebooting.
Here is the sequence of the test case (All time converted to Zulu to match logs):
Rule "after Date/Time" set to 14:05:00z Shutdown on Raspberry Pi at 14:04:00z Power back up at 14:08:00z Rule overview shows true as of 14:08:14z waiting for 00:00:00 in GUIFrom the log I can see that MSR is picking up the rule and knows that the state of the rule has changed from false to true and tries to send the update to HASS but failed with websocket error.
Here is what I see from the log:
14:04:04z shutdown complete 14:08:08z Power up 14:08:13.111z websocket connection 14:08:15:323z Reaction to the light failed, Websocket not opened After there is a series of websocket connection attempt until 14:08:51z where it seemed to be really ready.Back in 2021 we had a discussion (https://smarthome.community/topic/700/solved-start-up?_=1738766986566) and you proposed to add a startup_delay:xxxx and startup_wait:xxxx parameter in the engine section of "reactor.yaml". When I try the startup_delay (this used to be a hard delay), the engine failed to start (I think). I then try the startup_wait:xxxx without any success. Since it wait for the connection status to be up to cancel the delay, it does not do anyting since Hass is reporting the socket up without really being up ( I think...).
Questions:
Did I figured it all wrong? should the startup_delay:xxxxx have worked? Any ideas?Here is the log:
OK now I am stuck. I did add the log but when I submit the editor complained saying that I am limited to 32767 characters. The log from the shutdown to the time the websocket is stable is about 300000 character long. What are my options?
Not a big issue simply a request if easily doable.
The MSR logs files inside the container are owned by root witch is fine however, the permissions are very restrictive. I do not know if there is something wrong with my installation but the logs permission are set to 222 (write only). Even if the docker volume is set for Read/Write the log files are retaining these values.
I go around the problem by doing a chmod 777 on all reactor logs but every time there is an MSR log rotation the permissions are set back to 222. So unless the permission are implemented in the container there is no permanent solution to this (that I know of).
I do not know much about Docker container so I do not know what is involved here.
Can the logfiles permission be simply chaged in the container to at least allow "other" read permission?
Could the MSR log rotation routine implement a chmod to set the permission?
Just a small anoyance
Thanks
Issues installing MSR on Debian 10 Linux
-
I'm reading this article about Debian and time here.
The date and time is currently set correctly:
"By default, Debian 10 runs the standard ntpd server to keep your system time synchronized with a pool of external time servers. We can check that it’s running with the systemctl command:"
sudo systemctl status ntpWhen I run this command in Putty it says:
Unit ntp.service could not be found.It goes on to say "To get more information about the status of ntpd we can use the ntpq command:"
ntpq -pI get the response:
-bash: ntpq: command not foundSo maybe its not currently installed on my installation.
its only a 16GB SSD in the HP Thin Client, so I don't have a desktop environment installed only SSH server etc.
I will look at installing this ntpd service next.
EDIT:
Ran this command to install it:
apt-get install ntpNow the above commands are working.
-
Hi, well I bought the HP T520 Thin Client because of what you said to me previously. It was cheap enough from eBay.
I had some issues with the power supply however as it didn't come with one.
I did have a spare suitably spec'd laptop power supply, but it had the wrong DC connector plug on the end of it.So I ordered the correct "DC Tip 7.4x5.0mm Power Plug Socket Connector" off eBay and cut the other one off and soldered the new one on.
However the HP Thin Client was not turning on, no power nothing at all and totally dead.
I then read that you have to use a genuine HP power supply, as they have some kind of checking so that the thin clients won't power on if you are using a 3rd party power supply.
Corporate Greed !
I then found an article about hacking the unit and soldering in a 240K resister on the back of the power input jack and I did this today and amazingly it worked and the thin client powered on.
One thing I can't figure out how to do yet is to update the BIOS without having one of their supported OS installed.
-
I don't have this exact model but... my HP desktops all have the ability to update the BIOS from within the UEFI BIOS. Have you tried that? Sorry for the song and dance on the power supply. I never encountered this since I always got power bricks with the ones I bought and I actually have spare power supplies... Great soldering job though!
-
There is an option in the BIOS menu to update / flash the BIOS but when I click OK on it, it says:
"Can not find bios update interface"
I've not really looked in to it properly yet as I was keen to get MSR up and running first.
From the quick Google searches I did, most suggested you need to have one of the HP supported operating systems installed to be able to update the BIOS.
But there must be some work around some how. I need to read in to it more.
-
@toggledbits I copied over the storage and config folder contents from the Rpi to the HP Thin Client and then restarted MSR on the thin client.
I did edit the base URL in the Reactor.yaml file.
I've stopped the MSR service on the Rpi so now the thin client is the only one running..
None of my scheduled rulesets based around sunset have run their actions this evening for some reason.
The time shown in the top of the MSR Web GUI is the correct time.
So seems I need to look into this further.
There is another schedule up coming, the garden lights should turn on 20 minutes after sunset, that is in about 20 minutes time from now, so will see if that happens?
EDIT:
These are the before sunset rules that the other rules reference in their triggers.
20 and 40 minutes before sunset, not sure why both say true as of the same time at 20:48pm.
The after sunset 20 minutes rule says:
waiting for 21:21:00
Its now 21:25pm and my garden lights have NOT turned on, so something not right here.
This is the summary card for the rule that turns on the garden lights:
-
Not sure which rule this is, but I am seeing several errors in the log like these:
2021-05-15T19:48:14.906Z <Rule:5:Rule.js:957> Rule#rule-km50yfxo._evaluate() mutex acquired, evaluating 2021-05-15T19:48:14.907Z <Rule:5:Rule.js:961> Rule#rule-km50yfxo update rate is 1/min limit 60/min 2021-05-15T19:48:14.908Z <Rule:5:Rule.js:883> Rule#rule-km50yfxo evaluateExpressions() with 0 expressions 2021-05-15T19:48:14.910Z <Rule:5:Rule.js:973> Rule#rule-km50yfxo._evaluate() trigger state now true (was true) 2021-05-15T19:48:14.911Z <Rule:5:Rule.js:1351> Rule#rule-km50yfxo cond cond5hu03sp timer schedule 1621119600000<16/05/2021, 00:00:00> 2021-05-15T19:48:14.913Z <Rule:5:Rule.js:975> Rule#rule-km50yfxo._evaluate() constraints state false 2021-05-15T19:48:14.913Z <Rule:null> Rule#rule-km50yfxo rule state now false, changed no 2021-05-15T19:48:14.915Z <Rule:CRIT> Error: EACCES: permission denied, open '/home/stuart/reactor/storage/states/cs-rule-km50yfxo.json' Error: EACCES: permission denied, open '/home/stuart/reactor/storage/states/cs-rule-km50yfxo.json' at Object.openSync (fs.js:498:3) at Object.writeFileSync (fs.js:1524:35) at IndividualFileStrategy.saveDataObject (/home/stuart/reactor/server/lib/IndividualFileStrategy.js:137:29) at Container.saveDataObject (/home/stuart/reactor/server/lib/Container.js:94:54) at Data.save (/home/stuart/reactor/server/lib/Data.js:152:49) at Rule._evaluate (/home/stuart/reactor/server/lib/Rule.js:985:365) at runMicrotasks (<anonymous>) at processTicksAndRejections (internal/process/task_queues.js:95:5) at async /home/stuart/reactor/server/lib/Rule.js:940:17Think something may have gone wrong with copying over the stuff from the Pi.
This is that folder in WinSCP on the HP Thin Client.
I installed MSR as a none root user aka as my own username name. But these rule set files most are saying root as the owner.
I was logged in to WinSCP as root user when I did the copy so maybe that is why.
If I try logging in to WinSCP as my username instead of root and then doing the copy again from the Pi to the Thin Client it doesn't work and I don't seem to have the permissions to do it.
If instead I try to change the group and owner of a file from root to my username I can't do that either:
So I am stuck now and don't know what to do.....
OK I logged back in to WinSCP as root and now I can change all the files their group and owner from root to my own user name. I have done that now for all of them.
So hopefully that fixes the problem? Will have to wait for later schedules to happen later this evening to see.
-
Make sure your system time zone is set to local time. If the default is UTC or something else, all time-based rules will be a mess. The displayed time in the GUI is browser time, not system (host) time.
Fix permissions in your Reactor config and storage with this:
sudo chown -R stuart:stuart config/ storage/Edit: To see current host time configuration:
http://your-msr-host-ip:8111/diag/sunAuthor of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@toggledbits said in Issues installing MSR on Debian 10 Linux:
The host time is currently 16/05/2021, 14:20:58 offset 60 minutes from UTC (TZ=undefined); location (lat,lon) 53.99078,-1.5373 elev 127; sunrise 16/05/2021, 05:01:40, sunset 16/05/2021, 21:03:33. {"sunrise":1621137700000,"sunset":1621195413000,"civdawn":1621134941000,"civdusk":1621198173000,"nautdawn":1621130939000,"nautdusk":1621202174000,"astrodawn":null,"astrodusk":null,"solarnoon":1621166557000,"daylength":16.031,"angle":14.6}Time looks to be correct, however it says "TZ=undefined".
None of my schedule rules were running last night because of the permissions issue when I copied them from the Pi to the Thin Client.
I fixed that and then they started working again OK.
I've got everything moved over from the Pi now to the new Thin Client, also setup today Node-Red and Java HA-Bridge.
What's the best way to be backing up Debian ?
The SSD is only 16GB so guess I could take a full system snapshot rather than just backing up certain files and folders.
-
Indeed a full system snapshot would be best and easier to recover but short of that, you can always backup the entire folder by running a cron job to copy the reactor folder either to a network drive or to a USB SSD you would have to plug into the T520.
-
I use
scpjust to copy theconfigandstoragedirectories. That's really all you need to from Reactor to get it going on a reinstall, as you've seen.I find file-based backups of entire Linux systems to be perilous, because permissions, links and special files almost always get screwed up somehow, so I never recommend that route. An image backup is better (I use
partcloneto back up used space only, and it's good about the later target system being a different size/geometry than the original/source), but I'll only do that maybe 1-2 times per year. I figure if I can restore an image quickly andapt-get updatemy way back to current, that's fast enough on recovery. -
T toggledbits locked this topic on
