Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
SnowmanS

Snowman

@Snowman
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
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.
Multi-System Reactor
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
Multi-System Reactor
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
[SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor
[SOLVED] Question regarding "in" vs "contains" vs contents of the string
G
Topic thumbnail image
Multi-System Reactor
openLuup console disappeared - 500 - Internal Server Error
A
Love openLuup - it just keeps working perfectly. I started looking at trying to add a gen4 Shelly device to the Shelly plugin via L_ShellyBridge.lua. The plugin is a little uncooked (no rudeness intended), so a bit of a rabbit hole for me. All of a sudden no console pages available in either Firefox or Chrome. AltUI works perfectly and all the log files indicate no errors. openLuup still running everything works as it should - just no console pages. I possibly screwed something up but any recently changes files show no problems. The original/ backup of L_ShellyBridge.lua was reinstated but still no console. Bit stumped on this one. Not sure how to debug. Any ideas?
Plugins
Logon screen timeout
G
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen. Brave browser Brave 1.92.139 (Official Build) (arm64) Chromium: 150.0.7871.114
Multi-System Reactor
[MSR] Copy&past of actions and/or drag&drop between set/reset
therealdbT
Hey @toggledbits One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets. #1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth. Both will be appreciated, but I understand the technical challenges. Thanks!
Multi-System Reactor
Upgrade advice - upgrade from aarch64 to ARM64 image
T
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch. # Multi-System Reactor template docker-compose.yml (version 22160) # # Change the lines indicated by "DO"... # services: reactor: container_name: reactor environment: # DO change the TZ: line to set your local time zone. # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones TZ: GB # # DO NOT change this path. Your directory location is in "source" below. REACTOR_DATA_PREFIX: /var/reactor # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4) image: toggledbits/reactor:latest-aarch64 restart: "always" expose: - 8111 ports: - 8111:8111 volumes: # DO change the /home/username/reactor below to the directory you created for # your local data; DO NOT change the /var/reactor part - /home/pi/docker/reactor:/var/reactor - /etc/localtime:/etc/localtime:ro tmpfs: /tmp
Multi-System Reactor
Alexa for MSR, any interest?
MikeReadingtonM
Topic thumbnail image
Multi-System Reactor
Ezlo Paid Subscription for Vera Cloud Services
toggledbitsT
It appears that Ezlo is going to new levels of paid subscription for cloud services supporting Vera hubs. I have to congratulate them. It will soon be 8 years since Ezlo acquired Vera, and despite their purported financial and "intellectual" capital, they have to date not produced a viable full replacement for Vera. Now they are going to charge extra for services for a platform that they stopped updating years ago. If you know anyone who hasn't yet fully moved on from Captain Ahab's White Whale Chase, please remind them that my Decouple project is still up on Github to decouple a Vera Plus/Secure/Edge from Vera/Ezlo's cloud services. Veras have been said to misbehave when they can't reach the mother ship. I have also written my first new Vera plugin in... six years? more?... the AlertPushover project will send Vera hub alerts to Pushover, so you can still get messages generated by your Vera hub without paying for Ezlo's cloud service. It's crude but functional (i.e. better than nothing/worth every penny paid). These two projects won't replace the functionality of their cloud service and app for those who need those things. But any that don't, this may help bridge the gap. Hopefully these stragglers who have waited so long and been disappointed so often will get the idea that it's time to move on.
General Discussion
[RESOLVED] Telegram notification broke with latest update
3
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Phantom device, “INFO” appears
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Mode Status NULL
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] HTTP query failing after version 26177
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Question about the find function
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[Answered] OK to remove old json files?
3
Topic thumbnail image
Multi-System Reactor
Deprecation Announcement: 32-bit ARM *docker* images
toggledbitsT
If you are using the armv7l docker image, the OpenJS Foundation that publishes node is no longer producing 32-bit builds as of v24. That means the last supported LTS version of node for armv7l is v22, which will go End-of-Life in May 2027. Therefore, the Reactor armv7l image is now deprecated and will only be produced until node v22 goes EOL, and I will not publish armv7l images beyond that date. If you are running an RPi 3 or earlier with Reactor, you are on this image, and will need to upgrade hardware to a 64-bit model and use the arm64 image. If you need help getting it done, ask in this category.
Multi-System Reactor
About
Posts
67
Topics
18
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial
  • Cannot delete Global Expressions
    SnowmanS Snowman

    The new built fixed the issue. Thanks for the fast response. Much appreciated.

    Multi-System Reactor
  • Cannot delete Global Expressions
    SnowmanS Snowman

    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

    Multi-System Reactor
  • Button.Since Revisited
    SnowmanS Snowman

    @toggledbits In the MSR documentation, under Standard Capabilities, I noticed that the
    button.since attribute was deprecated as of version 22256 and the metadata is the preferred way to access the last-modified time of an attribute.

    Am I reading this right? Should I stop using it in my rules?

    Thanks

    Multi-System Reactor
  • [SOLVED]Hass websocket falsely reporting ready on boot??
    SnowmanS Snowman

    @toggledbits I have a similar issue but I do not have a wait_all_controllers: true in my engine subsection.

    I just add it I suppose ? Thanks

    This is what I have under engine.

    engine:
   # enabled - whether or not the rules engine runs. Change only when directed.
   enabled: true
   #
   # startup_wait - Time to wait for all controllers to come ready. Reactor often starts faster
   #                than most hubs, so this pause allows Reactor to wait for a tunable time. The
   #                Engine is not started until all controllers are ready or this timeout
   #                expires. See https://smarthome.community/topic/700/start-up
   startup_wait: 600000  # milliseconds, default 60000 (one minute)
   #
   # allow_shell_action - The "Shell Command" reaction action comes with some security risks, so
   #                      by default it is disabled. To enable it, set this value true.
   # allow_shell_action: true
   # allow_shell_action_substitution: true
   #
   # shell_action_timeout - The "Shell Command" action will allow the running command to run for
   #                        up to this many milliseconds before it terminates it (to prevent run-
   #                        away processes). The default is 30000 (milliseconds, 30 seconds).
   #shell_action_timeout: 30000
   #
   # monitored_entities - if you can't figure out what is changing an entity,
   #                      (not the data, but the physical device, like a light
   #                      that is being turned on or off at an unexpected time),
   #                      you can add it to this list and the logs will post
   #                      a message whenever an action is performed on the
   #                      device (no log level changes are needed, the message
   #                      is unconditional).
   # monitored_entities:
   #   - vera>device_XXX
    Multi-System Reactor
  • Reactor-Editor / Reactor-ui-Status Errors
    SnowmanS Snowman

    @toggledbits Below, the error and a screenshot while creating a new Global Expression, named "test". Hoping this helps answer your questions.

    As soon as I am done typing "test" and clicking in the field to add my formula, the error pops-up and will continue popping-up three times by the time it saved the changes. The error will also pop-up when I delete the expression and will pop-up a second time by the time it saved the changes.

    It did not happen on the first use of the tab/function. It took a few tries before I could re-produce the error. It does resolve itself after a page refresh.

    @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91
makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68
each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35
@http://192.168.0.13:8111/client/MessageBus.js:98:44
forEach@[native code]
@http://192.168.0.13:8111/client/MessageBus.js:95:54
@http://192.168.0.13:8111/client/MessageBus.js:106:44
@http://192.168.0.13:8111/client/Observable.js:78:28
signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:21
signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:29
reindexExpressions@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:32
@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:608:40
dispatch@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:40040

    Reactor - Global Expressions.jpg

    Multi-System Reactor
  • Reactor-Editor / Reactor-ui-Status Errors
    SnowmanS Snowman

    @toggledbits These errors are on the UI. Not from the logs. They are not preventing me from doing any work.

    For example, I'll go to Expressions, click the Add Expression, and when I click the Save Changes button, that is when these errors pop-up.

    Same goes with creating or updating a rule.

    I'll post a screenshot next time I see one.

    I'll try the Clear local storage suggestion and will let you know.

    Multi-System Reactor
  • Reactor-Editor / Reactor-ui-Status Errors
    SnowmanS Snowman

    @toggledbits I understand that you do not perform testing on Mac computers but thought I'd share the following with you in case something can be done.

    I started seeing these errors with version 24302. I thought that upgrading to 24343 would have fixed the issue but unfortunately not. I either have to close the browser or clear the cache for the errors to stop popping-up but they slowly come back.

    I see these errors on the following browsers:

    • Safari 16.6.1 on macOS Big Sur
    • Safari 18.1.1 on MacOS Sonoma
    • DuckDuckGo 1.118.0 on macOS Big Sur and Sonoma
    • Firefox 133.0.3 on macOS Big Sur
    • Chrome 131.0.6778 on macOS Big Sur

    Here are the errors

    Safari while creating/updating an expression

    @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91
makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68
each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35
@http://192.168.0.13:8111/client/MessageBus.js:98:44
forEach@[native code]
@http://192.168.0.13:8111/client/MessageBus.js:95:54
@http://192.168.0.13:8111/client/MessageBus.js:106:44
@http://192.168.0.13:8111/client/Observable.js:78:28
signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:21
signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:29
reindexExpressions@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:32
@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:608:40
dispatch@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:40040

    DuckDuckGo while clicking on status

    http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:789:44
asyncFunctionResume@[native code]
saveGridLayout@[native code]
dispatchEvent@[native code]
_triggerEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1401:30
_triggerAddEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1383:31
makeWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:968:30
addWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:388:24
placeWidgetAdder@http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:183:44

    Firefox while updating a rule

    @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91
makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68
each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35
@http://192.168.0.13:8111/client/MessageBus.js:98:44
forEach@[native code]
@http://192.168.0.13:8111/client/MessageBus.js:95:54
@http://192.168.0.13:8111/client/MessageBus.js:106:44
@http://192.168.0.13:8111/client/Observable.js:78:28
notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:82:21
notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:47:26
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1460:39
forEach@[native code]
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1459:58

    Chrome while creating/updating an expression

    TypeError: Cannot read properties of undefined (reading 'getEditor')
    at RuleEditor.makeExprMenu (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:1788:86)
    at Object.handler (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:2174:54)
    at http://192.168.0.13:8111/client/MessageBus.js:98:44
    at Array.forEach (<anonymous>)
    at MessageBus._sendToBus (http://192.168.0.13:8111/client/MessageBus.js:95:54)
    at MessageBus.send (http://192.168.0.13:8111/client/MessageBus.js:106:44)
    at ExpressionEditor.publish (http://192.168.0.13:8111/client/Observable.js:78:28)
    at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:14)
    at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:15)
    at ExpressionEditor.reindexExpressions (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:18)
``
    Multi-System Reactor
  • ZWaveJSController - Warning/Error Traceback - Registering action set volume for Aeotec Siren 6 (ZW164)
    SnowmanS Snowman

    @toggledbits Since I have upgraded ZWaveJSController to 24293 from 24257 I am seeing entries related to registering action set_volume, but action is not defined by the capability 143 every time I restart Reactor.

    The Siren seems to be doing what it is supposed to do. The volume levels are fine. Should I worry about it?

    Reactor version 24302
    ZWaveJSController version 24293
    Z-Wave JS UI version 9.27.4
    zwave-js version 14.3.4

    [latest-24302]2024-11-22T02:10:32.852Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 0 (entity "143-0")
[latest-24302]2024-11-22T02:10:32.854Z <Entity:WARN> Entity#zwavejs>143-1 registering action set_volume, but action is not defined by the capability
[latest-24302]2024-11-22T02:10:32.855Z <Entity:CRIT> Error: Traceback [-]
Error: Traceback
    at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288)
    at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112)
    at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84)
    at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38)
    at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[latest-24302]2024-11-22T02:10:32.859Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 1 (entity "143-1")
[latest-24302]2024-11-22T02:10:32.860Z <Entity:WARN> Entity#zwavejs>143-2 registering action set_volume, but action is not defined by the capability
[latest-24302]2024-11-22T02:10:32.861Z <Entity:CRIT> Error: Traceback [-]
Error: Traceback
    at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288)
    at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112)
    at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84)
    at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38)
    at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[latest-24302]2024-11-22T02:10:32.864Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 2 (entity "143-2")
