I have the following questions:
- Does it have to be 1 hour for a cycle? Can't you reduce that to 10 minutes or so?
- You can create a 'sensor gone' situation by disabling it in the app. Then restart CMX so it understands the sensor is gone
If not successfull I will ask you to just disable the soilmoisture sensor and when the upload fails leave it running failing. It may run until tomorrow morning, the result does not have to be tonight.
Than send me:
- The log for the useraskeddata run
- The ExtraLog202501.txt (the datafile)
- The corresponding json: the erroneous one which must be left in the utils directory and the last correct one which you will find on the server.
I just disabled my soilmoisture sensor and will see what I get (must be similar to you)
I did point to the additional problem of the extra sensor logging you have a pretty complex data log so it is difficult for me to see if something like that happens to you. Are you able to simplify the sensor situation by running a second instance and a beta test site to reduce the complexity?
We will now try to reduce the number of parameters for the error so do not change other sensors or intervals or whatever. Just one sensor disable and we'll see what it will bring us.
The most surprising thing is that when you disable the sensor the first datafile is OK but the second fails. I do not understand that.