Netatmo tag and binary_sensor discovery anomalies (3rd edit)

Hi,

Sorry, this is my 3rd edit since the behaviour is quite inconsistent:

  1. auto discovery of binary sensor returns:
    a. correct tags (open/vibration per tag - this is good!)
    b. correct binary sensors for welcome (Motion, Someone Known, Someone Unknown) - this is good!
    c. incorrect binary sensors for presence (Motion, Someone Known, Someone Unknown) - this is bad! Expected: Motion, Animal, Vehicle, Person

  2. Specifying all binary sensors in config:
    a. removes the tags - this is bad! Expected: they stay in there or config allows for specification of tags
    b. removes the welcome binary states - this is bad! Expected, they stay in there
    c. duplicates presence binary states - this is bad! Expected that discovery does not duplicate them, but anyway

  3. Removing specification of binary sensors in config leads to
    a. tags do not reappear until you reset client ID and client secret ant netatmo connect -> this is very bad! Expected: not having to reset anything!

  4. Resetting netatmo connect and specifying only the presence binary sensors leads to
    a. duplication of all tags and welcome binary sensors, but no correct presence binary sensors -> this is very bad! Expected: welcome auto discover and presence as specified

  5. Any possible combination of resetting netatmo connection, discovery and specification of binary sensors, leads to either welcome sensors overwriting presence sensors or other way around,

they seem not to be able to co-exist in the current implementation!

Appreciate any help/guidance/bugfix!
Thanks

p.s. another edit: “movement” is not covered for the welcome tags in general.
p.p.s. @jabesq @gieljnssns any additional info I can provide to make this fly? Thanks!