Local self-healing methods, devices, air conditioning and media for whole-house smart device malfunctions

By building local data acquisition, fault diagnosis, and self-healing modules in the smart home system, fault identification and self-healing without cloud involvement are achieved, solving the reliability problem of the system when it is disconnected from external network support and improving the device's autonomous fault handling capability and response speed.

CN123113281APending Publication Date: 2026-11-17GREE ELECTRIC APPLIANCE INC OF ZHUHAI
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611482269.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-22
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing smart home systems lack the ability to identify and handle faults when disconnected from external network support, resulting in the inability to detect and address device malfunctions in a timely manner, which affects system reliability and user experience.

Method used

By collecting device operating parameters and environmental data locally and comparing and analyzing them using preset fault judgment rules, autonomous fault identification and self-healing can be achieved. This includes a data acquisition module, a fault judgment module, and a fault self-healing module, constructing a closed-loop mechanism to reduce dependence on cloud servers and independent gateways.

Benefits of technology

It enables local autonomous fault identification and self-healing of smart home devices when the network is down or cloud services are unavailable, improving system reliability and response speed, and avoiding fault accumulation and security risks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123113281A_ABST
    Figure CN123113281A_ABST
Patent Text Reader

Abstract

This invention discloses a local self-healing method, device, air conditioner, and medium for whole-house smart device faults. The method includes: collecting operating parameters and indoor environmental data of the target device according to a preset collection cycle to obtain a device operating dataset; comparing and analyzing the device operating dataset according to preset fault judgment rules to obtain a fault judgment result, wherein the fault judgment result is used to characterize whether the target device has a fault event and the type of fault event; if the target device has a fault event, processing the operating status of the target device according to the self-healing strategy corresponding to the fault event type to obtain a self-healing execution result. This invention can realize local autonomous identification and self-healing of faults in whole-house smart devices, improve the reliability and response speed of the system when the network is down or cloud services are unavailable, and effectively avoid the accumulation of faults and security risks caused by network interruptions.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of smart home technology, and in particular to a local self-healing method, device, air conditioner, and medium for malfunctions of smart devices throughout the house. Background Technology

[0002] With the increasing prevalence of IoT technology in home environments, a variety of devices such as smart window openers, humidifiers, and temperature and humidity sensors have been widely deployed in modern residential systems. These devices vary in type and have complex operating characteristics, and their stable operation highly depends on real-time monitoring of operating parameters and indoor environmental data. However, the increase in the number of devices and the widening differences in their functions have brought challenges to whole-house collaborative monitoring, including difficulties in data integration and delays in fault response.

[0003] Current mainstream technical solutions employ a collaborative architecture of independent gateways and cloud servers for fault management. The independent gateway collects operational status data reported by various sub-devices and transmits it to a remote cloud server via an external network. The cloud server analyzes the data stream based on preset rules, determines the fault type, generates handling instructions, and then sends them to the faulty device for execution via the gateway. This architecture has significant drawbacks: the fault identification and handling process relies entirely on the external network link. When home broadband is interrupted, the cloud service platform is unavailable, or the gateway device loses power, the entire monitoring system immediately fails, resulting in the inability to detect and handle device anomalies in a timely manner. Furthermore, traditional gateways typically only manage peripheral sub-devices, excluding core devices such as air conditioning units. When environmental anomalies occur, such as conflicts between window opening and air conditioning cooling modes, the system cannot directly intervene in the air conditioning operation mode or coordinate with smart window openers for adjustment, leading to energy waste and reduced living comfort. In practical applications, device faults in areas with unstable networks may accumulate over time, and if abnormal environmental parameters under extreme weather conditions cannot be handled in real time, it will further exacerbate system risks and affect user safety and experience.

[0004] The aforementioned technical bottlenecks highlight the serious deficiencies of existing solutions in terms of local autonomous decision-making capabilities, resulting in a significant decrease in the reliability of smart home systems when they are disconnected from external support. Therefore, developing a mechanism that can complete fault identification and self-healing without the involvement of cloud servers and independent gateways, relying solely on devices within the home LAN, has become a key requirement for improving the robustness and practicality of the system. Summary of the Invention

[0005] This invention provides a local self-healing method, device, air conditioner, and medium for whole-house smart device faults, which can realize local autonomous identification and self-healing of whole-house smart device faults, improve the reliability and response speed of the system when the network is down or cloud services are unavailable, and effectively avoid the accumulation of faults and security risks caused by network interruption.

[0006] In a first aspect, embodiments of the present invention provide a local self-healing method for faults in whole-house smart devices, comprising: Collect the target equipment's operating parameters and indoor environmental data according to the preset collection cycle to obtain the equipment operation dataset; By comparing and analyzing the equipment operation dataset using preset fault determination rules, a fault determination result is obtained. The fault determination result is used to characterize whether the target equipment has a fault event and the type of fault event. If the target device has a fault event, the operating status of the target device is processed by the self-healing strategy corresponding to the fault event type to obtain the self-healing execution result.

[0007] Secondly, embodiments of the present invention provide a local self-healing device for whole-house smart device malfunctions, comprising: The data acquisition module is used to collect the operating parameters and indoor environmental data of the target equipment according to a preset acquisition cycle to obtain the equipment operation dataset; The fault determination module is used to compare and analyze the equipment operation dataset according to preset fault determination rules to obtain fault determination results, wherein the fault determination results are used to characterize whether the target equipment has a fault event and the type of fault event; The fault self-healing module is used to process the operating status of the target device according to the self-healing strategy corresponding to the fault event type if the target device has a fault event, and obtain the self-healing execution result.

[0008] Thirdly, embodiments of the present invention provide an air conditioner, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the local self-healing method for whole-house smart device faults described in the first aspect.

[0009] Fourthly, embodiments of the present invention also provide a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to perform the local self-healing method for whole-house smart device malfunctions described in the first aspect.

[0010] This invention provides a local self-healing method, device, air conditioner, and medium for whole-house smart device faults. The method includes collecting operating parameters and indoor environmental data of the target device according to a preset collection cycle to obtain a device operating dataset; comparing and analyzing the device operating dataset using preset fault determination rules to obtain a fault determination result; and if a fault event exists in the target device, processing the target device's operating status using a self-healing strategy corresponding to the fault event type to obtain a self-healing execution result. Through a closed-loop mechanism of localized data collection, fault determination, and self-healing execution, autonomous fault handling is achieved without the need for cloud servers and independent gateways. This enables local autonomous identification and self-healing of whole-house smart device faults, reducing reliance on external networks and cloud servers, and improving system reliability and response speed during network outages or when cloud services are unavailable. Attached Figure Description

[0011] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 A flowchart illustrating the local self-healing method for whole-house smart device malfunctions provided in this embodiment of the invention; Figure 2 This is a schematic diagram of the first sub-process of the air conditioning control method based on reinforcement learning provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the second sub-process of the air conditioning control method based on reinforcement learning provided in an embodiment of the present invention; Figure 4 This is a schematic diagram of the third sub-process of the air conditioning control method based on reinforcement learning provided in an embodiment of the present invention; Figure 5 This is a schematic diagram of the fourth sub-process of the air conditioning control method based on reinforcement learning provided in an embodiment of the present invention; Figure 6 This is a schematic diagram of the fifth sub-process of the air conditioning control method based on reinforcement learning provided in an embodiment of the present invention; Figure 7 This is a schematic diagram of the sixth sub-process of the air conditioning control method based on reinforcement learning provided in an embodiment of the present invention; Figure 8 A schematic block diagram of a local self-healing device for whole-house smart device malfunctions provided in an embodiment of the present invention; Figure 9 This is a schematic block diagram of an air conditioner provided in an embodiment of the present invention. Detailed Implementation

[0013] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0014] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0015] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0016] It should also be further understood that the term "and / or" as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0017] Existing smart home systems typically employ an architecture combining a dedicated gateway and a cloud server for device fault detection. Data acquisition, fault diagnosis, and the issuance of handling commands all rely on external network links. When the external network is interrupted, the cloud server becomes unavailable, or the dedicated gateway loses power, the faults of sub-devices cannot be diagnosed and handled in a timely manner, and the entire home monitoring link is prone to failure.

[0018] In response, this application proposes a local self-healing method for whole-house smart device malfunctions, including: The operating parameters and indoor environmental data of the target device are collected according to the preset collection cycle to obtain the device operation dataset. The device operation dataset is compared and analyzed according to the preset fault judgment rules to obtain the fault judgment result. The fault judgment result is used to characterize whether the target device has a fault event and the type of fault event. If the target device has a fault event, the operating status of the target device is processed according to the self-healing strategy corresponding to the fault event type to obtain the self-healing execution result.

