No it is not an apt package.
You are in the /var/www/emoncms/Modules/dashboard folder? To check you can used to command pwd
No it is not an apt package.
You are in the /var/www/emoncms/Modules/dashboard folder? To check you can used to command pwd
Sorry, there must be no difference which makes the earlier message odd.
So,
rpi-rw
cd /var/www/emoncms/Modules/dashboard
sudo git reset --hard
then
sudo git pull
I am making progress, but really slow:
I followed the instructions and was asked by RPi to git config my email address and name which I did.
So output from
sudo git pull
pi@emonpi(rw):dashboard$ sudo git pull
Auto-merging widget/sun/sun_render.js
CONFLICT (content): Merge conflict in widget/sun/sun_render.js
Auto-merging widget/signal/signal_render.js
CONFLICT (content): Merge conflict in widget/signal/signal_render.js
Auto-merging widget/humidex/humidex_render.js
Auto-merging widget/heatindex/heatindex_render.js
Auto-merging widget/frostpoint/frostpoint_render.js
Auto-merging widget/feedvalue/feedvalue_render.js
CONFLICT (content): Merge conflict in widget/feedvalue/feedvalue_render.js
Auto-merging widget/dial/dial_render.js
CONFLICT (content): Merge conflict in widget/dial/dial_render.js
Auto-merging widget/dewpoint/dewpoint_render.js
Auto-merging widget/battery/battery_render.js
CONFLICT (content): Merge conflict in widget/battery/battery_render.js
Auto-merging widget/bar/bar_render.js
CONFLICT (content): Merge conflict in widget/bar/bar_render.js
Auto-merging module.json
CONFLICT (add/add): Merge conflict in module.json
Auto-merging dashboard_langjs.php
CONFLICT (content): Merge conflict in dashboard_langjs.php
Auto-merging Views/dashboard_edit_view.php
Automatic merge failed; fix conflicts and then commit the result.
Thanks for helping me, I do appreciate it
It seems to me the repository is really out of sorts.
Try this to get things back to where they should be.
git fetch origin
git reset --hard origin/stable
git clean -f -d
git status
From within this directory?
/var/www/emoncms/Modules/dashboard
pi@emonpi(ro):dashboard$ pwd
/var/www/emoncms/Modules/dashboard
pi@emonpi(ro):dashboard$ rpi-rw
Filesystem is unlocked - Write access
type ā rpi-ro ā to lock
pi@emonpi(rw):dashboard$ git fetch origin
pi@emonpi(rw):dashboard$ git reset --hard origin/stable
HEAD is now at 9b03e57 Merge pull request #173 from emoncms/master
pi@emonpi(rw):dashboard$ git clean -f -d
pi@emonpi(rw):dashboard$ git status
On branch stable
Your branch is up-to-date with āorigin/stableā.
nothing to commit, working directory clean
THANKS IT WORKS!!!
Thanks a lot Brian and Bill!!
I really appreciate it very much
Something is still wrong:
I was able to add two dials and saved but only one dial shows.
Also look at the Toolbox icons.
I rebooted the emonPI via Admin page, and this is a screenshot after the reboot.
After I created a few dials with headers.
Save: appears to work.
BUT when I click on the eye icon to exit edit:
And when I then click anywhere else:
I also get this error: Perhaps it is a clue-

Have you cleared the browser cache since fixing the git repo?
Are you now trying to create a new dash or trying to regain access to a dashboard that ceased to render as described in your first posts?
Paul:
A error message flashed and I could not copy it; saying I should; Update the emonDatabase
So I did a āemonBase Updateā and it seems everything is now working correct.
BTW: I was creating a new dashboard and have not cleared the cache.
Just to be safe I will do it now and then create a few new dashboards and give feedback
Thanks for your patience and help!!!
Thatās good!
For future reference. The message to update the database just means to do a ācheck and updateā via the button on the admin page.
By doing a full emonpi update the database check and update is done as part of that at the tail end, thatās why doing a full update worked.
Problem solved.
thank you very much Paul for all your help.
I really appreciate it very much.
Thanks Brian also for your help. Much appreciated.
Should I now submit a ārpi-roā command to wrap everything up?
Frits
Yes that is best.
If I remember correctly, thereās a ātime-outā associated with the rpi-rw command.
i.e. if nothing is done, after a few miutes (Iām not sure of the exact number) the filesystem
goes back to ro mode.
Yes, once every hour the OS is returned to RO, so it could be anywhere between 0 and 60mins.
(the latest image isnāt read-only though so this does only applies to earlier images).
Tnx PB.
I couldnāt remember the number.
Itās been almost 3 years since Iāve run emonCMS. Iām surprised I remembered it at all. ![]()
Thanks for your help!!
Just as a tidy up - what appeared to work as the repository was out of sync as reported by git status
cd /var/www/emoncms/Modules/dashboard
rpi-rw
git fetch origin
git reset --hard origin/stable
git clean -f -d
git status
rpi-ro
Then do a database update from the admin screen.
Thanks Brian:
Just in case some else wants to see the responses from emonPi:
pi@emonpi(ro):dashboard$ pwd
/var/www/emoncms/Modules/dashboard
pi@emonpi(ro):dashboard$ rpi-rw
Filesystem is unlocked - Write access
type ' rpi-ro ' to lock
pi@emonpi(rw):dashboard$ git fetch origin
pi@emonpi(rw):dashboard$ git reset --hard origin/stable
HEAD is now at 9b03e57 Merge pull request #173 from emoncms/master
pi@emonpi(rw):dashboard$ git clean -f -d
pi@emonpi(rw):dashboard$ git status
On branch stable
Your branch is up-to-date with 'origin/stable'.
nothing to commit, working directory clean
pi@emonpi(rw):dashboard$ rpi-ro
Filesystem is locked - Read Only access
type ' rpi-rw ' to unlock
pi@emonpi(ro):dashboard$