Balboa Binding

update: I set the Balboa WiFi to “no internet for you” and had no issues since.

but of course it tries to reach home aggressively nevertheless, as my PiHole tells me:

I have been testing this a bit now and it works well for me, I mostly just turn the light on and off and check the temperature using Google Assistant but I have also turned off and on the heater and circulations. Thanks for all the great work!

After accidentially updating to openHAB 3.1 stable I get the following error in the log:

2021-06-30 16:36:40.273 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab/addons/org.openhab.binding.balboa-3.1.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.balboa [235]
  Unresolved requirement: Import-Package: javax.measure; version="[1.0.0,2.0.0)"
	at org.eclipse.osgi.container.Module.start(Module.java:463) ~[org.eclipse.osgi-3.16.200.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:440) ~[org.eclipse.osgi-3.16.200.jar:?]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.6.8]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.6.8]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [bundleFile:3.6.8]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [bundleFile:3.6.8]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.6.8]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.6.8]

Can I do something about this? or has this to be changed in the binding.jar?

Hi

Can anyone confirm if openHAB 3.1 stable breaks this binding.

Great work with this binding!!!

Thanks

@binderth @clinophobic

Did you guys end up getting this working with 3.1?
My system is currently updating to 3.1 now

I just went back to the previous build to keep system working.

I found on a previous post in forum

‘adding an explicit dependency in pom.xml solved the problem’

Unfortunately I have no understanding of what that means. There is a pom.xml in the source code but I have no idea how to turn the source into a jar to test.

So in short no and I have no idea how to even help how to solve it unfortunately.

I did this building my own binding, in my case using Visual Studio Code. I have not done any follow up to determine if the dependency is still needed in OH3. Lots of information out there on how to setup a build environment, not a quick undertaking, but the documentation is quite good if you decide to pursue it.

Sorry, no quick fix without help from the binding’s author or another contributor.

Thanks Scott for advice. Always up for learning. I’ll give it a go.

Bump, did anyone end up getting this working? I had a look at the coding stuff but it looks a little above my head unfortunately.

Hi,

Sorry for the lack of engagemang om my part, struggling to find the time between day-job and family life… Still have my own setup on OH2, but will take a look at bringing that up to OH3 with the binding.

Regards
//Carl

1 Like

Awesome thanks mate, I really appreciate it!

Is there anything I can do to help out? I don’t mind sending you some money to get this working with oh3 if that helps?

Hi @joedirt I used the tutorial here Eclipse IDE | openHAB and have managed to get a working version with 3.1 of @carlonnheim binding by doing what @scottr had done before with the dependency.

Btw i have no idea what I am doing or how to use git or github so I have just uploaded the jar to it. It can be found here to try.

Cant make any promises but it works for me.

1 Like

Thanks @clinophobic, works with me also:

2021-08-27 08:02:57.033 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from UNINITIALIZED to INITIALIZING
2021-08-27 08:02:57.040 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from INITIALIZING to UNKNOWN
2021-08-27 08:02:57.040 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.xxx.yyy at 4257
2021-08-27 08:02:58.273 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from UNKNOWN to ONLINE (CONFIGURATION_PENDING): Configuration request sent
2021-08-27 08:02:58.383 [INFO ] [inding.balboa.internal.BalboaHandler] - Balboa Protocol is Online
2021-08-27 08:02:58.386 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from ONLINE (CONFIGURATION_PENDING): Configuration request sent to ONLINE
2021-08-27 08:02:58.432 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'BalboaIPUnit_TargetTemperature' changed from 34 °C to 32 °C
2021-08-27 08:02:58.437 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'BalboaIPUnit_Priming' changed from OPEN to CLOSED
2021-08-27 08:02:58.442 [WARN ] [ab.core.internal.items.ExpireManager] - Expire config '1h0m0s,command=UNDEF' of item 'BalboaIPUnit_CurrentTemperature' is invalid: The string 'UNDEF' does not represent a valid command for item BalboaIPUnit_CurrentTemperature
2021-08-27 08:02:58.454 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'BalboaIPUnit_CurrentTemperature' changed from 34 °C to 32 °C
2021-08-27 08:03:01.470 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'BalboaIPUnit_WhirlpoolAutomatic' received command ON
2021-08-27 08:03:07.667 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from ONLINE to UNINITIALIZED
2021-08-27 08:03:07.697 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2021-08-27 08:03:07.926 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2021-08-27 08:03:07.932 [INFO ] [inding.balboa.internal.BalboaHandler] - Starting balboa protocol with 192.168.xxx.yyy at 4257
2021-08-27 08:03:07.934 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from INITIALIZING to UNKNOWN
2021-08-27 08:03:07.953 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from UNKNOWN to ONLINE (CONFIGURATION_PENDING): Configuration request sent
2021-08-27 08:03:08.120 [INFO ] [inding.balboa.internal.BalboaHandler] - Balboa Protocol is Online
2021-08-27 08:03:08.126 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'balboa:balboa-ip:b9e1682ef3' changed from ONLINE (CONFIGURATION_PENDING): Configuration request sent to ONLINE
1 Like

Nice one. Don’t think I could of been any help if it didn’t :slight_smile:

Has anyone made any fancy OH3 UIs for their spas?

1 Like

Not UIs, but rules!

  1. heat the Spa up, if needed
  2. turn the Spa down at night
  3. use PV logic (e.g. if there’s plenty of yield: "over"heat the Spa for later use, use it as “storage” so to speak)

So I don’t have an UI, I just want to use “Alexa turn on the Spa” or have it change to low range at night, …

1 Like

You sir are a bloody legend!!! It’s working flawlessly for me!!!

Happy i could help. :slight_smile:

I updated to openHAB 3.2.0.M3 and all is working well :slight_smile:

1 Like

Hi Guys,

I was trying to get this binding to work with my OH3.1 before and didn’t have any luck. Tried this today again with 3.2 binding but for some reason I can’t get this installed. What I’m doing is downloading the file and placing it in my addons folder, changing permissions on the .jar file and restarting OH service. Same process that I was doing with my other addons in the past but this binding is not visible in my OH3 install. I’ve checked via WebUI and also via openhab-cli. Can someone help me to get this working please.

Regards,
Walter