Connection refused/forbidden

[robertusw]

Hi,

Since a couple of days I am no longer able to use the CMS integration in HA. I am getting te error: "Instellen mislukt, wordt opnieuw geprobeerd: 403 Client Error: Forbidden for url: https://iot.controlmyspa.com/spas/xxxxxxxx". My official ControlMySpa app on my iPhone with the same account is working fine. I completely removed the Hares-ControlMySpa integration, restarted HA, reinstalled it, restarted HA, configured it and logged-in but still the same message. It seems that Balboa rejects the Hares-ControlMySpa integration (third party apps). But maybe I am doing something wrong???

Thanks for your help and keep up the good work. Realy love this integration!

Best regards,

Rene

[haresik]

It’s unfortunate that the integration is reporting a connection error. However, the integration is currently working and communicating properly in my Home Assistant.

It’s possible that some changes were made directly in the CMS that could have caused the cloud service to become unavailable.

Does the website https://controlmyspa.com/portal/spas work normally for you? The integration uses similar requests.

If, after reinstalling, you were able to log in successfully and select your SPA, then most connections to https://iot.controlmyspa.com/ are working. It’s rather strange that retrieving the data would be the part that fails.

If the problem still persists, the only thing I can suggest is that you provide a LOG, if you know how to obtain it.

[robertusw]

Thanks for looking into this — I dug in further (with the help of Claude pro) and think I found the actual cause.

1. Does controlmyspa.com/portal/spas work for me?
Yes, logging in there works fine.

2. Login / spa selection during setup
After a clean reinstall, the integration's login step itself completes without error — I'm just never prompted to pick a spa or enter spa details as the README describes. I only have one spa on the account though, so this may just be normal behavior when there's nothing to choose between.

3. What debug logging showed
The 403 is a genuine HTTP response from the server, not a local network/DNS issue — response.raise_for_status() fires in spa_client.py right after a completed request. The failing call is:

GET https://iot.controlmyspa.com/spas/696a243d4ae5a33584e5266c

There's no separate logged failure for an auth/login step before this, so whatever authentication happens first appears to succeed — the code gets far enough to make this specific request. Neither the response body nor headers of the 403 are logged, so I can't see Balboa's exact reason from here. Debug log attached.

4. The actual mismatch
I called that exact URL manually myself, outside Home Assistant, and got an error too — so it's not about the integration's headers or client type, that specific URL+ID is dead for anyone who hits it.

By comparison, the network requests made by the working web portal use a completely different pattern:

https://iot.controlmyspa.com/portal/spas/69a81010b6919aee19c9fa6a

Two differences: the path includes /portal/, and the spa ID itself is entirely different (not a formatting difference — a different ID).

Both IDs are 24-char and look like standard MongoDB-style ObjectIds. Decoding the embedded timestamps: 696a243d... was generated 2026-01-16, and 69a81010... was generated 2026-03-04. Both existed months before my issue started (mid-August), which fits a backend migration that happened a while back, where the old ID/path kept working until it was switched off only in the last few days — which would explain why it's fine on your account but not mine.

5. Where the integration stores things locally
I checked /config/.storage/core.config_entries on my HA instance — the integration only persists email/password there, no cached spa ID or token. So every setup does a fresh lookup against your servers for the spa ID, and that fresh lookup is itself what returns the old, dead ID/path. Reinstalling can't work around this client-side.

Summary: the "which spa belongs to this account" lookup seems to still resolve to the old /spas/{id} pattern with an ID that no longer resolves, while the current web portal has moved to /portal/spas/{id} with a newer ID. If the integration can be pointed at the new pattern (or wherever the current ID is discoverable), that would likely fix it. Happy to test anything.

home-assistant_control_my_spa_2026-08-20T05-14-07_942Z-filtered.log

[haresik]

The main problem is in step 2, where the spa selection should always be displayed, even if you have only one spa. This is where the spa_id is configured.

I have modified the integration. Are you able to install the integration manually? Once you have verified that it works, I will publish the official release.

In the new version, you have two options:

• Select Configure for the integration and choose the spa_id again, or enter it manually.

• If you remove the integration and add it again, the form for selecting the spa_id should always be displayed, where you can either select it or enter the key manually.

[haresik]

Information for everyone: The spa_id key can be found on the portal here:

[robertusw]

Hi,

I removed your official integration, restarted HA, copied the new repo, restarted HA (just in case), added the integration and repeated this proces a couple of times but I never get the configure screen????

[haresik]

If you already have the non-functional integration installed,
does the field also fail to appear here when you configure the integration?
Try enabling the LOG at this step and check whether there is any error.
Which version of HA are you using?

[robertusw]

Problem is the integration can't start ("configuration failed") so there are no options at all? I added another item under the integration but got the same error.

The screenshot which say "gelukt" means "Succesfull, configuration created for ControlMySpa"

Running versions pls see attached screenshot

home-assistant_2026-08-22T07-50-02.066Z.log

[haresik]

Please try the following:

1. Remove the integration.
2. Delete everything in this location: /config/custom_components/cms/.
3. Make sure the integration is correctly placed in this location: /config/custom_components/control_my_spa/ !!!

I normally have the integration installed through HACS, which correctly places it in the control_my_spa directory.

I’ve also added some additional LOG messages to the integration to detect whether it is being registered correctly. If the problem persists, please send me the LOG again.

(The log messages are at INFO level, so you should be able to see them even without enabling debug logging.)

[robertusw]

It is working!!! I think the removal of the content in the /config/custom_components/cms/. folder soved my problem. I didn't know this was part of/used by the integration so I never removed this. After a restart of HA I was able to add my spa suvvesfully and also got the possibility to manually add my Balboa Spa ID (which wasn't needed because the proposed ID was already correct now).

BTW: i normally also add this integration through HACS.

Thanks again for your great help en time!!!

Best regards, Rene

[robertusw]

This morning I was thinking that I wrote "BTW: i normally also add this integration through HACS." but that is not true at all. Problem is that wather I add https://github.com/haresik/Hares-ControlMySpa.git ir https://github.com/haresik/Hares-ControlMySpa as a custom repo (integration) to HACS I can not find the Control My Spa integration. When adding teh custom repo I get an error: "haresik/hares-controlmyspa" but when I search for it it can't be found?

[haresik]

I’m not entirely sure how HACS behaves exactly, but when I tested it on a clean HA installation, it worked.