-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Bluetooth: Mesh: Develop/fixing light lc sm conditions #12040
Bluetooth: Mesh: Develop/fixing light lc sm conditions #12040
Conversation
The code for the two case statements was the same, so merged the case statement to use the same code. Signed-off-by: Ingar Kulbrandstad <ingar.kulbrandstad@nordicsemi.no>
Test specificationCI/Jenkins/NRF
CI/Jenkins/integration
Detailed information of selected test modules Note: This message is automatically posted and updated by the CI |
1ca62bc
to
51a94ae
Compare
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
51a94ae
to
9472fb9
Compare
* should not be processed. | ||
*/ | ||
(srv->state == LIGHT_CTRL_STATE_ON && | ||
atomic_test_bit(&srv->flags, FLAG_TRANSITION))) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine now.
9472fb9
to
90c9696
Compare
!atomic_test_bit(&srv->flags, FLAG_MANUAL))) { | ||
if ((srv->state == LIGHT_CTRL_STATE_STANDBY && | ||
/* According to the Mesh Model Specification section | ||
* 6.2.5.6 specifications STANDBY state, and the Auto |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* 6.2.5.6 specifications STANDBY state, and the Auto | |
* 6.2.5.6 about the STANDBY state, if the Auto |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same below
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not agree in this change, because it is importent to reference to the specifications STANDBY state and not the STANDBY state in the code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The sentence as it stands makes no sense. What is the "and" related to? The "and" makes no sense. What are you trying to say? "According to section 6.2.5.6: when you are in the specifications STANDBY state and the Auto Occupancy is off, the event should not be processed"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, you have understood it correctly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then:
* 6.2.5.6 specifications STANDBY state, and the Auto | |
* 6.2.5.6: When in the specifications STANDBY state, and the Auto |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is becoming nitpicking, but I will add "When in the".
According to sections 6.2.3.5 of MshMDLd1.1r12, the value of the Light LC Ambient LuxLevel state is set to 0 at power-up and when the node is provisioned on the network. According to sections 6.2.5.12 and 6.2.5.7 the Occupancy On should not trigger any transition. Signed-off-by: Ingar Kulbrandstad <ingar.kulbrandstad@nordicsemi.no>
90c9696
to
d598a55
Compare
According to sections 6.2.3.5 of MshMDLd1.1r12, the value of the
Light LC Ambient LuxLevel state is set to 0 at power-up and when
the node is provisioned on the network.
According to sections 6.2.5.12 and 6.2.5.7 the Occupancy On should
not trigger any transition.
Signed-off-by: Ingar Kulbrandstad ingar.kulbrandstad@nordicsemi.no