Balboa Binding

Add-ons Bindings
41

hey guys since updating to 2.5.10 the binding has stopped working. is there anyway to fix this?
ive tried deleting and reinstalling the .jar with no luck.

42

Iā€™m running 2.5.10-1 with the binding smoothly.
did you take a look at it in the console and is it running?
if you did upgrade lately, you have to reinstall and restart all manually installed bindings

43

weird, that was it! thanks!

44

Was there any openhab 3 version of this available?

45

@carlonnheim I created beta release for openhab3. I just pulled your code over into my fork and complied it for openHAB 3. It worked right away. Thanks for the hard work and let me know if you need help with any features.

46

Thanks Dave! I do have a problem, though. The JAR must be put in /srv/openhab-addons/, right? I canā€™t put something in there, because if I try to put a file in there or change permissions:

chmod: changing permissions of '/srv/openhab-addons/': Read-only file system

Do you know how to change this?

47

@binderth I use openhab in docker and I put it in the /openhab/addons folder.
/openhab/addons/org.openhab.binding.balboa-3.1.0-SNAPSHOT.jar

sorry not much helpā€¦

1 Like
48

@ddempsey3 thanks!! thatā€™s awesome.

@binderth I had the same issue upgrading to OH3 I had to do a clean install to be able to paste add ons into the folder.

49

hmmā€¦ I did do a clean install of OH3, because I want to have a clean start into OH3ā€¦ :wink:
I have to have a deeper look, then.

50

Thanks @ddempsey3, much appreciated!

51

@carlonnheim I have an issue where once or twice a day the status changes from online to online config pending. it then continues to get the updates of the spa but wonā€™t send any commands. the only way to fix it is to disable and reenable the thing. is there a way to have the binding automatically disconnect and reconnect the thing if the status changes to online config pending or have a custom setting in the ting of a timer to automatically disconnect and reconnect the thing at a custom value of 5mins?

In my case I have 2 use cases for the binding. The primary use case for the binding is to turn the heat Setpoint up when the solar pv is generating enough to heat the spa with our own own generated energy and back down when a cloud comes over the panels and the sun sets. The 2nd use case is to trigger a scene when the spa lights change state twice within a 10 second window.

in its current state the binding has failed to fire the rules and also turn the temp down on the spa which has used quite a lot of extra power and failed to fire the rule that causes the different scenes to activate meaning I have to get out of the spa and grab my phone to disable and re-enable the thing. third world problems I know.

I donā€™t think its a wifi problem causing it to loose connectivity either because there is a unifi AP 4m from the spa with no obstructions that I installed thinking it might be a wifi issue. the wifi module is at the closest corner to the unifi which is coincidentally at the furtherest corner from the spa pumps and electronics. my phone also has full bars of wifi and is able to achieve 200+mbps on a speedtest while beside the spa. I also donā€™t use the Balboa app so that shouldnā€™t be kicking the binding off the module.

I cant find anything in the logs in regards to the state changes with the thing. if there is anything that I can do to help trouble shoot id like to so I can help get this sorted.

ps sorry for the novel.

52

@carlonnheim thatā€™s for all the hard work on this. Iā€™ve got my tub now set up in OH3 with @ddempsey3 jar. Before I was using the script but the binding is great.

Just a query for anyone using it. How are you defining you spa in the new semantic model?

53

I have the following locations:

- home (location)
-- outside (location)
--- garden (location)
---- whirlpool (location)
----- Balboa IP Unit (equipment)
------ all the items as Points from the binding.
1 Like
54

I seem to totally misunderstand the concept of the Balboa Unit, or itā€™s just messed up in my head! :wink:
The Balboa documentation is a mess in my eyes and far to clustered to be of useā€¦

My Use Case is very simple (and seemingly similar to yours):

  • put the Spa to sleep at night (lower target temperature at night)
  • wake the Spa in the morning (higher target temperature at daytime)

So, what I did until now is send the ā€œTemperature Range: LOWā€ at night and ā€œTemperature Range: HIGHā€ at day, but that doesnā€™t seem to do the trick? So, what are you doing? setting the ā€œTargetTemperatureā€ to a lower number?

55

