I have got some warnings i reactor that a rule is throttled because it update rate is over 120/minute, happens now and when with a week or two in between.

The rule monitors my house power consumption when charging my car, and if if consumption risks to kill a main fuse, it stops the charging.
Thought I was clever when I in Constraints added that my car should be located at home and charging is active, but apparantly it wasn't clever enough...
I had understand it that if Constraints isn't true, then the triggers isn't evaluated.

I have a Shelly 3EM meter that measure three channel/phases and updates every second. So just for this three channels it is 180 updates per minute...
And now when I start to take a closer look I can se in my logs that this rule is evaluated with every value change on any of the three phases...
So ~11MB of logs only goes back in time around 16 hours...

So what is the best solution?
Should move my "Constraints" in an new trigger group, before my existing triggers?

Rule as it is now

Hi

Bought a new ZB device, an EV charger.
I was aware that there would one manufacturer specific cluster that wouldn't work out of the box, but several other clusters I hoped would work from start does not. Or at least there isn't any enteties for them.

So I have tried to study how to write a local quirk, but it is a bit overwhelming for mt brain.
Usually I can manage do get stuff moving with intense googling, finding guides or different solutions that I can start from, but here I find nothing that I can wrap my head around.
My latest try was to chat with Gemini AI (programmers, rest assured that your job will be safe for the foreseeable future )

I have gathered my device Diagnostic Info.
I have manufacturers ZB documentation.
A device support request is created on zigpy github (no response the last weeks)

For now there is just two entities for my device, on/off switch and energy sensors.

All non manufacture attributes and commands seems to be recognized in ZHA "Manage this Device"
It would be great if I could get some entities out of them.
For example the entity for manage charging power is expected to be presented as a dimmer slider.
But why isn't there any entity created??

The manufacture specific cluster is more of nice-to-have and could maybe be solved another day.

Any help would be much appreciated.

@Snowman
I think my old thread could be helpful for you.
Good luck
Adding remotes, scene controllers as entities to MSR

@toggledbits
No, I get how NutController works. So far at least...

But when I got stuck several times trying to set up NUT I almost gave up. At the same time I remembered seeing some System Info in MSR and if could find data about battery level, charging and so on I would not even need the NUT Installation.
And that would be a big bonus for me as I realize that when my NUT installation fails one day it would take me long time to figure it out and also one less process/config to handle.

And from System Info I assume we could get info about temperatures, storage levels, fan speeds and so on?
This could be used to send warning notifications from MSR.

So yes, I was asking something else that come up in my head when I tried to find another way than using NUT.

@toggledbits
Yep, that did it
Thanks once again @toggledbits

Any thougts about getting more System Info into MSR by the way?
This got me thinking on another possible solution. Reactor already monitors "System Memory" "Uptime" and so on, so maybe it also could monitor Powersource, Battery Level, Charging State? Then let Reactor react with its magic

@toggledbits
So, back from vacation so time to take another shot at this

npm list:

