You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 14, 2023. It is now read-only.
I'm working on a project with iot central based data logging and the connection to the internet is done via a UMTS stic. Data is collected and stored locally until there is good signal strength, then all the collected data is sent to the iot central in a loop.
The issue is that after some messages
iotc.sendTelemetry(message)
returns code 4, connection refused.
After all collected messages I disconnect from iotc and reconnect again in the next cycle. Only some loops and some messages fail to send.
Does someone have any idea to fix this or experienced similar behavior?
The text was updated successfully, but these errors were encountered:
There are several limits in IoT Central - message size, # of messages per device and # of messages per second that IoT Hub (that is working in the back end) can absorb.
Could you please share size of message and # of messages that you are sending and during which period of time?
BTW. Error #4 = MQTT_ERR_NO_CONN = 4 it looks like no connection.
Also you can use class IOTLogLevel: IOTC_LOGGING_ALL = 16
to see all logs.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm working on a project with iot central based data logging and the connection to the internet is done via a UMTS stic. Data is collected and stored locally until there is good signal strength, then all the collected data is sent to the iot central in a loop.
The issue is that after some messages
iotc.sendTelemetry(message)
returns code 4, connection refused.
After all collected messages I disconnect from iotc and reconnect again in the next cycle. Only some loops and some messages fail to send.
Does someone have any idea to fix this or experienced similar behavior?
The text was updated successfully, but these errors were encountered: