Hello,
I am having a very similar issue, with my device, as “rob.arbouw” who has explained in a similar forum (PR58-1_MQTT Temperature and Humidity Sensor with Ignition SCADA) about connectivity issues between NCD and Ignition on this website.
In this forum I discovered that “TravisE” fixed a bug in the firmware and told rob to update the device.
Thinking this would help my issue as well, I took the same steps while referring to the user guide for my device.
I installed the firmware, which acted as expected, but when I installed the spiffs file, the device did not enter configuration mode after the update finished installing.
Now, my device is blinking red, every second, and I am unable to factory reset or enter configuration mode.
Respectfully, I have already tried unplugging and plugging back in.
Anything helps, thanks! 
Ah. Bummer. You would have already had this firmware update since it was ordered recently so the firmware update was not necessary.
Power down the device, press and hold the CFG button, then power up the device while holding the CFG button. See if the LED flashes random colors to do a factory reset. If not let me know and we can try uploading over USB.
Thank you,
Travis Elliott
I figured however, as I was running out of ideas, I tried testing anyway.
I believe I am overthinking how to power down the device because I do not really see an on or off button, really all I can do is plug/unplug the device so I just did that to power it down while following your advice.
Still no change in LED. It still blinks red and I cannot change the color at all by pressing the CFG button.
I apologize for missing your last post here Alex.
It sounds like updating firmware over USB is going to be necessary. Since the SPIFFS upload failed the firmware is not able to read the appropriate settings on boot and is thus locked up.
You can update firmware over the USB port on the board, you will need to remove it from the enclosure to access that port.
Follow the instructions detailed here:
When prompted to select a firmware enter option 30 for the MQTT V2 Push Notification device. If you have any trouble updating please let me know.
Thank you,
Travis
No worries, I appreciate any help that I can get.
I took your advice and updated the firmware over USB and selected the MQTT V2 firmware. I can now turn on the device, connect to the internet, and my broker as before.
Unfortunately, the original problem still persists. I can not connect to my MQTT broker without enabling anonymous MQTT connections.
In the past I have also been in contact with Dan, from CirrusLink support, about the MQTT modules I am using. While in contact he mentioned that a possible reason could be that the device might not be “not sending MQTT credentials properly”.
Interesting. I just reviewed the firmware and all calls to connect to the MQTT broker utilize the client ID setting.
Could I get you to send me a private message on here with screenshots of your settings? The only way I can see Client ID being blank on connection is if the field is not filled out in the settings.
Thank you,
Travis Elliott
No problem, I just sent you a message containing a screen shot of my MQTT settings. please let my know what you think!
best,
Alex Bermejo
Hey Alex,
First I owe you an apology.
I tested the firmware on the MQTT push notification device here. It was submitting the Username and Password to the MQTT broker. BUT. I was not submitting the password through the web interface but rather a configuration file passed to the device. It turns out the issue was in the web configuration interface. The password field was using the wrong ID. I’m not sure how this has been missed to this point or how it is different than the Temperature/Humidity sensor this was based on but somehow that ID got set wrong.
I pretty much assure you that if you update the firmware on your sensor to v1.0.1 it will connect right up to Ignition no problem. Updating the firmware is covered towards the end of the guide here:
When updating you really only need to update the SPIFFS file. That as all that was changed other than the version number.
Again I apologize for being “dense” on this one.
Thank you,
Travis
No need to apologize! I am glad that we have finally found a solution to our problem.
Unfortunately, I have ran into a problem while installing v1.0.1. I should apologize because I know that you said that I really only need to update the SPIFFS file, but I decided to reinstall the firmware as well just so that my mind can rest easy that it has been fully updated.
However, in doing so, I now can not connect to the sensor’s soft AP which blocks me from accessing the web interface so that I can update the SPIFFS file.
Whenever I enter the password “NCDBeast”, the network connection just keeps prompting for that network security key.
Hey, no need to apologize to me. This is all my fault.
You can still update the firmware on the device but you’ll need to do it over USB. To do that you’ll need to pull the board out of the enclosure slightly so you can access the USB port.
Plug it into your computer. You may need to install this driver:
It should mount to your computer as a virtual COM or Serial Port. Once it does run the script documented here:
For the firmware choice you will want option 30.
Let me know if you have any trouble.
Thank you,
Travis
Thank you for your help! I have followed your instructions, and the instructions from the documentation you provided, and have successfully updated the firmware on the device over USB.
Unfortunately, I still can not connect to the soft AP from the device.
The device still flashed blue (configuration mode) and emits the soft AP (NCD-1EA4) but whenever I enter the default password (NCDBeast), I am told “The network security key isn’t correct. Please try again” and after making another attempt I get a message: “Can’t connect to this network”.
was there a change made to the soft AP connection that I should be aware of?
Try a factory reset. Power the device up, then press and hold the CFG button until the LED flashes random colors. After it reboots try connecting to the soft AP again. If that doesn’t work let me know.
Thank you,
Travis Elliott
I followed your instructions on a factory reset and attempted to connect to the soft AP, after the reboot.
To make sure I was doing the process 100% correct, I followed the instructions from the user guide as well.
I also repeated the process of performing a factory reset & trying to connect to the soft AP multiple times.
Unfortunately, I still “Can’t connect to this network”. 
This is very confusing to me because I was able to connect, before the update.