Zooz ZEN76 ON is OFF

I have a couple ZEN76, firmware 2.0.1.

The lamp is ON when the switch is OFF in home assistant. Also the LED ON when the load is OFF is also inverted.


2022-09-04T17:41:42.169Z CNTRLR [Node 028] Beginning interview - last completed stage: None
2022-09-04T17:41:42.170Z CNTRLR [Node 028] new node, doing a full interview...
2022-09-04T17:41:42.171Z CNTRLR » [Node 028] querying protocol info...
2022-09-04T17:41:42.182Z DRIVER » [REQ] [GetNodeProtocolInfo]
 payload: 0x1c
2022-09-04T17:41:42.191Z DRIVER « [RES] [GetNodeProtocolInfo]
 payload: 0xd39c01041001
2022-09-04T17:41:42.197Z CNTRLR « [Node 028] received response for protocol info:
 basic device class: Routing Slave
 generic device class: Binary Switch
 specific device class: Binary Power Switch
 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
2022-09-04T17:41:42.198Z CNTRLR [Node 028] Interview stage completed: ProtocolInfo
2022-09-04T17:41:42.200Z CNTRLR » [Node 028] querying node info...
2022-09-04T17:41:42.217Z DRIVER » [Node 028] [REQ] [RequestNodeInfo]
 payload: 0x1c
2022-09-04T17:41:42.223Z DRIVER « [RES] [RequestNodeInfo]
 payload: 0x01
2022-09-04T17:41:42.255Z DRIVER « [Node 028] [REQ] [ApplicationUpdateRequest]
 payload: 0x1c130410015e25705b858e595586725a87739f6c7a
2022-09-04T17:41:42.264Z CNTRLR « [Node 028] node info received
 supported CCs:
 · Z-Wave Plus Info
 · Binary Switch
 · Configuration
 · Central Scene
 · Association
 · Multi Channel Association
 · Association Group Information
 · Transport Service
 · Version
 · Manufacturer Specific
 · Device Reset Locally
 · Indicator
 · Powerlevel
 · Security 2
 · Supervision
 · Firmware Update Meta Data
2022-09-04T17:41:42.267Z CNTRLR [Node 028] Interview stage completed: NodeInfo
2022-09-04T17:41:42.269Z CNTRLR [Node 028] Interviewing Manufacturer Specific...
2022-09-04T17:41:42.270Z CNTRLR » [Node 028] querying manufacturer information...
2022-09-04T17:41:42.281Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 177
 └─[ManufacturerSpecificCCGet]
2022-09-04T17:41:42.288Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:42.301Z DRIVER « [REQ] [SendData]
 callback id: 177
 transmit status: OK
2022-09-04T17:41:42.315Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[ManufacturerSpecificCCReport]
 manufacturer id: 0x027a
 product type: 0x7000
 product id: 0xa006
2022-09-04T17:41:42.320Z CNTRLR « [Node 028] received response for manufacturer information:
 manufacturer: Zooz (0x027a)
 product type: 0x7000
 product id: 0xa006
2022-09-04T17:41:42.321Z CNTRLR [Node 028] Interviewing Version...
2022-09-04T17:41:42.323Z CNTRLR » [Node 028] querying the CC version for Version...
2022-09-04T17:41:42.336Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 178
 └─[VersionCCCommandClassGet]
 CC: Version
2022-09-04T17:41:42.342Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:42.357Z DRIVER « [REQ] [SendData]
 callback id: 178
 transmit status: OK
2022-09-04T17:41:42.369Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Version
 version: 3
2022-09-04T17:41:42.373Z CNTRLR [Node 028] supports CC Version (0x86) in version 3
2022-09-04T17:41:42.374Z CNTRLR » [Node 028] querying node versions...
2022-09-04T17:41:42.386Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 179
 └─[VersionCCGet]
2022-09-04T17:41:42.392Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:42.407Z DRIVER « [REQ] [SendData]
 callback id: 179
 transmit status: OK
2022-09-04T17:41:42.420Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCReport]
 library type: Enhanced Slave
 protocol version: 7.13
 firmware versions: 2.0
 hardware version: 1
2022-09-04T17:41:42.425Z CNTRLR « [Node 028] received response for node versions:
 library type: Enhanced Slave (0x03)
 protocol version: 7.13
 firmware versions: 2.0
 hardware version: 1
