# \[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:** 12

<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:** [February 18, 2023, 8:14am UTC](https://community.homey.app/t/app-pro-balboa/57870/223 "2023-02-18T08:14:19Z")

</div>

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

> **Changelog:**
> 
> **FIXES:**  
> **1** : FIX: app error

* * *
  

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:** [February 18, 2023, 8:15am UTC](https://community.homey.app/t/app-pro-balboa/57870/224 "2023-02-18T08:15:15Z")

</div>

@OH2TH @Jan-Erik_Klokk Made a update which should fix the error. The url structure of one of the endpoint was not correct and it looked like that gave the error.

Let me know if it is fixed 🙂

---

<div class="post-metadata">

**Author:** ![Jan-Erik\_Klokk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan-erik_klokk/32/30919_2.png) [@Jan-Erik\_Klokk](https://community.homey.app/u/Jan-Erik_Klokk)\
**Post date:** [February 19, 2023, 1:47pm UTC](https://community.homey.app/t/app-pro-balboa/57870/225 "2023-02-19T13:47:17Z")

</div>

Installed the update yesterday, I am afraid we still have the same problem, it updated after the install, then it still says online one day ago (the time I installed app)  
and the current temp does not match CMS app

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/2/7280a29724cba306cc016fc454dfa1c0e6144d20.jpeg)

---

<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:** [February 19, 2023, 1:48pm UTC](https://community.homey.app/t/app-pro-balboa/57870/226 "2023-02-19T13:48:15Z")

</div>

@Jan-Erik_Klokk can you send a new report? 🙂

---

<div class="post-metadata">

**Author:** ![Jan-Erik\_Klokk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan-erik_klokk/32/30919_2.png) [@Jan-Erik\_Klokk](https://community.homey.app/u/Jan-Erik_Klokk)\
**Post date:** [February 19, 2023, 2:32pm UTC](https://community.homey.app/t/app-pro-balboa/57870/227 "2023-02-19T14:32:48Z")

</div>

Thoughts I did, will try again👍

---

<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:** [February 19, 2023, 2:35pm UTC](https://community.homey.app/t/app-pro-balboa/57870/228 "2023-02-19T14:35:28Z")

</div>

@Jan-Erik_Klokk Looks like you restarted the app and then sent the report? All logs are gone as soon as you restart, so not much to see there 😛

---

<div class="post-metadata">

**Author:** ![Jan-Erik\_Klokk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan-erik_klokk/32/30919_2.png) [@Jan-Erik\_Klokk](https://community.homey.app/u/Jan-Erik_Klokk)\
**Post date:** [February 19, 2023, 2:36pm UTC](https://community.homey.app/t/app-pro-balboa/57870/229 "2023-02-19T14:36:13Z")

</div>

Was unable with 1st attempt, (entry too large) restarted app then ok.  
2e37569a-b6a5-490a-9b70-9a8d71101499

---

<div class="post-metadata">

**Author:** ![Jan-Erik\_Klokk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan-erik_klokk/32/30919_2.png) [@Jan-Erik\_Klokk](https://community.homey.app/u/Jan-Erik_Klokk)\
**Post date:** [February 19, 2023, 2:37pm UTC](https://community.homey.app/t/app-pro-balboa/57870/230 "2023-02-19T14:37:13Z")

</div>

I will wait then send one later tonight, thanks for the support 👍😊

---

<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:** [February 19, 2023, 3:39pm UTC](https://community.homey.app/t/app-pro-balboa/57870/231 "2023-02-19T15:39:33Z")

</div>

Same here. And diag report was not able to send for the same reason.

I have a feeling that Balboa has changed something in the backend.

---

<div class="post-metadata">

**Author:** ![Jan-Erik\_Klokk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan-erik_klokk/32/30919_2.png) [@Jan-Erik\_Klokk](https://community.homey.app/u/Jan-Erik_Klokk)\
**Post date:** [February 19, 2023, 8:42pm UTC](https://community.homey.app/t/app-pro-balboa/57870/232 "2023-02-19T20:42:27Z")

</div>

Same result again, content to big error when trying to send🥹

---

<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:** [February 19, 2023, 9:19pm UTC](https://community.homey.app/t/app-pro-balboa/57870/233 "2023-02-19T21:19:00Z")

</div>

Really strange. Never saw that for the CMS app. Think something goes wrong 😕

Will try to check tomorrow when running local

---

<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:** [February 20, 2023, 8:02pm UTC](https://community.homey.app/t/app-pro-balboa/57870/234 "2023-02-20T20:02:26Z")

</div>

@Jan-Erik_Klokk checked your latest report, but everything looks fine. Did you experience any issues?

---

<div class="post-metadata">

**Author:** ![Jan-Erik\_Klokk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan-erik_klokk/32/30919_2.png) [@Jan-Erik\_Klokk](https://community.homey.app/u/Jan-Erik_Klokk)\
**Post date:** [February 21, 2023, 7:30am UTC](https://community.homey.app/t/app-pro-balboa/57870/235 "2023-02-21T07:30:32Z")

</div>

I am afraid it is still acting up, the only way to get a report out is not to long after a restart of the app, was hoping to get one before it got to large. Would it be possible to roll back to ver 1.9.1?  
Was noticing something, the hub for the CMS hardware had a flashing blue light (indicating software update) for a while yesterday.

---

<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:** [February 21, 2023, 12:44pm UTC](https://community.homey.app/t/app-pro-balboa/57870/236 "2023-02-21T12:44:42Z")

</div>

It starts throwing a lot of Internal Server Errors and those I think fills up the log and becomes too big to include into the diag-report.

---

<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:** [February 21, 2023, 12:45pm UTC](https://community.homey.app/t/app-pro-balboa/57870/237 "2023-02-21T12:45:18Z")

</div>

Yes indeed. Thats not version related but API related. Already working on a fix 🙂

---

<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:** [February 22, 2023, 8:19pm UTC](https://community.homey.app/t/app-pro-balboa/57870/238 "2023-02-22T20:19:45Z")

</div>

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

> **Changelog:**
> 
> **FIXES:**  
> **1** : FIX: refresh acces\_token when expired

* * *
  

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:** ![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:** [February 22, 2023, 8:20pm UTC](https://community.homey.app/t/app-pro-balboa/57870/239 "2023-02-22T20:20:00Z")

</div>

FYI @OH2TH@Jan-Erik_Klokk ☝

---

<div class="post-metadata">

**Author:** ![Jan-Erik\_Klokk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan-erik_klokk/32/30919_2.png) [@Jan-Erik\_Klokk](https://community.homey.app/u/Jan-Erik_Klokk)\
**Post date:** [February 22, 2023, 9:35pm UTC](https://community.homey.app/t/app-pro-balboa/57870/240 "2023-02-22T21:35:45Z")

</div>

Temp adjustments and other controls to operate the spa seems to work👍, it still does not refresh the status, sent you the log 88e22a4e-699a-40db-8cb7-775e6542e60d

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/c/9c3b3015b65269891e5d5381ae51a29c1bfb6792.jpeg)

Or maybe not, sent new report (requests timed out when tried the various modes lights state etc)  
445c0800-0f90-4bd7-a033-3db9ec27774a

Checked again temp and all commands working maybe I was too quick, will monitor and report back, about the status online is it meant to be counting from last time it was offline or last time the app polled?  
Thanks for your great support 👍

---

<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:** [February 23, 2023, 7:04am UTC](https://community.homey.app/t/app-pro-balboa/57870/241 "2023-02-23T07:04:01Z")

</div>

> [@Jan-Erik\_Klokk](#):
>
> status online is it meant to be counting from last time it was offline

Status is the status as seen by CMS service two your Spa.

The times you see there are the time since that information changed. So you will get different times there depending on the variable you look at.

For example Ready-Rest time since should be the time when the spa ready-mode was switched betwen Ready-Rest.

And if you restart the app on Homey, those get of course reset 🙂

---

<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:** [February 23, 2023, 7:06am UTC](https://community.homey.app/t/app-pro-balboa/57870/242 "2023-02-23T07:06:21Z")

</div>

So far looking ok.

This is the problem, when the API needs to be reverse engineered since there is no documented API, this go for authentication and authorization also.

But I guess this is the simpler of the APIs that have been rev-engineered.

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

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