Knx device monitoring method based on we link gateway and gateway

Abstract

The application discloses a KNX device monitoring method and gateway based on a WeLink gateway, and is applied to the WeLink gateway and comprises the following steps: receiving channel connection information and configuration information of a first target KNX device; the configuration information contains group address information of the device; the configuration information is stored based on a pre-constructed collection protocol; a communication connection with the first target KNX device is established based on the channel connection information and the configuration information; an engineering value is obtained according to the group address information of the first target KNX device, the engineering value is integrated with the configuration information of the first target KNX device based on the collection protocol, and monitoring data is obtained and uploaded to an Internet of Things platform; a control command containing group address information of a second target KNX device is obtained from the Internet platform, and the control command is sent to the second target KNX device. Through the application, the data collection efficiency of the KNX device is greatly improved, and the professional ability requirement of the staff is not high.

Description

Technical Field

[0001] This application relates to the field of smart home technology, and in particular to a KNX device monitoring method and gateway based on a WeLink gateway. Background Technology

[0002] KNX is an officially approved open international standard for residential and building control. As a next-generation fieldbus technology, the KNX bus, with its advantages of good interoperability and openness, simple and mature communication mechanisms, and support for multiple communication media, has begun to be applied in the automatic monitoring of numerous building equipment, including lighting, blinds, security systems, energy management, heating, ventilation, air conditioning systems, signaling and monitoring systems, service interfaces and building control systems, remote control, metering, video and audio control, and large household appliances. Devices controlled using the KNX bus are called KNX devices, and KNX devices are widely used in public buildings and residential homes. Therefore, how to monitor KNX devices is receiving increasing attention.

[0003] In existing technologies, KNX monitoring generally relies on KNX system tools. Specific software is required during the system engineering implementation and configuration process. Therefore, to monitor KNX devices, the corresponding software must first be obtained. The configuration and debugging of KNX devices and software require highly specialized personnel. This method is time-consuming and labor-intensive, resulting in low efficiency in monitoring KNX devices. Furthermore, this software places high demands on the professional skills of the personnel. Summary of the Invention

[0004] Based on this, a KNX device monitoring method and gateway based on WeLink gateway are provided to solve the problems of low efficiency in monitoring KNX devices and high requirements for the professional skills of staff.

[0005] Firstly, a KNX device monitoring method based on a WeLink gateway, applied to a WeLink gateway in an Internet of Things (IoT) system, the method comprising:

[0006] Receive channel connection information and configuration information of the first target KNX device; the configuration information of the first target KNX device includes the group address information of the first target KNX device; the configuration information of the first target KNX device is stored based on a pre-built acquisition protocol;

[0007] Based on the channel connection information and the configuration information of the first target KNX device, a communication connection is established with the first target KNX device;

[0008] Based on the integration of the engineering value of the first target KNX device and the configuration information of the first target KNX device, the first target address information is obtained to acquire the engineering value of the first target KNX device. Based on the acquisition protocol, the monitoring data of the first target KNX device is uploaded to the Internet of Things platform.

[0009] The system obtains a control command generated by the IoT platform that contains the group address information of the second target KNX device, and sends the control command to the second target KNX device.

[0010] Optionally, in the above scheme, the channel connection information includes the IP information and port information of the first target KNX device and the local IP of the WeLink gateway.

[0011] Optionally, in the above scheme, the configuration information of the first target KNX device may also include the internal ID, channel ID, device name, measurement point description, configuration description, and data type of the target KNX device.

[0012] Optionally, in the above scheme, the control commands are concatenated and processed into hexadecimal information and sent to the second target KNX device.

[0013] Optionally, after obtaining the monitoring data of the first target KNX device, it is checked whether the engineering value of the first target KNX device in the monitoring data has been refreshed. If not, it is checked whether the channel connection information and the configuration information of the first target KNX device are correct.

[0014] In the above scheme, optionally, if it is determined that the engineering value of the first target KNX device has been refreshed, then it is determined whether the refresh of the engineering value of the first target KNX device is correct.

[0015] In a second aspect, a WeLink gateway includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method for acquiring KNX device data based on the WeLink gateway described in the first aspect.

[0016] Thirdly, a computer-readable storage medium having a computer program stored thereon, characterized in that, when the computer program is executed by a processor, it implements the steps of the method for collecting KNX device data based on a WeLink gateway described in the first aspect.

