# Spikes in data **URL:** \ **Category:** Emoncms\ **Created:** [30 December 2022 11:33 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302 "2022-12-30T11:33:40Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Mike\_Henderson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mike_henderson/32/18051_2.png) [@Mike\_Henderson](https://community.openenergymonitor.org/u/Mike_Henderson)\ **Post date:** [30 December 2022 11:33 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/1 "2022-12-30T11:33:41Z")
I need a bit of help tracking down an issue. I’m seeing random spikes in data trends in EmonCMS and I’m having some trouble tracking down the source. They’re not confined to one node but spread across several nodes consisting of EmonTH’s and an emonTXv3. Here is one that showed up this morning on a temperature point coming from an emontx. ![image](https://community.openenergymonitor.org/uploads/default/original/3X/c/5/c5bff17238336318ee8fdb3ed2cef367454dadb2.png) It shows it spiking down to 28.8 degrees which cant really be a true reading. What I cant find by looking on in the emonhub log is the source of the 28.8 deg. A search through the complete log for around that time period doesnt show the 28.8 figure anywhere. These I think are the related data packets for that time period from the node. Temperature T2 from Node 15 is the Boiler Outlet temperature in the trend. ```auto 2022-12-30 10:45:21,674 DEBUG RFM2Pi 6128368 From Node : 15 2022-12-30 10:45:21,674 DEBUG RFM2Pi 6128368 Values : [1144001, 243.3, 0, 0, 0, 2, 0, 0, 0, 85346, 33.25, 35.87, 300, 2884] 2022-12-30 10:45:21,675 DEBUG RFM2Pi 6128368 RSSI : -63 2022-12-30 10:45:21,675 DEBUG RFM2Pi 6128368 Sent to channel(start)' : ToEmonCMS 2022-12-30 10:45:21,676 DEBUG RFM2Pi 6128368 Sent to channel(end)' : ToEmonCMS 2022-12-30 10:45:21,750 DEBUG MQTT Publishing: emon/emontx3cm15/MSG 1144001 2022-12-30 10:45:21,752 DEBUG MQTT Publishing: emon/emontx3cm15/Vrms 243.3 2022-12-30 10:45:21,753 DEBUG MQTT Publishing: emon/emontx3cm15/P1 0 2022-12-30 10:45:21,755 DEBUG MQTT Publishing: emon/emontx3cm15/P2 0 2022-12-30 10:45:21,756 DEBUG MQTT Publishing: emon/emontx3cm15/P3 0 2022-12-30 10:45:21,757 DEBUG MQTT Publishing: emon/emontx3cm15/P4 2 2022-12-30 10:45:21,759 DEBUG MQTT Publishing: emon/emontx3cm15/E1 0 2022-12-30 10:45:21,760 DEBUG MQTT Publishing: emon/emontx3cm15/E2 0 2022-12-30 10:45:21,761 DEBUG MQTT Publishing: emon/emontx3cm15/E3 0 2022-12-30 10:45:21,763 DEBUG MQTT Publishing: emon/emontx3cm15/E4 85346 2022-12-30 10:45:21,764 DEBUG MQTT Publishing: emon/emontx3cm15/T1 33.25 2022-12-30 10:45:21,765 DEBUG MQTT Publishing: emon/emontx3cm15/T2 35.87 2022-12-30 10:45:21,767 DEBUG MQTT Publishing: emon/emontx3cm15/T3 300 2022-12-30 10:45:21,768 DEBUG MQTT Publishing: emon/emontx3cm15/pulse 2884 2022-12-30 10:45:21,769 DEBUG MQTT Publishing: emon/emontx3cm15/rssi -63 2022-12-30 10:45:21,771 INFO MQTT Publishing 'node' formatted msg 2022-12-30 10:45:21,772 DEBUG MQTT Publishing: emonhub/rx/15/values 1144001,243.3,0,0,0,2,0,0,0,85346,33.25,35.87,300,2884,-63 2022-12-30 10:45:31,638 DEBUG RFM2Pi 6128375 From Node : 15 2022-12-30 10:45:31,638 DEBUG RFM2Pi 6128375 Values : [1144002, 243.31, 0, 0, 0, 2, 0, 0, 0, 85346, 33.12, 35.62, 300, 2884] 2022-12-30 10:45:31,639 DEBUG RFM2Pi 6128375 RSSI : -63 2022-12-30 10:45:31,639 DEBUG RFM2Pi 6128375 Sent to channel(start)' : ToEmonCMS 2022-12-30 10:45:31,640 DEBUG RFM2Pi 6128375 Sent to channel(end)' : ToEmonCMS 2022-12-30 10:45:31,823 DEBUG MQTT Publishing: emon/emontx3cm15/MSG 1144002 2022-12-30 10:45:31,825 DEBUG MQTT Publishing: emon/emontx3cm15/Vrms 243.31 2022-12-30 10:45:31,826 DEBUG MQTT Publishing: emon/emontx3cm15/P1 0 2022-12-30 10:45:31,827 DEBUG MQTT Publishing: emon/emontx3cm15/P2 0 2022-12-30 10:45:31,829 DEBUG MQTT Publishing: emon/emontx3cm15/P3 0 2022-12-30 10:45:31,830 DEBUG MQTT Publishing: emon/emontx3cm15/P4 2 2022-12-30 10:45:31,831 DEBUG MQTT Publishing: emon/emontx3cm15/E1 0 2022-12-30 10:45:31,833 DEBUG MQTT Publishing: emon/emontx3cm15/E2 0 2022-12-30 10:45:31,834 DEBUG MQTT Publishing: emon/emontx3cm15/E3 0 2022-12-30 10:45:31,835 DEBUG MQTT Publishing: emon/emontx3cm15/E4 85346 2022-12-30 10:45:31,837 DEBUG MQTT Publishing: emon/emontx3cm15/T1 33.12 2022-12-30 10:45:31,838 DEBUG MQTT Publishing: emon/emontx3cm15/T2 35.62 2022-12-30 10:45:31,839 DEBUG MQTT Publishing: emon/emontx3cm15/T3 300 2022-12-30 10:45:31,840 DEBUG MQTT Publishing: emon/emontx3cm15/pulse 2884 2022-12-30 10:45:31,842 DEBUG MQTT Publishing: emon/emontx3cm15/rssi -63 2022-12-30 10:45:31,844 INFO MQTT Publishing 'node' formatted msg 2022-12-30 10:45:31,844 DEBUG MQTT Publishing: emonhub/rx/15/values 1144002,243.31,0,0,0,2,0,0,0,85346,33.12,35.62,300,2884,-63 2022-12-30 10:45:41,622 DEBUG RFM2Pi 6128382 From Node : 15 2022-12-30 10:45:41,623 DEBUG RFM2Pi 6128382 Values : [1144003, 243.4, 0, 0, 0, 2, 0, 0, 0, 85346, 33, 35.37, 300, 2884] 2022-12-30 10:45:41,623 DEBUG RFM2Pi 6128382 RSSI : -63 2022-12-30 10:45:41,624 DEBUG RFM2Pi 6128382 Sent to channel(start)' : ToEmonCMS 2022-12-30 10:45:41,625 DEBUG RFM2Pi 6128382 Sent to channel(end)' : ToEmonCMS 2022-12-30 10:45:41,834 DEBUG MQTT Publishing: emon/emontx3cm15/MSG 1144003 2022-12-30 10:45:41,836 DEBUG MQTT Publishing: emon/emontx3cm15/Vrms 243.4 2022-12-30 10:45:41,837 DEBUG MQTT Publishing: emon/emontx3cm15/P1 0 2022-12-30 10:45:41,839 DEBUG MQTT Publishing: emon/emontx3cm15/P2 0 2022-12-30 10:45:41,840 DEBUG MQTT Publishing: emon/emontx3cm15/P3 0 2022-12-30 10:45:41,842 DEBUG MQTT Publishing: emon/emontx3cm15/P4 2 2022-12-30 10:45:41,844 DEBUG MQTT Publishing: emon/emontx3cm15/E1 0 2022-12-30 10:45:41,845 DEBUG MQTT Publishing: emon/emontx3cm15/E2 0 2022-12-30 10:45:41,847 DEBUG MQTT Publishing: emon/emontx3cm15/E3 0 2022-12-30 10:45:41,848 DEBUG MQTT Publishing: emon/emontx3cm15/E4 85346 2022-12-30 10:45:41,850 DEBUG MQTT Publishing: emon/emontx3cm15/T1 33 2022-12-30 10:45:41,852 DEBUG MQTT Publishing: emon/emontx3cm15/T2 35.37 2022-12-30 10:45:41,853 DEBUG MQTT Publishing: emon/emontx3cm15/T3 300 2022-12-30 10:45:41,855 DEBUG MQTT Publishing: emon/emontx3cm15/pulse 2884 2022-12-30 10:45:41,857 DEBUG MQTT Publishing: emon/emontx3cm15/rssi -63 2022-12-30 10:45:41,858 INFO MQTT Publishing 'node' formatted msg 2022-12-30 10:45:41,859 DEBUG MQTT Publishing: emonhub/rx/15/values 1144003,243.4,0,0,0,2,0,0,0,85346,33,35.37,300,2884,-63 2022-12-30 10:45:51,599 DEBUG RFM2Pi 6128391 From Node : 15 2022-12-30 10:45:51,600 DEBUG RFM2Pi 6128391 Values : [1144004, 243.51, 0, 0, 0, 2, 0, 0, 0, 85346, 32.87, 35.12, 300, 2884] 2022-12-30 10:45:51,600 DEBUG RFM2Pi 6128391 RSSI : -62 2022-12-30 10:45:51,600 DEBUG RFM2Pi 6128391 Sent to channel(start)' : ToEmonCMS 2022-12-30 10:45:51,600 DEBUG RFM2Pi 6128391 Sent to channel(end)' : ToEmonCMS 2022-12-30 10:45:51,786 DEBUG MQTT Publishing: emon/emontx3cm15/MSG 1144004 2022-12-30 10:45:51,787 DEBUG MQTT Publishing: emon/emontx3cm15/Vrms 243.51 2022-12-30 10:45:51,788 DEBUG MQTT Publishing: emon/emontx3cm15/P1 0 2022-12-30 10:45:51,789 DEBUG MQTT Publishing: emon/emontx3cm15/P2 0 2022-12-30 10:45:51,789 DEBUG MQTT Publishing: emon/emontx3cm15/P3 0 2022-12-30 10:45:51,790 DEBUG MQTT Publishing: emon/emontx3cm15/P4 2 2022-12-30 10:45:51,791 DEBUG MQTT Publishing: emon/emontx3cm15/E1 0 2022-12-30 10:45:51,791 DEBUG MQTT Publishing: emon/emontx3cm15/E2 0 2022-12-30 10:45:51,792 DEBUG MQTT Publishing: emon/emontx3cm15/E3 0 2022-12-30 10:45:51,793 DEBUG MQTT Publishing: emon/emontx3cm15/E4 85346 2022-12-30 10:45:51,793 DEBUG MQTT Publishing: emon/emontx3cm15/T1 32.87 2022-12-30 10:45:51,794 DEBUG MQTT Publishing: emon/emontx3cm15/T2 35.12 2022-12-30 10:45:51,795 DEBUG MQTT Publishing: emon/emontx3cm15/T3 300 2022-12-30 10:45:51,796 DEBUG MQTT Publishing: emon/emontx3cm15/pulse 2884 2022-12-30 10:45:51,796 DEBUG MQTT Publishing: emon/emontx3cm15/rssi -62 2022-12-30 10:45:51,797 INFO MQTT Publishing 'node' formatted msg 2022-12-30 10:45:51,797 DEBUG MQTT Publishing: emonhub/rx/15/values 1144004,243.51,0,0,0,2,0,0,0,85346,32.87,35.12,300,2884,-62 2022-12-30 10:46:01,658 DEBUG RFM2Pi 6128397 From Node : 15 2022-12-30 10:46:01,659 DEBUG RFM2Pi 6128397 Values : [1144005, 243.48000000000002, 0, 0, 0, 2, 0, 0, 0, 85346, 32.87, 35, 300, 2884] 2022-12-30 10:46:01,660 DEBUG RFM2Pi 6128397 RSSI : -63 2022-12-30 10:46:01,660 DEBUG RFM2Pi 6128397 Sent to channel(start)' : ToEmonCMS 2022-12-30 10:46:01,661 DEBUG RFM2Pi 6128397 Sent to channel(end)' : ToEmonCMS 2022-12-30 10:46:01,902 DEBUG MQTT Publishing: emon/emontx3cm15/MSG 1144005 2022-12-30 10:46:01,904 DEBUG MQTT Publishing: emon/emontx3cm15/Vrms 243.48000000000002 2022-12-30 10:46:01,905 DEBUG MQTT Publishing: emon/emontx3cm15/P1 0 2022-12-30 10:46:01,906 DEBUG MQTT Publishing: emon/emontx3cm15/P2 0 2022-12-30 10:46:01,908 DEBUG MQTT Publishing: emon/emontx3cm15/P3 0 2022-12-30 10:46:01,909 DEBUG MQTT Publishing: emon/emontx3cm15/P4 2 2022-12-30 10:46:01,910 DEBUG MQTT Publishing: emon/emontx3cm15/E1 0 2022-12-30 10:46:01,912 DEBUG MQTT Publishing: emon/emontx3cm15/E2 0 2022-12-30 10:46:01,913 DEBUG MQTT Publishing: emon/emontx3cm15/E3 0 2022-12-30 10:46:01,914 DEBUG MQTT Publishing: emon/emontx3cm15/E4 85346 2022-12-30 10:46:01,916 DEBUG MQTT Publishing: emon/emontx3cm15/T1 32.87 2022-12-30 10:46:01,917 DEBUG MQTT Publishing: emon/emontx3cm15/T2 35 2022-12-30 10:46:01,918 DEBUG MQTT Publishing: emon/emontx3cm15/T3 300 2022-12-30 10:46:01,920 DEBUG MQTT Publishing: emon/emontx3cm15/pulse 2884 2022-12-30 10:46:01,922 DEBUG MQTT Publishing: emon/emontx3cm15/rssi -63 2022-12-30 10:46:01,924 INFO MQTT Publishing 'node' formatted msg 2022-12-30 10:46:01,924 DEBUG MQTT Publishing: emonhub/rx/15/values 1144005,243.48000000000002,0,0,0,2,0,0,0,85346,32.87,35,300,2884,-63 ``` any clues where else I can check to see where this value has come from. Am I looking at some imminent failure within the EmonPI hardware? ---
**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:** [30 December 2022 11:51 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/2 "2022-12-30T11:51:07Z")
> [@Mike\_Henderson](#): > > Am I looking at some imminent failure within the EmonPI hardware? I think I’d invest in a new SD card, meanwhile back up your data to another drive. ---
**Author:** ![Mike\_Henderson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mike_henderson/32/18051_2.png) [@Mike\_Henderson](https://community.openenergymonitor.org/u/Mike_Henderson)\ **Post date:** [30 December 2022 11:59 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/3 "2022-12-30T11:59:35Z")
That very thing has been on my mind, and I’ve been running a backup every day for the past week 🙂 Might just order a preinstalled sdcard from the online shop. ---
**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:** [30 December 2022 12:07 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/4 "2022-12-30T12:07:39Z")
Buying a blank card locally and flashing it (Balena Etcher) would be quicker, if you can write SD cards on your computer. I don’t think The Shop will be there until Tuesday. ---
**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 December 2022 19:07 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/5 "2022-12-30T19:07:41Z")
> [@Robert.Wall](#): > > Buying a blank card locally and flashing it (Balena Etcher) would be quicker, if you can write SD cards on your computer. Just to note the shop uses high quality ‘industrial’ cards. ---
**Author:** ![Mike\_Henderson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mike_henderson/32/18051_2.png) [@Mike\_Henderson](https://community.openenergymonitor.org/u/Mike_Henderson)\ **Post date:** [6 January 2023 15:58 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/8 "2023-01-06T15:58:58Z")
Touch wood, replacing the card appears to have stopped the spikes I was seeing across all the feeds. Now was it the card, was it the reboot, or just switching it off and on that did it? Anyway, the card that was replaced was originally an emonSD Industrial - Pre-loaded SD card bought from the online shop back in August 2021. I’m going to put the card through some tests to see if I can pick up any failures. ---
**Author:** ![Gwil](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/gwil/32/29028_2.png) [@Gwil](https://community.openenergymonitor.org/u/Gwil)\ **Post date:** [6 January 2023 17:46 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/9 "2023-01-06T17:46:06Z")
Hi @Mike_Henderson, I work for the Shop. If there is anything amiss with the ‘old’ card, please send me a PM or email the shop - **[support@openenergymonitor.zendesk.com](mailto:support@openenergymonitor.zendesk.com)** - and we will refund the cost of the additional card and shipping. ---
**Author:** ![Mike\_Henderson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mike_henderson/32/18051_2.png) [@Mike\_Henderson](https://community.openenergymonitor.org/u/Mike_Henderson)\ **Post date:** [23 February 2023 09:53 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/10 "2023-02-23T09:53:36Z")
This appears to have returned again. This morning I’m seeing spikes in the data which don’t agree with the emonhub log file again. When this last appeared the SD card was changed. Could it just have been the power cycling of the EmonPI that cleared the issue when the card was changed? I’ve seen one spike on an EmonTH early this morning and the spike on this 2nd EmonTH later on. Any thoughts on whats causing this? ![image](https://community.openenergymonitor.org/uploads/default/original/3X/e/a/ea10ca99b703cec89ad42bc1b00b9151358fa822.png) ![image](https://community.openenergymonitor.org/uploads/default/original/3X/f/1/f13d2d74375408f369ed0c5fd792bdd846f8fd45.png) ```auto 2023-02-23 08:59:52,316 DEBUG RFM2Pi 2314967 NEW FRAME : OK 28 152 0 236 1 93 2 239 1 108 2 208 1 26 0 1 0 0 0 (-49) 2023-02-23 08:59:52,319 DEBUG RFM2Pi 2314967 Timestamp : 1677142792.316541 2023-02-23 08:59:52,320 DEBUG RFM2Pi 2314967 From Node : 28 2023-02-23 08:59:52,320 DEBUG RFM2Pi 2314967 Values : [15.200000000000001, 49.2, 60.5, 49.5, 62, 46.400000000000006, 2.6, 1] 2023-02-23 08:59:52,321 DEBUG RFM2Pi 2314967 RSSI : -49 2023-02-23 08:59:52,321 DEBUG RFM2Pi 2314967 Sent to channel(start)' : ToEmonCMS 2023-02-23 08:59:52,322 DEBUG RFM2Pi 2314967 Sent to channel(end)' : ToEmonCMS 2023-02-23 08:59:52,555 DEBUG MQTT Publishing: emon/emonth10/temperature 15.200000000000001 2023-02-23 08:59:52,556 DEBUG MQTT Publishing: emon/emonth10/external temperature1 49.2 2023-02-23 08:59:52,557 DEBUG MQTT Publishing: emon/emonth10/external temperature2 60.5 2023-02-23 08:59:52,558 DEBUG MQTT Publishing: emon/emonth10/external temperature3 49.5 2023-02-23 08:59:52,559 DEBUG MQTT Publishing: emon/emonth10/external temperature4 62 2023-02-23 08:59:52,560 DEBUG MQTT Publishing: emon/emonth10/humidity 46.400000000000006 2023-02-23 08:59:52,560 DEBUG MQTT Publishing: emon/emonth10/battery 2.6 2023-02-23 08:59:52,561 DEBUG MQTT Publishing: emon/emonth10/pulsecount 1 2023-02-23 08:59:52,561 DEBUG MQTT Publishing: emon/emonth10/rssi -49 2023-02-23 08:59:52,563 DEBUG MQTT Publishing: emonhub/rx/28/values 15.200000000000001,49.2,60.5,49.5,62,46.400000000000006,2.6,1,-49 ``` ```auto 2023-02-23 09:00:05,174 DEBUG RFM2Pi 2314980 NEW FRAME : OK 28 152 0 239 1 93 2 239 1 108 2 207 1 26 0 1 0 0 0 (-49) 2023-02-23 09:00:05,176 DEBUG RFM2Pi 2314980 Timestamp : 1677142805.174256 2023-02-23 09:00:05,177 DEBUG RFM2Pi 2314980 From Node : 28 2023-02-23 09:00:05,177 DEBUG RFM2Pi 2314980 Values : [15.200000000000001, 49.5, 60.5, 49.5, 62, 46.300000000000004, 2.6, 1] 2023-02-23 09:00:05,178 DEBUG RFM2Pi 2314980 RSSI : -49 2023-02-23 09:00:05,179 DEBUG RFM2Pi 2314980 Sent to channel(start)' : ToEmonCMS 2023-02-23 09:00:05,179 DEBUG RFM2Pi 2314980 Sent to channel(end)' : ToEmonCMS 2023-02-23 09:00:05,398 DEBUG MQTT Publishing: emon/emonth10/temperature 15.200000000000001 2023-02-23 09:00:05,400 DEBUG MQTT Publishing: emon/emonth10/external temperature1 49.5 2023-02-23 09:00:05,401 DEBUG MQTT Publishing: emon/emonth10/external temperature2 60.5 2023-02-23 09:00:05,403 DEBUG MQTT Publishing: emon/emonth10/external temperature3 49.5 2023-02-23 09:00:05,404 DEBUG MQTT Publishing: emon/emonth10/external temperature4 62 2023-02-23 09:00:05,406 DEBUG MQTT Publishing: emon/emonth10/humidity 46.300000000000004 2023-02-23 09:00:05,407 DEBUG MQTT Publishing: emon/emonth10/battery 2.6 2023-02-23 09:00:05,409 DEBUG MQTT Publishing: emon/emonth10/pulsecount 1 2023-02-23 09:00:05,411 DEBUG MQTT Publishing: emon/emonth10/rssi -49 2023-02-23 09:00:05,412 INFO MQTT Publishing 'node' formatted msg 2023-02-23 09:00:05,413 DEBUG MQTT Publishing: emonhub/rx/28/values 15.200000000000001,49.5,60.5,49.5,62,46.300000000000004,2.6,1,-49 ``` ```auto 2023-02-23 09:00:17,937 DEBUG RFM2Pi 2314986 NEW FRAME : OK 28 152 0 239 1 95 2 241 1 110 2 208 1 26 0 1 0 0 0 (-49) 2023-02-23 09:00:17,938 DEBUG RFM2Pi 2314986 Timestamp : 1677142817.937275 2023-02-23 09:00:17,938 DEBUG RFM2Pi 2314986 From Node : 28 2023-02-23 09:00:17,939 DEBUG RFM2Pi 2314986 Values : [15.200000000000001, 49.5, 60.7, 49.7, 62.2, 46.400000000000006, 2.6, 1] 2023-02-23 09:00:17,939 DEBUG RFM2Pi 2314986 RSSI : -49 2023-02-23 09:00:17,939 DEBUG RFM2Pi 2314986 Sent to channel(start)' : ToEmonCMS 2023-02-23 09:00:17,939 DEBUG RFM2Pi 2314986 Sent to channel(end)' : ToEmonCMS 2023-02-23 09:00:18,035 DEBUG MQTT Publishing: emon/emonth10/temperature 15.200000000000001 2023-02-23 09:00:18,036 DEBUG MQTT Publishing: emon/emonth10/external temperature1 49.5 2023-02-23 09:00:18,037 DEBUG MQTT Publishing: emon/emonth10/external temperature2 60.7 2023-02-23 09:00:18,038 DEBUG MQTT Publishing: emon/emonth10/external temperature3 49.7 2023-02-23 09:00:18,039 DEBUG MQTT Publishing: emon/emonth10/external temperature4 62.2 2023-02-23 09:00:18,039 DEBUG MQTT Publishing: emon/emonth10/humidity 46.400000000000006 2023-02-23 09:00:18,040 DEBUG MQTT Publishing: emon/emonth10/battery 2.6 2023-02-23 09:00:18,041 DEBUG MQTT Publishing: emon/emonth10/pulsecount 1 2023-02-23 09:00:18,042 DEBUG MQTT Publishing: emon/emonth10/rssi -49 2023-02-23 09:00:18,043 INFO MQTT Publishing 'node' formatted msg 2023-02-23 09:00:18,043 DEBUG MQTT Publishing: emonhub/rx/28/values 15.200000000000001,49.5,60.7,49.7,62.2,46.400000000000006,2.6,1,-49 ``` ```auto 2023-02-23 09:00:30,738 DEBUG RFM2Pi 2314997 NEW FRAME : OK 28 152 0 239 1 95 2 241 1 110 2 208 1 26 0 1 0 0 0 (-48) 2023-02-23 09:00:30,740 DEBUG RFM2Pi 2314997 Timestamp : 1677142830.738174 2023-02-23 09:00:30,741 DEBUG RFM2Pi 2314997 From Node : 28 2023-02-23 09:00:30,741 DEBUG RFM2Pi 2314997 Values : [15.200000000000001, 49.5, 60.7, 49.7, 62.2, 46.400000000000006, 2.6, 1] 2023-02-23 09:00:30,742 DEBUG RFM2Pi 2314997 RSSI : -48 2023-02-23 09:00:30,742 DEBUG RFM2Pi 2314997 Sent to channel(start)' : ToEmonCMS 2023-02-23 09:00:30,743 DEBUG RFM2Pi 2314997 Sent to channel(end)' : ToEmonCMS 2023-02-23 09:00:31,026 DEBUG MQTT Publishing: emon/emonth10/temperature 15.200000000000001 2023-02-23 09:00:31,028 DEBUG MQTT Publishing: emon/emonth10/external temperature1 49.5 2023-02-23 09:00:31,029 DEBUG MQTT Publishing: emon/emonth10/external temperature2 60.7 2023-02-23 09:00:31,031 DEBUG MQTT Publishing: emon/emonth10/external temperature3 49.7 2023-02-23 09:00:31,032 DEBUG MQTT Publishing: emon/emonth10/external temperature4 62.2 2023-02-23 09:00:31,033 DEBUG MQTT Publishing: emon/emonth10/humidity 46.400000000000006 2023-02-23 09:00:31,035 DEBUG MQTT Publishing: emon/emonth10/battery 2.6 2023-02-23 09:00:31,036 DEBUG MQTT Publishing: emon/emonth10/pulsecount 1 2023-02-23 09:00:31,038 DEBUG MQTT Publishing: emon/emonth10/rssi -48 2023-02-23 09:00:31,039 INFO MQTT Publishing 'node' formatted msg 2023-02-23 09:00:31,040 DEBUG MQTT Publishing: emonhub/rx/28/values 15.200000000000001,49.5,60.7,49.7,62.2,46.400000000000006,2.6,1,-48 ``` ---
**Author:** ![Mike\_Henderson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mike_henderson/32/18051_2.png) [@Mike\_Henderson](https://community.openenergymonitor.org/u/Mike_Henderson)\ **Post date:** [23 February 2023 11:49 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/11 "2023-02-23T11:49:24Z")
I’ve also noticed that the event occurring around 9.00 am affected more than one node. I see that data from a node measuring solar panel performance in the Shed also spiked at the same time. ![image](https://community.openenergymonitor.org/uploads/default/original/3X/9/1/910d57f440215d6e2148998f902dad28f9164d2c.png) ---
**Author:** ![Mike\_Henderson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mike_henderson/32/18051_2.png) [@Mike\_Henderson](https://community.openenergymonitor.org/u/Mike_Henderson)\ **Post date:** [23 February 2023 16:55 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/12 "2023-02-23T16:55:50Z")
These three feeds spike towards more or less the same value. ![image](https://community.openenergymonitor.org/uploads/default/original/3X/3/8/3845da6ab85dae332dc7e87afa2fe778a9292a26.png) ---
**Author:** ![christian](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/c/b2d939/32.png) [@christian](https://community.openenergymonitor.org/u/christian)\ **Post date:** [23 February 2023 23:10 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/13 "2023-02-23T23:10:37Z")
> [@Mike\_Henderson](#): > > the event occurring around 9.00 am It’s interesting that most seem to have all gone to a value that was in the data, 15.2. I’ve just noticed the “Publishing ‘node’ formatted message” in the debug, which a while ago I saw advice recommending to move to JSON, which I did (and don’t see spikes other than the odd -5.5 where there was a problem reading a temp sensor). This is how I changed my emonhub config: ```auto # Use with emoncms Nodes module node_format_enable = 0 node_format_basetopic = emonhub/ # Single JSON payload published - use with Emoncms MQTT node_JSON_enable = 1 node_JSON_basetopic = emon/ ``` Might be worth a try? ---
**Author:** ![Mike\_Henderson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mike_henderson/32/18051_2.png) [@Mike\_Henderson](https://community.openenergymonitor.org/u/Mike_Henderson)\ **Post date:** [23 February 2023 23:26 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/14 "2023-02-23T23:26:45Z")
Cheers, I’ll have a look at that tomorrow. Mike ---
**Author:** ![Mike\_Henderson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mike_henderson/32/18051_2.png) [@Mike\_Henderson](https://community.openenergymonitor.org/u/Mike_Henderson)\ **Post date:** [24 February 2023 15:07 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/15 "2023-02-24T15:07:11Z")
I’ve not made any changes yet. I’ve been waiting for the issue to show up today and to see if I could see where it’s going wrong. So there was this one a short while ago. What kind of fault would make all three feeds head for the same number? ![image](https://community.openenergymonitor.org/uploads/default/original/3X/9/a/9adc3fdad0e4f807b26f9fe2c3a410d744bc9b74.png) And the emonhub log just doesnt reflect this. ```auto 2023-02-24 14:38:14,465 DEBUG RFM2Pi 2395091 NEW FRAME : OK 28 174 0 11 1 221 1 11 1 236 1 213 1 26 0 1 0 0 0 (-47) 2023-02-24 14:38:14,467 DEBUG RFM2Pi 2395091 Timestamp : 1677249494.464789 2023-02-24 14:38:14,468 DEBUG RFM2Pi 2395091 From Node : 28 2023-02-24 14:38:14,468 DEBUG RFM2Pi 2395091 Values : [17.400000000000002, 26.700000000000003, 47.7, 26.700000000000003, 49.2, 46.900000000000006, 2.6, 1] 2023-02-24 14:38:14,469 DEBUG RFM2Pi 2395091 RSSI : -47 2023-02-24 14:38:14,469 DEBUG RFM2Pi 2395091 Sent to channel(start)' : ToEmonCMS 2023-02-24 14:38:14,470 DEBUG RFM2Pi 2395091 Sent to channel(end)' : ToEmonCMS 2023-02-24 14:38:14,531 DEBUG MQTT Publishing: emon/emonth10/temperature 17.400000000000002 2023-02-24 14:38:14,533 DEBUG MQTT Publishing: emon/emonth10/external temperature1 26.700000000000003 2023-02-24 14:38:14,535 DEBUG MQTT Publishing: emon/emonth10/external temperature2 47.7 2023-02-24 14:38:14,537 DEBUG MQTT Publishing: emon/emonth10/external temperature3 26.700000000000003 2023-02-24 14:38:14,538 DEBUG MQTT Publishing: emon/emonth10/external temperature4 49.2 2023-02-24 14:38:14,540 DEBUG MQTT Publishing: emon/emonth10/humidity 46.900000000000006 2023-02-24 14:38:14,541 DEBUG MQTT Publishing: emon/emonth10/battery 2.6 2023-02-24 14:38:14,543 DEBUG MQTT Publishing: emon/emonth10/pulsecount 1 2023-02-24 14:38:14,545 DEBUG MQTT Publishing: emon/emonth10/rssi -47 2023-02-24 14:38:14,547 INFO MQTT Publishing 'node' formatted msg 2023-02-24 14:38:14,547 DEBUG MQTT Publishing: emonhub/rx/28/values 17.400000000000002,26.700000000000003,47.7,26.700000000000003,49.2,46.900000000000006,2.6,1,-47 ``` if the mosquitto.log was enabled for debug, might I see something in that? ---
**Author:** ![Mike\_Henderson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mike_henderson/32/18051_2.png) [@Mike\_Henderson](https://community.openenergymonitor.org/u/Mike_Henderson)\ **Post date:** [24 February 2023 15:24 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/16 "2023-02-24T15:24:48Z")
> [@Mike\_Henderson](#): > > `26.700000000000003` Where are all the extra decimal places coming from? NEW FRAME : OK 28 174 0 **11 1** 221 1 11 1 236 1 213 1 26 0 1 0 0 0 (-47) Its just 267 (256+11) divided by 10? Mike ---
**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:** [24 February 2023 15:25 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/17 "2023-02-24T15:25:36Z")
Can you select ‘show missing data’ please. ![image](https://community.openenergymonitor.org/uploads/default/original/3X/1/1/11c6709869ceb134e48a660e048b0db28a58759f.png) > [@christian](#): > > a while ago I saw advice recommending to move to JSON, The advantage of the JSON format, is all values get the same timestamp (you can enable a timestamp value as well). The other thing is to look at the emoncms log at the same point and see what it thinks it received. ---
**Author:** ![Mike\_Henderson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mike_henderson/32/18051_2.png) [@Mike\_Henderson](https://community.openenergymonitor.org/u/Mike_Henderson)\ **Post date:** [24 February 2023 15:28 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/18 "2023-02-24T15:28:02Z")
Thats interesting, never thought about looking at that. ![image](https://community.openenergymonitor.org/uploads/default/original/3X/8/1/81c71d7feb488fdbea6f0bab7b4f33a45841431f.png) ---
**Author:** ![Mike\_Henderson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mike_henderson/32/18051_2.png) [@Mike\_Henderson](https://community.openenergymonitor.org/u/Mike_Henderson)\ **Post date:** [24 February 2023 15:33 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/19 "2023-02-24T15:33:36Z")
> [@borpin](#): > > The other thing is to look at the emoncms log at the same point and see what it thinks it received. My emoncms.log doesn’t show that level of detail. Does it need to be set for debug messages somewhere? ---
**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:** [24 February 2023 15:43 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/20 "2023-02-24T15:43:30Z")
Yes and interestingly nothing in the docs about doing so. ```auto nano /var/www/emoncms/settings.ini ``` ---
**Author:** ![Mike\_Henderson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mike_henderson/32/18051_2.png) [@Mike\_Henderson](https://community.openenergymonitor.org/u/Mike_Henderson)\ **Post date:** [24 February 2023 15:47 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/21 "2023-02-24T15:47:59Z")
> [@borpin](#): > > Yes and interestingly nothing in the docs about doing so. Yes, I hunted down. It’s now set to info and quite a busy logfile now. Waiting for another spike now. ---
**Author:** ![Mike\_Henderson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mike_henderson/32/18051_2.png) [@Mike\_Henderson](https://community.openenergymonitor.org/u/Mike_Henderson)\ **Post date:** [24 February 2023 15:58 UTC](https://community.openenergymonitor.org/t/spikes-in-data/22302/22 "2023-02-24T15:58:56Z")
I more or less understand what I’m seeing detailed in the emoncms.log. Just one thing, what the padding mode or lack of it means? ```auto 2023-02-24 15:57:01.-341|INFO|feed_model.php|post() feedid=21 updatetime=1677254221 feedtime=1677254221 value=628 padding_mode= 2023-02-24 15:57:01.-337|INFO|feed_model.php|post() feedid=528 updatetime=1677254221 feedtime=1677254221 value=385 padding_mode= 2023-02-24 15:57:01.-329|INFO|feed_model.php|post() feedid=22 updatetime=1677254221 feedtime=1677254221 value=10457.244817742 padding_mode=join 2023-02-24 15:57:01.-324|INFO|feed_model.php|post() feedid=469 updatetime=1677254221 feedtime=1677196800 value=5.1505878796894 padding_mode= 2023-02-24 15:57:01.-320|INFO|feed_model.php|post() feedid=23 updatetime=1677254221 feedtime=1677254221 value=474 padding_mode= 2023-02-24 15:57:01.-315|INFO|feed_model.php|post() feedid=24 updatetime=1677254221 feedtime=1677254221 value=5498.5856325348 padding_mode=join 2023-02-24 15:57:01.-310|INFO|feed_model.php|post() feedid=465 updatetime=1677254221 feedtime=1677196800 value=2.4053978951943 padding_mode= ``` [Next page](https://community.openenergymonitor.org/t/spikes-in-data/22302.md?page=2)