zwave-js / zwave-js-ui
20%

DEFAULT BRANCH: master
Repo Added
Token mus2r2yYRz7XGYVesP5DKNJXitjqkrcyd regen
Build 2362 Last
Files 69
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH master
branch: master
CHANGE BRANCH
x
Sync Branches

coverage: 19.521% (-0.01%) from 19.532%
20848380898

push

github

web-flow 
feat: add bypass option for association restrictions (#4512)

Z-Wave associations are currently blocked when certain compatibility
checks fail, including security class mismatches and unsupported command
classes. This prevents legitimate use cases where devices can work
around these restrictions (e.g., Fibaro FGKF-601 supports
per-association security mode configuration via parameter 29).

## Changes

### Backend (`api/lib/ZwaveClient.ts`)
- `addAssociations` now accepts `{ force: boolean }` option to bypass
association checks
- Logs warnings when associations are force-created
- Leverages upstream zwave-js controller support for forced associations

### Frontend (`src/components/dialogs/DialogAssociation.vue`)
- Adds "I know what I'm doing - bypass this check" checkbox for
bypassable errors
- Checkbox appears for these association check failures:
- `Forbidden_SecurityClassMismatch` - Devices have different security
classes
- `Forbidden_DestinationSecurityClassNotGranted` - Source node lacks
target's security class
- `Forbidden_NoSupportedCCs` - Target doesn't support source's command
classes
- Uses enum-based error detection (`canForceAssociation` computed
property)
- Enables ADD button when bypass is explicitly checked

### Frontend (`src/components/nodes-table/AssociationGroups.vue`)
- Passes `force` parameter through to backend API call

## UI Behavior

When attempting to create an association that fails compatibility
checks:

**Before:**
<img
src="https://github.com/user-attachments/assets/b85245c3-0884-4cbd-a692-e870e4a3dee2">

**After:**
A checkbox appears below the error message allowing expert users to
bypass the restriction with an explicit acknowledgment.

## Example

```javascript
// Backend API call with force option
await this.app.apiRequest('addAssociations', [
  sourceAddress,
  groupId,
  [targetAddress],
  { force: true }  // Bypass association checks
])
```

The upstream `Driver.controller.addAssociations()` method already
supports ... (continued)

334 of 443 branches covered (75.4%)

Branch coverage included in aggregate %.

0 of 19 new or added lines in 1 file covered. (0.0%)

4052 of 22025 relevant lines covered (18.4%)

1.14 hits per line

Relevant lines Covered
22025 RELEVANT LINES 4052 COVERED LINES
1.14 HITS PER LINE
Source Files on master

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
20848380898 master feat: add bypass option for association restrictions (#4512) Z-Wave associations are currently blocked when certain compatibility checks fail, including security class mismatches and unsupported command classes. This prevents legitimate use cases... push web-flow github
19.52
20779326840 master fix(markdownlint): ensure MD059 rule is explicitly set to false push robertsLando github
19.53
20394770530 master docs: update changelog formatting and correct links for version 11.9.0 push robertsLando github
19.53
20392278315 master Release 11.9.1 push zwave-js-bot github
19.53
20392260265 master feat: bump @release-it/conventional-changelog@10.0.4 (#4499) push web-flow github
19.53
20334720751 master fix: npm release persisted "update available" popup Fixes #4489 push robertsLando github
19.53
20330409806 master feat: bump zwave-js@15.18.0 push robertsLando github
19.53
20296410319 master Release 11.9.0 push zwave-js-bot github
19.53
20295471086 master fix(ui): ui settings not persisted on save Fixes #4333 push robertsLando github
19.53
20237632280 master fix: add null checks for metaThemeColor attributes in base store Fixes #4497 push robertsLando github
19.53
See All Builds (2002)

Badge your Repo: zwave-js-ui

We detected this repo isn’t badged! Grab the embed code to the right, add it to your repo to show off your code coverage, and when the badge is live hit the refresh button to remove this message.
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

Refresh