[latest-24302]2024-11-22T02:10:32.866Z <Entity:WARN> Entity#zwavejs>143-3 registering action set_volume, but action is not defined by the capability
[latest-24302]2024-11-22T02:10:32.866Z <Entity:CRIT> Error: Traceback [-]
Error: Traceback
    at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288)
    at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112)
    at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84)
    at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38)
    at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[latest-24302]2024-11-22T02:10:32.870Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 3 (entity "143-3")
[latest-24302]2024-11-22T02:10:32.871Z <Entity:WARN> Entity#zwavejs>143-4 registering action set_volume, but action is not defined by the capability
[latest-24302]2024-11-22T02:10:32.872Z <Entity:CRIT> Error: Traceback [-]
Error: Traceback
    at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288)
    at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112)
    at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84)
    at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38)
    at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[latest-24302]2024-11-22T02:10:32.876Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 4 (entity "143-4")
[latest-24302]2024-11-22T02:10:32.878Z <Entity:WARN> Entity#zwavejs>143-5 registering action set_volume, but action is not defined by the capability
[latest-24302]2024-11-22T02:10:32.878Z <Entity:CRIT> Error: Traceback [-]
Error: Traceback
    at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288)
    at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112)
    at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84)
    at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38)
    at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[latest-24302]2024-11-22T02:10:32.881Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 5 (entity "143-5")
[latest-24302]2024-11-22T02:10:32.883Z <Entity:WARN> Entity#zwavejs>143-6 registering action set_volume, but action is not defined by the capability
[latest-24302]2024-11-22T02:10:32.884Z <Entity:CRIT> Error: Traceback [-]
Error: Traceback
    at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288)
    at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112)
    at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84)
    at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38)
    at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[latest-24302]2024-11-22T02:10:32.887Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 6 (entity "143-6")
[latest-24302]2024-11-22T02:10:32.888Z <Entity:WARN> Entity#zwavejs>143-7 registering action set_volume, but action is not defined by the capability
[latest-24302]2024-11-22T02:10:32.889Z <Entity:CRIT> Error: Traceback [-]
Error: Traceback
    at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288)
    at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112)
    at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84)
    at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38)
    at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[latest-24302]2024-11-22T02:10:32.892Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 7 (entity "143-7")
[latest-24302]2024-11-22T02:10:32.893Z <Entity:WARN> Entity#zwavejs>143-8 registering action set_volume, but action is not defined by the capability
[latest-24302]2024-11-22T02:10:32.894Z <Entity:CRIT> Error: Traceback [-]
Error: Traceback
    at Entity.registerAction (/opt/reactor/server/lib/Entity.js:703:288)
    at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1689:112)
    at ZWaveJSController._register_nodes (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1401:84)
    at ZWaveJSController._process_init_data (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:844:38)
    at /var/reactor/ext/ZWaveJSController/ZWaveJSController.js:774:39
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[latest-24302]2024-11-22T02:10:32.896Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 143 endpoint 8 (entity "143-8")
    Multi-System Reactor
  • Unusual zwavejs entity naming convention
    SnowmanS Snowman

    @toggledbits It appears the ZIP file you provided me with to fix the TILT-ZWAVE2.5-ECO tilt_sensor.state issue also fixed this topic. I do not see the unusual entity names. Thanks

    image.png

    image.png

    Multi-System Reactor
  • TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL
    SnowmanS Snowman

    @toggledbits The ZIP file fixed the issue. The tilt_sensor.state working as expected. Thanks

    door_sensor.state=true
tamper.state=true
tilt_sensor.state=true
    Multi-System Reactor
  • TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL
    SnowmanS Snowman

    @toggledbits I now have the requested log file.

    Multi-System Reactor
  • TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL
    SnowmanS Snowman

    I did open and close the garage door after updating Reactor. More than once. I even removed the battery to see if it would make a difference.

    I am looking at the Notification values under ZWaveJS UI ans can see that the Window/door state do toggle between TRUE/FALSE when the door opens and closes. Nothing unusual here.

    Looking at Binary Sensor values, I am seing this though. Makes sense?

    When the garage door Opens
    1de1d60d-615b-4d3d-b400-b9e101c8daac-image.png

    When the garage door Closes
    69844462-27a1-482c-bd1e-59419f09d348-image.png

    Multi-System Reactor
  • Unusual zwavejs entity naming convention
    SnowmanS Snowman

    @toggledbits I have noticed after upgrading both Reactor and ZWaveJSController to version 24257 that two of my devices/entities, TILT-ZWAVE2.5-ECO and Zooz ZSE18, had their entity re-named in an unusual way and also appears to be duplicated.

    Reactor version 24257
    ZWaveJSController version 24257
    Z-Wave JS UI version 9.18.1
    zwave-js version 13.2.0

    Vestibule Motion Sensor State attributes/partial screenshot of entities it created. All entities have the same attributes.

    motion_sensor.state=true
