Hi @bertrand.gauvreau Please enable the ‘Wait For Network Formation’ checkbox. Then, disable all other already configured parameters and only leave the Power and Retries checkboxes enabled.
After making these adjustments, please try the configuration procedure again and share your results.
Hi @bertrand.gauvreau Apologies for the misunderstanding, this device does not support OTA, you can ignore the error messages, power and resets are set to maximum by default
Hi @Eduardo_Mtz Are you sure this device doesn’t support OTA? I’m asking because we regularly reconfigure this type of sensor remotely for our customers. You’re right about the default Power setting: it does seem to be the maximum (0x04). Unfortunately, in our case, we changed this setting to 0x03 before installation, and that doesn’t seem to be enough. That’s why we have to remotely reconfigure the sensors with the value 0x04.
Hi @bertrand.gauvreau I mean, this specific device does not support firmware update OTA. It does, however, support OTA Automatic Configuration.
Got it. Could you please try a factory reset? This will ensure the sensor returns to its original factory settings:
1. Press and release the RESET button
2. Immediately press and hold the CONFIGURATION button
3. Hold the CONFIGURATION button for about 20 seconds
4. Release CONFIGURATION button
5. Wait for 3 seconds
6. Press and release the RESET button
Then, perform a sensor configuration, leaving out; power and retries.
Thank you,
Eduardo M.
Hi @Eduardo_Mtz. The sensors are installed in one of our customers’ factories located more than 150 miles away from our office. That’s why I’m trying to reconfigure the sensors remotely (OTA). I really appreciate your efforts to help me. But I think we need to go back to the original question: “Why don’t the Power and Retries parameters give us the same confirmation message as the other parameters (True)” with these particular sensors, while this is OK with other similar sensors?
Thank You
Hi @bertrand.gauvreau Sometimes the sensor doesn’t respond to the settings quickly enough, causing the Node-RED configuration process to time out. This is likely the reason you are encountering an error. Could you please try the sensor configuration process again a couple of times?
Is there an effective way to check the “Power” and ‘Retries’ values stored in the sensor once these values have been modified? Unfortunately, the values returned in “Config Results” do not include Power or Retries.
The sensors are installed in one of our customers’ factories located more than 150 miles away from our office. That’s why I’m trying to reconfigure the sensors remotely (OTA). Is there a way to read Power and Retries other than the Node-Red node in OTA, since the Node-Red node seems to be unable to do so for several of the sensors?
We changed the Power and Retries settings at our office before installing the sensors at our customer’s factory. We reduced the Power setting to 3 to save battery life. But that was a mistake. That’s why we want to change the Power setting back to 4 and also verify that the setting has been changed correctly. We have around 30 sensors in the same situation.
Therefore, based on my observations, the error message during configuration seems to be related to the firmware version.
Now the key question is: are these messages generated because of a bug in the node-red-wireless node, because the parameters are simply not saved in the sensor, or because the sensor sends an error message even though the data has been saved correctly?
I have already spent several hours performing these tests. Unfortunately, I cannot go any further because further investigation is beyond my technical expertise.
Are you sure this device doesn’t support OTA? I’m asking because we regularly reconfigure this type of sensor remotely for our customers. You’re right about the default Power setting: it does seem to be the maximum (0x04). Unfortunately, in our case, we changed this setting to 0x03 before installation, and that doesn’t seem to be enough. That’s why we have to remotely reconfigure the sensors with the value 0x04.
