we have a situation where our CoAP clients succesfully begin Observing a topic. Next we use an MQTT client to periodicaly (20s) post something on that topic. We receive some messages through this pipeline. Alongside this feature our CoAP client keeps sending Confirmable data packets to the server, every 5s.
But after some time the packets stop coming... we have observed on the dashboard that on the MQTT side the client is not subscribed anymore. Meanwhile we still successfully deliver the data and get confirmation messages from the server...
We did multiple checks and we know that our client does not send an Un-Observe CoAP packet. As such we cannot find why it unsubscribes.
Similar behaviour happens instantly if we use 3-5 packet bursts from the MQTT client side, as if the CoAP plugin cannot handle this situation...
We are using eqmx 4.3.4.
We extended the CoAP "keep alive" to 24h.
Please could you provide suggestion on which setting we could check or set...
Hello!
we have a situation where our CoAP clients succesfully begin Observing a topic. Next we use an MQTT client to periodicaly (20s) post something on that topic. We receive some messages through this pipeline. Alongside this feature our CoAP client keeps sending Confirmable data packets to the server, every 5s.
But after some time the packets stop coming... we have observed on the dashboard that on the MQTT side the client is not subscribed anymore. Meanwhile we still successfully deliver the data and get confirmation messages from the server...
We did multiple checks and we know that our client does not send an Un-Observe CoAP packet. As such we cannot find why it unsubscribes.
Similar behaviour happens instantly if we use 3-5 packet bursts from the MQTT client side, as if the CoAP plugin cannot handle this situation...
We are using eqmx 4.3.4. We extended the CoAP "keep alive" to 24h.
Please could you provide suggestion on which setting we could check or set...