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?
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)
btw: after starting the old sd-card again I see that the last line is “emonpi login:”.
This line is only shortly shown with the new sd-card.
Can this explain the error?
Linux screen of old sd-card shows “emonpi login:” as the last line contionusly:
Linux screen of the new sd-card shows 5 seconds the following as the last line “emonpi login:”:
And than the last line “emonpi login:” is gone after 5 seconds and doesn’t return in screen besides the blinking cursor on that line:
In what? An RPi with the emonbase RFM card or an EmonPi?
Could you please post the system info. Please click on the button Copy as Markdown next to Server Information on the Admin page and paste here (no further formatting required).
Model :- Raspberry Pi 3 Model B Rev 1.2 - 1GB (Sony UK)
Serial num. :- 670D57CB
Temperature :- 48.31°C - 48.3°C
emonpiRelease :- emonSD-17Oct19
File-system :- read-write
OK, thanks.
Do you have 24 temperature sensors hanging off the EmonPi original EmonTX?
Yes, 24 temperature and 4 current sensors on the EmonTx V3 that I bought in 2015.
And working fine for several years now.
Did you modify the Firmware on the EmonTX to achieve this?
No, it is all original. I only needed a power full 5 V source.
Hereby the system info of the previous SD card.
Server Information
Emoncms Version low-write 9.8.3 | 2017.04.18
Modules admin app backup config dashboard device eventp feed graph input openbem postprocess process schedule time user vis wifi
Buffer 145 feed points pending write
Writer Daemon is running with sleep 60s
Server OS Linux 4.1.19-v7+
Host emonpi emonpi (127.0.1.1)
Date 2019-12-30 10:46:58 UTC
Uptime 10:46:58 up 4 min, 0 users, load average: 0,47, 0,45, 0,23
HTTP Server Apache/2.4.10 (Raspbian) HTTP/1.1 CGI/1.1 80
Database Version MySQL 5.5.60-0+deb8u1
Host localhost (127.0.0.1)
Date 2019-12-30 10:46:58 (UTC 00:00)
Stats Uptime: 1761 Threads: 3 Questions: 1128 Slow queries: 0 Opens: 62 Flush tables: 1 Open tables: 54 Queries per second avg: 0.640
Redis Version 2.8.17
Host localhost:6379 (127.0.0.1)
Size 153 keys (498.38K)Flush
Uptime 0 days
MQTT Version
Host localhost:1883 (127.0.0.1)
Pi CPU Temp 47.77°CShutdownReboot
Release emonSD-03May16
Memory RAM
Used 23,92%
Total: 973,37 MB Used: 232,81 MB Free: 740,56 MB
Disk Mount Stats
/
Used 47,53%
Total: 3,33 GB Used: 1,58 GB Free: 1,59 GB
/boot
Used 33,25%
Total: 59,95 MB Used: 19,93 MB Free: 40,02 MB
/home/pi/data
Used 33,76%
Total: 3,63 GB Used: 1,23 GB Free: 2,22 GB
PHP Version 5.6.33-0+deb8u1 (Zend Version 2.6.0)
Modules Core date ereg libxml openssl pcre zlib bcmath bz2 calendar ctype dba dom hash fileinfo filter ftp gettext SPL iconv mbstring session posix Reflection standard shmop SimpleXML soap sockets Phar exif sysvmsg sysvsem sysvshm tokenizer wddx xml xmlreader xmlwriter zip apache2handler PDO curl dio json mcrypt mosquitto mysql mysqli pdo_mysql readline redis mhash Zend OPcache
I mean a separate power full 5 Volt source for the 24 sensors.
This is the EmonPi that I use:
This is not an EmonPi, That is an EmonBase (as stated in the shop banner).
Makes a big difference.
This is an EmonPi
So you posted a config in the first post;
Is this the config from the original emonhub.cfg
file?
That is odd. I thought the limit was 6. More than 6 can cause timing issues but let’s leave that for later.
About the original emonhub.cfg: What I remember is that I only added temp sensors over time. And that the emonhub.cfg is not changed in one or another way.
What I once had to change is logged in the following: MQTT Server Issue - Connection Refused not authorized - #5 by emontxv3
About the EmonBase (sorry that I got that wrong by mentioning EmonPi) with the new SD card: do you why the linux screen is not showing the “emonpi login:” line, about 5 seconds after completing reboot?
Looking at Trystan’s sketch “EmonTxV3CM.ino”, it is horribly confused.
The comment at the top says - from an early version:
/*
Change Log:
v0.1: First version, combination of EmonTxV3CM_max and EmonTx v3 original firmware
emonhub.conf node decoder (nodeid is 8 when switch is off, 9 when switch is on)
See: https://github.com/openenergymonitor/emonhub/blob/emon-pi/configuration.md
copy the following in to emonhub.conf:
[[8]]
nodename = emontx8
[[[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
*/
and the DIP switch changes it to NodeID = 9.
and from a later version:
/*
Change Log:
v1.0: First release of EmonTxV3 Continuous Monitoring Firmware.
v1.1: First stable release, Set default node to 15
v1.2: Enable RF startup test sequence (factory testing), Enable DEBUG by default to support EmonESP
v1.3: Inclusion of watchdog
emonhub.conf node decoder (nodeid is 8 when switch is off, 9 when switch is on)
See: https://github.com/openenergymonitor/emonhub/blob/emon-pi/configuration.md
copy the following in to emonhub.conf:
[[15]]
nodename = EmonTxV3CM_15
[[[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
*/
and the DIP switch changes it to NodeID = 16.
So, if the ORIGINAL emonTx is Node 14, then no - no matter which version of software the new emonTx has.
But remember, you must have only one definition for each NodeID in the emonhub.conf file.