My install is local, I have MQTT messages working and openevse is passing the data along with messages going out.
I installed demandshaper as instructed but don’t seem to get it working at all, the on/off/smart/time tab does nothing and i get an odd error like a route problem, although dashboards/apps all work.
Also the box for selecting a demand shaper signal is blank
As i run it on my own install i decided to create the pi directory and give www-data permissions and put the demandshaper directory in there and this seems to fix it as much as i now get the graph and options for demand signal etc.
But at the top it says openevse unresponsive, so now working on what that means? and where to find the problem.
I suggest your best route may be to export your data and start afresh. If you don’t want to use the EmonSD image, you can do an install using the EmonScripts. This then puts everything where EmonCMS expects to find them.
You can also edit the config and install just what you want.
Thanks for the reply, but this problem seems related to the demandshaper module, you can read the install instructions says to put it in /home/pi but for people who don’t use the emonpi it’s not correct but do think something is hardcoded, i need to try work that out.
I’d rather understand where and what is going wrong really but also think reporting my findings will help others.
Do appreciate your reply though and if i only had emoncms on the pc it might be an option but it’s a Intel NUC running Domoticz and other stuff and don’t want to really start breaking it all.
If available can you click on the button Copy as Markdown next to Server Information on the Admin page and paste here please (no further formatting required).
However, I suspect your issue may be that service-runner is not running and I think Demand Shaper requires it (I could be wrong).
The scripts work quite well on a clean Ubuntu - check my post on the subject - and you can select what to install, so for instance, just the mosquitto client and not the server if it is already installed and configured. However, there has never been an ‘uninstall’ done first .
So as to finish this post off with what I found. My install might not quite be right and had to manually create the pi dir in home to emulate it being on the raspberry pi, this i think is down to a setting somewhere for the path to find the files which i will find but my workaround got the front-end actually to respond.
I then had an issue with it saying unresponsive next to openevse after a few seconds, this turn out to be a problem with a setting on the openevse mqtt setup, i had it set to just openevse on the base topic as it suggest in the gui, changing this to emon/openevse fixed the response and now scheduling is working.