Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Balboa spa client not detecting pumps or lights #79391

Closed
kiwiRickNZ opened this issue Oct 1, 2022 · 38 comments
Closed

Balboa spa client not detecting pumps or lights #79391

kiwiRickNZ opened this issue Oct 1, 2022 · 38 comments

Comments

@kiwiRickNZ
Copy link

kiwiRickNZ commented Oct 1, 2022

The problem

the Balboa spa client is not detecting the 3 pumps on my spa or the lights.

the climate and circulation pump appear to be working.

What version of Home Assistant Core has the issue?

20220907.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Balboa Spa Client

Link to integration documentation on our website

https://www.home-assistant.io/integrations/balboa/

Diagnostics information

MBP21UX
by Balboa Water Group
Firmware: M100_225 V43.0

sorry I don't know how. im more than happy to provide some kind of logs if there's a tutorial on how to do it

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

The spa works in openhab ok so the connection is ok

@homeassistant
Copy link
Contributor

Hey there @garbled1, mind taking a look at this issue as it has been labeled with an integration (balboa) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)


balboa documentation
balboa source
(message by IssueLinks)

@modert
Copy link

modert commented Oct 27, 2022

I'm also having this issue, please let me know how I can assist in troubleshooting!

@davericher
Copy link

Same, and same sentiment as the person above me ^ :D

@kiwiRickNZ
Copy link
Author

@garbled1 hi Tim, have you had a chance to look at this yet?

@kiwiRickNZ
Copy link
Author

@natekspencer hey Nate, is this something that you might be able to help with?

@VK3GG
Copy link

VK3GG commented Nov 13, 2022

Same here.

@kiwiRickNZ
Copy link
Author

Bump @garbled1 @natekspencer if either of you guys had time to look at this id really appreciate it as would the outer people with the same issue 😊

@natekspencer
Copy link
Contributor

If any of you could run the pybalboa python package directly with your spa IP and submit the information here, as well as your spa model/expected config, that would be helpful. You'll have to make sure you disable this integration when running this or it won't be able to connect to your spa since it only allows one connection to the IP at a time.

@VK3GG
Copy link

VK3GG commented Dec 19, 2022

@natekspencer happy to help, but no idea how to do this - can you give some direction?

@kiwiRickNZ
Copy link
Author

hey @natekspencer im in the same boat as @VK3GG. I'm not sure how to do that but really want to get it sorted could you help out all?

@400killer
Copy link

I think I am having a similar issue, as I don't have any filter sensors. But the integration imported two. And I do have two pumps, that did not show up. I feel like the integration mistakenly brought in the two pumps as binary sensors labeled filter1 and filter 2. They do not have any status change with the pumps. The Two Pumps, and the Light show in the Balboa App, and function. All the filled in for the entity's for me is the temp, heat, rest under the clime. And two filter entity's that don't do anything.

@400killer
Copy link

Running the Debug in the logs I got the following
2022-12-19 09:20:11.173 DEBUG (MainThread) [homeassistant.components.balboa.const] Starting listener and monitor tasks
2022-12-19 09:20:11.173 DEBUG (MainThread) [pybalboa.balboa] Sending message: 7e050abf04777e
2022-12-19 09:20:11.174 DEBUG (MainThread) [pybalboa.balboa] Sending message: 7e080abf22000001587e
2022-12-19 09:20:11.174 DEBUG (MainThread) [pybalboa.balboa] Sending message: 7e080abf22020000897e
2022-12-19 09:20:11.174 DEBUG (MainThread) [pybalboa.balboa] Sending message: 7e080abf22040000f47e
2022-12-19 09:20:11.174 DEBUG (MainThread) [pybalboa.balboa] Sending message: 7e080abf22010000347e
2022-12-19 09:20:11.505 DEBUG (MainThread) [pybalboa.balboa] Sending message: 7e080abf22000001587e
2022-12-19 09:20:12.034 DEBUG (MainThread) [homeassistant.components.balboa.const] Primary update callback triggered
2022-12-19 09:20:12.178 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.balboa
2022-12-19 09:20:12.180 INFO (MainThread) [homeassistant.components.climate] Setting up climate.balboa
2022-12-19 09:20:12.184 DEBUG (MainThread) [homeassistant.components.balboa.const] Setting up daily time sync
2022-12-19 09:20:12.184 DEBUG (MainThread) [homeassistant.components.balboa.const] Syncing time with Home Assistant
2022-12-19 09:20:12.184 DEBUG (MainThread) [pybalboa.balboa] Sending message: 7e070abf210914e17e

@400killer
Copy link

I am running Homeassistant on an Intel Nuc via the system image.
HA 2022.10.4
Supervisor 2022.11.2
OS 9.2
Frontend 20221010.0-latest

