I have ported/updated two bindings with the help of AI and would appreciate some guidance:
-
How should I make them available? Should I post them in the forum first and potentially move them to the Marketplace later? (It seems a bit of a waste to only keep them for myself).
-
How should the use of AI be disclosed? The code was 100% generated by AI. I didn’t do a review of the code, but mainly tested the resulting bindings for functionality. Do we have standard disclaimers for this.
-
Are there any best practices to improve quality? My current approach was:
- Generate the binding with Sonnet 5
- Have Opus 5 review the result
- Feed most of the findings back to Sonnet and fix them
- Run a similar review cycle specifically looking for resource-related risks
The bindings are: (I’ll post them in seperate threads):
-
Balboa binding: Updated from OH3 to OH5.2, including autodetection, performance improvements and fixes for network-related bugs.
-
Jablotron binding: A new, local USB binding generated from an existing Python implementation. This one particularly surprised me — with relatively few iterations, AI produced a correctly working binding. Interestingly, the AI itself recommended not creating a full openHAB binding, but instead connecting the Python script via MQTT, arguing that a proper openHAB binding would be quite complex.
I understand, and actually share, some of the concerns about AI-generated bindings. On the other hand, smart home has a very long tail of devices and integrations, and AI-generated bindings could potentially be a way to achieve much broader coverage.
So: What would be the recommended way to proceed with these bindings, and are there any guidelines or best practices for AI-generated openHAB add-ons?