@binderth hereā€™s my 3 rules
the first one is triggered every time the solar pv being generated change and also how much load the house is drawing changes. if there is more than 3kw of power being sent from the house to the grid it turns the hot water cylinder on and if there is more than 5kw of power being generated then it turns the spa temp up to 40c. when the house is pulling more than 1kw from the grid it turns the hot water cylinder off and lowers the temp of the spa to 30c

rule "Auto Solar Power Usage"

when
	Item Inverter_Generation_Combined changed or
	Item Inverter_1_Grid changed
	then
	createTimer(now.plusSeconds(2), [ |
		if		(Inverter_1_Grid.state < -3000 && Hot_water_Element_2.state !== OFF)

				{
					Hot_water_Element_2.sendCommand(OFF)
					Hot_water_Element_1.sendCommand(OFF)
				}
		if		(Inverter_1_Grid.state < -5000 && Spa_Target_Temp.state !== "40")
				{
				Spa_Target_Temp.sendCommand(40)
				}
		if		(Inverter_1_Grid.state > 1000)
				{
				Hot_water_Element_2.sendCommand(ON)
				Hot_water_Element_1.sendCommand(ON)
				}
		if		(Inverter_1_Grid.state > 1000 && Force_Spa_Heat.state !== ON && Spa_Target_Temp.state !== "33")
				{
				Spa_Target_Temp.sendCommand(30.0)
				}
    ])   
end

my next rule openhab monitors the in built spa lights and when they are switched on the spa controller touchscreen twice in 10 seconds it turns all the lights off inside the house, sets the backyard lights brightness and colour and turns the outdoor speakers to Spotify and sets the volume

rule "Spa Lights turn on and off 3 times within 10 seconds then turn all house lights Off"

when
	Item Spa_Lights changed
then
        SpaLightsCounter = SpaLightsCounter +1
	Thread::sleep(100)
	if	( SpaLightsCounter == 2 ) {
		 GHouseLights.sendCommand(OFF)
		}
	if	( SpaLightsCounter == 2 ) {
		 HueBackYardSpotColour.sendCommand("0,100,100")
		 GSpaLights.sendCommand("0,100,30")
		 HueBackYardBollardColour.sendCommand("287,100,100")
		MusicCast_Power.sendCommand(ON)
		MusicCast_Backyard_Power.sendCommand(ON)
		Thread::sleep(300)
		MusicCast_Input.sendCommand("spotify")
		sendCommand(MusicCast_Backyard_Server, "192.168.178.149***main")
		Thread::sleep(300)
		MusicCast_Player.sendCommand("PLAY")
		Thread::sleep(300)
		sendCommand(MusicCast_Backyard_Volume, 40)
		sendCommand(MusicCast_Volume, 0)
		MusicCast_Player.sendCommand("PLAY")
		}
		createTimer(now.plusSeconds(10), [|	        
	        SpaLightsCounter = SpaLightsCounter -1
        		])

and my last rule, if there is music playing outside and one of the 3 jet pumps turn on the music volume will be increased so that the apparent volume is the same and when all of the jet pumps have been turned off it will reduce the volume again.

rule "Spa Volume while pumps are on and off"
when
	Item Spa_Pump_1 changed or
	Item Spa_Pump_2 changed or
	Item Spa_Pump_3 changed
then
		Thread::sleep(100)
if		(Spa_Pump_1.state == OFF && Spa_Pump_2.state == OFF && Spa_Pump_3.state == OFF && MusicCast_Backyard_Power.state == ON && SpaVolumeCounter == 1)
		{
			logInfo("Spa Volume while pumps are on and off", "Pumps turned off so lowering the volume")
        	VSpaVolume = MusicCast_Backyard_Volume_ABS.state as Number - 15
		    SpaVolumeCounter = 0
			sendCommand(MusicCast_Backyard_Volume_ABS, VSpaVolume)
		}
if		(Spa_Pump_1.state == ON && Spa_Pump_2.state == OFF && Spa_Pump_3.state == OFF && MusicCast_Backyard_Power.state == ON && SpaVolumeCounter == 0)
		{
			logInfo("Spa Volume while pumps are on and off", "Pump/s turned on so increasing the volume")
        	VSpaVolume = MusicCast_Backyard_Volume_ABS.state as Number + 15
		    SpaVolumeCounter = 1
			sendCommand(MusicCast_Backyard_Volume_ABS, VSpaVolume)
		}
