zwave-js / zwave-js-ui / 20848380898 / 1

19%

master: 19%

push

github

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 %.

4052 of 22025 relevant lines covered (18.4%)

1.14 hits per line