2022-09-04T17:41:42.426Z CNTRLR » [Node 028] querying CC versions...
2022-09-04T17:41:42.427Z CNTRLR » [Node 028] querying the CC version for Basic...
2022-09-04T17:41:42.438Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 180
 └─[VersionCCCommandClassGet]
 CC: Basic
2022-09-04T17:41:42.444Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:42.459Z DRIVER « [REQ] [SendData]
 callback id: 180
 transmit status: OK
2022-09-04T17:41:42.469Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Basic
 version: 2
2022-09-04T17:41:42.473Z CNTRLR [Node 028] supports CC Basic (0x20) in version 2
2022-09-04T17:41:42.474Z CNTRLR » [Node 028] querying the CC version for Binary Switch...
2022-09-04T17:41:42.485Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 181
 └─[VersionCCCommandClassGet]
 CC: Binary Switch
2022-09-04T17:41:42.491Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:42.505Z DRIVER « [REQ] [SendData]
 callback id: 181
 transmit status: OK
2022-09-04T17:41:42.516Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Binary Switch
 version: 2
2022-09-04T17:41:42.523Z CNTRLR [Node 028] supports CC Binary Switch (0x25) in version 2
2022-09-04T17:41:42.524Z CNTRLR [Node 028] skipping query for All Switch (0x27) because max implemented vers
 ion is 0
2022-09-04T17:41:42.524Z CNTRLR » [Node 028] querying the CC version for Z-Wave Plus Info...
2022-09-04T17:41:42.535Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 182
 └─[VersionCCCommandClassGet]
 CC: Z-Wave Plus Info
2022-09-04T17:41:42.541Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:42.556Z DRIVER « [REQ] [SendData]
 callback id: 182
 transmit status: OK
2022-09-04T17:41:42.567Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Z-Wave Plus Info
 version: 2
2022-09-04T17:41:42.571Z CNTRLR [Node 028] supports CC Z-Wave Plus Info (0x5e) in version 2
2022-09-04T17:41:42.572Z CNTRLR » [Node 028] querying the CC version for Configuration...
2022-09-04T17:41:42.585Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 183
 └─[VersionCCCommandClassGet]
 CC: Configuration
2022-09-04T17:41:42.591Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:42.606Z DRIVER « [REQ] [SendData]
 callback id: 183
 transmit status: OK
2022-09-04T17:41:42.616Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Configuration
 version: 4
2022-09-04T17:41:42.620Z CNTRLR [Node 028] supports CC Configuration (0x70) in version 4
2022-09-04T17:41:42.621Z CNTRLR » [Node 028] querying the CC version for Central Scene...
2022-09-04T17:41:42.633Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 184
 └─[VersionCCCommandClassGet]
 CC: Central Scene
2022-09-04T17:41:42.640Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:42.654Z DRIVER « [REQ] [SendData]
 callback id: 184
 transmit status: OK
2022-09-04T17:41:42.665Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Central Scene
 version: 3
2022-09-04T17:41:42.669Z CNTRLR [Node 028] supports CC Central Scene (0x5b) in version 3
2022-09-04T17:41:42.669Z CNTRLR » [Node 028] querying the CC version for Association...
2022-09-04T17:41:42.679Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 185
 └─[VersionCCCommandClassGet]
 CC: Association
2022-09-04T17:41:42.686Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:42.700Z DRIVER « [REQ] [SendData]
 callback id: 185
 transmit status: OK
2022-09-04T17:41:42.711Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Association
 version: 3
2022-09-04T17:41:42.715Z CNTRLR [Node 028] supports CC Association (0x85) in version 3
2022-09-04T17:41:42.716Z CNTRLR » [Node 028] querying the CC version for Multi Channel Association...
2022-09-04T17:41:42.726Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 186
 └─[VersionCCCommandClassGet]
 CC: Multi Channel Association
2022-09-04T17:41:42.732Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:42.749Z DRIVER « [REQ] [SendData]
 callback id: 186
 transmit status: OK
2022-09-04T17:41:42.764Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Multi Channel Association
 version: 4
2022-09-04T17:41:42.775Z CNTRLR [Node 028] supports CC Multi Channel Association (0x8e) in version 4
2022-09-04T17:41:42.779Z CNTRLR » [Node 028] querying the CC version for Association Group Information...
2022-09-04T17:41:42.803Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 187
 └─[VersionCCCommandClassGet]
 CC: Association Group Information
2022-09-04T17:41:42.825Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:42.847Z DRIVER « [REQ] [SendData]
 callback id: 187
 transmit status: OK
2022-09-04T17:41:42.867Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Association Group Information
 version: 3
