MESH callback is not properly called when multiple models registered in an element

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at https://www.dialog-semiconductor.com/support . We’ll be fixing bugs / optimising the searching and tagging over the coming days.
3 posts / 0 new
Last post
firebird
Offline
Last seen: 1 year 10 hours ago
Joined: 2019-07-12 09:48
MESH callback is not properly called when multiple models registered in an element

When designing MESH device, it is possible for an element to contain multiple models inside.

For example, we can register a generic level server and a level client into an element, and it is so-called "control model".

But, in current SDK 1.6.1, only one model can call its callback, in my case, MS_ACCESS_GENERIC_LEVEL_STATUS_OPCODE is received in level server, but not in level client.

Is this behaviour by design, or bug?

Should I modify "generic_level_opcode_list" in "app_model_level.c" and separate to "generic_level_server_opcode_list/generic_level_client_opcode_list"?

Keywords: 
Device: 
PM_Dialog
Offline
Last seen: 5 months 2 weeks ago
Staff
Joined: 2018-02-08 11:03
Hi firebird,

Hi firebird,

Let me check it and I’ll get back to you.

Thanks, PM_Dialog

firebird
Offline
Last seen: 1 year 10 hours ago
Joined: 2019-07-12 09:48
Awaiting update...

Awaiting update...