Thomas Jaeckle

Closing as duplicate of #298

I would check if our used MQTT client - [HiveMQ MQTT client](https://github.com/hivemq/hivemq-mqtt-client) - even supports that. As this client strictly follows the MQTT protocols (and not interpretations of MQTT from...

Hi @antoniyatrifonova 1. The mentioned headers do not have static default values which could be specified, however: * if `content-type` is missing from the headers, `application/json` will be assumed for...

I fear that is a bigger topic as not even all available headers are currently documented on that page. What kind of information do you need and what do you...

Hi @marcluque I would start looking at `org.eclipse.ditto.connectivity.service.messaging.mqtt.hivemq.AbstractHiveMqttClientFactory.configureSimpleAuth()` - that's where the password is passed into the used HiveMQ MQTT client. Maybe HiveMQ MQTT client needs the password URL encoded...

This issue should be fixed with #1407 and #1424 Can you confirm that @Yannic92 ?

I don't see how the SimpleJson plugin should work - as it states in the docs: > Your backend needs to implement 4 urls: > `/` should return 200 ok....

Ah, ok. I did overread that :) Yes, that should work. Would the bridge than subscribe to events and build a little history itself? As I undestood the SimpleJson plugin...

Maybe this is not required at all and #700 is sufficient in order for a device to retrieve all "unapplied" `desired` changes.

@ffendt one concern could be that the `desired` state should not be cleared when the `properties` state reached the desired value. That's where a delta would still be beneficial, e.g....