Cumulus Support

• Failing in GenerateExtraSensorDataJson - i.e. ExtraSensors (incl External) data).
  Message - Object reference not set to an instance of an object.)

• Uploading => extrasensorsdata.json from utils/extrasensorsdata.json
  No valid JSON data in the received data
  (this 2nd error could be just a consequence of the 1st error).

2025-01-04 23:30:31.485 Information ExtraSensorslog constructor: Using fixed path: | data/ |; file: | *log.txt
2025-01-04 23:30:31.485 Information ExtraSensorslog: starting
2025-01-04 23:30:31.486 Information ExtraSensorslog: timeStart = 04.01.2025 23:16:00; timeEnd = 04.01.2025 23:30:00
2025-01-04 23:30:31.486 Information ExtraSensorslog: Require data/ExtraLog202501.txt to start
2025-01-04 23:30:31.498 Information ExtraSensorslog: Finished reading the log at 04.01.2025 23:30:00
2025-01-04 23:30:31.498 Information ExtraSensorslog: MainExtraSensorsValuesList created: 3 records.
2025-01-04 23:30:31.498 Information ExtraSensorslog: End
2025-01-04 23:30:31.498 Information UserAskedData: Failing in GenerateExtraSensorDataJson - i.e. ExtraSensors (incl External) data)
2025-01-04 23:30:31.498 Information UserAskedData: Message - Object reference not set to an instance of an object.)
2025-01-04 23:30:31.498 Information UserAskedData: Continuing

lse-cumulus wrote: ↑Mon 06 Jan 2025 8:17 am All my sensors are now reachable and sending data, so no null values produced in Extra Logs.
Therefore ExtraSensor module from CU is working fine and no errors in UserAskedData.
I think my problem is related to the following forum topic: viewtopic.php?t=22846.
For CustomLogs the workarround from CMX/Mark with Webtag nv=0 is a valid solution. For CU ExtraLogs I have no direct control of the webtags used internally by CU ... (would need a code change in CU or a global parameter settings in CMX for webtag null values as Hans suggested).

1. I consider this topic solved
2. It is not related to the CustomLog issue in the cited topic because the ExtraSensor values are read by CUtils explicitly from the log and not through the webtags. CustomLogs are fundamentally different from ExtraSensors (both in CMX as in CUtils).
3. When there are null values, they should display in the chart as a straight line to the next valid value. If there appears to be a problem with that (I'll start testing later) I will take action.

lse-cumulus wrote: ↑Tue 07 Jan 2025 2:29 pm c) But my problem is the following: as soon as an extra sensor does not send data, a NULL VALUE is written to Extra Logfile (in the CMX Edit log Editor I see an empty field in that case, instead of numerical value like 0 or 1.3, ...)
and exactly in that situation the utils UseraskedData does not produce any extrasensorsdata.json data structure at all and does not try to upload any data or produces an invalid json structure detected by upload.php.
And as a consequence the CU extra chart stop. And not only for the missing sensor but for all extra sensors.
That is my problem.

lse-cumulus wrote: ↑Tue 07 Jan 2025 2:29 pm I do not know where CU writes the interim extrasensorsdata.json file before trying the upload so I could not attach.

lse-cumulus wrote: ↑Tue 07 Jan 2025 2:29 pm also no error appears, but just the following informational lines:
Information UserAskedData: Failing in GenerateExtraSensorDataJson - i.e. ExtraSensors (incl External) data)
Information UserAskedData: Message - Object reference not set to an instance of an object.)

lse-cumulus wrote: ↑Tue 07 Jan 2025 2:29 pm As soon as no null values are recorded any longer in the extra Logfile (in the 1 hour intervall that useraskedata looks up, as I run it hourly), the two informational lines disappear and a correct extrasensorsdata.json is uploaded.

During the CMX/CU upgrade I did first overlook the informational lines and thought i had just an upload.php problem and deleted the file extrasensorsdata.json from my webserver directory. Then of course no extra sensor charts were displayed at all,
but I also did not get a new extrasensorsdata.json file as any useraskeddata run failed to produce a new file (or upload it) as long as null values were found in the Extra Logfile.

lse-cumulus wrote: ↑Wed 08 Jan 2025 6:50 pm Hans, just one question: why do you say there will also be a future CMX fix? for me the CMX null value behavior seems correct ...

• 15:00 utils useraskeddata and utisl Website BEFORE null values; just to verify that all is ok with CU 7.3.3 Beta4

• 15:45 removed batterie from WH51CH2 soilmoisture sensor. Needed to restart CMX to ask GW2000 again to detect that sensor sends no longer data

• 16:00 Utils UserAskedData runs OK and can handle null vaues, no error messages, no info messages in GenerateExtraSensorDataJson; extrasensorsdata.json uploaded without errors; problem seems to be resolved. Extra Chart shows continuing line with previous value. Unfortunately I did NOT take a screenshot and wanted to do it after next UserAskedData.

• 17:00 but 2nd UserAskedData could not upload extrasensorsdata.json. upload.php reported no valid json data in file; but in the logfile I canot see the previous info lines that accompanied the null value problem (Failing in GenerateExtraSensorDataJson, Message - Object reference not set to an instance of an object). The Website Extra Sensor Charts no longer shows any data at all. So the problem seems to be back but in a slightly different form. But it could also be that I ran here into a new or other issue ...

• 18:00 disabled another sensor WH31CH3 Temperature (as I saw that soil moisture is no ideal candidate and takes too long to refelect changes and went to 0 when removing from soil). Utils Useraskeddata reports no errors during Generation of Extra Sensors, but reports no valid json data when trying to upload extrasensorsdata.json

• 18:15 activated both sensors again; restarted CMX and waited until extra Logfile shows no longer null values

• 18:30 utils UserAskedData works OK and uploads succesfully extrasensorsdata.json. The error no valid json data disappeared. The Website Extra Sensors Charts work again and I took screenshot. The charts show no data for both sensors before 18:15, but data start at 18:15 again for extra Temperature and Extra Soil Moisture.

• 19:00 waited for next utils UserAskedData and continues to be ok.