Using "Edge Nodes" in the topic of a regular mqtt transmitter

Hello,

Is it bad practise to use "Edge Nodes/" in the topic of a MQTT transmitter that does not have sparkplug B? Meaning that a sensor transmitting on "regular" mqtt ends up in the MQTT engine "Edge Nodes" folder together with the sparkplug B sensors.

We are doing it right now, and it looks to work fine besides the million JsonPayloadHandler errors:

com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'D8': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: (byte[])"D8:3B:DA:C4:03:C8"; line: 1, column: 4]

at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:2391)

at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:745)

at com.fasterxml.jackson.core.json.UTF8StreamJsonParser._reportInvalidToken(UTF8StreamJsonParser.java:3634)

at com.fasterxml.jackson.core.json.UTF8StreamJsonParser._handleUnexpectedValue(UTF8StreamJsonParser.java:2734)

at com.fasterxml.jackson.core.json.UTF8StreamJsonParser._nextTokenNotInObject(UTF8StreamJsonParser.java:902)

at com.fasterxml.jackson.core.json.UTF8StreamJsonParser.nextToken(UTF8StreamJsonParser.java:794)

at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:4761)

at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4667)

at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3707)

at com.cirruslink.mqtt.engine.gateway.json.JsonPayloadHandler.handlePayload(JsonPayloadHandler.java:148)

at com.cirruslink.mqtt.engine.gateway.EngineCallback.lambda$messageArrived$0(EngineCallback.java:260)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.base/java.lang.Thread.run(Unknown Source)

When i removed the parsing to json in the custom name space the JSONpayloadhandler error dissappeared. But i am still concerned that using regular mqtt with the "edge nodes/" might cause other issues as we view the "edge nodes/" folder as a sparkplug B feature