Having got up to speed on the beta3 release, I’m interested in how to define the meta/config data in ESH-INF/binding/binding.xml where there are potentially multiple endpoints 1…n
As example, for each endpoint there are a number of parameters, e.g.
<name>plclogo</name>
<description>Binding for Siemens Logo PLC 0BA7 and 0BA8</description>
<author>Lehane Kellett</author>
<config-description>
<parameter name="logo1.host" type="text" required="true">
<context>network-address</context>
<label>Logo! IP address</label>
</parameter>
<parameter name="logo1.remoteTSAP" type="text">
<label>Remote TSAP</label>
<default>0x0200</default>
</parameter>
…
How would one define, and the user add, a second endpoint, such as logo2 via the PaperUI? Or should this be left to a cfg entry? Or left to a full OH2 binding and define each endpoint as a Thing?