Disabling IP match

[phillprice]

Hi,
I don't have a static IP for everything and for those that don't they all end up being marked as Device X (IP match) when they're different devices.

Is there a way to disable the naming of such devices like that?

[jokob-sk]

Hi @phillprice ,

Not currently, but I could see this as valuable to others and implement it. Would this be a global setting or plugin specific setting?

[phillprice]

I think global but happy to be overruled if there's a great argument

[jokob-sk]

cool, will be available in the next release.

You can test it on the netalertx-dev container, which runs on the latest code base. Please note the docker-compose and volume mappings have changed, here is an example:

services:
  netalertx_fresh:
    container_name: netalertx_fresh
    image: "jokobsk/netalertx-dev:latest"
    network_mode: "host"
    cap_add:                          # 🆕 New line
      - NET_RAW                       # 🆕 New line 
      - NET_ADMIN                     # 🆕 New line
      - NET_BIND_SERVICE              # 🆕 New line
    volumes:
      - /local_data_dir/config:/data/config   # ⚠ changed folder from /app -> /data 
      - /local_data_dir/db:/data/db           # ⚠ changed folder from /app -> /data 
    environment:
      - TZ=Australia/Sydney
      - PORT=20212                                 # change PORT as needed
      - APP_CONF_OVERRIDE={"GRAPHQL_PORT":"20223"} # change PORT as needed
    tmpfs: 
      - "/tmp:uid=20211,gid=20211,mode=1700,rw,noexec,nosuid,nodev,async,noatime,nodiratime" # 🆕 New line

You will need to run these commands:

sudo chown -R 20211:20211 /local_data_dir
sudo chmod -R a+rwx  /local_data_dir

[Necrosaurus]

Thank you very much for implementing this, where can I find the setting please?

[jokob-sk]

Here you go (NEWDEV_IP_MATCH_NAME):

[Necrosaurus]

🤔 Doesn't seem to have made it into the Home Assistant version yet, but now I know where to look after the next update. Thank you very much 😊