[EN] Suppoort "Notification by gateway" method of gateway to get device properties

【Summary】

In line with the continuous growth of "status" type properties, to increase the efficiency of data collection, NextDrive Gateway (hereinafter referred to as "GW") will add a "Gateway Notification" method to obtain device properties in addition to the four existing methods.

【Detail explanation】

Abount how GW retrieves device properties

The following explains how NextDrive GW retrieves device properties.
bIn this feature, we will add a method of "⑤ GW Notification" to collect device information more efficiently. A comparison of each method of retrieving properties is provided in the following table.

① Without polling

GW supports retrieving data of device scope, but does not do so by default.
The “device scope acquisition method” can be changed to “Regular Polling” through IoE Suite Developer portal.

② Read Once EXIST FEATURE

GW supports retrieving data of device scope data, but only reads the device scope “once” and uploads it to IoE platform when GW is initialized or rebooted.
The “device scope acquisition method” can be changed to “Regular Polling” through IoE Suite Developer portal.

③ Regular Polling EXIST FEATURE

GW supports retrieving data of device scope, and reads the device scope ”periodically'' and uploads it to IoE platform based on the defined “Sampling Rate” by default.
The “Sampling Rate” of the device scope can be changed through IoE Suite Developer portal.

“Sampling Rate after Change” is higher than “Default Value”
1. If the "Default Value" is a divisor of the "Sampling Rate after Change", the GW will retrieve data periodically based on the "Default Value".
2. If the "Default Value" is not a divisor of the "Sampling Rate after Change", GW will retrieve data periodically based on the greatest common divisor (1 minute) of the two values.
"Sampling Rate after Change" is lower than "Default Value"
1. If the "Default Value" is a multiple of the "Sampling Rate after Change", the GW will retrieve data periodically based on the "Sampling Rate after change".
2. If the "Default Value" is not a multiple of the "Sampling Rate after Change", the GW will retrieve data periodically based on the greatest common divisor (1 minute) of the two values.

④ Device notification EXIST FEATURE

GW supports retrieving data of device scope and performs this according to the device notification frequency and upload it to IoE platform.
The “device scope acquisition method” cannot be changed to “Regular Polling” through IoE Suite Developer portal.

⑤ GW notification release on MAR. 15, 2024

GW supports retrieving data of device scope and performs this every minute, but only uploads the data to the IoE platform if the value changes.
The “device scope acquisition method” cannot be changed to “Regular Polling” through IoE Suite Developer portal.

Method to Get Scope	Sampling Rate （Device ↔ GW）	Upload （GW ↔ IoE Platform）	Weather to change the Scope acquisition method to Regular Polling through IoE Suite Developer	Model example	Scope example
Not support	N/A	N/A	✕	SmartMeter	0xE2（Historical data of measured cumulative amounts of electric energy 1 (normal direction)）
① Without polling	N/A	N/A	◯	SmartMeter	operationStatus currentNormalUsage
② Read Once	Read the device Scope “once only” when GW is initialized or restarted	◯	◯	SmartMeter	smartMeterCoefficient
③ Regular Polling `Polling interval varies by device`	Read the device Scope "periodically" based on the defined sampling rate by default	◯	◯ Sampling Rate can be changed.	SmartMeter	instanceElectricity
④ Device Notification	Obtain device Scope data based on the notification frequency on the device side	◯	✕	SmartMeter	normalUsage reverseUsage
⑤ GW Notification	Read device Scope “every minute”	Uploaded the data only if the value read every minute changes.	✕	For details, please refer to "Model and Scope of the device that supports notifications by GW" below.

Model and Scope of the device that supports notifications by GW

With this feature adjustment, the method for retrieving the Scope of Model in the table below will be adjusted to "GW Notification".
For details on how to retrieve the Scope of each model, please refer to the description of the "Method to Get Scope" field in the Device Profile of each device at Table of Reference for Device Name, Model Name and Device Profile.

	Model	Scope	Device Profile	Remark（Protocol）
1	ECHONET Lite device（Applicable throughout）	faultCode	Super Class	ECN
2	Primevolt_PV-3000N-V	alarm1 alarm2 alarm3	Primevolt_PV-3000N-V	Modbus RTU
3	AEC_Tough-Pro	alarm1 alarm2 alarm3 alarm4	AEC_Tough-Pro
4	AEC_Tough-3P	alarm1 alarm2 alarm3 alarm4	AEC_Tough-3P
5	AEC_Trinergy	alarm1 alarm2 …（abbreviate） alarm31 alarm32	AEC_Trinergy
6	Delta_M-Series	alarm0 alarm1 …（略） alarm8 alarm9	Delta_M-Series
7	Moritec_MEVS	errorStatus	Moritec_MEVS
8	Kaori_Mcthanol-RMFC	errorCode
9	Yamabishi_YRW-Series	powerSupplyMinorFault powerSupplyModerateFault powerSupplyCriticalFault1 powerSupplyCriticalFault2	Yamabishi_YRW-Series	Modbus TCP
10	NittoKogyo_Safalink-One	alarm1 alarm2 alarm3	NittoKogyo_Safalink-One
11	SmartLogger	alarm1 alarm2 alarm3 alarm4	Huawei_SmartLogger