-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Unknown command support for ClusterClients (API and shell) #1053
Comments
Hi, ok what exactly is your usecase? Or do you need this in controller code? Because there it is already existing and can be used. So please be more specific what exactly you need and for which usecase. |
Ok I looked into the code. In general: In Controller code when you see in log that a custom cluster was added or custom attributes these are available as objects too. You could create a matter.js schema for the relevant clusters and register this then you could use it in controller code with all the typing and also tlv parsing convenience. as all the other clusters have. This is for cases where you know the structure f the cluster. For cases where this is not the case we do the best to parse the data generically. basically use ´pairedNode.getDeviceById(2) Re: the question why the attribute value is always 0 can be one of two cases depending on how you connected to the node in the shell And please consider posting logs and screen infos as text and not image for copy&paste convenience. Thank you. |
PS: In general a full debug log of that would be interesting because also the warnings about attribute updates received for an unknown endpoint but after this you can interact with this endpoint is weird. So a full debug log of a connect and also a "nodes log" for this node would be interesting. Thank you.- |
For the debug log, please see the attached document. |
Thank you, in fact the connection is done with a subscription, so basically it reads locally because it expects attributes to be reported. You can try to connect without a subscription (kind of with just "nodes connect 111") then it should just do a read* atthe beginning and all reads will be done remotely. Does that values change then? |
Thank you, I will try this method tomorrow |
BTW: I also considered this with Eve energy and their custom cluster. Also there energy values are not reported on subscribe which is meehh because you need to poll it which is bad in my eyes :( maybe it changes then with the official Energy cluster soon |
Hello, thanks for the library.
I want to invoke the command of unknown cluster, for example:
The matter bridge enable the function of scanning subdevices.
Here's what I think:
Can command-by-id be implemented? For example:
./chip-tool any command-by-id 0x130DFC00 0x02 '{"0": 180}' 1 0
After the device is added, Unknown cluster is automatically generated for easy invocation.
The text was updated successfully, but these errors were encountered: