I know this issue will never be solved because no one cares about this repository but I want to help people that encounter the same problem, I did.
However, the library has some issues of parsing mqtt packages that were not sent with QoS level 0. Therefore it's the safest way to use only QoS 0.
It depends on the software you are using for sending the messages. I'm going to explain what I did:
I have a mosquitto server and the NanoESP. Sending messages with MQTT.fx is fine, no matter which qos you use. Using Paho javascript via websocket is difficult. Using qos 2 I didn't receive the messages. I sent "trigger" and received "+CIPSEND=0". I think it's a parsing problem of the library. Mosquitto_sub and mgtt.fx show all qos messages.
I know this issue will never be solved because no one cares about this repository but I want to help people that encounter the same problem, I did. However, the library has some issues of parsing mqtt packages that were not sent with QoS level 0. Therefore it's the safest way to use only QoS 0. It depends on the software you are using for sending the messages. I'm going to explain what I did:
I have a mosquitto server and the NanoESP. Sending messages with MQTT.fx is fine, no matter which qos you use. Using Paho javascript via websocket is difficult. Using qos 2 I didn't receive the messages. I sent "trigger" and received "+CIPSEND=0". I think it's a parsing problem of the library. Mosquitto_sub and mgtt.fx show all qos messages.