Track Nut tags with ESP-Home

I have set up a ESP32 with

esp32_ble_tracker:

logger:
  level: VERY_VERBOSE

And I get this in return:

# Nut 1
[21:12:55][VV][esp32_ble_tracker:402]: Parse Result:
[21:12:55][VV][esp32_ble_tracker:419]:   Address: EB:35:27:DF:10:94 (RANDOM)
[21:12:55][VV][esp32_ble_tracker:421]:   RSSI: -40
[21:12:55][VV][esp32_ble_tracker:422]:   Name: 'nut'
[21:12:55][VV][esp32_ble_tracker:430]:   Ad Flag: 6
[21:12:55][VV][esp32_ble_tracker:433]:   Service UUID: 0x1803
[21:12:55][VV][esp32_ble_tracker:436]:   Manufacturer data: 00.46 (2)
[21:12:55][VV][esp32_ble_tracker:447]:   Service data:
[21:12:55][VV][esp32_ble_tracker:448]:     UUID: 0x180A
[21:12:55][VV][esp32_ble_tracker:449]:     Data: EB.35.27.DF.10.94 (6)
[21:12:55][VV][esp32_ble_tracker:452]: Adv data: 02.01.06.03.03.03.18.05.FF.59.00.00.46.09.16.0A.18.EB.35.27.DF.10.94.04.09.6E.75.74 (28)

# Nut 2
[21:17:17][VV][esp32_ble_tracker:402]: Parse Result:
[21:17:17][VV][esp32_ble_tracker:419]:   Address: E5:A9:DF:E2:96:06 (RANDOM)
[21:17:17][VV][esp32_ble_tracker:421]:   RSSI: -42
[21:17:17][VV][esp32_ble_tracker:422]:   Name: 'nut'
[21:17:17][VV][esp32_ble_tracker:430]:   Ad Flag: 6
[21:17:17][VV][esp32_ble_tracker:433]:   Service UUID: 0x1803
[21:17:17][VV][esp32_ble_tracker:436]:   Manufacturer data: 00.46 (2)
[21:17:17][VV][esp32_ble_tracker:447]:   Service data:
[21:17:17][VV][esp32_ble_tracker:448]:     UUID: 0x180A
[21:17:17][VV][esp32_ble_tracker:452]: Adv data: 02.01.06.03.03.03.18.05.FF.59.00.00.46.09.16.0A.18.E5.A9.DF.E2.96.06.04.09.6E.75.74 (28)

Since he mac is random that is not something I can track (?).
But ESP32 Bluetooth Low Energy Device — ESPHome says you can use the UUID, but that is the same on both tags, not really an issue I could live with that.
How do I set that up?

binary_sensor:
  - platform: ble_presence
    service_uuid: "0x180A" # does not work (red box error not accepted input), and "180A" works but it's not found.
    name: "Nut tracker"

Or which part is the service_uuid?

Try with single quotes

    service_uuid: '0x180A' or '180A'

I get the same error with ‘0x180A’ and doesn’t work with just ‘180A’.