Global Moderators group | Smart Home

toggledbits

Sorry, that's not possible in the current incarnation of access control... either everything is protected by user authentication (login), or its not. I use a trivial password on my guest account ("guest") to work around it.

toggledbits

TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future.

In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level.

Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way.

I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption.

A few other things to know:

If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc.
Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy).
The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON.
You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach).
The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case.
This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change.

This thread is open for any questions or concerns.

toggledbits

Please post a readable screen shot. I don't know what or how this one got posted, but it's tiny and low resolution and I can't see clearly what's in it.

therealdb

@toggledbits yes, fixed! thanks.

CatmanV2

Oh! Damn! And thanks!

C

toggledbits

Try 26011

therealdb

I have this Global Reaction doing some work around lights, based on the season:

When I run it, both the lights in Summer and Winter groups are turned on. Very, very strange. I tried removing and adding the groups again, with no joy.

I see these on the logs:

[latest-25328]2026-01-11T18:23:11.847Z <Engine:CRIT> TypeError: this[_0x3c7c88(...)][_0x3c7c88(...)] is not a function [-]
TypeError: this[_0x3c7c88(...)][_0x3c7c88(...)] is not a function
    at GlobalReactionPredicateContext.toString (/opt/reactor/server/lib/PredicateContext.js:87:126)
    at Logger.getLogger (/opt/reactor/server/lib/Logger.js:417:31)
    at new GlobalReactionPredicateContext (/opt/reactor/server/lib/GlobalReactionPredicateContext.js:62:93)
    at Engine._resume_reaction (/opt/reactor/server/lib/Engine.js:2136:55)
    at Engine._process_reaction_queue (/opt/reactor/server/lib/Engine.js:2031:133)
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
[latest-25328]2026-01-11T18:23:12.155Z <Engine:CRIT> Engine#1 alarm() context is rule Rule#rule-mf29005p condition condmf29005q Script; timer ID will be alarm:rule:rule-mf29005p:cond:condmf29005q
[latest-25328]2026-01-11T18:23:13.159Z <Engine:CRIT> Engine#1 alarm() context is rule Rule#rule-mf29005p condition condmf29005q Script; timer ID will be alarm:rule:rule-mf29005p:cond:condmf29005q
[latest-25328]2026-01-11T18:23:14.376Z <Engine:CRIT> TypeError: this[_0x3c7c88(...)][_0x3c7c88(...)] is not a function [-]
TypeError: this[_0x3c7c88(...)][_0x3c7c88(...)] is not a function
    at GlobalReactionPredicateContext.toString (/opt/reactor/server/lib/PredicateContext.js:87:126)
    at Logger.getLogger (/opt/reactor/server/lib/Logger.js:417:31)
    at new GlobalReactionPredicateContext (/opt/reactor/server/lib/GlobalReactionPredicateContext.js:62:93)
    at Engine._resume_reaction (/opt/reactor/server/lib/Engine.js:2136:55)
    at Engine._process_reaction_queue (/opt/reactor/server/lib/Engine.js:2031:133)

Maybe some old format that was corrupted in the rule? @toggledbits

toggledbits

Reaction build 26011

USERS OF AARCH64-tagged DOCKER IMAGES: Per this earlier post, this build will likely be the last with the aarch64 tag. Please follow the post's guidance for changing to one of the newer tags appropriate for your hardware and OS (32-bit armv7l or 64-bit arm64).

Reactions UI: Fix update of display after copy in-place.
Don't store reaction history entries for sub-reactions
VirtualEntityController: better consistency in time-series configuration; update documentation.
Fix an error in date display of time range conditions within certain parameters.
HassController: Bless HA to 2026.1.0

This is a "silent" release (it is not advertised in the Status page of Reactor).

toggledbits

Reactor build 25238

Rules/Date-Time: Fix a regression (in 25315) where a Date-Time between condition that crosses midnight may determine incorrect state if the Rule is reloaded (e.g. by editing it or a Reactor restart) in the period after midnight but before the end time.
Restarts on Win32 systems can now (finally) do a gradual, organized reload or shutdown.
HassController: Bless HA to 2025.11.3

This is a "silent" release (it is not advertised in the Status page of Reactor)

toggledbits

@CatmanV2 said in Possible feature request 2?:

Any chance of a 'bulk delete' option?

Each Controller instance implements sys_system.purge_dead_entities action.

This is also automatic for the Controller implementations I provide for entities that are older than 24 hours when the controller connects/reconnects.

Global Moderators

Posts

Reaction build 26011

Reactor build 25238

Member List