No I haven’t but I’ve just tried and it works, thank you man!
Those 2 lines have been in emoncms since May 2017 (v9.8.6), if they were not there for you, you are not running the updated/latest version. If you believe you were, then you should check for local changes that may be blocking the previous updates, just as this edit will block future updates.
That was specifically why I asked
I’m actually (and I was) on 9.3.8, the fix on 9.8.6 worked correctly at that time for this issue…I sincerly don’t know what happened after that. I haven’t blocked anything on purpose and I haven’t manually edited anything before.
hi @pb66, I write this just to inform you that after an update (emonbase update) I’m facing this issue again…I suppose I need to edit that file to fix it…
It looks like the previous fix has been removed again in a later commit.
I have submitted a PR for consideration, but it’s untested as I’m not able to recreate the issue. Perhaps you could test by manually adding a line as done previously, but in a different place as the code is different now.
Please let us know if it works, perhaps @TrystanLea can review the change.
If you just stumbled here from google like I did, and you JUST installed emoncms, if your emoncms database is a new database and no inputs or devices are yet configured. Then this will happen to you as well.
The solution is to Goto Admin, click the drop down arrow next to Full Update, and next click Update Database Only.
It will create the necessary tables in your new database.
How did you do the install? The last thing EmonScript does is run that exact command so the database should be there ready.
I seen that the official install method was to install it so that the user can issue sudo without password, didnt really like that so I followed this one:
That guide is not a complete step by step but I know enough about Linux to make that install method work. I can write up a short guide later.
This is only for instances where you are using a ‘Shared Hosting’ environment i.e. not on your own machine/RPi etc.
I’m not surprised it doesn’t work.
What hardware are you using?
Not to mention that a “paswordless sudo” is easy to change to a “password required” sudo.
A small change to one line in /etc/sudoers is all that’s necessary.
Yes you could always change it back.
I will admit it is a bit of a hack but within a home network does not pose any real risk. If you use Raspbian, this is how the default user is setup, hence the change for other Debian distros.
If someone with more knowledge than me would like to suggest modifications to the scripts such that sudo is not needed on Debian (but still works with Raspbian) we’d be open to exploring that.
I have everything working good now 
I am using an Arduino Due. emoncms is running on a server with Ubuntu 18.04.
Apologies for resurrecting such an old thread but it looked like this is exactly the issue I’m facing.
I had the rpi eat an SD card so did a fresh re-install from emonSD-24Jul20.img on a new SD card and when trying to set up the inputs it just hangs at “Loading”. I thought maybe I’d done something stupid so since it wasn’t configured just rewrote the image but the same thing happened - the input list will not load.
Looking in the javascript console I see the following error:
vue.min.js:6 ReferenceError: col_h is not defined
at eval (eval at Ya (vue.min.js:1), <anonymous>:3:3920)
at wn.vt [as _l] (vue.min.js:6)
at eval (eval at Ya (vue.min.js:1), <anonymous>:3:2718)
at wn.vt [as _l] (vue.min.js:6)
at wn.eval (eval at Ya (vue.min.js:1), <anonymous>:3:80)
at wn.e._render (vue.min.js:6)
at wn.r (vue.min.js:6)
at fn.get (vue.min.js:6)
at fn.run (vue.min.js:6)
at un (vue.min.js:6)
I found if I had the console open I could catch the error and the rest would render but thought it worth flagging here regardless as this is a fresh install.