Skip to content

Commit

Permalink
fix(config): disable Supervision for Zooz ZSE11 (#6990)
Browse files Browse the repository at this point in the history
  • Loading branch information
@AlCalzone
AlCalzone authored Jul 9, 2024
1 parent 889dcdb commit 2e57702
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions packages/config/config/devices/0x027a/zse11.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -133,6 +133,16 @@
]
}
],
"compat": {
"commandClasses": {
"remove": {
// The wakeup destination cannot be set using Supervision, resulting in missing wakeup reports
"Supervision": {
"endpoints": "*"
}
}
}
},
"metadata": {
"inclusion": "Put your Z-Wave hub into inclusion mode and click the Z-Wave button 3 times as quickly as possible. The LED indicator will start blinking to confirm inclusion mode and turn off once inclusion is completed. The sensor will automatically pair as a repeater if connected to USB power, no special button sequence required",
"exclusion": "1. Bring the sensor within direct range of your Z-Wave gateway (hub).\n2. Put the Z-Wave hub into exclusion mode (not sure how to do that? [email protected]).\n3. Press and release the Z-Wave button 3 times quickly.\n4. Your hub will confirm exclusion and the sensor will disappear from your controller's device list",
Expand Down

5 comments on commit 2e57702

@apella12
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't see how this is related, but I'm not getting Luminance and humidity after updating to 13.0. But device is reporting via zniff. Also Temp seems to ignore I have set to F Device is on USB power.
zui zse11 zniff 2024-07-18 122830
zui zse11 2024-07-18 122637

@meyerrj
Copy link

@meyerrj meyerrj commented on 2e57702 Jul 19, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@apella12 Same problem for me, I've lost humidity and luminescence values in the sensor reporting.
Re-interviewing the device is not restoring this information.
I also have to resend the configuration to use F for temperature, defaults to reading C after any re-interview attempts.

From the one sensor I did NOT update, these appear in the Debug Info as values:

    {
      "id": "36-49-0-Illuminance",
      "nodeId": 36,
      "toUpdate": false,
      "commandClass": 49,
      "commandClassName": "Multilevel Sensor",
      "endpoint": 0,
      "property": "Illuminance",
      "propertyName": "Illuminance",
      "type": "number",
      "readable": true,
      "writeable": false,
      "label": "Illuminance",
      "ccSpecific": {
        "sensorType": 3,
        "scale": 1
      },
      "stateless": false,
      "commandClassVersion": 5,
      "unit": "Lux",
      "list": false,
      "value": 0,
      "lastUpdate": 1719687336850,
      "newValue": 0
    },
    {
      "id": "36-49-0-Humidity",
      "nodeId": 36,
      "toUpdate": false,
      "commandClass": 49,
      "commandClassName": "Multilevel Sensor",
      "endpoint": 0,
      "property": "Humidity",
      "propertyName": "Humidity",
      "type": "number",
      "readable": true,
      "writeable": false,
      "label": "Humidity",
      "ccSpecific": {
        "sensorType": 5,
        "scale": 0
      },
      "stateless": false,
      "commandClassVersion": 5,
      "unit": "%",
      "list": false,
      "value": 57,
      "lastUpdate": 1719695929476,
      "newValue": 57
    }

@meyerrj
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update: This is fixed with Release v13.0.1. This just came through Home Assistant as an update. Patch notes noted a regression issue.

@apella12
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update. I did not have time to fully investigate and file an issue. Hoped @AlCalzone would see this. I did discover it was bigger than just this. I had a fibaro motion that stopped reporting luminance too. Suspected the multisensor class.

@AlCalzone
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct, that was broken by #6927 and fixed in v13.0.1

Please sign in to comment.