Your system, reachable.
Without opening a single port.
The EisBär Portal Service connects the app and the KNX installation securely to the outside world — without port forwarding, DynDNS or VPN on the home router. Bookable annually, set up in minutes.
Remote access, without touching the router
Normally, remote access means port forwarding, DynDNS or VPN — with security risks and setup effort. The Portal Service makes that unnecessary.
No router changes
The connection is initiated from the installation itself — the router stays untouched, no port needs opening.
Even behind CGNAT & mobile
Many connections (cable, LTE/5G) no longer have a fixed, reachable IP. The Portal Service is unaffected by this.
Set up in minutes
Book the licence, connect the installation, done — no network technician needed on site.
Booked annually
Clearly calculable costs per year, per installation and service — with no long-term commitment.
The installation calls out — not the other way round
Instead of allowing incoming connections, the installation itself opens a secure, outbound connection to the EisBär Portal. The client and the ETS Connector likewise connect outbound only — the Portal then securely brings both sides together.
Path 1 — Client
Its own Portal Service licenceEisBär app / client
- Smartphone, tablet or PC
- Visualisation & control
- Sign-in with portal credentials
EisBär Portal Service
Brings client and installation together — no open port, no fixed IP required.
EisBär system
- EisBär Portal Connector — registers the installation with the Portal
- Visualisation / installation project
- Router unchanged — no port opened
Path 2 — KNX2GO ETS remote programming
Its own Portal Service licenceETS + EisBär ETS Connector
- Program on the integrator's notebook
- Presents ETS with a local KNXnet/IP interface
- Installation picked via the customer account
EisBär Portal Service
Brokers only — the KNX data stays end-to-end encrypted.
EisBär ETS Remote Agent
- Windows service or Raspberry Pi
- Speaks KNXnet/IP to the KNX IP interface
- The installation's KNX bus
Two paths, the same technology
The Portal Service supports two use cases — depending on who needs to reach the installation from outside. Each service works on its own and is licensed on its own.
Client
Residents or operators access their own installation from anywhere with the EisBär app — visualisation, control, status. Just like on the home Wi-Fi, only from anywhere.
- On site, the EisBär Portal Connector registers the installation with the Portal and keeps the outbound connection open
- Access to the EisBär visualisation from any location with internet access
- No router setup: no port forwarding, no DynDNS, no VPN client on the phone
- Ideal for residents, users and facility operators
ETS remote programming
The system integrator programs the KNX installation via ETS remotely — as if sitting directly on the bus on site. Two programs work together for this: the EisBär ETS Connector at the technician's end and the EisBär ETS Remote Agent at the installation.
- The ETS Connector presents the remote installation to ETS as an ordinary KNXnet/IP interface — programming, group and bus monitor as if on site, KNX IP Secure included
- The Remote Agent runs on site as a Windows service or on a Raspberry Pi and talks to the KNX IP interface; setup is done with a configuration key from the installer
- Access only when released — remote access can be blocked on site at any time, including by a KNX telegram from within the installation
- Ideal for integrators, installers and support — saves site visits for changes and faults
Both services at once? No problem.
Client and ETS remote programming run independently of each other — in the same installation, through the same Portal, without interfering with one another.
Both paths in parallel in one installation
2 licencesEisBär app / client
Operate the visualisation, check status — while away.
ETS + EisBär ETS Connector
Program the KNX bus, group and bus monitor.
EisBär Portal Service
Brokers each connection separately — one licence per service.
One installation, two services
EisBär Portal Connector
→ EisBär system, visualisation
EisBär ETS Remote Agent
→ KNX IP interface → KNX bus
Router unchanged — no port opened.
Both services can be used independently of each other — separately or together. Each requires its own licence.
Because both services serve different access paths and user groups, each requires its own, separately booked Portal Service licence per year and installation.
For users and for professionals
Frequently asked questions
Do I need to set up anything on my router?
No. No port forwarding, no DynDNS, no VPN. The connection is initiated from the installation — the router stays untouched.
Does the Portal Service work behind mobile or cable internet without a fixed IP?
Yes — it was built exactly for these cases (CGNAT, changing IP addresses). No fixed, publicly reachable IP address is needed.
Can I use Client and ETS remote programming at the same time?
Yes, both services can run in parallel in the same installation and are independent of each other. Since they serve different access paths, two separate Portal Service licences are required — one per service.
What exactly are the ETS Connector and the Remote Agent?
Two programs that work together. The EisBär ETS Connector runs on the technician's notebook and presents the remote installation to ETS as an ordinary KNXnet/IP interface — it is started when needed and closes the remote access again afterwards. The EisBär ETS Remote Agent runs permanently at the installation as a Windows service (or on a Raspberry Pi) and connects that interface to the actual KNX bus on site. Both establish their connections outbound to the Portal only.
How is the Remote Agent set up on site?
Usually with a configuration key supplied by the installer: run the setup, type in the key, done — the settings are fetched from the Portal. Alternatively there is a prepared configuration file with a separate PIN, for when the machine has no internet during installation. The Remote Agent normally detects the KNX IP interface by itself; the technician can also trigger that search remotely if needed.
Can remote access be blocked on site?
Yes, at any time and reversibly. Via the Remote Agent's tray icon, via its web interface on the local network — or straight from the KNX installation by a telegram on a configurable group address. While access is blocked, no telegrams pass between ETS and the KNX bus.
How secure is the connection?
The installation opens an encrypted, outbound connection to the EisBär Portal — no inbound ports on the installation are ever opened. The client and the ETS Connector authenticate separately with the Portal before any connection is brokered. For ETS remote programming, the path between the ETS Connector and the Remote Agent is additionally end-to-end encrypted: the Portal only passes encrypted data through and never sees the KNX telegrams itself.
What happens if I don't renew a licence?
The corresponding remote access via the Portal Service ends. The installation itself — app visualisation on the home network as well as the KNX installation — keeps working locally, unchanged.
What does the Portal Service cost?
The Portal Service is booked annually, per service and per installation. Details and pricing on request at info@busbaer.de.
Ready for effortless remote access?
We advise on licensing, setup and combining Client with KNX2GO ETS remote programming.
Get in touch
Imprint
Alexander Maier GmbH
Beckstraße 3
D-69412 Eberbach
Managing director: Alexander Maier
Registered office: Eberbach
Register court: Mannheim
Commercial register: HRB 335404
VAT ID: DE177682654
Phone: +49 (0) 6271 – 91 94 70
E-Mail: info@busbaer.de