This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 25%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESR%3C/text%3E%3C/svg%3E)
I am trying to add a sensor to IoT Central. I already have 2 identical sensors running, but suddenly I cant add sensor nr. 3. I get the following error :
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13864
load:0x40080400,len:3608
entry 0x400805f0
1970/1/1 00:00:06 [INFO] Connecting to WIFI wifi_ssid mms-wireless
.0
1970/1/1 00:00:07 [INFO] WiFi connected, IP address: 10.11.12.106
1970/1/1 00:00:07 [INFO] Setting time using SNTP
........
2022/11/10 11:59:37 [INFO] Time initialized!
2022/11/10 11:59:37 [INFO] Azure IoT client initialized (state=2)
2022/11/10 11:59:37 [INFO] MQTT client target uri set to 'mqtts://global.azure-devices-provisioning.net'
2022/11/10 11:59:37 [INFO] MQTT client connecting.
2022/11/10 11:59:38 [INFO] MQTT client connected (session_present=0).
2022/11/10 11:59:38 [INFO] MQTT client subscribing to '$dps/registrations/res/#'
2022/11/10 11:59:38 [INFO] MQTT topic subscribed (message id=37503).
2022/11/10 11:59:38 [INFO] MQTT client publishing to '$dps/registrations/PUT/iotdps-register/?$rid=1{"modelId":"dtmi:azureiot:co2Template;1"}{"registrationId":"co2demo1","payload":{"modelId":"dtmi:azureiot:co2Template;1"}}'
2022/11/10 11:59:39 [INFO] MQTT message received.
2022/11/10 11:59:39 [INFO] MQTT client publishing to '$dps/registrations/GET/iotdps-get-operationstatus/?$rid=1&operationId=5.07d3c19271d37856.635fd50d-bec6-4415-a560-ea6386e10bac'
2022/11/10 11:59:39 [INFO] MQTT message received.
2022/11/10 11:59:42 [INFO] MQTT client publishing to '$dps/registrations/GET/iotdps-get-operationstatus/?$rid=1&operationId=5.07d3c19271d37856.635fd50d-bec6-4415-a560-ea6386e10bac'
2022/11/10 11:59:42 [INFO] MQTT message received.
2022/11/10 11:59:45 [INFO] MQTT client publishing to '$dps/registrations/GET/iotdps-get-operationstatus/?$rid=1&operationId=5.07d3c19271d37856.635fd50d-bec6-4415-a560-ea6386e10bac'
2022/11/10 11:59:45 [INFO] MQTT message received.
2022/11/10 11:59:48 [INFO] MQTT client publishing to '$dps/registrations/GET/iotdps-get-operationstatus/?$rid=1&operationId=5.07d3c19271d37856.635fd50d-bec6-4415-a560-ea6386e10bac'
2022/11/10 11:59:48 [INFO] MQTT message received.
2022/11/10 11:59:51 [INFO] MQTT client publishing to '$dps/registrations/GET/iotdps-get-operationstatus/?$rid=1&operationId=5.07d3c19271d37856.635fd50d-bec6-4415-a560-ea6386e10bac'
2022/11/10 11:59:51 [INFO] MQTT message received.
2022/11/10 11:59:54 [INFO] MQTT client publishing to '$dps/registrations/GET/iotdps-get-operationstatus/?$rid=1&operationId=5.07d3c19271d37856.635fd50d-bec6-4415-a560-ea6386e10bac'
2022/11/10 11:59:54 [INFO] MQTT message received.
2022/11/10 11:59:57 [INFO] MQTT client publishing to '$dps/registrations/GET/iotdps-get-operationstatus/?$rid=1&operationId=5.07d3c19271d37856.635fd50d-bec6-4415-a560-ea6386e10bac'
2022/11/10 11:59:57 [INFO] MQTT message received.
2022/11/10 12:00:00 [INFO] MQTT client publishing to '$dps/registrations/GET/iotdps-get-operationstatus/?$rid=1&operationId=5.07d3c19271d37856.635fd50d-bec6-4415-a560-ea6386e10bac'
2022/11/10 12:00:00 [INFO] MQTT message received.
2022/11/10 12:00:00 [INFO] MQTT client being disconnected.
2022/11/10 12:00:00 [INFO] MQTT client target uri set to 'mqtts://iotc-23dd2f7e-b6cc-4460-bb6a-dd296ea2881b.azure-devices.net'
2022/11/10 12:00:00 [INFO] MQTT client connecting.
2022/11/10 12:00:01 [ERROR] MQTT client in ERROR state.
2022/11/10 12:00:01 [ERROR] esp_tls_stack_err=0; esp_tls_cert_verify_flags=0;esp_transport_sock_errno=0;error_type=2;connect_return_code=3
2022/11/10 12:00:01 [ERROR] connect_return_code=MQTT_CONNECTION_REFUSE_SERVER_UNAVAILABLE
E (35969) MQTT_CLIENT: MQTT connect failed
2022/11/10 12:00:01 [INFO] MQTT client disconnected.
2022/11/10 12:00:16 [INFO] MQTT client connecting.
2022/11/10 12:00:17 [ERROR] MQTT client in ERROR state.
2022/11/10 12:00:17 [ERROR] esp_tls_stack_err=0; esp_tls_cert_verify_flags=0;esp_transport_sock_errno=0;error_type=2;connect_return_code=3
2022/11/10 12:00:17 [ERROR] connect_return_code=MQTT_CONNECTION_REFUSE_SERVER_UNAVAILABLE
E (52353) MQTT_CLIENT: MQTT connect failed
2022/11/10 12:00:17 [INFO] MQTT client disconnected.
2022/11/10 12:00:27 [INFO] MQTT client connecting.
What is going wrong?
Hi @Søren Thestrup ,
Welcome to Microsoft Q&S forum! Thank you for posting this question. Can you share any articles or resources that you might have followed in building this solution?
The error message in the log says MQTT_CONNECTION_REFUSE_SERVER_UNAVAILABLE. This could be related to a network error. Can you confirm if you still see this issue?
I don’t Think the issue is network related seen from the device perspective. As you can see in the log, the device obtaints an ip, gets current time from ntp server and does initial communication via mqtt.
The issue remains the same and it look like only one device can be active at a time. All devices are configured in iot central with their own device id, primary key an so on.
The device code is build from the Microsoft Azure esp32 example code from the Arduino IDE.
Thanks for helping.
Thank you @Søren Thestrup for providing the additional information. Could you please acknowledge if this is the repository you have used in setting up the connection - azure-iot-central-esp32-sample
May I know what type of sensor you are trying to test here? You question states you have 2 sensors that are running while the third one fails. Could you please clarify if you are using multiple Arduino boards to connect the sensor to Azure IoT Central? Also, are the other two sensors pushing data without issues when the third one failed. Providing these details would help us better to understand and isolate the issue.
Thanks for answering.
Correction. We have 3 identical devices measuring CO2 with the SCD41 sensor running on an ESP32 Wroom board. 1 device works fine. They alle have their own device name in IoT central. It seems that only one device can be active at a time. It doesn't make sense to me.
Yes that is the repository we use.
I just drove to the location of device 1. It doesn't matter if device 1 is disconnected or not. Device 2 and device 3 reacts with th.e same error as mentioned above
Hello @Søren Thestrup , thank you for validating the information and sharing additional details. Please allow me sometime to test the behavior from my end and I will get back to you with my findings.
Hi LeelaRajeshSayana-MSFT
I already have an ongoing support case with Microsoft, but they are at the moment unable to resolve the issue and have escalated my case.
Hi @Søren Thestrup , thank you for your response. Can you share the support request ID for your ticket so we can track it internally.
We have confirmation from Microsoft support that our problem can be reproduced. It turns out that if your application is based on "Azure_IoT_Central_ESP32" it will not be able to connect at the moment. Microsoft is investigating the issue. Until the issue is resolved Microsoft advise to use "Azure_IoT_Central_ESP32_AzureIoTKit" instead.
Hello @Søren Thestrup ,
Thank you for posting the solution you were shared with on the forum. I highly appreciate it! This will help our fellow community members facing a similar issue.
Please test with "Azure_IoT_Central_ESP32_AzureIoTKit" and update this thread if you still face any issues with it.
I used Azure_IoT_Central_ESP32_AzureIoTKit but still experiencing this error. This is a demo I was preparing for some live event on the capabilities of Azure IoT, "community based" Note that my current setup is different. I am using ESP-WROOM32 board, after I selected my board as Adafruit ESP32 Feather in Arduino IDE, the device status changed to provisioned, which was a good vibe, since then i have been receiving errors in my logs as below: Any insights on this ? 2023/4/14 15:20:30 [ERROR] MQTT client in ERROR state. 2023/4/14 15:20:30 [ERROR] esp_tls_stack_err=0; esp_tls_cert_verify_flags=0;esp_transport_sock_errno=0;error_type=2;connect_return_code=3 2023/4/14 15:20:30 [ERROR] connect_return_code=MQTT_CONNECTION_REFUSE_SERVER_UNAVAILABLE E (201543) MQTT_CLIENT: MQTT connect failed 2023/4/14 15:20:30 [INFO] MQTT client disconnected. 2023/4/14 15:20:45 [INFO] MQTT client connecting. 2023/4/14 15:20:47 [ERROR] MQTT client in ERROR state. 2023/4/14 15:20:47 [ERROR] esp_tls_stack_err=0; esp_tls_cert_verify_flags=0;esp_transport_sock_errno=0;error_type=2;connect_return_code=3 2023/4/14 15:20:47 [ERROR] connect_return_code=MQTT_CONNECTION_REFUSE_SERVER_UNAVAILABLE E (218748) MQTT_CLIENT: MQTT connect failed 2023/4/14 15:20:47 [INFO] MQTT client disconnected. 2023/4/14 15:20:57 [INFO] MQTT client connecting. 2023/4/14 15:20:59 [ERROR] MQTT client in ERROR state. 2023/4/14 15:20:59 [ERROR] esp_tls_stack_err=0; esp_tls_cert_verify_flags=0;esp_transport_sock_errno=0;error_type=2;connect_return_code=3 2023/4/14 15:20:59 [ERROR] connect_return_code=MQTT_CONNECTION_REFUSE_SERVER_UNAVAILABLE E (230830) MQTT_CLIENT: MQTT connect failed 2023/4/14 15:20:59 [INFO] MQTT client disconnected. 2023/4/14 15:21:14 [INFO] MQTT client connecting. 2023/4/14 15:21:17 [ERROR] MQTT client in ERROR state. 2023/4/14 15:21:17 [ERROR] esp_tls_stack_err=0; esp_tls_cert_verify_flags=0;esp_transport_sock_errno=0;error_type=2;connect_return_code=3 2023/4/14 15:21:17 [ERROR] connect_return_code=MQTT_CONNECTION_REFUSE_SERVER_UNAVAILABLE E (248034) MQTT_CLIENT: MQTT connect failed 2023/4/14 15:21:17 [INFO] MQTT client disconnected. 2023/4/14 15:21:32 [INFO] MQTT client connecting. 2023/4/14 15:21:34 [ERROR] MQTT client in ERROR state. 2023/4/14 15:21:34 [ERROR] esp_tls_stack_err=0; esp_tls_cert_verify_flags=0;esp_transport_sock_errno=0;error_type=2;connect_return_code=3 2023/4/14 15:21:34 [ERROR] connect_return_code=MQTT_CONNECTION_REFUSE_SERVER_UNAVAILABLE E (265237) MQTT_CLIENT: MQTT connect failed 2023/4/14 15:21:34 [INFO] MQTT client disconnected. 2023/4/14 15:21:44 [INFO] MQTT client connecting. 2023/4/14 15:21:46 [ERROR] MQTT client in ERROR state. 2023/4/14 15:21:46 [ERROR] esp_tls_stack_err=0; esp_tls_cert_verify_flags=0;esp_transport_sock_errno=0;error_type=2;connect_return_code=3 2023/4/14 15:21:46 [ERROR] connect_return_code=MQTT_CONNECTION_REFUSE_SERVER_UNAVAILABLE E (277319) MQTT_CLIENT: MQTT connect failed 2023/4/14 15:21:46 [INFO] MQTT client disconnected. 2023/4/14 15:22:01 [INFO] MQTT client connecting. 2023/4/14 15:22:03 [ERROR] MQTT client in ERROR state. 2023/4/14 15:22:03 [ERROR] esp_tls_stack_err=0; esp_tls_cert_verify_flags=0;esp_transport_sock_errno=0;error_type=2;connect_return_code=3 2023/4/14 15:22:03 [ERROR] connect_return_code=MQTT_CONNECTION_REFUSE_SERVER_UNAVAILABLE E (294524) MQTT_CLIENT: MQTT connect failed 2023/4/14 15:22:03 [INFO] MQTT client disconnected. 2023/4/14 15:22:18 [INFO] MQTT client connecting. 2023/4/14 15:22:20 [ERROR] MQTT client in ERROR state. 2023/4/14 15:22:20 [ERROR] esp_tls_stack_err=0; esp_tls_cert_verify_flags=0;esp_transport_sock_errno=0;error_type=2;connect_return_code=3 2023/4/14 15:22:20 [ERROR] connect_return_code=MQTT_CONNECTION_REFUSE_SERVER_UNAVAILABLE E (311726) MQTT_CLIENT: MQTT connect failed 2023/4/14 15:22:20 [INFO] MQTT client disconnected. 2023/4/14 15:22:30 [INFO] MQTT client connecting. 2023/4/14 15:22:32 [ERROR] MQTT client in ERROR state. 2023/4/14 15:22:32 [ERROR] esp_tls_stack_err=0; esp_tls_cert_verify_flags=0;esp_transport_sock_errno=0;error_type=2;connect_return_code=3 2023/4/14 15:22:32 [ERROR] connect_return_code=MQTT_CONNECTION_REFUSE_SERVER_UNAVAILABLE E (323810) MQTT_CLIENT: MQTT connect failed 2023/4/14 15:22:32 [INFO] MQTT client disconnected. 2023/4/14 15:22:42 [INFO] MQTT client connecting. 2023/4/14 15:22:44 [ERROR] MQTT client in ERROR state. 2023/4/14 15:22:44 [ERROR] esp_tls_stack_err=0; esp_tls_cert_verify_flags=0;esp_transport_sock_errno=0;error_type=2;connect_return_code=3 2023/4/14 15:22:44 [ERROR] connect_return_code=MQTT_CONNECTION_REFUSE_SERVER_UNAVAILABLE E (335893) MQTT_CLIENT: MQTT connect failed 2023/4/14 15:22:44 [INFO] MQTT client disconnected. 2023/4/14 15:22:59 [INFO] MQTT client connecting. 2023/4/14 15:23:01 [ERROR] MQTT client in ERROR state. 2023/4/14 15:23:01 [ERROR] esp_tls_stack_err=0; esp_tls_cert_verify_flags=0;esp_transport_sock_errno=0;error_type=2;connect_return_code=3 2023/4/14 15:23:01 [ERROR] connect_return_code=MQTT_CONNECTION_REFUSE_SERVER_UNAVAILABLE E (352892) MQTT_CLIENT: MQTT connect failed 2023/4/14 15:23:01 [INFO] MQTT client disconnected.
Hi @AronAyub-7919, I appreciate it if you can open a new thread to track this issue so that we can provide more concise feedback targeted to your scenario.
Alright, thank you @LeelaRajeshSayana-MSFT , i appreciate you