[0017] This application has at least the following beneficial effects:

[0018] This application pre-receives configuration and channel information of the target KNX device based on the acquisition protocol in the WeLink gateway. A connection is established between the target KNX device and the gateway using the channel connection information and the configuration information of the first target KNX device. Then, the group address information of the first target KNX device is used to obtain the engineering value of the first target KNX device. The engineering value is integrated with the first configuration information to obtain monitoring data, which is then uploaded to the IoT platform; this completes the data acquisition of the KNX device. A control command containing the group address information of a second target KNX device, generated by the Internet platform, is obtained and sent to the second target KNX device. Therefore, KNX device monitoring can be performed without specific software, simplifying the configuration and debugging process, reducing operational difficulty, greatly improving the monitoring efficiency of KNX devices, and requiring low professional skills from personnel. Attached Figure Description

[0019] Figure 1 A screenshot of the software page for viewing KNX device information using specialized software;

[0020] Figure 2 This is a software page diagram showing how control commands are issued to KNX devices using specialized software.

[0021] Figure 3 A flowchart illustrating a KNX device monitoring method based on a WeLink gateway, provided as an embodiment of this application;

[0022] Figure 4 This application provides a channel page for establishing a connection between a WeLink gateway and a target KNX device, as one embodiment of the present application.

[0023] Figure 5 This is a detailed flowchart illustrating a method for collecting KNX device data and controlling KNX devices based on a WeLink gateway, provided as an embodiment of this application. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0025] In the description of this application: unless otherwise stated, "a plurality of" means two or more. The terms "first," "second," "third," etc., in this application are intended to distinguish the objects referred to and do not have any special meaning in terms of technical connotation (e.g., they should not be construed as an emphasis on importance or order). Expressions such as "comprising," "including," and "having" also mean "not limited to" (certain units, components, materials, steps, etc.).

[0026] In existing technologies, viewing information on traditional KNX devices requires specialized software tools, such as... Figure 1 As shown, this tool connects to a KNX device to view the data refresh status. The data refresh format is a string of hexadecimal codes, which is not conducive to data viewing. Controlling the KNX device by inputting the group address and control commands also requires inputting hexadecimal codes, which is inconvenient for manual operation. Figure 2 As shown.

[0027] In one embodiment, such as Figure 3 As shown, a KNX device monitoring method based on a WeLink gateway is applied to a WeLink gateway in an IoT system. The method includes:

[0028] Step S101: Receive channel connection information and configuration information of the first target KNX device; the configuration information of the first target KNX device includes the group address information of the first target KNX device; the configuration information of the first target KNX device is stored based on a pre-built acquisition protocol;

[0029] In step S101, the code logic in the KNX acquisition tool is extracted and converted into an acquisition specification. Data is then acquired through simple configuration, as shown in Table 1. Configuring device names facilitates management and viewing of the corresponding devices.

[0030] The group address information of the first target KNX device is usually represented by the acquisition configuration in the configuration information, as shown in Table 1. The acquisition configuration includes acquisition configuration 2int, acquisition configuration 3int, and acquisition configuration 4int, which correspond to the first, second, and third bits of the target KNX device group address, respectively. The group address is generally three numbers separated by " / ". For example, the group addresses of the five dots in Table 1 are 1 / 0 / 1, 1 / 0 / 3, 1 / 0 / 5, 3 / 0 / 1, and 3 / 0 / 3, respectively.

[0031] Table 1

[0032]

[0033]

[0034] Step S102: Based on the channel connection information and the configuration information of the first target KNX device, establish a communication connection with the first target KNX device.

[0035] In step S102, the corresponding device IP information and port information are obtained through, for example... Figure 4 The channel page configuration shown indicates that the local IP refers to the gateway's local IP address, and the device IP refers to the IP address of the KNX acquisition device. After configuring the IP address, the acquisition program will establish a connection based on the corresponding information.

[0036] Step S103: Integrate the engineering value of the first target KNX device with the configuration information of the first target KNX device to obtain the first target address information and the engineering value of the first target KNX device. Based on the acquisition protocol, upload the monitoring data of the first target KNX device to the Internet of Things platform.

