Creating this topic to add some organization to the discussion, PR58-1_MQTT Contact Closure Push Notification, as it was becoming very dense.
At the end of the last discussion, I followed Travis’ instructions to install a firmware update (v1.0.1) on the Push Notification Sensor for use with MQTT. To make sure I was doing the process 100% correct, I followed the instructions from the Push Notification Sensor user guide as well.
Long story short, after installing the new firmware, I currently can not connect to the Push Notification Sensor’s soft AP so that I can access the Push Notification Sensor’s web interface.
to trouble shoot, I updated the device over USB and performed a factory reset on the device, as instructed by Travis and the user guide. I have always used the default password that has been defined in the user guide.
Unfortunately, I still “Can’t connect to this network”. 
This is very confusing to me because I was able to connect before the update.
Anything helps!
I just flashed a Push Notification device here using the Python script. I selected the Serial port, then entered 30 as the firmware option. After flashing completed I pressed the CFG button to put it in configuration mode(flashing Blue LED), I clicked the WiFi network for the device and when prompted for the network password I entered NCDBeast, WiFi connected, then in my browser I entered 192.168.0.1 and the configuration interface opened. Are these the same steps you took? It seems to be working here.
Yes these are the steps that I took after carefully reading the instructions from the resources that you have provided.
I believe the error lies somewhere between flashing the Push Notification Device and entering the device into configuration mode.
Whenever the Python script finishes, I am prompted to “Press any key to continue” and the LED prints white repeatedly.
I then pressed the CFG button to put it in configuration mode, clicked on NCD-1EA4, entered NCDBeast, and received this message:
After doing some testing I feel that, even though the Python script completed, the SPIFFS might not have flashed correctly. If the password is stored in SPIFFS, a bad flash could cause the AP to reject even the correct password.
Of course it could also be caused user-error, on my end, if the USB-to-serial communication was unstable, then the firmware might have flashed incompletely.
Since I cannot access the Configuration Interface, is there a way to run.bat the SPIFFS file only?
Hi Alex,
I don’t think it would be feasible for the firmware flash to succeed but the SPIFFS flash to fail. Also If you never changed the AP password then even if the SPIFFS flash failed I think it would still accept the NCDBeast password.
If the device goes into Configuration mode when you press the CFG button(LED flashes blue and it appears as a WiFi network) then it sounds like the SPIFFS file is on the device.
Have you tried forgetting the WiFi network on your computer or tried connecting with a different computer, phone, or tablet?
I think the best solution at this point may be to have you return the device and I can update the firmware for you. I don’t want you to struggle any more than you already have, especially when I know the issue is now resolved with the bug fix.
Thank you,
Travis Elliott
Thank you for sending a new device with the new firmware V1.0.1! I have successfully connected this device to our MQTT broker while requiring authentication. IWM has returned the other device and should arrive soon.
Now, we have another device (NCD-DE78) that is still V1.0.0 that needs to be updated to V1.0.1. Would it be possible to schedule a call so that you could walk me through the steps to update the device firmware? I have read the instructions carefully and taken your advice before, but the last time I failed to update the firmware which resulted in an inoperable device, and I am afraid of that happening again.
Hi Alex,
Yes, we could jump on a call to update. I would highly recommend just updating over the USB connection using the instructions I provided previously. I have tested that method and it does work reliably. I think the issue in the past was updating through the web interface which messed some things up. I’m confident if you do the update over USB you should have no problems.
Thank you,
Travis Elliott
Cool! I will send you a PM including my contact information.
I agree that updating over USB seems to be more reliable & that the issue lies updating through the web-interface.
This is why I would like your guidance so that we can be sure I am not messing anything up and avoid another Sensor exchange.