2022-09-04T17:41:42.890Z CNTRLR [Node 028] supports CC Association Group Information (0x59) in version 3
2022-09-04T17:41:42.893Z CNTRLR » [Node 028] querying the CC version for Transport Service...
2022-09-04T17:41:42.919Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 188
 └─[VersionCCCommandClassGet]
 CC: Transport Service
2022-09-04T17:41:42.944Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:42.964Z DRIVER « [REQ] [SendData]
 callback id: 188
 transmit status: OK
2022-09-04T17:41:43.008Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Transport Service
 version: 2
2022-09-04T17:41:43.029Z CNTRLR [Node 028] supports CC Transport Service (0x55) in version 2
2022-09-04T17:41:43.031Z CNTRLR » [Node 028] querying the CC version for Manufacturer Specific...
2022-09-04T17:41:43.064Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 189
 └─[VersionCCCommandClassGet]
 CC: Manufacturer Specific
2022-09-04T17:41:43.083Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:43.104Z DRIVER « [REQ] [SendData]
 callback id: 189
 transmit status: OK
2022-09-04T17:41:43.136Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Manufacturer Specific
 version: 2
2022-09-04T17:41:43.167Z CNTRLR [Node 028] supports CC Manufacturer Specific (0x72) in version 2
2022-09-04T17:41:43.170Z CNTRLR [Node 028] skipping query for Device Reset Locally (0x5a) because max implem
 ented version is 1
2022-09-04T17:41:43.173Z CNTRLR » [Node 028] querying the CC version for Indicator...
2022-09-04T17:41:43.213Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 190
 └─[VersionCCCommandClassGet]
 CC: Indicator
2022-09-04T17:41:43.242Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:43.253Z DRIVER « [REQ] [SendData]
 callback id: 190
 transmit status: OK
2022-09-04T17:41:43.268Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Indicator
 version: 3
2022-09-04T17:41:43.279Z CNTRLR [Node 028] supports CC Indicator (0x87) in version 3
2022-09-04T17:41:43.282Z CNTRLR [Node 028] skipping query for Powerlevel (0x73) because max implemented vers
 ion is 1
2022-09-04T17:41:43.285Z CNTRLR [Node 028] skipping query for Security 2 (0x9f) because max implemented vers
 ion is 1
2022-09-04T17:41:43.288Z CNTRLR » [Node 028] querying the CC version for Supervision...
2022-09-04T17:41:43.311Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 191
 └─[VersionCCCommandClassGet]
 CC: Supervision
2022-09-04T17:41:43.320Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:43.333Z DRIVER « [REQ] [SendData]
 callback id: 191
 transmit status: OK
2022-09-04T17:41:43.345Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Supervision
 version: 1
2022-09-04T17:41:43.354Z CNTRLR [Node 028] supports CC Supervision (0x6c) in version 1
2022-09-04T17:41:43.356Z CNTRLR » [Node 028] querying the CC version for Firmware Update Meta Data...
2022-09-04T17:41:43.371Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 192
 └─[VersionCCCommandClassGet]
 CC: Firmware Update Meta Data
2022-09-04T17:41:43.376Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
 n 100 ms.
2022-09-04T17:41:43.379Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Supervision
 version: 1
2022-09-04T17:41:43.478Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 192
 └─[VersionCCCommandClassGet]
 CC: Firmware Update Meta Data
2022-09-04T17:41:43.484Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:43.498Z DRIVER « [REQ] [SendData]
 callback id: 192
 transmit status: OK
2022-09-04T17:41:43.509Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCommandClassReport]
 CC: Firmware Update Meta Data
 version: 5
2022-09-04T17:41:43.513Z CNTRLR [Node 028] supports CC Firmware Update Meta Data (0x7a) in version 5
2022-09-04T17:41:43.514Z CNTRLR » [Node 028] querying if Z-Wave Software Get is supported...
2022-09-04T17:41:43.523Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 193
 └─[VersionCCCapabilitiesGet]
2022-09-04T17:41:43.529Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:43.544Z DRIVER « [REQ] [SendData]
 callback id: 193
 transmit status: OK
2022-09-04T17:41:43.555Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCCapabilitiesReport]
 supports Z-Wave Software Get command: true
2022-09-04T17:41:43.559Z CNTRLR « [Node 028] Z-Wave Software Get is supported
2022-09-04T17:41:43.559Z CNTRLR » [Node 028] querying Z-Wave software versions...
2022-09-04T17:41:43.569Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 194
 └─[VersionCCZWaveSoftwareGet]
