# OpenEVSE to emoncms shows "Connected : No" **URL:** \ **Category:** OpenEVSE\ **Created:** [3 August 2019 12:00 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545 "2019-08-03T12:00:50Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![Steven\_Bense](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/steven_bense/32/10274_2.png) [@Steven\_Bense](https://community.openenergymonitor.org/u/Steven_Bense)\ **Post date:** [3 August 2019 12:00 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/1 "2019-08-03T12:00:50Z")
I have entered the settings on the Energy Monitor panel on the Services section on OpenEVSE WiFi. I then registered on [data.openevse.com](http://data.openevse.com), grabbed the write-apikey and tried to save the settings… Connected stays showing “No”. If I enter a random bit of text in the api key field it does say that it is not valid. Checking the requests in Chrome dev tools shows the requests getting sent to the emoncms server. Am I missing something obvious - is there configuration required on the emoncms side. I looked at the video guide on setting up the emoncms - I can’t see any of the openevse data on the inputs section, but if it is not connecting then seems that this would be expected. Any pointers would be appreciated. Thanks. ![openevsetocms](https://community.openenergymonitor.org/uploads/default/original/2X/e/efa13a3000e299f2a80aa17d70f794858fbb26d8.png) ---
**Author:** ![borpin](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/borpin/32/193_2.png) [@borpin](https://community.openenergymonitor.org/u/borpin)\ **Post date:** [4 August 2019 21:26 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/3 "2019-08-04T21:26:10Z")
I don’t know but I suggest you try and take the `/emoncms’ part off the domain name. There is also an Openevse forum [OpenEVSE Forums : Support](https://openev.freshdesk.com/support/discussions/6000055577) ---
**Author:** ![Robert.Wall](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/robert.wall/32/38246_2.png) [@Robert.Wall](https://community.openenergymonitor.org/u/Robert.Wall)\ **Post date:** [4 August 2019 22:02 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/4 "2019-08-04T22:02:18Z")
If Brian’s suggestions go nowhere, I think Glyn will be back at the end of this coming week. ---
**Author:** ![Steven\_Bense](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/steven_bense/32/10274_2.png) [@Steven\_Bense](https://community.openenergymonitor.org/u/Steven_Bense)\ **Post date:** [4 August 2019 22:29 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/5 "2019-08-04T22:29:30Z")
Thanks for the tip on the support desk! I found this [article](https://openev.freshdesk.com/support/discussions/topics/6000057314) The steps needed are as follows: 1. Add a device under the emoncms Device Setup: 2. Initialise the device - this is what was missing! ![2_InitialiseDevice](https://community.openenergymonitor.org/uploads/default/original/2X/a/af9409faded9e674a081b85d5d908eea82a026df.png) The node name of the device is, of course, what is added to the emoncms settings on the OpenEVSE. Once I completed step 1 and 2 above and copied the Device access key to the write-api key setting and saved, it connected immediately. Some confusion on which key to use for the api, as there is one on your profile on emoncms and one for each device you add to emoncms. You have to use the one from the device as mentioned in the linked article. ---
**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\ **Post date:** [6 August 2019 09:59 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/6 "2019-08-06T09:59:49Z")
Glad to hear you got it up and running, did you see our OpenEnergyMonitor specific setup guide: [OpenEVSE / EmonEVSE Setup Guide - Guide | OpenEnergyMonitor](https://guide.openenergymonitor.org/integrations/evse-setup/) ---
**Author:** ![Steven\_Bense](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/steven_bense/32/10274_2.png) [@Steven\_Bense](https://community.openenergymonitor.org/u/Steven_Bense)\ **Post date:** [6 August 2019 19:17 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/7 "2019-08-06T19:17:59Z")
I have watched both videos. There is however a slight disconnect. If you follow the OpenEVSE setup video and then the emonCMS, the actual experience is not quite the same. I appreciate that the videos are based in some instances on the beta version of emoncms. This forum is a wonderful place to share the experiences and help each other out. ---
**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\ **Post date:** [7 August 2019 11:17 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/8 "2019-08-07T11:17:28Z")
Yes, this is because the OpenEnergyMonitor guide uses [Emoncms.org](http://Emoncms.org) instead of data.openevse. [Emoncms.org](http://Emoncms.org) runs a newer version of Emoncm with easier to use setup procedure. ---
**Author:** ![jaygrovr](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/jaygrovr/32/18665_2.png) [@jaygrovr](https://community.openenergymonitor.org/u/jaygrovr)\ **Post date:** [29 May 2021 19:02 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/9 "2021-05-29T19:02:02Z")
Hey guys, no matter what I try I cannot get the API key to be accepted and have the emonevse to connect to [emoncms.org](http://emoncms.org) I tried copying it directly and it still refuses. I am running 4.0.0 on the evse, and I think it has internet access. ---
**Author:** ![jaygrovr](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/jaygrovr/32/18665_2.png) [@jaygrovr](https://community.openenergymonitor.org/u/jaygrovr)\ **Post date:** [29 May 2021 19:07 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/10 "2021-05-29T19:07:53Z")
Nevermind, I was using the wrong API key. .you want the account write key, not the node key. A bit confusing. ---
**Author:** ![salmundo11](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/salmundo11/32/21837_2.png) [@salmundo11](https://community.openenergymonitor.org/u/salmundo11)\ **Post date:** [3 August 2022 01:13 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/11 "2022-08-03T01:13:46Z")
My situation is: OpenEVSE, have had it working with [emoncms.org](http://emoncms.org), just built a local emoncms server. I have created and initialized the device, and had it generate a Device Access Key. I get “Connected: No. Failed to connect”. For the Emoncms server I’m using $HOST\_NAME/emoncms, and the Device Access Key. I’ve also tried the Read & Write Key from the Input API page, and the user account API key. I’m not finding any logging on the Emoncms server, nor on the OpenEVSE, that are useful, so I don’t know how to troubleshoot this, beyond reading all of the support articles that I can find. ![Screen Shot 2022-08-02 at 6.06.48 PM](https://community.openenergymonitor.org/uploads/default/original/3X/e/0/e0260a42a472ffe72c61a7eb5dacb9ca9b247cae.png) ![Screen Shot 2022-08-02 at 6.10.37 PM](https://community.openenergymonitor.org/uploads/default/original/3X/3/7/371a130f1629a9cf895fd714a796d6ca226ca0f2.png) ---
**Author:** ![JJC](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/j/a9adbd/32.png) [@JJC](https://community.openenergymonitor.org/u/JJC)\ **Post date:** [3 August 2022 16:11 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/12 "2022-08-03T16:11:50Z")
Hi, can you ping emonpi.local from a PC on the network? Many routers will not resolve the name in that format. either look at the router’s DHCP list and see if you can ping the name the Pi has registered itself as or do as I have give the Pi a static IP address and then use the IP address in place of the name. John ---
**Author:** ![salmundo11](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/salmundo11/32/21837_2.png) [@salmundo11](https://community.openenergymonitor.org/u/salmundo11)\ **Post date:** [3 August 2022 19:04 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/13 "2022-08-03T19:04:33Z")
Yes, hostname resolves, I have also tried using the IP address in place of the hostname. ---
**Author:** ![JJC](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/j/a9adbd/32.png) [@JJC](https://community.openenergymonitor.org/u/JJC)\ **Post date:** [4 August 2022 09:57 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/14 "2022-08-04T09:57:16Z")
Hi, bit out of ideas now, only other thing you could try is seeing if you enable MQTT and see is that connects to your Pi. John ---
**Author:** ![salmundo11](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/salmundo11/32/21837_2.png) [@salmundo11](https://community.openenergymonitor.org/u/salmundo11)\ **Post date:** [5 August 2022 00:51 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/15 "2022-08-05T00:51:15Z")
Thanks John. No, it will not connect to MQTT on the local server. I’m poking around on the emonpi server to see if there are any logs that would show connectivity errors, not finding anything so far. In reading through the emonpi docs, it seems like once the software is installed and a device configured, there is nothing else that needs doing on the server side? Do you know of any troubleshooting docs for emoncms emonpi? ---
**Author:** ![salmundo11](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/salmundo11/32/21837_2.png) [@salmundo11](https://community.openenergymonitor.org/u/salmundo11)\ **Post date:** [6 August 2022 00:49 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/17 "2022-08-06T00:49:36Z")
After playing around some more, yes, I can get the OpenEVSE to connect to the local emonpi MQTT service. But still no luck connecting to the Emoncms service. ---
**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\ **Post date:** [16 August 2022 09:34 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/18 "2022-08-16T09:34:15Z")
`/emoncms` should not be required in the emonpi hostname try just `emonpi.local` ---
**Author:** ![salmundo11](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/salmundo11/32/21837_2.png) [@salmundo11](https://community.openenergymonitor.org/u/salmundo11)\ **Post date:** [17 August 2022 20:13 UTC](https://community.openenergymonitor.org/t/openevse-to-emoncms-shows-connected-no/11545/19 "2022-08-17T20:13:37Z")
does not work with either emonpi.local, $IP\_ADDR, or $IP\_ADDR/emoncms. Have tried both the user read/write API key and the device API key. Would there be any service logs on the emonpi that would indicate what the issue is?