# Bad data in emonESP transmission

**URL:** <https://community.openenergymonitor.org/t/bad-data-in-emonesp-transmission/22701>\
**Category:** emonESP\
**Tags:** emontx\
**Created:** [30 January 2023 19:54 UTC](https://community.openenergymonitor.org/t/bad-data-in-emonesp-transmission/22701 "2023-01-30T19:54:35Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Roberto\_Zanasi](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/roberto_zanasi/32/15553_2.png) [@Roberto\_Zanasi](https://community.openenergymonitor.org/u/Roberto_Zanasi)\
**Post date:** [30 January 2023 19:54 UTC](https://community.openenergymonitor.org/t/bad-data-in-emonesp-transmission/22701/1 "2023-01-30T19:54:35Z")

</div>

I use an emonTX with emonESP wifi antenna to send data to my emonPI. Yesterday the data transmission stopped; I looked at the inputs list and the logs and I found a lot of bad data and bad inputs.

I think that the problems lies in how emonESP transmits data: these are some lines of its log file:

```auto
|2023-01-30T19:44:28.142Z|{MSG:2305,Vrms:261.12,P1:4,E1:22,pulse:1,freeram:29216,srssi:-22,psent:6,psuccess:0}|
|---|---|
|2023-01-30T19:44:46.130Z|{MSG:2306,Vrms:261.39,P1:5,E1:22,pulse:1,freeram:28824,srssi:-22,psent:7,psuccess:0}|
|2023-01-30T19:45:04.126Z|{32,P1:5,E1:22,pulse:1,freeram:29016,srssi:-22,psent:8,psuccess:0}|
|2023-01-30T19:45:22.113Z|{pulse:1,freeram:29272,srssi:-22,psent:9,psuccess:0}|
|2023-01-30T19:45:40.128Z|{2,pulse:1,freeram:29056,srssi:-22,psent:10,psuccess:0}|
|2023-01-30T19:45:58.113Z|{pulse:1,freeram:29032,srssi:-22,psent:11,psuccess:0}|
|2023-01-30T19:46:16.121Z|{E1:22,pulse:1,freeram:29072,srssi:-22,psent:12,psuccess:0}|
|2023-01-30T19:46:34.949Z|{.56,P1:5,E1:22,pulse:1,freeram:29000,srssi:-22,psent:13,psuccess:0}|

```

Besides, data are not sent to [emoncms.org](http://emoncms.org).

What can I do to fix the problem?

---

<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:** [30 January 2023 22:25 UTC](https://community.openenergymonitor.org/t/bad-data-in-emonesp-transmission/22701/2 "2023-01-30T22:25:54Z")

</div>

> [@Roberto\_Zanasi](#):
>
> What can I do to fix the problem?

What have you tried? Reboot?

Has anything else changed/happened? Powercut?

---

<div class="post-metadata">

**Author:** ![Roberto\_Zanasi](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/roberto_zanasi/32/15553_2.png) [@Roberto\_Zanasi](https://community.openenergymonitor.org/u/Roberto_Zanasi)\
**Post date:** [30 January 2023 22:30 UTC](https://community.openenergymonitor.org/t/bad-data-in-emonesp-transmission/22701/3 "2023-01-30T22:30:55Z")

</div>

> [@borpin](#):
>
> What have you tried? Reboot?
> 
> Has anything else changed/happened? Powercut?

I rebooted the emonPI and the emonTX: nothing changed. I deleted the spurious entries in emonCMS inputs list, but eventually they were recreated.

---

<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:** [31 January 2023 13:29 UTC](https://community.openenergymonitor.org/t/bad-data-in-emonesp-transmission/22701/4 "2023-01-31T13:29:22Z")

</div>

> [@Roberto\_Zanasi](#):
>
> I rebooted the emonPI and the emonTX

Did you completely power down the TX and Pi? i.e. remove all power (and the 9V supply)?

---

<div class="post-metadata">

**Author:** ![Roberto\_Zanasi](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/roberto_zanasi/32/15553_2.png) [@Roberto\_Zanasi](https://community.openenergymonitor.org/u/Roberto_Zanasi)\
**Post date:** [31 January 2023 15:17 UTC](https://community.openenergymonitor.org/t/bad-data-in-emonesp-transmission/22701/5 "2023-01-31T15:17:35Z")

</div>

> [@borpin](#):
>
> Did you completely power down the TX and Pi? i.e. remove all power (and the 9V supply)?

Yes, completely.

---

<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:** [31 January 2023 17:54 UTC](https://community.openenergymonitor.org/t/bad-data-in-emonesp-transmission/22701/6 "2023-01-31T17:54:53Z")

</div>

Odd that it should have started misbehaving. The emonESP man is @glyn.hudson .

> [@Roberto\_Zanasi](#):
>
> these are some lines of its log file:

This is the log on the emonESP?

---

<div class="post-metadata">

**Author:** ![Roberto\_Zanasi](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/roberto_zanasi/32/15553_2.png) [@Roberto\_Zanasi](https://community.openenergymonitor.org/u/Roberto_Zanasi)\
**Post date:** [31 January 2023 21:12 UTC](https://community.openenergymonitor.org/t/bad-data-in-emonesp-transmission/22701/7 "2023-01-31T21:12:57Z")

</div>

> [@borpin](#):
>
> This is the log on the emonESP?

Yes, copied from the emonESP web interface.

---

<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:** [31 January 2023 21:19 UTC](https://community.openenergymonitor.org/t/bad-data-in-emonesp-transmission/22701/8 "2023-01-31T21:19:50Z")

</div>

Sorry, I don’t have any solution.