x_zwave_values.Notification_Home_Security_Motion_sensor_status=8
zwave_device.capabilities=[113]
zwave_device.endpoint=0
zwave_device.failed=null
zwave_device.manufacturer_info=null
zwave_device.node_id=23
zwave_device.valueId=[113,"Notification","Home Security","Home Security","Motion sensor status","Motion sensor status"]
zwave_device.version_info=null

    Zooz ZSE18 Motion Sensor.jpg

    Tilt Sensor Door State and Tilt Sensor Door State Simple attributes/partial screenshot of entities it created. All entities have similar attributes with exception of x_zwave_values.Notification_Access_Control_Door_State = 22 or 23.

    tilt_sensor.state=true
x_zwave_values.Notification_Access_Control_Door_state=22
zwave_device.capabilities=[113]
zwave_device.endpoint=0
zwave_device.failed=null
zwave_device.manufacturer_info=null
zwave_device.node_id=24
zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"]
zwave_device.version_info=null

    tilt_sensor.state=true
x_zwave_values.Notification_Access_Control_Door_state_simple=22
zwave_device.capabilities=[113]
zwave_device.endpoint=0
zwave_device.failed=null
zwave_device.manufacturer_info=null
zwave_device.node_id=24
zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"]
zwave_device.version_info=null

    tilt_sensor.state=false
x_zwave_values.Notification_Access_Control_Door_state=23
zwave_device.capabilities=[113]
zwave_device.endpoint=0
zwave_device.failed=null
zwave_device.manufacturer_info=null
zwave_device.node_id=24
zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"]
zwave_device.version_info=null

    tilt_sensor.state=false
x_zwave_values.Notification_Access_Control_Door_state_simple=23
zwave_device.capabilities=[113]
zwave_device.endpoint=0
zwave_device.failed=null
zwave_device.manufacturer_info=null
zwave_device.node_id=24
zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"]
zwave_device.version_info=null

    TILT-ZWAVE2.5-ECO.jpg

    Multi-System Reactor
  • TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL
    SnowmanS Snowman

    @toggledbits I appears the tilt_sensor.state = false is back again after I upgraded both Reactor and ZWaveJSController to version 24257. It was working fine with ZWaveJSController version 24242.

    I can certainly stop using this entity and use the door_sensor.state instead.

    I did check the latest changes for zwave-js 13.2.0 and did not see any thing that may have been introduced causing this.

    I have copied, below, the attributes of the tilt sensor in hopes it can help.

    Thanks in advance.

    Reactor version 24257
    ZWaveJSController version 24257
    Z-Wave JS UI version 9.18.1
    zwave-js version 13.2.0

    battery_maintenance.charging=0
