System Monitor - dynamic network interfaces

Configuration
1

I am running a remote HAOS that connects home with wireguard client, this works nicely.

But, I mount a volume from my home server over the VPN which is ofc not available at boot.

So, I though to use the System Monitor 's IPV4 Address of wg0 state change to trigger an automation to re-mount. So far, so good.

Sadly it seems that the System Monitor ignores the wg0 interface as it probably does not exist at boot…and alas, the automation never triggers.

If I reload the System Monitor it updates correctly, if I afterwards take the interface down and up again it triggers as it should, but not at boot.

Anyone have any ideas?

Regards
Morten

2

My solution was to ditch System Monitor and use the API into Wireguard client:

rest:
  - resource: "http://localhost:51821"
    scan_interval: 30
    timeout: 10
    verify_ssl: false
    sensor:
      - name: "WireGuard Status"
        value_template: "{{ value_json.status }}"
        icon: "mdi:vpn"

automation:
  - alias: Re-mount when vpn is available
    id: remount_on_available
    description: "Re-mount hypervisor storage when wireguard vpn is available"
    triggers:
      - trigger: state
        entity_id:
          - sensor.wireguard_status
        to:
          - connected
    conditions: []
    actions:
      - action: hassio.mount_reload
        metadata: {}
        data:
          device_id: 7916d3fabd358a32f682135cede16bc8
    mode: single