API Overview eng: Unterschied zwischen den Versionen
Lh (Diskussion | Beiträge) |
Lh (Diskussion | Beiträge) |
||
(7 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt) | |||
Zeile 5: | Zeile 5: | ||
From experience with successfully implemented customer projects, the following basic functions are important in an integration: | From experience with successfully implemented customer projects, the following basic functions are important in an integration: | ||
* Switching the outputs on and off | * Switching the outputs on and off | ||
− | + | *Reset function per outlet | |
* Query of the port status | * Query of the port status | ||
* Measurement data: voltage, current + residual current (RCM), current consumption, energy counter (one counter resettable) | * Measurement data: voltage, current + residual current (RCM), current consumption, energy counter (one counter resettable) | ||
Zeile 40: | Zeile 40: | ||
''Positive'': simple handling | ''Positive'': simple handling | ||
| | | | ||
+ | *[[Console]] | ||
|- | |- | ||
|'''SNMP''' | |'''SNMP''' | ||
Zeile 55: | Zeile 56: | ||
Read state of Over-voltage Protection | Read state of Over-voltage Protection | ||
|''Positive'': desired use in SNMP environment<br>''Negative'': Device not completely configurable | |''Positive'': desired use in SNMP environment<br>''Negative'': Device not completely configurable | ||
+ | | | ||
+ | *[[SNMP_eng]] | ||
|- | |- | ||
|'''Modbus TCP''' | |'''Modbus TCP''' | ||
Zeile 77: | Zeile 80: | ||
|''Positive'': Publish data locally or in the cloud<br /> | |''Positive'': Publish data locally or in the cloud<br /> | ||
''Positive'': Complete range of functions through CLI | ''Positive'': Complete range of functions through CLI | ||
+ | | | ||
+ | *[[MQTT_eng]] | ||
|} | |} |
Aktuelle Version vom 13. Mai 2024, 14:48 Uhr
This is an overview of the GUDE API (Application Programming Interface) for controlling and accessing GUDE devices with different protocols.
Our APIs are modular and thus uniform to use for all GUDE devices. We use a REST API. Devices can be automatically accessed through the following five different interfaces, which provide different ways to control and access configuration data and status information. Only HTTP(S) and the console (Command Line Interface) provide full access to the device.
From experience with successfully implemented customer projects, the following basic functions are important in an integration:
- Switching the outputs on and off
- Reset function per outlet
- Query of the port status
- Measurement data: voltage, current + residual current (RCM), current consumption, energy counter (one counter resettable)
- Status of the overvoltage protection (Over Voltage Protection)
- External sensor data: Temperature, Humidity and Air Pressure
API Overview | |||||
---|---|---|---|---|---|
Protocol | Transport | Functional Scope | Positive / Negative | Further Information | |
CGI/JSON | HTTP(S) | Read/Write all Configuration Data Read/Write all Status Data |
Positive: Complete functional scope Negative: Needs HTTP(S) Libraries and JSON Parser |
| |
CLI Command Line Interface |
Telnet / SSH / MQTT HTTP(S) / RS232 |
Read/Write all Configuration Data Read/Write all Status Data |
Positive: Complete functional scope Positive: simple handling |
||
SNMP | SNMPv2 / SNMPv3 | Read/write state of the ports (Relay or eFuses) Read/Write Port names (Relay or eFuses) |
Positive: desired use in SNMP environment Negative: Device not completely configurable |
||
Modbus TCP | Modbus TCP | Read/write state of the ports (Relay or eFuses) Read input states |
Positive: desired use in Modbus TCP environment Negative: Device not completely configurable |
||
MQTT |
MQTT | Distribution of messages via MQTT broker Distribution of sensor data via MQTT broker |
Positive: Publish data locally or in the cloud Positive: Complete range of functions through CLI |