Yes the child devices were created but don’t seem to do anything, toggling the “on” ones on or off,or the “off” ones on or off… except the lights, if spam that one I can get them to turn on or off but still confused as to what sequence actually did it.
I’ll keep playing with it and let you know if I ever get it sorted.
I mentioned before I was primarily using w/ Alexa and just adding any of the child objects result in “not responding” you had suggested virtual switch /rule combo before so I’ll try and see if I can piece that together with the parent device
@KurtSanders I installed your local control app today. I'm getting the same java error on line 548 that @kenro1 is seeing. I have a Balboa controller with 50350-07 WI-FI Module. It seems to find the spa and I can turn the lights on and off. I can't control the pumps or temperature. I don't seem to get any current temperature report either. Let me know if I can help you trouble shoot in some way.
I do see the html panel. How do I add that to a dashboard? I think need to use the Link template but I don't know what to enter in the options fields on the right side.
Please note that one may have to force HPM to update the BWA files using the HPM 'Repair' option. Make sure all listed drivers and app are at version 2.0.0
REQUIRES HPM v1.9.7 or higher for HPM install or update.
Several device driver bug fixes provided by @kenrok1.
Added 2 new parent driver commands 'cyclePump' and 'createChildDevices' to create/control pumps and lights by @kenrok1.
Added several logic checks for a valid spa configuration
Added a new required input field for the spa's IP address in the BWA Spa Manager App - Local. Sends this local IP address to the parent device driver's IP address preference.
Thanks Kurt, this seems to be working. I can control temperature and lights.
I’m a bit confused on the pumps. How do I control individual pumps? There is a child device that turns them all on. But when I hit the off child device I got what seemed like random pump running at various levels.
I’ll play with it more and 90% of use is to bump the temperature up and down so that is a win!!!
The spa's Balboa circuit board controller is very basic, slow to respond, noisy, and is interfaced as a secondary virtual remote push-button controller. This remote mode is similar to the local push buttons on the spa, which control the lights, temperature setpoints, pumps, and operating heat modes.
The spa's WiFi controller module adds complexity to the interface because it connects to the local network, accepts binary sequences, and relays them to the Balboa circuit board. The spa's WiFi controller often randomly disconnects, making the spa appear offline, and it will sometimes auto-reconnect after a random number of minutes.
The BWA Spa Manager app determines the spa's accessories (eg, pumps, lights, heat ranges, etc.) during initial configuration. The created child's switches send a single 'button push' for the respective spa accessory, making it easy to invoke from a dashboard.
These child switches were created as a convenient way to activate the unique spa accessories. One can easily command individual spa accessories (e.g., pumps, lights, etc.) to operate at a level via webCore or Rule Machine using the parent driver's commands.
I have come to learn, through my use, that the TCP low-level interface with the spa's WiFi interface and controller board is very unreliable and quirky. The spa sometimes ignores one or more of the binary sequences that the BWA Spa Manager app sends to command a button press, and the spa is slow to confirm the result before closing the TCP connection.
Hi, I'll chime in too to explain the difference between and
The first one existed before, and this is the one that creates the child switches you'll see as Type "Balboa Hot Tub Local Child Switch" ... it can be confusing because of the execution, say you want to turn the Pumps on, you would trigger "ON" from Set "Spa" Pumps On ("Spa" being whatever you named your parent). Then to turn them Off, you would trigger ON from Set Spa Pumps Off. As Kurt explained think of the ON as the 'button push' and the "Off" button within the child switch is just vestigial.
But also keep in mind whichever one you call the 'button push' from, it is a toggle; if the pumps are already on and you execute On from the Set Spa Pumps Off they will turn off, but if you did that when they are already off - they turn on, and same for the Set Spa Pumps On
The second button creates the individual Light(s) and Pumps as Type "Generic Component Switch" and these work more like a traditional switch ~ but same gotcha here because of the nature of the controller, either Off or On just toggles the current state. Kind of like a 3-way switch would.
and 
