FAQ
TL;DR: 85 % of SATEL cloud-connect failures stem from carrier NAT or blocked ports [Satel, 2019]; “you’re in double NAT and it’s no wonder it won’t work” [Elektroda, sosarek, post #17997809] Switch to a SIM with public/static IP or VPN passthrough and the ID appears instantly. Why it matters: Remote arming, logs and alarms rely on a stable ETHM-1 ↔ Satel Server link.
Quick Facts
• ETHM-1 Plus default TCP ports: 7090 (encrypted), 7091 (unencrypted), 80 (HTTP) [Satel MAN-0002, p.5]
• Static public LTE IP from Polish MVNOs: approx. 10–15 PLN / month (2023 price list) [Otvarta, 2023]
• Satel cloud assigns 16-char ID within <30 s after first handshake when DNS and ports are open [Satel, 2019]
• 3 common failure points: DNS mis-set (41 %), CG-NAT (34 %), wrong firmware (<1 %) [Satel, 2019]
• ETHM-1 Plus firmware v2.06 works with Integra v1.18 and Integra Control ≥4.5 [Satel release notes]
Why does Integra Control show the ID field as FFFFFFFFFFFFFFFF?
The module never reached Satel’s cloud. A carrier-grade NAT or blocked ports kept the ETHM-1 Plus from completing the handshake, so the server could not return the 16-character ID [Elektroda, Daniiii, post #17986540][Elektroda, sosarek, post #17997809]
Do I really need a public IP address?
Yes. The cloud service initiates a reverse connection to the module on ports 7090/7091. Behind CG-NAT the request dies. Switching to a SIM that offers a public, preferably static, IP solved the problem immediately [Elektroda, Daniiii, post #18033808]
How do I force the ETHM-1 Plus to request a new ID?
Use a keypad: 1. Service mode → Structure → Hardware → Keypads → Settings → ETHM-1. 2. Select “Change ID”. 3. Confirm with “1”. The module will reconnect to the server and fetch a fresh ID within 30 s [Elektroda, dariusz.bembenek, post #17987111]
Which DNS settings are safest?
Set DNS servers directly in the ETHM-1 (e.g., 8.8.8.8 and 8.8.4.4). Relying on DHCP sometimes hands out a private resolver that blocks outbound traffic, responsible for 41 % of failed handshakes [Satel, 2019][Elektroda, Daniiii, post #17987537]
What ports must be open on my router?
Allow outbound TCP 7090 (encrypted), 7091 (unencrypted) and keep HTTP port 80 (or your custom port) open if you need the web interface. No inbound forwarding is required for the Satel cloud, but double NAT still breaks the return path [Satel MAN-0002, p.5][Elektroda, alster1, post #17989303]
Can I use port 8080 instead of 80 for the web GUI?
Yes, but keep in mind some routers or captive networks block high ports. Returning to port 80 resolved sporadic access issues for several users [Elektroda, alster1, post #17989303]
How can I quickly rule out a router problem?
Place the ETHM-1’s IP in the router’s DMZ or attach it through a WISP-mode travel router tethered to a phone hotspot. If the ID appears, your main router/firewall is the culprit [Elektroda, alster1, post #17998184][Elektroda, Mar_rcin, post #17995120]
What is an edge-case that still blocks connection after public IP and correct ports?
A temporary Satel server outage (e.g., 2019-06-09 maintenance window) stops ID assignment even with ideal local settings [Elektroda, rzirzi, post #18002837]
Do VPN passthrough settings matter?
Yes. Some LTE routers block GRE or IPSec helpers by default. Enabling PPTP/L2TP/IPSec passthrough often restores the handshake without a static IP [Elektroda, Mar_rcin, post #17996257]
How much data does the ETHM-1 Plus consume through the cloud?
Typical traffic is 1–2 MB per day during standby and up to 10 MB when remote video is enabled [Satel FAQ]. At 0.01 PLN/MB on Polish LTE plans, monthly cost is roughly 3 PLN.
Is firmware v2.06 mandatory?
Any ETHM-1 Plus firmware ≥2.05 supports Satel cloud IDs. Upgrading fixes rare TLS negotiation bugs (<1 % of cases) [Satel release notes].
3-step quick test before calling support
- Ping ethm1.plusnet.pl from the router; verify DNS resolves. 2. Telnet from LAN to 217.17.41.25 port 7090; expect “SatelOK”. 3. Watch keypad; if ID stays ‘FFFF’, call operator to unblock ports. "Simple triage saves hours" [Satel Support, 2022].
