# \[APP\]\[Pro\] Balboa

**URL:** <https://community.homey.app/t/app-pro-balboa/57870>\
**Category:** Apps\
**Tags:** app, official, homey-pro\
**Created:** [January 5, 2022, 2:44pm UTC](https://community.homey.app/t/app-pro-balboa/57870 "2022-01-05T14:44:00Z")\
**Posts on this page:** 20\
**Page:** 10

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [January 13, 2023, 12:28pm UTC](https://community.homey.app/t/app-pro-balboa/57870/182 "2023-01-13T12:28:31Z")

</div>

I’ll make some changes to the library and to the celsius calculation in the app itself 🙂

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [January 13, 2023, 4:41pm UTC](https://community.homey.app/t/app-pro-balboa/57870/183 "2023-01-13T16:41:06Z")

</div>

## New app update (TEST: [1.7.3](https://homey.app/a/com.balboa/test)):

> **Changelog:**
> 
> **NEW:**  
> **1** : NEW: recover after API outage  
> **2** : NEW: use response data
> 
>   
> 
> **FIXES:**  
> **1** : FIX: temperature issues  
> **2** : FIX: login error (pairing)  
> **3** : FIX: wrong button handler for tempRange  
> **4** : FIX: dynamic thermostat min/max based on tempRange Low/High  
> **5** : OPT: update library

  

* * *
  

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)

  

* * *
  

> You can install the **test** version by clicking the link above and press install
> 
> **Don’t want to be part of this test version?** Install the live version → [Balboa | Homey](https://homey.app/a/com.balboa/)

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [January 13, 2023, 4:49pm UTC](https://community.homey.app/t/app-pro-balboa/57870/184 "2023-01-13T16:49:34Z")

</div>

@OH2TH hope this works.  
One thing I was not sure about is the responseData when you set the temp for example. As I don’t have a test account anymore I couldn’t test. 😛

if you want to check the changes: [FIX: temperature | OPT: update library | NEW: use response data · martijnpoppen/com.balboa@377bcfe · GitHub](https://github.com/martijnpoppen/com.balboa/commit/377bcfe061ec43ff77fd9c9f974003c5951dd5db)

and feel free to create a PR ofcourse 😃

---

<div class="post-metadata">

**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\
**Post date:** [January 13, 2023, 5:51pm UTC](https://community.homey.app/t/app-pro-balboa/57870/185 "2023-01-13T17:51:33Z")

</div>

Test version seems to be restaring continuously. Device flashed as unavailable momentarily every couple of seconds.

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [January 13, 2023, 6:41pm UTC](https://community.homey.app/t/app-pro-balboa/57870/186 "2023-01-13T18:41:13Z")

</div>

Ah i see. Strange behaviour. Because that should have happened in the previous too. Unless its looping due to the recent changes. Will have a look!

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [January 13, 2023, 6:52pm UTC](https://community.homey.app/t/app-pro-balboa/57870/187 "2023-01-13T18:52:04Z")

</div>

@OH2TH New version is in test (1.7.3

---

<div class="post-metadata">

**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\
**Post date:** [January 14, 2023, 4:02am UTC](https://community.homey.app/t/app-pro-balboa/57870/188 "2023-01-14T04:02:25Z")

</div>

Oh yes, first test looks good. High/Low range toggle works. I’ll test a little more when I wake up.

---

<div class="post-metadata">

**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\
**Post date:** [January 14, 2023, 2:01pm UTC](https://community.homey.app/t/app-pro-balboa/57870/189 "2023-01-14T14:01:16Z")

</div>

Something is a bit off with the target temperature now.  
CMS Mobile shows target as 36.5C and CMS Homey shows 37, as requested.

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [January 15, 2023, 1:41pm UTC](https://community.homey.app/t/app-pro-balboa/57870/190 "2023-01-15T13:41:07Z")

</div>

@OH2TH I do some rounding in de Homey app. Not sure if CMS allows steps of 0.1?

---

<div class="post-metadata">

**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\
**Post date:** [January 19, 2023, 6:53am UTC](https://community.homey.app/t/app-pro-balboa/57870/191 "2023-01-19T06:53:38Z")

</div>

I’ll grab the source and do some testing for this bit

> <https://github.com/martijnpoppen/com.balboa/blob/6ca7c367f5d447a92e617f1c2aea2693e460b88e/drivers/main-device.js#L300>

CMS returns three values, but only when it has been recently active, i.e. when CIRCULATION\_PUMP is HIGH

```auto
"desiredTemp":"93.2","targetDesiredTemp":"93.6","currentTemp":"94.1"

```

After a while when it has gone OFF, CMS returns only targetDesiredTemp. What I do not understand what is the actual difference to desiredTemp and targetDesiredTemp.

Once I figure out how it acts, I’ll send a PR for you.

---

<div class="post-metadata">

**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\
**Post date:** [January 19, 2023, 9:26am UTC](https://community.homey.app/t/app-pro-balboa/57870/192 "2023-01-19T09:26:28Z")

</div>

Oh, but I can’t test. I need to set the SECRET in env.json. Is that a string and how many characters?  
I guess I will need to configure an other balboa device for testing with locally installed app.

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [January 19, 2023, 9:43am UTC](https://community.homey.app/t/app-pro-balboa/57870/193 "2023-01-19T09:43:06Z")

</div>

@OH2TH I’ll send you some instructions in a DM.

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [January 22, 2023, 3:42pm UTC](https://community.homey.app/t/app-pro-balboa/57870/194 "2023-01-22T15:42:15Z")

</div>

## New app update (TEST: [1.8.0](https://homey.app/a/com.balboa/test)):

> **Changelog:**
> 
> **NEW:**  
> **1** : NEW: temperature fixes (@OH2TH)

* * *
  

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)

  

* * *
  

> You can install the **test** version by clicking the link above and press install
> 
> **Don’t want to be part of this test version?** Install the live version → [Balboa | Homey](https://homey.app/a/com.balboa/)

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [January 22, 2023, 3:43pm UTC](https://community.homey.app/t/app-pro-balboa/57870/195 "2023-01-22T15:43:47Z")

</div>

Thanks a lot to @OH2TH for fixing the Temperature issue! 😃 🎉

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [January 23, 2023, 1:22pm UTC](https://community.homey.app/t/app-pro-balboa/57870/196 "2023-01-23T13:22:42Z")

</div>

## New app update (LIVE: [1.8.0](https://homey.app/a/com.balboa)):

> **Changelog:**
> 
> **NEW:**  
> **1** : NEW: temperature fixes (@OH2TH)

* * *
  

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)

---

<div class="post-metadata">

**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\
**Post date:** [January 31, 2023, 4:10am UTC](https://community.homey.app/t/app-pro-balboa/57870/197 "2023-01-31T04:10:37Z")

</div>

## Heater Mode is mixed up with HEATER status

These relate to Rest mode vs Ready mode:

- Heater Ready mode - Maintain the selected temperature
- Heater Rest mode - Only heat during filter cycle

**What would you, ControlMySpa users, think of a change:**  
Remove measure\_runmode as it just duplicates measure\_heater\_mode, removing:

- Trigger (When) card: Is ready state changed
- Condition (And) card: is ready

You can still use Heater has changed (should be renamed to Heater Mode has changed for trigger and heater is ready (should be renamed to “Heater is in Ready mode”).  
And the “Toggle Heater on or off” action (then) card will stay as it is.

Github issue opened [heaterMode is mixed up with HEATER status · Issue #6 · oh2th-homey/com.balboa · GitHub](https://github.com/martijnpoppen/com.balboa/issues/6)

After above changes, it would be doable to introduce Heater Status if is ON or OFF, Showing that the spa is actually heating or not.

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [January 31, 2023, 10:21am UTC](https://community.homey.app/t/app-pro-balboa/57870/198 "2023-01-31T10:21:40Z")

</div>

@OH2TH

The way I see it:

- change measure\_heater\_mode to:

```auto
  "title": {
    "en": "Heater mode",
    "nl": "Verwarmings modus"
  },

```

- change `action_heater_mode` to listen to the HEATER component. That button will also toggle the heater to ON/OFF

- leave measure\_runmode as is. As it does take another key from the API and we don’t want to deprecate this as it might be different on other spa’s

Made a PR for this: [FIX: heater and heater\_mode by martijnpoppen · Pull Request #11 · martijnpoppen/com.balboa · GitHub](https://github.com/martijnpoppen/com.balboa/pull/11/files)

---

<div class="post-metadata">

**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\
**Post date:** [January 31, 2023, 3:51pm UTC](https://community.homey.app/t/app-pro-balboa/57870/199 "2023-01-31T15:51:01Z")

</div>

After some tests and reviews on the PR, it is starting to look good. I think some of the options that are in the app now, will start making more sense soon.

One thing comes to mind more. Not sure if everyone would agree, but here goes:  
Tie the “uiQuickAction” to action\_heater\_mode, this would mean that the device tile would start acting like on/off toggle button.

---

<div class="post-metadata">

**Author:** ![martijnpoppen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijnpoppen/32/84849_2.png) [@martijnpoppen](https://community.homey.app/u/martijnpoppen)\
**Post date:** [January 31, 2023, 4:05pm UTC](https://community.homey.app/t/app-pro-balboa/57870/201 "2023-01-31T16:05:00Z")

</div>

> [@OH2TH](#):
>
> One thing comes to mind more. Not sure if everyone would agree, but here goes:  
> Tie the “uiQuickAction” to action\_heater\_mode, this would mean that the device tile would start acting like on/off toggle button.

Might be possible, but not sure if that’s clear for everybody. This could lead to accidential heating of the spa

---

<div class="post-metadata">

**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\
**Post date:** [January 31, 2023, 4:26pm UTC](https://community.homey.app/t/app-pro-balboa/57870/202 "2023-01-31T16:26:33Z")

</div>

> [@martijnpoppen](#):
>
> could lead to accidential heating

Yes, that is also true.

[Previous page](https://community.homey.app/t/app-pro-balboa/57870.md?page=9)

[Next page](https://community.homey.app/t/app-pro-balboa/57870.md?page=11)
