-
Notifications
You must be signed in to change notification settings - Fork 466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rolling beta to production #1668
Conversation
Adds a new certified preference 'forceStateChange' that allows users to select whether they want their virtual device events to always be a state change or not.
* Matter Sensor: add new device Heiman smoke sensor * Update device label
* Matter Sensor: Add HEIMAN Smart CO sensor fingerprint * Update device label * Update profile to be "co-comeas" instead of "co" --------- Co-authored-by: Alissa Dornbos <[email protected]>
Co-authored-by: Alissa Dornbos <[email protected]>
Drivers in this state would already be nonfunctional, but we want to avoid chewing up resources with a hot crash loop.
`utils.determine_device_type` will more gracefully degrade than querying the device type field directly, making it less troublesome in cases where datastore loss has occurred and the field no longer exists.
…crash-on-lost-api-key
* add supportedAlarmValues * add remote unlock event by Homekit or RF447 * fix TC and add nil check
* new-devices-shelly-switch * Added id: 1120/2/143 * Added 1120/2/142 * Removing two fingerprints due to incorrect profile assignments. Product IDs: 0x0083 and 0x008E were removed. * switch to parent/child * fixup * Adding back in "Wave 1" and "Wave 1 Mini" Both of these devices are single component, and are believed to be best fist to the switch-binary profile * make the number of children explicit * transpose product type and product id * Revert "transpose product type and product id" This reverts commit 5b7f211. * transpose correctly * update tests for native handlers --------- Co-authored-by: Steven Green <[email protected]>
Rolling up main to beta
When setting the code at index 0 for yale locks, the MASTER_CODE user type should be sent.
…_code Yale Zigbee Locks: Use MASTER_CODE user type
CHAD-14071 Zigbee: Add generic fingerprint for ZLL color temp light
Initial Matter 1.3 Device Type Support --------- Co-authored-by: Nick DeBoom <[email protected]> Co-authored-by: Hunsup Jung <[email protected]>
Signed-off-by: WangShao <[email protected]>
* New-devices-letianpai-three-switches * Update Device Labels There was feedback provided from the partner that they wanted updated Device Labels, so that feedback is being incorporated in this commit. * Fixing Brand Name Spelling Error
CHAD-13777 Allow virtual device events to not always be a state change
Sort endpoints before initializing switch
Rolling Main to Beta
Cherry pick to beta
Duplicate profile check: Warning - duplicate profiles detected. |
Test Results 63 files 395 suites 0s ⏱️ Results for commit e262085. |
aqara-lock_coverage.xml
matter-appliance_coverage.xml
matter-evse_coverage.xml
matter-lock_coverage.xml
matter-sensor_coverage.xml
matter-switch_coverage.xml
virtual-switch_coverage.xml
zigbee-lock_coverage.xml
zigbee-switch_coverage.xml
Minimum allowed coverage is Generated by 🐒 cobertura-action against e262085 |
No description provided.