Incorrect Thermostat Mode displayed in HA

[JaggedJax]

Version of the custom_component

1.6.2

Bestway device

Saluspa Coronado
https://bestwayusa.com/saluspa-coronado-energysense-smart-airjet-inflatable-hot-tub-spa-4-6-person-60068e

Describe the bug

Often, but not always, the thermostat in HA shows the wrong mode. It will show off even though the device is actually heating. Here is a screenshot showing the temperature rising, and the HA device detected the correct mode (Heating) for a little bit (shared orange/red) but then it toggled back to Off even though you can see the temperature continue to rise because the heater is actually on.

The timing that the Heat stopped showing correctly is the same time as an unavailable/off log is shown. The device was never turned off, but sometimes I notice Bestway API calls must fail and the unit briefly shows unavailable. However future calls/updates were definitely successful as you can see the temperate continue to raise, but the Heat setting never gets corrected when it becomes available again.

The Bestway app does show the correct Heat status at all times, but I only ever control the device through HA and only open the Bestway app if there's a discrepancy to review like this.

Logs

I don't see any under HA Settings > Logs that refer to Bestway. Unless there's another way to access logs for this integration?

[cdpuk]

Try going through Devices & services > Bestway > Enable debug logging. Logs will definitely be required to understand what's happening on the network and how this maps to what's being displayed in HA.

[JaggedJax]

Series of events, logs below:

1. Device heating to set temperature: Heater On
2. Device hits target temperature: Heater Off
3. Target temperature raised: Heater On, but shows Off in HA

Screenshot of this in HA with problem area highlighted:

Step 1. HA device showing correct Heater status: Heater On