2022-09-04T17:41:43.575Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:43.589Z DRIVER « [REQ] [SendData]
 callback id: 194
 transmit status: OK
2022-09-04T17:41:43.610Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[VersionCCZWaveSoftwareReport]
 SDK version: 7.13.10
 appl. framework API version: 10.13.10
 appl. framework build number: 423
 host interface version: unused
 Z-Wave protocol version: 7.13.10
 Z-Wave protocol build number: 423
 application version: 2.0.1
 application build number: 43707
2022-09-04T17:41:43.615Z CNTRLR « [Node 028] received Z-Wave software versions
2022-09-04T17:41:43.641Z CNTRLR [Node 028] Embedded device config loaded
2022-09-04T17:41:43.646Z CNTRLR [Node 028] Interviewing Z-Wave Plus Info...
2022-09-04T17:41:43.647Z CNTRLR » [Node 028] querying Z-Wave+ information...
2022-09-04T17:41:43.657Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 195
 └─[ZWavePlusCCGet]
2022-09-04T17:41:43.663Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:43.678Z DRIVER « [REQ] [SendData]
 callback id: 195
 transmit status: OK
2022-09-04T17:41:43.691Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[ZWavePlusCCReport]
 version: 2
 node type: Node
 role type: AlwaysOnSlave
 icon (mgmt.): 0x0700
 icon (user): 0x0704
2022-09-04T17:41:43.696Z CNTRLR « [Node 028] received response for Z-Wave+ information:
 Z-Wave+ version: 2
 role type: AlwaysOnSlave
 node type: Node
 installer icon: 0x0700
 user icon: 0x0704
2022-09-04T17:41:43.698Z CNTRLR [Node 028] Interviewing Indicator...
2022-09-04T17:41:43.699Z CNTRLR » [Node 028] scanning supported indicator IDs...
2022-09-04T17:41:43.709Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 196
 └─[IndicatorCCSupportedGet]
 indicator: 0 (default)
2022-09-04T17:41:43.718Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:43.730Z DRIVER « [REQ] [SendData]
 callback id: 196
 transmit status: OK
2022-09-04T17:41:43.743Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[IndicatorCCSupportedReport]
 indicator: 0x50 (Node Identify)
 supported properties: On/Off Period: Duration, On/Off Cycle Count, On/Off 
 Period: On time
 next indicator: 0 (default)
2022-09-04T17:41:43.749Z CNTRLR « [Node 028] supported indicator IDs: 80
2022-09-04T17:41:43.750Z CNTRLR » [Node 028] requesting current indicator value (id = 0x50)...
2022-09-04T17:41:43.763Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 197
 └─[IndicatorCCGet]
 indicator: 0x50 (Node Identify)
2022-09-04T17:41:43.769Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:43.788Z DRIVER « [REQ] [SendData]
 callback id: 197
 transmit status: OK
2022-09-04T17:41:43.805Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[IndicatorCCReport]
 values:
 · indicatorId: 80
 propertyId: 3
 value: 0
 · indicatorId: 80
 propertyId: 4
 value: 0
 · indicatorId: 80
 propertyId: 5
 value: 0
2022-09-04T17:41:43.811Z CNTRLR [Node 028] Interviewing Firmware Update Meta Data...
2022-09-04T17:41:43.812Z CNTRLR » [Node 028] Querying firmware update capabilities...
2022-09-04T17:41:43.821Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 198
 └─[FirmwareUpdateMetaDataCCMetaDataGet]
2022-09-04T17:41:43.827Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:43.841Z DRIVER « [REQ] [SendData]
 callback id: 198
 transmit status: OK
2022-09-04T17:41:43.856Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[FirmwareUpdateMetaDataCCMetaDataReport]
 manufacturer id: 634
 firmware id: 40966
 checksum: 0
 firmware upgradable: true
 max fragment size: 40
 additional firmware IDs: []
 hardware version: 1
 continues to function: unknown
 supports activation: unknown
2022-09-04T17:41:43.861Z CNTRLR « [Node 028] Received firmware update capabilities:
 firmware targets: 0
 continues to function: unknown
 supports activation: unknown
2022-09-04T17:41:43.862Z CNTRLR [Node 028] Interviewing Association...
2022-09-04T17:41:43.863Z CNTRLR » [Node 028] querying number of association groups...
2022-09-04T17:41:43.873Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 199
 └─[AssociationCCSupportedGroupingsGet]
2022-09-04T17:41:43.879Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:43.893Z DRIVER « [REQ] [SendData]
 callback id: 199
 transmit status: OK
