-
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 up beta to production #1218
Conversation
Consolidates the timer logic used to check up on changing window shades into the sub-driver. Also uses a default response success from the device to indicate that the shade is moving. A subsequent poll should change the status to a stationary one if no updates are received within 30s.
BUG2-521 Rework yoolax window shade driver
Users reported higher battery consumption with edge drivers and a disparity was noted between DTH and driver cluster configurations. A forthcoming change in the lua libraries will change the defaults, but this change should significantly improve the situation for most users in the meantime with a simple refresh. Changes the IAS Zone reporting configuration to use the device defaults and changes temperature reporting to a max interval of 10 minutes with a 1 degree celsius reporting threshold. add change for zigbee contact as well
CHAD-12259 zigbee motion: high battery usage
* Adding SONOFF matter device:MINIR4M * Adding SONOFF matter device:M5-1C、M5-2C、M5-3C --------- Co-authored-by: lelandblue <[email protected]>
…battery-check Fix the battery check in matter-thermostat, look for feature map
…on-battery-check Matter Button: specifically check for battery in power source
…f-fingerprint Matter Switch: fix Nanoleaf NL71K1 fingerprint
* Add Smartvill Switch drivers * Modify the code according to the specifications. * Correct an oversight * use 2 spaces for our tab width * Change to multi_switch_no_master * Add a comment
rolling up main to beta
This change puts an API Version guard around the call that performs the auto-add/auto-delete scan at startup, which is causing a crash on 0.47 TV's due to an issue with looking up non-existent UUID's. We believe the root of the issue is that the non-existent UUID lookup is related to trying to look up the Hub UUID as the parent of the bridge, but because this is a pretty gnarly issue we're going to roll back while we're confirming our suspicion.
Channel deleted. |
Test Results 55 files 352 suites 0s ⏱️ Results for commit 2464a89. |
matter-button_coverage.xml
matter-switch_coverage.xml
matter-thermostat_coverage.xml
zigbee-contact_coverage.xml
zigbee-motion-sensor_coverage.xml
zigbee-switch_coverage.xml
zigbee-window-treatment_coverage.xml
Minimum allowed coverage is Generated by 🐒 cobertura-action against 2464a89 |
No description provided.