C:\reactor\ext\NUTController>npm list
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
reactor-nutcontroller@0.1.22305 C:\reactor\ext\NUTController
`-- node-nut@1.0.3

NutController config

  - id: nut
    implementation: NUTController
    enabled: true
    #name: Eddie UPS NUTController
    config:
      server: 22.33.44.11        # modify the IP address as needed
      port: 3493              # optional, default shown
      username: "***"      # optional, no user auth if not set
      password: "***"  # optional, must be specified if username is used

I rescued an Eaton Ellipse ups from work that come back to life with fresh batteries.

Thought it would be easy to get some kind of system status or notification (from Windows) that somehow could be picked up in Reactor or at least in HA. Oh my... what a horror

After a long time following this guide I got NUT up and running on Windows @wmarcolin (Another VM is not a resonable option here)
Monitor a UPS attached to a Windows machine

Then I added the HA integration just to se if it worked and it actually did

So now I want over the finish line, and install NUTController in Reactor.
It looked easy, but still, no luck.
This got me thinking on another possible solution. Reactor already monitors "System Memory" "Uptime" and so on, so maybe it also could monitor Powersource, Battery Level, Charging State? Then let Reactor react with its magic @toggledbits ?
For a Windows user that seems a lot easier and efficient as Windows just handle my UPS as the battery it actually is so it looked like "a laptop".

Anyway, here is were I got stuck. No clue what more to try since the Nutserver is up and running and speaks with HA.
reactor.log gives me two errors:

[latest-23196]2023-07-28T19:34:28.862Z <Structure:CRIT> TypeError: self.nut.setUsername is not a function [-]
TypeError: self.nut.setUsername is not a function
    at NUTController.start_client (c:\reactor\ext\NUTController\NUTController.js:221:22)
    at NUTController.start (c:\reactor\ext\NUTController\NUTController.js:44:14)
    at Structure.start (c:\reactor\server\lib\Structure.js:362:56)
[latest-23196]2023-07-28T19:34:28.863Z <NUTController:CRIT> TypeError: Cannot read properties of undefined (reading 'end') [-]
TypeError: Cannot read properties of undefined (reading 'end')
    at Nut.close (c:\reactor\ext\NUTController\node_modules\node-nut\node-nut.js:65:15)
    at NUTController.stop (c:\reactor\ext\NUTController\NUTController.js:53:26)
    at c:\reactor\server\lib\Structure.js:366:48
[latest-23196]2023-07-28T19:34:28.864Z <Controller:NOTICE> NUTController#nut stopping

NUTController.js:221:22 looks like this

NUTController.js:44:14

Structure.js:362:56

node-nut.js:65:15

NUTController.js:53:26

Structure.js:366:48

@toggledbits said in Update from 22240 to 22310 failed. New Install also failed. (Windows):

I built a bare-metal only build 22238; download that and try it. Follow the instructions exactly. Do not run npm audit on Windows, you'll break the node-windows package and the service will not be installed. You must use exactly the version specified in the installation instructions right now.

Yes, that fixed it!
Awesome support as always!

So it was time to update MSR (and then HA but I got stuck here)
Can't figure out what I have missed.

My installed version of MSR was 22240.
Node.js is version 16.15.1

First I tried to update, following online manual.

||Download a Reactor distribution ZIP from https://reactor.toggledbits.com/download/ and place it in the folder above your existing reactor (runtime) directory.
Stop and remove any existing Reactor service:

cd \path\to\reactor
node tools\install_reactor_windows_service.js -u .
Remove any existing package-lock.json file from your Reactor directory.

Unzip the archive file and copy its contents over the contents of your existing Reactor install directory.
From the Reactor install directory, re-install/upgrade all package dependencies:

npm install --no-save --omit dev
If you are running Reactor as a Windows service, repeat those steps above.

Restart Reactor (restart the service).
Hard-refresh all browsers that are displaying Reactor content.||

I found several (maybe it was 3) package-lock.json and I deleted all I could search in reactor folder.
Unzip the new version and replaced old existing files.

Install the reactor service again by instructions.

||In a command prompt window, running as Administrator, change directory to your Reactor install directory.
Install the node-windows package as a global package (it must be global or the service will not work, and you must install the specific version provided by the command below):

npm uninstall node-windows
npm uninstall -g node-windows
npm install -g node-windows@1.0.0-beta.6
npm link node-windows
Run the script to install:

node tools\install_reactor_windows_service.js -i .||

So this failed. Service wont start.

Tried again.

Then deleted everything exept my config folder and did a new install.
Also downloaded 22310 again, but from "latest" build instead of "stable"
When running node app.js in command promt i get some kind of error message:

c:\reactor>node app.js
Reactor latest-22310-a6da8097 app 22310 configuration from c:\reactor\config
NODE_PATH C:\reactor
[latest-22310]2022-11-23T22:18:43.030Z <app:null> Reactor build latest-22310-a6da8097 starting on v16.15.1
c:\reactor\app.js:277
log['always'](a0_0x3d42be(0x26a), BUILD_VERSION, process['version']), log['always']('Process\x20ID\x20%1\x20user/group\x20%2/%3;\x20%4;\x20platform\x20%5/%6\x20%7;\x20locale\x20%8', process['pid'], process[a0_0x3d42be(0x269)](), process[a0_0x3d42be(0x278)](), is_docker ? 'docker' : a0_0x3d42be(0x288), process[a0_0x3d42be(0x287)], process['arch'], os[a0_0x3d42be(0x263)](), sys_locale), log[a0_0x3d42be(0x28c)]('Basedir\x20%1;\x20data\x20in\x20%2', c[a0_0x3d42be(0x1f8)], c[a0_0x3d42be(0x27b)]), log[a0_0x3d42be(0x28c)](a0_0x3d42be(0x21b), process['env'][a0_0x3d42be(0x291)]);
                                                                                                                                                                                                                                 ^

TypeError: process[a0_0x3d42be(...)] is not a function
    at Object.<anonymous> (c:\reactor\app.js:277:226)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47

But I can't figure out what TypeError means?

Also, before I tried a new install, there apperd an warning when installing reactor service.

c:\reactor>npm install -g node-windows@1.0.0-beta.6
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

added 5 packages, and audited 6 packages in 3s

2 vulnerabilities (1 moderate, 1 critical)

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

Running npm audit fix --force seems to broke something, because I could not install service after that.

c:\reactor>npm audit fix --force
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm WARN using --force Recommended protections disabled.

up to date, audited 89 packages in 826ms

12 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

c:\reactor>node tools\install_reactor_windows_service.js -i .
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'node-windows'
Require stack:
- c:\reactor\tools\install_reactor_windows_service.js
←[90m    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m
←[90m    at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m
←[90m    at Module.require (node:internal/modules/cjs/loader:1005:19)←[39m
←[90m    at require (node:internal/modules/cjs/helpers:102:18)←[39m
    at Object.<anonymous> (c:\reactor\tools\install_reactor_windows_service.js:102:15)
←[90m    at Module._compile (node:internal/modules/cjs/loader:1105:14)←[39m
←[90m    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)←[39m
←[90m    at Module.load (node:internal/modules/cjs/loader:981:32)←[39m
←[90m    at Function.Module._load (node:internal/modules/cjs/loader:822:12)←[39m
←[90m    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)←[39m {
  code: ←[32m'MODULE_NOT_FOUND'←[39m,
  requireStack: [ ←[32m'c:\\reactor\\tools\\install_reactor_windows_service.js'←[39m ]
}

Some input from a Windows user.
An update button would of course be a nice to have feature, but I also agree with several other here. A "normal" update, aka don't need new dependencies, just take a short moment to install.
Were I usually stumble is when an update of dependencies are needed. That have taken me hours of search-try--error-tryagain before getting that to work sometimes.

My dream would be to have a "windows installer" for MSR, that checks dependencies, install a systemservice etc.
Over time I think that would be a safer/more stable way, with fewer user errors.

With this said, I can understand really understand that @toggledbits need to handle this "his way" to be able to support differen't enviroments (and users )

@toggledbits said in Can't upgrade package dependencies [Windows10]:

I trust the government more than I trust Windows. I'll leave it at that.

Hard choice...

@toggledbits
Any idea what could cause this?

Finally!

Tried out almost every google result I could find I found something that worked.

Repair the nodejs install from windows control panel did the trick

c:\reactor>npm install --no-save --omit dev
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

added 1 package, removed 6 packages, changed 3 packages, and audited 91 packages in 6s

13 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
npm notice
npm notice New minor version of npm available! 8.11.0 -> 8.18.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.18.0
npm notice Run npm install -g npm@8.18.0 to update!
npm notice

c:\reactor>

Preparing for an upgrade to latest msr build, and got stuck on upgrade package dependencies.
Then I remembered that this was the case last time the upgrade package dependencies was required also. After a lot of trying i gave up and did a clean install of everything. But since this happens again I would love to get this sorted out.

It might be that the manual regarding node js should be updated. Or more noob-proof? I have a vague memory that the very first install required som searching to get node js up and running.

What I have done so far.
Stop reactor service.
Delete package-lock.json
Uninstall reactor service. (command prompt with admin)

c:\reactor>node tools\install_reactor_windows_service.js -u .
Uninstalling Reactor service c:\reactor
Reactor service uninstalled.

Unzip new version.
Delete package-lock.json (again)

c:\reactor>npm install --no-save --omit dev
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'
←[90m    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m
←[90m    at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m
←[90m    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)←[39m
←[90m    at node:internal/main/run_main_module:17:47←[39m {
  code: ←[32m'MODULE_NOT_FOUND'←[39m,
  requireStack: []
}

Going wild and testing command from new installations.

c:\reactor>npm install --no-save --omit dev
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'
←[90m    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m
←[90m    at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m
←[90m    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)←[39m
←[90m    at node:internal/main/run_main_module:17:47←[39m {
  code: ←[32m'MODULE_NOT_FOUND'←[39m,
  requireStack: []
}

c:\reactor>npm install --loglevel error --no-save --omit dev
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'
←[90m    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m
←[90m    at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m
←[90m    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)←[39m
←[90m    at node:internal/main/run_main_module:17:47←[39m {
  code: ←[32m'MODULE_NOT_FOUND'←[39m,
  requireStack: []
}

What module is needed?
Were to find it?
What to do with it?

@toggledbits
OK. Not so big deal at the moment, but in future versions of Reactor Dashboard i hope for a way to set up areas/groups in Reactor instead.

A low priority question, but still a question
I have both a Vera Edge and Homeassistant connected to MSR, and all devices from my Vera is neatly grouped in MSR by my room names that are set up in Vera.

But HA devices just have one group in MSR "Ha>controller all" and not the areas I set up in HA.

Have I missed something in my config or is HA areas simply not supported in MSR?

@christian_fabre
Happy to hear that it come to use (and that myself learned a few things on the way)

Need to ask, have thougth about this since the move from Rector to MSR I think.

What is the difference between putting constraints under trigger groups, like this

Compared to this similar rule, but the time limits is under contraints instead?

I think the Constraints parts in manual is still to be done because I can only find in the chapter menu, but it is not mentioned anywhere else.

Seems to work like a charm

Started out with a few rules to let him control a Sonos in his room.
This one is for starting his favorite playlist, when it not is bedtime and that playlist isn't already playing.

Anyway, some kinds of sucess the last nights

All buttons are configured and seems to work so far.

The final reactor.yaml looks like this (just showing the first two buttons as it is just the entity name and 'property key' that differ )

event_targets:    # this section starts the event-receiving entities
        "Keyfob_Fyrkant":      # Assign an ID to your entity; each entity must have a unique ID
          name: Lukas Keyfob Fyrkant   # This is optional but recommended, so you have a friendly name
          capabilities: ['button']  # define an array of capabilities to be modified by the event 
          events:  # define an array of events that modify capability attributes on the entity
            - event:  # start of an event; each element of the events array begins this way
                event_type: zwave_js_value_notification
                data:  # optional section, if further matching to the event data is required
                  node_id: 15
                  property: "scene" # Square button
                  property_key: "001"
              response:  # begin the (required) response section for handling the event
                "button.state":  # an attribute that the event modifies.
                  from: "event.data.value"  # dot-reference expression to pull value from event message
                  map:                    # optional, map to modify value
                    KeyPressed: 'single'   # if value is value_in, it is mapped to new_value
                    KeyPressed2x: 'double'
                    KeyPressed3x: 'tripple'
                    KeyHeldDown: 'hold'
                    KeyReleased: 'release'
                "button.since":  # an attribute that the event modifies.
                  from: "event.context.id"  # dot-reference expression to pull value from event message
        "Keyfob_Ring":      # Assign an ID to your entity; each entity must have a unique ID
          name: Lukas Keyfob Ring   # This is optional but recommended, so you have a friendly name
          capabilities: ['button']  # define an array of capabilities to be modified by the event 
          events:  # define an array of events that modify capability attributes on the entity
            - event:  # start of an event; each element of the events array begins this way
                event_type: zwave_js_value_notification
                data:  # optional section, if further matching to the event data is required
                  node_id: 15
                  property: "scene" # Circle button
                  property_key: "002"
              response:  # begin the (required) response section for handling the event
                "button.state":  # an attribute that the event modifies.
                  from: "event.data.value"  # dot-reference expression to pull value from event message
                  map:                    # optional, map to modify value
                    KeyPressed: 'single'   # if value is value_in, it is mapped to new_value
                    KeyPressed2x: 'double'
                    KeyPressed3x: 'triple'
                    KeyHeldDown: 'hold'
                    KeyReleased: 'release'
                "button.since":  # an attribute that the event modifies.
                  from: "event.context.id"  # dot-reference expression to pull value from event message

A thought that crossed my mind recently, to maybe expand the functions of this little remote in the future.
Fibaro have built in a possibilty for 6 extra scenes that activates after a sequence of button presses I specify. I have not activated this yet as I don't think I really need it, but what I realised is that it probably quite easy to add a lot of differnt button sequences in MSR as long or short that I want?

Next part is to get some rules and actions set-up that can use the remote.