Open MMM-Tech-Support opened 3 months ago
Hey again!
Here are some more informations to isolate the bug. When I run the JSON Datasource in Test Run Mode, i get a correct reading and the value is correct parsed with 3 decimal places.
When I load the same data in non test mode the bug happens and 1014.375 becomes 1014375.
Best regards!
Hi, for simpler debugging, can you attach the json example here?
Hey,
Sure, it's attached. The JSON path to atmospheric pressure is data/values/0 to 720/110_133_828
The first datapoint with more than 2 decimal places is at data/values/1/110_133_828
Please let me know if you need more information and again thanks for your great work!!! Best regards
working for me. I will do some more testing. is the error coming up when loading via the "load now" or during scheduled loads?
I found it. single value update is ok. batch update is causing an issue on some values.
by the way: I do not know how you loaded the numbers above. but with the array-type loading, you can get the timestamp also from the json file
data/values{110_133_828 ,read_at_group,110_133_828}
then you have all values from the file. not the perfect format. this can be adjusted later, but I think this might be more what you need?
fyi
path string:
data/values{Luftdruck,read_at_group,110_133_828}
I can see that you are reporting on your environmental sensors. If you want to discuss a better integration, feel free to get in direct contact with me analytics(at)scherello.de
same when using data from tables app. Value with 3 decimal values is parsed like: 9,600 -> 9,6 but 9,612 -> 9.612
Hey,
I use the JSON Datasource to get the atmospheric pressure via a HTTP GET command. It work's quite well.
When I analysed the data I recognized, that everytime the pressure has more than 2 decimal places the value is 1000 times to high.
So the value 1014.375 becomes 1014375 Please see the 3. column.
Here is the Graph and the the jumps between 1000 and 1000000 are clearly visible.
I checked the JSON file and the values are all correct. So I think there is a bug in the JSON Parser.
Best regards and thanks for your work! Heinrich