Global Moderators group | Smart Home

CatmanV2

Awesome!

C

toggledbits

sys_system.state for the Controller instance.

CatmanV2

Having been messing around with some stuff I worked a way to self trigger some tests that I wanted to do on the HA <> MSR integration

This got me wondering if there's an entity that changes state / is exposed when a configured controller goes off line? I can't see one but thought it might be hidden or something?

Cheers

C

CatmanV2

Having hours of (actually quite fun) interaction with AI (Chat GPT) making up dashboards and sensors for HA.

It's OK (well it's better than I am!) but it makes soooo many mistakes. Gets there in the end though, if you've half a clue (which I do half the time)

C

CatmanV2

Another vote. Moved off Vera years ago. Ran OpenLuup on a Zwave.me stick. Minimised my Z-wave network this last month. I have two thermostats, a fibaro smart module with three temperature sensors that I don't need, and some virtual switches that I'm migrating into HA / Reactor.
Once I can settle on replacements for the thermostats, it'll all go, and I'll be HA / MSR only / MQTT only

C

therealdb

I’d go with ZwaveJS. I migrated from Vera Zwave radio to a new usb radio and then to home assistant Zwave dongle. I recommend their antenna because the range is incredible. Zero lags and zero packet lost. See my older posts.

toggledbits

It should be fine. Take a backup of your storage directory in its entirety before the upgrade, along with config and any other directories where you may have customizations (perhaps also ext if you have add-in Controllers). Then go. Make sure you do a npm run deps in the install directory before starting the new version of Reactor, to upgrade package dependencies, or Reactor will likely not start. Post if you have any problems.

Edit: Oh! And very important... make sure you are running nodejs version 18 or higher. If you have to upgrade, install a current LTS (Long-Term Support) version (either 22 or 24). Stick to even-numbered releases.

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.

Global Moderators

Posts

Member List