082824 Controller AI 2.0 082824 控制器 AI 2.0

We are improving the user experience by removing the controller buttons and replacing the complicated LCD control panel with a TFT interface that only displays sensor readings. This change allows us to target other markets more effectively, as we can tailor the app experience to each market more effectively without seeming awkward with unrelated contents. We can cater the experience to each market via the app. Additionally, by developing it as a Border Router that works with our Thread Devices and Sensors, we have cutting-edge secure local network capabilities to go along with our AI and ACI advance features that can enhance our branding by positioning ourselves as a leader in tech within the growers' market. Implementing this change requires relatively little work for a significant impact, as it does not involve major hardware or UI modifications.
我们通过移除控制器按钮并用仅显示传感器读数的 TFT 界面取代复杂的 LCD 控制面板，来改善用户体验。这一改变使我们能够更有效地针对其他市场，因为我们能够更有效地根据每个市场的特点定制应用体验，而不会因为包含与之无关的内容而显得突兀。我们可以通过应用来适应每个市场。此外，通过将其开发为与我们的 Thread 设备和传感器一起工作的边界路由器，我们拥有了先进的安全本地网络能力，这与我们的 AI 和 ACI 高级功能相结合，可以增强我们的品牌定位，使我们在种植者市场中成为技术领导者的形象。实施这一改变需要相对较少的工作，对影响却很大，因为它不需要进行重大的硬件或用户界面修改。

However, significant work is required to pair the Controller AI 2.0 with our ACI Thread Devices, such as the Room-to-Room Fan, Smart Watering System, Window Fan, Wireless Single Plug, and wirelessly with 4.0 dongles via Thread and form a Thread Network.
然而，将 Controller AI 2.0 与我们的 ACI 线程设备配对，如房间到房间风扇、智能浇水系统、窗户风扇、无线单插头以及通过 Thread 和 4.0dongles 无线配对形成 Thread 网络，需要进行大量工作。

The Controller AI 2.0 should be Border Router-ready upon release. This will allow us to focus on ensuring that our ACI Thread Ecosystem functions seamlessly with our own Thread Devices and Thread Sensors. We understand that the Controller AI 2.0 is not a standard Thread Border Router and will not work with third-party Border Routers. However, we need to ensure that our ACI Thread Devices and Sensors are compatible with third-party Border Routers via Thread, depending on the third-party platform, so they can adhere to standard protocols. And we would need to know how we OTA the Controller AI 2.0 to a Standard Border Router if we decide to update it.
控制器 AI2.0 在发布时应具备边界路由器功能。这将使我们能够专注于确保我们的 ACI 线程生态系统与我们自己的线程设备和线程传感器无缝协作。我们明白，控制器 AI2.0 不是标准的线程边界路由器，并且不与第三方边界路由器兼容。然而，我们需要确保我们的 ACI 线程设备和传感器能够通过线程与第三方边界路由器兼容，具体取决于第三方平台，以便它们遵循标准协议。如果决定更新它，我们需要知道如何通过 OTA 方式将控制器 AI2.0 更新到标准边界路由器。

Modify the current Controller AI to create Controller AI 2.0, updating it from 8 device ports and 2 sensors to 8 UIS device ports and 4 UIS sensors. Remove the buttons and replace it with a small black-and-white TFT display to show sensor readings and alerts.
修改当前的控制器 AI，创建控制器 AI 2.0，将设备端口从 8 个增加到 8 个 UIS 设备端口，传感器从 2 个增加到 4 个 UIS 传感器。移除按钮，替换为一个小黑白 TFT 显示屏，用于显示传感器读数和警报。

Control Panel: Yes 控制面板：是

Built-In Sensors: 1 x Climate Sensor (Temp. + Humidity) Accurately measures the temperature and humidity of the environment.
内置传感器：1 x 气候传感器（温度+湿度） 准确测量环境的温度和湿度。

Need to be Thread Border Router ready when it's released.
在它发布时，需要准备好成为边界路由器。

Battery: same as 3.5 电池：与 3.5 相同

Memories: Built-In memories to retain the previous setting
记忆：内置记忆以保留之前的设置

8 LED Light (Indicator): White
8 LED 灯（指示灯）: 白色

Our UIS devices may be able to move to threads more quickly because we will make the 4.0 S-controller (Review needed), Thread Dongle, and new devices are being built with threads, so we don’t need that many UIS ports to begin with. We can even include two 4.0 dongles with each controllers. However, our sensors will lag behind in development so its better to have 4 UIS sensor ports to start. Many sensors also might not be appropriate to be threads since there’s the hassle of batteries which devices do not have this issue.
我们的 UIS 设备可能能够更快地转移到线程，因为我们将会制作 4.0 S 控制器（需要审核），线程适配器，以及新的设备正在被构建为支持线程，因此我们一开始就不需要那么多的 UIS 端口。甚至每个控制器都可以包含两个 4.0 适配器。然而，我们的传感器在开发上可能会落后，因此最好开始时有 4 个 UIS 传感器端口。许多传感器可能也不适合使用线程，因为电池的麻烦问题，而设备本身没有这个问题。

Alarm: Physical Alarm sounds
警报：物理警报响起

IP Rating: same as 3.5
IP 等级：与 3.5 相同