[0019] For ease of understanding, the following explains some key terms in this embodiment: Target devices refer to hardware devices deployed in indoor environments and incorporated into local monitoring and control systems, such as various environmental sensors, home appliances, or mechanical actuators.

[0020] Equipment operation dataset refers to the collection of parameters representing the current working status of the target equipment and indoor physical environment parameters collected within a preset collection period.

[0021] Fault determination rules refer to locally preset logical judgment conditions and comparison benchmarks used to identify abnormal equipment operation, and are used to determine whether the equipment has a fault and to define the specific fault type.

[0022] Self-healing strategies refer to control commands or repair processes corresponding to specific fault types, used to automatically adjust the operating status of target devices to eliminate abnormalities without external cloud intervention.

[0023] This application's embodiments achieve closed-loop processing of data acquisition, fault comparison and analysis, and self-healing control locally, enabling smart home devices to maintain normal operation even when disconnected from cloud servers and independent gateways. In scenarios where the home network is interrupted or external links are unavailable, it effectively avoids the problem of whole-house monitoring failure, ensuring that indoor device faults can be identified and handled locally in a timely manner, and guaranteeing the system's operational continuity even when offline.

[0024] Please see Figure 1 , Figure 1 This is a flowchart illustrating a local self-healing method for whole-house smart device malfunctions provided in an embodiment of the present invention. The local self-healing method for whole-house smart device malfunctions provided in this embodiment of the present invention is applied to air conditioners.

[0025] S1: Collect the operating parameters and indoor environmental data of the target device according to the preset collection cycle to obtain the device operation dataset.

[0026] Specifically, the process of collecting operating parameters and indoor environmental data of the target devices according to a preset collection cycle to obtain the device operation dataset can be implemented in several ways. For example, the local control host can send data query messages to each target device in the local area network at preset fixed time intervals. After receiving the query message, the target device passively transmits back the current operating current, operating voltage, or switch status to complete the data collection. As another implementation method, each target device can also actively unicast the collected temperature and humidity values ​​or its own operating mode to the local control host according to its internally fixed reporting frequency. Alternatively, the local control host can periodically read the register data of each target device connected to the bus through a wired bus, thereby summarizing them to form the device operation dataset.

[0027] In one specific embodiment, step S1 includes: sending a heartbeat message to the target device according to an adaptive heartbeat cycle through timed heartbeat detection, and recording the response message of whether the target device returns a heartbeat message as communication status data; The adaptive heartbeat period is determined as follows: A preset heartbeat period configuration table is queried based on the target device type to obtain the basic heartbeat period. The basic heartbeat period for environmental sensor-type target devices in the heartbeat period configuration table is shorter than that for actuator-type target devices. The average packet loss rate is obtained by calculating the ratio of the number of times no response messages are returned in the communication status data within a preset time window to the total number of heartbeat messages sent. The average packet loss rate and the degree of environmental interference are multiplied by their respective preset weighting coefficients and then summed to obtain the period correction amount. The period correction amount is subtracted from the basic heartbeat period to obtain the adaptive heartbeat period, which is such that the adaptive heartbeat period is shorter when the average packet loss rate and the degree of environmental interference are higher.

[0028] Specifically, timed heartbeat detection refers to proactively sending status probe data packets to target devices within a local area network according to a set time pattern, and determining their online status and link connectivity by listening to and recording the responses of the target devices. In practical implementation, heartbeat messages can be implemented using lightweight User Datagram Protocol (UDP) probe frames, Transmission Control Protocol (TCP) heartbeat packets, or PING request messages based on specific application layer protocols (such as MQTT, CoAP), thereby completing the collection and updating of communication status data with extremely low data overhead.

[0029] The heartbeat cycle configuration table is a pre-built mapping table of device types and time parameters stored on the local host. Device types are primarily categorized based on their functional roles in the whole-house control logic and their sensitivity requirements to environmental responses. For example, environmental sensor devices such as temperature and humidity sensors and air quality sensors directly reflect transient changes in the indoor environment; therefore, a shorter basic heartbeat cycle is configured to ensure high-frequency sensing. In contrast, actuator devices such as smart curtain motors and switch panels typically have actions triggered by specific commands and relatively stable states; therefore, a longer basic heartbeat cycle is configured to reduce local area network channel occupancy and device power consumption.

[0030] A preset time window refers to a historical sliding time interval used to statistically analyze communication quality indicators. Its specific span can be preset based on the number of devices in the house and the network throughput capacity; for example, it can be set to the past few minutes or a fixed number of heartbeat rounds. By counting the proportion of unanswered messages within this time window relative to the total number of heartbeat messages sent, the average packet loss rate of the current communication link can be accurately quantified, truly reflecting the transmission reliability of the current local area network wireless channel.

[0031] Environmental interference level refers to the physical interference level caused by electromagnetic noise or frequency contention in the current communication medium to signal transmission. In practice, the environmental interference level can be quantified and calculated using physical layer parameters such as signal-to-noise ratio (SNR), the variance of received signal strength indication (RSSI) fluctuation, or channel utilization ratio in the same frequency band, which are collected in real time by the local host or wireless communication module, thereby characterizing the severity of the wireless environment.

[0032] The periodic correction is a dynamically adjusted parameter generated by weighting and fusing the average packet loss rate at the network layer and the degree of environmental interference at the physical layer using preset weighting coefficients. By subtracting this periodic correction from the basic heartbeat cycle, the adaptive heartbeat cycle can adaptively shrink as the network deteriorates and interference increases.

[0033] This application's embodiments organically combine the inherent functional attributes of the device with the dynamic communication environment, achieving multi-dimensional adaptive adjustment of the heartbeat cycle. On the one hand, differentiated basic heartbeat cycles are allocated based on the characteristic differences between environmental sensor-type and actuator-type target devices, balancing high-sensitivity monitoring with system communication resource overhead. On the other hand, the heartbeat cycle is dynamically shortened based on real-time packet loss rate and environmental interference level, proactively increasing detection density when network fluctuations or interference intensify. This effectively avoids missed detections or misjudgments of communication anomalies caused by fixed acquisition cycles, significantly enhancing the system's fault perception sensitivity and self-healing trigger timeliness in dynamic and complex network environments.

[0034] S2: By using preset fault determination rules, the device operation dataset is compared and analyzed to obtain fault determination results, wherein the fault determination results are used to characterize whether the target device has a fault event and the type of fault event.

[0035] Specifically, the step of comparing and analyzing the equipment operation dataset using preset fault determination rules to obtain fault determination results can be executed by the local control logic. For example, comparing the equipment operation parameters in the equipment operation dataset with a preset static value range table, and determining that an overload or overtemperature fault event exists when the operating current or internal temperature value exceeds the preset value range; or, analyzing the equipment operation dataset using a preset logic state lookup table, and determining that a power supply abnormality fault event exists when the target device's switch state is on but the real-time power detection value is zero; or, performing text matching between the status codes parsed from the equipment operation dataset and the locally fixed fault code library, and determining the specific fault event type based on the matched code.

[0036] In one specific embodiment, the fault event types include communication interruption events, operational abnormality fault events, environmental conflict events, and circuit abnormality events. Environmental conflict events include window opening conflict events and humidification conflict events.

[0037] Please see Figure 2 , Figure 2 A specific implementation of step S2 when the fault event type is a communication interruption fault event is shown below: S211: Determine whether the communication status data in the device operation dataset indicates that the target device has not returned a response message for a preset number of consecutive times, and obtain a heartbeat timeout determination result. S212: When the heartbeat timeout determination result indicates that the target device has not returned a response message for a preset number of consecutive times, mark the target device as a suspected communication interruption state. S213: Send a probe message to the target device in the suspected communication interruption state, and determine whether a response message is received from the target device in response to the probe message within a preset probe timeout period, and obtain a communication interruption confirmation result. S214: When the communication interruption confirmation result indicates that the response message has not been received, generate the communication interruption fault event.

