A Schneider iSE KNX miniserver can remain visible in a network scan while disappearing from the iPad application. In the reported case, all LEDs began cycling after the unit was connected to a PC, although no configuration parameter had knowingly been changed. Recovery required restoring the iSE service with the iDOLOAD application—not configuring DDNS or port forwarding.
Separate Local Failure from Remote-Access Configuration
| Condition | Relevant action |
|---|---|
| The iSE appears in a local network scan, but the application cannot discover its local server | Recover the iSE service with iDOLOAD, then test local operation. |
| The PC and iSE cannot communicate locally | Confirm that they use different IP addresses within the same subnet. |
| Local access works, but access from another Wi-Fi or cellular network is required | Configure DDNS, an IP reservation, UDP port forwarding, and the remote-server address. |
| KNX devices must be programmed in ETS5 | Use access to the KNX bus. Do not treat the iSE configuration workflow as an ETS programming interface. |
The remote-access instructions do not repair failed local discovery. Complete local recovery and verification before changing router settings.
Understand the Supported iSE and ETS Workflow
The available evidence identifies two applications: iSE Installer and iSE Control. iSE Installer transfers KNX group addresses that already exist in an ETS project into the miniserver. This means the ETS project and its group addresses must exist before configuring those addresses in iSE Installer.
Connecting the iSE Ethernet port to a PC does not, by itself, establish an ETS5 path to the KNX bus. The reported guidance requires a separate connection to the KNX bus, such as the referenced USB interface, when ETS must program KNX devices. The evidence does not specify an interface model or the wiring for the reported RJ10 connector, so verify those details in the applicable Schneider documentation before connecting bus conductors.
Check the Local Network Before Recovery
The PC and miniserver must have unique IP addresses in the same subnet. Compare each device's IP address and subnet mask; the network portion must match, while the host portion must differ. An IP conflict or mismatched subnet prevents normal communication.
Run a local network scan and record whether the iSE appears and which IP address it uses. If the scanner finds the miniserver at its previous address but iSE Installer or iSE Control shows no local server, basic Ethernet visibility exists and the failure is more specific than a completely missing network connection.
LAN and KNX LEDs can flash when their respective networks carry traffic. However, the evidence does not define the reported all-LED cycling pattern as a documented alarm code. Do not diagnose a specific hardware or firmware fault from that pattern alone.
Recover the iSE Service with iDOLOAD
- Download and open the iDOLOAD application, select the affected iSE, and activate Turn On. This action restored operation in the reported case.
- Reopen iSE Installer or iSE Control and confirm that the local server is discovered again. Issue a known command and verify the expected response, including KNX LED activity where applicable.
If the unit becomes unavailable again and only returns after a physical power cycle, the initial recovery has not established stable operation. Record the LED behavior, IP address, recurrence conditions, and whether Turn On restores service, then contact Schneider through an official support channel.
A factory reset was considered but not documented in the evidence. Do not improvise one: resetting the miniserver could remove configuration associated with the installation. Preserve the existing project and configuration before any manufacturer-directed reset or firmware action.
Configure Remote Access Only After Local Verification
Once local access is stable, follow the supplied remote-access sequence:
- Create a DDNS name if no public IP address is available.
- Enter the DDNS credentials in the router connected to the KNX server.
- Reserve the IP address that the router's DHCP service assigns to the iSE.
- Create the specified forwarding rule for external UDP traffic on port 18900 to the reserved iSE address. The supplied instruction describes forwarding for both incoming and outgoing traffic; router terminology varies, so map that requirement to the router's documented controls rather than opening unrelated ports.
- Enter the DDNS server address in the application's remote-server credential settings.
Verify local access first, then test from a genuinely external connection such as cellular service or a different Wi-Fi network. A successful local test does not verify DDNS or UDP port 18900 forwarding.
FAQ
How do I restore a Schneider iSE that no longer appears in the app?
Open iDOLOAD, select the iSE, and press Turn On. Then reopen iSE Installer or iSE Control and verify that the local server is discovered.
Can ETS5 program KNX devices through the Schneider iSE Ethernet connection?
The supported evidence describes iSE Installer as importing group addresses already present in the ETS project, not as an ETS bus-programming interface. Use a suitable connection to the KNX bus for ETS programming.
Which port does Schneider iSE remote access use?
The supplied remote-access instructions specify UDP port 18900. Reserve the iSE address, forward that UDP traffic to it, and configure the DDNS server address only after local access works.