Dynamic endpoints / bridge support

[cmair]

Hi,

I'm wondering what would be needed to support dynamic endpoints to implement a Matter bridge. Currently, endpoint and cluster initialization seems to be const and I didn't see an easy way to change those at runtime. As I'm still trying to understand how everything works (this includes the Rust language) I might have missed something tough. Any help would be appreciated!

[ivmarkov]

Also something I've missed as I do t get notifications for the q&a section... sorry!

Dynamic support is completely supported and baked-in! In fact, that's what I use in my own project.

You just need to implement the Node trait on top of some Vec, like either heapless::Vec or - if you are OK with allocations - on top of alloc:vec::Vec and then serve with it a bunch of Endpoint<'static> instances.

The catch a bit is that you cannot really change your dynamic Node layout while you are serving requests with your async handler. You have to wrap it with an async rw lock or mutex and then only change it when you are able to lock it - I.e. between two requests.

[ivmarkov]

I'm available to contribute, FYI - feel free to reach out (for now, just as a community contribution side project, but hopefully that'll change in the future)

That would be great! Perhaps you could just look at all issues newer than May'2024 and if you like one, we can discuss how to implement?

Another option would be - if you have a pain point, we can also discuss how it could be addressed?

[gmarcosb]

That sounds good, I'll take a look 👍🙏

[ivmarkov]

@madchicken this.

[madchicken]

Thanks @ivmarkov I'll take a look!

[ivmarkov]

@madchicken Be prepared that the current breed of Matter controllers (Google / Apple / Alexa) do not:

• Take into consideration the location of the bridged devices, as reported by the bridge. I.e. even if you implement the actions cluster which says a TV of yours is in your living room, the controller will not display the TV under your living room
• Take into consideration "composite" devices, where you have e.g. multiple sensors arranged/aggregated under a single device (e.g. your fridge)

Until this is fixed, importing a large number of bridged devices in the Matter controller results in a difficult to use system, because they are not arranged/clustered in a useful way and just listed as a one large list "in your home".