2022-09-04T17:41:43.904Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[AssociationCCSupportedGroupingsReport]
 group count: 3
2022-09-04T17:41:43.908Z CNTRLR « [Node 028] supports 3 association groups
2022-09-04T17:41:43.909Z CNTRLR » [Node 028] querying association group #1...
2022-09-04T17:41:43.920Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 200
 └─[AssociationCCGet]
 group id: 1
2022-09-04T17:41:43.926Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:43.941Z DRIVER « [REQ] [SendData]
 callback id: 200
 transmit status: OK
2022-09-04T17:41:43.954Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[AssociationCCReport]
 group id: 1
 max # of nodes: 1
 node IDs: 1
 reports to follow: 0
2022-09-04T17:41:43.958Z CNTRLR « [Node 028] received information for association group #1:
 maximum # of nodes: 1
 currently assigned nodes: 1
2022-09-04T17:41:43.959Z CNTRLR » [Node 028] querying association group #2...
2022-09-04T17:41:43.970Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 201
 └─[AssociationCCGet]
 group id: 2
2022-09-04T17:41:43.976Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:43.991Z DRIVER « [REQ] [SendData]
 callback id: 201
 transmit status: OK
2022-09-04T17:41:44.002Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[AssociationCCReport]
 group id: 2
 max # of nodes: 5
 node IDs:
 reports to follow: 0
2022-09-04T17:41:44.007Z CNTRLR « [Node 028] received information for association group #2:
 maximum # of nodes: 5
 currently assigned nodes: 
2022-09-04T17:41:44.007Z CNTRLR » [Node 028] querying association group #3...
2022-09-04T17:41:44.018Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 202
 └─[AssociationCCGet]
 group id: 3
2022-09-04T17:41:44.024Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:44.039Z DRIVER « [REQ] [SendData]
 callback id: 202
 transmit status: OK
2022-09-04T17:41:44.052Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[AssociationCCReport]
 group id: 3
 max # of nodes: 5
 node IDs:
 reports to follow: 0
2022-09-04T17:41:44.056Z CNTRLR « [Node 028] received information for association group #3:
 maximum # of nodes: 5
 currently assigned nodes: 
2022-09-04T17:41:44.057Z CNTRLR [Node 028] AssociationCC: delaying configuration of lifeline associations unti
 l after Multi Channel Association interview...
2022-09-04T17:41:44.059Z CNTRLR [Node 028] Interviewing Multi Channel Association...
2022-09-04T17:41:44.060Z CNTRLR » [Node 028] querying number of multi channel association groups...
2022-09-04T17:41:44.069Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 203
 └─[MultiChannelAssociationCCSupportedGroupingsGet]
2022-09-04T17:41:44.075Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:44.090Z DRIVER « [REQ] [SendData]
 callback id: 203
 transmit status: OK
2022-09-04T17:41:44.100Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[MultiChannelAssociationCCSupportedGroupingsReport]
 group count: 3
2022-09-04T17:41:44.104Z CNTRLR « [Node 028] supports 3 multi channel association groups
2022-09-04T17:41:44.105Z CNTRLR » [Node 028] querying multi channel association group #1...
2022-09-04T17:41:44.116Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 204
 └─[MultiChannelAssociationCCGet]
 group id: 1
2022-09-04T17:41:44.122Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:44.136Z DRIVER « [REQ] [SendData]
 callback id: 204
 transmit status: OK
2022-09-04T17:41:44.150Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[MultiChannelAssociationCCReport]
 group id: 1
 maximum # of nodes: 1
 node ids: 1
 endpoints:
2022-09-04T17:41:44.155Z CNTRLR « [Node 028] received information for multi channel association group #1:
 maximum # of nodes: 1
 currently assigned nodes: 1
 currently assigned endpoints: 
2022-09-04T17:41:44.156Z CNTRLR » [Node 028] querying multi channel association group #2...
2022-09-04T17:41:44.167Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 205
 └─[MultiChannelAssociationCCGet]
 group id: 2
2022-09-04T17:41:44.173Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:44.188Z DRIVER « [REQ] [SendData]
 callback id: 205
 transmit status: OK
2022-09-04T17:41:44.199Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[MultiChannelAssociationCCReport]
 group id: 2
 maximum # of nodes: 5
 node ids:
 endpoints:
2022-09-04T17:41:44.204Z CNTRLR « [Node 028] received information for multi channel association group #2:
 maximum # of nodes: 5
 currently assigned nodes: 
 currently assigned endpoints: 
