What is going on?
I have to say you guys make it really hard to keep using your platform.
From the 01st of July you decided to limit the MQTT access to paying customers which is fine, but to stop the support of the retain feature which is kind of essential i think for MQTT.
On your side you supply a workaround (Article for workaround) but it is actually not mutch help and to complicated to implement a feature which already worked (only with the use of an additional analysis).
For our application we would like to subscribe to a topic to send new settings or similar.
Can you please explain why you guys are constantly change things which worked already?
And can you give a example which publish data once I subscribe to a topic? What I understand in the above article you would need to publish to the subscribed topic?
Just to clarify, the Retained Messages feature was removed some months ago. On July 1st, we only limited MQTT access to paying accounts.
Anyway, I understand your concern; any changes inevitably affect a portion of our customer base. We face the challenge of maintaining the platform’s performance and reliability while keeping costs the same. That’s why we’re always finding ways to achieve this goal with minimal changes.
Currently, we offer an MQTT Broker at no cost and with very few limitations to our Starter and Scale users. However, to keep this service free, we chose to offer an MQTT broker primarily to facilitate the ingestion of data from sensors to data buckets. Therefore, our broker doesn’t offer all the features of a standard MQTT protocol like HiveMQ and EXMQ, which are paid services.
We know this impacts users, which is why I’m here to help. Beyond the workaround, we have also recently deployed a simple way to connect external MQTT Brokers to TagoIO. You can read more about it here: Connecting your MQTT Broker to TagoIO.
Michael, I know this still doesn’t solve your problem immediately. Although, I hope it clarifies.