@400killer
Copy link

@natekspencer I ran the python program above, and pasted the results in the other topic. as well as logs in debug mode from HA above.

@natekspencer
Copy link
Contributor

Thanks, I'll take a look

@natekspencer
Copy link
Contributor

Ahh ok, I know the issue now. Currently, the only two entities for the official integration implemented are the climate and the binary sensor (for filter cycles/circ pump). I use my HACS integration still because the official HA core integration hasn't been completed. @garbled1 had started on it, but doesn't look like there has been any new progress on it.

@400killer
Copy link

I deleted the HA integration, and installed it through HACS. And restarted. I then went to add the integration and it shows as a custom component now. But I get "Config flow could not be loaded: {"message":"Invalid handler specified"}" when I click it to install it and add my IP. I am guessing it's a collision with the fact that there is official integration with the same name...

@VK3GG
Copy link

VK3GG commented Dec 19, 2022 via email

@natekspencer
Copy link
Contributor

natekspencer commented Dec 19, 2022

Try using this repository in HACS: https://github.com/natekspencer/hacs-balboa

I released a beta version today with the latest I've been using

@400killer
Copy link

I added the repository to HACs. And it installed correctly. And I now have 12 entities associated with the device. Works great for me. Thanks for taking the time!!! You didn't have too. And you probably helped 3 or 4 people, if it works for them too.

@VK3GG
Copy link

VK3GG commented Dec 19, 2022 via email

@400killer
Copy link

@natekspencer I spoke a little too soon. I have two issues...

  1. I did not import the balboa.climate entity. It looks like the variable is no longer valid on 2022.10.4. I posted the log entry below.

  2. Also then I turn pump 2 on. It turns pump one on for the heater as well, as design. And the status in HA shows Pump 1 turn on. But then the status of pump 2 goes back to off. So it will turn the pump 2 on, but doesn't get status of it actually turning Pump 2 on. So its shows it as off in HA again. So it cant turn it off. I saw this in the download I sent into the other topic as well.

Climate error Log entry:
Logger: homeassistant.setup
Source: setup.py:320
First occurred: 1:14:13 PM (1 occurrences)
Last logged: 1:14:13 PM

Unable to prepare setup for platform balboa.climate: Platform not found (cannot import name 'UnitOfTemperature' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py)).

@natekspencer
Copy link
Contributor

  • I did not import the balboa.climate entity. It looks like the variable is no longer valid on 2022.10.4. I posted the log entry below.

The UnitOfTemperature was introduced in 2022.11.0. So you'll need to upgrade to at least that for the climate entity to work.

  • Also then I turn pump 2 on. It turns pump one on for the heater as well, as design. And the status in HA shows Pump 1 turn on. But then the status of pump 2 goes back to off. So it will turn the pump 2 on, but doesn't get status of it actually turning Pump 2 on. So its shows it as off in HA again. So it cant turn it off. I saw this in the download I sent into the other topic as well.

If you can enable debug logs for pybalboa, then I might be able to see what it is doing. Please post this issue in https://github.com/natekspencer/hacs-balboa/issues now, however, as we are no longer talking about the official integration.

@400killer
Copy link

Will do. It will be in an hour or so. I have a call I need to be on. Thanks again.

@Manbearpig92
Copy link

Manbearpig92 commented Mar 2, 2023

@natekspencer So happy I found this! It works phenomenal. I do have 1 question tho, how do you modify the pump settings? I have 1 pump 2 speeds. (3 settings total: off, circulate, jets full power) the toggle button has a little glitch when the pump is off I toggle the pump switch and it activates circulation mode. When I toggle the pump switch from on to off it goes to "jets full power" for 1 second and then toggles back automatically to circulation mode. I let it circulate for a while and then the the pump shut off.

@natekspencer
Copy link
Contributor

Please enable debug logging for this integration and post the logs as well as your spa/pump information

@Manbearpig92
Copy link

2023-03-02 20:09:31.657 DEBUG (MainThread) [pybalboa.client] 192.168.86.249 <- TOGGLE_STATE: 060abf1104e2
2023-03-02 20:09:31.658 DEBUG (MainThread) [pybalboa.client] 192.168.86.249 <- TOGGLE_STATE: 060abf1104e2
2023-03-02 20:09:34.543 DEBUG (MainThread) [pybalboa.client] 192.168.86.249 <- TOGGLE_STATE: 060abf1104e2
2023-03-02 20:09:34.544 DEBUG (MainThread) [pybalboa.client] 192.168.86.249 <- TOGGLE_STATE: 060abf1104e2

Currently the hottub is in a filter cycle and I hit the toggle switch, and this is the result.

