@glyn.hudson When I log on I appear to be logging to an account in the cloud. Is there a way that I can log onto the local system. The HP Monitor was installed by Octopus (EOS45) but they are not interested in any output. In fact, the last time I spoke to them, no one appeared to know that the item was installed and no one ever monitors it. Because of this, there appears no way that I can get someone at Octopus to agree transfer of the local system to me.
You’ll need to find the IP address of the emonpi on your network (you should be able to find this from your router or wireless access point). Once you’ve got that, in your browser head to:
http://{emonpi-ip-address}
Then try logging in with the default emonpi username and password: emonCMS: Getting started emonPi/Base — OpenEnergyMonitor 0.0.1 documentation
I’m pretty sure Octopus hadn’t changed these when they installed the kit alongside my heat pump.
Log on to what URL/Website?
When I check my data for the heat pump I use: https://emoncms.org/app/view?name=MyHeatpump&readkey This I am assuming is logging onto my account on the cloud.
I want to log into the HP Monitor locally ( the Pi fitted to the product) which would save be depending on the internet.
Correct.
No, that won’t work (or, it should not work). The heatpump monitor emonCMS has a different set of credentials, these should have come to you as a printed sheet with the goods.
@dmhom
Look out for a PM shortly.
The monitors that myself and I presume @dmhom had fitted were bought and installed by Octopus Energy Services, they didn’t provide a printout of the login details for the system(for me at least). Interestingly they also didn’t inform me that they were installing the system or ask my permission to gather this data, which is a cavalier approach to privacy for sure.
On balance, I’m happier that the system was installed and that I’ve now got access to it to monitor my heat pump installation than I am annoyed/concerned that they installed the system without regard for my consent.
I followed the path I laid out above to get access to the emonpi device (labelled OES31). I’ve since changed the local login account but have left the sync to emoncms so if somebody at Octopus is still monitoring these systems, they are still receiving data from my system.
I have no knowledge of either your or Megi’s contracts with Octopus, however it will be within Trystan or Glyn’s power to change your API key and forbid their access to your data.
I would not worry too much. On the last visit of an engineer, I spoke to him a couple of days before he visited and asked him to check the data Octopus was receiving from my emoncms setup. He advised me, after checking within Octopus, that no one had any knowledge of my system. I am surprised that they installed a system without advising you. They only installed mine after I had been complaining the HP was not working correctly.