Hello everyone, is there a way to send a text to the device through the text input box in preferences? Where can I find relevant references or implementation code Thank you!
You can use the info changed lifecycle event to run code when a preference changes and do whatever you want there. Example:
Just mind the preferences do not sync with the device state and that, if the write operation fails, the user will not know.
Thank you! I have reviewed the reference code you provided, which appears to be used for setting device parameters. You might have misunderstood my intention. I’m looking to get a copyright-related information from the device (and the retrieval method should not be easily discoverable by the customers)
I find that driver , on line 158-160, it seem like my need— I’m not sure.
You’ll have to clarify what do you need. To send text to a device you write an attribute, to get text from a device you read it.
1 Like
Hi, @chenjun.
As @mocelet mentioned, your first description doesn’t match this new question, so it is important to clarify what you’re really looking for.
Now, is the device you want to get copyright-related information from one of the manufacturer’s devices you’re working on, or is it from another device?
What purpose will you give to this information?
Sorry, I didn’t reply your question in time.
My ultimate goal is to read out a string related to the copyright information of the firmware from the device.
My initial design was to send a string to the device, and upon receiving it, the device would proactively report the information I needed.
Later, I realized that since this requirement should be invisible to the customer, I certainly couldn’t send my request through the input in preferences.
So I said this driving method might be more suitable for me. Of course, its feasibility still needs to be verified.
Sorry, I didn’t make my needs clear. My purpose is to read out the copyright information in the firmware.
The purpose of reading out the copyright information of the firmware is to prevent illegal misuse of the firmware.
Perhaps, for this requirement, do you have an existing implementation plan or better suggestions?
ok, @chenjun
Let me ask the engineering team and I’ll get back to you