battery_maintenance.rechargeable=0
battery_maintenance.replace=false
battery_maintenance.state="normal"
battery_power.level=1
battery_power.since=null
door_sensor.state=true
tamper.state=true
tilt_sensor.state=false
x_debug.dt={"entity_class":"Binary Sensor","match":"deviceClass.generic.key=7","description":"Z-Wave Plus Tilt Sensor","default_name":"Tilt Sensor","model":"TILTZWAVE2.5-ECO","capabilities":["tilt_sensor"],"primary_attribute":"tilt_sensor.state","values":[{"valueId":"32:currentValue:","capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}},{"match":{"endpoint":0,"commandClass":48,"metadata.ccSpecific.sensorType":255},"capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}},{"match":{"endpoint":0,"commandClass":113,"metadata.ccSpecific.notificationType":6},"capabilities":{"tilt_sensor":{"attributes":{"state":{"expr":"value === 22"}}}}}],"manufacturerId":330,"productType":4,"productId":3}
x_zwave_values.Battery_isLow=false
x_zwave_values.Battery_level=100
x_zwave_values.Binary_Sensor_Any=false
x_zwave_values.Binary_Sensor_Door_Window=true
x_zwave_values.Configuration_Basic_Sets_for_Association_Group_2=0
x_zwave_values.Configuration_Send_Reports=0
x_zwave_values.Manufacturer_Specific_manufacturerId=330
x_zwave_values.Manufacturer_Specific_productId=3
x_zwave_values.Manufacturer_Specific_productType=4
x_zwave_values.Notification_Access_Control_Door_state=22
x_zwave_values.Notification_Access_Control_Door_state_simple=22
x_zwave_values.Notification_Home_Security_Cover_status=3
x_zwave_values.Notification_Power_Management_Battery_maintenance_status=0
x_zwave_values.Notification_UNKNOWN_0x46=23
x_zwave_values.Notification_alarmLevel=0
x_zwave_values.Notification_alarmType=0
x_zwave_values.Version_firmwareVersions=["10.1"]
x_zwave_values.Version_hardwareVersion=2
x_zwave_values.Version_libraryType=6
x_zwave_values.Version_protocolVersion="4.5"
x_zwave_values.Wake_Up_controllerNodeId=1
x_zwave_values.Wake_Up_wakeUpInterval=14400
zwave_device.capabilities=[48,112,113,114,128,132,134]
zwave_device.endpoint=0
zwave_device.failed=false
zwave_device.generic_class="Notification Sensor"
zwave_device.impl_sig="24256:1:24192:1"
zwave_device.is_beaming=true
zwave_device.is_listening=false
zwave_device.is_routing=true
zwave_device.is_secure=false
zwave_device.last_wakeup=1726513928400
zwave_device.manufacturer_info=[330,4,3]
zwave_device.max_data_rate=100000
zwave_device.node_id=24
zwave_device.specific_class="Notification Sensor"
zwave_device.status=1
zwave_device.status_text="asleep"
zwave_device.version_info=[4,"10.1"]
zwave_device.wakeup_interval=14400
    Multi-System Reactor
  • How to reference a local expression inside a Shell Command
    SnowmanS Snowman

    @toggledbits It never crossed my mind to use HTTP. I'll give it a try.

    Multi-System Reactor reactor
  • How to reference a local expression inside a Shell Command
    SnowmanS Snowman

    Referencing an expression inside a reaction is in the form of ${{ expression }}. When referenced inside my shell command to set the watering delay duration for my Rachio sprinkler system, it just does not work.

    If I enter "86400" instead of referencing the expression lWateringDelayDuration, it works. Either I am doing something wrong or referencing an expression inside a shell command is not supported.

    Reactor version: 24212

    Local Expression
    lWateringDelayDuration =

    WDD = getEntity( "hass>input_number_h_watering_delay_duration" ).attributes.value_sensor.value,

if WDD == 0 then 0
  elif WDD == 1 then 86400
  elif WDD == 2 then 172800
  elif WDD == 3 then 259200
  elif WDD == 4 then 345600