[0038] Specifically, the communication status data in the device operation dataset is used to characterize the interactive response of the target device in periodic communication. The number of consecutive preset counts can be configured according to the specific local area network communication protocol type. For example, it can be set to 3 consecutive counts in a wireless local area network (Wi-Fi) communication environment, and 5 consecutive counts in a low-power local area network (such as ZigBee or Bluetooth Mesh) environment. The method for determining consecutive non-responding messages can be implemented by maintaining a packet loss counter locally. The counter is cleared whenever a normal response message is received, and the counter is incremented whenever a single timeout occurs. When the count reaches the preset number of consecutive counts, the result representing the heartbeat timeout is output. Alternatively, a sliding time window can be used to record the status of the most recent preset number of heartbeat cycles. When all records within the time window are non-responding, it is determined as a heartbeat timeout.

[0039] The suspected communication interruption state serves as an intermediate marker state to isolate intermittently abnormal devices from normal communication devices. This state does not directly trigger resource-intensive communication self-healing actions, but rather serves as a prerequisite for triggering the active detection mechanism to avoid premature intervention measures on the device.

[0040] Probe messages are test data packets specifically used for secondary active verification of link connectivity. In specific implementations, probe messages can use specific unicast probe frames with high priority, or they can use application-layer echo request commands. For the preset probe timeout, a fixed-length countdown window (e.g., set to 3 to 5 seconds) can be used, or a dynamic timeout can be set based on the weighted average of historical round-trip times (RTTs) to reserve sufficient response buffer time for target devices that may be under instantaneous high load.

[0041] Communication interruption fault events are event objects generated after both passive reception timeout and active probe failure conditions are met. When no acknowledgment packet (ACK) or application layer response is received for the probe message within the preset probe timeout period, the local system determines that the physical or logical link between the target device and the host has been substantially interrupted, and then generates a fault event record to guide the subsequent execution of communication self-healing strategies.

[0042] This application's embodiments effectively improve the accuracy of communication fault identification by constructing a multi-level progressive judgment mechanism from passive monitoring to active detection. First, by using a judgment rule based on multiple rounds of consecutive non-responding messages, occasional packet loss caused by spatial electromagnetic interference, sporadic network jitter, or instantaneous channel contention is effectively filtered out. Second, for target devices marked as potentially abnormal, secondary verification is performed by sending targeted probe messages, accurately distinguishing whether the target device's response delay is due to temporary task overload or a substantial link interruption. This hierarchical confirmation logic significantly reduces the false alarm rate of communication faults, ensuring that the self-healing strategy is only activated when the link is confirmed to be truly faulty, avoiding invalid reconnections or frequent link switching caused by misjudgments, and guaranteeing the accuracy and reliability of local self-healing processing.

[0043] Please see Figure 3 , Figure 3 Another specific implementation of step S2 when the fault event type is a runtime abnormality fault event is shown below: S221: Calculate the difference between two adjacent timestamps in the device status data of the device operation dataset to obtain the update time interval, and determine whether the update time interval continuously exceeds a preset duration to obtain a data stagnation determination result. S222: Determine whether the room temperature data and / or indoor humidity data in the environmental data are within a preset reasonable range to obtain a numerical drift determination result. S223: When the data stagnation determination result is that the update time interval continuously exceeds the preset duration, and / or the numerical drift determination result is that the room temperature data and / or the indoor humidity data exceed the preset reasonable range, generate the operational anomaly fault event.

[0044] Specifically, the timestamps in the device status data are used to mark the time information of the target device reporting operating parameters or status variables. Calculating the difference between two adjacent timestamps to obtain the update time interval can be achieved in several ways, such as: reading the target device's timestamps carried in two consecutive device status data frames from local storage and calculating the difference; or having the local host receiving the device status data record the timestamp based on the local system clock of each received data frame and perform a subtraction operation. Regarding the determination of whether the update time interval continuously exceeds a preset duration, the preset duration can be configured according to the target device's preset periodic reporting cycle, for example, configured as a fixed multiple of the reporting cycle. Logically, a continuous timeout counter can be maintained, accumulating the count value each time the update time interval exceeds the preset duration and resetting it to zero when the update time interval returns to normal. When the count value reaches a preset threshold, the data stagnation determination result is determined to be a continuous exceedance of the preset duration, thereby effectively filtering out temporary delay interference caused by occasional network congestion or retransmissions.

[0045] Room temperature and / or indoor humidity data in environmental data are key parameters reflecting the true physical environment of an indoor space. Pre-defined reasonable ranges are used to define effective numerical boundaries that conform to the laws of actual physical environments. To determine whether room temperature and / or indoor humidity data are within the pre-defined reasonable range, a comparison can be made using preset static physical extreme value intervals. For example, the reasonable range for room temperature data can be pre-set to the normal range between extreme cold and extreme heat, and the reasonable range for indoor humidity data can be pre-set to the normal relative humidity limit range. When the collected values ​​exceed these intervals, it is directly determined as numerical drift. Alternatively, a dynamic reasonable range can be set based on the temporal rate of change of environmental data. For example, the slope of change between the currently collected environmental data and the environmental data at the previous collection time can be calculated. When the temperature and humidity fluctuations per unit time exceed the reasonable threshold for actual environmental physical diffusion, it is determined as numerical drift, thus flexibly adapting to the anomaly detection needs in different scenarios.

[0046] In the process of generating abnormal operation failure events, by integrating the determination of the continuity of state updates in the time dimension and the determination of the rationality of numerical logic in the spatial environment dimension, when the data stagnation determination result indicates that the data update is stagnant, or the numerical drift determination result indicates that the numerical is abnormal, or both occur at the same time, the corresponding abnormal operation failure event is generated locally, so as to provide a reliable basis for the accurate triggering of subsequent self-healing strategies.

[0047] This application's embodiments construct a multi-indicator collaborative mechanism for identifying operational anomalies from two dimensions: data update timing and physical sensing values. By continuously detecting timeouts between adjacent timestamps, it can accurately identify silent stagnation faults in target devices caused by main control program freezes, data acquisition thread deadlocks, etc., and avoid misjudgments caused by instantaneous network fluctuations. By verifying the reasonable range of room temperature and indoor humidity data, it can effectively identify abnormal value drifts caused by sensor dampness, aging, or device damage, accurately capturing pseudo-normal states where devices are connected to the network but have lost their sensing effectiveness. The combination of these two approaches significantly improves the accuracy and monitoring coverage of the whole-house smart system in identifying deep-seated, hidden operational faults locally, without the need for external cloud intervention.

[0048] Please see Figure 4 , Figure 4 Another specific implementation of step S2 is shown when the fault event type is a window opening conflict event, as detailed below: S231: Read the operating status of the smart window opener, the operating mode of the air conditioner, and the set temperature from the device status data of the device operation dataset to obtain window opening status data, wherein the operating status of the smart window opener includes the window open / closed state. S232: Calculate the difference between the room temperature data in the environmental data and the set temperature in the window opening status data to obtain a temperature difference value. S233: Determine whether the temperature difference value meets the preset temperature difference condition corresponding to the operating mode of the air conditioner to obtain a temperature difference determination result, wherein the preset temperature difference condition includes a temperature difference value greater than zero when the operating mode is cooling mode and a temperature difference value less than zero when the operating mode is heating mode. S234: When the window open / closed state is "window open," the operating mode is "air condition on," and the temperature difference determination result meets the preset temperature difference condition, count the duration of the window opening conflict. S235: When the duration of the window opening conflict exceeds a first time threshold and the absolute value of the temperature difference is greater than the preset temperature difference value, generate the window opening conflict event.

[0049] Specifically, the operating status of the aforementioned smart window opener can be obtained by detecting the window sash position and generating a status message through the travel limit switch or Hall sensor integrated inside the smart window opener, or by identifying the feedback signal when the window sash reaches the closed or open limit position through the drive current monitoring module of the window opener motor; the operating mode and set temperature of the air conditioner can be directly extracted from the operating parameter register of the air conditioner's main control board, or obtained by parsing the status data packets broadcast by the air conditioner periodically through the home LAN.

[0050] For room temperature data in the environmental data, it can be obtained by periodically sampling using the return air vent temperature sensor built into the air conditioner, or by parsing environmental data packets reported by independent temperature and humidity sensors installed on the indoor walls or by smart thermostats. The temperature difference is calculated using arithmetic subtraction to quantitatively characterize the deviation of the current actual indoor temperature from the air conditioner's set target temperature.

[0051] To track the duration of window-opening conflicts, the system can either use an internal software timer to accumulate time when the initial conflict conditions are met, or record the timestamp of the first detected window opening and abnormal temperature difference, and calculate the difference between the current timestamp and the initial timestamp in subsequent sampling periods. The initial time threshold and preset temperature difference value can be pre-written into the storage medium based on the specific living space volume and energy consumption sensitivity. A numerical comparison logic can then be used to determine whether the current conflict state has reached a stable triggering state.