the Spa is a beachcomber 340 Leep. I did replace the heater with a Balboa BP7 with TP500 Bundle and I kept the Pump the same. the pump is a century 3.0
Screenshot_20230302_202052_Gallery

@Manbearpig92
Copy link

2023-03-02 20:07:05.471 DEBUG (MainThread) [pybalboa.client] 192.168.86.249 -> STATUS_UPDATE: 20ffaf13000367140602040100080c010000000000000120660000001e000012
2023-03-02 20:09:31.657 DEBUG (MainThread) [pybalboa.client] 192.168.86.249 <- TOGGLE_STATE: 060abf1104e2
2023-03-02 20:09:31.658 DEBUG (MainThread) [pybalboa.client] 192.168.86.249 <- TOGGLE_STATE: 060abf1104e2
2023-03-02 20:09:34.543 DEBUG (MainThread) [pybalboa.client] 192.168.86.249 <- TOGGLE_STATE: 060abf1104e2
2023-03-02 20:09:34.544 DEBUG (MainThread) [pybalboa.client] 192.168.86.249 <- TOGGLE_STATE: 060abf1104e2

@natekspencer
Copy link
Contributor

One thing maybe to clarify here is the way the pumps work in the balboa app (which this attempts to reproduce). The pumps "toggle" to each subsequent setting, so if a pump has 2 settings (off/on) it will go off -> on -> off. If it has 3 settings (off/low/high), it will go off -> low -> high -> off. In HA, you essentially see a shortcut from on to off which has to toggle the pump multiple times potentially to get it to the off state, which is why you see it go full speed for a second first. I'm curious what you see in the "Spa Control" app when you toggle the pump (i.e. does it go to "circulation" after attempting to turn it off)

@Manbearpig92
Copy link

@natekspencer I just ran a little test and currently the spa is not in any filter mode so the pump is off. I had the Balboa app opened on my phone, I toggled the pump1 switch in home assistant (off->on) and watched the Balboa app pump change from off --> low. I toggled pump1 in home assistant again (on->off) and the pump in the Balboa app looked like it went to high for a fraction of a millisecond before landing in the off state. Hard to say without knowing forsure if it actually did go to high or if the image just changed so fast I couldn't make it out. So now that the pump is in the off state I decided to try from the Balboa app and watch the HA Integration. While the pump is off I toggled the pump (off->low), and in Home assistant pump 1 went from off to on. I toggled the Balboa app pump 1 more time (low->high) and the home assistant pump1 remained unchanged and stayed on.

Screenshot_20230303_123815_Spa Control.jpg

@natekspencer
Copy link
Contributor

@Manbearpig92 it seems to be working as intended then. If you open up the pump entity in HA, you should also have a speed setting slider below it that allows you to adjust it there.

@Manbearpig92
Copy link

Ah okay my greatest apologies I didn't realize there was a slider. Yes it does work quite well. Thanks so much for your help

@tonyfitzs
Copy link

I am having the same problem as described in this issue. I have just installed the BWA interface to my spa, I have connected it and can control it via my mobile phone.
In Home Assistant, the BWA interface is being detected and I can see only 4 entities,
• binary_sensor.bp601g1_circ_pump
• climate.bp601g1_climate
• binary_sensor.bp601g1_filter1
• binary_sensor.bp601g1_filter2
I have turned logging on, I have filtered out only logs related to pybalboa.client, homeassistant.components.balboa or pybalboa.control as you can see, when I turn the pumps, lights and other functions on the spa, they are getting captured in the logs, but they are not being enabled as controls within Home Assistant.
I suspect that the Spa controller is being misidentified, the spa controller is a BP601G1 and is configured with 2 high speed pumps, a circulation pump, Ozone Injector and Lights.

