Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Connexoon RTS Japan / APAC returns 403 with Server.SOMFY site token flow

Open
  • Is something wrong?
#2,273 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
api, authentication

Research direction

Read the pyoverkiz authentication flow for Server.SOMFY (account token exchange, BOB site discovery, region selection, site-scoped token issuance) and compare it with how the APAC enduser endpoints /enduser-mobile-web/enduserAPI/setup and /setup/devices are called. The report gives no file, test or reproduction without a real Japanese Connexoon RTS gateway (type 56), and no decision has been made in the thread yet. Done means a maintainer answer on whether CONNEXOON_RTS_JAPAN is supported through this flow, or a documented region/resource mapping change plus a test.

Written by the indexing model from the issue text.

Description

bug

Hi,
I'm testing pyoverkiz 2.2.0 with a Japanese Connexoon Window RTS gateway that has already been migrated to the TaHoma by Somfy app.
The gateway and its connected devices are currently working normally from the official TaHoma iOS app.
Using Server.SOMFY, the current pyoverkiz authentication flow successfully reaches:

  • Somfy account authentication
  • account token exchange
  • BOB site discovery
  • JP → APAC region selection
  • site-scoped token issuance
    The returned site token is reported as Bearer, has a server-provided valid expires_in, and includes a scope field.
    However, APAC enduser API read requests return HTTP 403:
  • /enduser-mobile-web/enduserAPI/setup → 403
  • /enduser-mobile-web/enduserAPI/setup/devices → 403
    Both responses were classified as RESOURCE_ACCESS_DENIED.
    Changing only the User-Agent to pyoverkiz's standard User-Agent did not change the result (403 → 403).
    No device commands, configuration changes, pairing, Developer Mode, Local API, or write operations have been attempted.
    Before doing further testing, I'd like to confirm compatibility:
    Is the current Server.SOMFY → BOB site discovery → site-scoped Bearer token → APAC enduser API flow known to work with CONNEXOON_RTS_JAPAN (gateway type 56)?
    If Japanese Connexoon RTS gateways require a different supported authentication/resource mapping or API path after migration to TaHoma by Somfy, could you point me in the right direction?
    I'm happy to provide additional non-sensitive diagnostic information if useful, but I won't post access/refresh tokens, account IDs, site IDs, gateway IDs, or device URLs publicly.
    Thanks!
Dominant language
Python
Stars
59
Forks
37
Avg merge
3d 14h
Merged PRs (30d)
31

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from iMicknl/python-overkiz-api

All issues in iMicknl/python-overkiz-api

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.