@Daniel_Johansson3 please send a diagnostic report so i can see what goes wrong 
Reported now
1 Like
Working great 
Thanks for the great collaboration 
2 Likes
Wow, sounds great!
But what am I missing, mine is not working…are the credentials the same as for (Cloud Connect) in the ”Spa Control” App from Balboa BWA?
I can install the app
I can Add my device Balboa BWA
But no values are updated in the app and the controls have no effect
1 Like
@Daniel_Johansson3 i hope @Kjetil_Vert can answer that 
1 Like
yes the credential is the same as for the cloud connect in the balboa bwa app.
so a username not a email and the password you have
1 Like
New app update (
TEST: 2.0.4):
Changelog:
NEW:
1: BREAK: App rebrand to Balboa
2: NEW: add Balboa BWA
3: NEW: improve login screenFIXES:
1: FIX: issue with decoding in BWA
If you find any issues, send a report via the mobile homey app
More - apps - ControlMySpa - settings wheel right top - send diagnostic report (put your email in the input field to make it easier)
2 Likes
Thanks!
Since last update 2.0.4 it works
2 Likes
New app update (
LIVE: 2.0.4):
Changelog:
NEW:
1: BREAK: App rebrand to Balboa
2: NEW: add Balboa BWA
3: NEW: improve login screenFIXES:
1: FIX: issue with decoding in BWA
If you find any issues, send a report via the mobile homey app
More - apps - ControlMySpa - settings wheel right top - send diagnostic report (put your email in the input field to make it easier)
2 Likes
Hi, I could connect to Balboa BWA but not ControlMy Spa?
What I doing wrong?
In ControllMy Spa there is more settings.
I use the same credentials that I use in BWA. The anser I get is “No device found” (In swedish “Inga enheter hittades”)
I use v2.0.4 in 2023 Pro
@Magnus_Sward do you have a controlmyspa module?
Oops, probably not…
@Magnus_Sward then it wont work
Ok, thanks for quick respons!
1 Like
Something strange going on with the target temperature on CMS.
API returns
[log] [Device] poreallas CMS - deviceInfo => {
runMode: ‘Rest’,
desiredTemp: ‘92.3’,
targetDesiredTemp: ‘93,2’,
currentTemp: ‘88.7’,
While UI shows:
I suspect they changed something in the API , again.
setValue says:
[log] [Device] poreallas CMS - setValue => target_temperature => NaN
And now I see what the problem is, they did break the API. the decimal char in targetDesiredTemp is ‘,’ and not ‘.’
Made a PR FIX: Workaround for number format error in desiredTemp from CMS API by oh2th · Pull Request #14 · martijnpoppen/com.balboa · GitHub for you to catch the API issue to make it back into a valid Number.
[log] [Device] poreallas CMS - setValue => target_temperature => 34
Seems that the API broke on 2023-12-19 as the graph started showing the null value then:
1 Like
@OH2TH Thanks fir the fix.
I left one comment, but i think it’s good for now
Luckily Balboa doesn’t change their API that much 
New app update ( LIVE: 2.0.5):
Changelog:
NEW:
1: noneFIXES:
1: FIX: ControlMySpa targettemperature
If you find any issues, send a report via the mobile homey app
More - apps - Balboa - settings wheel right top - send diagnostic report (put your email in the input field to make it easier)
Not much anyway, however seems that there is another problem with the API now where REST/Ready mode switching does not work. This is also on the CMS mobile app, so that suggests the problem is at CMS API.
1 Like
And this morning REST/Ready toggle works again, both from CMS mobile and from this app.
1 Like
Filter Schedule
The CMS API has filter scheduling with a quite complex way of doing it. Would it be possible to:
- Show the time and duration value for the first and second schedules, if set. Null value if not set.
- Flow cards for:
- When: Filter cycle state changed.
- And: Filter cycle is/isn’t active.
Then: Action card to set the filter cycles already exists.
1 Like
