Indeed, partly refactored but forgot to check the details. Fix available in test.
2 Likes
@OH2TH , now everything is good. Thanks for a quick fix!
2 Likes
Hi! Problems When setting the temperature range to high or low. It changes the values when lookin at native app but in flow it gives “network request failed” ang changes the range back in native app after this.
I have tried the latest test app but when I add a “Control My Spa” unit it just tells me the password is wrong. Ive tried to reset the password and tried to set a very very basic password.
Thanks for all the work on this app! I understand Balboas sudden big changes are annoying. 
And now it started to work for me. So all good! Thanks Tapio for taking this app 
2 Likes
@OH2TH , The heater does not update correctly. It updates when it goes on, but then it is “stuck” in on, and never goes to off.
The text in the picture is " 3 hours ago".
The heater was activated 3 hours ago (13:00), it was off again at 13:36. But the app has not updated the status as for the heater, and the time is now 16:06.
The circulation pump does update as it should, it went off 16:00, and that one updated to off.
If you need a app-diagnostic or something else from me, I can provide it.
As noted before, the new API is not returning the information.
1 Like
Sorry, did not see that.
1 Like
Have you tried to log in at Control My Spa | Balboa Water Group with the same username and password?
The site and the (updated) app works. The Homey app worked before Balboa changed everything. I have also tried to uninstall the Homey app and install the (test) app again.
Strange. From my experience it is very random from the CMS side if the login is successful, that is why I asked if you have tried to log in on the web with the same credentials, since I do no not have any issues with it.
Interesting 24 minutes ago the Heater element was detected on my Spa and the status updated.
And I can see it in the API as a Spa component also.
This is what comes from the API
{
componentId: null,
alertState: null,
materialType: null,
targetValue: null,
name: 'HEATER',
componentType: 'HEATER',
value: 'ON',
availableValues: [],
registeredTimestamp: '2025-05-02T15:41:09.921Z',
port: '0',
hour: null,
minute: null,
durationMinutes: null
},
So the ON state shows it. I will keep an eye on that how it goes when we finish bathing tonight.
What does the web portal show you Control My Spa | Balboa Water Group ?
The ON state is working just fine, tried it yesterday too, but did not report it before it happend a second time. But have a look out for, if you get the OFF state or something else, when the heater is done.
On the WEB portal, I can not find the status of the heater. Do you?
Yep I have it:
Maybe they noticed that it is missing and adding it back in their backend.
What I have done today, is that the spa was completely without power for a short service to it. The means that the onboard controller and the gateway has been reset. Don’t know if that trigger a change.
It should not, but a interesting observation. Maybe you triggered a FW update? I will try the power cycle right now.
I do not fin the FW-version anymore in the web, or in the app.
Right, I see now what happens. HEATER component disappears also from the web portal and the APIwhen it goes off. That inturn means the app doesn’t see that it when off.
I’ll look if I can do a workaround, but hopefully they will fix it inthei backend.
Then maybe, if no status, you can return “OFF”? I have now tried the power cycle and it did not made any difference. I guess, When the heater is ON, I also get in the WEB. But the heater was off when I made the screenshot.
Something like that.
I replied to their info email that are they aware that the Heater is not present in their web portal when it is off. Maybe that will trigger them to fix it.
1 Like
