I would have thought that would crash the page entirely, as the json string might not parse?
Interesting that you get it on a numerical node… I wonder if it might be the javascript getting in a mix as to whether its a associative array or a index…
If that’s the case this might help? but probably not for @ian as the OpenEvse nodeid is definetly a string already…
I don’t know if it might be significant but 2 days ago I got the “maximum inputs reached, input ??? Ignored”
I immediately edited settings to raise limit from 32 to 64.
LAST ENTRIES ON THE LOG FILE
Starting update via service-runner-update.sh (v3.0) >
- emonSD version: emonSD-17Oct19
- supported images: emonSD-24Jul20 emonSD-02Oct19 emonSD-17Oct19
- emonSD base image check passed...continue update
git pull /opt/openenergymonitor/EmonScripts
master
* stable
On branch stable
Your branch is up to date with 'origin/stable'.
nothing to commit, working tree clean
Already up to date.
-------------------------------------------------------------
Main Update Script
-------------------------------------------------------------
Date: Tue 15 Sep 19:53:09 BST 2020
EUID: 1000
openenergymonitor_dir: /opt/openenergymonitor
type: emoncms
firmware: none
Hardware detected: rfm2pi
Start emoncms update:
-------------------------------------------------------------
Update Emoncms Core
-------------------------------------------------------------
Checking status of /var/www/emoncms git repository
- git branch: stable
- no local changes
- running: git pull origin stable
Fetching origin
From https://github.com/emoncms/emoncms
f781bed0..7124d6e0 master -> origin/master
From https://github.com/emoncms/emoncms
* branch stable -> FETCH_HEAD
Already up to date.
The last update had a number of changes in demandshaper.
This morning I went into demandshaper and only 2 devices were showing called Default but http://192.168.1.22/demandshaper/clearall restored them to original names.
OpenEVSE has now disappeared from the list of devices.
Thanks @ian, has that made any difference to the input list? I imagine you are seeing the same error?
Device module looks up to date in the log, so that’s fine.
Difficult to see any changes on the input list with the error popping up so quickly I cannot scroll completely down the list.
As a last resort I have just upgraded to emonSD-24Jul20 (Stable) image.
USB import worked perfectly.
Bad news is the problem remains when I switch to inputs page!
There was an error creating device: nodeid=openevse message=Device already exists
And as I reported in an earlier post OpenEVSE disappeared from Demandshaper although that may be the result of the demandshaper updates I pulled in on the last update.
Should I now try all the delete methods I tried before? I haven’t taken any action so far in case there is any reports I can obtain and post to help track the issue.
Also what process should I follow to get OpenEVSE into demandshaper? Again I have done nothing since switching to the latest image apart from running an update.
LAST ENTRIES ON THE LOG FILE
Starting update via service-runner-update.sh (v3.0) >
- emonSD version: emonSD-24Jul20
- supported images: emonSD-24Jul20 emonSD-02Oct19 emonSD-17Oct19
- emonSD base image check passed...continue update
git pull /opt/openenergymonitor/EmonScripts
master
* stable
On branch stable
Your branch is up to date with 'origin/stable'.
nothing to commit, working tree clean
Already up to date.
-------------------------------------------------------------
Main Update Script
-------------------------------------------------------------
Date: Wed 16 Sep 16:13:37 BST 2020
EUID: 1000
openenergymonitor_dir: /opt/openenergymonitor
type: emoncms
firmware: none
Hardware detected: rfm2pi
Start emoncms update:
-------------------------------------------------------------
Update Emoncms Core
-------------------------------------------------------------
Checking status of /var/www/emoncms git repository
- git branch: stable
- no local changes
- running: git pull origin stable
Fetching origin
From https://github.com/emoncms/emoncms
* branch stable -> FETCH_HEAD
Already up to date.
From https://github.com/emoncms/demandshaper
c20a456..bcfb1ff master -> origin/master
Already up to date.
Already on 'stable'
Your branch is up to date with 'origin/stable'.
I think I’ve found what’s causing the issue, I think it’s a capitalisation issue, If you have a device in the device list that is capitalised differently from the nodeid in the input list it’s causing this error, I’ve just been able to replicate it here.
Can you check if there is a device called openevse with different capitalisation on the hidden device page:
/device/view
If there is, you can delete it from there safely without affecting your inputs.
Great, you need to select the OpenEVSE device template by clicking on the cog icon on the inputs page, see screenshots in the guide here Smart Charge your Electric Vehicle - Guide | OpenEnergyMonitor. You dont need to initialize at the end, just save and then cancel
Do you have the OpenEvse configured to send data to emoncms using both the HTTP (Energy Monitoring: Enable Emoncms) and MQTT? I see that its a bit confusing, the MQTT actually replaces that other route…
The emonpi was set up by someone else previously and I have limited understanding on how they set the inputs up etc. I noticed that there is an input tab called msgMbus that hasn’t got any inputs attached to it. Could this be the issue? Would deleting this solve the issue?
At the moment the inputs are getting readings and I am able to create new feeds. However, is a very time consuming process as the message keeps popping up. I would like to try solve this issue however I am worried I will loose data/ data will not be plotted in the apps for a while since my project relies on these readings.
Thank you in advance for your help!
Hello @Rolop it looks like this is a bug being created by having two nodes with similar names, the first called msgMBus and the second msg.MBus. I’ve now fixed this error in the device module, are you able to update the system via the updater on the admin page?
I can only log into emoncms.org as I only have remote access, is there any way to update through remote access? Would the error get fixed if I delete the input msgMbus?
Otherwise I will try to get someone to access emoncms locally.