Hi Bob,
now I got the new firmware (2.2.30), the local graph app loads fast now, but the feedlist is still empty.
OK Szenti,
Can you try the following URL in your browser (substituting how you access iotawatt.local) and post the result?
http://iotawatt.local/feed/list.json
Also, what device/browser are you using?
I see the problem, now I need to find out why that is happening.
Would you delete output Fszt_Total and try graph again?
After deleting Fszt_Total it works fine!
That’s great. Could you try adding it back and see if it fails again? If so, could you upload your config.txt file so I can try to recreate.
This appears to be a problem with a library that I use to build Json responses. It is version controlled and you are running a six-month old version in 02_02_30. I’ll be upgrading to the latest with the next release, and maybe that fixes the problem.
In any event, could you mark this as solved?
I readded the line, and unfortunately it failed again doing the graph. Where do I find the config.txt?
I would consider that fortunate. Deleting your output is not a solution. If I can recreate it, I can fix it (or workaround).
you can download the config.txt file using the “File Manager and Editor” tool. Select it. The left column will be a list of the file system on your SD. You will see CONFIG.TXT among the root files. Right click on it and select download. Retrieve the file from your download folder and either:
Post it, redacting any server credentials, or
Send it to me in a PM (private message - click my icon and select “message”).
Thanks.
Done.
I found the problem. Long story short, when the feed list is too long, it doesn’t work. It’s not the number of feeds, but the total size of the list. In your case, the names are long, so it exceeds the limits. You got lucky removing that on output. The gap must have appeared in a non sensitive portion of the Json.
In the short term, you could reduce the size of the names or wait a few more days and take the next ALPHA release which resolves the issue. I was able to recreate the problem and made some changes to the development release. Your configuration is graphing fine here (ignore the data, it’s meaningless)
I hope to put out 02_02_31 as ALPHA auto-update later this week.
1 Like
All right, thanks. Shall I leave the update in major, or switch back to minor?
Once we kinda solved this I’d have another issue:-) I’d like to make a data cleanup, because last year I made some tests and there’s been a lot of junk data stored. How can I delete all data before the 01.01.2018?
You said alpha, I got it.
Sorry, I missed this inquiry. ALPHA is for users who would not have a problem downloading and installing a new firmware with one of several tools like ESPTOOL.PY should the wheels fall off the wagon. The sequence that I have been following is to run a new version on my three local systems for a day or two. If absolutely no problems, I publish to ALPHA. If no problems with the ALPHA community after a few days, I will push to BETA. MINOR is when I designate it an official release, and MAJOR is after MINOR has proven solid.
So if you think you can download and flash the ESP8266, you can go with ALPHA. I can always use more in that category. But if you would need help with the flashing beyond the instructions available with say ESPTOOL online, then I would recommend you wait a few more days for BETA to reduce risk.
FYI the new release done and is going into local test today.
I set it to BETA now. Will it be automatically updated?
Yes. Will go ALPHA today, and if all goes well, should be BETA in about a week.
There is no way to selectively delete portions of the datalog. You can delete the entire log and it will rebuild from the present time. There is an API to delete the log files. Each time it is invoked, the designated log is deleted and the IoTaWatt restarts. To delete all of your history, issue the following commands from your browser, being sure to do it in the order specified and waiting for the device to reboot after each. You will receive the response “ok” each time the command is run.
iotawatt.local/command?deletelog=current
iotawatt.local/command?deletelog=history
After you delete the current log, the system will create a new current log beginning at the time of restart. Your history log will remain intact with all of the accumulated history to date. You will notice no difference in running the local graph unless you request resolution of less than 60 seconds.
You can delete the history log anytime after that - up to about a year later. When the system restarts, it will build a new history log from the data in your current log, so history before the current log was created will be gone.
Be careful with these commands. There’s no undelete.
Hi Bob,
I’m wondering if the beta is out yet, how will I notice? The update class is set to beta, but the firmware is still 02_02_30. Please advise.
Hello @szentiga, Bob Lemaire can now be found at https://community.iotawatt.com, he has setup a dedicated forum for IotaWatt, if you post your question there Im sure he will get back to you quickly.
I have a doubt with the three phase (direct method - using 3 ac-ac adapter)… For this setup to work i need to connect each of the ac-ac adapter to a socket from each phase?
I suggest The IoTaWatt forum is a better place to ask a question that is specifically about the operation and use of IoTaWatt. That is managed by Bob Lemaire (@Overeasy), and he and the other users there are more likely to have the specific knowledge to help you.