if		(Spa_Pump_1.state == OFF && Spa_Pump_2.state == ON && Spa_Pump_3.state == OFF && MusicCast_Backyard_Power.state == ON && SpaVolumeCounter == 0)
		{
			logInfo("Spa Volume while pumps are on and off", "Pump/s turned on so increasing the volume")
        	VSpaVolume = MusicCast_Backyard_Volume_ABS.state as Number + 15
		    SpaVolumeCounter = 1
			sendCommand(MusicCast_Backyard_Volume_ABS, VSpaVolume)
		}
if		(Spa_Pump_1.state == OFF && Spa_Pump_2.state == OFF && Spa_Pump_3.state == ON && MusicCast_Backyard_Power.state == ON && SpaVolumeCounter == 0)
		{
			logInfo("Spa Volume while pumps are on and off", "Pump/s turned on so increasing the volume")
        	VSpaVolume = MusicCast_Backyard_Volume_ABS.state as Number + 15
		    SpaVolumeCounter = 1
			sendCommand(MusicCast_Backyard_Volume_ABS, VSpaVolume)
		}
end

so my issue where the Balboa thing keeps loosing a connection/freazing is a right pain because then the rules stop working.

56

My understanding with the Temp Range setting is that it allows you to have the winter temp range (high) and a summer temp range(low) On my spa the available temp range in the high temp range is 30c-40c and in the low temp range it has a range from 15c-30c so like a cold dip pool in summer or for people who donā€™t use their spas in summer to use allow less power.

57

Hi,

Ok. Sounds like binding first loses the connection (could be other reasons than the wifi), tries to reconnect but the configuration response message from the unit is getting corrupted or for some other reason lost in the reconnection attempt. The binding needs this message to determine how many pumps are present etc. Can you turn on debugging in order to confirm that this is the case? Issue these in the openhab console and share the output next time the issue happens. Set them back to INFO when done.

log:set TRACE org.openhab.binding.balboa.internal.BalboaMessage
log:set DEBUG org.openhab.binding.balboa.internal.BalboaProtocol
log:set DEBUG org.openhab.binding.balboa.internal.BalboaHandler

If you want a quick fix until I can make something proper, I would suggest a cron job to check the status of the thing using the REST API /things/{thingUID}/status and then (if it is stuck) put a ā€œfalseā€ and then a ā€œtrueā€ to /things/{thingUID}/enable. Something like this (you need to change the thing UID to match your setup).

curl -s -X GET "http://localhost:8080/rest/things/balboa%3Abalboa-ip%3Ahottub/status" | grep -q "ONLINE" || (curl -s -X PUT --header "Content-Type: application/json" -d "false" "http://localhost:8080/rest/things/balboa%3Abalboa-ip%3Ahottub/enable"; curl -s -X PUT --header "Content-Type: application/json" -d "true" "http://localhost:8080/rest/things/balboa%3Abalboa-ip%3Ahottub/enable") > /dev/null

My experience with the Temperature Range is is that you simply need to set it to low or high depending on which target temperature you want to set (ranges are not overlapping). If you set it to low you can have 10-26 degrees (centigrade) and if you set it to high you can have 26.5 up to 40 degrees. The spa (mine at least) remembers the setpoint you had in each range, so you can use it to switch between the two. There is also the Heat Mode which affects the heating patterns (but for the solar powered heating scenario I would also go with altering the setpoint).

Inspiring work on the rules - thanks for sharing!

Regards
//Carl

58

Itā€™s just stopped working hereā€™s the logs.

Iā€™m not familiar with cron jobs so might just leave that one as after a little googling it appears quite complicated :joy:

