David Göransson

Hello @t-m-w, I stumbled upon this PR as I was working on a related issue. I've gone through your test cases and they are what I can see mostly correct....

I'm going to close this PR, I'm open to opening it up again if needed. As mentioned previously we've added an internal task to clarify the android behavior in a...

Thank you for your detailed reply! Maybe it wasn't clear in my example but in OnResume I would update my data by starting my presenter and binding it to a...

Quick fix for https://github.com/NordicSemiconductor/Android-nRF-Mesh-Library/issues/539 possibly this logic should be on a setter in ProvisionedBaseMeshNode.

@philips77 Thanks for the response, regarding the changing of elements. Just read up on the [Mesh Profile 1.0.1 spec](https://www.bluetooth.com/specifications/specs/mesh-profile-1-0-1/) and believe I found what you refereed to under the section...

Not sure exactly why, I saw it was referenced in this PR: https://github.com/NordicSemiconductor/IOS-nRF-Mesh-Library/pull/167 It feels a bit wrong just to ignore the element information and just not caring about it....

Yes, that correct. However, imagine that you have a set of lights that is the majority of your mesh and they receive a new firmware update that adds a new...

@philips77 That sounds strange, not allowing for changes to the `vid`. Then there is no way of knowing what version a device runs by looking at the mesh configuration, and...

I'm not sure about the best way to address this, it is a bit weird that the entire stack depends on IP, especially for UDS. So that is a bit...

I believe this UX-flow has been improved since the creation of this issue. And as @raksooo mentioned With DAITA + Direct only the user will see only DAITA servers and...