Nice idea, but I guess a “binding” is the wrong approach here.
Actually, it’s not binding but UI addon.
The dashboard is already an OSGi service, why not simply add some configuration possibilities to it that picks up a conf/services/dashboard.cfg file in which additional tiles can be specified?
I tested this approach yesterday and I agree, this could be better option. Do you or anyone else have suggestion/opinion about the dashboard.cfg file content?
Currently dashboard links have four parameters; name, url, overlay and image url.
JSON:
org.openhab.ui.dashboard:link1={“name” : “openHAB Log Viewer”, “url” : “http://192.168.1.5:9001”, “overlay” : “”, “imageUrl” : “data:image/png;base64,iVBORw0KGgoAAA…uQmCC” }
org.openhab.ui.dashboard:link2={“name” : “Node-RED”, “url” : “http://192.168.1.5:1880”, “overlay” : “”, “imageUrl” : “data:image/png;base64,iVBORw0KGgoAAAANSUh…SuQmCC” }
Individual options:
org.openhab.ui.dashboard:link-name1=openHAB Log Viewer
org.openhab.ui.dashboard:link-url1=http://192.168.1.5:9001
org.openhab.ui.dashboard:link-overlay1=
org.openhab.ui.dashboard:link-imageurl1=data:image/png;base64,iVBORw0KGgoAAA…uQmCC
org.openhab.ui.dashboard:link-name2=
org.openhab.ui.dashboard:link-url2=
org.openhab.ui.dashboard:link-overlay2=
org.openhab.ui.dashboard:link-imageurl2=
Comma separated options:
org.openhab.ui.dashboard:link1=“openHAB Log Viewer”, http://192.168.1.5:9001, html5, data:image/png;base64,iVBORw0KGgoAAA…uQmCC
org.openhab.ui.dashboard:link2=…
Any other options?