tree: 3b34a1f53f896530b0c7f501b41447487d5e3c32 [path history] [tgz]
  1. data_model/
  2. java/
  3. python/
  4. tests/
  5. AbstractDnssdDiscoveryController.cpp
  6. AbstractDnssdDiscoveryController.h
  7. BUILD.gn
  8. CHIPCluster.cpp
  9. CHIPCluster.h
  10. CHIPCommissionableNodeController.cpp
  11. CHIPCommissionableNodeController.h
  12. CHIPDeviceController.cpp
  13. CHIPDeviceController.h
  14. CHIPDeviceControllerFactory.cpp
  15. CHIPDeviceControllerFactory.h
  16. CHIPDeviceControllerSystemState.h
  17. CommandSenderAllocator.h
  18. CommissioneeDeviceProxy.cpp
  19. CommissioneeDeviceProxy.h
  20. DeviceAddressUpdateDelegate.h
  21. DeviceDiscoveryDelegate.h
  22. EmptyDataModelHandler.cpp
  23. ExampleOperationalCredentialsIssuer.cpp
  24. ExampleOperationalCredentialsIssuer.h
  25. InvokeInteraction.h
  26. OperationalCredentialsDelegate.h
  27. ReadInteraction.h
  28. README.md
  29. SetUpCodePairer.cpp
  30. SetUpCodePairer.h
  31. TypedCommandCallback.h
  32. TypedReadCallback.h
  33. WriteInteraction.h
src/controller/README.md

CHIP controller

There are currently 4 implementations of the CHIP device controller with varying support for certain CHIP features.

Implementations

iOS

The iOS chip-tool is located in ../darwin/CHIPTool.

Android

The Android chip-tool is located in ../android/CHIPTool.

POSIX CLI

The POSIX CLI chip-tool is located in ../../examples/chip-tool.

Python

The Python chip-device-ctrl is located in ../controller/python/.

Feature Overview

OnboardingiOSAndroidCLIPython
Setup codey?nyy
QR codeyynn
NFCyynn
ProvisioningiOSAndroidCLIPython
Soft-APynyy
WiFi-BLEy?yyy
Thread-BLEn(*0)y(*1)ny(*1)
Commands/ClustersiOSAndroidCLIPython
Echo Clienty?yyy
On/Off Clientyyyy
LevelControl Client?yyy
Identify Client?n(*2)yy
Scene Clientn?n(*2)yy
Group Clientn?n(*2)yy
Binding Clientn?n(*2)yy
Attributes/ClustersiOSAndroidCLIPython
Readnn(*2)yy
Writenn(*2)yn
iOSAndroidCLIPython
Multiple Devicesyn?y

Notes:

(*0) https://github.com/project-chip/connectedhomeip/pull/4829

(*1) Only static commissioning, not MeshCoP.

(*2) Locally a patch exists, could be upstreamed.