I’m still on this forum, just on other topics/bindings mostly
BTW, my source repo for the updated 2.3.x binding is here (the one that supports add’l devices, scenes updates, etc.)
The ISY binding stuff has taken a bit of a back seat for me, since the stuff I have is working the way I need it, and I haven’t added any other Insteon devices lately - it’s more of the other networked stuff on OpenHAB (like the Eagle-200, Enphase Envoy or AmbiWeather bindings). However, for actual bugs in the 2.3.x binding, please submit a bug report on the github website (prefixed with [ISY] since I got a few other bindings there too).
Maybe an incentive to try? You know, there are really decent doc’s on the openhab web page how to set things up to make a “extremely trivial” change like that.
I bet that @kai and quite a few others are working on that every day, to get sponsors+money to pay those dedicated developers. Loads of OSS projects have started that way, they’re really slow to take off, but eventually gain that momentum (see Linux, Apache, etc). In the meantime, I’m happy for what has been already created with OpenHAB, I can add what I need and that isn’t there yet, and I’ll share it (my repo link is up in this post).
But you also have options:
Maybe OpenHAB/OSS devel pace isn’t for you, then you should use one of the commercial offerings
You can post on bountysource, beerpay, etc and see if someone can fix your problem for you
You can petition on the UDI forum that they create a official ISY binding for OpenHAB, which then should have all ISY devices supported, and which would supplant this current binding. Make sure to report back, I’ll be sure to vote for that request.
Use another platform (like node-red with the isy plugin), perhaps your device is supported there?
You can also use the existing openhab doc’s and get the devel environment setup, and see if you can get that “one-liner” copied/pasted, compiled, build and tested. 50/50 chances it works, if it doesn’t then the REST layout on the ISY is different for your device, and you’ll have to make adaptions for that different REST layout. Rinse/repeat until it works. Either way, once it works, I’ll gladly accept your pull request on github.