[0052] This application expands the scope of fault diagnosis from the physical and communication status of a single device to the identification of logical conflicts in multi-device collaborative operation scenarios. By fusing and analyzing multi-source data such as the window opening / closing status of the smart window opener with the air conditioner's operating mode, set temperature, and real-time room temperature data, it can accurately identify energy consumption and regulation conflicts between window ventilation and air conditioning temperature control. Furthermore, by combining a dual filtering mechanism of the duration of the window opening conflict and the absolute value of the temperature difference, it effectively eliminates misjudgments caused by brief window openings or minor fluctuations in ambient temperature, significantly improving the reliability and accuracy of the window opening conflict determination results. This lays a solid foundation for the system to subsequently execute precise local self-healing control.

[0053] S3: If the target device has a fault event, the operating status of the target device is processed by the self-healing strategy corresponding to the fault event type to obtain the self-healing execution result.

[0054] Specifically, if a fault event occurs in the target device, the operating status of the target device is processed through a self-healing strategy corresponding to the fault event type to obtain a self-healing execution result. Specifically, data from multiple sensors is automatically collected, the current environmental conditions are analyzed in real time, and combined with the device's operating status for analysis. Potential environmental conflicts are automatically detected and handled to obtain a self-healing execution result.

[0055] Please see Figure 5 , Figure 5 A specific implementation of step S3 when the fault event type is a window opening conflict event is shown below: S311: If the target device experiences a communication interruption fault event, a reconnection request is sent to the target device, and it is determined whether the communication link should be re-established, obtaining a reconnection result. S312: When the reconnection result indicates that the communication link has been re-established, communication with the target device is restored, and the steps of collecting the target device's operating parameters and indoor environmental data according to a preset collection cycle continue. S313: When the reconnection result indicates that the communication link has not been re-established, the communication between the air conditioner's built-in unit and the target device is switched from the primary communication link to the backup communication link through link switching, and it is determined whether the backup communication link is connected, obtaining a link switching result. S314: When the link switching result indicates that the link is not connected or the backup communication link is unavailable, a default communication parameter configuration instruction is sent to the target device, restoring the target device's communication configuration to the initial communication configuration, and the reconnection request is resent based on the initial communication configuration. S315: When the reconnection result, the link switching result, and the reconnection result obtained again based on the initial communication configuration all indicate failure, push device abnormality prompt information to the user terminal, wherein the device abnormality prompt information includes a manual restart suggestion.

[0056] Specifically, a reconnection request is used to proactively trigger a handshake probe after determining that a device has lost connection, in order to confirm whether the communication link can be restored immediately. The specific form of the reconnection request may include sending a unicast probe message carrying a handshake identifier to the target device, or sending a lightweight status synchronization request frame. The determination of whether to re-establish the communication link can be implemented by listening for an acknowledgment packet returned by the target device within a preset reconnection window period, or by polling to check the connectivity status of the physical communication ports allocated to the target device within the local area network.

[0057] The primary and backup communication links constitute a multi-channel redundant communication path between the air conditioner's built-in host and the target device. The primary and backup communication links can use different operating channels of the same communication standard (e.g., different frequency bands in a Wi-Fi network), or they can use heterogeneous communication protocol media (e.g., using Wi-Fi or Ethernet as the primary communication link and ZigBee, Bluetooth Mesh, or infrared channels as backup communication links). Link switching can be performed by the air conditioner's built-in host modifying its internal routing table to switch the data transmission port, or by broadcasting a wake-up command over the local area network to instruct the target device to synchronously switch to the backup radio frequency channel.

[0058] The default communication parameter configuration command is used to correct communication configuration anomalies in the target device caused by parameter drift or accidental overwriting. The initial communication configuration is the factory-set communication parameter set preset by the target device. The specific implementation of sending the default communication parameter configuration command can be either broadcasting a control command to restore the factory communication parameters to the target device via a reserved out-of-band management channel, or issuing a parameter reset data packet containing the fixed communication baud rate, default network channel number, and initial verification key to forcibly overwrite the target device's currently disordered operating configuration.

[0059] Device anomaly alerts are used to provide precise guidance for manual intervention when automated repair methods fail to restore communication. These alerts can be pushed to user terminals via a local area network (LAN) instant messaging protocol to send alarm pop-ups directly to the linked mobile application, or via a LAN multicast protocol to synchronize operation instructions containing device identification, fault type, and manual restart suggestions to the indoor smart control panel.

[0060] This application's embodiments construct a multi-level, progressively advancing local closed-loop self-healing mechanism for communication interruptions. First, a reconnection request quickly eliminates false disconnections caused by occasional network jitter with minimal overhead. When the main link remains abnormal, a backup communication link is activated via link switching, utilizing heterogeneous or multi-channel redundancy to avoid blockages caused by single-point physical links or localized radio frequency interference. If link switching is still not feasible, a default communication parameter configuration command is issued to restore the device to its known normal initial state, effectively resolving deep deadlock faults caused by parameter configuration disorder. Finally, when automatic methods are exhausted, a clear manual restart suggestion is generated and pushed to the user terminal, significantly improving the network resilience and availability of the whole-house smart system when it is no longer dependent on external cloud environments.

[0061] Please see Figure 6 , Figure 6 Another specific implementation of step S3 is shown when the fault event type is a window opening conflict event, as detailed below: S321: If the target device experiences an operational malfunction, a restart command is sent to the target device where the malfunction occurred. After the target device restarts, the step of collecting the target device's operating parameters and indoor environmental data according to a preset collection cycle is re-executed to obtain restarted device status data and restarted environmental data. S322: If the update time interval represented by the restarted device status data does not exceed the preset duration and the restarted environmental data is within the preset reasonable range, the self-healing execution result is a successful self-healing. S323: If the update time interval represented by the restarted device status data exceeds the preset duration and / or the restarted environmental data exceeds the preset reasonable range, a parameter reset command is sent to the target device to restore it to its initial settings. After restoration, the step of collecting the target device's operating parameters and indoor environmental data according to a preset collection cycle is re-executed to obtain reset device status data and reset environmental data. S324: If the update time interval represented by the reset device status data does not exceed the preset duration and the reset environment data is within the preset reasonable range, then the self-healing execution result is self-healing successful. S325: If the update time interval represented by the reset device status data exceeds the preset duration and / or the reset environment data exceeds the preset reasonable range, a device maintenance prompt message is pushed to the user terminal. When a backup device of the same type as the target device exists, the device maintenance prompt message also includes a query to enable the backup device.

[0062] Specifically, a restart command is a control command that triggers the main control unit or operating system of the target device to re-execute the initialization loading process. Its purpose is to quickly eliminate logical blockages caused by temporary memory leaks, thread deadlocks, or data buffer overflows with minimal system overhead. In practice, the restart command can be implemented by sending a specific formatted application-layer soft reset message to the target device, or by sending a hard restart command to the intelligent power supply unit connected in series with the target device, indicating a power outage followed by power restoration.

[0063] Parameter reset commands are control commands used to eliminate abnormal configuration offsets that occur during the operation of a target device and revert it to a baseline state. Their purpose is to resolve deep anomalies caused by data corruption in non-volatile memory, communication parameter inconsistencies, or calibration parameter drift. In specific implementations, parameter reset commands can either use a factory default configuration overwrite command, where the controller writes the factory preset parameter table to the target device; or they can use a standard configuration script to rewrite the command, overwriting the target device's current operating configuration by re-issuing the standard communication topology and calibration configuration file.

[0064] The equipment maintenance prompts and the prompts to activate backup devices are human-machine collaboration and redundancy fault-tolerance mechanisms triggered after the local automatic recovery mechanism has exhausted all options. In specific implementations, these prompts can be pushed to the user's smart home application via the home LAN, containing structured messages with interactive controls, allowing the user to directly click to confirm and activate the backup device; alternatively, the physical location of the faulty device, fault details, and backup device replacement suggestions can be presented to the user via the local display screen or voice broadcast component of the air conditioner's built-in host.

