-
-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SyntaxError: JSON.parse: unexpected keyword at line 1379 column 25 of the JSON data #225
Comments
Nan does not exist in json. Encoder needs to respect this, maybe using null instead. |
could you please post the raw data for SystemFlowTemp in this case? |
Sorry, I am only looking at this now again. Thanks for implementing nan-support. Here you can find one "nan" message (z1RoomTemp): root@ubuntu:/home/ubuntu/ebusd-configuration/latest/de/vaillant# cat /var/log/ebusd.log | grep z1RoomTemp I tried now to compile your update, I get the following error: CXX datatype.o I am using Ubuntu 16.04.5 LTS (GNU/Linux 4.4.0-1100-raspi2 armv7l). Many thanks and kind regards |
should work with be8d772 |
Perfect. That worked. Many thanks and Merry Christmas. |
great. thanks, same to you! |
I have ebusd running, using Domoticz via JSON to communicate with the deamon. However, every once in a while the JSON file cannot be properly parsed anymore (error from Domoticz, same when using firefox):
SyntaxError: JSON.parse: unexpected keyword at line 1433 column 25 of the JSON data
When I check the JSON file is is as follows:
"SystemFlowTemp": {
"name": "SystemFlowTemp",
"passive": false,
"write": false,
"lastup": 1542221911,
"zz": 21,
"id": [181, 36, 2, 0, 0, 0, 75, 0],
"fields": {
"tempv": {"value": nan}
},
The error seems to result from the ebusd message:
2018-11-14 19:58:13.198 [update error] unable to parse read 700 z1Name2 from 0015b52406020003001800 / 06030318003100: ERR: invalid position
I am using the following config for 15.700
address 15: slave #2, scanned "MF=Vaillant;ID=70000;SW=0419;HW=4603", loaded "vaillant/15.700.
The problem seems to lie in the "nan" value of the field. Do you have any idea on how to solve this?
Many thanks,
Jens
The text was updated successfully, but these errors were encountered: