Balboa Binding

[carlonnheim (Carl Önnheim)]

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

@joedirt

Connection Failed: No route to host

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?

@binderth

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.

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