# Second emonpi on network

**URL:** <https://community.openenergymonitor.org/t/second-emonpi-on-network/21378>\
**Category:** emonSD\
**Created:** [21 September 2022 13:19 UTC](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378 "2022-09-21T13:19:18Z")\
**Posts on this page:** 13\
**Page:** 2

<div class="post-metadata">

**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:** [29 November 2022 17:23 UTC](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378/22 "2022-11-29T17:23:51Z")

</div>

You definitely have the correct API Key (read write), for the right emonpi?

What does the config screen of the working openevse look like?

---

<div class="post-metadata">

**Author:** ![graemetherunner](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/g/d78d45/32.png) [@graemetherunner](https://community.openenergymonitor.org/u/graemetherunner)\
**Post date:** [29 November 2022 18:38 UTC](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378/23 "2022-11-29T18:38:18Z")

</div>

working openevse looks like…

 ![image](https://community.openenergymonitor.org/uploads/default/original/3X/0/0/00054f37ad39d8cfe95c49b6d5704aa9ba973b05.png)

Device key from here… is that correct?

 ![image](https://community.openenergymonitor.org/uploads/default/original/3X/6/5/6519ac876fc16634288819f4e65a1dfe04a30921.png)

---

<div class="post-metadata">

**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:** [29 November 2022 18:43 UTC](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378/24 "2022-11-29T18:43:48Z")

</div>

This is different

![image](https://community.openenergymonitor.org/uploads/default/original/3X/0/c/0c4569edbd20de86a1e6cd908d1edfe679925c80.png)

![image](https://community.openenergymonitor.org/uploads/default/original/3X/d/6/d68e3df7adbd8f8bb8c0fae5d85de990ec25f364.png)

Note the instructions tell you to add the trailing `/emoncms`.

---

<div class="post-metadata">

**Author:** ![graemetherunner](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/g/d78d45/32.png) [@graemetherunner](https://community.openenergymonitor.org/u/graemetherunner)\
**Post date:** [29 November 2022 18:46 UTC](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378/25 "2022-11-29T18:46:00Z")

</div>

yeh, found a thread somewhere when it had been mentioned adding / removing those bits… tried with each variation but no difference…

 ![image](https://community.openenergymonitor.org/uploads/default/original/3X/d/8/d88a506cd9f365b0b9574ef0804e9810611df5e4.png)

---

<div class="post-metadata">

**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:** [29 November 2022 19:07 UTC](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378/26 "2022-11-29T19:07:00Z")

</div>

API key definitely the right RW key?

---

<div class="post-metadata">

**Author:** ![graemetherunner](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/g/d78d45/32.png) [@graemetherunner](https://community.openenergymonitor.org/u/graemetherunner)\
**Post date:** [29 November 2022 19:40 UTC](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378/27 "2022-11-29T19:40:35Z")

</div>

its the device key for the emonevse node?

 ![image](https://community.openenergymonitor.org/uploads/default/original/3X/f/e/fe3534d745ed7bda8df71dd7d37decf696d07e45.png)

---

<div class="post-metadata">

**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:** [29 November 2022 21:10 UTC](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378/28 "2022-11-29T21:10:36Z")

</div>

I don’t think so @glyn.hudson?

Go to ‘My Account’ and selet the read write API Key

![image](https://community.openenergymonitor.org/uploads/default/original/3X/f/b/fb5e5106d151e88afe2a6eb5de489a1abf290c0f.png)

---

<div class="post-metadata">

**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:** [29 November 2022 21:34 UTC](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378/29 "2022-11-29T21:34:54Z")

</div>

> [@borpin](#):
>
> Note the instructions tell you to add the trailing `/emoncms`.

`/emoncms` is not needed. I think the trailing `/` needs to be removed from the IP address

> [@borpin](#):
>
> Go to ‘My Account’ and select the read write API Key

Correct.

---

<div class="post-metadata">

**Author:** ![graemetherunner](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/g/d78d45/32.png) [@graemetherunner](https://community.openenergymonitor.org/u/graemetherunner)\
**Post date:** [1 December 2022 16:39 UTC](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378/30 "2022-12-01T16:39:42Z")

</div>

Thanks both for your assistance. But it’s still not connecting.  
I’ve tried using the my accound read write api key with the ip address with no “/” with “/emoncms” I also tried with “emonpipc/emoncms”

 ![image](https://community.openenergymonitor.org/uploads/default/original/3X/e/2/e2b353b8464e87ad8a9be7988899484ce04b5184.png)

but still “connected no - failed to connect”

 ![image](https://community.openenergymonitor.org/uploads/default/original/3X/8/7/87ebf7111522e83e15653ac6a2cdaf0b178c6dc5.png)

---

<div class="post-metadata">

**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:** [2 December 2022 01:04 UTC](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378/31 "2022-12-02T01:04:17Z")

</div>

That OpenEVSE screenshot shows that MQTT is connected to emonpipc and publishing data on `openevse` topic. If you want data to appear in Emoncms you need to published to `emon/openevse`, see

> **[MQTT](https://guide.openenergymonitor.org/technical/mqtt/)**
>
> emonPi / emonBase MQTT technical guide

---

<div class="post-metadata">

**Author:** ![graemetherunner](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/g/d78d45/32.png) [@graemetherunner](https://community.openenergymonitor.org/u/graemetherunner)\
**Post date:** [2 December 2022 07:51 UTC](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378/32 "2022-12-02T07:51:48Z")

</div>

Thank you the information is now in emonpipc

 ![image](https://community.openenergymonitor.org/uploads/default/original/3X/a/f/af1fe359993e3f27a9568655b55ab801e3bbfc6b.png)  
 ![image](https://community.openenergymonitor.org/uploads/default/original/3X/a/3/a3c5bc9879bb7d4efab518d2e84ff3901da2d914.png)

but now I’m really confused / feeling very silly and emonpipc energy monitoring is still not connecting.  
I followed your video for setting up openevse with emonpi on my first setup… all worked fine… note the pictures below are the original install with no "emon/"openevse

 ![image](https://community.openenergymonitor.org/uploads/default/original/3X/0/2/022bde69720e7aba7552590f4c3b933fcaf39c4a.png)  
 ![image](https://community.openenergymonitor.org/uploads/default/original/3X/8/6/8636a978a4ebb893b339873b612f08c4efd7fade.png)

---

<div class="post-metadata">

**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:** [2 December 2022 09:05 UTC](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378/33 "2022-12-02T09:05:19Z")

</div>

> [@glyn.hudson](#):
>
> If you want data to appear in Emoncms you need to published to `emon/openevse`,

Doesn’t explain why the HTTP interface will not connect.

---

<div class="post-metadata">

**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:** [5 December 2022 17:48 UTC](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378/34 "2022-12-05T17:48:12Z")

</div>

You should use either HTTP or MQTT, they both post the same data it would just be duplicated if you used both posting to the same Emoncms instance. I use MQTT to post to my local emonPi, then HTTP to post to [emoncms.org](http://emoncms.org).

> [@borpin](#):
>
> Doesn’t explain why the HTTP interface will not connect.

Yes, I’ve not seen this before. There must be some sort of local network issue. Nothing should be stopping a direct HTTP connection to an IP address.

[Previous page](https://community.openenergymonitor.org/t/second-emonpi-on-network/21378.md?page=1)