2021-01-04 13:46:28.678 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 13:46
2021-01-04 13:46:33.637 [DEBUG] [inding.balboa.internal.BalboaHandler] - Polling stopped
2021-01-04 13:46:33.640 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol disconnecting
2021-01-04 13:46:33.644 [INFO ] [inding.balboa.internal.BalboaHandler] - Balboa Protocol went Offline
2021-01-04 13:46:33.648 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Not connected when disconnect attempted.
2021-01-04 13:46:33.653 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol disconnected
2021-01-04 13:46:33.654 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-04 13:46:33.658 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-04 13:46:33.855 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Pending Ponfiguration: Configuration request sent
2021-01-04 13:46:33.916 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E1A0ABF2464E12B004D425032315558200308FAD2BE030A03004D7E
2021-01-04 13:46:33.918 [TRACE] [inding.balboa.internal.BalboaMessage] - Information Response received
2021-01-04 13:46:33.959 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E0B0ABF2E150001900040FB7E
2021-01-04 13:46:33.960 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte5..6 10101 0: Pumps [1, 1, 1, 0, 0, 0]
2021-01-04 13:46:33.962 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte7 1: Lights [1, 0]
2021-01-04 13:46:33.964 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte8 10010000: circulation 2, blower 0
2021-01-04 13:46:33.965 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte9 0: AUX [false, false], mister 0
2021-01-04 13:46:34.265 [INFO ] [inding.balboa.internal.BalboaHandler] - Balboa Protocol is Online
2021-01-04 13:46:34.271 [DEBUG] [inding.balboa.internal.BalboaHandler] - Polling started with 30 seconds interval
2021-01-04 13:46:34.273 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF131403510D2E000A5151070C000002000000000124500100001E00002B7E
2021-01-04 13:46:34.274 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 13:46
2021-01-04 13:46:40.441 [DEBUG] [inding.balboa.internal.BalboaHandler] - Polling stopped
2021-01-04 13:46:40.447 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol disconnecting
2021-01-04 13:46:40.449 [INFO ] [inding.balboa.internal.BalboaHandler] - Balboa Protocol went Offline
2021-01-04 13:46:40.454 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Not connected when disconnect attempted.
2021-01-04 13:46:40.454 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-04 13:46:40.458 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-04 13:46:40.460 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol disconnected
2021-01-04 13:46:40.462 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-04 13:46:40.662 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Pending Ponfiguration: Configuration request sent
2021-01-04 13:46:40.679 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF131403510D2E000A5151070C000002000000000124500100001E00002B7E
2021-01-04 13:46:40.681 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 13:46
2021-01-04 13:46:40.721 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E1A0ABF2464E12B004D425032315558200308FAD2BE030A03004D7E
2021-01-04 13:46:40.723 [TRACE] [inding.balboa.internal.BalboaMessage] - Information Response received
2021-01-04 13:46:40.759 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E0B0ABF2E150001900040FB7E
2021-01-04 13:46:40.761 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte5..6 10101 0: Pumps [1, 1, 1, 0, 0, 0]
2021-01-04 13:46:40.763 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte7 1: Lights [1, 0]
2021-01-04 13:46:40.764 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte8 10010000: circulation 2, blower 0
2021-01-04 13:46:40.765 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte9 0: AUX [false, false], mister 0
2021-01-04 13:46:41.047 [INFO ] [inding.balboa.internal.BalboaHandler] - Balboa Protocol is Online
2021-01-04 13:46:41.050 [DEBUG] [inding.balboa.internal.BalboaHandler] - Polling started with 30 seconds interval
2021-01-04 13:46:41.052 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF131403510D2E000A5151070C000002000000000124500100001E00002B7E
2021-01-04 13:46:41.054 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 13:46
2021-01-04 13:46:46.000 [DEBUG] [inding.balboa.internal.BalboaHandler] - Polling stopped
2021-01-04 13:46:46.002 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol disconnecting
2021-01-04 13:46:46.006 [INFO ] [inding.balboa.internal.BalboaHandler] - Balboa Protocol went Offline
2021-01-04 13:46:46.009 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Not connected when disconnect attempted.
2021-01-04 13:46:46.011 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol disconnected
2021-01-04 13:46:46.014 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-04 13:46:46.017 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-04 13:46:46.220 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Pending Ponfiguration: Configuration request sent
2021-01-04 13:46:46.260 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E1A0ABF2464E12B004D425032315558200308FAD2BE030A03004D7E
2021-01-04 13:46:46.261 [TRACE] [inding.balboa.internal.BalboaMessage] - Information Response received
2021-01-04 13:46:46.303 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E0B0ABF2E150001900040FB7E
2021-01-04 13:46:46.305 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte5..6 10101 0: Pumps [1, 1, 1, 0, 0, 0]
2021-01-04 13:46:46.306 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte7 1: Lights [1, 0]
2021-01-04 13:46:46.308 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte8 10010000: circulation 2, blower 0
2021-01-04 13:46:46.309 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte9 0: AUX [false, false], mister 0
2021-01-04 13:46:46.595 [INFO ] [inding.balboa.internal.BalboaHandler] - Balboa Protocol is Online
2021-01-04 13:46:46.597 [DEBUG] [inding.balboa.internal.BalboaHandler] - Polling started with 30 seconds interval
2021-01-04 13:46:46.602 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF131403510D2E000A5151070C000002000000000124500100001E00002B7E
2021-01-04 13:46:46.604 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 13:46
2021-01-04 13:46:50.334 [DEBUG] [inding.balboa.internal.BalboaHandler] - Polling stopped
2021-01-04 13:46:50.336 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol disconnecting
2021-01-04 13:46:50.339 [INFO ] [inding.balboa.internal.BalboaHandler] - Balboa Protocol went Offline
2021-01-04 13:46:50.342 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Not connected when disconnect attempted.
2021-01-04 13:46:50.344 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol disconnected
2021-01-04 13:46:50.346 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-04 13:46:50.349 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-04 13:46:50.550 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Pending Ponfiguration: Configuration request sent
2021-01-04 13:46:50.603 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E1A0ABF2464E12B004D425032315558200308FAD2BE030A03004D7E
2021-01-04 13:46:50.605 [TRACE] [inding.balboa.internal.BalboaMessage] - Information Response received
2021-01-04 13:46:50.648 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E0B0ABF2E150001900040FB7E
2021-01-04 13:46:50.649 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte5..6 10101 0: Pumps [1, 1, 1, 0, 0, 0]
2021-01-04 13:46:50.650 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte7 1: Lights [1, 0]
2021-01-04 13:46:50.652 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte8 10010000: circulation 2, blower 0
2021-01-04 13:46:50.653 [DEBUG] [inding.balboa.internal.BalboaMessage] - Panel Configuration: byte9 0: AUX [false, false], mister 0
2021-01-04 13:46:50.980 [INFO ] [inding.balboa.internal.BalboaHandler] - Balboa Protocol is Online
2021-01-04 13:46:50.991 [DEBUG] [inding.balboa.internal.BalboaHandler] - Polling started with 30 seconds interval
2021-01-04 13:46:50.993 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF131403510D2E000A5151070C000002000000000124500100001E00002B7E
2021-01-04 13:46:50.995 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 13:46
2021-01-04 13:46:54.152 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF131403500D2E000A5051070C000002000000000124500100001E0000F57E
2021-01-04 13:46:54.154 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 13:46
2021-01-04 13:46:54.157 [TRACE] [inding.balboa.internal.BalboaMessage] - Changes on unknown bits: 00000000001402000000000A50510008000000000000000124000100001E00000000
2021-01-04 13:46:54.447 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF131403500D2E000A5151070C000002000000000124500100001E0000D97E
2021-01-04 13:46:54.449 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 13:46
2021-01-04 13:46:54.452 [TRACE] [inding.balboa.internal.BalboaMessage] - Changes on unknown bits: 00000000001402000000000A51510008000000000000000124000100001E00000000
2021-01-04 13:46:54.752 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF131403510D2E000A5151070C000002000000000124500100001E00002B7E
2021-01-04 13:46:54.754 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 13:46
59

