Plates starting with a number recognized by ALPR but not recorded by HA

[safepay]

Great integration, but in Victoria, Australia, we have plates that these days begin with a number. Currently they are all number 1.
E.g.

The ALPR portal is successfully recognising the images sent, but HA just no information in the attributes after detection.

I'm not sure where to look, but this looks similar to the previous issue #35 where sensors need the plates in brackets. E.g. ['1XY123'] to work.

It's probably breaking Python!

So the system half works for me.

image_processing:
  - platform: platerecognizer
    api_token: !secret plate_recognizer_token
    regions:
      - au-vic
    watched_plates:
      - '1XXXXX'
      - '1YYYYY'
    save_file_folder: /config/www/plate_recognizer
    save_timestamped_file: true
    always_save_latest_file: true
    source:
      - entity_id: camera.driveway

[robmarkcole]

Not really sure the cause, the API calls should be handled elsewhere so have created #59

[doenau]

Great integration, but in Victoria, Australia, we have plates that these days begin with a number. Currently they are all number 1. E.g.

The ALPR portal is successfully recognising the images sent, but HA just no information in the attributes after detection.

I'm not sure where to look, but this looks similar to the previous issue #35 where sensors need the plates in brackets. E.g. ['1XY123'] to work.

It's probably breaking Python!

So the system half works for me.

image_processing:
  - platform: platerecognizer
    api_token: !secret plate_recognizer_token
    regions:
      - au-vic
    watched_plates:
      - '1XXXXX'
      - '1YYYYY'
    save_file_folder: /config/www/plate_recognizer
    save_timestamped_file: true
    always_save_latest_file: true
    source:
      - entity_id: camera.driveway

Maybe just try the au region, not au-vic

Also you don't need the quotes around the watched plates.
Works fine for me with qld plates (3numbers : letters)