[Release] New BWA Spa Manager (Cloud Control & Direct Local TCP)

These two Hubitat applications allow one to connect to a network connected spa, which is equipped with a Balboa Water Group 50350-07 WI-FI Module with 7ft interface cable for BP Systems.

Integrate your spa Balboa BP Control System WiFi Module to the Hubitat environment with the following features:

  1. View real-time temperature
  2. Set spa's clock time to the same as the Hubitat Hub.
  3. Set heatingSetPoint temperature
  4. Turn on/off lights and pumps
  5. Set & automate High/Low & Rest/Ready modes to reduce energy usage
  6. Control spa using Hubitat's Rules/WebCore

Choose from one type connection below for spa control:

1. Cloud Control App & Drivers (Legacy)

  • The Hubitat Hub indirectly connects to the Control System WiFi Module via the internet BWA Cloud Server.
    • The BWA Cloud server often loses connection to the Control System WiFi Module which makes this app unreliable,
  • Requires Spa Control - BWA mobile app for spa configuration and access.
    • Download app from Apple/Goggle app stores and create a username and password.
    • Install app/drivers using HPM.

2. Direct Local TCP Drivers (New)

  • The Hubitat Hub connects directly to the Spa Control System WiFi Module via the home network.
  • Since the Hubitat Hub creates a raw TCP socket directly to the Spa Control System WiFi Module, this parent driver provides a fast & robust connection.
  • The Spa's WiFi module must be on the same network as Hubitat hub.
  • Requires Spa Control - BWA mobile app for spa network configuration and access.
    • Download app from Apple/Goggle app stores and create a username and password.
    • Install parent driver using HPM.
  • Creates several child device virtual switches to refresh spa status & control the spa's pumps, lights, heat mode (Ready/Rest) and heat range (high/low).

Version Notes on Github

Connection Type Version Release Date
Cloud Version 2.02 Mar-11-2025
Local Version 0.03 Mar-13-2025
Please be advised that this latest release with all these new features may introduce some unwanted bugs that hopefully we can identify and work to correct. Each spa has a different configuration (e.g., pumps, lights, blowers, misters, etc) and therefore I can only test on my BullFrog A7L model. If your current release of BWA Spa Manager is working and you are completely satisfied, I would suggest you not overwrite your working release, and install this on a separate hub (if you have multiple hubs).
2 Likes

New 'BWA Spa Manager - Local' Version Announcement

  • A new Spa Manager App - Local installation starter app is now part of the application suite to help users with the initial install the required drivers below.
  • The new app will also assist {optionally} to rename the spa's parent driver.
  • Spa parent device child switches are automatically created when the app is first installed.

HPM Install/Upgrade FAQs:

New Installs:

  • Install via HPM are highly recommended. Search for BWA Spa Manager and select the BWA Spa Manager - Local App version.

Previous Versions of this App:

  • If you try to upgrade a previous version via HPM and notice that your hub has multiple versions of the device drivers or libraries listed below, use HPM to uninstall the app.
  • If HPM displays an error with removing this app, use HPM's 'Package Manager Settings' option and then select ' Un-Match a Package to make HPM remove any of it's cached information of the previous versions of this app.
  • Check the hub's drivers code and library code views for residual files listed below, If they exists, manually delete ALL/ANY of the application's drivers, app and libraries files that might still be installed. This will allow HPM to install as a fresh new install.
  • Perform a new install via HPM. Search for BWA Spa Manager and select the Local version to install. HPM will automatically launch the Application and create the required spa control devices.

'BWA Spa Manager - Local' TCP Control Application Files

Filename Type Version
BWA Spa Manager App - Local.groovy App Version 0.0.4
Balboa Hot Tub Local Driver.groovy Parent Device Driver Version 0.0.4
Balboa Hot Tub Local Child Switch.groovy Child Device Driver Version 0.0.4
Balboa-Hot-Tub-API-Library.groovy App Library Version 0.0.4
SanderSoft-Library.groovy Main Library Version 0.0.5

BWA Spa Manager - Local Application Installation Screen

1 Like

Hi Kurt - first, thank you for the work you put into this. I just got around to updating ~ not sure what version I was running previous but I'm now running into an issue with child devices and hoping you might be able to help. My pumps are single-speed only so they only respond to on/off... if I change them to binary switches they work fine but as soon polling runs they revert back. I also tried the local driver and pumps don't get discovered at all (the only child objects that show up are Heat Mode and Temp Range.

Oh, sorry to hear that. I'm guessing that the app is not checking for the pump speeds in the cloud based version of this app and assumes a Low, High, Off, like my Bullfrog A7.

Just curious, is your Balboa controlled spa on the same home network as your hubitat hub? If so, have you tried the newer 'BWA Spa Manager - Local TCP Direct Connection' in HPM. It does not use the cloud for control and accesses the spa direct for control.

oh yes - I guess I didnt say that correctly, when I said I tried the local driver - I meant the new App with Local direct connection. When it discovers the child objects it doesn't see any pumps at all just finds

The new Balboa Hot Tub Local Parent Device Driver has an On/Off' switch attribute that when activated (for example via a dashboard, WebCore or Rule), will turn on all "detected" spa pumps and lights for you to prepare the spa for one's pleasure. The child device switches are for individual spa controls for the dashboard.

The Balboa Hot Tub Local Parent Device Driver also has some "commands" to cycle spa pumps through their speeds, set the spa's internal clock to the time on the hub, etc....

OK that is different than what I'm used to / was expecting - I did see where I could turn everything on from the parent.

1 Like

Let me know if this version works for you. I have been using this local version of the Balboa Spa app for sometime. It works better/faster than the original cloud control version.

I still get random WiFi Spa Module disconnects from my Netgear Orbi system. It appears that Balboa's WiFi controller is prone to these and re-connects after a small amount of time.

Here is a chart of the Spa WiFi's disconnects (black) and Online (Green) below:

The parent driver tracks Online/Offline as Present/Not Present attribute

I don't use any dashboards - so the real advantage to me was the Alexa integration - being able to say "Alexa, turn on spa pump 1" or "turn on spa lights" - I can't figure out how to do that with local integration - since when I added it just configures the parent with just one on/off... even if a rename it to something other than Balboa Hot Tub Local Driver :slight_smile: it just turns on all the pumps but not the lights

This parent and child devices will work with Alexa for voice control. You just need to add those devices and switches to Amazon Alexa Skill so that Alexa can gain access to them.

Suggestions:

  • Create a virtual switch and use Hubitat Rules to turn on and off the pumps and lights you chose with the parent devices commands.
  • Create Alexa Routines to automate several spa controls, like "Alex, turn on the Spa Lights" and/or "Alexa Turn on the spa pumps" and these can control the virtual switch which activates a Hubitat Rule to send commands to the parent driver.

The next version of this app , I will add child switches for control of pumps on/off and lights on/off. It will take a few days or more to add these. Thanks for the suggestions.

I was incorrect, the spa lights do not turn on with the parent On/Off switch, it only controls the pumps. I will add lights to this parent switch so that lights and pumps all turn on or off.

1 Like