FAQ
TL;DR: For Satel INT‑TSI uploads via TSI‑Builder, use a simple 3‑step LAN sync; “Remote access is temporary.” Disable firewall, build, then sync from the Sync pane. [Elektroda, alster1, post #19096406]
Why it matters: It saves time for Satel Integra WRL users who want painless, card‑free interface updates at home.
Quick Facts
- Put the INT‑TSI and your TSI‑Builder PC on the same LAN and confirm ping replies before syncing. [Elektroda, alster1, post #19096325]
- Remote access on the keypad is session‑based; enable it right before each synchronization attempt. [Elektroda, alster1, post #19096406]
- Use TSI‑Builder’s Sync > Search LAN to discover the keypad; project sync doesn’t rely on manual port settings. [Elektroda, alster1, post #19096459]
- If LAN sync fails, you can still update by copying the project via the INT‑TSI microSD card. [Elektroda, marcin.daszkiewicz, post #19091183]
- Integra 128‑WRL lacks thermostat outputs; temperature control from INT‑TSI needs an Integra Plus panel. [Elektroda, dariusz.bembenek, post #19096524]
How do I upload a TSI‑Builder project to an INT‑TSI over LAN?
Use this quick flow:
- On the INT‑TSI, enable Remote access in settings.
- In TSI‑Builder, Build the project.
- In the Sync pane, the keypad name appears; start synchronization.
If it stalls, temporarily disable antivirus and firewall, then retry. “Remote access in the keypad is temporary,” so toggle it right before each attempt. [Elektroda, alster1, post #19096406]
TSI‑Builder shows “Connection refused: connect.” What should I check?
Toggle Remote access on the keypad immediately before syncing. Build the project so the keypad name can appear under Sync. Temporarily disable antivirus and firewall to rule out local blocking. Then retry the synchronization. This error often indicates the keypad isn’t accepting the session because Remote access expired or the PC is blocking the connection. [Elektroda, alster1, post #19096406]
Do I need to set a port for INT‑TSI synchronization?
No. “The ports for project synchronisation should not matter.” Use Sync > Search LAN to find the keypad and start synchronization from there. Manual port entries are unnecessary for this workflow. This avoids confusion with other modules and ensures the correct target is selected. [Elektroda, alster1, post #19096459]
Where in TSI‑Builder do I find the keypad for syncing?
Open your project, right‑click Sync in the project tree, and choose Search LAN. If networking is correct, the INT‑TSI will appear by name under Sync after building. Select it and run the synchronization. This discovery avoids manual IP or port configuration mistakes. [Elektroda, alster1, post #19096459]
The keypad pings but sync still fails—what’s missing?
Enable Remote access on the INT‑TSI right before each attempt. It times out between sessions, so a previous enable may have expired. Build the project, then confirm the keypad name appears under Sync. If needed, temporarily disable antivirus and firewall and retry. [Elektroda, alster1, post #19096406]
Can I change wireless temperature sensor settings from INT‑TSI on Integra 128‑WRL?
No. “No possibility for Integra 128‑WRL.” Temperature control from INT‑TSI requires an Integra Plus panel with Thermostat‑type outputs. Without a Plus panel, you cannot expose thermostat controls on the TSI user interface. Consider panel upgrade if thermostat control is a requirement. [Elektroda, dariusz.bembenek, post #19096524]
Is there any installer‑only workaround for temperature control on 128‑WRL?
Yes, but it’s limited. You can enter the keypad’s service mode and switch settings there. This path is intended for installers, not daily end‑user control. For normal thermostat features, an Integra Plus controller is needed. [Elektroda, dariusz.bembenek, post #19096524]
If LAN sync fails, can I still update via microSD?
Yes. Copy the built project to the INT‑TSI’s microSD and update locally. The original poster used this physical method when LAN wasn’t set up. It’s a reliable fallback when Discovery or Remote access isn’t available. Plan to return to LAN sync once networking is resolved. [Elektroda, marcin.daszkiewicz, post #19091183]
Do I need to share my config privately to get help?
No. “There is nothing to show on the priv.” Start with basics: same LAN, ping replies, and Remote access enabled. Those checks usually surface the cause. Only share sensitive data with trusted installers if required. [Elektroda, alster1, post #19096325]
Does Remote access stay enabled indefinitely on the INT‑TSI?
No. “Remote access in the keypad is temporary.” Turn it on immediately before syncing each time. If you wait, it expires and the connection is refused. Keep the TSI‑Builder window ready so you can sync right after enabling. [Elektroda, alster1, post #19096406]
Did LAN discovery actually fix this issue for someone?
Yes. In this thread, 1 out of 1 reported cases connected after using Search LAN. The user confirmed discovery found the keypad and synchronization proceeded. This validates the discovery approach when manual settings fail. [Elektroda, marcin.daszkiewicz, post #19096490]
I’m far from installers—can I still get help expanding my system?
Remote help may be limited by distance and access. One installer declined due to being too far and suggested finding someone closer. Look for a nearby certified Satel installer for on‑site work. [Elektroda, alster1, post #19096613]
I selected ETHM‑1 in project properties—could that block INT‑TSI syncing?
Use the Sync workflow instead. Right‑click Sync and run Search LAN to target the INT‑TSI directly. Project synchronization does not depend on manual port settings or ETHM‑1 selection for the keypad. This approach avoids misconfiguration. [Elektroda, alster1, post #19096459]
