Zone node in Node-RED not being triggered

I am trying to test my zone-based automations in Node-RED but I am unable to trigger the Zone node.
It works when the location is actually reported by the companion app in my phone, but I am using the Device tracker: See service and that somehow doesn’t trigger that particular node.
In Home Assistant I can see myself in the zone I fake to be in and some events are triggered in the event bus, but that node really receives no input.

Any clue what could be going on?

This is what I am doing:

My person now has only “aaa” assigned as a device tracker, but I added explicitly the device_tracker here to see if that changed anything (which didn’t).

And these are the events that get triggered:

event_type: call_service
data:
  domain: device_tracker
  service: see
  service_data:
    dev_id: AAAA
    location_name: Home
origin: LOCAL
time_fired: "2024-01-19T17:15:30.932260+00:00"
context:
  id: 01HMHBGXQMCGAKF3K9CNKX2HCC
  parent_id: null
  user_id: 559a68921d8f440381a1169fe1280964
event_type: state_changed
data:
  entity_id: device_tracker.aaaa
  old_state:
    entity_id: device_tracker.aaaa
    state: Work
    attributes:
      source_type: gps
      friendly_name: aaaa
    last_changed: "2024-01-19T17:15:08.411782+00:00"
    last_updated: "2024-01-19T17:15:08.411782+00:00"
    context:
      id: 01HMHBG7QV0706M08S4T99AQ78
      parent_id: null
      user_id: null
  new_state:
    entity_id: device_tracker.aaaa
    state: Home
    attributes:
      source_type: gps
      friendly_name: aaaa
    last_changed: "2024-01-19T17:15:30.932379+00:00"
    last_updated: "2024-01-19T17:15:30.932379+00:00"
    context:
      id: 01HMHBGXQMQSH971SN5TBSFG61
      parent_id: null
      user_id: null
origin: LOCAL
time_fired: "2024-01-19T17:15:30.932379+00:00"
context:
  id: 01HMHBGXQMQSH971SN5TBSFG61
  parent_id: null
  user_id: null
event_type: state_changed
data:
  entity_id: person.sergi
  old_state:
    entity_id: person.sergi
    state: Work
    attributes:
      editable: true
      id: sergi
      source: device_tracker.aaaa
      user_id: 559a68921d8f440381a1169fe1280964
      device_trackers:
        - device_tracker.aaaa
      entity_picture: /api/image/serve/d3a325616457e7a022552fff3a913091/512x512
      friendly_name: Sergi
    last_changed: "2024-01-19T17:15:08.413467+00:00"
    last_updated: "2024-01-19T17:15:08.413467+00:00"
    context:
      id: 01HMHBG7QXNCVRFE8DNW1TGM8A
      parent_id: null
      user_id: null
  new_state:
    entity_id: person.sergi
    state: Home
    attributes:
      editable: true
      id: sergi
      source: device_tracker.aaaa
      user_id: 559a68921d8f440381a1169fe1280964
      device_trackers:
        - device_tracker.aaaa
      entity_picture: /api/image/serve/d3a325616457e7a022552fff3a913091/512x512
      friendly_name: Sergi
    last_changed: "2024-01-19T17:15:30.933023+00:00"
    last_updated: "2024-01-19T17:15:30.933023+00:00"
    context:
      id: 01HMHBGXQNMXH2BAKH16B1673H
      parent_id: null
      user_id: null
origin: LOCAL
time_fired: "2024-01-19T17:15:30.933023+00:00"
context:
  id: 01HMHBGXQNMXH2BAKH16B1673H
  parent_id: null
  user_id: null
event_type: state_changed
data:
  entity_id: zone.sergi_s_work
  old_state:
    entity_id: zone.sergi_s_work
    state: "1"
    attributes:
      latitude: 41.4934307597571
      longitude: 2.057898044586182
      radius: 156.9987122305805
      passive: false
      persons:
        - person.sergi
      editable: true
      icon: mdi:office-building
      friendly_name: work
    last_changed: "2024-01-19T17:15:08.414406+00:00"
    last_updated: "2024-01-19T17:15:08.414406+00:00"
    context:
      id: 01HMHBG7QYAWNAY61DBCZ0WED6
      parent_id: null
      user_id: null
  new_state:
    entity_id: zone.sergi_s_work
    state: "0"
    attributes:
      latitude: 41.4934307597571
      longitude: 2.057898044586182
      radius: 156.9987122305805
      passive: false
      persons: []
      editable: true
      icon: mdi:office-building
      friendly_name: work
    last_changed: "2024-01-19T17:15:30.933746+00:00"
    last_updated: "2024-01-19T17:15:30.933746+00:00"
    context:
      id: 01HMHBGXQN1X26FVBYR0F021E1
      parent_id: null
      user_id: null
origin: LOCAL
time_fired: "2024-01-19T17:15:30.933746+00:00"
context:
  id: 01HMHBGXQN1X26FVBYR0F021E1
  parent_id: null
  user_id: null

I don’t use this but it looks like it is not asking for the entity but the device as it is listed in the known_devices.yaml file inside your cofig files.

Further, If you call device_tracker.see in NR it asks for the mac of the device.

Not really, the only required parameter is the device id.

This node requires either a device_tracker or person entity. And in the example above I am trying with both and it doesn’t work (and the device_tracker I use is present in the known_devices.yaml file)

I just tried myself with the zone node and no dice but I can grab the event with a trigger node.

Looking at the code of that node, it looks like gps coordinates are a must for that node. If gps coordinates are empty, then the node assumes the device_tracker is not in a known zone, even though it’s reporting in which zone it is.

It’s possible to fake the location and use the Zone node for automations, but it could be more testing-friendly.