Purpose of the integration
Web Master reads controller and luminaire status through the local HTTP API of the EZ2 adapter, schema ges-v2. This interface provides monitoring data. Starting tests is covered separately under Modbus IP.
Prepare the connection
- Connect the controller and the integration computer to a network where they can communicate.
- Note the controller IP address. Use a fixed address or a DHCP reservation.
- Enable luminaire data sharing in the controller's local API settings. When disabled, the luminaire list and individual diagnostics return HTTP 403.
- Open the controller address in a browser, then check
/data/systeminfo.phpand/lumlist.php. - Select EZ2 integration in Web Master and enter the controller address according to your Web Master configuration.
- Import the list and compare the device count and locations with the controller. Add error descriptions from
/data/errorcodes.phpto the external dictionary.
Replace the example address 192.168.1.50 with your controller address. Keep these services on a trusted monitoring network. This local interface does not require a token; do not expose it directly to the Internet.
Data retrieved by Web Master
| GET request | Format | Purpose |
|---|---|---|
/data/systeminfo.php |
JSON | System status, counters and data schema |
/lumlist.php |
TSV, 10 columns | Inventory and luminaire status |
/data/errorcodes.php |
JSON | Error dictionary |
/data/luminaire.php?id=196618 |
JSON | Individual diagnostics, including NVG |
For full examples and HTTP handling, see EZF API.
Identifying devices
The luminaire ID is channel × 65536 + physical address. Channels: 1 = BUS1, 2 = BUS2, 3 = AirBus. Physical address 10 therefore produces 65546, 131082 and 196618. Store the complete adresse value; do not truncate it to 16 bits.
When migrating from an older integration using physical addresses alone, synchronise the inventory again. Remove old records according to the Web Master procedure to avoid duplicates. Moving a luminaire to another channel changes its ID.
Luminaire list columns
| Column | Meaning |
|---|---|
| adresse | Unique channel/address ID |
| geraetetyp | AW, PIKTO, KOMBI, NVG or UNKNOWN |
| gruppe | Group number stored in the controller |
| ueberwachung | 1 = monitored; 0 = individually excluded from monitoring |
| schaltungsart | DS = maintained operation; BS = non-maintained operation; may be empty |
| betriebszeit | LTM_1H / LTM_2H / LTM_3H / LTM_8H; may be empty |
| letzte_testdauer | Empty when measured duration of the last test is unavailable |
| fehlercode | Four hexadecimal characters |
| ortstext | Location description |
| aktualisiert_am | Empty when the last update timestamp is unavailable |
Do not replace empty fields with zero or the current date. Configured autonomy is not a measurement of the previous test duration. For NVG, the operating mode is reported only when both outputs agree. Mode and autonomy are empty after communication is lost.
Checks before acceptance
- Device counts and IDs match the controller.
- The same physical address on BUS1, BUS2 and AirBus creates three separate records.
- Types and locations are recognised; Fxxx codes have readable descriptions.
- Simulated LED, battery and communication failures are displayed correctly.
- Missing HTTP responses are shown as unavailable current data.
- Tests, inhibition and searches are distinguished from a healthy installation.
The local simulator helps prepare the integration. Acceptance requires a real controller and the intended Web Master. See programs and downloads.