1) If we, (provision -> unprovision -> provision) the Bluetooth Mesh Node which is based on onoff_level_lighting_vnd_app then in case of some arbitrary available Model APP key not get save on SoC persistent storage during "any" reprovision event.
After reboot we have to reassign APP key to things get work.
2) Still facing Mesh initialisation delay. This is because of some recent commits.
There could be problem in commits which are merged after
