Clarificaton: What does the -i flag constrain?

[lnksz]

System

• Linux (Ubuntu 26.04)
• EEBUS-HUB: v3.0.0

Question

eebus-hub can list my interfaces:

./eebus-hub-linux-amd64 -l
lo
enp0s31f6
wlp0s20f3
eth0
...

I can also see form the --help that eebus-hub takes the port and address as positional arguments.

./eebus-hub-linux-amd64 --help
usage: EEBUS-Hub [<flags>] [<port>] [<bindaddress>]

So for example, if I try to define -i lo, but no port/IP:

/eebus-hub-linux-amd64 -i lo
Warning: Failed to create logs subdirectory: mkdir ./logs/: file exists
EEBUS-Hub v3.0.0 - Built at Sun Jun 21 16:06:57 EEST 2026
Analyzer enabled (db=./analyzer_database/analyzer.db)
Logging: [normal error]
License successfully verified!
Valid till: [snip]
Local .env file not found.. Checking local environment variables..
[TEST_RUNNER]: Compliance tests are disabled by the current license.
Using network interfaces: [lo]
2026-08-07 12:36:45 INFO Local SKI: [snip]
2026-08-07 12:36:45 INFO mdns: none of the 1 required interfaces are available, will retry
2026-08-07 12:36:45 INFO mdns: no interfaces available, skipping initial announcement
[ModbusMeter] [snip]
Binding on HTTP 0.0.0.0:8080

Based on the "INFO" error logs I guess this is the restriction for MDNS only? And then port/IP for the webserver, so that port won't ever be part of the EEBUS communication?