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.
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
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 
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
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…?
@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.
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! 
@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.