[goecharger] Not working after #12400

[cribskip]

As pointed out from several people (see below), the newly introduced category Temperature seems to cause the binding to malfunction.

Best description seems to be done by kreutzer_peter in the community forum (see https://community.openhab.org/t/go-e-charger-wallbox-binding/93338/99)

21:08:30.073 [WARN ] [fig.xml.osgi.XmlDocumentBundleTracker] - The XML document '/OH-INF/thing/thing-types.xml' in module 'org.openhab.binding.goecharger' could not be parsed: The document is invalid, it contains further unsupported data: [NodeValue [nodeName=category, value=Temperature]]!
---- Debugging information ----
message             : The document is invalid, it contains further unsupported data: [NodeValue [nodeName=category, value=Temperature]]!
class               : org.openhab.core.thing.xml.internal.ChannelTypeXmlResult
required-type       : org.openhab.core.thing.xml.internal.ChannelTypeXmlResult
converter-type      : org.openhab.core.thing.xml.internal.ChannelTypeConverter
path                : /thing-descriptions/channel-type[22]
line number         : 209
class[1]            : java.util.ArrayList
required-type[1]    : java.util.ArrayList
converter-type[1]   : com.thoughtworks.xstream.converters.collections.CollectionConverter
class[2]            : org.openhab.core.thing.xml.internal.ThingDescriptionList
required-type[2]    : org.openhab.core.thing.xml.internal.ThingDescriptionList
converter-type[2]   : org.openhab.core.thing.xml.internal.ThingDescriptionConverter
version             : 1.4.19

Introduced with #12400, this seem to be the source of the problem:

openhab-addons/bundles/org.openhab.binding.goecharger/src/main/resources/OH-INF/thing/thing-types.xml

Line 208 in ba03fef

<category>Temperature</category>

@ranzen84, maybe you may take a look at this? Would be great to use the binding with your additions :-)

Cheers,
Sascha

[niklas85]

Unfortunately the same error is also in "openHAB 3.3.0 Milestone 4"... A fix would be great!

[ranzen84]

Havn't had the issue while developing. But I have created a PR to hopefully fix the issue: #12682