[ #BluetoothMesh ] possible Bug .. without assigning subscription address to Model, it is reacting to subscription address assign to other Model #bluetoothmesh
Vikrant More <vikrant8051@...>
This is observation based on following configuration done by #meshctl.
Two nRF52840-PDK boards has been used for it.**************************************************************************************
appkey-add 1
bind 0 1 1000For Board 2. after provisioning, I used following commands to configure it
**************************************************************************************
appkey-add 1
bind 0 1 1000In case of Board 2, I didn't assign pub & sub addresses to Models 1002 & 1003
**************************************************************************************
Button 1 & 2 are related to GEN_ONOFF_CLIENT
Button 3 & 4 are related to GEN_LEVEL_CLIENT
Button 3 & 4 are related to GEN_LEVEL_CLIENT
As per my coding,
1. if Button 1 is pressed, then LED1 on all Boards turns ON.
2. if Button 2 is pressed, then LED1 on all Boards turns OFF.
3.if Button 3 is pressed, then it publishes value for eg. 2000.
On subscriber side, it checks that value (since it is less than 10000 it turns ON LED3 & turns OFF LED4 )
4. if Button 4 is pressed, then it publishes value for eg. 15000.
On subscriber side, it checks that value (since it is greater than 10000 it turns OFF LED 3 & turns ON LED4)
******************************************************************************************
1. if Button 1 is pressed, then LED1 on all Boards turns ON.
2. if Button 2 is pressed, then LED1 on all Boards turns OFF.
3.if Button 3 is pressed, then it publishes value for eg. 2000.
On subscriber side, it checks that value (since it is less than 10000 it turns ON LED3 & turns OFF LED4 )
4. if Button 4 is pressed, then it publishes value for eg. 15000.
On subscriber side, it checks that value (since it is greater than 10000 it turns OFF LED 3 & turns ON LED4)
******************************************************************************************
Ideally, as per #meshctl configuration,
if I pressed Button1 on any board, then LED1 on all boards should turn ON & if pressed
pressed Button2 then LED1 should OFF.
And if I pressed Button3 or Button4 on Board1, it should affect LED3&4 on only self Board.
And if I pressed Button3 or Button4 on Board2, it should not affect LEDs on any Board.
********************************************************************************************
And if I pressed Button3 or Button4 on Board1, it should affect LED3&4 on only self Board.
And if I pressed Button3 or Button4 on Board2, it should not affect LEDs on any Board.
********************************************************************************************
But here, I found strange behavior in case of Board2. Here without assigning subscription
addresses to Model 1002, LED 3 & LED 4 on Board 2 are reacting as soon as I pressed
addresses to Model 1002, LED 3 & LED 4 on Board 2 are reacting as soon as I pressed
Button 3&4 on Board 1.