[0065] This application's embodiments construct a graded self-healing handling and closed-loop verification mechanism for operational anomalies, progressing from minor to severe. First, a lightweight restart command is used to quickly attempt to restore the device's basic operating state. After restarting, a dual comparison of the device update time interval and environmental data enables real-time quantitative verification of the self-healing effect, avoiding omissions due to blind judgment. If restarting proves ineffective, an adaptive upgrade to a parameter reset strategy is implemented to deeply eliminate abnormal parameters and logical conflicts, improving the success rate of fault self-healing without human intervention. When both software and hardware automatic self-healing methods fail, timely maintenance prompts are pushed out, and similar backup devices are seamlessly integrated to ensure that the whole-house smart system maintains the integrity and continuity of its core functions even when the target device faces severe physical damage.

[0066] Please see Figure 7 , Figure 7 Another specific implementation of step S3 is shown when the fault event type is a window opening conflict event, as detailed below: S331: If the target device experiences the window opening conflict event, a window closing confirmation prompt is pushed to the user terminal. The window closing confirmation prompt includes a preset confirmation time and optional operation items, including closing the window immediately, maintaining ventilation, and turning off the air conditioner. S332: Determine whether an operation command returned by the user terminal is received within the preset confirmation time. If received, match the operation command with the optional operation items to obtain a user response result. S333: If the user response result indicates that no operation command was received within the preset confirmation time and the window opening conflict event persists, send a window closing control command to the smart window opener and determine whether the window opening / closing state changes from open to closed to obtain a window closing result. S334: If the user response result indicates that the operation command matches "maintain ventilation," do not send the window closing control command to the smart window opener within a preset suppression time, and reduce the operating intensity of the air conditioner or switch the air conditioner's operating mode to a ventilation mode.

[0067] Specifically, the window-closing confirmation prompt is an information interaction carrier used to achieve human-machine collaborative decision-making. Methods for pushing window-closing confirmation prompts to user terminals can include: sending pop-up notifications or instant push messages to user terminals (such as mobile terminals or smart control panels) that have established communication connections with the air conditioner's built-in main unit via a local area network; or providing voice prompts via a local voice interaction device, thereby presenting the user with an interface or voice options that include a preset confirmation time (e.g., 60 seconds or 120 seconds) and various selectable operation items.

[0068] The step of receiving and matching operation instructions returned by the user terminal within a preset confirmation time is mainly responsible for parsing the user's intent in real time and triggering the corresponding control flow. Its implementation includes: listening to control messages from the user terminal, extracting the function operation codes from the messages and mapping them to predefined optional operation item codes (such as immediately closing windows, keeping ventilation open, turning off the air conditioner, etc.); or parsing the instruction tags generated by the user clicking through the graphical user interface and determining the matching result based on the tag type.

[0069] The steps for sending a window-closing control command to the smart window opener and determining the window's open / closed status when the user does not respond serve to achieve a self-healing, closed-loop safety system without human intervention. This is achieved by: the air conditioner's built-in unit sending a closing command to the smart window opener's drive unit via a wireless communication link; subsequently, by reading the limit switch status reported by the smart window opener, or by receiving physical opening / closing signals from door and window magnetic sensors installed in the window frame, determining whether the window's open / closed status has successfully transitioned to a closed state.

[0070] The procedure of not sending window-closing control commands and adjusting air conditioning operation within a preset suppression time while maintaining ventilation aims to balance the user's subjective ventilation needs with system energy saving and consumption reduction. This is achieved by: the system starting a timer to block automatic closing commands for smart window openers within a preset suppression time (e.g., 30 or 60 minutes); during this period, reducing the air conditioning operating intensity by directly lowering the air conditioning compressor's operating frequency, reducing the fan speed, or directly switching the air conditioning operation mode to a lower-energy-consumption pure air supply mode.

[0071] This application embodiment achieves refined closed-loop management of window opening conflict events by introducing a human-computer interaction confirmation mechanism and differentiated automatic handling strategies. First, after identifying a window opening conflict event, a confirmation prompt message containing multiple optional operation items is pushed to the user, giving the user the decision-making power in advance and avoiding interference with the user's subjective will and personalized ventilation experience caused by mechanically forcibly closing the window. Second, if the user does not respond within the preset confirmation time, the system can autonomously execute a closed-loop self-healing process that sends a window closing control command to the smart window opener and monitors the closing result, ensuring that environmental conflicts such as heat loss are eliminated in a timely manner without human intervention, effectively avoiding energy waste caused by the air conditioner continuously operating ineffectively with the window open. Finally, for special scenarios where the user actively chooses to maintain ventilation, the automatic window closing is paused by setting a preset suppression time, and the air conditioner's operating intensity is simultaneously reduced or switched to air supply mode. While fully respecting the user's ventilation needs, a dynamic balance is achieved between indoor environmental regulation and energy-saving operation of equipment, significantly improving the intelligence level and environmental adaptability of the local self-healing of smart devices throughout the house.

[0072] Furthermore, environmental conflict failure events include humidification conflict events; In the determination step, the humidification conflict event is obtained as follows: It is determined whether the indoor humidity data in the environmental data exceeds a preset humidity threshold, thus obtaining a humidity exceeding the threshold determination result; when the humidity exceeding the threshold determination result indicates that the indoor humidity data exceeds the preset humidity threshold, and the humidifier's operating status in the device status data indicates that the humidifier is in operation, the duration of this state is timed to obtain the duration of the humidification conflict, where the humidifier's operating status includes the humidifier's running status; when the duration of the humidification conflict reaches a second time threshold, a humidification conflict event is generated. In the self-healing process, the self-healing strategy corresponding to the humidification conflict event includes: sending a shutdown command to the humidifier and determining whether the humidifier's operating status changes from indicating that the humidifier is in an operating state to indicating that the humidifier is in a stopped state, thus obtaining the humidifier shutdown result; pushing the current humidity status prompt information to the user terminal, which includes indoor humidity data and the humidifier shutdown result.

[0073] Specifically, the preset humidity threshold is a benchmark value used to define whether the indoor relative humidity is at a comfortable or safe upper limit. In practice, the preset humidity threshold can be preset to a fixed upper limit value for comfortable humidity, or it can be dynamically configured and issued according to the current seasonal mode, changes in outdoor temperature and humidity, or user-defined personalized comfort ranges.

[0074] The second time threshold is used to filter out transient interference caused by short-term humidity fluctuations or localized water vapor accumulation, ensuring the stability and accuracy of humidification conflict determination. In specific implementation, the duration of humidification conflict can be timed by maintaining a local hardware or software timer to periodically accumulate as the exceeding conditions are continuously met, or by recording the start timestamp of the first detection of humidity exceeding the standard and the humidifier being in operation and calculating the difference with the current collection timestamp. The second time threshold can be set as a fixed anti-shake delay parameter, or it can be adaptively adjusted based on the room volume, current ventilation conditions, and humidity rise rate.

[0075] The process of sending a shutdown command to the humidifier and determining its status constitutes a control closed loop. In specific implementations, the shutdown command can be sent directly to the humidifier via a local area network using wireless communication protocols (such as Wi-Fi, ZigBee, or Bluetooth Mesh protocols) to send a shutdown control message or a power-off command. The determination of whether the humidifier's operating state has changed to a stopped state can be confirmed by the operation response message returned by the humidifier, or by cross-checking and confirming the humidifier's real-time operating current and power feedback data, or by reading the humidifier's device status data in the next acquisition cycle.

[0076] The current humidity status notification is used to achieve human-machine collaboration and status transparency. In specific implementations, this notification can be pushed to the user terminal in ways such as displaying it as a system notification pop-up through a mobile application, generating a status notification card on the control panel, or linking with indoor smart voice devices for voice broadcasting, allowing users to intuitively understand the current humidity level exceeding the standard and the humidifier's shutdown status.

[0077] This application embodiment deeply correlates the actual indoor humidity environment monitoring with the humidifier's own operating status and introduces a duration determination mechanism to effectively avoid system malfunctions caused by short-term local humidity disturbances and accurately identify environmental conflicts caused by continuous excessive operation of the humidifier. During the self-healing execution phase, by issuing a shutdown command and detecting changes in the humidifier's operating status in real time, a closed-loop verification of self-healing control is achieved, preventing the inability to resolve faults due to the loss of one-way commands. At the same time, by synchronously pushing prompts containing environmental data and equipment handling results to the user terminal, the transparency of equipment handling and the safety of whole-house environmental regulation are significantly improved.

[0078] Furthermore, this application also provides a feedback step: The fault event type, the communication status data on which the fault determination result is based, the device status data and the environmental data, the sending order of the self-healing control command, and the self-healing execution result are associated and stored in the local memory of the air conditioner's built-in host to obtain a fault file. Based on the communication status data in the fault file, the preset collection period is re-determined to obtain the corrected preset collection period. The corrected preset collection period is used to subsequently execute the step of collecting the target device's operating parameters and indoor environment data according to the preset collection period. The historical success rate of each self-healing strategy is obtained by comparing the total number of times each self-healing strategy is executed in the fault file with the number of times the self-healing execution result indicates successful self-healing. The self-healing strategies corresponding to the same type of fault event are reordered according to the historical success rate from high to low to obtain the adjusted self-healing strategy execution priority. The adjusted self-healing strategy execution priority is used to determine the execution order of the self-healing strategies when the same type of fault event is generated in the future.

[0079] Specifically, the associated storage can be recorded using a structured key-value database or a lightweight embedded relational database, with the unique identifier and timestamp of the fault event as the primary key, and the diagnostic context data and execution sequence packaged and solidified. Alternatively, the serialized fault data packets can be stored in non-volatile storage media using log appending files. This step provides the necessary data benchmark for local system state tracing and subsequent parameter evolution.

[0080] In the process of re-determining the preset acquisition period based on the communication status data in the fault file, the specific implementation method can be to dynamically update the period value used for subsequent acquisitions by looking up a table based on the historical communication packet loss and retry frequency recorded in the fault file; or, alternatively, a sliding window mean function relating communication response delay and packet loss rate can be constructed to adaptively shorten or extend the acquisition interval to obtain the corrected preset acquisition period. This processing is used to adaptively encrypt sampling to prevent missed detections when the target device is in an unstable communication environment, or to appropriately reduce the polling frequency to save local area network bandwidth when communication is stable.

[0081] In the process of calculating the historical success rate of each self-healing strategy in the fault file and adjusting its priority, a specific implementation method can be to use a sliding time window to only count data within a preset historical period, or to introduce a time decay weighting factor to give higher weight to recent self-healing execution results, so as to calculate the effective success rate of each strategy; then, the strategy index list is reconstructed through a descending sorting algorithm and dynamically written into the local control strategy routing table of the air conditioner's built-in host. When a similar fault event is triggered again, the system can allocate self-healing instructions in the optimal order according to the adjusted execution priority.

[0082] This application's embodiments achieve self-evolution of the whole-house smart device local self-healing system by introducing a closed-loop feedback mechanism locally in the air conditioner's built-in host, which includes fault profile construction, dynamic correction of the data acquisition cycle, and priority reordering of self-healing strategies. On the one hand, the data acquisition cycle is dynamically adjusted based on feedback from the actual communication status in the fault profile, overcoming the shortcomings of fixed cycles that cannot adapt to dynamic network fluctuations, ensuring monitoring timeliness while taking into account network load. On the other hand, the execution order of self-healing strategies for similar faults is dynamically optimized based on historical success rates, enabling the system to prioritize the self-healing methods that perform best in the current home physical environment in a purely local operation scenario without cloud intervention. This significantly shortens the fault self-healing time and increases the success probability of multi-strategy cascading processing, effectively enhancing the robustness of the whole-house smart system's long-term local autonomous operation.

[0083] In a typical home application scenario, the room is equipped with an air conditioner, a smart window opener, a humidifier, and an indoor temperature and humidity sensor. The air conditioner's built-in main unit acts as the local control core, establishing a local area network communication connection with the smart window opener, humidifier, and indoor temperature and humidity sensor.

[0084] During the data acquisition phase, the air conditioner's built-in host sends heartbeat messages to the smart window opener, humidifier, and indoor temperature and humidity sensors according to a preset acquisition cycle, and collects operational status data. This yields a device operation dataset including device online status, window open / close status, humidifier operating status, air conditioner operating mode and set temperature, indoor temperature data, and indoor humidity data. Specifically, the air conditioner's built-in host queries a heartbeat cycle configuration table based on device type to obtain the basic heartbeat cycle. This ensures that the basic heartbeat cycle for environmental sensor devices is shorter than that for actuator devices. Furthermore, it calculates a cycle correction based on the statistically average packet loss rate and the degree of environmental interference. The adaptive heartbeat cycle is obtained by subtracting the cycle correction from the basic heartbeat cycle.

[0085] During the fault diagnosis phase, the air conditioner's built-in main unit locally calls preset fault diagnosis rules to compare and analyze the equipment's operating dataset: Regarding the communication link status, when an indoor temperature and humidity sensor fails to return a response message for a preset number of consecutive times, it is marked as a suspected communication interruption and a probe message is sent to it; if no response message is received within the preset probe timeout period, a communication interruption fault event is generated locally.

[0086] Regarding the equipment's operating status, when the difference between two consecutive timestamps in the data reported by the indoor temperature and humidity sensor exceeds a preset duration, or when the detected indoor temperature data exceeds a preset reasonable range, an abnormal operation fault event is generated locally.

[0087] Regarding device collaboration, when the smart window opener is detected to be open, the air conditioner is in cooling mode, and the indoor temperature is higher than the set temperature, and this state lasts for more than a first time threshold and the absolute value of the temperature difference is greater than a preset temperature difference value, a window opening conflict event is generated locally. When the indoor humidity data is detected to exceed a preset humidity threshold and the humidifier is running for a duration that reaches a second time threshold, a humidification conflict event is generated locally.

[0088] During the self-healing execution phase, the air conditioner's built-in main unit matches the corresponding self-healing strategy based on the determined fault event type: When a communication interruption failure event is determined, the air conditioner's built-in host first sends a reconnection request to the target device; if the reconnection fails, the communication is switched from the primary communication link to the backup communication link; if the backup communication link is unavailable, a default communication parameter configuration command is sent to the target device to restore the initial configuration and attempt to reconnect again; if all reconnection attempts fail, a device error message containing a manual restart suggestion is pushed to the user terminal.

[0089] When an abnormal operation is detected, the air conditioner's built-in main unit sends a restart command to the target device and re-collects data after restarting. If the data remains stagnant or exceeds the limit after restarting, a parameter reset command is sent to restore it to its initial settings. If the data still does not recover after resetting, a device maintenance prompt message and an option to activate the backup device are pushed to the user terminal.

[0090] When a window opening conflict is detected, the air conditioner's built-in main unit pushes a window closing confirmation message to the user's terminal, including options to close the window immediately, keep the ventilation open, and turn off the air conditioner. If no instruction is received within the preset confirmation time and the conflict continues, the air conditioner's built-in main unit directly sends a window closing control instruction to the smart window opener. If the user chooses to keep the ventilation open, the air conditioner's built-in main unit directly switches the air conditioner mode to the air supply mode or reduces the operating intensity.

[0091] When a humidification conflict is detected, the air conditioner's built-in main unit sends a shutdown command to the humidifier and pushes a notification message containing the current humidity data and shutdown result to the user terminal after confirming that the humidifier has stopped running.

[0092] In this process, compared to the existing architecture that relies on an independent gateway to upload data to a cloud server for calculation, and then the cloud server sends instructions to the independent gateway, this solution allows the air conditioner's built-in host to independently complete the entire closed-loop process of device data acquisition, fault type determination, and self-healing strategy execution locally. Even in the event of an external network outage or cloud server unavailability, the system maintains local monitoring and fault self-healing capabilities, and can directly adjust the air conditioner's own operating mode and intensity, eliminating dependence on cloud servers and independent gateways.

[0093] After the self-healing process is completed, the air conditioner's built-in host will associate and store the fault event type, judgment basis data, self-healing control command execution sequence, and self-healing execution result in local memory to generate a fault file. The air conditioner's built-in host will adjust the subsequent preset collection cycle based on the communication status data in the fault file, and will also calculate the historical success rate of each handling strategy, adjusting the execution priority of the self-healing strategy corresponding to the same type of fault event according to the success rate from high to low.

[0094] This invention also provides a local self-healing device for whole-house smart device malfunctions, which is used to execute any embodiment of the aforementioned local self-healing method for whole-house smart device malfunctions. Specifically, please refer to... Figure 8 , Figure 8 This is a schematic block diagram of a local self-healing device for whole-house smart device malfunctions provided in an embodiment of the present invention.

[0095] Among them, such as Figure 8 As shown, the local self-healing device 4 for whole-house smart device malfunctions includes a data acquisition module 41, a fault determination module 42, and a fault self-healing module 43.

[0096] Data acquisition module 41 is used to collect the operating parameters and indoor environmental data of the target equipment according to a preset acquisition cycle to obtain the equipment operation dataset; The fault determination module 42 is used to compare and analyze the equipment operation dataset according to the preset fault determination rules to obtain the fault determination result, wherein the fault determination result is used to characterize whether the target equipment has a fault event and the type of fault event; The fault self-healing module 43 is used to process the operating status of the target device according to the self-healing strategy corresponding to the fault event type if the target device has a fault event, and obtain the self-healing execution result.

