websitedata file error - lightning data (v3116)

[liddelljs]

Hi all,
Very much enjoying having a 'play' with the look and feel of the new web pages - congrats to all.
I did strike an issue making a mod to the index page to include some lightning information from my Ecowitt lightning sensor. MX didn't have any data stored for it and so the time and distance was returning "---". When I added these tags to the websitedata file, it didn't like it and returned an undefined error on the webpage (the "---" string was recorded in the json file). None of the website data would populate to any of the web pages (not just the lightning data). I could see that there was some data in the json file but nothing below the lightning tags. No errors in the MXdiags file I could see.
As it happens, we had a thunderstorm today and some strikes were detected. I added the lightning tags back into the websitedata file and all is good. Not sure if the data file didn't like the non-numeric values.

Cheers
Steve

[ConligWX]

you did add the lightning tag into the websitedataT.json and not the actual websitedata.json file yes?

[liddelljs]

Hi Simon,
Correct - into the template file. The websitedata.json file contained the non-numeric strings ("---") that I thought were returned when there was no lightning data available. Problem went away when I got some actual data today courtesy of a thunderstorm. Hasn't been an issue since.

Cheers
Steve

[mcrossley]

Did you add quote marks around the lightning web tag in the template file so it was treated as text?

[liddelljs]

Hi Mark,
Pretty sure the syntax was correct - no problems since the lightning sensor had data. Based on @grimers comments on websitedata.json errors, I'm wondering whether it is something else. I'll keep monitoring and report back if any further problems.

cheers
Steve

[liddelljs]

Well spoke too soon. One of the updates just produce the attached websitedata.json file - not data but a system.argument error. No errors in MXdiags I could see.

Cheers
Steve

[mcrossley]

OK, I have found the issue, it's a conflict between the real time and interval processing, it only occurs when they happen at the same time. It will need a new release to fix.