Seich
/
HomeSpan
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update TLV8.md

This commit is contained in:
HomeSpan 2024-04-21 12:41:14 -05:00 committed by GitHub
parent 4334789d50
commit 059c58ca46
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/TLV8.md
View File

@ -274,7 +274,7 @@ it_E TAG=200, LENGTH=32, Sum of all bytes = 496
## Reading and Writing TLV8 Characteristics ## Reading and Writing TLV8 Characteristics
As documented in the [API Reference](Reference.md#spancharacteristicvalue-boolean-nvsstore), the following *SpanCharacteristic* methods are used to read and write TLV8 objects to TLV8 Characteristics: As documented in the [API Reference](Reference.md), the following *SpanCharacteristic* methods are used to read and write TLV8 objects to TLV8 Characteristics:
* `getVal(TLV8 &tlv)` * `getVal(TLV8 &tlv)`
* `getNewVal(TLV8 &tlv)` * `getNewVal(TLV8 &tlv)`
@ -286,12 +286,8 @@ Note that since TLV8 Characteristics are stored as base-64 encoded strings, you
Also, if you really don't want to use HomeSpan's TLV8 library to produce TLV8 objects, but instead prefer to use your own methods to create a TLV8-compliant byte-array, you can do so and then use `setData()` to save the byte-array you produced to the TLV8 Characteristic, which will perform the base-64 encoding. Or if you want to additionally perform your own base-64 encoding (why?) you can do so and then simply use `setString()` to save the resulting encoded string to the TLV8 Characteristic. Also, if you really don't want to use HomeSpan's TLV8 library to produce TLV8 objects, but instead prefer to use your own methods to create a TLV8-compliant byte-array, you can do so and then use `setData()` to save the byte-array you produced to the TLV8 Characteristic, which will perform the base-64 encoding. Or if you want to additionally perform your own base-64 encoding (why?) you can do so and then simply use `setString()` to save the resulting encoded string to the TLV8 Characteristic.
---
[API Reference](https://github.com/HomeSpan/HomeSpan/blob/tlvwork/docs/Reference.md#spancharacteristicvalue-boolean-nvsstore) [↩️](../README.md) Back to the Welcome page