[0037] In step S103, while the WeLink gateway obtains the engineering value of the first target KNX device, the group address information of the first target KNX device will appear as an identifier in the characters before the engineering value of the first target KNX device. For example, if the data of the light strip is obtained as 1011, the first three digits 101 represent the group address information of the light strip, and 1 represents the engineering value of the light strip, indicating that the state of the light strip is on.

[0038] After obtaining the group address information of the first target KNX device, since the WeLink gateway may store configuration information of multiple devices, the obtained group address information of the target KNX device is matched with the multiple group address information stored in the WeLink gateway to determine the configuration information of the first target KNX device. The engineering value and configuration information of the first target KNX device are then integrated to obtain the monitoring data of the first target KNX device.

[0039] Step S104: Obtain the control command generated by the IoT platform that contains the group address information of the second target KNX device, and send the control command to the second target KNX device.

[0040] In step S104, the first KNX device is the device object to which data is to be collected, and the KNX device is the device object to be controlled. Therefore, the second target KNX device can be, but is not limited to, the first target KNX device. That is to say, when issuing control commands, the gateway can send them to multiple KNX devices, which can be the first target device or other target devices.

[0041] Furthermore, since the monitoring data of each KNX device is composed of the KNX device configuration information and the KNX device's engineering values, and the configuration information includes the KNX device's group address information, the monitoring data of the KNX device also includes the target KNX device's group address information. Therefore, when the platform wants to issue a control command, the IoT platform looks up the corresponding KNX device's group address information, integrates this group address information into the control command, and then issues the control command based on this group address information.

[0042] In the above method for collecting KNX device data based on a WeLink gateway, the configuration information and channel information of the target KNX device based on the collection protocol are received in advance in the WeLink gateway. A connection is established between the target KNX device and the gateway using the channel connection information and the configuration information of the first target KNX device. Then, the group address information of the first target KNX device is used to obtain the engineering value of the first target KNX device. The engineering value is integrated with the first configuration information to obtain monitoring data, which is then uploaded to the IoT platform; this completes the data collection of the KNX device. A control command containing the group address information of a second target KNX device is obtained from the Internet platform and sent to the second target KNX device. Therefore, KNX devices can be monitored without specific software, simplifying the configuration and debugging process, reducing operational difficulty, greatly improving the monitoring efficiency of KNX devices, and requiring less professional expertise from personnel.

[0043] In one embodiment, the channel connection information includes the IP information and port information of the first target KNX device, as well as the local IP of the WeLink gateway.

[0044] In one embodiment, the configuration information of the first target KNX device further includes the internal ID, channel ID, device name, measurement point description, configuration description, and data type of the target KNX device.

[0045] The internal ID is the sequence number of the configuration information set by the target device in the WeLink gateway. In other words, if the WeLink gateway wants to collect data from a device, it will collect the configuration information of the corresponding device inside the WeLink gateway and number the configuration information of multiple devices. This number is called the internal ID.

[0046] The channel ID is the channel number of the acquisition program. When the acquisition program is used to establish a connection between the WeLink gateway and the target KNX device, the acquisition protocol operates under this channel ID.

[0047] In one embodiment, the control commands are concatenated and processed into hexadecimal information and sent to the second target KNX device.

[0048] In one embodiment, after obtaining the monitoring data of the first target KNX device, it is checked whether the engineering value of the first target KNX device in the monitoring data has been refreshed. If not, it is checked whether the channel connection information and the configuration information of the first target KNX device are correct.

[0049] In one embodiment, if it is determined that the first target KNX device engineering value has been refreshed, then it is determined whether the refresh of the first target KNX device engineering value is correct.

[0050] like Figure 5 As shown, this document describes the process from establishing a gateway point to collecting KNX device information and finally displaying that information on the platform. This method acquires KNX device information by configuring the gateway point. During configuration, we need to obtain the KNX device's IP and port information, and then configure the corresponding group address, allowing the gateway device to collect the relevant information.

[0051] After configuring the information, check if the locations have refreshed and verify that the refresh is correct. If the location refresh status is incorrect, then we need to check, debug, and modify the configuration. Generally, we need to check if the IP and port information are correct, and then check if the group address information is configured correctly. After confirming that the information is correct, perform simple debugging.

