Bindings M thru R: Add equipment tags

[andrewfg]

This PR adds Equipment tags (only) to bindings M thru R.

• It adds Equipment tags where it is relatively easy to determine the type of Equipment from the context.
• It does NOT add any Point or Property tags => I am hoping that you code contributors will provide these.
• See Equipment tags in this table for reference.

Signed-off-by: Andrew Fiddian-Green software@whitebear.ch

Depends on: openhab/openhab-core#4738

[mvalla]

for OpenWebNet see some suggested changes. Other than those, LGTM

[lsiepel]

Thanks @andrewfg. Massive! Looked at all 317 files. Have some questions, suggestions and some comments are open for discussion.

[jlaur]

@andrewfg - can you rebase? #18538 was merged in the meantime, so there should not be any changes for the Miele binding.

[lsiepel]

Thanks. When the depending PR is merged, this can also be merged. LGTM

[mherwege]

LGTM for mybmw and nikohomecontrol

[andrewfg]

Many thanks to all contributors. Many thanks to @lsiepel for merging.

[lolodomo]

@andrewfg : is there a logic to use WebService for the bridge (account) and WeatherService for the things?
Shouldn't we have WeatherService here also?

[lsiepel]

Depends, if the bridge is just an account / proxy for other child Things, Webservice is fine.
If the bridge has channels and provides weather information by itself, it can be tagged WeatherService.

[lolodomo]

@andrewfg : can you explain what "Receiver" is for?
Is it for radio tuner?

[andrewfg]

Receiver is the English (American) term for a typical audio visual amplifier e.g. https://europe.yamaha.com/en/products/audio_visual/av_receivers_amps/index.html -- strictly it describes an "amplifier-plus-other-features" which may include a radio tuner, but in fact includes other features like streaming, multi channel surround, dolby or other processing, video switching and pass through. In other words "receiver" has become a generic name for any a/v device. By contrast the term "amplifier" has come to mean only purist stereo amps without any other features.

[lolodomo]

So you should have used Receiver more often for the Rotel devices (you largely used AudioVisual).
Is Receiver also adapted to a device that handles audio but not video ?

[andrewfg]

AudioVisual is the parent of Receiver so if the thing is not self evidently the latter then it gets classified as the former.

Apropos the device that handles audio only, the same rule would apply. I.e. AudioVisual is essentially the catch all for home entertainment equipment where no more precise sub classification can clearly be applied.

[jlaur]

I'll add that in this list: https://github.com/openhab/openhab-core/blob/main/bundles/org.openhab.core.semantics/model/SemanticTags.csv

Receiver has the synonyms: "Receivers, Audio Receiver, Audio Receivers, AV Receiver, AV Receivers"

So it should also cover at least some devices that handle only audio?

[mherwege]

When updating that file, maybe also think about adding a description that makes the result of this discussion clear to future users. The description will be shown as a tooltip in the UI.

[andrewfg]

think about adding a description

I will add that to the PR in core.. EDIT: done -- See openhab/openhab-core#4750