Android : Network connection unstable

[maxime-granger]

The docker is installed
when i launch the OpenNova Admin it finds my mower and charger.

DNS is configured

docker-compose.yml i believe is setup appropriately

When i launch the app on my phone i get the error message : the network connexion is abnormal, please check your mobile network .

I ma not sure what i need to change for the original app to find the mower from the docker. Any help to send to the correct direction would be appreciated.

Thanks.

[dir26738]

Look at the address your server open nova admin, it is 172.18.0.2.
I guess you are on a Linux system, so have a look in the wiki at docker-compose.linux.yml (the file is a the root directory o the git) to use the option network_mode: host and the env TARGET_IP.

[maxime-granger]

thank you for your help, this exactly what i needed.

[stempfle]

well - since I changed to OpenNova my Novabot-APP says: Failed to load, please check your network connection and try again.
but via Browser i can control the Mower.

But - i have installed the CA-Certificate for my Android Device (Pixel 8 Pro)

[maxime-granger]

to better assist you, you will need to give more details about your install and maybe relevant screenshots.
In my situation i was not using the correct docker-compose file which resulted in my official Novabot app not to be able to connect to the new server. If your server is installed on a Linux machine search for the file docker-compose.linux.yml

[stempfle]

Yes, its Raspberry PI 3 with Docker. Here my compose: docker-compose.linux.yml

services:
  opennova:
    image: rvbcrs/opennova:latest
    build: .
    container_name: opennova
    restart: unless-stopped
    network_mode: host          # Geen Docker NAT — echte client-IPs zichtbaar
                                # + mDNS multicast bereikt LAN
    environment:
      # Timezone — must match the timezone used by the app when creating schedules
      TZ: ${TZ:-Europe/Amsterdam}
      PORT: 80
      DB_PATH: /data/novabot.db
      STORAGE_PATH: /data/storage
      FIRMWARE_PATH: /data/firmware
      ENABLE_TLS: "true"

      # Tijdelijk: log iedere succesvolle JWT auth zodat we wisselende tokens kunnen tracen
      AUTH_DEBUG: "1"

      # Optional: enable web dashboard (default: disabled)
      ENABLE_DASHBOARD: "true"

      # Your server's LAN IP (for firmware download URLs, TLS cert SAN + DNS)
      TARGET_IP: 192.168.178.8

      # Proxy mode: 'local' (default) serves Novabot endpoints locally;
      # 'cloud' forwards every HTTP request to app.lfibot.com (debug).
      PROXY_MODE: ${PROXY_MODE:-local}

      # Optional: DNS redirect for Novabot app (requires TARGET_IP).
      # Maps mqtt.lfibot.com / app.lfibot.com → TARGET_IP so unmodified
      # stock app + firmware reach this server. Bind on host port 53/udp.
      ENABLE_DNS: "true"
      UPSTREAM_DNS: ${UPSTREAM_DNS:-8.8.8.8}

      # Home Assistant MQTT bridge — auto-discover mowers + map images
      HA_MQTT_HOST: ${HA_MQTT_HOST:-}
      HA_MQTT_PORT: ${HA_MQTT_PORT:-1883}
      HA_MQTT_USER: ${HA_MQTT_USER:-}
      HA_MQTT_PASS: ${HA_MQTT_PASS:-}

      # Public base URL of the OpenNova server — needed so HA can fetch
      # the rendered map SVG via image entity. Without this the bridge
      # still publishes sensors but no image entity is discovered.
      RENDER_BASE_URL: ${RENDER_BASE_URL:-http://192.168.178.8}

      # Min interval (ms) between map image republishes. Default 15s
      # keeps HA responsive without spamming the broker.
      HA_MAP_THROTTLE_MS: ${HA_MAP_THROTTLE_MS:-15000}

      # ntfy.sh push notifications — set NTFY_TOPIC in .env to enable.
      # Topics are unauthenticated; pick something long and random.
      NTFY_TOPIC: ${NTFY_TOPIC:-}
      NTFY_URL: ${NTFY_URL:-https://ntfy.sh}
      NTFY_PRIORITY: ${NTFY_PRIORITY:-}

      # Optional: HA webhook trigger URL (full event JSON POSTed)
      HA_WEBHOOK_URL: ${HA_WEBHOOK_URL:-}

      # Battery % crossing point for the low_battery event
      LOW_BATTERY_THRESHOLD: ${LOW_BATTERY_THRESHOLD:-20}
    volumes:
      - ./data:/data

[dir26738]

I have the same issue, official novabot app not finding my mower.
To my point of view, my android phone which is connected to the wifi and data disabled, does not get the dns configuration.

To test it, I launch Chrome and i enter the url http://app.lfibot.com Result => it go on offcial novabot server instead of my local server.

I did not find how to specify dns in my phone (Android Xiaomi hyperOs 3): the option "automatic private dns" does not seem to have any effect.

[stempfle]

so I have a FritzBox and changed the Network Settings to use a Local DNS and added the IP of my Raspberry Pi-IP. After changing in the Fritzbox i had to reconnect the Phone to the wifi to get the new setting with the Raspberry Pi as DNS. Have you tried this?
But - i had some more issues with my Raspberry DNS. But solved in this conversation: #78

[stempfle]

here is what you simply have to to when your DNS is correct on your phone (and mower...) but still you get to the wrong IP for app.lfibot.com

on the Raspberry CMD (or Putty)

sudo nano /etc/dnsmasq.conf
Enter Password
Paste:

address=/app.lfibot.com/192.168.178.8
address=/mqtt.lfibot.com/192.168.178.8

Ctrl + O
Enter
Ctrl + X
sudo reboot