Seems to be working perfectly. Thanks! Should have thought of that myself.
R
RHCPNG
@RHCPNG
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179
Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day.
"What did you do to trigger it?" Literally nothing, just walked away and returned and there it was.
Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer.
I'll try to grab some logs here shortly.
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.
This post does not apply to users of Intel/AMD-based systems. If you are using a Reactor image tagged latest-amd64 or stable-amd64, then this post does not apply to you. It also does not apply to bare-metal installs; it's for users of docker images on ARM-based systems only (principally Raspberry Pi hosts, but could be others).
After January 15, 2026, I will no longer produce the aarch64-tagged docker image for Reactor. The ARM images will be arm64 for 64-bit operating systems, and armv7l for 32-bit operating systems.
For those of you running a container from the aarch64 image today, this will be a relatively simple change: you just need to switch the image used for your docker container to a differently-tagged image. If you are using docker-compose, then this is a relatively simple matter of changing the image line in your docker-compose.yaml file and then stopping (docker-compose down) and restarting (docker-compose up -d) your Reactor daemon.
But there's a catch... not all of you can safely just switch from the aarch64 image to the arm64 image. And, you can't just trust the output of uname -m, for example, because this exposes the CPU architecture, but not the word size of the OS running on that CPU.
For Raspberry Pi systems, the transition to 64-bit operating systems was long (starting in 2016) and not always obvious — although there was a first "official" 64-bit OS for RPis in 2020, it did not become a default recommendation in the Raspberry Pi Imager until 2021, and then that was only the default for Pi 3/4 systems with >4GB RAM; it was 2022 before it was universally recommended for all 64-bit CPUs regardless of RAM size. Depending on when you first imaged your RPi system and what default you may have been offered/chosen, you could today easily have a 64-bit CPU Raspberry Pi running a 32-bit version of the operating system. Upgrades along the way would not change this; changing it to fully 64-bit requires a full reimage of the system.
To establish if your OS is 64- or 32-bit, log in to your Pi and run: sudo dpkg-architecture -q DEB_HOST_ARCH. If the response is arm64 or aarch64, then you are running a 64-bit OS and you should use the arm64-tagged image. If it's anything else, you are running a 32-bit OS, and you should use the armv7l-tagged image.
pi@rpi4-1:~ $ sudo dpkg-architecture -q DEB_HOST_ARCH
armhf
pi@rpi4-1:~ $ uname -m
aarch64
pi@rpi4-1:~ $
In the example above, the uname command reports that the CPU is 64-bit architecture (aarch64), which is true for the host on which I ran these commands, but the DEB_HOST_ARCH value is armhf, indicating a 32-bit operating system. This system has to use the armv7l-tagged image.
Other systems will have their own ways of determining the word size of the running OS. Since the majority of Reactor users running ARM systems are on Raspberry Pis, I am able to supply the above instructions, but if you happen to have a different ARM system, you'll need to do some web searching to figure out how to expose that information. Or, you can just try the arm64 image, and if it doesn't start up, try the armv7l image.
Remember to always back up your system before making any changes.
For everyone, please make this change as soon as possible, and if you have any trouble finding a working image, please (1) go back to the current aarch64 image; and (2) let me know in this thread along with as much detail about your host system as you can offer (including the output of the dpkg-architecture command mentioned above).
Hi,
I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available.
None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5.
Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image?
Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way:
docker buildx build --push \
-t <localrepo>/<project>:<tag> \
--platform=linux/arm64,linux/amd64 \
--file ./apps/<project>/Dockerfile .
This produces both the AMD64 and ARM64/v8 variants automatically.
Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications.
@toggledbits - tagging you in case you missed this.
Thanks,
mgvra
Sorry to write here without trying, but I’m flying today.
Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes?
That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Just throwing out a general hint to the people running Homebridge and MQTT.
Homebridge MQTT-Thing hasn't been updated in almost 2 years and it falls behind on compatibility with the development of Homebridge.
I was looking for a replacement and found Homebridge Easy MQTT and I think it's a good replacement for MQTT-Thing. I particularly find Easy MQTT Value tranformers easier to to understand and use compared to MQTT-Thing Apply function.
It took a while to migrate everything but I'm pleased and can recommend.
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1?
[latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" }
[latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } }
[latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-]
[latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed!
[latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload:
{"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320}
[latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data:
{"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}}
[latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-]
[latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" }
[latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1
[latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 }
[latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } }
[latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-]
[latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed!
[latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload:
{"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323}
[latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data:
{"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}}
[latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-]
[latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 }
[latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2
[latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Hello,
I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light?
Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ
Please help,
P.S
Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
I don't know if you guys are into dashboards, but I am.
For a second home I tried the Shelly Wall Display 2, and while not so big, it worked well over the summer.
Since we're remodeling our house, I just swapped my old Fire Tablet (with its own problems) with two new Shelly Wall Display XL. I just removed the standard firmware, and I added mine (https://github.com/dbochicchio/ShellyElevate), forked from https://github.com/RapierXbox/ShellyElevate
I just managed to support buttons (this thing has 4 of them) and it's all auto-discovered by Home Assistant and accessible via Reactor.
I also have a new build in the works with support for buttons inside HA.
I added a bonus Javascript interface sending events (screen/screensaver status, buttons, motion) to automatically drive the dashboard (all doing in HTML+Javascript and monitoring Reactor's variable).
This specifical thing excluded, go get one of them, the device has a decent CPU for HA dashboards and blends wonderfully in the decor.
Posts
-
Reset attribute value of entity in event handler -
Reset attribute value of entity in event handler@toggledbits Thanks, this is great. I will try it out!
-
Reset attribute value of entity in event handlerAdditional question:
- The entity value is not changing, because the value doesn't change, right? Or is the event not even triggered? (I don't see the entity flashing in the entities section, when I try to trigger the event)
- Can I add attribute metadata to the rule trigger to see if there was an update?
-
Reset attribute value of entity in event handlerHi all,
I have successfully created an event handler for the interactive notifications of HA, see: https://smarthome.community/post/15414
However, I'm not able to reset the value that the event has set.
This is my event handler:
event_targets: interactive_notification_responses: name: "Handle notification responses" capabilities: - string_sensor events: - event: event_type: mobile_app_notification_action data: action: "LAUNDRY_INSIDE" response: "string_sensor.value": expr: "event.data.action"I have only 1 button in the notification, so the value is the same every time.
Because of this my rule does not trigger a second time, because the value is the same.
My solution was to use an entity action and do a set_attribute to reset the value of the entity. But this does not seem to work.
This is my set reaction part:
Shouldn't this be working? And maybe there is a smarter way?
-
Organizing/ structuring rule sets and rulesThanks for your answer, that's basically the same way I use the rule sets.
-
Organizing/ structuring rule sets and rulesHi 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.
-
Feature Request: Sublevel in RulesetsHi @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!
-
Switching between z-wave software controllersHi all,
Is it easy to switch between z-wave software controllers? I have a UZB and I want to update the firmware through Z-Way, but in the end I would like to use Z-Wave JS UI.
Can I just turn the controller off and switch to another one?
-
Docker container for Z-Way@PerH said in Docker container for Z-Way:
Its been a while since i've used this now, I've moved to Z-WaveJS..
Socat - so you have a remote connection to your z-stick? Should work fine with this contatiner, just set it up in the docker-compose file.
That said, I would ask on the z-way forum, you may find a more current z-way version in a newer container..All settings should be persistent if volumes are set up correctly.
I don't have a remote connection yet, I'm preparing for the migration from Vera to Z-way. I wanted to nuke the Vera and use it as a central hub for my Z-way stick.
From what I've read, Socat will not work in combination with docker. The Ser2net/ Socat solution is giving me a headache with the preparation alone. It is difficult with docker, so it seems, unless you create a docker specifically with Socat in it. But creating docker images is not a skill I possess (yet).
Unlike others in this thread, I'm a fan of docker containers. (Easier to maintain, troubleshoot and keep up-to-date). But Socat is a show stopper for now.
I think I'll ditch the Vera Edge and Z-way docker. I'm looking at using a Raspberry Pi with USB/IP (can't easily install this on the Vera) now instead of Ser2net/Socat and running the Z-way addon for HA.
-
Docker container for Z-Way@PerH Does your docker image support Socat? And, if so, is the configuration persistent after a container update?
-
Expressions page showing old dataThe only lead I have is the disk space, I don't know what else it could be, although I cleared some space as soon as I got the notification.
I don't know what to do to further analyze this. I will monitor this and see if it happens again.
It would be helpful if Reactor could save the expressions to the json more often.
-
Expressions page showing old dataThe exit procedure seems fine.
[latest-23114]2023-06-21T17:47:59.159Z <Rule:INFO> Windows open (rule-grp1myo029o in Weer) starting evaluation; because expression-state-changed GlobalExpression#gTempOutside [latest-23114]2023-06-21T17:47:59.159Z <Rule:INFO> Windows closed (rule-grp1mznck5b in Weer) starting evaluation; because expression-state-changed GlobalExpression#gTempOutside [latest-23114]2023-06-21T17:47:59.160Z <Rule:INFO> Windows open (rule-grp1myo029o in Weer) trigger evaluation result is true (previously true) [latest-23114]2023-06-21T17:47:59.160Z <Rule:INFO> Windows open (rule-grp1myo029o in Weer) evaluated; trigger state unchanged (true); rule state remains SET [latest-23114]2023-06-21T17:47:59.161Z <Rule:INFO> Windows closed (rule-grp1mznck5b in Weer) trigger evaluation result is false (previously false) [latest-23114]2023-06-21T17:47:59.162Z <Rule:INFO> Windows closed (rule-grp1mznck5b in Weer) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23114]2023-06-21T17:47:59.162Z <Rule:INFO> Windows open (rule-grp1myo029o in Weer) evaluation complete [latest-23114]2023-06-21T17:47:59.162Z <Rule:INFO> Windows closed (rule-grp1mznck5b in Weer) evaluation complete [latest-23114]2023-06-21T17:48:07.032Z <app:NOTICE> Shutdown signal (SIGTERM) received. Stopping Reaction Engine... [latest-23114]2023-06-21T17:48:07.034Z <app:NOTICE> Closing APIs... [latest-23114]2023-06-21T17:48:07.035Z <wsapi:NOTICE> wsapi: closing... [latest-23114]2023-06-21T17:48:07.036Z <httpapi:NOTICE> HTTP API closing... [latest-23114]2023-06-21T17:48:07.036Z <app:NOTICE> Stopping Engine... [latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Motor op lader (rule-liot7yyg in Garage) stopping [latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Zonnescherm auto IN (rule-lipp4379 in Tuin) stopping [latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Zonnescherm auto UIT (rule-lhdixs68 in Tuin) stopping [latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Disk space low (rule-lgyxocj5 in System) stopping [latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Niels at home (rule-lg7vjm7n in Proximity) stopping [latest-23114]2023-06-21T17:48:07.042Z <Rule:NOTICE> Tessa at home (rule-lg7v960f in Proximity) stopping [latest-23114]2023-06-21T17:48:07.043Z <Rule:NOTICE> Tessa driving (rule-lg7v6f3w in Proximity) stopping [latest-23114]2023-06-21T17:48:07.043Z <Rule:NOTICE> Tessa at work (rule-lg7v3cm6 in Proximity) stopping [latest-23114]2023-06-21T17:48:07.043Z <Rule:NOTICE> Tessa at S&K (rule-lg7uxvzo in Proximity) stopping [latest-23114]2023-06-21T17:48:07.088Z <Rule:NOTICE> Windows open (rule-grp1myo029o in Weer) stopping [latest-23114]2023-06-21T17:48:07.088Z <Rule:NOTICE> Windows closed (rule-grp1mznck5b in Weer) stopping [latest-23114]2023-06-21T17:48:07.088Z <wsapi:NOTICE> wsapi: server closed [latest-23114]2023-06-21T17:48:07.089Z <httpapi:INFO> HTTP server closed. [latest-23114]2023-06-21T17:48:07.090Z <Rule:NOTICE> Motor op lader (rule-liot7yyg in Garage) stopped [latest-23114]2023-06-21T17:48:07.091Z <Rule:NOTICE> Zonnescherm auto IN (rule-lipp4379 in Tuin) stopped [latest-23114]2023-06-21T17:48:07.094Z <Rule:NOTICE> Zonnescherm auto UIT (rule-lhdixs68 in Tuin) stopped [latest-23114]2023-06-21T17:48:07.095Z <Rule:NOTICE> Disk space low (rule-lgyxocj5 in System) stopped [latest-23114]2023-06-21T17:48:07.096Z <Rule:NOTICE> Niels at home (rule-lg7vjm7n in Proximity) stopped [latest-23114]2023-06-21T17:48:07.097Z <Rule:NOTICE> Tessa at home (rule-lg7v960f in Proximity) stopped [latest-23114]2023-06-21T17:48:07.098Z <Rule:NOTICE> Tessa driving (rule-lg7v6f3w in Proximity) stopped [latest-23114]2023-06-21T17:48:07.099Z <Rule:NOTICE> Tessa at work (rule-lg7v3cm6 in Proximity) stopped [latest-23114]2023-06-21T17:48:07.100Z <Rule:NOTICE> Tessa at S&K (rule-lg7uxvzo in Proximity) stopped [latest-23114]2023-06-21T17:48:07.101Z <Rule:NOTICE> Windows open (rule-grp1myo029o in Weer) stopped [latest-23114]2023-06-21T17:48:07.102Z <Rule:NOTICE> Windows closed (rule-grp1mznck5b in Weer) stopped [latest-23114]2023-06-21T17:48:07.111Z <Engine:NOTICE> [Engine]Engine#1 has shut down. [latest-23114]2023-06-21T17:48:07.112Z <app:NOTICE> Closing Structure... [latest-23114]2023-06-21T17:48:07.112Z <Structure:NOTICE> Structure#1 Stopping controllers... [latest-23114]2023-06-21T17:48:07.112Z <Structure:INFO> Structure#1 stopping VeraController#openluup [latest-23114]2023-06-21T17:48:07.113Z <Controller:NOTICE> VeraController#openluup stopping [latest-23114]2023-06-21T17:48:07.117Z <Controller:ERR> Controller VeraController#openluup is off-line! [latest-23114]2023-06-21T17:48:07.952Z <Structure:INFO> Structure#1 stopping HassController#hass [latest-23114]2023-06-21T17:48:07.952Z <HassController:NOTICE> HassController#hass stopping [latest-23114]2023-06-21T17:48:07.965Z <wsapi:WARN> client close from unknown connection? "192.168.1.174#25" [latest-23114]2023-06-21T17:48:07.966Z <wsapi:WARN> client close from unknown connection? "192.168.1.174#24" [latest-23114]2023-06-21T17:48:07.983Z <HassController:NOTICE> HassController#hass websocket closing, 1000 [latest-23114]2023-06-21T17:48:07.985Z <Controller:NOTICE> HassController#hass stopping [latest-23114]2023-06-21T17:48:07.988Z <Controller:ERR> Controller HassController#hass is off-line! [latest-23114]2023-06-21T17:48:09.266Z <Structure:INFO> Structure#1 stopping DynamicGroupController#groups [latest-23114]2023-06-21T17:48:09.266Z <DynamicGroupController:null> DynamicGroupController#groups stopping [latest-23114]2023-06-21T17:48:09.267Z <Controller:NOTICE> DynamicGroupController#groups stopping [latest-23114]2023-06-21T17:48:09.268Z <Controller:ERR> Controller DynamicGroupController#groups is off-line! [latest-23114]2023-06-21T17:48:09.279Z <Structure:INFO> Structure#1 stopping SystemController#reactor_system [latest-23114]2023-06-21T17:48:09.279Z <Controller:NOTICE> SystemController#reactor_system stopping [latest-23114]2023-06-21T17:48:09.281Z <Controller:ERR> Controller SystemController#reactor_system is off-line! [latest-23114]2023-06-21T17:48:09.288Z <Structure:INFO> Structure#1 Final data sync... [latest-23114]2023-06-21T17:48:09.288Z <default:INFO> Closing container Container#rulesets [latest-23114]2023-06-21T17:48:09.289Z <default:INFO> Closing container Container#rules [latest-23114]2023-06-21T17:48:09.289Z <default:INFO> Closing container Container#reactions [latest-23114]2023-06-21T17:48:09.289Z <default:INFO> Closing container Container#states [latest-23114]2023-06-21T17:48:09.316Z <default:INFO> Closing container Container#default [latest-23114]2023-06-21T17:48:09.316Z <default:INFO> Closing container Container#expressions [latest-23114]2023-06-21T17:48:09.318Z <Structure:NOTICE> Structure Structure#1 stopped [latest-23114]2023-06-21T17:48:09.319Z <app:NOTICE> Stopping timers... [latest-23114]2023-06-21T17:48:09.319Z <app:NOTICE> Shutdown complete, process ID 1I did get a disk space notification, so my first thought was that that was the problem. But I believe there always was enough space, more than 1 gb at least.
Does Reactor do something more then only give a signal that disk space is low? Maybe save the cache or something in that line.
-
Expressions page showing old dataIs it possible to save it more often? I have to figure out what's causing the loss of the expressions, but for now my backup is "worthless". Now, the only way to get the expressions back would be a restore of a full backup of the docker files, but then I will potentially lose other changes.
Any idea why I only lose the expressions and not other changes that are done later?
-
Expressions page showing old dataSorry for posting in the other thread, but the problem didn't seem to only be applicable to the add-on.
You don't understand the problem fully. The browser was not the problem. The changes were gone in the expressions.json.
After doing the changes again in the browser, the changes were still not visible in the json. Only after a restart, they were visible in the json.
-
Expressions page showing old dataHi @toggledbits,
I seem to be having the same issue. Is it possible that the expressions are only saved to the json when a restart of Reactor is done?
Today I looked in Reactor and saw an old version of all my expressions. My latest changes were gone (done a few days ago). Reactor didn't have a restart in the meantime.
When I recreated all new expressions and looked in expression.json, the new expressions weren't there (yet). After I did a restart of Reactor, the changes were visible.
Which moments are the expressions saved to the file?
I'm not running the add-on, but the docker. I do not have the latest update yet (latest-23114-e4060aae)
This doesn't explain why my changes were gone, but I'm still tinkering about that. Maybe my backup messes something up.
-
Can't post screen shots here now?Same here.
-
Testing reaction set global expressionOk, that makes sense. Thanks for clearing this up! Maybe make a note in the documentation? Most kind of expect all the actions to run when you click the "Run action now" button on the Reaction, I think. And it's even more confusing if it's also dependent on the rule being active or not.
-
Testing reaction set global expression@toggledbits But why do other actions DO run, when I hit "Run action now", even though my rule is deactivated.
I have an "entity action" next to the "set variable" in the same reaction and this action does fire.
-
Testing reaction set global expressionSorry, can't upload a screenshot. The website gives me a connection error when I try to add it.
-
Testing reaction set global expressionHi @toggledbits
Just a quick question. I noticed that I can't test a "set variable" action when the rule is not active. I wanted to set a global expression in a reaction and wanted to test it by pushing the "Run action now" button in the border of the reaction, but it didn't do anything. Only when I activated the rule, the button worked.
Is this a bug or is this by design?
I'm running the latest docker build:
latest-23114-e4060aae