Hold the button for 5 seconds to activate the BLE/WIFI function to pair with the APP. Auto leave pairing process if 5 mins of unpaired.
按住按钮 5 秒以激活 BLE/WIFI 功能与 APP 配对。如果 5 分钟未配对，则自动退出配对过程。

Press and Hold for 10 sec to reset to factory setting until a beep sound the reset is completed and the rocket logo flying away animation ready for pairing.
按住 10 秒以恢复出厂设置，直到听到一声蜂鸣声，表示设置已恢复完成，火箭标志飞行远离动画已准备好进行配对。

The light dot will be steady White when the device is connected to the controller and not running.
当设备连接到控制器且未运行时，光点将保持为白色。

default display build in sensor reading
默认显示内置传感器读数

option for user to select whatever sensor (app only)
用户可以选择任意传感器（仅限应用）的选项

This will also help us test border router technology and our Thread devices and 4.0 dongles before developing a fully dedicated, non-UIS port controller for another market. Being prepared positions us better to transition to Thread if we have a controller capable of working with our Thread devices sooner.
这也将帮助我们在开发专门为另一个市场设计的、非 UIS 端口控制器之前，测试边界路由器技术以及我们的 Thread 设备和 4.0 适配器。做好准备使我们处于更有利的地位，如果我们的控制器能够与我们的 Thread 设备协同工作，我们就能更快地过渡到 Thread。

Most features share between Controller AI+. Adjust App UI to be able to accept higher number of max devices and sensors, by being able to add Thread Devices, including Smart Watering System, Room to Room Fan, Window Fan, and Wireless Single Plug, and future Thread Sensors beyond the ports. Allow mix and match between wired UIS devices, wired UIS sensors, 3.5 2.4G transmitter/ receiver, ACI Thread devices, and Thread sensors.
大多数功能与 Controller AI+共享。调整应用 UI 以接受更多设备和传感器，包括能够添加 Thread 设备，如智能浇水系统、房间到房间风扇、窗口风扇和无线单插头，以及未来的 Thread 传感器。允许混合使用有线 UI 设备、有线 UI 传感器、3.5 2.4G 发射器/接收器、ACI Thread 设备和 Thread 传感器。

It will provide users wireless control. The software：
它将为用户提供无线控制。软件：

need to discuss with Gyan on how to pair Thread Border Router with aci app.
需要与 Gyan 讨论如何将 Thread Border Router 与 aci app 配对。

modify on top of the current UI and display everything connect Tap to access the programming of the device.
在当前 UI 的基础上进行修改，并显示所有连接。点击以访问设备的编程。

Display in list 1. Sensor ID, Default name, user set name. 2. Device ID, Default name, and user set name, basic status (On, OFF, 0-10)
显示为列表 1. 传感器 ID，默认名称，用户自定义名称。 2. 设备 ID，默认名称，用户自定义名称，基本状态（开，关，0-10）

Depending on the device, we may offer tailored modes, advanced settings, and sensor options.
根据设备的不同，我们可能会提供定制模式、高级设置和传感器选项。

modify on top of the current UI. set limitation on Device and Sensor number. Top section, all Devices, including UIS and Thread, use current scrolling option for up to 8 devices. once reaches 9 and above we would convert it to drop down selection.
在当前 UI 的基础上进行修改。设置设备和传感器数量的限制。 顶部部分，所有设备，包括 UIS 和线程，最多使用当前滚动选项支持 8 个设备。一旦超过 9 个设备，我们将转换为下拉选择。

Bottom section Display an empty sensor section when the user doesn't pair any sensor, or show the default sensor that comes with the device.
底部部分 当用户未配对任何传感器时，显示一个空的传感器部分，或者显示设备自带的默认传感器。

Display sensor pair with the device only.
显示传感器对与设备仅连接。

For example, we are only offering a single sensor mode. Within this mode, the options depend on the device type. We may be limited in the available sensor types and whether we offer a secondary sensor.
例如，我们仅提供单一传感器模式。在这个模式中，选项取决于设备类型。我们可能受限于可用的传感器类型以及是否提供备用传感器。

Depending on the Device, we will provide a chart later.
根据设备的不同，我们稍后会提供一个图表。

Paring with Thread Devices and Thread Sensors entrance in Controller.
控制器中的线程设备和线程传感器入口。

after the Thread Devices being paired, then it will generate and display the corresponding Devices ID and Sensor ID, (see above device page)
配对线程设备后，将生成并显示相应的设备 ID 和传感器 ID，请参见上方的设备页面

Step 1. select device (s) or device type
步骤 1. 选择设备（s）或设备类型

Step 2. select a mode, OFF Mode, On Mode, Sensor Mode (only 1 sensor mode option), and Cycle Mode. or Recipe.
步骤 2. 选择一种模式， 关机模式，开机模式，传感器模式（仅有一个传感器模式选项）和循环模式。或食谱。

Step 3. if user select a sensor mode, then depending on the device(s) you selected, displaying programing based on Primary Sensor Type, and/ or Secondary Sensor Type.
步骤 3. 如果用户选择了传感器模式，然后根据您选择的设备，显示基于主传感器类型和/或次传感器类型的编程。

same as 3.5 controller. 与 3.5 控制器相同。

same as 3.5 controller for now, may update it to Event with IPC.
目前与 3.5 控制器相同，可能更新为具有 IPC 的 Event。