Balboa Binding

Hi,

@joedirt The first set of logs indicate a few reconnect cycles close to each other. Does not seem to be stuck in CONFIGRATION_PENDING though (it enters that state after the Panel Configuration request is sent and leaves it at the point it logs “Balboa Protocol is Online”). Also seems it got out of it at the end?

In the second set, it might be the oh framework itself that updates the item state, depending on your item configuration. Refer this [post].(Using autoupdate=false - #2 by rlkoshak)

This message

Indicates that your spa controller is in fact unreachable. Could be WiFi or any other network issue. Could also be that the balboa app has connected if you have it on your phone? At least my unit only allows one concurrent connection.

I cannot tell from this what has gone wrong and how to fix. Maybe raise all the debug levels to TRACE and see if it becomes clearer?

Interesting. I thought these were fixed values but maybe it varies like the pump configuration and must be parsed from the panel configuration. Can you try with the app from balboa? What is the highest and lowest temp you can set in the respective modes?

Thanks!
//Carl

Is there a way to set the time of the control unit?
My Wifi died the other day, and now I think, the Spa got confused and didn’t heat up today morning (which is strange, because I set the Range at 10am to HIGH, and now (5pm) its icecold (28°), which is below the LOW Range…

My only bet is, the wrong time was the issue…!

I configured my “CurrentTemp”-item like this in GUI:

From my understanding there had to be a UNDEF in between these to log entries?

2021-01-14 07:36:16.122 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'BalboaIPUnit_CurrentTemperature' changed from 35.0 °C to 34.5 °C
...
2021-01-14 08:37:22.389 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'BalboaIPUnit_CurrentTemperature' changed from 34.5 °C to 34.0 °C

or is the Temperature updated regularly from the binding with the same value and I only see the “changes” in the logs obviously?

Hi,

The WiFi units supports setting the time, but I have not implemented those messages yet.

The WiFi unit sends updates continuously. Mine emits such messages about once per second. I have set the binding to discard repeated messages. The status updates include hour and minute part of the clock, so there will always be an update every minute even if nothing else changes.

I think the OH framework will only log changes, not updates with the same value. You can raise the log levels of the binding to see the messages and the updates.

Regards
//Carl

1 Like

What I’m experiencing is, that after some time, the Wifi will completely disconnect also from the AP and won’t come online, unless I turn off/on the whole Spa again. If the Wifi is disconnected, I won’t get it online also after leaving it be for an hour or so… After I cold-started the Spa, it works for a few days. Happened to me now thrice since I moved to openHAB3, so I guess perhaps that’s connected somehow?
Is this something anyone else also has seen with his Balboa spa?

@binderth
Mines done that a few times both on oh2 and 3 but a little less frequently on oh3 maybe once every 2 weeks now.

I’m still having the same config pending or whatever the actual wording is error in which I have to pause the thing and resume it to actually get connected again.

I thought it might be phoning home that caused it but I’ve blocked internet access and it’s still happening 1-3 times a day which is really frustrating. A timer that if the config is pending for more than 5 mins it tries again until it gets connected properly would be ideal.

hmmm. I never even installed a cloud account for the Spa-App “bwa Spa Control”, does it still sent information? That’d be… bad!
But you mean, this behaviour could lead to the disconnection of the Spa-wifi from my AccessPoint? It doesn’t show up, can’t be pinged and only a cold start brings it back online. Same with you?

I am a bit confused by the binding/whatever:

I try to set the TargetTemperature to 30°C, but it keeps jumping back to 38°C:
Whenever I set the TargetTemp rule based

  if (TargetTemp > LowTemp) {
    logInfo("Whirlpool.SetTemp.AUTO", "SetTemp: " + LowTemp)
    Whirlpool_TargetTemperature.postUpdate(LowTemp);
  }

I always use the logInfo command together with the postUpdate.
System responds with

2021-02-09 17:09:05.089 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Whirlpool_TargetTemperature' changed from 38.0 °C to 30.0 °C

2021-02-09 17:09:05.324 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Whirlpool_TargetTemperature' changed from 30.0 °C to 38.0 °C

for every single call. I do not know where the second (“30 to 38”) is coming from.
Any idea?

2021-02-09 17:05:05.084 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Whirlpool_TargetTemperature' changed from 38.0 °C to 30.0 °C

2021-02-09 17:05:05.398 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Whirlpool_TargetTemperature' changed from 30.0 °C to 38.0 °C

2021-02-09 17:05:20.046 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - ------------------------------------------------------------------------------

2021-02-09 17:05:20.052 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - Persistent_BALBOA_OPERATIONMODE: AUTO

2021-02-09 17:05:20.054 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - BALBOA_MANUAL:                   OFF

2021-02-09 17:05:20.057 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - Whirlpool_TargetTemperature:     38.0 °C

2021-02-09 17:05:20.059 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - Whirlpool_TemperatureRange:      HIGH

2021-02-09 17:05:20.076 [INFO ] [.model.script.Whirlpool.SetTemp.AUTO] - SetTemp: 30

2021-02-09 17:05:20.079 [INFO ] [.model.script.Whirlpool.SetTemp.AUTO] - SwitchOn: 0

2021-02-09 17:05:20.081 [INFO ] [.model.script.Whirlpool.SetTemp.AUTO] - SwitchOff: 17

2021-02-09 17:05:20.087 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Whirlpool_TargetTemperature' changed from 38.0 °C to 30.0 °C

2021-02-09 17:05:35.046 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - ------------------------------------------------------------------------------

2021-02-09 17:05:35.053 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - Persistent_BALBOA_OPERATIONMODE: AUTO

2021-02-09 17:05:35.056 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - BALBOA_MANUAL:                   OFF

2021-02-09 17:05:35.059 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - Whirlpool_TargetTemperature:     30.0 °C

2021-02-09 17:05:35.061 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - Whirlpool_TemperatureRange:      HIGH

2021-02-09 17:05:35.079 [INFO ] [.model.script.Whirlpool.SetTemp.AUTO] - SwitchOn: 0

2021-02-09 17:05:35.082 [INFO ] [.model.script.Whirlpool.SetTemp.AUTO] - SwitchOff: 18

2021-02-09 17:05:50.046 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - ------------------------------------------------------------------------------

2021-02-09 17:05:50.062 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - Persistent_BALBOA_OPERATIONMODE: AUTO

2021-02-09 17:05:50.065 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - BALBOA_MANUAL:                   OFF

2021-02-09 17:05:50.067 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - Whirlpool_TargetTemperature:     30.0 °C

2021-02-09 17:05:50.070 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - Whirlpool_TemperatureRange:      HIGH

2021-02-09 17:05:50.086 [INFO ] [.model.script.Whirlpool.SetTemp.AUTO] - SwitchOn: 0

2021-02-09 17:05:50.088 [INFO ] [.model.script.Whirlpool.SetTemp.AUTO] - SwitchOff: 19

2021-02-09 17:05:51.282 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Whirlpool_TargetTemperature' changed from 30.0 °C to 38.0 °C

2021-02-09 17:06:05.047 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - ------------------------------------------------------------------------------

2021-02-09 17:06:05.052 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - Persistent_BALBOA_OPERATIONMODE: AUTO

2021-02-09 17:06:05.055 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - BALBOA_MANUAL:                   OFF

2021-02-09 17:06:05.057 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - Whirlpool_TargetTemperature:     38.0 °C

2021-02-09 17:06:05.060 [INFO ] [odel.script.Whirlpool.SetTemp.Before] - Whirlpool_TemperatureRange:      HIGH


2021-02-09 17:06:05.090 [INFO ] [.model.script.Whirlpool.SetTemp.AUTO] - SetTemp: 30

2021-02-09 17:06:05.094 [INFO ] [.model.script.Whirlpool.SetTemp.AUTO] - SwitchOn: 0

2021-02-09 17:06:05.096 [INFO ] [.model.script.Whirlpool.SetTemp.AUTO] - SwitchOff: 20

2021-02-09 17:06:05.099 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Whirlpool_TargetTemperature' changed from 38.0 °C to 30.0 °C

2021-02-09 17:06:05.378 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Whirlpool_TargetTemperature' changed from 30.0 °C to 38.0 °C

@binderth I can get mine back online using the pause button on the thing in the openhab gui.

@carlonnheim im still having the issue of it dropping out 3+ times a day and I know its not my wifi. can we please get an option in the binding that when it drops it pauses it and resumes it every 5 mins until its back online? it would solve my issue.

In my case, it seems to be the wifi, which drops the connection from time to time, and if, sometimes for more than 2 hours.
It would be great to have a channel which holds the last proper response (timestamp) from the device. (setting or getting values).
I had to switch back to the script based version as this one seem more reliable (and tells me when not working).

Hmm… in my case - as with @ThomasBrodkorb - the Wifi drops completely in the Spa-Wifi (isn’t responding, can’t be pinged and doesn’t come up even after a few hours) and I have to shut down and restart the pool again.
Perhaps I’ll set the binding on TRACE for some time and look what happens there…?

I do have a network-thing and use the “online”-mode of it with the IP of the Spa-Wifi to tell me, if that happens - now I need to find an switch capable of remote switching 40A of 230V! :wink:

@binderth with the latest version of the wifi module, the one I have allows multiple concurrent connections and also when it drops wifi it reconnects after a certain amount of time.

The problem is that the binding does not recognise when it comes back online.

ok, then I don’t have the latest version… it only allows one connection at a time.

Interestingly enough, I just have the state, that the binding can’t find the wifi module, but it is live and I can connect locally with the App to it.
setting the binding to TRACE I get:

2021-02-18 14:22:27.246 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from UNINITIALIZED (DISABLED) to INITIALIZING
==> /var/log/openhab/openhab.log <==
2021-02-18 14:22:27.260 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.xx.yy at 4257
==> /var/log/openhab/events.log <==
2021-02-18 14:22:27.261 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from INITIALIZING to UNKNOWN
==> /var/log/openhab/openhab.log <==
2021-02-18 14:22:27.267 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
... 
nothing
...
2021-02-18 14:23:43.015 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from UNKNOWN to UNINITIALIZED
==> /var/log/openhab/openhab.log <==
2021-02-18 14:23:43.038 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol disconnecting
2021-02-18 14:23:43.042 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Connection Failed: null
2021-02-18 14:23:43.046 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol disconnected
2021-02-18 14:23:43.047 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Error: Connection Failed: null
==> /var/log/openhab/events.log <==
2021-02-18 14:23:43.065 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from UNINITIALIZED to OFFLINE (CONFIGURATION_ERROR): Connection Failed: null
2021-02-18 14:23:43.070 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from OFFLINE (CONFIGURATION_ERROR): Connection Failed: null to UNINITIALIZED (DISABLED)

turning the whole Spa off and on again => it works.

My status is usually “No route to host”, when the connection fails.
Then I cannot ping it either, so I guess it is really a Wifi issue which occurs from time to time.

just out of curiosity! :wink: Do you use a FritzBox? I have a Fritz-Mesh - don’t know, if this is important, which AP you’re using - should be of no concern for the device in theory…

I am running my wireless network on ubiquiti unifi APs.

The problem here is more that the Balboa WIFI is under ground level and hard to reach anyway :slight_smile:.

Hi,

I will look into setting up timeouts as proposed above. Need to get my installation up to OH3 first though, sorry for delaying.

Regards
//Carl

2 Likes

This is really good, thanks for all the great work Carl! I´m gonna get my wifi unit connected again, it´s disconnected since yesterday due to a new AP, and see if I can´t get this up and running in my OH3. Also, let me know if there is anything you need me to test etc!

Amazing rules, I wish I had the time to do automation like that… :slight_smile:

1 Like