[0097] Furthermore, when the fault event type is a communication interruption fault event, the fault determination module 42 includes: The heartbeat timeout determination result generation unit is used to determine whether the communication status data in the device operation dataset indicates that the target device has not returned a response message for a preset number of consecutive times, and to obtain the heartbeat timeout determination result. A suspected communication interruption status marking unit is used to mark the target device as a suspected communication interruption status when the heartbeat timeout determination result is that the target device has not returned a response message for a preset number of consecutive times; The communication interruption confirmation result generation unit is used to send a probe message to the target device in the suspected communication interruption state, and determine whether the response message returned by the target device in response to the probe message is received within a preset probe timeout period, so as to obtain the communication interruption confirmation result. A communication interruption fault event generation unit is used to generate the communication interruption fault event when the communication interruption confirmation result is that the response message has not been received.

[0098] Furthermore, when the fault event type is a communication interruption fault event, the fault self-healing module 43 includes: The device reconnection unit is used to send a reconnection request to the target device if the target device has the communication interruption fault event, and to determine whether to re-establish the communication link and obtain the reconnection result. The link reconstruction unit is used to restore communication with the target device and continue to execute the data acquisition steps of the data acquisition module 41 when the reconnection result is to re-establish the communication link; The link switching unit is used to switch the communication between the air conditioner's built-in host and the target device from the main communication link to the backup communication link when the reconnection result is that the communication link has not been re-established, and to determine whether the backup communication link is connected, thereby obtaining the link switching result. The reconnection request sending unit is used to send a default communication parameter configuration instruction to the target device when the link switching result is disconnected or the backup communication link is unavailable, so that the communication configuration of the target device is restored to the initial communication configuration, and resend the reconnection request based on the initial communication configuration; An error message push unit is used to push device error messages to the user terminal when the reconnection result, the link switching result, and the reconnection result obtained again based on the initial communication configuration all indicate failure. The device error messages include a manual restart suggestion.

[0099] Furthermore, when the fault event type is an operational abnormality fault event, the fault determination module 42 includes: The update time interval calculation unit is used to calculate the difference between two adjacent timestamps in the device status data of the device operation dataset to obtain the update time interval, and to determine whether the update time interval continuously exceeds a preset duration to obtain a data stagnation determination result. The numerical drift determination result generation unit is used to determine whether the room temperature data and / or indoor humidity data in the environmental data are within a preset reasonable range, and to obtain the numerical drift determination result. An abnormal operation fault event generation unit is used to generate the abnormal operation fault event when the data stagnation determination result is that the update time interval continuously exceeds the preset duration, and / or the numerical drift determination result is that the room temperature data and / or the indoor humidity data exceed the preset reasonable range.

[0100] Furthermore, when the fault event type is the operational abnormality fault event, the fault self-healing module 43 includes: The restart command sending unit is used to send a restart command to the target device that has the abnormal operation fault event if the target device has the abnormal operation fault event, and to re-execute the data acquisition module 41 acquisition steps after the target device restarts to obtain the device status data and the environment data after restarting. The first self-healing success determination unit is used to determine that the self-healing execution result is successful when the update time interval represented by the device status data after restart does not exceed the preset duration and the environmental data after restart is within the preset reasonable range. The reset instruction sending unit is used to send a parameter reset instruction to the target device when the update time interval represented by the restarted device status data exceeds the preset duration and / or the restarted environment data exceeds the preset reasonable range, so that the target device is restored to the initial setting, and after restoration, the data acquisition module 41 re-executes the acquisition steps to obtain the reset device status data and the reset environment data. The second self-healing success determination unit is used to determine the self-healing success result when the update time interval represented by the reset device status data does not exceed the preset duration and the reset environment data is within the preset reasonable range. The maintenance reminder information push unit is used to push equipment maintenance reminder information to the user terminal when the update time interval represented by the reset equipment status data exceeds the preset duration and / or the reset environmental data exceeds the preset reasonable range. When there is a backup device of the same type as the target device, the equipment maintenance reminder information also includes an option to enable the backup device.

[0101] Furthermore, when the fault event type is a window opening conflict event, the fault determination module 42 includes: The window opening status data reading unit is used to read the working status of the smart window opener, the operating mode of the air conditioner and the set temperature from the device status data of the device operation dataset to obtain window opening status data, wherein the working status of the smart window opener includes the window opening / closing status. The temperature difference calculation unit is used to calculate the difference between the room temperature data in the environmental data and the set temperature in the window opening status data to obtain the temperature difference value. A temperature difference determination result generation unit is used to determine whether the temperature difference value meets the preset temperature difference condition corresponding to the operating mode of the air conditioner, and to obtain a temperature difference determination result. The preset temperature difference condition includes the temperature difference value being greater than zero when the operating mode is cooling mode and the temperature difference value being less than zero when the operating mode is heating mode. The conflict duration statistics unit is used to count the duration of the window opening conflict when the window opening state is open, the operating mode is the air conditioner is on, and the temperature difference determination result is that the preset temperature difference condition is met. The window opening conflict event generation unit is used to generate the window opening conflict event when the duration of the window opening conflict exceeds a first time threshold and the absolute value of the temperature difference is greater than a preset temperature difference value.

[0102] Furthermore, when the fault event type is the window opening conflict event, the fault self-healing module 43 includes: A confirmation prompt message push unit is used to push a window closing confirmation prompt message to the user terminal if the target device has the window opening conflict event. The window closing confirmation prompt message includes a preset confirmation time and optional operation items, and the optional operation items include closing the window immediately, keeping the ventilation open, and turning off the air conditioner. The user response result generation unit is used to determine whether the operation instruction returned by the user terminal is received within the preset confirmation time, and when received, to match the operation instruction with the optional operation item to obtain the user response result; The window closing result generation unit is used to send a window closing control command to the smart window opener when the user response result is that no operation command is received within the preset confirmation time and the window opening conflict event continues to exist, and to determine whether the window opening and closing state has changed from window open to window closed, so as to obtain the window closing result. The mode switching unit is used to, when the user response result is that the operation command matches the "keep ventilation" command, not send the window closing control command to the smart window opener within a preset suppression time, and reduce the operating intensity of the air conditioner, or switch the operating mode of the air conditioner to the air supply mode.

[0103] The aforementioned local self-healing device for malfunctions of smart home devices can be implemented as a computer program, which can, for example... Figure 9 The air conditioner shown is running.

[0104] Please see Figure 9 , Figure 9 This is a schematic block diagram of an air conditioner provided in an embodiment of the present invention. The air conditioner 500 includes a processor 502, a memory, and a network interface 505 connected via a device bus 501, wherein the memory may include a storage medium 503 and an internal memory 504.

[0105] The storage medium 503 may store an operating system 5031 and a computer program 5032. When the computer program 5032 is executed, it enables the processor 502 to perform a local self-healing method for malfunctions of smart home devices.

[0106] The processor 502 provides computing and control capabilities to support the operation of the entire air conditioner 500.

[0107] The internal memory 504 provides an environment for the operation of the computer program 5032 in the storage medium 503. When the computer program 5032 is executed by the processor 502, the processor 502 can perform a local self-healing method for faults in the whole-house smart devices.

[0108] The network interface 505 is used for network communication, such as providing data information transmission. Those skilled in the art will understand that the structures shown in the embodiments of this application are merely block diagrams of some structures related to the present invention and do not constitute a limitation on the air conditioner 500 to which the present invention is applied. A specific air conditioner 500 may include more or fewer components than shown in the figures, or combine certain components, or have different component arrangements.

[0109] The processor 502 is used to run the computer program 5032 stored in the memory to implement the local self-healing method for whole-house smart device faults disclosed in the embodiments of the present invention.

[0110] Those skilled in the art will understand that the air conditioner embodiments shown in this application do not constitute a limitation on the specific structure of the air conditioner. In other embodiments, the air conditioner may include more or fewer components than shown, or combine certain components, or have different component arrangements. For example, in some embodiments, the air conditioner may only include a memory and a processor. In such embodiments, the structure and function of the memory and processor are consistent with those shown in the above embodiments, and will not be repeated here.