2023-03-10 14:56:01.111 DEBUG (MainThread) [homeassistant.components.balboa] Attempting to connect to 10.110.11.104 2023-03-10 14:56:01.111 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -- establishing connection 2023-03-10 14:56:01.239 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -- connected 2023-03-10 14:56:01.963 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 <- DEVICE_PRESENT: 050abf0477 2023-03-10 14:56:01.964 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 <- REQUEST_SYSTEM_INFORMATION: 080abf2202000089 2023-03-10 14:56:01.965 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 <- REQUEST_SETUP_PARAMETERS: 080abf22040000f4 2023-03-10 14:56:01.965 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 <- REQUEST_DEVICE_CONFIGURATION: 080abf2200000158 2023-03-10 14:56:01.966 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 <- REQUEST_FILTER_CYCLE: 080abf2201000034 2023-03-10 14:56:01.988 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3700000306031c000002030000000000490000001e00008f 2023-03-10 14:56:01.988 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Temperature range is now HIGH (1) 2023-03-10 14:56:01.989 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Heat mode is now READY (0) 2023-03-10 14:56:02.337 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> MODULE_IDENTIFICATION: 1e0abf940214800015278a36230000000000000000001527ffff8a36236a 2023-03-10 14:56:02.401 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> SYSTEM_INFORMATION: 1a0abf2464ce2c004250363031473120020b27d3060306000092 2023-03-10 14:56:02.443 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3700000306031c000002030000000000490000001e00008f 2023-03-10 14:56:02.553 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> SETUP_PARAMETERS: 0f0abf250602326350684103410269 2023-03-10 14:56:02.647 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> DEVICE_CONFIGURATION: 0b0abf2e050001900068bd 2023-03-10 14:56:03.318 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> FILTER_CYCLE: 0d0abf23120001008800000fcf 2023-03-10 14:56:03.504 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3700000306031c000002030000000000490000001e00008f 2023-03-10 14:56:04.333 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 <- SET_TIME: 070abf218e38f8 2023-03-10 14:56:04.630 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3800000306031c000002030000000000490000001e00007a 2023-03-10 14:57:04.450 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3900000306031c000002030000000000490000001e0000c3 2023-03-10 14:58:04.423 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3a00000306031c000002030000000000490000001e00000f 2023-03-10 14:59:04.403 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3b00000306031c000002030000000000490000001e0000b6 2023-03-10 14:59:09.795 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3b00000306031c000002000000000000490000001e00000d 2023-03-10 14:59:09.795 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Light 1 is now OFF (0) 2023-03-10 14:59:13.396 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3b00000306031c000002030000000000490000001e0000b6 2023-03-10 14:59:13.397 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Light 1 is now ON (1) 2023-03-10 14:59:16.997 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3b00000306031c000002000000000000490000001e00000d 2023-03-10 14:59:16.997 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Light 1 is now OFF (0) 2023-03-10 14:59:20.592 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3b00000306030c020002000000000000490000001e0000e9 2023-03-10 14:59:20.592 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Pump 1 is now ON (2) 2023-03-10 14:59:25.691 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3b00000306030c000002000000000000490000001e0000ed 2023-03-10 14:59:25.691 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Pump 1 is now OFF (0) 2023-03-10 14:59:29.291 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3b00000306030c080002000000000000490000001e0000fd 2023-03-10 14:59:29.292 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Pump 2 is now ON (2) 2023-03-10 14:59:31.688 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3b00000306030c000002000000000000490000001e0000ed 2023-03-10 14:59:31.689 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Pump 2 is now OFF (0) 2023-03-10 14:59:34.128 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480e3b00000306030c080002000000000000490000001e0000fd 2023-03-10 14:59:34.129 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Pump 2 is now ON (2) 2023-03-10 15:00:04.392 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480f0000000306030c080002000000000000490000001e000020 2023-03-10 15:04:19.759 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480f0401000306030c0000020000000000004900000000000006 2023-03-10 15:04:19.759 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Heat mode is now REST (1) 2023-03-10 15:04:39.865 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480f0401000306030800000200000000000048000000000000e1 2023-03-10 15:04:39.866 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Temperature range is now LOW (0) 2023-03-10 15:05:17.678 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480f050100030603040000000000000000004900000000000002 2023-03-10 15:05:17.678 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Temperature range is now HIGH (1) 2023-03-10 15:05:28.470 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480f0501000306030000000000000000000048000000000000e5 2023-03-10 15:05:28.471 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Temperature range is now LOW (0) 2023-03-10 15:05:57.881 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480f05000003060308000002000000000000480000001e000084 2023-03-10 15:05:57.881 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Heat mode is now READY (0) 2023-03-10 15:06:41.667 DEBUG (MainThread) [pybalboa.client] 10.110.11.104 -> STATUS_UPDATE: 20ffaf130000480f0601000306030c0000020000000000004900000000000073 2023-03-10 15:06:41.667 DEBUG (MainThread) [pybalboa.control] 10.110.11.104 -- Heat mode is now REST (1)

@natekspencer
Copy link
Contributor

@tonyfitzs this is waiting on a PR before pumps are available in the core integration
#87497

@Manbearpig92
Copy link

Is there a way to prevent the Integration from going unavailable? I was reading it's an issue with the module itself. Is there a better fix or do I just have to keep reconfiguring it everytime she goes down?

@natekspencer
Copy link
Contributor

You shouldn't need to reconfigure. Once the module is communicating again, it should come back online automatically.

@Manbearpig92
Copy link

it was unavailable for 2 days and I just deleted it and added it again but that's good to know that there is a solution

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 22, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jul 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants