Why does /user/me return an empty 'homeys' for authnticated owner account?

Developers
1

Why does /user/me return an empty homeys array for an authenticated owner
account with a visible, manageable physical Homey Pro?

Please confirm:

  • whether a specific OAuth client setting or approval status is required before
    Homey runtimes appear in /user/me.homeys;
  • whether a scope beyond homey.device.readonly, homey.insights.readonly and
    homey.user.self is required for Homey runtime discovery;
  • whether homey.user.readonly, homey.energy.readonly, homey.zone.readonly
    or homey.app.readonly should have exposed owned Homey runtimes if scopes
    were the blocker;
  • whether recent Homey Pro models should appear in /user/me.homeys when using
    homey-api@3.19.1;
  • whether there is a supported replacement discovery route for owned Homey Pro
    runtimes;
  • whether GET /user/me/client should be accessible to this OAuth client for
    local client-configuration verification.
2

As far as I know, the user must select a Homey when authenticating with OAuth2, so it’s probably not sending the full array. I don’t know why it wouldn’t be sending the selected Homey though