Your work is highly valued by me and many others. I have been tracking your PR’s and I understand the frustration. You are touching an area that does not fit in the standard pattern yet, and it always takes a very long time to come to a conclusion for the key decisions with openHAB maintainers, if one is ever reached at all. I still believe it will progress eventually, but I expect to see that rather towards 3.0.0 than 2.5.x. Don’t walk away from it on your side please.
While working on this binding, I ran into issues that only can be resolved in the core or UI’s. Again, core developers are aware of many of these, but it will not be fully resolved before 3.0.0. Specifically, issues I have are:
- The ability to dynamically refresh DynamicStateOptionList and DynamicCommandOptionList objects in the UI’s. See openhab/openhab-core#1505 and openhab/openhab-addons#7396 (comment). This is key if you want a UI that is able to browse through the content hierarchy.
- There is no text input field possibility in BasicUI. This would be useful to be able to put in a textual search string to search the content directory. There is some workaround using a Webview element here, but it comes with its challenges. See also openhab/openhab-webui#274.
In the mean time, enjoy gardening.