Thatā€™s strange, my Balboa unit has a much different range, so I couldset the low range all the way up to 40Ā°C and the high range all the way down to 16Ā°C (I think); what the Unit doesnā€™t allow is overlapping, so that I set low higher than high.
But I donā€™t see a drop in temperatures over night, if I change to lowā€¦? But I must investigate this further!

What channel are these Items connected to? I donā€™t seem to have direct access to the Heatingā€¦?

60

@binderth Sorry for the confusion, the water elements are for my hot water heater not the spa.

@carlonnheim I just left the binding after it said config pending. it looks like it has recovered from the UI but any commands that are sent to run any of the pumps or change the temp are not working.

In the example below I turned the jet pump one on and then off but nothing happened in the spa.
the events log looks like they are sending the commands?

2021-01-05 04:04:39.559 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Spa_Pump_1' received command ON
2021-01-05 04:04:39.564 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Spa_Pump_1' predicted to become ON
2021-01-05 04:04:39.568 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Spa_Pump_1' changed from OFF to ON
2021-01-05 04:04:46.496 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Spa_Pump_1' received command OFF
2021-01-05 04:04:46.503 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Spa_Pump_1' predicted to become OFF
2021-01-05 04:04:46.508 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Spa_Pump_1' changed from ON to OFF
2021-01-05 04:05:51.351 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Spa_Pump_1' received command ON
2021-01-05 04:05:51.356 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Spa_Pump_1' predicted to become ON
2021-01-05 04:05:51.362 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Spa_Pump_1' changed from OFF to ON
2021-01-05 04:06:10.197 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Spa_Pump_1' received command OFF
2021-01-05 04:06:10.203 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Spa_Pump_1' predicted to become OFF
2021-01-05 04:06:10.210 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Spa_Pump_1' changed from ON to OFF

