Bindings A thru F: Add equipment tags

[andrewfg]

This PR adds Equipment tags (only) to bindings A thru F.

• 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

Edit: Depends on: openhab/openhab-core#4738

[andrewfg]

@jlaur you may be interested in the tag usage statistics so far.

[mherwege]

LGTM for elroconnects

[ccutrer]

LGTM for bondhome

[jlaur]

LGTM for boschindego as well.

[lsiepel]

thanks, @andrewfg Covered all files. Some questions and suggestions to look at.

[lsiepel]

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

[mherwege]

LGTM for elroconnects

[andrewfg]

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

[Nadahar]

I'm getting a validation error when opening thing-types.xml for the Chromecast binding now, because of <semantic-equipment-tag>. When I check https://openhab.org/schemas/thing-description-1.0.0.xsd manually, it's there - however, Eclipse refuses to accept this.

My question is: Are the schemas being modified without bumping the version? Since this tag wasn't there earlier, it should no longer be 1.0.0. Doing that will cause trouble, "the rules" are that a version won't change, so they can be cached - and there might be no way to "reload" them, since they should never change. I'm guessing that is what is going on here.

Is there a reason why the version hasn't been bumped?

[andrewfg]

Eclipse IDE holds a cached version of the XSD which it never seems to refresh. You need to do a global search for the XSD in your Eclipse workgroup files, and replace those files with a freshly downloaded copy from the OH web server.

[Nadahar]

Eclipse IDE holds a cached version of the XSD which it never seems to refresh. You need to do a global search for the XSD in your Eclipse workgroup files, and replace those files with a freshly downloaded copy from the OH web server.

Yeah, I've found the files, but my point is: Why isn't the version bumped? Eclipse is doing it correctly, like every other piece of software should. Once you have a versioned schema, it can never change, so it should never expire.