Open Chapoly1305 opened 6 months ago
all-clusters-app does not have a client switch cluster, yes? So why would this be expected to work?
lighting-app does have a switch client, I believe.
@bzbarsky-apple Thank you for your response. As code indicated the all-cluster-all does have the client role of onoff cluster.
As well as the decoded in zap,
We expect this app can act a a light/switch that forwards the action to another lightbulb, it should not have to be a switch client to onoff server, should it? And lighting-app does not have a onoff or switch client. We respectfully ask for more information.
Ah, interesting. It does have a client, and there's some binding handling code. I have no idea what it's supposed to be able to do, though...
Thanks for your help. And one more question about the binding: If the binding function succeeds, like when the switch is on and the light turns on, is the 'light on' message sent by the switch directly or through the controller? @bzbarsky-apple
Binding is for direct communication.
We (cc @agatah2333 ) are currently trying to write automation to test the feature of binding. We have used example/all-cluster-app/linux, and referring to the articles listed below,
We were able to write acl to device act as the light, bind the switch and light (chip-tool displayed success), but when the switch turned on or off, but the light status has not changed accordingly.
The command we used to write ACL and Binding, 1111 is the light role, 2222 is the switch role.
The command used to trigger the status of onoff,
We would like to know if the feature on linux version of all-cluster-app has been implemented, if there are other apps that on linux is in knowledge working, thanks.
chiptool.log
Bug prevalence
Always
GitHub hash of the SDK that was being used
5bb5c9e23d532cea40476fc0bd1d3008522792ba
Platform
core
Platform Version(s)
No response
Type
Common Cluster Logic, Core SDK Interopability Issue
Anything else?
No response