Andreas Motl

omg. Thanks for letting us know, and apologies for the late reply. We will take corresponding steps to remedy the problem in one way or another. > Paho™ MQTT Python...

At least the dependency version pinning in project metadata is right. So, when package managers are taking them into account, nothing should break from one day to the other _accidentally_?...

@dlangille: Relaying the error you reported.... > `ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md for details` ... it probably relates to the topmost item from...

## Thoughts - There might be issues with 2.0.0 yet, for example `AttributeError: ‘MQTTClient’ object has no attribute ‘_sock’`, see below. - Not sure if we should better wait upgrading...

I've just submitted a patch to remedy the breaking change on the most prominent spot, based on learnings from https://github.com/mqtt-tools/pytest-mqtt/pull/18. - https://github.com/eclipse/paho.mqtt.python/pull/831 However, I don't think that patch will be...

Hi. It looks like my patch might get accepted, helping users in basic use case scenarios to upgrade to Paho MQTT client version 2 without a breaking change. Naturally, it...

It looks like paho-mqtt v2 is causing serious havoc throughout the community. That is natural with breaking changes, and apparently, much of what is behind is about the proper transitioning...

For mqttwarn, I think it is sensible to wait for any further changes happen on paho-mqtt. Because mqttwarn is correctly applying the version pinning, I guess there is not much...

Hi Martin, excellent. Thanks for sharing your procedures. So, effectively you are doing some JSON attribute filtering and MQTT topic rewriting in your custom code, right? I wonder if mqttwarn...

Dear @tka85, thanks a stack for reporting this flaw. You might have discovered a bug, which should be addressed properly. To confirm: This is the error you are observing, regardless...