Two different methods of creating controllers?

[sambs]

Hi!

There are two different methods for creating controllers and commissioning devices in the examples - controller-onoff and controller. Could someone elaborate on the difference between them? It looks like the controller example uses newer APIs?

I've been trying to commission my hue bridge (possibly too ambitious?!). Using a ServerNode from @matter/main with nodes.commission I encounter an error "Cannot initialize hue-controller-test.hue-bridge.ep1.ep2 because it is already active".

I'm able to successfully commission using the CommissioningController from @project-chip/matter.js but I'm struggling to get endpoint.stateOf to return anything.

So, I have a general question I guess - what's the direction of travel here? Is service.nodes.commission the new way? There seems to be a lot of flux in this area of the project at the moment! Would it be wise to hold off for now and wait for things to settle?

Great project by the way - lots of exciting possibilities!

[Apollon77]

As noted in "control-onoff" example in

matter.js/packages/examples/src/control-onoff/OnOffController.ts

Line 10 in 4927c58

* This API is a work in progress and is not yet fully implemented.

this will be the new API in the future, but it is still work in progress. So right now this approach is not ready for production usage, but hopefully will be till we officially release 0.16 or 0.17

So the current "full featured" way to create a controller is to do it like the Controler example / https://github.com/matter-js/matter.js/blob/main/packages/examples/src/controller/ControllerNode.ts whicl bases on the "legacy" API approach. An "endpoint.stateOf" method exists there too in the recent nightly builds.

[sambs]

Okay great, thanks for clarifying.