2022-09-04T17:41:44.205Z CNTRLR » [Node 028] querying multi channel association group #3...
2022-09-04T17:41:44.216Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 206
 └─[MultiChannelAssociationCCGet]
 group id: 3
2022-09-04T17:41:44.222Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:44.237Z DRIVER « [REQ] [SendData]
 callback id: 206
 transmit status: OK
2022-09-04T17:41:44.248Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[MultiChannelAssociationCCReport]
 group id: 3
 maximum # of nodes: 5
 node ids:
 endpoints:
2022-09-04T17:41:44.253Z CNTRLR « [Node 028] received information for multi channel association group #3:
 maximum # of nodes: 5
 currently assigned nodes: 
 currently assigned endpoints: 
2022-09-04T17:41:44.254Z CNTRLR [Node 028] Checking/assigning lifeline groups: 1
 supports classic associations: true
 supports multi channel associations: true
2022-09-04T17:41:44.255Z CNTRLR [Node 028] Configuring lifeline group #1:
 group supports multi channel: true
 configured strategy: auto
 must use node association: true
 must use endpoint association: false
2022-09-04T17:41:44.258Z CNTRLR [Node 028] Lifeline group #1 is already assigned with a node association
2022-09-04T17:41:44.260Z CNTRLR [Node 028] Interviewing Association Group Information...
2022-09-04T17:41:44.261Z CNTRLR » [Node 028] Association group #1: Querying name...
2022-09-04T17:41:44.272Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 207
 └─[AssociationGroupInfoCCNameGet]
 group id: 1
2022-09-04T17:41:44.283Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:44.293Z DRIVER « [REQ] [SendData]
 callback id: 207
 transmit status: OK
2022-09-04T17:41:44.308Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
 └─[AssociationGroupInfoCCNameReport]
 group id: 1
 name: Lifeline
2022-09-04T17:41:44.312Z CNTRLR « [Node 028] Association group #1 has name "Lifeline"
2022-09-04T17:41:44.313Z CNTRLR » [Node 028] Association group #1: Querying command list...
2022-09-04T17:41:44.324Z DRIVER » [Node 028] [REQ] [SendData]
 │ transmit options: 0x25
 │ callback id: 208
 └─[AssociationGroupInfoCCCommandListGet]
 group id: 1
 allow cache: true
2022-09-04T17:41:44.330Z DRIVER « [RES] [SendData]
 was sent: true
2022-09-04T17:41:44.344Z DRIVER « [REQ] [SendData]
 callback id: 208
 transmit status: OK

I have a few Zooz ZEN76.
Looking at the settings you might have Inverted Orientation enabled [38-112-0-1] under Configuration if using the control panel for Zwave2MQTT.
LED Indicator is [38-112-0-2] which can be selected to ‘on when load is on’ or ‘on when load is off’ or ‘always on’ or ‘always off’

I am assuming that ‘lamp’ is your load on the switch.

Do you know which firmware version you have?

I tried orientation both ways, it didn’t invert on/off.

Now I’m unable to change any configuration settings. When I do, it says “the parameter has been updated”, but it’s not sticking.

Version 2.0.1 for all of them.

You might have to remove and re-interview it.

I installed a 3rd and 4th Zen76. Did a factory reset at boot, then inclusion. I was able to get one of them working normal.

On the first 2 units, I did an exclusion, factory reset, then re-inclusion. One of them came up normal, the other is still OFF when showing ON. I’ll retry the factory reset, add the rest of the devices and update here.

I have noticed that if some devices don’t seem to be working correctly, then resetting and re-adding usually fixes the issue on Z-Wave.

So far on Zigbee, I have never had an issue but I don’t have nearly as many zigbee devices either.

Update: I have 6 installed, 3 are inverted. All were installed, factory reset after boot, added to Home Assistant in identical manner.

The 3 that are acting weird are all switching CFL lamps with a photo cell. I’m thinking the photo-cell may be confusing the switch, as on the weird ones show a weird effect where the control slider kinda rubber band effect, when I set it OFF to ON, it slides to the ON, bounces back to OFF and then back to ON.

There is no mention of a minimum load for the Zen76.

I’ll retry to factory reset at night, when there will be a guaranteed load.

This issue is still in place for me.

Everything works fine, but the light switches are basically inverted. I believe it’s buggy firmware.

As a band-aid, is it possible to simply invert the logic of the switch in home assistant?

I have the exact same scenario, complete with the photocell lights. Did you ever find a solution?