Why is gpsd integration very unstable?

Configuration
1

In my boat I have gpsd running on one Pi (192.168.3.2) and Hass running on the other (192.168.3.1). Hass gpsd integration keeps loosing the connection to the other Pi. I have gpsd running directly (not in a container) on 3.2 and Hass running in Docker on 3.1. It shouldn’t be the network because I have network_mode: host on the container. Today I was out for three hours trolling mackerel, but the integration hasn’t logged a meter of that! The last time it logged was a week ago. This is the screen on the integration:

image
image670×760 27.5 KB

“Ukjent” is Norwegian for “unknown”. The problem is not the gpsd daemon on 3.2, because this is a screenshot of cgps on 3.1, so same Pi as Hass is running on (I removed the lat and long, so I don’t tell the world where my boat with two Pi’s is docked :joy: ):slight_smile:

image
image985×645 107 KB

And this is Node-RED running in a container on the same Pi as Hass, 3.2:

image
image630×210 13.8 KB

So that sees it too. If I restart the daemon on Pi 3.2 and then Hass it starts to work. But if gpsd has been running for a while when I restart Hass, it doesn’t help. And when I restart Pi 3.1 with Hass, the gpsd integration won’t work until I do another restart of Hass when the Pi is up. Here’s the full Docker Compose file:

services:
  homeassistant:
    container_name: Homeassistant
    image: "ghcr.io/home-assistant/home-assistant:stable"
    volumes:
      - /media/pi/Docker/Docker-Compose/Homeassistant/Homeassistant:/config
      - /etc/localtime:/etc/localtime:ro
    restart: unless-stopped
    privileged: true
    network_mode: host

Nothing wonky in there. So does anybody know what can be going on?

2

What kind of Pi, specifically. Model and how much RAM?

3

@NathanCu Thanks for answering!

Pi 3.1 with Hass: Pi 5, 8 gig RAM.

Pi 3.2 with gpsd: Pi 4, 4 gig RAM.

4

Ok you labeled them 3.1… Got it (for the record you may want to refer to them as something else than 3- yes I know Mashup of your ip addr… it confuses the reader with a Pi3, which is what I was making sure you weren’t using)

Ok it’s not resource exhaustion from substandard equipment. next theory. :smiling_face_with_sunglasses:

5

No chance for that, the secondary Pi (is that better? :wink: ) only runs gpsd, a MQTT server and a wireless access point.