openHAB Integration

Hi John,

would you mind to share your sitemap configuration, how you achieved such a clean overview as shown on https://github.com/openhab/openhab1-addons/wiki/Garadget-Binding ?

Glad you got the config sorted out!

I think the example items are similar to here, and since all items were in the UI group, I had simply navigated into that group using the Classic UI and taken the screenshot there. In other words, this was the default item rendering for the items defined in the items file.

Glad to see that Garadget finally got true off-line / no internet / no-cloud functionality via MQTT. I posted a request for this in August 2016, my Garadget from the Kickstarter sale has been sitting on a shelf waiting. I’ll be integrating it with OpenHab 2.x sometime later this year.

1 Like

For those interested in MQTT link, there is a good discussion in OpenHAB forum.

An issue with particle.io still has not been resolved in openHab. Is anyone working on fixing the binding? I put a lot of work into this setup and hate to see it wasted. I do not wish to rewrite my whole setup for MQTT.

The binding is not generating a token and gives the same error, even after clearing the cache, and restarting openHab.

Next I completely uninstalled the binding, cleared the cache, then reinstalled the binding. Still no success.

   2020-06-01 14:26:19.329 [DEBUG] [binding.garadget.internal.Connection] - About to execute 'https://api.particle.io/oauth/token'

2020-06-01 14:26:19.679 [DEBUG] [binding.garadget.internal.Connection] - Method failed: HTTP/1.1 400 Bad Request

2020-06-01 14:26:19.681 [DEBUG] [binding.garadget.internal.Connection] - Body of response: {"error":"invalid_grant","error_description":"User credentials are invalid"}

2020-06-01 14:26:23.940 [ERROR] [b.core.service.AbstractActiveService] - Error while executing background thread Garadget Refresh Service

java.lang.NullPointerException: null

	at org.openhab.binding.garadget.internal.Connection.sendCommand(Connection.java:229) ~[?:?]

	at org.openhab.binding.garadget.internal.Connection.sendCommand(Connection.java:186) ~[?:?]

	at org.openhab.binding.garadget.internal.Connection.getDevices(Connection.java:154) ~[?:?]

	at org.openhab.binding.garadget.internal.GaradgetBinding.execute(GaradgetBinding.java:204) ~[?:?]

	at org.openhab.core.binding.AbstractActiveBinding$BindingActiveService.execute(AbstractActiveBinding.java:146) ~[bundleFile:?]

	at org.openhab.core.service.AbstractActiveService$RefreshThread.run(AbstractActiveService.java:169) [bundleFile:?]

Particle must have changed their authentication API at some point. The binding has as you know the username and password but that probably went out of favour as too potentially insecure. I still have my Garadget device but no openHAB development environment setup. Could anyone isolate the API change that broke the binding? I would like the binding in a working state on case I put the device back into service. regards, John

Thanks for looking into this.
Particle moved away from product specific authentication. I’ve provided and oAuth2 endpoint for community integrations. Please see more details in this post: