EmonPi feeds page blank

I have a system runnign EmonPi and it’s been working for several years without a problem (using an SSD rather than an SD card). I added another input and edited the feeds page… When i came back to the feeds page it’s now completely blank. All of the input are working, Dashboards are being updated and EmonHub seems happy receiving data and passing it along. But of course I can no longer edit any feeds. I’ve imported an old backup and all is fine - except a years worth of lost data and some feeds not setup. I have restored the ‘broken’ backup and it doesn’t complain but the feed page remains empty.

Can anyone advise what I should be looking at - please be gentle as I’m no Linux person!

Carl

I can add one further piece of information: The EmonCMS log shows:

2026-08-18 21:28:45.573|ERROR|feed_model.php|get_timevalue() Feed ‘175’ does not exist.
2026-08-18 21:28:45.575|WARN|feed_model.php|Feed model: Requested feed does not exist feedid=175

Might this have something to do with the problem?

Hi and welcome.

What version of emoncms are you on?

Is the page completely blank or does it have the header and menu?

Have you tried rebooting?

Have you tried clearing the browser cache?

Beware! Don’t reboot the Raspberry Pi without doing a controlled shutdown first, either using the button on the front of the emonPi or via the Admin menu of emonCMS. If you do, even though the risk is probably lower with your SSD, you risk further damage to the file structure.

I think the problem is most likely to be the missing Feed 175. @borpin Isn’t there a script to tidy up problems like this? Or is this something we need @TrystanLea’s input to?
What I think Carl needs to do is take Feed 175 out of the input processing, delete and re-create it, but there’s no way of knowing it’s name in words except via the Feeds page :roll_eyes:.

Possibly, but the page should load @TrystanLea.

The API call is;

http://x.x.x.x/feed/delete.json?id=175

Thanks for all of the help. I have managed to fix it using ChatGPT - It was indeed something to do with feed 175 but an indirect use of it that was causing the browser to crash with a Javascript problem (I think). I certainly wouldn’t have found it my myself and it took a long hour back and forward with ChatGPT trying various things but a manual edit of the SQL database in the end was required to remove the offending entry. What really puzzles me is how did it happen in the first place. All I did was a small update to a feed and it all went wrong.

Carl

I perhaps didn’t make my initial post that clear. The feeds page had headers and footers but all buttons were greyed out. As far as I can tell the browser started to render the page then crashed and nothing more was added.