# Stange values like 21845 from all sensors **URL:** \ **Category:** Getting Started\ **Tags:** emontx\ **Created:** [17 December 2019 16:00 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764 "2019-12-17T16:00:06Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![emontxv3](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/e/439d5e/32.png) [@emontxv3](https://community.openenergymonitor.org/u/emontxv3)\ **Post date:** [17 December 2019 16:00 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/1 "2019-12-17T16:00:06Z")
I installed a second emontx3. But I’m getting strange values as measurements. What can be wrong? 21855, 21845, 21841, 2402.95, 218.45, 2184.5, 2184.5, 2184.5, 2184.5, 2184.5, 2184.5, 2184.5, 2184.5, 2184.5, 2184.5, 2129.1, 2143.1, 2147, 2184.4, 2184.5 The config is as follows: [[14]] nodename = emontx1 [[[rx]]] names = P1, P2, P3, P4, batt, temp1, temp2, temp3, temp4, temp5, temp6,temp7,temp8,temp9,temp10,temp11,temp12,temp13,temp14,temp15,temp16,temp17,temp18,temp19,temp20,temp21,temp22,temp23,temp24,pulse datacode = h scales = 1,1,1, 0.11, 0.01, 0.1,0.1,0.1,0.1,0.1, 0.1,0.1,0.1,0.1,0.1, 0.1,0.1,0.1,0.1,0.1, 0.1,0.1,0.1,0.1,0.1, 0.1,0.1,0.1,0.1, 1 units = W,W,W,W, V, C,C,C,C,C, C,C,C,C,C, C,C,C,C,C, C,C,C,C,C, C,C,C,C, N [[15]] nodename = emontx2 [[[rx]]] names = P5, P6, P7, P8, batt, temp25, temp26, temp27, temp28, temp29, temp30, temp31, temp32, temp33,temp34,temp35,temp36,temp37,temp38,temp39,temp40,temp41,temp42,temp43,temp44,temp45,temp46,temp47,temp48,pulse datacode = h scales = 1,1,1, 0.11, 0.01, 0.1,0.1,0.1,0.1,0.1, 0.1,0.1,0.1,0.1,0.1, 0.1,0.1,0.1,0.1,0.1, 0.1,0.1,0.1,0.1,0.1, 0.1,0.1,0.1,0.1, 1 units = W,W,W,W, V, C,C,C,C,C, C,C,C,C,C, C,C,C,C,C, C,C,C,C,C, C,C,C,C, N ---
**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:** [17 December 2019 16:27 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/2 "2019-12-17T16:27:07Z")
It looks as if you have a new emonTx V3.4 purchased after 18/10/2019 and this uses the new ‘continuous monitoring’ sketch with a new data format; and you are using an old emonhub.conf that does not have the necessary node definition. Replace the definitions for the node it is using - change `[[15]]` to the correct ID - with this: ```auto [[15]] nodename = emontx3cm15 [[[rx]]] names = MSG, Vrms, P1, P2, P3, P4, E1, E2, E3, E4, T1, T2, T3, pulse datacodes = L,h,h,h,h,h,L,L,L,L,h,h,h,L scales = 1,0.01,1,1,1,1,1,1,1,1,0.01,0.01,0.01,1 units = n,V,W,W,W,W,Wh,Wh,Wh,Wh,C,C,C,p whitening = 1 ``` You might also need to update emonCMS (or at least emonHub) for it to be able to handle the way the data is encoded. ---
**Author:** ![emontxv3](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/e/439d5e/32.png) [@emontxv3](https://community.openenergymonitor.org/u/emontxv3)\ **Post date:** [17 December 2019 16:40 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/3 "2019-12-17T16:40:51Z")
Thx, I received the new emontx today. Will this influence the older one that’s running as [[14]] ? Can they work together on the same emonCMS ? ---
**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:** [17 December 2019 16:52 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/4 "2019-12-17T16:52:00Z")
Yes - in exactly the same way that (say) an emonTH can work with an emonTx. The clue to the data encoding is `whitening = 1` If you don’t have that, you are back to the way the old “Discrete Sample” sketch works. (In the new sketch, a long stream of unchanging data bits may allow the radios to lose synchronism. Therefore we ‘XOR’ each data byte with 0x55 before transmission and the same after reception to restore the original data. 0x5555 (two bytes, one integer) is 21845 decimal.) ---
**Author:** ![emontxv3](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/e/439d5e/32.png) [@emontxv3](https://community.openenergymonitor.org/u/emontxv3)\ **Post date:** [17 December 2019 18:46 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/5 "2019-12-17T18:46:30Z")
I tried several ways to update the emonhub. But they all failed. And the emonhub is not measuring anymore because of “MainThread RFM2Pi thread is dead”. This happend after an attempt to update by SSH. But this stopped after 443 not authorised error. Deleting the new lines in the CONF file doesn’t solves this and is still reporting “MainThread RFM2Pi thread is dead”. What is the best way to update? For instance: make a backup, create a new SD card and than importing the backup? And if so, where can I read how to create a new SD card with the latest software? ---
**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:** [17 December 2019 19:10 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/6 "2019-12-17T19:10:42Z")
I’m not an emonCMS expert, so I’m afraid I can’t help. I think Brian’s about to come to your rescue. ---
**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:** [17 December 2019 19:11 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/7 "2019-12-17T19:11:01Z")
> [@emontxv3](#): > > What is the best way to update? From what version? Can you click on the button **Copy as Markdown** next to **Server Information** on the Admin page and paste here please (no further formatting required). ---
**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:** [17 December 2019 19:15 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/8 "2019-12-17T19:15:15Z")
My advice is to upgrade to the lastest version. [emonSD-17Oct19 release](https://community.openenergymonitor.org/t/emonsd-17oct19-release/12231) - get a new SD Card (you can always put the old one back in if there is an issue) - download & flash a new EmonSD image [emonSD pre built SD card Download & Change Log · openenergymonitor/emonpi Wiki · GitHub](https://github.com/openenergymonitor/emonpi/wiki/emonSD-pre-built-SD-card-Download-&-Change-Log) - take a backup of the existing system. You may need to clone [GitHub - emoncms/backup: emoncms backup module](https://github.com/emoncms/backup) and do a manual export. - install the new SD card & power up - wait, wait, wait, make a cup of coffee, wait, wait, wait… (lots of updates etc) - import the backup But look here first… > [@Backup module usb-import.sh script (beta)](https://community.openenergymonitor.org/t/backup-module-usb-import-sh-script-beta/12234): > > After reading through @mjseeley’s thread on migrating from an old 2015 image to the latest ([LCD Screen says "Updating - Do Not Unplug" (updating system from V8.5)](https://community.openenergymonitor.org/t/lcd-screen-says-updating-do-not-unplug/12191)) it got me thinking again about an idea for migrating that would avoid the need to update software or run a script on the original image. The idea is to take the original SD card and mount it as a ‘USB drive’ on to the Pi running the latest image, then run an import script on the new image to copy the files across directly. ---
**Author:** ![emontxv3](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/e/439d5e/32.png) [@emontxv3](https://community.openenergymonitor.org/u/emontxv3)\ **Post date:** [17 December 2019 19:23 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/9 "2019-12-17T19:23:26Z")
**Emoncms** Version low-write 9.8.3 2017.04.18 ---
**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:** [17 December 2019 19:30 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/10 "2019-12-17T19:30:33Z")
Yes update by SSH is not a good idea! Best idea, Start with new SD card. ---
**Author:** ![emontxv3](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/e/439d5e/32.png) [@emontxv3](https://community.openenergymonitor.org/u/emontxv3)\ **Post date:** [19 December 2019 21:02 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/11 "2019-12-19T21:02:45Z")
I installed the image on a 16GB SD card. The emonhub started. But I can’t do the update under admin. ([http://emonpi/admin/view](http://emonpi/admin/view)) How can I perform the update? Starting update via service-runner-update.sh (v3.0) \> - emonSD version: emonSD-17Oct19 ERROR: emonSD base image old or undefined…update will not continue See latest verson: [emonSD pre built SD card Download & Change Log · openenergymonitor/emonpi Wiki · GitHub](https://github.com/openenergymonitor/emonpi/wiki/emonSD-pre-built-SD-card-Download-&-Change-Log) Stopping update ---
**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:** [19 December 2019 21:08 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/12 "2019-12-19T21:08:52Z")
> [@emontxv3](#): > > I installed the image on a 16GB SD card. Do you mean you downloaded a new EmonSD image from the link and flashed it to a new Card? I have started a new Updating Guide here [Updating with new SD Card · openenergymonitor/emonpi Wiki · GitHub](https://github.com/openenergymonitor/emonpi/wiki/Updating-with-new-SD-Card) ---
**Author:** ![emontxv3](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/e/439d5e/32.png) [@emontxv3](https://community.openenergymonitor.org/u/emontxv3)\ **Post date:** [23 December 2019 18:05 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/13 "2019-12-23T18:05:14Z")
Yes, I downloaded the stable version and burned it with win32diskImager on the 16 GB SD card. Besides this error I also have the following two errors. The second one is showing after reading the backup from the previous SD card. ```auto **Notice** : Trying to get property 'gravatar' of non-object in **/var/www/emoncms/Theme/basic/menu_view.php** on line **144** ``` The thrid one occures when I look at the graphs in the graphs edit screen and shows the following error: ```auto **Warning** : Illegal string offset 'path' in **/var/www/emoncms/Theme/basic/sidebar_view.php** on line **210** **Warning** : Illegal string offset 'href' in **/var/www/emoncms/Theme/basic/sidebar_view.php** on line **211** **Warning** : Cannot assign an empty string to a string offset in **/var/www/emoncms/Theme/basic/sidebar_view.php** on line **211** **Warning** : Illegal string offset 'path' in **/var/www/emoncms/Theme/basic/sidebar_view.php** on line **213** **Warning** : Cannot assign an empty string to a string offset in **/var/www/emoncms/Theme/basic/sidebar_view.php** on line **213** **Warning** : Illegal string offset 'href' in **/var/www/emoncms/Theme/basic/sidebar_view.php** on line **215** ``` ---
**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 December 2019 07:01 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/14 "2019-12-24T07:01:07Z")
You must have a bad ‘flash’. Is it a new card? Download a new image and try again following this guide [Updating with new SD Card · openenergymonitor/emonpi Wiki · GitHub](https://github.com/openenergymonitor/emonpi/wiki/Updating-with-new-SD-Card) ---
**Author:** ![emontxv3](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/e/439d5e/32.png) [@emontxv3](https://community.openenergymonitor.org/u/emontxv3)\ **Post date:** [24 December 2019 07:25 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/15 "2019-12-24T07:25:27Z")
Thx, I will try the new build. And yes, the SD card is a new Scandisk Ultra 16 GB card. ---
**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 December 2019 07:57 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/16 "2019-12-24T07:57:36Z")
Remember to wait a good while for the updates to complete, that is where most folk fall down on initial startup. ---
**Author:** ![emontxv3](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/e/439d5e/32.png) [@emontxv3](https://community.openenergymonitor.org/u/emontxv3)\ **Post date:** [24 December 2019 12:09 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/17 "2019-12-24T12:09:52Z")
I’m already waiting more than one hour for the initial update. The photo is showing what is shown the last hour. The cursor is blinking (about 2 or three times per second). Can I proceed now to import the data from the backup file or do I have to wait longer? ![image](https://community.openenergymonitor.org/uploads/default/original/2X/b/b90f4a52760103e3d5234e99d92148b162097659.jpeg) ---
**Author:** ![emontxv3](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/e/439d5e/32.png) [@emontxv3](https://community.openenergymonitor.org/u/emontxv3)\ **Post date:** [24 December 2019 12:30 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/18 "2019-12-24T12:30:58Z")
Hereby the outcome of the import with a Permission denied error: Perhaps this was the reason? ```auto Emoncms MYSQL database import... Import feed meta data.. Restore phpfina and phptimeseries data folders... Import emonhub.conf > /etc/emonhub/old.emohub.conf mv: cannot move '/opt/openenergymonitor/data/import/emonhub.conf' to '/etc/emonhub/old.emonhub.conf': Permission denied emonhub.conf files restored as old.emonhub.conf, original file not modified. Please merge manually. Start with fresh config: copy NEW default emonpi.emonhub.conf: cp /opt/openenergymonitor/emonhub/conf/emonpi.default.emonhub.conf /etc/emonhub/emonhub.conf OK Restarting emonhub... Restarting feedwriter... 2019-10-17-12:30:37 ``` ---
**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 December 2019 15:38 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/19 "2019-12-24T15:38:15Z")
Could be. Is it all working now? ---
**Author:** ![emontxv3](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/e/439d5e/32.png) [@emontxv3](https://community.openenergymonitor.org/u/emontxv3)\ **Post date:** [30 December 2019 07:58 UTC](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764/20 "2019-12-30T07:58:28Z")
No, nothing seems to help yet. Is it possible to use the new purchased emonTx V3 with the older emonhub? For instance by substracting or deviding the values with 21845? Or is there an another alternative to update the emonhub for the old an new emonTx V3? [Next page](https://community.openenergymonitor.org/t/stange-values-like-21845-from-all-sensors/12764.md?page=2)