Well both logs seem to report issues with MQTT, do you have Mosquitto running? are there any logs for Mosquitto?
no mosquitto installed,
I have the original emonpi of may 2015, with 2 CT and one voltage sensor that’s all,
I suppose that the MQTT is some development that have to be not activate on my installation (at least as is now). but how to stop it?
Can I download the last SD image and update everything?
Is it compatible with my emonpi version?
I made a backup of all data.
As far as I recall Mosquitto has been installed on every SD image since the emonPi was released so you should have it.
However the earlier images had the Nodes module which is no longer supported, the MQTT input of emonCMS has been changed significantly and the MQTT implementation in the emonpi variant of emonHub altered to suit those changes.
If you have your data backed up, I think perhaps you would be better off investing your time in to personalizing a fresh image rather than trying to fix a broken and out of date image.
Thanks Paul,
I’m not so familiar with software in general and “linux command” is a unknown world.
In any case I update the SD with latest version. Process is gone correctly.
Now i get the node running at least I see the value.
Inputs:
Node Key Name Process list Updated Value
emonpi power1 -0s ago 181
emonpi power2 -0s ago -6.00
emonpi power1pluspower2 -0s ago 175
This is good.
but now I’m not able to setup the feeds
following the setup procedure I get this error when I try to add a new feed as a “Log to feed”
ERROR: Feed could not be created, undefined
Could you tell me why?
I made a emonpi restart and also an update as suggested on some post on community, but with no result.
here is the log file
2016-12-31 00:21:37,788 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 29 229 1 113 199 163 144 207 229 189 141 110 161 1 90 183 31 127 31 3 118 (-97)
2016-12-31 00:21:37,894 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 26 83 232 140 250 143 26 242 217 254 80 28 116 50 90 183 31 127 31 3 118 (-97)
2016-12-31 00:21:38,113 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 20 45 33 56 253 193 120 127 131 244 111 195 207 103 86 57 178 53 6 220 121 (-98)
2016-12-31 00:21:38,237 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 19 181 73 46 60 226 47 173 90 202 21 242 242 205 89 202 2 165 192 180 70 (-99)
2016-12-31 00:21:38,932 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 29 178 133 197 61 92 54 46 249 73 243 83 244 61 238 227 67 205 138 244 223 (-97)
2016-12-31 00:21:39,042 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 14 0 245 103 88 93 154 184 91 225 158 200 160 206 189 211 80 17 4 159 168 (-99)
2016-12-31 00:21:39,810 DEBUG RFM2Pi 359 NEW FRAME : OK 5 173 0 251 255 168 0 243 85 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2016-12-31 00:21:39,814 DEBUG RFM2Pi 359 Timestamp : 1483143699.81
2016-12-31 00:21:39,815 DEBUG RFM2Pi 359 From Node : 5
2016-12-31 00:21:39,816 DEBUG RFM2Pi 359 Values : [173, -5, 168, 220.03, 0, 0, 0, 0, 0, 0, 0]
2016-12-31 00:21:39,817 DEBUG RFM2Pi 359 Sent to channel(start)' : ToEmonCMS
2016-12-31 00:21:39,818 INFO RFM2Pi Publishing: emon/emonpi/power1 173
2016-12-31 00:21:39,820 INFO RFM2Pi Publishing: emon/emonpi/power2 -5
2016-12-31 00:21:39,823 INFO RFM2Pi Publishing: emon/emonpi/power1pluspower2 168
2016-12-31 00:21:39,825 INFO RFM2Pi Publishing: emon/emonpi/vrms 220.03
2016-12-31 00:21:39,827 INFO RFM2Pi Publishing: emon/emonpi/t1 0
2016-12-31 00:21:39,830 INFO RFM2Pi Publishing: emon/emonpi/t2 0
2016-12-31 00:21:39,832 INFO RFM2Pi Publishing: emon/emonpi/t3 0
2016-12-31 00:21:39,834 INFO RFM2Pi Publishing: emon/emonpi/t4 0
2016-12-31 00:21:39,836 INFO RFM2Pi Publishing: emon/emonpi/t5 0
2016-12-31 00:21:39,894 INFO RFM2Pi Publishing: emon/emonpi/t6 0
2016-12-31 00:21:39,897 INFO RFM2Pi Publishing: emon/emonpi/pulsecount 0
2016-12-31 00:21:39,899 INFO RFM2Pi Publishing: emon/emonpi/rssi 0
2016-12-31 00:21:39,901 INFO RFM2Pi Publishing: emonhub/rx/5/values 173,-5,168,220.03,0,0,0,0,0,0,0
2016-12-31 00:21:39,906 INFO RFM2Pi Publishing: emonhub/rx/5/rssi 0
2016-12-31 00:21:39,909 DEBUG RFM2Pi 359 adding frame to buffer => [1483143699.809919, 5, 173, -5, 168, 220.03, 0, 0, 0, 0, 0, 0, 0]
2016-12-31 00:21:39,910 DEBUG RFM2Pi 359 Sent to channel(end)' : ToEmonCMS
2016-12-31 00:21:40,018 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 27 108 150 173 2 247 240 88 91 221 235 245 245 48 11 183 10 130 139 232 72 (-98)
2016-12-31 00:21:42,546 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 10 228 58 40 176 161 5 142 50 51 33 175 215 255 176 1 28 246 36 25 182 (-93)
2016-12-31 00:21:43,859 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 11 28 47 0 73 104 221 1 159 104 230 104 75 167 227 134 49 206 116 65 180 (-90)
what I understand is that the RFM2pi get wrong data and discard some strings (but there is nothing connected!) the measured power1, power2,… is correct (it is night time). this means that the hardware part work correctly.
[if it is not correct to post here, please suggest me how to change/move the discussion.]
Unfortunately not, this has been reported before but it is unclear why it has happened. See these 2 posts
and on the old forum there are these
Are you by any chance using any odd characters in the feed names? try something simpler to see if it works eg “myfeed”, the feed names can be changed again afterwards.
Hi, thanks for your support,
no odd characters there are no feeds at all.
something strange happen when i open the feeds page. The page display “loading…” for a long time.
To avoid mistake I download a new image for an other mirror and rebuilt the SD.
No changes.
The only thing that I’m able to do is to add a feed out of “main” one, but after that I’m not able to see them. feed page still stay on “loading…”
even if i try to remove all feed from the node process.
I’m a bit lost 
Any clues in emoncms.log?
here is the log
2016-12-31 13:58:47,027 INFO RFM2Pi Publishing: emonhub/rx/5/values 1396,775,2171,221.72,0,0,0,0,0,0,0
2016-12-31 13:58:47,041 INFO RFM2Pi Publishing: emonhub/rx/5/rssi 0
2016-12-31 13:58:47,047 DEBUG RFM2Pi 1360 adding frame to buffer => [1483192726.984786, 5, 1396, 775, 2171, 221.72, 0, 0, 0, 0, 0, 0, 0]
2016-12-31 13:58:47,052 DEBUG RFM2Pi 1360 Sent to channel(end)' : ToEmonCMS
2016-12-31 13:58:50,430 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 16 164 80 64 146 19 65 154 222 99 221 242 99 190 221 217 230 163 108 223 31 (-97)
2016-12-31 13:58:51,989 DEBUG RFM2Pi 1361 NEW FRAME : OK 5 109 5 17 3 126 8 96 86 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2016-12-31 13:58:51,993 DEBUG RFM2Pi 1361 Timestamp : 1483192731.99
2016-12-31 13:58:51,994 DEBUG RFM2Pi 1361 From Node : 5
2016-12-31 13:58:51,995 DEBUG RFM2Pi 1361 Values : [1389, 785, 2174, 221.12, 0, 0, 0, 0, 0, 0, 0]
2016-12-31 13:58:51,996 DEBUG RFM2Pi 1361 Sent to channel(start)' : ToEmonCMS
2016-12-31 13:58:51,997 INFO RFM2Pi Publishing: emon/emonpi/power1 1389
2016-12-31 13:58:51,999 INFO RFM2Pi Publishing: emon/emonpi/power2 785
2016-12-31 13:58:52,001 INFO RFM2Pi Publishing: emon/emonpi/power1pluspower2 2174
2016-12-31 13:58:52,003 INFO RFM2Pi Publishing: emon/emonpi/vrms 221.12
2016-12-31 13:58:52,006 INFO RFM2Pi Publishing: emon/emonpi/t1 0
2016-12-31 13:58:52,009 INFO RFM2Pi Publishing: emon/emonpi/t2 0
2016-12-31 13:58:52,012 INFO RFM2Pi Publishing: emon/emonpi/t3 0
2016-12-31 13:58:52,014 INFO RFM2Pi Publishing: emon/emonpi/t4 0
2016-12-31 13:58:52,017 INFO RFM2Pi Publishing: emon/emonpi/t5 0
2016-12-31 13:58:52,021 INFO RFM2Pi Publishing: emon/emonpi/t6 0
2016-12-31 13:58:52,031 INFO RFM2Pi Publishing: emon/emonpi/pulsecount 0
2016-12-31 13:58:52,034 INFO RFM2Pi Publishing: emon/emonpi/rssi 0
2016-12-31 13:58:52,037 INFO RFM2Pi Publishing: emonhub/rx/5/values 1389,785,2174,221.12,0,0,0,0,0,0,0
2016-12-31 13:58:52,056 INFO RFM2Pi Publishing: emonhub/rx/5/rssi 0
2016-12-31 13:58:52,060 DEBUG RFM2Pi 1361 adding frame to buffer => [1483192731.988953, 5, 1389, 785, 2174, 221.12, 0, 0, 0, 0, 0, 0, 0]
2016-12-31 13:58:52,066 DEBUG RFM2Pi 1361 Sent to channel(end)' : ToEmonCMS
2016-12-31 13:58:52,184 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 8 139 89 238 33 220 60 162 37 126 175 102 79 179 143 19 61 130 46 5 113 (-99)
2016-12-31 13:58:53,114 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 5 62 185 212 181 255 143 189 79 13 250 139 71 111 225 63 5 188 73 116 11 (-100)
2016-12-31 13:58:53,434 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 21 61 105 2 131 217 207 222 191 166 91 147 28 17 140 233 155 241 158 61 111 (-98)
2016-12-31 13:58:54,260 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 26 138 206 58 122 163 198 216 192 253 12 254 63 222 3 15 46 126 172 173 133 (-93)
?? I didn’t identify anything in particular.
I also try to import my backup feed does not imported “process not valid”
That’s emonhub.log, the issue is with emoncms, is there anything in emoncms.log?
makes me think when I first moved to phpfina etc on my hosted version. It was pointing to the wrong directories
Could it be there is some write refusal on the SD-card or lack of free space ?
Sorry,
here is
2016-12-31 12:09:31.794|WARN|phpmqtt_input.php|Starting MQTT Input script
2016-12-31 12:09:39.524|WARN|phpmqtt_input.php|Subscribing to: emon/#
2016-12-31 12:09:39.525|WARN|phpmqtt_input.php|Not connected, retrying connection
2016-12-31 12:09:39.527|WARN|phpmqtt_input.php|Connecting to MQTT server: Connection Accepted.: code: 0
2016-12-31 12:09:39.528|WARN|phpmqtt_input.php|Subscribed to topic: emon/#
2016-12-31 12:09:45.961|WARN|phpmqtt_input.php|Starting MQTT Input script
2016-12-31 12:09:47.125|WARN|phpmqtt_input.php|Subscribing to: emon/#
2016-12-31 12:09:47.126|WARN|phpmqtt_input.php|Not connected, retrying connection
2016-12-31 12:09:47.127|WARN|phpmqtt_input.php|Connecting to MQTT server: Connection Accepted.: code: 0
2016-12-31 12:09:47.128|WARN|phpmqtt_input.php|Subscribed to topic: emon/#
2016-12-31 14:05:53.506|ERROR|feed_model.php|EngineClass() Engine id '1' is not supported.
2016-12-31 14:19:19.259|ERROR|feed_model.php|EngineClass() Engine id '1' is not supported.
2016-12-31 14:19:19.550|ERROR|feed_model.php|EngineClass() Engine id '1' is not supported.
last row appears when i try to upload my backup
Feed directory paths or permissions were my first thought but being a prepared image there should be no issues there, lack of space is possible I guess but I thought the SD card should auto expand on first boot.
@Pierluigi_Dall_Osto What size SD card are you using? and what is the result of using df -h at the command line?
Engine type 1 is timestore which is now deprecated.
Do you have any timestore feeds in your old data?
i use the original 4Gb SD card and write over it the new SD image with Win32DiskImager. as proposed in the guide.
As I’m on windows… I did not format the SD is it wrong?
thanks for any feedback and thinks that I’m a newbie on linux command
What you have done sounds right and should be correct, what about on the emoncms admin page, what is the reported disc usage there?
pi@emonpi(ro):~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 3.4G 1.9G 1.4G 59% /
devtmpfs 483M 0 483M 0% /dev
tmpfs 487M 0 487M 0% /dev/shm
tmpfs 487M 6.6M 481M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 487M 0 487M 0% /sys/fs/cgroup
tmpfs 40M 6.6M 34M 17% /var/lib/openhab
tmpfs 1.0M 4.0K 1020K 1% /var/lib/dhcpcd5
/dev/mmcblk0p3 194M 167M 18M 91% /home/pi/data
tmpfs 1.0M 0 1.0M 0% /var/lib/dhcp
tmpfs 50M 4.6M 46M 10% /var/log
/dev/mmcblk0p1 60M 21M 40M 35% /boot
tmpfs 30M 40K 30M 1% /tmp
no time store feed set by me, there is an empty folder “phptimeseries”
Pi CPU Temp 32.55°C
Release emonSD-07Nov16
Memory RAM
Used 25,78%
Total: 973,11 MB Used: 250,88 MB Free: 722,22 MB
Disk Mount Stats
/
Used 56,10%
Total: 3,33 GB Used: 1,87 GB Free: 1,3 GB
/home/pi/data
Used 85,72%
Total: 193,66 MB Used: 166,01 MB Free: 17,65 MB
/boot
Used 34,75%
Total: 59,95 MB Used: 20,83 MB Free: 39,12 MB
PHP Version 5.6.27-0+deb8u1 (Zend Version 2.6.0)
The data partition is 91% full so it might cause problems with importing your old data, but it would not stop you creating new feeds.
Are you still unable to create new feeds?
Has that created an entry in emoncms.log?