Losant documentation ( https://docs.losant.com/mqtt/overview/#mqtt-version-and-limitations ) indicates that QoS 2 is not supported, implying that QoS 1 is. When I subscribe to a topic using node-red with QoS set to 1 the received messages indicate that they are sent as QoS 0. This is replicated when …

@Brandon_Cannaday : almost 4 years later, but we’re in the same boat as the post in here ► our MQTTS broker prefers/suggests SSL/Certificate (which we already implemented successfully) and QoS 1 - currently all messages in Losant are showing in the broker as QoS 0. I apologize if this has already be…

Hey @Jose_Cruz , QoS 1 is supported for publishing to Losant’s broker. This results in every message being PUBACK’d by the broker to verify delivery. QoS 1 is technically allowed for subscriptions, but Losant’s broker does not support cleansession=0, which means unacknowledged publishes to client s…

I am assuming by cleansession=0 you mean the [✓] Clean option in the Losant Integration page to be ‘unchecked’, which is not. Please correct me if wrong. If that’s the case, is showing on the broker (I consider Losant to be the client) as QoS=0: [image] Let me know if any of this makes sense, …

I see, you’re referring to Losant’s MQTT integration connecting to other brokers. This thread, and the other thread I linked are referring to clients connecting to Losant’s broker. Supporting QoS 1 for integration subscriptions may be possible. I’ll create a ticket to investigate.

Ok, thanks. Now here’s the very dumb question: Losant has its own broker? Where is that configurable? :red_circle:

Yep, Losant provides an MQTT broker. It’s one of the most common ways for devices to send telemetry data to the platform. All the details can be found here: MQTT Protocol Learn how to leverage the Losant IoT Platform through MQTT.

Oh, yes, I remember now - Losant broker can’t change the topic and has to be fixed (no wildcards). Nevermind. I remember now why it didn’t work for us and we had to go to an independent broker. Yes, if you can find about QoS1 that’d be great! :red_circle:

You can use any arbitrary topics with Losant’s broker and wildcards are supported in most places. Can you describe the limitation you experienced in more details?

[image] MQTT publishing Help I’ve seen a couple of threads of this issue, I’ve read them extensively but I’m still having some questions. In my case, the MQTT client and Losant MQTT broker work as long as: MQTT Broker URL is correct (which it is) MQTT path matches (wheth…

That makes sense. Connections to the broker require a device to authenticate, which makes it hard to use for system-to-system or “application level” access. We’ve been exploring ways to authenticate against the broker at an application level, specifically to help enable system-to-system integrations…

Cannot subscribe with MQTT QoS 1

Help

Jose_Cruz July 15, 2021, 3:26pm 14

Topic		Replies	Views
Workflow MQTT publish QoS? Help mqtt , workflow	4	557	June 18, 2021
Losant MQTT Broker and nodered Help mqtt	10	1013	December 9, 2021
MQTT Publish to external Broker with QOS Help mqtt , workflow	1	485	October 13, 2021
Any plans for MQTT QOS 1 Feature Request	5	1471	July 11, 2016
MQTT subscription using python and paho MQTT Help mqtt	3	188	September 18, 2024

Cannot subscribe with MQTT QoS 1

Related topics