# Reboot and EmonHub complaints formatting errors **URL:** \ **Category:** emonPi\ **Tags:** emonpi, emonhub\ **Created:** [24 December 2022 11:46 UTC](https://community.openenergymonitor.org/t/reboot-and-emonhub-complaints-formatting-errors/22255 "2022-12-24T11:46:18Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Tagware](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/tagware/32/17731_2.png) [@Tagware](https://community.openenergymonitor.org/u/Tagware)\ **Post date:** [24 December 2022 11:46 UTC](https://community.openenergymonitor.org/t/reboot-and-emonhub-complaints-formatting-errors/22255/1 "2022-12-24T11:46:18Z")
Hi All, EMONPI setup on PI W Zero on with your board & PSU for feed to board. The Solar 2 setup with setup as on diagram. Emoncms Core v11.2.9 | App v2.6.8 | EmonHub Config v2.1.5 | Dashboard v2.3.3 | Device v2.2.2 | Graph v2.2.3 | Network Setup v1.0.2 | WiFi v2.1.1 | Backup v2.3.2 | DemandShaper v2.2.2 | Postprocess v2.2.7 | Sync v2.1.4 | Usefulscripts v2.3.10 | EmonScripts v1.5.14 | RFM2Pi v1.4.1 | Emonhub v2.5.2 | EmonPi v2.9.5 Which, was working for couple of years until I had to reboot the system yesterday and since lost all input feeds? As the EmonHub is stopped. I looked at the Serial feed and got this back in the console. ```auto OK 5 64 1 214 0 22 2 26 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 151 170 2 0 29 93 0 0 (-0) ``` So, it seems that I haven’t killed the daughter board. However, I’m getting an error on as below; ```auto 2022-12-24 11:33:36,167 WARNING RFM2Pi 14 RX data length: 36 is not valid for datacodes ['h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'L'] ``` I don’t know what I touched? It’s obviously not happy with the input string. Not certain how to fix this issue? Do I need to reflash the firmware? Help please! Cheers David. ---
**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:** [26 December 2022 14:04 UTC](https://community.openenergymonitor.org/t/reboot-and-emonhub-complaints-formatting-errors/22255/2 "2022-12-26T14:04:12Z")
> [@Tagware](#): > > EMONPI setup on PI W Zero EmonPi is a specific piece of hardware. Do you mean an emonSD on a PiZero (so emoncms and emonhub)? > [@Tagware](#): > > So, it seems that I haven’t killed the daughter board. Do you mean the OEM RFM board? > [@Tagware](#): > > As the EmonHub is stopped. Why is it stopped or do you mean you stopped it to read the serial data? Try a full update, but check the update log for errors. ---
**Author:** ![Tagware](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/tagware/32/17731_2.png) [@Tagware](https://community.openenergymonitor.org/u/Tagware)\ **Post date:** [27 December 2022 10:46 UTC](https://community.openenergymonitor.org/t/reboot-and-emonhub-complaints-formatting-errors/22255/3 "2022-12-27T10:46:16Z")
The error was in the message? Versions were current? Firmware is not loaded on F/Update ---
**Author:** ![Tagware](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/tagware/32/17731_2.png) [@Tagware](https://community.openenergymonitor.org/u/Tagware)\ **Post date:** [11 January 2023 11:43 UTC](https://community.openenergymonitor.org/t/reboot-and-emonhub-complaints-formatting-errors/22255/4 "2023-01-11T11:43:25Z")
Did that and nothing has changed. 🤔 Anyone else got any ideas? ---
**Author:** ![Tagware](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/tagware/32/17731_2.png) [@Tagware](https://community.openenergymonitor.org/u/Tagware)\ **Post date:** [11 January 2023 11:58 UTC](https://community.openenergymonitor.org/t/reboot-and-emonhub-complaints-formatting-errors/22255/5 "2023-01-11T11:58:30Z")
When in the stream in Minicom I press ‘v’ and this comes back ‘emonPi CM V1.0.0’ it’s working but sending more values than is expected back? ---
**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:** [11 January 2023 20:52 UTC](https://community.openenergymonitor.org/t/reboot-and-emonhub-complaints-formatting-errors/22255/6 "2023-01-11T20:52:00Z")
@Robert.Wall any ideas? ---
**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:** [11 January 2023 21:34 UTC](https://community.openenergymonitor.org/t/reboot-and-emonhub-complaints-formatting-errors/22255/7 "2023-01-11T21:34:49Z")
> [@Tagware](#): > > I don’t know what I touched? > [@Tagware](#): > > So, it seems that I haven’t killed the daughter board. What is this daughter board you refer to? > [@Tagware](#): > > I’m getting an error on as below; This means that the specification for the message in emonhub.conf doesn’t fit the data stream that’s arriving. 10 ‘h’ @ 2 bytes + 1 ‘L’ @ 4 bytes isn’t the same as the 36 bytes coming in. 24 bytes is the number for a standard emonPi sketch, as far as I know. The software for the emonPiCM sends 32 bytes, so it isn’t that either. My guesses are you’ve overwritten your old, working, emonhub.conf; or you’ve got a new sketch in Node 5 - which is normally the emonPi analogue front end. Now I don’t have a message of 36 bytes on my crib sheet of radio messages, so I don’t know where it’s coming from.