TA C.M.I binding - struggling with detection of channels on API Scheme

Dear Community,

I’m an absolute beginner to openhab, but quite experienced with T.A. I wish to read temperature values from a CMI API page exactly like shown in the documentation of the binding.

I get the thing connected, but no channels appear.

This is the API Schema page:

TSZ TemperaturSZ: 20.0 °C

TAZ TemperaturAZ: 20.2 °C

TBad TemperaturBad: 19.2 °C

TFlurOG TemperaturFlurOG: 20.3 °C

The CGI file of the API Schema page reads (for the first value) :

t
t TSZ TemperaturSZ:
c o c 10121500387
t

What am I missing? After the thing is “online” it should be able to see the page. Why does it not find the channels? How is the parsing for channels triggered?

regards,

Patrick

I know nothing about this binding nor the technology but I do notice this from the docs for the add-on:

All objects from this special ‘API’ page are automatically mapped as channels of this thing, so the labels of the objects on this page have to follow a specific schema.

When adding objects to this page, the schema for the Object’s Pre-Text field has to follow the schema <channelName> <channel description>:.

The Text from the Pre-Text will be used to define the channel. The first word tempCollector (highlighted in the screenshot) will be used as channel name, so it has to be unique. Everything else till the final : will be used as channel description. Be sure to have at least 2 words in the Pre-Text as we need both - the channel name and a description. The binding will log an error otherwise. Also keep in mind: for the channel name we have to adhere to the openHAB channel name conventions - so just use letters and numbers without any special sings here. The type of the channel will be automatically determined by the type of the object added. Also don’t forget the final colon - this is the separator between the label and the value. Without the colon the parser couldn’t build up a working channel for this value.

It is unclear what you’ve posted above is the pre-text field but nothing you posted above looks correct for that field based on these docs.