2021-01-05 03:48:36.488 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E1A0ABF2464E12B004D425032315558200308FAD2BE030A03004D7E
2021-01-05 03:48:36.490 [TRACE] [inding.balboa.internal.BalboaMessage] - Information Response received
2021-01-05 03:48:36.535 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF1314004E033000004D4D03040000000300000000043C0100001E0000DC7E
2021-01-05 03:48:36.536 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 3:48
2021-01-05 03:49:06.499 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E1A0ABF2464E12B004D425032315558200308FAD2BE030A03004D7E
2021-01-05 03:49:06.500 [TRACE] [inding.balboa.internal.BalboaMessage] - Information Response received
2021-01-05 03:49:06.548 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF1314004E033000004D4D03040000000300000000043C0100001E0000DC7E
2021-01-05 03:49:06.549 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 3:48
2021-01-05 03:49:29.066 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF1314004E033100004D4D03040000000300000000043C0100001E0000657E
2021-01-05 03:49:29.068 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 3:49
2021-01-05 03:49:36.502 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E1A0ABF2464E12B004D425032315558200308FAD2BE030A03004D7E
2021-01-05 03:49:36.503 [TRACE] [inding.balboa.internal.BalboaMessage] - Information Response received
2021-01-05 03:49:36.548 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF1314004E033100004D4D03040000000300000000043C0100001E0000657E
2021-01-05 03:49:36.550 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 3:49
2021-01-05 03:49:37.130 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF1314004E033100004D4D070C0200020300000000043C0100001E0000747E
2021-01-05 03:49:37.131 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 3:49
2021-01-05 03:49:37.134 [TRACE] [inding.balboa.internal.BalboaMessage] - Changes on unknown bits: 0000000000140000000000004D4D0008000000000000000004000100001E00000000
2021-01-05 03:49:43.733 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF1314004E033100004D4D070C0000020300000000043C0100001E0000707E
2021-01-05 03:49:43.734 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 3:49
2021-01-05 03:49:45.233 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF1314004E033100004D4E070C0000020300000000043C0100001E00000D7E
2021-01-05 03:49:45.235 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 3:49
2021-01-05 03:49:45.239 [TRACE] [inding.balboa.internal.BalboaMessage] - Changes on unknown bits: 0000000000140000000000004D4E0008000000000000000004000100001E00000000
2021-01-05 03:49:46.436 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF1314004E033100004E4E070C0000020300000000043C0100001E0000797E
2021-01-05 03:49:46.438 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 3:49
2021-01-05 03:49:46.440 [TRACE] [inding.balboa.internal.BalboaMessage] - Changes on unknown bits: 0000000000140000000000004E4E0008000000000000000004000100001E00000000
2021-01-05 03:49:51.236 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF1314004E033100004D4E070C0000020300000000043C0100001E00000D7E
2021-01-05 03:49:51.238 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 3:49
2021-01-05 03:49:51.241 [TRACE] [inding.balboa.internal.BalboaMessage] - Changes on unknown bits: 0000000000140000000000004D4E0008000000000000000004000100001E00000000
2021-01-05 03:49:54.833 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF1314004E033100004D4D070C0000020300000000043C0100001E0000707E
2021-01-05 03:49:54.834 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 3:49
2021-01-05 03:49:54.837 [TRACE] [inding.balboa.internal.BalboaMessage] - Changes on unknown bits: 0000000000140000000000004D4D0008000000000000000004000100001E00000000
2021-01-05 03:50:06.481 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E1A0ABF2464E12B004D425032315558200308FAD2BE030A03004D7E
2021-01-05 03:50:06.482 [TRACE] [inding.balboa.internal.BalboaMessage] - Information Response received
2021-01-05 03:50:06.527 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Processing message: 7E20FFAF1314004E033100004D4D070C0000020300000000043C0100001E0000707E
2021-01-05 03:50:06.529 [TRACE] [inding.balboa.internal.BalboaMessage] - Status update received 3:49
2021-01-05 04:06:18.947 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol disconnecting
2021-01-05 04:06:18.950 [DEBUG] [inding.balboa.internal.BalboaHandler] - Polling stopped
2021-01-05 04:06:18.953 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-05 04:06:18.955 [INFO ] [inding.balboa.internal.BalboaHandler] - Balboa Protocol went Offline
2021-01-05 04:06:30.681 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.handleCommand()' on 'org.openhab.binding.balboa.internal.BalboaHandler@921f5a': Cannot send message while not connected
	at org.openhab.binding.balboa.internal.BalboaProtocol$Writer.startWrite(BalboaProtocol.java:288) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaProtocol$Writer.sendMessage(BalboaProtocol.java:266) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaProtocol.sendMessage(BalboaProtocol.java:208) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaHandler$TemperatureChannel.handleCommand(BalboaHandler.java:948) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaHandler.handleCommand(BalboaHandler.java:249) ~[?:?]
