Jasco Pro Z-Wave Dimmer

Configuration Z-Wave
1

Hello,

I have a ton of these dimmers through the house (Jasco = GE in Canada) that I setup when I first installed HA with the old integrated Z-Wave system. Since then, I have upgraded HA to the latest and transitioned to ZWaveJS. I am now trying to add two more of these dimmers, but a newer model. When I use inclusion mode, it detects the device and picks it up, but doesn’t populate properly. If I use the default inclusion mode, it doesn’t work at all, but if I switch to legacy, I get a partial inclusion. It doesn’t pickup the manufacturer or model. I have try re-interviewing to no avail. I have also removed/included several times. Most of my devices are using S2. I have an Aeotec Zwave stick with the latest firmware.

I have attached a screenshot of what the device looks like and also the logs. Any help is very much appreciated!

Blockquote
Subscribed to Z-Wave JS log messages…
2025-02-13T20:51:36.040Z CNTRLR « [Node 179] Received updated node info
2025-02-13T20:51:37.038Z CNTRLR « [Node 179] received CentralScene notification {
“nodeId”: 179,
“ccId”: “Central Scene”,
“ccCommand”: “0x03”
}
2025-02-13T20:51:37.354Z CNTRLR starting exclusion process…
2025-02-13T20:51:37.362Z CNTRLR The controller is now ready to remove nodes
2025-02-13T20:51:39.907Z CNTRLR handling remove node request (status = NodeFound)
2025-02-13T20:51:40.579Z CNTRLR handling remove node request (status = RemovingSlave)
2025-02-13T20:51:40.586Z CNTRLR handling remove node request (status = Done)
2025-02-13T20:51:40.590Z CNTRLR the exclusion process was stopped
2025-02-13T20:51:40.590Z CNTRLR Node 179 was removed
2025-02-13T20:51:41.033Z CNTRLR « [Node 062] Received updated node info
2025-02-13T20:51:46.198Z CNTRLR Starting inclusion process with strategy Default…
2025-02-13T20:51:46.206Z CNTRLR The controller is now ready to add nodes
2025-02-13T20:51:48.429Z CNTRLR stopping inclusion process…
2025-02-13T20:51:48.488Z CNTRLR The inclusion process was stopped
2025-02-13T20:51:50.635Z CNTRLR Starting inclusion process with strategy Security_S0…
2025-02-13T20:51:50.643Z CNTRLR The controller is now ready to add nodes
2025-02-13T20:52:12.471Z CNTRLR stopping inclusion process…
2025-02-13T20:52:12.529Z CNTRLR The inclusion process was stopped
2025-02-13T20:52:14.780Z CNTRLR « [Node 063] Received updated node info
2025-02-13T20:52:41.312Z CNTRLR Starting inclusion process with strategy Default…
2025-02-13T20:52:41.319Z CNTRLR The controller is now ready to add nodes
2025-02-13T20:52:42.654Z CNTRLR stopping inclusion process…
2025-02-13T20:52:42.713Z CNTRLR The inclusion process was stopped
2025-02-13T20:52:44.009Z CNTRLR Starting inclusion process with strategy Security_S0…
2025-02-13T20:52:44.017Z CNTRLR The controller is now ready to add nodes
2025-02-13T20:52:47.945Z CNTRLR handling add node request (status = NodeFound)
2025-02-13T20:52:48.883Z CNTRLR handling add node request (status = AddingSlave)
2025-02-13T20:53:01.955Z CNTRLR handling add node request (status = ProtocolDone)
2025-02-13T20:53:01.956Z CNTRLR finishing inclusion process…
2025-02-13T20:53:02.018Z CNTRLR The inclusion process was stopped
2025-02-13T20:53:02.020Z CNTRLR finished adding node 180:
basic device class: Routing End Node
generic device class: Multilevel Switch
specific device class: Unused
supported CCs:
· Z-Wave Plus Info (0x5e)
· Application Status (0x22)
· Association (0x85)
· Multi Channel Association (0x8e)
· Association Group Information (0x59)
· Multilevel Switch (0x26)
· Indicator (0x87)
· Transport Service (0x55)
· Version (0x86)
· Manufacturer Specific (0x72)
· Device Reset Locally (0x5a)
· Powerlevel (0x73)
· Configuration (0x70)
· Security 2 (0x9f)
· Supervision (0x6c)
· Central Scene (0x5b)
· Firmware Update Meta Data (0x7a)
controlled CCs:
2025-02-13T20:53:02.021Z CNTRLR » [Node 180] Assigning SUC return route…
2025-02-13T20:53:02.021Z CNTRLR » [Node 180] Deleting SUC return route…
2025-02-13T20:53:05.959Z CNTRLR [Node 180] Beginning interview - last completed stage: None
2025-02-13T20:53:05.960Z CNTRLR [Node 180] new node, doing a full interview…
2025-02-13T20:53:05.960Z CNTRLR » [Node 180] querying protocol info…
2025-02-13T20:53:05.970Z CNTRLR « [Node 180] received response for protocol info:
basic device class: Routing End Node
generic device class: Multilevel Switch
specific device class: Unused
node type: End Node
is always listening: true
is frequent listening: false
can route messages: true
supports security: false
supports beaming: true
maximum data rate: 100000 kbps
protocol version: 3
2025-02-13T20:53:05.971Z CNTRLR [Node 180] Interview stage completed: ProtocolInfo
2025-02-13T20:53:05.973Z CNTRLR » [Node 180] querying node info…
2025-02-13T20:53:06.135Z CNTRLR « [Node 180] node info received
supported CCs:
· Z-Wave Plus Info
· Application Status
· Association
· Multi Channel Association
· Association Group Information
· Multilevel Switch
· Indicator
· Transport Service
· Version
· Manufacturer Specific
· Device Reset Locally
· Powerlevel
· Configuration
· Security 2
· Supervision
· Central Scene
· Firmware Update Meta Data
2025-02-13T20:53:06.136Z CNTRLR « [Node 180] node info received
supported CCs:
· Z-Wave Plus Info
· Application Status
· Association
· Multi Channel Association
· Association Group Information
· Multilevel Switch
· Indicator
· Transport Service
· Version
· Manufacturer Specific
· Device Reset Locally
· Powerlevel
· Configuration
· Security 2
· Supervision
· Central Scene
· Firmware Update Meta Data
2025-02-13T20:53:06.138Z CNTRLR [Node 180] Interview stage completed: NodeInfo
2025-02-13T20:53:06.138Z CNTRLR [Node 180] Interviewing Manufacturer Specific…
2025-02-13T20:53:06.139Z CNTRLR » [Node 180] querying manufacturer information…
2025-02-13T20:53:06.350Z CNTRLR « [Node 180] received response for manufacturer information:
manufacturer: Jasco Products (0x63)
product type: 0x4944
product id: 0x3434
2025-02-13T20:53:06.351Z CNTRLR [Node 180] Interviewing Version…
2025-02-13T20:53:06.351Z CNTRLR » [Node 180] querying the CC version for Version…
2025-02-13T20:53:06.558Z CNTRLR [Node 180] supports CC Version (0x86) in version 3
2025-02-13T20:53:06.558Z CNTRLR » [Node 180] querying node versions…
2025-02-13T20:53:06.771Z CNTRLR « [Node 180] received response for node versions:
library type: Enhanced Slave (0x03)
protocol version: 7.15
firmware versions: 1.25
hardware version: 1
2025-02-13T20:53:06.772Z CNTRLR » [Node 180] querying CC versions…
2025-02-13T20:53:06.772Z CNTRLR » [Node 180] querying the CC version for Basic…
2025-02-13T20:53:06.978Z CNTRLR [Node 180] supports CC Basic (0x20) in version 2
2025-02-13T20:53:06.979Z CNTRLR » [Node 180] querying the CC version for Z-Wave Plus Info…
2025-02-13T20:53:07.186Z CNTRLR [Node 180] supports CC Z-Wave Plus Info (0x5e) in version 2
2025-02-13T20:53:07.186Z CNTRLR [Node 180] skipping query for Application Status (0x22) because max implemen
ted version is 0
2025-02-13T20:53:07.187Z CNTRLR » [Node 180] querying the CC version for Association…
2025-02-13T20:53:07.396Z CNTRLR [Node 180] supports CC Association (0x85) in version 2
2025-02-13T20:53:07.397Z CNTRLR » [Node 180] querying the CC version for Multi Channel Association…
2025-02-13T20:53:07.606Z CNTRLR [Node 180] supports CC Multi Channel Association (0x8e) in version 3
2025-02-13T20:53:07.607Z CNTRLR » [Node 180] querying the CC version for Association Group Information…
2025-02-13T20:53:07.815Z CNTRLR [Node 180] supports CC Association Group Information (0x59) in version 3
2025-02-13T20:53:07.816Z CNTRLR » [Node 180] querying the CC version for Multilevel Switch…
2025-02-13T20:53:08.025Z CNTRLR [Node 180] supports CC Multilevel Switch (0x26) in version 4
2025-02-13T20:53:08.026Z CNTRLR » [Node 180] querying the CC version for Indicator…
2025-02-13T20:53:08.235Z CNTRLR [Node 180] supports CC Indicator (0x87) in version 3
2025-02-13T20:53:08.236Z CNTRLR » [Node 180] querying the CC version for Transport Service…
2025-02-13T20:53:08.446Z CNTRLR [Node 180] supports CC Transport Service (0x55) in version 2
2025-02-13T20:53:08.446Z CNTRLR » [Node 180] querying the CC version for Manufacturer Specific…
2025-02-13T20:53:08.661Z CNTRLR [Node 180] supports CC Manufacturer Specific (0x72) in version 2
2025-02-13T20:53:08.661Z CNTRLR » [Node 180] querying the CC version for Device Reset Locally…
2025-02-13T20:53:08.864Z CNTRLR [Node 180] supports CC Device Reset Locally (0x5a) in version 1
2025-02-13T20:53:08.865Z CNTRLR » [Node 180] querying the CC version for Powerlevel…
2025-02-13T20:53:09.076Z CNTRLR [Node 180] supports CC Powerlevel (0x73) in version 1
2025-02-13T20:53:09.076Z CNTRLR » [Node 180] querying the CC version for Configuration…
2025-02-13T20:53:09.286Z CNTRLR [Node 180] supports CC Configuration (0x70) in version 4
2025-02-13T20:53:09.287Z CNTRLR » [Node 180] querying the CC version for Security 2…
2025-02-13T20:53:09.496Z CNTRLR [Node 180] supports CC Security 2 (0x9f) in version 1
2025-02-13T20:53:09.496Z CNTRLR » [Node 180] querying the CC version for Supervision…
2025-02-13T20:53:09.706Z CNTRLR [Node 180] supports CC Supervision (0x6c) in version 1
2025-02-13T20:53:09.707Z CNTRLR » [Node 180] querying the CC version for Central Scene…
2025-02-13T20:53:09.916Z CNTRLR [Node 180] supports CC Central Scene (0x5b) in version 3
2025-02-13T20:53:09.917Z CNTRLR » [Node 180] querying the CC version for Firmware Update Meta Data…
2025-02-13T20:53:10.129Z CNTRLR [Node 180] supports CC Firmware Update Meta Data (0x7a) in version 5
2025-02-13T20:53:10.129Z CNTRLR » [Node 180] querying if Z-Wave Software Get is supported…
2025-02-13T20:53:10.335Z CNTRLR « [Node 180] Z-Wave Software Get is supported
2025-02-13T20:53:10.336Z CNTRLR » [Node 180] querying Z-Wave software versions…
2025-02-13T20:53:10.558Z CNTRLR « [Node 180] received Z-Wave software versions
2025-02-13T20:53:10.562Z CNTRLR [Node 180] No device config found
2025-02-13T20:53:10.563Z CNTRLR [Node 180] Interviewing Z-Wave Plus Info…
2025-02-13T20:53:10.563Z CNTRLR » [Node 180] querying Z-Wave+ information…
2025-02-13T20:53:10.774Z CNTRLR « [Node 180] received response for Z-Wave+ information:
Z-Wave+ version: 2
role type: AlwaysOnSlave
node type: Node
installer icon: 0x0604
user icon: 0x0600
2025-02-13T20:53:10.775Z CNTRLR [Node 180] Interviewing Indicator…
2025-02-13T20:53:10.775Z CNTRLR » [Node 180] scanning supported indicator IDs…
2025-02-13T20:53:10.977Z CNTRLR « [Node 180] supported indicator IDs: 80
2025-02-13T20:53:10.978Z CNTRLR » [Node 180] requesting current indicator value (id = 0x50)…
2025-02-13T20:53:11.195Z CNTRLR [Node 180] Interviewing Firmware Update Meta Data…
2025-02-13T20:53:11.196Z CNTRLR » [Node 180] Querying firmware update capabilities…
2025-02-13T20:53:11.411Z CNTRLR « [Node 180] Received firmware update capabilities:
firmware targets: 0
continues to function: undefined
supports activation: undefined
2025-02-13T20:53:11.412Z CNTRLR [Node 180] Interviewing Association…
2025-02-13T20:53:11.413Z CNTRLR » [Node 180] querying number of association groups…
2025-02-13T20:53:11.616Z CNTRLR « [Node 180] supports 3 association groups
2025-02-13T20:53:11.617Z CNTRLR » [Node 180] querying association group #1…
2025-02-13T20:53:11.826Z CNTRLR « [Node 180] received information for association group #1:
maximum # of nodes: 5
currently assigned nodes:
2025-02-13T20:53:11.827Z CNTRLR » [Node 180] querying association group #2…
2025-02-13T20:53:12.035Z CNTRLR « [Node 180] received information for association group #2:
maximum # of nodes: 5
currently assigned nodes:
2025-02-13T20:53:12.035Z CNTRLR » [Node 180] querying association group #3…
2025-02-13T20:53:12.246Z CNTRLR « [Node 180] received information for association group #3:
maximum # of nodes: 5
currently assigned nodes:
2025-02-13T20:53:12.246Z CNTRLR [Node 180] AssociationCC: delaying configuration of lifeline associations unti
l after Multi Channel Association interview…
2025-02-13T20:53:12.247Z CNTRLR [Node 180] Interviewing Multi Channel Association…
2025-02-13T20:53:12.247Z CNTRLR » [Node 180] querying number of multi channel association groups…
2025-02-13T20:53:12.454Z CNTRLR « [Node 180] supports 3 multi channel association groups
2025-02-13T20:53:12.455Z CNTRLR » [Node 180] querying multi channel association group #1…
2025-02-13T20:53:12.668Z CNTRLR « [Node 180] received information for multi channel association group #1:
maximum # of nodes: 5
currently assigned nodes:
currently assigned endpoints:
2025-02-13T20:53:12.669Z CNTRLR » [Node 180] querying multi channel association group #2…
2025-02-13T20:53:12.876Z CNTRLR « [Node 180] received information for multi channel association group #2:
maximum # of nodes: 5
currently assigned nodes:
currently assigned endpoints:
2025-02-13T20:53:12.877Z CNTRLR » [Node 180] querying multi channel association group #3…
2025-02-13T20:53:13.085Z CNTRLR « [Node 180] received information for multi channel association group #3:
maximum # of nodes: 5
currently assigned nodes:
currently assigned endpoints:
2025-02-13T20:53:13.086Z CNTRLR [Node 180] Checking/assigning lifeline groups: 1
supports classic associations: true
supports multi channel associations: true
2025-02-13T20:53:13.086Z CNTRLR [Node 180] Configuring lifeline group #1:
group supports multi channel: true
configured strategy: auto
must use node association: true
must use endpoint association: false
2025-02-13T20:53:13.087Z CNTRLR » [Node 180] Assigning lifeline group #1 with a node association via Association
CC…
2025-02-13T20:53:13.506Z CNTRLR [Node 180] Lifeline group #1 was assigned with a node association via Associat
ion CC
2025-02-13T20:53:13.507Z CNTRLR [Node 180] Interviewing Association Group Information…
2025-02-13T20:53:13.508Z CNTRLR » [Node 180] Association group #1: Querying name…
2025-02-13T20:53:13.720Z CNTRLR « [Node 180] Association group #1 has name “Lifeline”
2025-02-13T20:53:13.721Z CNTRLR » [Node 180] Association group #1: Querying command list…
2025-02-13T20:53:13.933Z CNTRLR » [Node 180] Association group #2: Querying name…
2025-02-13T20:53:14.160Z CNTRLR « [Node 180] Association group #2 has name “Group2 On/Off/Dim control”
2025-02-13T20:53:14.161Z CNTRLR » [Node 180] Association group #2: Querying command list…
2025-02-13T20:53:14.371Z CNTRLR » [Node 180] Association group #3: Querying name…
2025-02-13T20:53:14.600Z CNTRLR « [Node 180] Association group #3 has name “Group3 On/Off/Dim control”
2025-02-13T20:53:14.601Z CNTRLR » [Node 180] Association group #3: Querying command list…
2025-02-13T20:53:14.809Z CNTRLR » [Node 180] Association group #1: Querying info…
2025-02-13T20:53:15.018Z CNTRLR « [Node 180] Received info for association group #1:
info is dynamic: false
profile: General: Lifeline
2025-02-13T20:53:15.019Z CNTRLR » [Node 180] Association group #2: Querying info…
2025-02-13T20:53:15.232Z CNTRLR « [Node 180] Received info for association group #2:
info is dynamic: false
profile: Control: Key 01
2025-02-13T20:53:15.233Z CNTRLR » [Node 180] Association group #3: Querying info…
2025-02-13T20:53:15.450Z CNTRLR « [Node 180] Received info for association group #3:
info is dynamic: false
profile: Control: Key 02
2025-02-13T20:53:15.451Z CNTRLR [Node 180] Interviewing Multilevel Switch…
2025-02-13T20:53:15.451Z CNTRLR » [Node 180] requesting switch type…
2025-02-13T20:53:15.666Z CNTRLR « [Node 180] has switch type Down/Up
2025-02-13T20:53:15.669Z CNTRLR » [Node 180] requesting current switch state…
2025-02-13T20:53:15.877Z CNTRLR [Node 180] Interviewing Configuration…
2025-02-13T20:53:15.878Z CNTRLR » [Node 180] finding first configuration parameter…
2025-02-13T20:53:16.087Z CNTRLR » [Node 180] querying parameter #3 information…
2025-02-13T20:53:17.095Z CNTRLR « [Node 180] received information for parameter #3:
parameter name: LED Light Mode
value format: SignedInteger
value size: 1 bytes
min value: 0
max value: 3
default value: 0
is read-only: false
is advanced (UI): false
has bulk support: false
alters capabilities: false
2025-02-13T20:53:17.096Z CNTRLR » [Node 180] querying parameter #4 information…
2025-02-13T20:53:18.714Z CNTRLR « [Node 180] received information for parameter #4:
parameter name: Invert Switch
value format: SignedInteger
value size: 1 bytes
min value: 0
max value: 1
default value: 0
is read-only: false
is advanced (UI): false
has bulk support: false
alters capabilities: false
2025-02-13T20:53:18.715Z CNTRLR » [Node 180] querying parameter #5 information…
2025-02-13T20:53:20.643Z CNTRLR « [Node 180] received information for parameter #5:
parameter name: 3-Way Type
value format: SignedInteger
value size: 1 bytes
min value: 0
max value: 1
default value: 0
is read-only: false
is advanced (UI): false
has bulk support: false
alters capabilities: false
2025-02-13T20:53:20.644Z CNTRLR » [Node 180] querying parameter #16 information…
2025-02-13T20:53:22.437Z CNTRLR « [Node 180] received information for parameter #16:
parameter name: Switch Mode
value format: SignedInteger
value size: 1 bytes
min value: 0
max value: 1
default value: 0
is read-only: false
is advanced (UI): false
has bulk support: false
alters capabilities: false
2025-02-13T20:53:22.438Z CNTRLR » [Node 180] querying parameter #19 information…
2025-02-13T20:53:23.872Z CNTRLR « [Node 180] received information for parameter #19:
parameter name: Alternate Exclus io
value format: SignedInteger
value size: 1 bytes
min value: 0
max value: 1
default value: 0
is read-only: false
is advanced (UI): false
has bulk support: false
alters capabilities: false
2025-02-13T20:53:23.873Z CNTRLR » [Node 180] querying parameter #30 information…
2025-02-13T20:53:24.967Z CNTRLR « [Node 180] received information for parameter #30:
parameter name: Minimum Dim Thre hol
value format: SignedInteger
value size: 1 bytes
min value: 1
max value: 99
default value: 1
is read-only: false
is advanced (UI): false
has bulk support: false
alters capabilities: false
2025-02-13T20:53:24.968Z CNTRLR » [Node 180] querying parameter #31 information…
2025-02-13T20:53:26.519Z CNTRLR « [Node 180] received information for parameter #31:
parameter name: Maximum Brightne ss Threhol
value format: SignedInteger
value size: 1 bytes
min value: 1
max value: 99
default value: 99
is read-only: false
is advanced (UI): false
has bulk support: false
alters capabilities: false
2025-02-13T20:53:26.519Z CNTRLR » [Node 180] querying parameter #32 information…
2025-02-13T20:53:27.900Z CNTRLR « [Node 180] received information for parameter #32:
parameter name: Brightness Level
value format: SignedInteger
value size: 1 bytes
min value: 0
max value: 99
default value: 0
is read-only: false
is advanced (UI): false
has bulk support: false
alters capabilities: false
2025-02-13T20:53:27.901Z CNTRLR » [Node 180] querying parameter #34 information…
2025-02-13T20:53:28.919Z CNTRLR « [Node 180] received information for parameter #34:
parameter name: LED Light Color
value format: SignedInteger
value size: 1 bytes
min value: 1
max value: 8
default value: 5
is read-only: false
is advanced (UI): false
has bulk support: false
alters capabilities: false
2025-02-13T20:53:28.920Z CNTRLR » [Node 180] querying parameter #35 information…
2025-02-13T20:53:30.016Z CNTRLR « [Node 180] received information for parameter #35:
parameter name: LED Light Intens it
value format: SignedInteger
value size: 1 bytes
min value: 1
max value: 7
default value: 4
is read-only: false
is advanced (UI): false
has bulk support: false
alters capabilities: false
2025-02-13T20:53:30.017Z CNTRLR » [Node 180] querying parameter #36 information…
2025-02-13T20:53:31.410Z CNTRLR « [Node 180] received information for parameter #36:
parameter name: Guidelight Mode Intensit
value format: SignedInteger
value size: 1 bytes
min value: 1
max value: 7
default value: 4
is read-only: false
is advanced (UI): false
has bulk support: false
alters capabilities: false
2025-02-13T20:53:31.411Z CNTRLR » [Node 180] querying parameter #84 information…
2025-02-13T20:53:32.824Z CNTRLR « [Node 180] received information for parameter #84:
parameter name: Reset Factory De faul
value format: SignedInteger
value size: 1 bytes
min value: 0
max value: 1
default value: 0
is read-only: false
is advanced (UI): false
has bulk support: false
alters capabilities: false
2025-02-13T20:53:32.825Z CNTRLR » [Node 180] querying parameter #3 value…
2025-02-13T20:53:33.037Z CNTRLR » [Node 180] querying parameter #4 value…
2025-02-13T20:53:33.247Z CNTRLR » [Node 180] querying parameter #5 value…
2025-02-13T20:53:33.455Z CNTRLR » [Node 180] querying parameter #16 value…
2025-02-13T20:53:33.665Z CNTRLR » [Node 180] querying parameter #19 value…
2025-02-13T20:53:33.878Z CNTRLR » [Node 180] querying parameter #30 value…
2025-02-13T20:53:34.094Z CNTRLR » [Node 180] querying parameter #31 value…
2025-02-13T20:53:34.377Z CNTRLR » [Node 180] querying parameter #32 value…
2025-02-13T20:53:34.587Z CNTRLR » [Node 180] querying parameter #34 value…
2025-02-13T20:53:34.802Z CNTRLR » [Node 180] querying parameter #35 value…
2025-02-13T20:53:35.009Z CNTRLR » [Node 180] querying parameter #36 value…
2025-02-13T20:53:35.218Z CNTRLR » [Node 180] querying parameter #84 value…
2025-02-13T20:53:35.428Z CNTRLR [Node 180] Interviewing Central Scene…
2025-02-13T20:53:35.429Z CNTRLR » [Node 180] Querying supported scenes…
2025-02-13T20:53:35.637Z CNTRLR « [Node 180] received supported scenes:
# of scenes: 2
supports slow refresh: true
2025-02-13T20:53:35.638Z CNTRLR » [Node 180] Enabling slow refresh capability…
2025-02-13T20:53:35.850Z CNTRLR [Node 180] Interview stage completed: CommandClasses
2025-02-13T20:53:35.851Z CNTRLR [Node 180] Interview stage completed: OverwriteConfig
2025-02-13T20:53:35.852Z CNTRLR [Node 180] Interview completed
2025-02-13T20:53:35.852Z CNTRLR [Node 180] The node is ready to be used
2025-02-13T20:53:39.259Z CNTRLR « [Node 180] received CentralScene notification {
“nodeId”: 180,
“ccId”: “Central Scene”,
“ccCommand”: “0x03”
}

