Mesh Opcodes and linking them to the handler in the access layerhttps://devzone.nordicsemi.com/f/nordic-q-a/64676/mesh-opcodes-and-linking-them-to-the-handler-in-the-access-layerI&#39;ve been writing a vendor model for Bluetooth mesh based on the light lightness model in the SDK. I&#39;m extending the generic level model into my model - a window openess level model. It&#39;s far complete, but it&#39;s to the point where I want to be able toen-USTelligent Community 13Tue, 11 Aug 2020 20:08:42 GMTRE: Mesh Opcodes and linking them to the handler in the access layerhttps://devzone.nordicsemi.com/thread/264132?ContentTypeID=1Tue, 11 Aug 2020 20:08:42 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bff3b7b2-3922-480b-93b8-cecf8362e326Ryjan<p>It turns out that my issue was that I was not looking in the right place. I figured that as soon as i posted something I&#39;d get a lead on a new idea.&nbsp; I was actually getting a callback from the generic level model, but it was linked to a stub function I had made in my new model. I had the regular level callbacks with a proto-implementation, not for the delta level callbacks. It appears that the app sends level commands for the generic lever server as a change in level (delta) rather than a set to a specific level. Now I can see that callback and I am stitching it into my normal window controller callback, so the issue is solved.</p><div style="clear:both;"></div>