endif

    Setting Reaction using Shell command

    curl -X PUT -H "Content-Type: application/json" -H "Authorization: Bearer xxxxxxxxxx -d '{ "id" : "xxxxxxxxxx", "duration" : ${{ lWateringDelayDuration}} }' https://api.rach.io/1/public/device/rain_delay

    Thanks in advance

    Multi-System Reactor reactor
  • TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL
    SnowmanS Snowman

    @toggledbits That fixed it. Thank you sir.

    battery_maintenance.charging=null
    battery_maintenance.rechargeable=false
    battery_maintenance.replace=false
    battery_maintenance.state="normal"
    battery_power.level=1
    battery_power.since=1720778246637
    door_sensor.state=true
    power_source.source=null
    tamper.state=true
    tilt_sensor.state=true

    Multi-System Reactor
  • TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL
    SnowmanS Snowman

    @toggledbits I just noticed that the tilt_sensor.state = false now and no longer can be used in my rule. I have to use door_sensor.state instead.

    I cannot tell when the issue started and not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.

    Thanks in advance.

    Reactor version 24190
    ZWaveJSController version 23326
    Z-Wave JS UI version 9.14.5
    zwave-js version 12.12.3

    battery_maintenance.charging=null
    battery_maintenance.rechargeable=false
    battery_maintenance.replace=false
    battery_maintenance.state=null
    battery_power.level=1
    battery_power.since=1720636775292
    door_sensor.state=true
    power_source.source=null
    tamper.state=true
    tilt_sensor.state=false
    x_debug.dt={"entity_class":"Binary Sensor","match":"deviceClass.generic.key=7","description":"Z-Wave Plus Tilt Sensor","default_name":"Tilt Sensor","model":"TILTZWAVE2.5-ECO","capabilities":["tilt_sensor"],"primary_attribute":"tilt_sensor.state","values":[{"valueId":"32:currentValue:","capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}},{"match":{"endpoint":0,"commandClass":48,"metadata.ccSpecific.sensorType":255},"capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}}],"manufacturerId":330,"productType":4,"productId":3}
    x_zwave_values.Battery_isLow=false
    x_zwave_values.Battery_level=100
    x_zwave_values.Binary_Sensor_Any=false
    x_zwave_values.Binary_Sensor_Door_Window=true
    x_zwave_values.Configuration_Basic_Sets_for_Association_Group_2=0
    x_zwave_values.Configuration_Send_Reports=0
    x_zwave_values.Manufacturer_Specific_manufacturerId=330
    x_zwave_values.Manufacturer_Specific_productId=3
    x_zwave_values.Manufacturer_Specific_productType=4
    x_zwave_values.Notification_Access_Control_Door_state=22
    x_zwave_values.Notification_Access_Control_Door_state_simple=22
    x_zwave_values.Notification_Home_Security_Cover_status=3
    x_zwave_values.Notification_Power_Management_Battery_maintenance_status=0
    x_zwave_values.Notification_UNKNOWN_0x46=23
    x_zwave_values.Notification_alarmLevel=0
    x_zwave_values.Notification_alarmType=0
    x_zwave_values.Version_firmwareVersions=["10.1"]
    x_zwave_values.Version_hardwareVersion=2
    x_zwave_values.Version_libraryType=6
    x_zwave_values.Version_protocolVersion="4.5"
    x_zwave_values.Wake_Up_controllerNodeId=1
    x_zwave_values.Wake_Up_wakeUpInterval=14400
    zwave_device.capabilities=[48,112,113,114,128,132,134]
    zwave_device.endpoint=0
    zwave_device.failed=false
    zwave_device.generic_class="Notification Sensor"
    zwave_device.impl_sig="23326:1:23318:2"
    zwave_device.is_beaming=false
    zwave_device.is_listening=false
    zwave_device.is_routing=true
    zwave_device.is_secure=false
    zwave_device.last_wakeup=1720636775220
    zwave_device.manufacturer_info=[330,4,3]
    zwave_device.max_data_rate=null
    zwave_device.node_id=24
    zwave_device.specific_class="Notification Sensor"
    zwave_device.status=1
    zwave_device.status_text="asleep"
    zwave_device.version_info=[null,"10.1"]
    zwave_device.wakeup_interval=14400

    Multi-System Reactor
  • Smart plugs showing battery maintenance capability
    SnowmanS Snowman

    @toggledbits Got it. Will show all attributes next time. Thanks

    Multi-System Reactor
  • Smart plugs showing battery maintenance capability
    SnowmanS Snowman

    @toggledbits Any reasons that might escape me why there are battery_maintenance attributes for the Zooz (ZEN04), Aeotec (ZWA023) and Dome (DMOF1) smart plugs (and probably other smart plugs)?

    Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes in question in hopes it can help.

    Thanks in advance.

    Reactor: 23344
    ZWaveJSController: 9.6.0.ec8995c
    zwave-js: 12.4.1
    home id: 3589098709
    home hex: 0xd5ed4cd5

    PS I could copy all attributes but there are too many to be listed in this thread.

    Attributes

    battery_maintenance.charging=null
battery_maintenance.rechargeable=false
battery_maintenance.replace=false
battery_maintenance.state=null
    Multi-System Reactor
  • Login
  • Don't have an account? Register
  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved