【Kalay1.0 Standard Plus PSC】
<p>This version update has made the following adjustments, please read them carefully. (2024/4/24)</p>
<h1><strong>1. Update the Framework</strong></h1>
<h2><strong>[Adjusted Purpose]</strong></h2>
<p>Synchronously fix problems discovered during internal testing and optimize functions/performance.</p>
<h2><strong>[Adjusted Content]</strong></h2>
<ol>
<li>Updated IOTCamera.framework 2.8.0.3 /IOTCamera.aar 2.8.0.3；</li>
<li>Fixed some UI issues, please refer to [#Release Note](<a href="https://www.showdoc.com.cn/kalaypscnew/10956308905687683">https://www.showdoc.com.cn/kalaypscnew/10956308905687683</a> "#Release Note").</li>
</ol>
<h2><strong>[Impact and Suggestions]</strong></h2>
<ol>
<li>IOTCamera.framework and IOTCamera.aar need to be updated to the latest version;</li>
</ol>
<h1><strong>2. Change the QR code format added by scanning the code</strong></h1>
<h2><strong>[Adjusted Content]</strong></h2>
<p>Compatible with SDK 4.x, Nebula protocol (using 40-bit UDID) for device addition and connection.</p>
<h2><strong>Adjust content</strong></h2>
<ol>
<li>When adding a device using the "Not been connected to the router" - "Scan WiFi QRCode" (qrcode) mode, the device-side QR code scanned by the App adds two optional parameters: "realm" and "amToken";</li>
<li>When adding a device using the "Been connected to the router" - "Scan QR code" (eth) mode, the device-side QR code scanned by the App adds two optional parameters: "realm" and "amToken";</li>
</ol>
<h2><strong>[Impact and Suggestions]</strong></h2>
<ol>
<li>If the device uses a 40-digit UDID and supports Nebula protocol connection, if you need to scan the QR code to add the device, please follow the [# Docking Guide](<a href="https://www.showdoc.com.cn/kalayappforpublic/10953824482837812">https://www.showdoc.com.cn/kalayappforpublic/10953824482837812</a> "# Docking Guide") for implementation.</li>
</ol>
<h1><strong>3. Update KOTA Version Check</strong></h1>
<h2><strong>[Adjusted Purpose]</strong></h2>
<p>The format of the version number defined on the device side is inconsistent, resulting in the inability to unify the comparison rules. It is estimated that the parameter type of the KOTA version number in the relevant command should be modified.</p>
<h2><strong>[Adjusted Content]</strong></h2>
<ol>
<li>In IO Command: IOTYPE_USER_IPCAM_DEVICE_INFO_RESP = 0x8016, change the type of "version" from "int" to "char[64]";</li>
<li>When comparing KOTA version numbers, if the latest version number obtained by the App from the KOTA server is inconsistent with the "version" returned by the device in IO Command 0x8016, it is determined that the latest firmware version exists, and the user can click Firmware Upgrade;</li>
</ol>
<h2><strong>[Impact and Suggestions]</strong></h2>
<ol>
<li>During the docking implementation, the device side needs to ensure that when uploading firmware in the KOTA background, the version number format filled in is consistent with the definition of "version" in IO Command to avoid misjudgment;</li>
<li>For details, please refer to [IO Command Definition - 2.41 Get device information](<a href="https://www.showdoc.com.cn/tutkiocmd/8933939875585050">https://www.showdoc.com.cn/tutkiocmd/8933939875585050</a> "IO Command Definition - 2.41 Get device information") for modification.</li>
</ol>
<h1><strong>4. Added Two-way Video Function</strong></h1>
<h2><strong>[Adjustment Purpose]</strong></h2>
<p>In response to market demand, this time a one-to-one two-way video call function has been added to support call scenarios.
> (Premise: The device supports the calling function)</p>
<h2><strong>[Adjusted Content]</strong></h2>
<ol>
<li>A two-way video call button is added to the Liveview page, which allows the App to actively initiate a call request and establish a one-to-one two-way video call;</li>
<li>A new event type (Event Type = 102) has been added to device push. Through KPNS push, call notifications initiated from the device can be received.</li>
</ol>
<h2><strong>[Impact and Suggestions]</strong></h2>
<ol>
<li>If you need to implement this function on the device side, please confirm that it is connected to the corresponding IO Command. For details, please refer to the document [IO Command Definition - 2.59 Obtain whether the device supports two-way video & 2.60 Initiate two-way video](<a href="https://www.showdoc.com.cn/tutkiocmd/8933939875585050">https://www.showdoc.com.cn/tutkiocmd/8933939875585050</a> "IO Command Definition - 2.59 Obtain whether the device supports two-way video & 2.60 Initiate two-way video") for implementation.</li>
<li>The device needs to add a new event type (Event Type = 102) and initiate an HTTPS request to KPNS to implement call notification initiated by the device.
(For how to realize the connection between the device and KPNS, please consult the relevant FAE to obtain the connection information)</li>
</ol>
<h1><strong>5. Configuration Upgrade to XCode 15</strong></h1>
<h2><strong>[Adjustment Purpose]</strong></h2>
<p>None</p>
<h2><strong>[Adjusted Content]</strong></h2>
<p>None</p>
<h2><strong>[Impact and Suggestions]</strong></h2>
<p>If you develop in XCode15 version, running the simulator requires at least iOS 12 and above. When switching between real machines and simulators, or when switching simulators to real machines for debugging, modify <strong>[Architectures]</strong> -> <strong>[Excluded Architectures]</strong> -> <strong>[Debug]</strong> -> <strong>[Any iOS Simulator SDK]</strong> -> Settings arm64, including (KalayMain, KalayControl, KalayBase, KalayLive, KalaySlider projects).</p>
<p>As shown below:
<img src="https://www.showdoc.com.cn/server/api/attachment/visitFile?sign=8bb8e9390dacf75b85efeadfeb9ca083&amp;file=file.png" alt="" /></p>