2021-01-05 04:06:43.820 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.handleCommand()' on 'org.openhab.binding.balboa.internal.BalboaHandler@921f5a': Cannot send message while not connected
	at org.openhab.binding.balboa.internal.BalboaProtocol$Writer.startWrite(BalboaProtocol.java:288) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaProtocol$Writer.sendMessage(BalboaProtocol.java:266) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaProtocol.sendMessage(BalboaProtocol.java:208) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaHandler$TemperatureChannel.handleCommand(BalboaHandler.java:948) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaHandler.handleCommand(BalboaHandler.java:249) ~[?:?]
2021-01-05 04:06:48.953 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnecting...
2021-01-05 04:06:48.956 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-05 04:06:48.958 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-05 04:06:52.068 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Connection Failed: No route to host
2021-01-05 04:06:52.070 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Error: Connection Failed: No route to host
2021-01-05 04:06:52.073 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-05 04:06:56.588 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.handleCommand()' on 'org.openhab.binding.balboa.internal.BalboaHandler@921f5a': Cannot send message while not connected
	at org.openhab.binding.balboa.internal.BalboaProtocol$Writer.startWrite(BalboaProtocol.java:288) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaProtocol$Writer.sendMessage(BalboaProtocol.java:266) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaProtocol.sendMessage(BalboaProtocol.java:208) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaHandler$TemperatureChannel.handleCommand(BalboaHandler.java:948) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaHandler.handleCommand(BalboaHandler.java:249) ~[?:?]
2021-01-05 04:07:09.751 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.handleCommand()' on 'org.openhab.binding.balboa.internal.BalboaHandler@921f5a': Cannot send message while not connected
	at org.openhab.binding.balboa.internal.BalboaProtocol$Writer.startWrite(BalboaProtocol.java:288) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaProtocol$Writer.sendMessage(BalboaProtocol.java:266) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaProtocol.sendMessage(BalboaProtocol.java:208) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaHandler$TemperatureChannel.handleCommand(BalboaHandler.java:948) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaHandler.handleCommand(BalboaHandler.java:249) ~[?:?]
2021-01-05 04:07:22.073 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnecting...
2021-01-05 04:07:22.075 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-05 04:07:22.076 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-05 04:07:22.684 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.handleCommand()' on 'org.openhab.binding.balboa.internal.BalboaHandler@921f5a': null
	at org.openhab.binding.balboa.internal.BalboaProtocol$Writer.startWrite(BalboaProtocol.java:284) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaProtocol$Writer.sendMessage(BalboaProtocol.java:266) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaProtocol.sendMessage(BalboaProtocol.java:208) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaHandler$TemperatureChannel.handleCommand(BalboaHandler.java:948) ~[?:?]
	at org.openhab.binding.balboa.internal.BalboaHandler.handleCommand(BalboaHandler.java:249) ~[?:?]
