Meeting, 2023-10-06

[ivmarkov]

(@kedars We should probably open the "Discussions" functionality in the GH project, and then make one item there, "Meetings". Or at least this is what the esp-rs folks practice.)

CC: @jasta @mabezdev @jessebraham

Overall: Intro, availability of folks

• Participants: @kedars, @bjoernQ, @ivmarkov

Did a review of the existing issues / errors:

• 109

  • Hypothesis 1: (Kedars) extra/changed parameters in the ASN.1 certificate encoding that need processing
  • Hypothesis 2: (Ivan) the Fabric ID coming with the cert does not match the one in the session (?)
  • Action: @ivmarkov to try to repro the bug with his Alexa controller

• 103

  • Will be addressed by PR #107

• 102 (also PR #107)

  • Seems Matter C++ SDK returns empty string instead of UnsupportedAttribute (to be confirmed)
  • Kedar reported that for him provisioning does work with a Matter C++ SDK device (but then again, that might be because the C++ SDK returns an empty string)
  • Action: @kedars to check with chiptool the Matter C++ device what exactly it returns for UniqueId - empty strong or not
  • Action: @kedars to check another optional attribute with the Matter C++ device; if both return default values with the Matter C++ SDK then we should do the same; if only UniqueId returns a default values, we should treat it as a special case, as we do now

• 100

  • Action: @kedars, Merge

• 108

  • Agreement is we would not be doing this
  • Action: @kedars, Close

• 94

  • Action: @kedars, Merge

• 101

  • The source of confusion here is that the OnOffCluster sample implementation is part of the rs-matter library, while it should be provided as part of the example, to make it clear that users should provide their own one
  • Action: @ivmarkov - open a PR

Did a review of the longer term roadmap; Top 3 roadmap items seem to be:

• 41

  • In a way this is also the way to provision for Wifi
  • Also the way to provision for Thread
  • Ivan noted that there is another way for WiFi provisioning (SoftAP with a special name, according to the spec)
  • Action, @kedars - to check if any company has implemented this ^^^ else it might become optional part of the spec and would not be a widely used feature anyway
  • Bjoern mentioned that he is looking into Thread support; seems that also is a sub-item of BLE provisioning

• 35

  • Ivan suspects the lack of this is the reason why provisioning with Google controller fails with "device not found" at the end, however Kedar believes this is most likely an mDNS issue (so much easier to fix)
  • In any case consensus is we need this functionality
  • Ivan mentioned this would most likely need Exchange in Initiator mode to be supported; Kedar believes it should actually be a long-running Exchange initiated by the controller
  • Action, @kedars, all: check in the spec if subscription events are delivered over a long running Exchange/Transaction opened by the controller, or (as Ivan believes) each subscription report is a new exchange initiated by the device

• 37

  • Should be relatively easy to implement, now that we are async based
  • (Not mentioned during the discussion) After that we probably need another roadmap item - "Consolidate most of exchange logic in ExchangeMgr"; also related to #35 ^^^

• 36

  • Not one of the top 3, but maybe still important; Kedar explained this is the vehicle for delivering notifications of a type "new fabric was provisioned", which might be important
  • Action, @kedars - check if this part of the spec is actually implemented by anybody

[kedars]

Discussions is now open

[ivmarkov]

Thanks! Moved here: https://github.com/project-chip/rs-matter/discussions/115