[0052] Verification of point refresh accuracy is primarily determined manually. The system checks whether the target KNX device's status matches its engineering values. If they match, the point refresh is considered correct; otherwise, it's considered a failure. For example, if a light strip is on, the returned engineering value should be 1, indicating a correct point refresh. However, if an air conditioner is in cooling mode and the returned engineering value is 30℃, this is clearly an incorrect value, indicating an incorrect point refresh.

[0053] The method proposed in this application primarily involves adding a KNX acquisition protocol to the acquisition program and then adding corresponding methods to the Weilink gateway to acquire and control KNX devices. Data acquisition through a single Weilink gateway device does not rely on other tools. The data acquired via the Weilink gateway is sent to the platform, which displays and refreshes the data and controls the transmission to the gateway. The gateway then issues commands to the KNX bus devices according to the corresponding configuration protocol, thus achieving control. This method reduces the difficulty of acquisition operations and simplifies the acquisition configuration process. Furthermore, this method allows data to be sent to the platform to obtain KNX device information and monitor the status of KNX devices. The gateway acts as an intermediary bridge, connecting and communicating between the KNX devices and the platform, making the abstract protocol configurable, acquireable, and monitorable. The platform issues relevant commands to the gateway to directly control the KNX devices, simplifying the operation process and reducing operational difficulty.

[0054] In IoT platform systems, ease of data acquisition is paramount, and the ability to collect and control multiple protocol specifications through a single gateway is of utmost importance for gateway products. This patent proposes a system and method based on KNX applied in Weilink, which achieves this functionality from the following aspects:

[0055] 1) Obtain the KNX device IP address and port number to connect to the device;

[0056] 2) Real-time acquisition of KNX device status information;

[0057] 3) Send the collected data to the platform management;

[0058] 4) The platform sends control information to the Weilink gateway to control the KNX device.

[0059] In one embodiment, a WeLink gateway in an Internet of Things (IoT) system is provided, including a memory and a processor. The memory stores a computer program. The WeLink gateway includes a processor, a memory, and a network interface connected via a system bus. The processor of the WeLink gateway provides computing and control capabilities. The memory of the WeLink gateway includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the WeLink gateway stores initial configuration information of a KNX device. The network interface of the computer device is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements the aforementioned KNX device monitoring method based on the WeLink gateway.

[0060] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, characterized in that the computer program, when executed by a processor, implements the steps of the method for collecting KNX device data based on a WeLink gateway.

[0061] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0062] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0063] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A KNX device monitoring method based on a WeLink gateway, characterized in that: The method, applied to a WeLink gateway in an IoT system, includes: The system receives channel connection information and configuration information of the first target KNX device; the configuration information of the first target KNX device includes group address information of the first target KNX device; the configuration information of the first target KNX device is stored based on a pre-built acquisition protocol; the acquisition protocol is formed by stripping the code logic in the KNX acquisition tool into an acquisition protocol form; Based on the channel connection information and the configuration information of the first target KNX device, a communication connection is established with the first target KNX device; Based on the integration of the target KNX device engineering value and the configuration information of the first target KNX device, the monitoring data of the first target KNX device is obtained. Based on the acquisition protocol, the monitoring data of the first target KNX device is uploaded to the Internet of Things platform. The system obtains a control command generated by the IoT platform that contains the group address information of the second target KNX device, and sends the control command to the second target KNX device.

2. The KNX device monitoring method based on a WeLink gateway according to claim 1, characterized in that, The channel connection information includes the IP information and port information of the first target KNX device, as well as the local IP of the WeLink gateway.

3. The KNX device monitoring method based on a WeLink gateway according to claim 1, characterized in that, The configuration information of the first target KNX device also includes the internal ID, channel ID, device name, measurement point description, configuration description, and data type of the target KNX device.

4. The KNX device monitoring method based on a WeLink gateway according to claim 1, characterized in that, The control commands are concatenated and processed into hexadecimal information and sent to the second target KNX device.

5. The KNX device monitoring method based on a WeLink gateway according to claim 1, characterized in that, After obtaining the monitoring data of the first target KNX device, check whether the engineering value of the first target KNX device in the monitoring data has been refreshed. If not, check whether the channel connection information and the configuration information of the first target KNX device are correct.

6. The KNX device monitoring method based on a WeLink gateway according to claim 4, characterized in that, If it is determined that the engineering value of the first target KNX device has been refreshed, then determine whether the refresh of the engineering value of the first target KNX device is correct.

7. A WeLink gateway, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images