2021-01-05 04:07:25.188 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Connection Failed: No route to host
2021-01-05 04:07:25.189 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Error: Connection Failed: No route to host
2021-01-05 04:07:25.191 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-05 04:07:55.191 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnecting...
2021-01-05 04:07:55.193 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-05 04:07:55.195 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-05 04:07:58.309 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Connection Failed: No route to host
2021-01-05 04:07:58.312 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Error: Connection Failed: No route to host
2021-01-05 04:07:58.316 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-05 04:08:28.316 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnecting...
2021-01-05 04:08:28.318 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-05 04:08:28.320 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-05 04:08:31.428 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Connection Failed: No route to host
2021-01-05 04:08:31.430 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Error: Connection Failed: No route to host
2021-01-05 04:08:31.432 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-05 04:09:01.432 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnecting...
2021-01-05 04:09:01.434 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-05 04:09:01.436 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-05 04:09:04.548 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Connection Failed: No route to host
2021-01-05 04:09:04.549 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Error: Connection Failed: No route to host
2021-01-05 04:09:04.552 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-05 04:09:34.552 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnecting...
2021-01-05 04:09:34.555 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-05 04:09:34.556 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-05 04:09:37.678 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Connection Failed: No route to host
2021-01-05 04:09:37.680 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Error: Connection Failed: No route to host
2021-01-05 04:09:37.681 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-05 04:10:07.682 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnecting...
2021-01-05 04:10:07.684 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-05 04:10:07.685 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-05 04:10:10.788 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Connection Failed: No route to host
2021-01-05 04:10:10.790 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Error: Connection Failed: No route to host
2021-01-05 04:10:10.791 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-05 04:10:40.791 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnecting...
2021-01-05 04:10:40.794 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-05 04:10:40.796 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-05 04:10:43.909 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Connection Failed: No route to host
2021-01-05 04:10:43.911 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Error: Connection Failed: No route to host
2021-01-05 04:10:43.912 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-05 04:11:13.912 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnecting...
2021-01-05 04:11:13.914 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-05 04:11:13.916 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-05 04:11:17.032 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Connection Failed: No route to host
2021-01-05 04:11:17.034 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Error: Connection Failed: No route to host
2021-01-05 04:11:17.037 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-05 04:11:47.037 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnecting...
2021-01-05 04:11:47.039 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-05 04:11:47.042 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-05 04:11:50.148 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Connection Failed: No route to host
2021-01-05 04:11:50.149 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Error: Connection Failed: No route to host
2021-01-05 04:11:50.151 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-05 04:12:20.151 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnecting...
2021-01-05 04:12:20.153 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-05 04:12:20.155 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-05 04:12:23.268 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Connection Failed: No route to host
2021-01-05 04:12:23.270 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Error: Connection Failed: No route to host
2021-01-05 04:12:23.272 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-05 04:12:53.272 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnecting...
2021-01-05 04:12:53.275 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-05 04:12:53.277 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-05 04:12:56.388 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Connection Failed: No route to host
2021-01-05 04:12:56.390 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Error: Connection Failed: No route to host
2021-01-05 04:12:56.392 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-05 04:13:26.392 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnecting...
2021-01-05 04:13:26.394 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-05 04:13:26.397 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting
2021-01-05 04:13:29.509 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Connection Failed: No route to host
2021-01-05 04:13:29.511 [DEBUG] [inding.balboa.internal.BalboaHandler] - Balboa Protocol Error: Connection Failed: No route to host
2021-01-05 04:13:29.513 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnection attempt in 30 seconds
2021-01-05 04:13:59.513 [DEBUG] [inding.balboa.internal.BalboaHandler] - Reconnecting...
2021-01-05 04:13:59.515 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.178.154 at 4257
2021-01-05 04:13:59.518 [DEBUG] [nding.balboa.internal.BalboaProtocol] - Balboa protocol connecting

and now in the UI the binding is showing a config error which it wasnā€™t just after the commands sent. disabling and reenabling the thing isnā€™t fixing it this time and neither is changing the ip address to something random and back to the balboas IP address. im in the process of restarting openhab to see if thatā€™ll help.