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 ?
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.)
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?
I’m not an emonCMS expert, so I’m afraid I can’t help. I think Brian’s about to come to your rescue.
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).
My advice is to upgrade to the lastest version. emonSD-17Oct19 release
- 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
- take a backup of the existing system. You may need to clone GitHub - emoncms/backup: emoncms backup module 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…
Emoncms Version low-write 9.8.3 2017.04.18
Yes update by SSH is not a good idea!
Best idea, Start with new SD card.
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)
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
Stopping update
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
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.
**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:
**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**
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
Thx, I will try the new build.
And yes, the SD card is a new Scandisk Ultra 16 GB card.
1 Like
Remember to wait a good while for the updates to complete, that is where most folk fall down on initial startup.
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?
Hereby the outcome of the import with a Permission denied error:
Perhaps this was the reason?
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
Could be.
Is it all working now?
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?
Let’s walk this back.
Can you explain exactly what your setup is? You started off with
To what? If you switch that off, does everything work as it did before?
Just now I started all over again with only the older emontx V3 and emonhub with the new SD card (without the new emontx V3).
I waited for the updates.
The next step was that I logged in with http://emonpi.local/ and choose the wifi and set the password for it.
This is shown in the log screen after the first run without any changes:
2019-10-17 10:48:54,633 INFO MainThread Logging level set to DEBUG
2019-10-17 10:48:54,633 INFO MainThread Creating EmonHubJeeInterfacer 'RFM2Pi'
2019-10-17 10:48:54,638 DEBUG MainThread Opening serial port: /dev/ttyAMA0 @ 38400 bits/s
2019-10-17 10:48:56,644 INFO MainThread RFM2Pi device firmware version: [RF12demo.12]
2019-10-17 10:48:56,645 INFO MainThread RFM2Pi device current settings: E i5 g210 @ 433 MHz
2019-10-17 10:48:56,646 INFO MainThread Setting RFM2Pi quiet: 0 (0q)
2019-10-17 10:48:57,648 INFO MainThread Setting RFM2Pi calibration: 230V (1p)
2019-10-17 10:48:58,651 DEBUG MainThread Setting RFM2Pi subchannels: ['ToRFM12']
2019-10-17 10:48:58,652 DEBUG MainThread Setting RFM2Pi pubchannels: ['ToEmonCMS']
2019-10-17 10:48:58,653 INFO MainThread Creating EmonHubMqttInterfacer 'MQTT'
2019-10-17 10:48:58,656 DEBUG RFM2Pi acknowledged command: > 0q
2019-10-17 10:48:58,660 DEBUG MainThread Setting MQTT subchannels: ['ToEmonCMS']
2019-10-17 10:48:58,660 DEBUG MainThread Setting MQTT pubchannels: ['ToRFM12']
2019-10-17 10:48:58,661 INFO MainThread Setting MQTT nodevar_format_enable: 1
2019-10-17 10:48:58,662 INFO MainThread Setting MQTT node_format_enable: 1
2019-10-17 10:48:58,662 INFO MainThread Setting MQTT nodevar_format_basetopic: emon/
2019-10-17 10:48:58,664 INFO MainThread Creating EmonHubEmoncmsHTTPInterfacer 'emoncmsorg'
2019-10-17 10:48:58,665 DEBUG MainThread Setting emoncmsorg subchannels: ['ToEmonCMS']
2019-10-17 10:48:58,666 DEBUG MainThread Setting emoncmsorg pubchannels: ['ToRFM12']
2019-10-17 10:48:58,667 INFO MainThread Setting emoncmsorg url: https://emoncms.org
2019-10-17 10:48:58,667 INFO MainThread Setting emoncmsorg senddata: 1
2019-10-17 10:48:58,668 WARNING MainThread Setting emoncmsorg apikey: obscured
2019-10-17 10:48:58,668 INFO MainThread Setting emoncmsorg sendstatus: 1
2019-10-17 10:48:58,759 DEBUG RFM2Pi device settings updated: E i5 g210 @ 433 MHz
2019-10-17 10:48:58,861 DEBUG RFM2Pi acknowledged command: > 1p
2019-10-17 10:48:59,168 DEBUG RFM2Pi acknowledged command: <nn> i - set node ID (standard node ids are 1..30)
2019-10-17 10:48:59,273 DEBUG RFM2Pi acknowledged command: <n> b - set MHz band (4 = 433, 8 = 868, 9 = 915)
2019-10-17 10:48:59,379 DEBUG RFM2Pi acknowledged command: <nnnn> o - change frequency offset within the band (default 1600)
2019-10-17 10:48:59,590 DEBUG RFM2Pi acknowledged command: <nnn> g - set network group (RFM12 only allows 212, 0 = any)
2019-10-17 10:48:59,695 DEBUG RFM2Pi acknowledged command: <n> c - set collect mode (advanced, normally 0)
2019-10-17 10:48:59,904 DEBUG RFM2Pi acknowledged command: ...,<nn> a - send data packet to node <nn>, request ack
2019-10-17 10:49:00,009 DEBUG RFM2Pi acknowledged command: ...,<nn> s - send data packet to node <nn>, no ack
2019-10-17 10:49:00,115 DEBUG RFM2Pi acknowledged command: <n> q - set quiet mode (1 = don't report bad packets)
2019-10-17 10:49:00,221 DEBUG RFM2Pi acknowledged command: <n> x - set reporting format (0: decimal, 1: hex, 2: hex+ascii)
2019-10-17 10:49:00,533 DEBUG RFM2Pi acknowledged command: <hchi>,<hclo>,<addr>,<cmd> f - FS20 command (868 MHz)
2019-10-17 10:49:00,639 DEBUG RFM2Pi acknowledged command: <addr>,<dev>,<on> k - KAKU command (433 MHz)
2019-10-17 10:49:00,844 DEBUG RFM2Pi device settings updated: E i5 g210 @ 433 MHz
2019-10-17 10:49:00,950 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 14 226 87 10 183 6 121 1 248 1 15 1 145 0 132 0 146 0 168 0 69 (-39)
2019-10-17 10:49:01,258 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 30 106 95 67 235 127 250 56 109 199 222 125 189 146 217 31 231 94 252 239 179 (-96)
2019-10-17 10:49:07,225 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 179 243 152 56 125 (-96)
2019-10-17 10:49:07,432 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 14 226 59 10 122 6 112 1 246 1 26 1 145 0 132 0 148 0 168 0 70 (-37)
2019-10-17 10:49:08,768 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 165 88 161 186 231 96 83 227 247 90 134 111 95 111 163 46 206 (-94)
2019-10-17 10:49:13,381 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 179 109 132 164 206 75 147 57 185 229 139 14 78 85 48 245 197 171 75 254 188 (-89)
2019-10-17 10:49:15,009 DEBUG RFM2Pi 7 NEW FRAME : OK 14 222 0 182 2 194 6 113 1 247 1 37 1 145 0 132 0 151 0 168 0 71 1 140 0 12 0 168 0 160 0 156 0 156 0 149 1 254 255 216 0 214 1 71 2 130 0 42 0 236 0 138 0 220 0 115 0 138 0 1 0 (-38)
2019-10-17 10:49:15,011 WARNING RFM2Pi 7 RX data length: 60 is not valid for datacodes ['h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'h', 'L']```
Than I changed the [[14]] setup in the config screen as mentioned above in the first question 13 days ago.
This shows the following values of the first emontx V3 of all attached sensors.
2019-10-17 10:57:53,806 INFO MainThread Setting RFM2Pi quiet: 0 (0q)
2019-10-17 10:57:53,908 DEBUG RFM2Pi acknowledged command: > 0q
2019-10-17 10:57:54,011 DEBUG RFM2Pi device settings updated: E i5 g210 @ 433 MHz
2019-10-17 10:57:54,809 INFO MainThread Setting RFM2Pi calibration: 230V (1p)
2019-10-17 10:57:54,815 DEBUG RFM2Pi acknowledged command: > 1p
2019-10-17 10:57:55,123 DEBUG RFM2Pi acknowledged command: <nn> i - set node ID (standard node ids are 1..30)
2019-10-17 10:57:55,228 DEBUG RFM2Pi acknowledged command: <n> b - set MHz band (4 = 433, 8 = 868, 9 = 915)
2019-10-17 10:57:55,334 DEBUG RFM2Pi acknowledged command: <nnnn> o - change frequency offset within the band (default 1600)
2019-10-17 10:57:55,545 DEBUG RFM2Pi acknowledged command: <nnn> g - set network group (RFM12 only allows 212, 0 = any)
2019-10-17 10:57:55,650 DEBUG RFM2Pi acknowledged command: <n> c - set collect mode (advanced, normally 0)
2019-10-17 10:57:55,860 DEBUG RFM2Pi acknowledged command: ...,<nn> a - send data packet to node <nn>, request ack
2019-10-17 10:57:55,965 DEBUG RFM2Pi acknowledged command: ...,<nn> s - send data packet to node <nn>, no ack
2019-10-17 10:57:56,071 DEBUG RFM2Pi acknowledged command: <n> q - set quiet mode (1 = don't report bad packets)
2019-10-17 10:57:56,178 DEBUG RFM2Pi acknowledged command: <n> x - set reporting format (0: decimal, 1: hex, 2: hex+ascii)
2019-10-17 10:57:56,491 DEBUG RFM2Pi acknowledged command: <hchi>,<hclo>,<addr>,<cmd> f - FS20 command (868 MHz)
2019-10-17 10:57:56,597 DEBUG RFM2Pi acknowledged command: <addr>,<dev>,<on> k - KAKU command (433 MHz)
2019-10-17 10:57:56,802 DEBUG RFM2Pi device settings updated: E i5 g210 @ 433 MHz
2019-10-17 10:57:56,906 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 157 70 244 45 200 219 28 18 (-96)
2019-10-17 10:57:57,716 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 1 222 72 190 79 20 214 44 61 196 174 7 100 247 159 91 214 246 198 103 161 (-94)
2019-10-17 10:57:57,831 DEBUG RFM2Pi 57 NEW FRAME : OK 14 212 0 72 3 174 6 147 7 246 1 185 1 145 0 133 0 196 0 167 0 52 1 138 0 15 0 175 0 160 0 157 0 11 1 179 1 0 0 222 0 199 1 51 2 130 0 63 0 226 0 141 0 220 0 107 0 140 0 1 0 (-40)
2019-10-17 10:57:57,836 DEBUG RFM2Pi 57 Timestamp : 1571306277.83
2019-10-17 10:57:57,837 DEBUG RFM2Pi 57 From Node : 14
2019-10-17 10:57:57,838 DEBUG RFM2Pi 57 Values : [212, 840, 1710, 213.29, 5.0200000000000005, 44.1, 14.5, 13.3, 19.6, 16.7, 30.8, 13.8, 1.5, 17.5, 16, 15.700000000000001, 26.700000000000003, 43.5, 0, 22.200000000000003, 45.5, 56.300000000000004, 13, 6.300000000000001, 22.6, 14.100000000000001, 22, 10.700000000000001, 14, 1]
2019-10-17 10:57:57,838 DEBUG RFM2Pi 57 RSSI : -40
2019-10-17 10:57:57,839 DEBUG RFM2Pi 57 Sent to channel(start)' : ToEmonCMS
2019-10-17 10:57:57,840 DEBUG RFM2Pi 57 Sent to channel(end)' : ToEmonCMS
2019-10-17 10:57:57,893 INFO MQTT Connecting to MQTT Server
2019-10-17 10:57:57,997 INFO MQTT connection status: Connection successful
2019-10-17 10:57:57,998 DEBUG emoncmsorg Buffer size: 1
2019-10-17 10:57:57,999 DEBUG MQTT CONACK => Return code: 0
2019-10-17 10:57:58,129 INFO MQTT on_subscribe
2019-10-17 10:57:58,348 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 4 183 170 206 128 242 13 141 215 254 157 149 232 140 186 32 152 196 60 68 95 (-96)
2019-10-17 10:58:00,866 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 0 197 50 238 71 130 194 210 242 237 15 146 127 248 34 249 175 152 113 218 24 (-93)
2019-10-17 10:58:05,438 DEBUG RFM2Pi 58 NEW FRAME : OK 14 213 0 100 3 169 6 124 7 254 1 185 1 145 0 133 0 196 0 167 0 52 1 138 0 15 0 175 0 160 0 157 0 11 1 179 1 0 0 222 0 199 1 53 2 130 0 63 0 226 0 141 0 220 0 107 0 138 0 1 0 (-40)
2019-10-17 10:58:05,443 DEBUG RFM2Pi 58 Timestamp : 1571306285.44
2019-10-17 10:58:05,444 DEBUG RFM2Pi 58 From Node : 14
2019-10-17 10:58:05,445 DEBUG RFM2Pi 58 Values : [213, 868, 1705, 210.76, 5.1000000000000005, 44.1, 14.5, 13.3, 19.6, 16.7, 30.8, 13.8, 1.5, 17.5, 16, 15.700000000000001, 26.700000000000003, 43.5, 0, 22.200000000000003, 45.5, 56.5, 13, 6.300000000000001, 22.6, 14.100000000000001, 22, 10.700000000000001, 13.8, 1]
2019-10-17 10:58:05,446 DEBUG RFM2Pi 58 RSSI : -40
2019-10-17 10:58:05,446 DEBUG RFM2Pi 58 Sent to channel(start)' : ToEmonCMS
2019-10-17 10:58:05,447 DEBUG RFM2Pi 58 Sent to channel(end)' : ToEmonCMS
2019-10-17 10:58:05,698 DEBUG MQTT Publishing: emon/emontx1/P1 213
2019-10-17 10:58:05,700 DEBUG MQTT Publishing: emon/emontx1/P2 868
2019-10-17 10:58:05,701 DEBUG MQTT Publishing: emon/emontx1/P3 1705
2019-10-17 10:58:05,703 DEBUG MQTT Publishing: emon/emontx1/P4 210.76
2019-10-17 10:58:05,704 DEBUG MQTT Publishing: emon/emontx1/batt 5.1
2019-10-17 10:58:05,706 DEBUG MQTT Publishing: emon/emontx1/temp1 44.1
2019-10-17 10:58:05,708 DEBUG MQTT Publishing: emon/emontx1/temp2 14.5
2019-10-17 10:58:05,710 DEBUG MQTT Publishing: emon/emontx1/temp3 13.3
2019-10-17 10:58:05,712 DEBUG MQTT Publishing: emon/emontx1/temp4 19.6
2019-10-17 10:58:05,713 DEBUG MQTT Publishing: emon/emontx1/temp5 16.7
2019-10-17 10:58:05,714 DEBUG MQTT Publishing: emon/emontx1/temp6 30.8
2019-10-17 10:58:05,716 DEBUG MQTT Publishing: emon/emontx1/temp7 13.8
2019-10-17 10:58:05,718 DEBUG MQTT Publishing: emon/emontx1/temp8 1.5
2019-10-17 10:58:05,720 DEBUG MQTT Publishing: emon/emontx1/temp9 17.5
2019-10-17 10:58:05,721 DEBUG MQTT Publishing: emon/emontx1/temp10 16
2019-10-17 10:58:05,723 DEBUG MQTT Publishing: emon/emontx1/temp11 15.7
2019-10-17 10:58:05,724 DEBUG MQTT Publishing: emon/emontx1/temp12 26.7
2019-10-17 10:58:05,726 DEBUG MQTT Publishing: emon/emontx1/temp13 43.5
2019-10-17 10:58:05,727 DEBUG MQTT Publishing: emon/emontx1/temp14 0
2019-10-17 10:58:05,729 DEBUG MQTT Publishing: emon/emontx1/temp15 22.2
2019-10-17 10:58:05,730 DEBUG MQTT Publishing: emon/emontx1/temp16 45.5
2019-10-17 10:58:05,732 DEBUG MQTT Publishing: emon/emontx1/temp17 56.5
2019-10-17 10:58:05,732 DEBUG MQTT Publishing: emon/emontx1/temp18 13
2019-10-17 10:58:05,733 DEBUG MQTT Publishing: emon/emontx1/temp19 6.3
2019-10-17 10:58:05,734 DEBUG MQTT Publishing: emon/emontx1/temp20 22.6
2019-10-17 10:58:05,735 DEBUG MQTT Publishing: emon/emontx1/temp21 14.1
2019-10-17 10:58:05,736 DEBUG MQTT Publishing: emon/emontx1/temp22 22
2019-10-17 10:58:05,736 DEBUG MQTT Publishing: emon/emontx1/temp23 10.7
2019-10-17 10:58:05,737 DEBUG MQTT Publishing: emon/emontx1/temp24 13.8
2019-10-17 10:58:05,738 DEBUG MQTT Publishing: emon/emontx1/pulse 1
2019-10-17 10:58:05,739 DEBUG MQTT Publishing: emon/emontx1/rssi -40
2019-10-17 10:58:05,740 INFO MQTT Publishing: emonhub/rx/14/values 213,868,1705,210.76,5.1,44.1,14.5,13.3,19.6,16.7,30.8,13.8,1.5,17.5,16,15.7,26.7,43.5,0,22.2,45.5,56.5,13,6.3,22.6,14.1,22,10.7,13.8,1,-40
And finally I created 3 feeds in the Inputs menu:
But I can not create a graph from this. (and also not if I import the backup from the former SD card)
