Preparation for 2.5M2

[marcel_erkel]

@David_Graeff

no chance of any bugs fixed for 2.5.0

Yup that’s how it is atm.

@David_Graeff

Regarding MQTT. The thing is that the underlying library (paho mqtt) is full of bugs and only maintained by one guy that only occasionally works on it and currently focuses on mqtt5. And its an eclipse project

paho would need to be replaced by that other mqtt library (forgotten the name but linked in one of the issues). That’s unfortunately a Core contribution, which I’m clearly not doing at the moment.

paho has several subscription bugs with the async API that I’m using. Most of the java people out there seem to use the synchronous API which apparently works (most of the time). I don’t see a point in working around in the mqtt binding when the actual bugs are further down in the stack.

@rlkoshak

So MQTT 2.x is essentially abandon-ware. Wonderful.

Is there any way that a binding can be marked as experimental?