[0111] It should be understood that, in this embodiment of the invention, the processor 502 may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0112] In another embodiment of the invention, a computer-readable storage medium is provided. This computer-readable storage medium may be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. The computer-readable storage medium stores a computer program, wherein when executed by a processor, the computer program implements the local self-healing method for whole-house smart device malfunctions disclosed in embodiments of the invention.

[0113] Those skilled in the art will readily understand that, for the sake of convenience and brevity, the specific working processes of the devices, apparatuses, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this invention.

[0114] In the embodiments provided by this invention, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Units with the same function may be grouped into one unit. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, or may be electrical, mechanical, or other forms of connection.

[0115] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of the present invention, depending on actual needs.

[0116] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0117] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of this invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an air conditioner (which may be a personal computer, a backend server, or a network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a magnetic disk, or an optical disk.

[0118] The above are merely specific embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A local self-healing method for faults in whole-house smart devices, characterized in that, include: Collect the target equipment's operating parameters and indoor environmental data according to the preset collection cycle to obtain the equipment operation dataset; By comparing and analyzing the equipment operation dataset using preset fault determination rules, a fault determination result is obtained. The fault determination result is used to characterize whether the target equipment has a fault event and the type of fault event. If the target device has a fault event, the operating status of the target device is processed by the self-healing strategy corresponding to the fault event type to obtain the self-healing execution result.

2. The local self-healing method for whole-house smart device faults according to claim 1, characterized in that, When the fault event type is a communication interruption fault event, the step of comparing and analyzing the device operation dataset according to preset fault determination rules to obtain a fault determination result includes: Determine whether the communication status data in the device operation dataset indicates that the target device has not returned a response message for a preset number of consecutive times to obtain a heartbeat timeout determination result; When the heartbeat timeout determination result is that the target device fails to return a response message for a preset number of consecutive times, the target device is marked as a suspected communication interruption state; Send a probe message to the target device that is in the suspected communication interruption state, and determine whether the response message returned by the target device in response to the probe message is received within a preset probe timeout period to obtain a communication interruption confirmation result; When the communication interruption confirmation result is that the response message has not been received, the communication interruption fault event is generated.

3. The local self-healing method for whole-house smart device faults according to claim 2, characterized in that, When the fault event type is a communication interruption fault event, if the target device has a fault event, the operating state of the target device is processed through the self-healing strategy corresponding to the fault event type to obtain a self-healing execution result, including: If the target device experiences a communication interruption failure event, a reconnection request is sent to the target device, and it is determined whether to re-establish the communication link to obtain the reconnection result. When the reconnection result is the re-establishment of the communication link, communication with the target device is restored and the step of collecting the target device's operating parameters and indoor environmental data according to the preset collection cycle continues; When the reconnection result is that the communication link is not re-established, the communication between the air conditioner's built-in host and the target device is switched from the main communication link to the backup communication link through link switching, and it is determined whether the backup communication link is connected to obtain the link switching result; When the link switching result is disconnected or the backup communication link is unavailable, a default communication parameter configuration instruction is sent to the target device to restore the communication configuration of the target device to the initial communication configuration, and the reconnection request is resent based on the initial communication configuration; When the reconnection result, the link switching result, and the reconnection result obtained again based on the initial communication configuration all indicate failure, a device abnormality prompt message is pushed to the user terminal, wherein the device abnormality prompt message includes a manual restart suggestion.

4. The local self-healing method for whole-house smart device faults according to claim 1, characterized in that, When the fault event type is an operational anomaly fault event, the step of comparing and analyzing the equipment operation dataset according to preset fault determination rules to obtain a fault determination result includes: The difference between two adjacent timestamps in the device status data of the device operation dataset is calculated to obtain the update time interval, and it is determined whether the update time interval continuously exceeds the preset duration to obtain the data stagnation determination result; Determine whether the room temperature data and / or indoor humidity data in the environmental data are within a preset reasonable range to obtain the numerical drift determination result; When the data stagnation determination result is that the update time interval continuously exceeds the preset duration, and / or the numerical drift determination result is that the room temperature data and / or the indoor humidity data exceed the preset reasonable range, the abnormal operation fault event is generated.

5. The local self-healing method for whole-house smart device faults according to claim 4, characterized in that, When the fault event type is the operational anomaly fault event, if the target device has a fault event, the operating state of the target device is processed through the self-healing strategy corresponding to the fault event type to obtain a self-healing execution result, including: If the target device has the abnormal operation fault event, a restart command is sent to the target device that has the abnormal operation fault event, and after the target device restarts, the step of collecting the target device's operating parameters and indoor environmental data according to the preset collection cycle is re-executed to obtain the device status data and the environmental data after restart; If the update time interval represented by the device status data after restart does not exceed the preset duration and the environmental data after restart is within the preset reasonable range, then the self-healing execution result is self-healing successful. When the update time interval represented by the restarted device status data exceeds the preset duration and / or the restarted environmental data exceeds the preset reasonable range, a parameter reset command is sent to the target device to restore the target device to its initial settings. After restoration, the step of collecting the target device's operating parameters and indoor environmental data according to the preset collection cycle is re-executed to obtain the reset device status data and reset environmental data. If the update time interval represented by the reset device status data does not exceed the preset duration and the reset environment data is within the preset reasonable range, then the self-healing execution result is self-healing successful. When the update time interval represented by the reset device status data exceeds the preset duration and / or the reset environment data exceeds the preset reasonable range, a device maintenance prompt message is pushed to the user terminal. When there is a backup device of the same type as the target device, the device maintenance prompt message also includes an option to enable the backup device.

6. The local self-healing method for whole-house smart device malfunctions according to any one of claims 1 to 5, characterized in that, When the fault event type is a window opening conflict event, the fault determination result is obtained by comparing and analyzing the equipment operation dataset according to preset fault determination rules, including: The working status of the smart window opener, the operating mode of the air conditioner, and the set temperature are read from the device status data of the device operation dataset to obtain the window opening status data, wherein the working status of the smart window opener includes the window opening / closing status. The temperature difference value is obtained by calculating the difference between the room temperature data in the environmental data and the set temperature in the window opening status data; Determine whether the temperature difference value meets the preset temperature difference condition corresponding to the operating mode of the air conditioner, and obtain the temperature difference determination result. The preset temperature difference condition includes the temperature difference value being greater than zero when the operating mode is cooling mode and the temperature difference value being less than zero when the operating mode is heating mode. When the window switch status is open, the operating mode is the air conditioner is on, and the temperature difference determination result is that the preset temperature difference condition is met, the duration of the window opening conflict is recorded. When the duration of the window opening conflict exceeds a first time threshold and the absolute value of the temperature difference is greater than a preset temperature difference value, the window opening conflict event is generated.

7. The local self-healing method for whole-house smart device faults according to claim 6, characterized in that, When the fault event type is the window opening conflict event, if the target device has a fault event, the operating state of the target device is processed through the self-healing strategy corresponding to the fault event type to obtain the self-healing execution result, including: If the target device has the window opening conflict event, push a window closing confirmation prompt message to the user terminal. The window closing confirmation prompt message includes a preset confirmation time and optional operation items, which include closing the window immediately, keeping the ventilation open, and turning off the air conditioner. Determine whether an operation instruction returned by the user terminal is received within the preset confirmation time, and if received, match the operation instruction with the optional operation item to obtain the user response result; When the user response result is that no operation instruction is received within the preset confirmation time and the window opening conflict event continues, a window closing control instruction is sent to the smart window opener, and it is determined whether the window opening / closing state changes from window open to window closed, thus obtaining the window closing result; When the user response result is that the operation command matches the "keep ventilation" command, the window closing control command will not be sent to the smart window opener within a preset suppression time, and the operating intensity of the air conditioner will be reduced, or the operating mode of the air conditioner will be switched to the air supply mode.

8. A local self-healing device for malfunctions of whole-house smart devices, characterized in that, include: The data acquisition module is used to collect the operating parameters and indoor environmental data of the target equipment according to a preset acquisition cycle to obtain the equipment operation dataset; The fault determination module is used to compare and analyze the equipment operation dataset according to preset fault determination rules to obtain fault determination results, wherein the fault determination results are used to characterize whether the target equipment has a fault event and the type of fault event; The fault self-healing module is used to process the operating status of the target device according to the self-healing strategy corresponding to the fault event type if the target device has a fault event, and obtain the self-healing execution result.

9. An air conditioner, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements a local self-healing method for whole-house smart device malfunctions as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, causes the processor to perform a local self-healing method for whole-house smart device malfunctions as described in any one of claims 1 to 7.