ZWave_js_Node
ZWave_js_Node2614×122 7.13 KB

2

The device is detected as product id 0x3434 from Jasco. Searching the zwavejs config browser, it appears that your product is too new to be on the list, which explains why the interview process looks incomplete. You may be able to submit an issue with their GitHub to add a config file for this new device, similar to this one.

Side note, it looks like you’re using S0 security. PSA — don’t ever use S0 security. It’s only an option for old legacy devices that require it. You should either use S2 or do not use security at all.

3

Not sure how you install zwavejs?

You can copy one of the older device zwave files to create a config for the new one. It not too complicated.

4

you can add your own custom file for this device

I had to create a file for my GE dimmer Product ID# 0x3038. I forgot I did this and discovered it when checking save location of the files. i saved using instructions at link. I modified below for your device so I believe it will work. I dont know the model number so you can change that if you like but it is not important. You need to restart zwavejs after and reinterview the device

If it works let me know and I will submit on github

{
	"manufacturer": "GE/Jasco",
	"manufacturerId": "0x0063",
	"label": "14294 / ZW3005",
	"description": "In-Wall Dimmer Switch",
	"devices": [
		{
			"productType": "0x4944",
			"productId": "0x3434"
		}
	],
	"firmwareVersion": {
		"min": "0.0",
		"max": "255.255"
	},
	"supportsZWavePlus": true,
	"associations": {
		// One entry for each association group
		"1": {
			"label": "Lifeline",
			"maxNodes": 5,
			"isLifeline": true
		},
		"2": {
			"label": "Basic - Local Load",
			"maxNodes": 5
		},
		"3": {
			"label": "Basic - Double Tap", // required
			"maxNodes": 5,
			"isLifeline": true
		}
	},
	"paramInformation": {
		"3": {
			"label": "Night Light",
			"description": "Defines the behavior of the blue LED. Default is on when switch is off.",
			"valueSize": 1,
			"minValue": 0,
			"maxValue": 2,
			"defaultValue": 0,
			"allowManualEntry": false,
			"options": [
				{
					"label": "LED on when switch is OFF",
					"value": 0
				},
				{
					"label": "LED on when switch is ON",
					"value": 1
				},
				{
					"label": "LED always off",
					"value": 2
				}
			]
		},
		"4": {
			"label": "Invert Switch",
			"description": "Invert the ON/OFF Switch State.",
			"valueSize": 1,
			"minValue": 0,
			"maxValue": 1,
			"defaultValue": 0,
			"allowManualEntry": false,
			"options": [
				{
					"label": "No",
					"value": 0
				},
				{
					"label": "Yes",
					"value": 1
				}
			]
		},
		"7": {
			"label": "Dim Rate Steps (Z-Wave Command)",
			"description": "Number of steps or levels",
			"valueSize": 1,
			"minValue": 0,
			"maxValue": 99,
			"defaultValue": 1,
			"unsigned": true
		},
		"8": {
			"label": "Dim Rate Timing (Z-Wave)",
			"description": "Timing of steps or levels",
			"valueSize": 2,
			"unit": "10ms",
			"minValue": 1,
			"maxValue": 255,
			"defaultValue": 3,
			"unsigned": true
		},
		"9": {
			"label": "Dim Rate Steps (Manual)",
			"description": "Number of steps or levels",
			"valueSize": 1,
			"minValue": 1,
			"maxValue": 99,
			"defaultValue": 1,
			"unsigned": true
		},
		"10": {
			"label": "Dim Rate Timing (Manual)",
			"description": "Timing of steps",
			"valueSize": 2,
			"unit": "10ms",
			"minValue": 1,
			"maxValue": 255,
			"defaultValue": 3,
			"unsigned": true
		},
		"11": {
			"label": "Dim Rate Steps (All-On/All-Off)",
			"description": "Number of steps or levels",
			"valueSize": 1,
			"minValue": 1,
			"maxValue": 99,
			"defaultValue": 1,
			"unsigned": true
		},
		"12": {
			"label": "Dim Rate Timing (All-On/All-Off)",
			"description": "Timing of steps or levels",
			"valueSize": 2,
			"unit": "10ms",
			"minValue": 1,
			"maxValue": 255,
			"defaultValue": 3,
			"unsigned": true
		},
		"16": {
			"label": "Switch Mode",
			"description": "Turn your dimmer into an On/Off switch with switch mode",
			"valueSize": 1,
			"minValue": 0,
			"maxValue": 1,
			"defaultValue": 0,
			"unsigned": true,
			"allowManualEntry": false,
			"options": [
				{
					"label": "Normal Operation",
					"value": 0
				},
				{
					"label": "Switch Mode",
					"value": 1
				}
			]
		}
	},
	"compat": {
		"treatBasicSetAsEvent": true
	}
}
5

I am also using the new jasco pro devices. Even though the device doesn’t have a configuration file it should still interview properly. I have no problem controlling my devices from home assistant.

6

Thanks @tmjpugh. I’m having trouble locating the folder. In the guide, it says to looks for a config folder under the store folder in the application folder. I’m running HA in a docker and I found folders called zwave_js, but there is no store. Any idea where to look?

7

The .json file for the device should be added to the zwavejs or zwavejsui folder. sorry I did not provide detail of this previously.

I run zwavejsui in docker. I have mounted a zwavejsui folder /usr/src/app/store for zwavejsui to store its files. This is standard install method for me and recommended folder to mount in zwavejsui compose example.. Inside this mounted folder, there is a “/config” folder. full path is

/usr/src/app/store/config

I have placed a folder “0x0063” inside the config folder and placed the .json file there.
full path to file for my device in zwavejsui docker container is

/usr/src/app/store/config/0x0063/ge_14294_zw3005.json

the “0x0063” folder name is correct for you I believe. Jasco and GE are same
I dont know your product model number but you should probably replace that in file name.
File group:user should match those of the config folder or zwavejs/zwavejsui will not have access.

8

FYI you don’t need sub-directories except for template files.