-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Level Control Server Cluster fix for level transitions #19392
Level Control Server Cluster fix for level transitions #19392
Conversation
Change-Id: I7fa4e59bb4bc822220de366139fa315e94b8d369
Change-Id: I09f5b3a2e2139aa2ff6fcf078f34ab84263db7c0
…ent still exists on eventEndpoints
Change-Id: Iff5c718dacff7624b7af5543bac812711dd646d9
Change-Id: I2384a31c63bdd87e0312184112c1cb682712f9b4
0acfd2d
to
a12f513
Compare
removed the references to level control cluster from the |
PR #19392: Size comparison from a8b3a07 to f173928 Increases (8 builds for cc13x2_26x2, cyw30739, esp32, nrfconnect)
Decreases (18 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, nrfconnect, p6, telink)
Full report (28 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, mbed, nrfconnect, p6, telink)
|
PR #19392: Size comparison from a8b3a07 to 276b4a2 Increases (11 builds for cc13x2_26x2, cyw30739, efr32, esp32, nrfconnect, telink)
Decreases (18 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, nrfconnect, p6, telink)
Full report (30 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
|
Fast tracking given this has had enough time for review, and comments are resolved. |
Fwiw, because of the confusion about this PR and #19390 there are in fact unresolved comments pending on this, they're just over on #19390. I did not realize they were targeting different branches.... @rochaferraz Can you please do a follow-up to fix? |
…19392) * fix: level control server handles its own ticks
* chg: addressing a few comments left from previous pr #19390 #19392 * Update src/app/clusters/level-control/level-control.cpp Co-authored-by: Boris Zbarsky <bzbarsky@apple.com> * Update src/app/clusters/level-control/level-control.cpp Co-authored-by: Boris Zbarsky <bzbarsky@apple.com> * Restyled by clang-format Co-authored-by: Boris Zbarsky <bzbarsky@apple.com> Co-authored-by: Restyled.io <commits@restyled.io>
* Level Control Server Cluster fix for level transitions (project-chip#19392) * fix: level control server handles its own ticks * chg: addressing a few comments left from previous pr project-chip#19390 project-chip#19392
Problem & Solution
The all-clusters and lighting apps rely on the
af-gen-event.h
file for theEMBER_AF_GENERATED_EVENTS
definition, along with its context. However, the file is not automatically generated by zap. Thus other sample apps that rely on level control don't perform the level transition.This definition enables the cluster events/ticks that cause a transition from one state to another on time-dependent clusters such as level control.
This change to level control deprecates the use of af-events. Level control server cluster now handles its own timer for state transitions using standard Matter SDK calls.
This fixes the issue on
interop_testing_te9
event. Once discussed and approved another similar PR will be made againstmaster
branch.Testing