2025-01-19 11:30:58.658 DEBUG (MainThread) [custom_components.bestway.bestway.api] Status for device type 'Airjet_V01' returned: {"E19": 0, "E18": 0, "E32": 0, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 150, "word4": 0, "word7": 34, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 150, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 93, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 1, "heat": 3, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 94, "filter": 2, "E28": 0, "bit6": 1, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

Step 2. HA device showing correct Heater status after reaching temperature: Heater Off

2025-01-19 11:50:05.782 DEBUG (MainThread) [custom_components.bestway.bestway.api] Status for device type 'Airjet_V01' returned: {"E19": 0, "E18": 0, "E32": 1, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 170, "word4": 0, "word7": 35, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 170, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 95, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 1, "heat": 4, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 94, "filter": 2, "E28": 0, "bit6": 1, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

Step 3. HA device showing incorrect Heater status after target temperature is raised: Shows Heater Off (but should show Heater On)

2025-01-19 12:15:21.582 DEBUG (MainThread) [custom_components.bestway.bestway.api] Status for device type 'Airjet_V01' returned: {"E19": 0, "E18": 0, "E32": 1, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 195, "word4": 0, "word7": 35, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 195, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 95, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 1, "heat": 6, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 104, "filter": 2, "E28": 0, "bit6": 1, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

The changes I see are:

• heat: 3 => 4 => 6
• word2: 150 => 170 => 195
• word5: 150 => 170 => 195
• word7: 34 => 35 => 35
• E32: 0 => 1 => 1

[TheOneOgre]

Also having this issue with a Saluspa Madrid. Been an ongoing issue for months and breaks automations for me.

Shows model Airjet V01

[cdpuk]

For the sake of clarity, and mapping this on to what happens in the code, there are two things we need to feed in to HA:

• The HVACMode, which is HEAT or OFF
• The HVACAction, which is HEATING or IDLE - this is only relevant when in HEAT mode and indicates whether we're at the target temperature.

The current best guess used to display data works like this:

• heat == 0 sets HVACMode to HEAT
• heat == 3 sets HVACMode to OFF
• word3 == 0 sets HVACAction to HEATING (but only when HVACMode == HEAT)
• word3 == 1 sets HVACAction to IDLE

Clearly the heat values of 4 and 6 need to be accounted for in some way. It's possible that it needs to be interpreted as a bitfield:

3 = 011
4 = 100
6 = 110

So maybe that middle value of 1 means heater on (temp not reached), but the values either side don't clearly map to anything. The use of word3 to determine this state is clearly wrong for your spa, so perhaps the bitfield approach would work better.

It would be interesting to see log line changes when simply turning spa heating on/off via the app. Doing once when below the target temp and once when at the target temp would also provide useful data. We need to find the right way to determine whether heating is enabled.

[tylerbean]

I experience this on my Saluspa as well. The heating state shown in HA is almost always incorrect. Turning the heater off and on again in HA does cause it to actually begin heating, but the state flips back to OFF in HA within a minute's time.

[JaggedJax]

@cdpuk Ran a bunch of tests as you suggested, turning Heat Mode on/off from the app at different temperatures. This Spa keeps heating when at the desired temp and stops when it passes it, so I included one at the desired temp and one over the desired temp.

Then I re-ran the original scenario one more time.

Under Desired Temp

Heat Mode On (2 results within 1 minute):
{"E19": 0, "E18": 0, "E32": 0, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 0, "word4": 0, "word7": 35, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 61, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 95, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 0, "heat": 2, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 104, "filter": 2, "E28": 0, "bit6": 0, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

{"E19": 0, "E18": 0, "E32": 0, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 2, "word4": 0, "word7": 35, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 63, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 95, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 0, "heat": 3, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 104, "filter": 2, "E28": 0, "bit6": 0, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

Heat changes to 2 briefly and then settles on 3.

Heat Mode Off:
{"E19": 0, "E18": 0, "E32": 0, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 0, "word4": 0, "word7": 35, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 60, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 95, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 0, "heat": 0, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 104, "filter": 2, "E28": 0, "bit6": 0, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

At Desired Temp

Spa continues to heat water while at desired temp and does not stop until measured temp goes over desired temp.

Heat Mode On:
{"E19": 0, "E18": 0, "E32": 1, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 1, "word4": 0, "word7": 35, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 54, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 95, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 0, "heat": 4, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 95, "filter": 2, "E28": 0, "bit6": 0, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

Heat Mode Off:
{"E19": 0, "E18": 0, "E32": 0, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 0, "word4": 0, "word7": 35, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 58, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 95, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 0, "heat": 0, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 95, "filter": 2, "E28": 0, "bit6": 0, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

Over Desired Temp

Heat Mode On:
{"E19": 0, "E18": 0, "E32": 1, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 6, "word4": 0, "word7": 35, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 51, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 95, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 0, "heat": 4, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 94, "filter": 2, "E28": 0, "bit6": 0, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

Heat Mode Off:
{"E19": 0, "E18": 0, "E32": 0, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 0, "word4": 0, "word7": 35, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 52, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 95, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 0, "heat": 0, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 94, "filter": 2, "E28": 0, "bit6": 0, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

Original Scenario Re-Test

After the above tests I re-ran the original scenario as well. Heat On, Temp set to 95, Actual temp 95. Spa keeps heating until it hits 97 then turns off the heating element. I then went in and bumped up the temp to 104 leaving the Heating Mode on.

Heating while at Set Temp and Actual Temp both 95:
{"E19": 0, "E18": 0, "E32": 0, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 21, "word4": 0, "word7": 36, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 82, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 95, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 0, "heat": 3, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 95, "filter": 2, "E28": 0, "bit6": 0, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

Actual temp reaches 97. Heat Mode On, Heater stops:
{"E19": 0, "E18": 0, "E32": 1, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 37, "word4": 0, "word7": 36, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 98, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 97, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 0, "heat": 4, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 95, "filter": 2, "E28": 0, "bit6": 0, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

Increase set temp to 104 (Heat Mode On & Heater On) - 2 results within 1 minute:
{"E19": 0, "E18": 0, "E32": 1, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 38, "word4": 0, "word7": 36, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 99, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 97, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 0, "heat": 5, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 104, "filter": 2, "E28": 0, "bit6": 0, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

{"E19": 0, "E18": 0, "E32": 1, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 41, "word4": 0, "word7": 36, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 102, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 97, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 0, "heat": 6, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 104, "filter": 2, "E28": 0, "bit6": 0, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

Heat changes to 5 briefly and then settles on 6.

Set Temp 104, Heat Mode Off:
{"E19": 0, "E18": 0, "E32": 0, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 0, "word4": 0, "word7": 36, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 110, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 97, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 0, "heat": 0, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 104, "filter": 2, "E28": 0, "bit6": 0, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

Set Temp 104, Heat Mode On Again:
{"E19": 0, "E18": 0, "E32": 0, "E31": 0, "E30": 0, "E11": 0, "E10": 0, "E13": 0, "E12": 0, "E15": 0, "E14": 0, "E17": 0, "E16": 0, "word5": 3, "word4": 0, "word7": 36, "word6": 0, "word1": 0, "word0": 0, "E29": 0, "word2": 113, "option6": 10244, "ver": 1174, "E22": 0, "jet": 0, "E23": 0, "power": 1, "Tnow": 97, "option7": 10260, "option4": 0, "option5": 27187, "option2": 0, "option3": 30, "option0": 59940, "option1": 59940, "E24": 0, "E25": 0, "E26": 0, "E27": 0, "E20": 0, "E21": 0, "E08": 0, "E09": 0, "E06": 0, "E07": 0, "E04": 0, "E05": 0, "E02": 0, "E03": 0, "E01": 0, "bit7": 0, "heat": 3, "Tunit": 0, "wave": 0, "word3": 0, "Tset": 104, "filter": 2, "E28": 0, "bit6": 0, "bit5": 0, "bit4": 0, "bit3": 0, "bit2": 1}

After turning Heat Off and then back on, heat resets to 3 as we expect.

Some Learnings

• Heat doesn't seem to act quite like a bitmap
• When Heat first starts it's often 1 less for a few moments. See the examples where it goes from 2 to 3 and then later 5 to 6. This may be a flag indicating heating requested vs the heater physically enabling
• When at-temp (and still heating) sometimes we see heat 3 and sometimes heat 4. Strange.
• My best guesses:
  • Heat 0: Clearly Off
  • Heat 2: Heat Mode On, Heater not yet started
  • Heat 3: Clearly On
  • Heat 4: Heat Mode On - May or may not be heating. Not clear how to tell (Only word5 & word2 differ, word5 does seem to have a connection to Heater status)
    • Maybe 4 can be considered heater off as in "reached temperature." Yes maybe sometimes it continues heating a little to ensure it doesn't undershoot
    • The app doesn't actually display heating element info so it might not matter to it. Maybe if I watched the spa lights I could tell.
  • Heat 5: Heat Mode On, Heater not yet started, Previously reached desired temp
  • Heat 6: Heater On, Previously reached desired temp

[cdpuk]

Thanks for running those tests. This seems far messier than I ever imagined. Perhaps the answer here is to simply remove the heating status from the climate entity on affected models. It doesn't feel like this can be coded up in an accurate way.

[Marty-McFly73]

I am experiencing the same thing. The heat is on but HA reports it as off. Saluspa Hydrojet Pro.

[DavyBer]

Hello,
I am experiencing the same effect with Santorini Hydrojet Pro.
After updating HA, the Heat indicates that it is in ‘off’ mode, while the status on the Hydrojet Jet or APP is in ‘heat’ mode.

[Zal3D]

Hello, I have the same problem on my Bestway hydrojet Dominica, when I turn on the heater, HA displays the heating mode but after a minute displays off while the heater is still physically on on the spa. When the spa is at the set temperature it never displays idle.

[TailGunR]

I have been looking into this today. I have a Power meter connected to my Airjet V01.

Heat mode numbers

Looking at the power use, and from reading the manual, the heating element has different power levels that it can run at. If you have the bubble jets running and the heating element turned on, it cannot run at full power otherwise it will draw more than 2000W. So I have found that a power draw of between 1800W and 2000W indicates that the unit is heating without the jets on. When the Jets are on MEDIUM and the Heating is turned on, the power draw is approximately 1400W. With the Jets at HIGH and the heating element on the power draw is approximately 1700W.

This is what I have seen with relation to the numbers in the heat attribute:
heat = 0: Heat mode is turned off
heat = 2: Heating element is running at reduced power. Either starting up or bubble jets are on.
heat = 3: Heating element is running at full power.
heat = 4: Heating element is idle.
heat = 5: Same as heat = 2 but after target temperature has been reached at least once (E32 = 1).
heat = 6: Same as heat = 3 but after target temperature has been reached at least once (E32 = 1).

I assume there is a heat = 1 that is similar to heat = 4 but I have not been able to get it to occur. It feels like Bestway has a bug in their code where the E32 Boolean does not get reset after the temperature drops back below the target temperature. This seems to affect the heat status numbers; perhaps the code is heat += 2 when the temp drops below target temperature?

If you turn the heat mode on with the temp above the target temperature the heat attribute jumps straight to heat = 4.

Attribute word5 and word2

It looks like word5 and word2 are used for the scheduling part of the app. word5 appears to count the number of minutes the spa has been set on heat mode. and word2 appears to count the number of minutes that the filter has been turned on. The numbers reset to 0 as soon as you turn off either heat or filter.

Proposed code changes

I have changed my local copy of the code in the following ways:

climate.py hvac_mode
Original:
@property
def hvac_mode(self) -> HVACMode | None:
"""Return the current mode (HEAT or OFF)."""
if not self.status:
return None
return HVACMode.HEAT if self.status.attrs["heat"] == 3 else HVACMode.OFF

Modified:
@property
def hvac_mode(self) -> HVACMode | None:
"""Return the current mode (HEAT or OFF)."""
if not self.status:
return None
return HVACMode.HEAT if self.status.attrs["heat"] > 0 else HVACMode.OFF

climate.py hvac_action
Original:
@property
def hvac_action(self) -> HVACAction | None:
"""Return the current running action (HEATING or IDLE)."""
if not self.status:
return None
heat_on = self.status.attrs["heat"] == HydrojetHeat.ON
target_reached = self.status.attrs["word3"] == 1
return (
HVACAction.HEATING if (heat_on and not target_reached) else HVACAction.IDLE
)

Modified:
@property
def hvac_action(self) -> HVACAction | None:
"""Return the current running action (HEATING or IDLE)."""
if not self.status:
return None
heat_on = self.status.attrs["heat"] > 0
target_reached = self.status.attrs["heat"] == 4
return (
HVACAction.HEATING if (heat_on and not target_reached) else HVACAction.IDLE
)

[Marty-McFly73]

Thank you very much for this! It looks very promising. I have modified my files the same way. Fingers crossed this fixes the issue. Thanks again.

[TailGunR]

The API should not be able to change how the light on the pump box operates. The code for this custom component basically pretends to be the phone app.

I do remember that my heat button has at least two colour options for the backlight. But I am not sure what situations caused each colour.

With that being said, if you are sure the light behaviour has changed, you could try resetting your system and starting it from fresh to see if it goes back to normal.