Flukso v2b on P1, no pulses at all.

Recently my smart meter has been installed. It took some time to get the meter working properly as the energy supplier hadnt deployed it correctly and all usage was registered on the night tariff (including the pv output). For a few days now it's actually showing the correct usage for day and night tariffs so I decided to hook up my Flukso v2b and start reading our energy usage. I have had the Flukso for a while and only used it for a short time to read out the previous gas meter with a probe. This all worked perfectly.

What I have done so fas is plug in the phone jack of the data cable in the P1 port of the smart meter (Iskra ME382) and disable sensor 1 to 5 as the P1 port should be recognized automagically. This didnt result in any pulses being registered. It just showed the heartbeat every 15 min. in the log. Strange thing I did noticed after connecting the phone jack is that the Flukso would reboot at least every 3 hours or so. When this happens there is something in the log about a user nobody that logged in. With the data cable unplugged again from the smart meter it does not do this. So for some reason connecting to the P1 port results in reboots of the Flukso. In another topic I read that the data cable supplied with the Flukso was faulty so I also created another one from a (working) phone data cable. This resulted in the same behaviour, no pulses and random reboots of the Flukso with a maximum uptime of a couple of hours.

Oh, I don't think it's relevant but just to be sure. I edited the firewall so I can access the Flukso through Wifi.

I really have no clue where to continue from here so it would be great if someone could help me out so I can finally get this up and running. Below is a clean syslog from right after a manual reboot. I will add a log where with a heartbeat and a random reboot later in the next post.

[log cleaned as it's no relevant anymore]

gebhardm's picture

Did you check that the RJ11-connector is connected correctly?
Quote from the description in the shop-ad:"Connect the Rj11 pins as follows: pin 2 > 6a, pin 3 > 5-, pin 4 > free, pin 5 > 6b. Pin numbering is from left to right when the RJ11 connector has its lip pointing upwards."
If reversed, there is no GND potential to the data link and data-lines are opposite direction what may be the cause for the reboot according to Murphy's law or Dogbert's tech support ;-)
Your log just shows the boot sequence without any sensor registering
Regards, Markus

jghaanstra's picture

Thank you for your reply Markus.

I did check the pins of the data cable after noticing it wasnt working. The description from the shop isnt quite clear to me though as the data cable that came with the Fluksometer only has four pins/wires and the description is talking about pin 2 to 5. So I cant really check if it is connected correctly but I just assumed that Flukso knew what they where doing when creating this cable and supplying it with my Fluksometer. I also copied that same setup (also a 4-pin cable) on a data cable I created myself (to make sure the data cable that came with the Fluksometer wasnt broken).

I did notice that the Fluksometer hasnt rebooted with the data cable I created myself. But that could very well be because no sensor was detected at all as you mention from the log above. This evening I will reconnect the data cable that came with the Flukso and post another log after a reboot occurs.

(Or should I get myself a 6 pin data cable?)

gebhardm's picture

It is "to be precise" 6P4C - 6 pins with 4 connected... - the RJ-something is quite misleading

jghaanstra's picture

Thanx for clarifying that. The data cable was already connected when I unpackaged the Fluksometer. But of course it could be that they made a mistake during assembly. I'll triple check everything once again with these new insights.

jghaanstra's picture

Well, after fiddeling with it I now have different errors in my syslog. Still no pulses though. Below is a new log. One thing that isnt clear to me is that the following line in the instruction: "from left to right when the RJ11 connector has its lip pointing upwards". Does this mean when viewing it flat on the table and the lip pointing upwards or having the connector in your hands and turning it around so the lip (and the hole for the cable) is pointing upwards.

  1. Jan  1 00:00:30 flukso-eb6e6c user.info kernel: ath_rate_minstrel: max segment size in the mrr set to 6000 us
  2. Jan  1 00:00:30 flukso-eb6e6c user.warn kernel: Atheros HAL provided by OpenWrt, DD-WRT and MakSat Technologies
  3. Jan  1 00:00:30 flukso-eb6e6c user.warn kernel: wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
  4. Jan  1 00:00:30 flukso-eb6e6c user.warn kernel: wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
  5. Jan  1 00:00:30 flukso-eb6e6c user.warn kernel: wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
  6. Jan  1 00:00:30 flukso-eb6e6c user.warn kernel: wifi0: H/W encryption support: WEP AES AES_CCM TKIP
  7. Jan  1 00:00:30 flukso-eb6e6c user.info kernel: ath_ahb: wifi0: Atheros 2317 WiSoC REV1: mem=0xb0000000, irq=3
  8. Jan  1 00:00:30 flukso-eb6e6c user.warn kernel: IRQ 3/wifi0: IRQF_DISABLED is not guaranteed on shared IRQs
  9. Jan  1 00:00:32 flukso-eb6e6c user.info sysinit: sysctl: short write
  10. Jan  1 00:00:35 flukso-eb6e6c user.info sysinit: udhcpc (v1.15.3) started
  11. Jan  1 00:00:41 flukso-eb6e6c user.info sysinit: Sending discover...
  12. Jan  1 00:00:44 flukso-eb6e6c user.info sysinit: Sending discover...
  13. Jan  1 00:00:44 flukso-eb6e6c user.info sysinit: Sending select for 192.168.0.124...
  14. Jan  1 00:00:44 flukso-eb6e6c user.info sysinit: Lease of 192.168.0.124 obtained, lease time 268435455
  15. Jan  1 00:00:45 flukso-eb6e6c user.info sysinit: Loading defaults
  16. Jan  1 00:00:45 flukso-eb6e6c user.info sysinit: udhcpc: ifconfig ath0 192.168.0.124 netmask 255.255.255.0 broadcast 192.168.0.255
  17. Jan  1 00:00:47 flukso-eb6e6c user.info sysinit: udhcpc: setting default routers: 192.168.0.100
  18. Jan  1 00:00:47 flukso-eb6e6c user.info sysinit: Loading synflood protection
  19. Jan  1 00:00:48 flukso-eb6e6c user.info sysinit: udhcpc: setting dns servers: 192.168.0.100
  20. Jan  1 00:00:48 flukso-eb6e6c user.info sysinit: udhcpc: setting dns domain: WORKGROUP
  21. Jan  1 00:00:48 flukso-eb6e6c user.info sysinit: Adding custom chains
  22. Jan  1 00:00:51 flukso-eb6e6c user.notice ifup: Allowing Router Advertisements on wan (ath0)
  23. Jan  1 00:00:51 flukso-eb6e6c user.info sysinit: Loading zones
  24. Jan  1 00:00:54 flukso-eb6e6c user.notice root: starting ntpclient
  25. Jan  1 00:00:56 flukso-eb6e6c user.info sysinit: Loading forwardings
  26. Jan  1 00:00:56 flukso-eb6e6c user.info sysinit: Loading redirects
  27. Jan  1 00:00:56 flukso-eb6e6c user.info sysinit: Loading rules
  28. Jan  1 00:00:57 flukso-eb6e6c user.info sysinit: Loading includes
  29. Jan  1 00:00:57 flukso-eb6e6c user.info sysinit: Optimizing conntrack
  30. Jan  1 00:00:57 flukso-eb6e6c user.info sysinit: Loading interfaces
  31. Jan  1 00:00:58 flukso-eb6e6c user.info firewall: adding wan (ath0) to zone wan
  32. Jan  1 00:01:00 flukso-eb6e6c user.info firewall: adding lan (eth0) to zone lan
  33. Jan  1 00:01:04 flukso-eb6e6c daemon.info avahi-daemon[939]: Found user 'nobody' (UID 65534) and group 'nogroup' (GID 65534).
  34. Jan  1 00:01:04 flukso-eb6e6c daemon.info avahi-daemon[939]: Successfully dropped root privileges.
  35. Jan  1 00:01:04 flukso-eb6e6c daemon.info avahi-daemon[939]: avahi-daemon 0.6.29 starting up.
  36. Jan  1 00:01:04 flukso-eb6e6c daemon.warn avahi-daemon[939]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
  37. Jan  1 00:01:04 flukso-eb6e6c daemon.warn avahi-daemon[939]: Failed to initialize inotify: Function not implemented
  38. Aug  9 17:35:51 flukso-eb6e6c daemon.info avahi-daemon[939]: Loading service file /etc/avahi/services/flukso.service.
  39. Aug  9 17:35:51 flukso-eb6e6c daemon.info avahi-daemon[939]: Loading service file /etc/avahi/services/http.service.
  40. Aug  9 17:35:51 flukso-eb6e6c daemon.info avahi-daemon[939]: Loading service file /etc/avahi/services/mqtt.service.
  41. Aug  9 17:35:51 flukso-eb6e6c daemon.info avahi-daemon[939]: Loading service file /etc/avahi/services/ssh.service.
  42. Aug  9 17:35:51 flukso-eb6e6c daemon.info avahi-daemon[939]: Joining mDNS multicast group on interface ath0.IPv4 with address 192.168.0.124.
  43. Aug  9 17:35:51 flukso-eb6e6c daemon.info avahi-daemon[939]: New relevant interface ath0.IPv4 for mDNS.
  44. Aug  9 17:35:51 flukso-eb6e6c daemon.info avahi-daemon[939]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.255.1.
  45. Aug  9 17:35:51 flukso-eb6e6c daemon.info avahi-daemon[939]: New relevant interface eth0.IPv4 for mDNS.
  46. Aug  9 17:35:51 flukso-eb6e6c daemon.info avahi-daemon[939]: Network interface enumeration completed.
  47. Aug  9 17:35:51 flukso-eb6e6c daemon.info avahi-daemon[939]: Registering new address record for 192.168.0.124 on ath0.IPv4.
  48. Aug  9 17:35:51 flukso-eb6e6c daemon.info avahi-daemon[939]: Registering new address record for 192.168.255.1 on eth0.IPv4.
  49. Aug  9 17:35:51 flukso-eb6e6c daemon.info avahi-daemon[939]: Registering HINFO record with values 'MIPS'/'LINUX'.
  50. Aug  9 17:35:51 flukso-eb6e6c cron.info crond[946]: crond: crond (busybox 1.15.3) started, log level 1
  51. Aug  9 17:35:52 flukso-eb6e6c daemon.info avahi-daemon[939]: Server startup complete. Host name is flukso-eb6e6c.local. Local service cookie is 3322676600.
  52. Aug  9 17:35:52 flukso-eb6e6c authpriv.info dropbear[953]: Running in background
  53. Aug  9 17:35:53 flukso-eb6e6c daemon.info avahi-daemon[939]: Service "Secure Shell on flukso-eb6e6c" (/etc/avahi/services/ssh.service) successfully established.
  54. Aug  9 17:35:53 flukso-eb6e6c daemon.info avahi-daemon[939]: Service "MQTT Broker on flukso-eb6e6c" (/etc/avahi/services/mqtt.service) successfully established.
  55. Aug  9 17:35:53 flukso-eb6e6c daemon.info avahi-daemon[939]: Service "Web Server on flukso-eb6e6c" (/etc/avahi/services/http.service) successfully established.
  56. Aug  9 17:35:53 flukso-eb6e6c daemon.info avahi-daemon[939]: Service "Flukso RESTful API on flukso-eb6e6c" (/etc/avahi/services/flukso.service) successfully established.
  57. Aug  9 17:35:54 flukso-eb6e6c user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
  58. Aug  9 17:35:59 flukso-eb6e6c daemon.info dnsmasq[985]: started, version 2.55 cachesize 150
  59. Aug  9 17:35:59 flukso-eb6e6c daemon.info dnsmasq[985]: compile time options: IPv6 GNU-getopt no-DBus no-I18N DHCP TFTP
  60. Aug  9 17:35:59 flukso-eb6e6c daemon.info dnsmasq-dhcp[985]: DHCP, IP range 192.168.255.100 -- 192.168.255.250, lease time 12h
  61. Aug  9 17:35:59 flukso-eb6e6c daemon.info dnsmasq[985]: using local addresses only for domain lan
  62. Aug  9 17:35:59 flukso-eb6e6c daemon.info dnsmasq[985]: reading /tmp/resolv.conf.auto
  63. Aug  9 17:35:59 flukso-eb6e6c daemon.info dnsmasq[985]: using nameserver 192.168.0.100#53
  64. Aug  9 17:35:59 flukso-eb6e6c daemon.info dnsmasq[985]: using local addresses only for domain lan
  65. Aug  9 17:35:59 flukso-eb6e6c daemon.info dnsmasq[985]: read /etc/hosts - 2 addresses
  66. Aug  9 17:35:59 flukso-eb6e6c daemon.info dnsmasq-dhcp[985]: read /etc/ethers - 0 addresses
  67. Aug  9 17:36:03 flukso-eb6e6c user.info sysinit: 1376069763: mosquitto version 1.1.3 (build date 2013-05-19 23:48:09+0200) starting
  68. Aug  9 17:36:03 flukso-eb6e6c user.info sysinit: 1376069763: Config loaded from /etc/mosquitto/mosquitto.conf.
  69. Aug  9 17:36:03 flukso-eb6e6c user.info sysinit: 1376069763: Opening ipv6 listen socket on port 1883.
  70. Aug  9 17:36:03 flukso-eb6e6c user.info sysinit: 1376069763: Warning: Address family not supported by protocol
  71. Aug  9 17:36:03 flukso-eb6e6c user.info sysinit: 1376069763: Opening ipv4 listen socket on port 1883.
  72. Aug  9 17:36:03 flukso-eb6e6c user.info sysinit: using gpio pin 5
  73. Aug  9 17:36:03 flukso-eb6e6c user.info sysinit: using gpio pin 5
  74. Aug  9 17:36:03 flukso-eb6e6c user.info sysinit: using gpio pin 7
  75. Aug  9 17:36:04 flukso-eb6e6c user.info sysinit: Daemon returned 0 as return value.
  76. Aug  9 17:36:04 flukso-eb6e6c daemon.info supd[1008]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
  77. Aug  9 17:36:04 flukso-eb6e6c user.info sysinit: Daemon returned 0 as return value.
  78. Aug  9 17:36:04 flukso-eb6e6c daemon.info spid[1011]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
  79. Aug  9 17:36:04 flukso-eb6e6c user.info sysinit: Daemon returned 0 as return value.
  80. Aug  9 17:36:04 flukso-eb6e6c daemon.info fluksod[1014]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
  81. Aug  9 17:36:05 flukso-eb6e6c user.info sysinit: Daemon returned 0 as return value.
  82. Aug  9 17:36:05 flukso-eb6e6c daemon.info parsed[1019]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
  83. Aug  9 17:36:12 flukso-eb6e6c user.info sysinit: 1376069772: New connection from 127.0.0.1.
  84. Aug  9 17:36:12 flukso-eb6e6c user.info sysinit: 1376069772: New client connected from 127.0.0.1 as fluksod.
  85. Aug  9 17:36:13 flukso-eb6e6c user.info heartbeat[1022]: POST <a href="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:" title="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:">https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:</a> 200
  86. Aug  9 17:36:14 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  87. Aug  9 17:36:14 flukso-eb6e6c user.info sysinit: 1376069774: Socket read error on client fluksod, disconnecting.
  88. Aug  9 17:36:15 flukso-eb6e6c user.info sysinit: 1376069775: New connection from 127.0.0.1.
  89. Aug  9 17:36:15 flukso-eb6e6c user.info sysinit: 1376069775: New client connected from 127.0.0.1 as fluksod.
  90. Aug  9 17:36:24 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  91. Aug  9 17:36:24 flukso-eb6e6c user.info sysinit: 1376069784: Socket read error on client fluksod, disconnecting.
  92. Aug  9 17:36:25 flukso-eb6e6c user.info sysinit: 1376069785: New connection from 127.0.0.1.
  93. Aug  9 17:36:25 flukso-eb6e6c user.info sysinit: 1376069785: New client connected from 127.0.0.1 as fluksod.
  94. Aug  9 17:36:34 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  95. Aug  9 17:36:34 flukso-eb6e6c user.info sysinit: 1376069794: Socket read error on client fluksod, disconnecting.
  96. Aug  9 17:36:36 flukso-eb6e6c user.info sysinit: 1376069796: New connection from 127.0.0.1.
  97. Aug  9 17:36:36 flukso-eb6e6c user.info sysinit: 1376069796: New client connected from 127.0.0.1 as fluksod.
  98. Aug  9 17:36:44 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  99. Aug  9 17:36:44 flukso-eb6e6c user.info sysinit: 1376069804: Socket read error on client fluksod, disconnecting.
  100. Aug  9 17:36:46 flukso-eb6e6c user.info sysinit: 1376069806: New connection from 127.0.0.1.
  101. Aug  9 17:36:46 flukso-eb6e6c user.info sysinit: 1376069806: New client connected from 127.0.0.1 as fluksod.
  102. Aug  9 17:36:54 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  103. Aug  9 17:36:54 flukso-eb6e6c user.info sysinit: 1376069814: Socket read error on client fluksod, disconnecting.
  104. Aug  9 17:36:55 flukso-eb6e6c user.info sysinit: 1376069815: New connection from 127.0.0.1.
  105. Aug  9 17:36:55 flukso-eb6e6c user.info sysinit: 1376069815: New client connected from 127.0.0.1 as fluksod.
  106. Aug  9 17:37:04 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  107. Aug  9 17:37:04 flukso-eb6e6c user.info sysinit: 1376069824: Socket read error on client fluksod, disconnecting.
  108. Aug  9 17:37:05 flukso-eb6e6c user.info sysinit: 1376069825: New connection from 127.0.0.1.
  109. Aug  9 17:37:05 flukso-eb6e6c user.info sysinit: 1376069825: New client connected from 127.0.0.1 as fluksod.
  110. Aug  9 17:37:14 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  111. Aug  9 17:37:14 flukso-eb6e6c user.info sysinit: 1376069834: Socket read error on client fluksod, disconnecting.
  112. Aug  9 17:37:15 flukso-eb6e6c user.info sysinit: 1376069835: New connection from 127.0.0.1.
  113. Aug  9 17:37:15 flukso-eb6e6c user.info sysinit: 1376069835: New client connected from 127.0.0.1 as fluksod.
  114. Aug  9 17:37:24 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  115. Aug  9 17:37:24 flukso-eb6e6c user.info sysinit: 1376069844: Socket read error on client fluksod, disconnecting.
  116. Aug  9 17:37:25 flukso-eb6e6c user.info sysinit: 1376069845: New connection from 127.0.0.1.
  117. Aug  9 17:37:25 flukso-eb6e6c user.info sysinit: 1376069845: New client connected from 127.0.0.1 as fluksod.
  118. Aug  9 17:37:34 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  119. Aug  9 17:37:34 flukso-eb6e6c user.info sysinit: 1376069854: Socket read error on client fluksod, disconnecting.
  120. Aug  9 17:37:35 flukso-eb6e6c user.info sysinit: 1376069855: New connection from 127.0.0.1.
  121. Aug  9 17:37:35 flukso-eb6e6c user.info sysinit: 1376069855: New client connected from 127.0.0.1 as fluksod.
  122. Aug  9 17:37:44 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  123. Aug  9 17:37:44 flukso-eb6e6c user.info sysinit: 1376069864: Socket read error on client fluksod, disconnecting.
  124. Aug  9 17:37:45 flukso-eb6e6c user.info sysinit: 1376069865: New connection from 127.0.0.1.
  125. Aug  9 17:37:45 flukso-eb6e6c user.info sysinit: 1376069865: New client connected from 127.0.0.1 as fluksod.
  126. Aug  9 17:37:54 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  127. Aug  9 17:37:54 flukso-eb6e6c user.info sysinit: 1376069874: Socket read error on client fluksod, disconnecting.
  128. Aug  9 17:37:55 flukso-eb6e6c user.info sysinit: 1376069875: New connection from 127.0.0.1.
  129. Aug  9 17:37:55 flukso-eb6e6c user.info sysinit: 1376069875: New client connected from 127.0.0.1 as fluksod.
  130. Aug  9 17:38:04 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  131. Aug  9 17:38:04 flukso-eb6e6c user.info sysinit: 1376069884: Socket read error on client fluksod, disconnecting.
  132. Aug  9 17:38:05 flukso-eb6e6c user.info sysinit: 1376069885: New connection from 127.0.0.1.
  133. Aug  9 17:38:05 flukso-eb6e6c user.info sysinit: 1376069885: New client connected from 127.0.0.1 as fluksod.
  134. Aug  9 17:38:14 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  135. Aug  9 17:38:14 flukso-eb6e6c user.info sysinit: 1376069894: Socket read error on client fluksod, disconnecting.
  136. Aug  9 17:38:15 flukso-eb6e6c user.info sysinit: 1376069895: New connection from 127.0.0.1.
  137. Aug  9 17:38:15 flukso-eb6e6c user.info sysinit: 1376069895: New client connected from 127.0.0.1 as fluksod.
  138. Aug  9 17:38:24 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  139. Aug  9 17:38:24 flukso-eb6e6c user.info sysinit: 1376069904: Socket read error on client fluksod, disconnecting.
  140. Aug  9 17:38:25 flukso-eb6e6c user.info sysinit: 1376069905: New connection from 127.0.0.1.
  141. Aug  9 17:38:25 flukso-eb6e6c user.info sysinit: 1376069905: New client connected from 127.0.0.1 as fluksod.
  142. Aug  9 17:38:34 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  143. Aug  9 17:38:34 flukso-eb6e6c user.info sysinit: 1376069914: Socket read error on client fluksod, disconnecting.
  144. Aug  9 17:38:35 flukso-eb6e6c user.info sysinit: 1376069915: New connection from 127.0.0.1.
  145. Aug  9 17:38:35 flukso-eb6e6c user.info sysinit: 1376069915: New client connected from 127.0.0.1 as fluksod.
  146. Aug  9 17:38:44 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  147. Aug  9 17:38:44 flukso-eb6e6c user.info sysinit: 1376069924: Socket read error on client fluksod, disconnecting.
  148. Aug  9 17:38:45 flukso-eb6e6c user.info sysinit: 1376069925: New connection from 127.0.0.1.
  149. Aug  9 17:38:45 flukso-eb6e6c user.info sysinit: 1376069925: New client connected from 127.0.0.1 as fluksod.
  150. Aug  9 17:38:54 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  151. Aug  9 17:38:54 flukso-eb6e6c user.info sysinit: 1376069934: Socket read error on client fluksod, disconnecting.
  152. Aug  9 17:38:56 flukso-eb6e6c user.info sysinit: 1376069936: New connection from 127.0.0.1.
  153. Aug  9 17:38:56 flukso-eb6e6c user.info sysinit: 1376069936: New client connected from 127.0.0.1 as fluksod.

jghaanstra's picture

And when doing these commands through SSH I see correct output now ... but I still dont see pulses in the log. Just these errors as mentioned above (and the cable that came with the FLM was incorrect. Wire 3 was cut instead of wire 4 which was connected to the FLM and which is why I had no registered sensor :-| ) .

  1.     root@flukso-87d245:~$ /etc/init.d/flukso restart
  2.     root@flukso-87d245:~$ /etc/init.d/flukso stop  
  3.     root@flukso-87d245:~$ cat /dev/ttyS0

voogt's picture

See my earlyer post, same issue. You have a liander smart meter? Some how you have to sent a start signal. Bart (icarus) can help you with it. For me now it works for rasberry pi the same problem.

Regards Richard

jghaanstra's picture

It's supplied by Enexis but it's an Iskra ME382 which is the same as yours. Bart seems to be on vacation till the 15th of august so I guess I have to be patient a little more.

I'm not sure if it's the same problem as yours though. The cat /dev/ttyS0 command through SSH gives me proper output where I can see pulses with proper values. So the FLM is able to receive the signal from the P1 port of the smart meter but somehow it's not getting submitted to the Flukso website presumably because of that error in the log every few seconds:

  1. Aug  9 17:38:54 flukso-eb6e6c daemon.err fluksod[1014]: /usr/sbin/fluksod.lua:164: attempt to index local 'data' (a nil value)
  2. Aug  9 17:38:54 flukso-eb6e6c user.info sysinit: 1376069934: Socket read error on client fluksod, disconnecting.
  3. Aug  9 17:38:56 flukso-eb6e6c user.info sysinit: 1376069936: New connection from 127.0.0.1.
  4. Aug  9 17:38:56 flukso-eb6e6c user.info sysinit: 1376069936: New client connected from 127.0.0.1 as fluksod.

jghaanstra's picture

Not sure if it helps but this is the output from 'cat /dev/ttyS0':

  1. /ISk5\2ME382-1003
  2.  
  3. 0-0:96.1.1(4B413650303035313436333833343133)
  4. 1-0:1.8.1(00122.531*kWh)
  5. 1-0:1.8.2(00013.882*kWh)
  6. 1-0:2.8.1(00195.596*kWh)
  7. 1-0:2.8.2(00012.108*kWh)
  8. 0-0:96.14.0(0001)
  9. 1-0:1.7.0(0000.00*kW)
  10. 1-0:2.7.0(0000.24*kW)
  11. 0-0:17.0.0(0999.00*kW)
  12. 0-0:96.3.10(1)
  13. 0-0:96.13.1()
  14. 0-0:96.13.0()
  15. 0-1:24.1.0(3)
  16. 0-1:96.1.0(4730303135353631303131353136363133)
  17. 0-1:24.3.0(130810120000)(00)(60)(1)(0-1:24.2.1)(m3)
  18. (00019.556)
  19. 0-1:24.4.0(1)

I'm pulling the plug from the FLM now in the hope Bart can help me out when he gets back from vacation.

voogt's picture

I am also on holiday whats your firmware version? 223?

You have the same meter so it should work, maybe just a reset

jghaanstra's picture

Yes, I'm on the 223 firmware. I'll have Bart look at it before doing a reset. Hopefully he knows what is going on and why these errors appear instead of the pulses that are clearly being send to the FLM.

jghaanstra's picture

Has anyone spotted Bart already after the holiday break, this issue still hasnt been addressed and I get no response to a support question through the contact form ... :-|

icarus75's picture

I just had a quick peek at your FLM. Everything seems to be up and running, your configuration is correct and has been synchronised with the Flukso server. However, I'm not seeing the same output on /dev/ttyS0 as what you posted in the comment on 10/08. This is the 'rubbish' coming out now:

  1. root@flukso-eb6e6c:~$ hexdump -C /dev/ttyS0
  2. 00000000  00 00 00 00 00 00 7f 04  00 00 00 00 00 7e 08 00  |.............~..|
  3. 00000010  00 7e 00 00 00 7f 00 00  00 00 00 00 00 00 00 00  |.~..............|
  4. 00000020  00 00 7f 00 00 00 7e 00  00 00 00 00 00 7e 00 00  |......~......~..|
  5. 00000030  00 00 00 00 7f 00 00 00  7e 04 00 00 7f 00 00 00  |........~.......|
  6. 00000040  00 00 00 00 00 00 7f 00  00 00 7e 00 00 00 7e 00  |..........~...~.|
  7. 00000050  00 00 7f 00 00 00 7e 00  00 00 00 00 00 00 00 00  |......~.........|
  8. 00000060  7f 00 00 00 00 00 00 7f  00 00 00 7e 00 00 00 7f  |...........~....|
  9. 00000070  00 00 00 7f 00 00 00 7f  00 00 00 7e 00 00 00 7f  |...........~....|

I don't know whether your FLM is currently hooked up to the smart meter. But please check the connection again, and report back via the forum.

Cheers
/Bart

jghaanstra's picture

Thank you for the response. I currently do not have the FLM connected to the P1 port because of the syslog was being flooded with these error messages every second, which just didnt seem good to just leave it like that for days.

I will plug it back in up this evening (CET) and leave it like that for you to check.

jghaanstra's picture

Where you able to check it now it's plugged in Bart?

icarus75's picture

Seems you're generating so much solar power that your electricity counter is reporting negative values. I've got a code fix for that, although there's still an issue plotting negative values on the flukso.net charts. That one will be fixed at a later date. Could you reboot the FLM once more?

jghaanstra's picture

We received the solar panels right before summer and the smart meter a little later then that. So yes, our generation is currently higher then our consumption. This will change during the winter but it's good to see you have a code fix so I dont have to wait until then to start using my FLM.

I have executed a reboot command through SSH, I still see the same errors in the syslog though. Not sure if these should have been gone now.

icarus75's picture

I've just patched /usr/sbin/fluksod.lua with commit [1]. It's now accepting negative counter values. You can double-check via the syslog, or by subscribing to the mosquitto broker:

  1. root@flukso-eb6e6c:~$ mosquitto_sub -v -t /sensor/#

If you're talking about this error in the syslog:
  1. Sep  5 07:40:19 flukso-eb6e6c user.info sysinit: 1378366819: Socket read error on client mosqsub/1659-flukso-eb6, disconnecting.

Don't worry. It's just a mosquitto client subscription timing out. It's re-established once fluksod has new readings to post to the broker.

[1] https://github.com/flukso/flm02/commit/47c59e1841a9d891e0d28fc4075913034...

jghaanstra's picture

Awesome, I see pulses in the syslog and my dash is showing results. Thank you for your efforts!

jghaanstra's picture

Could you explain me something?

The p1 telegram contains values for current power consumption and current return delivery. Both can not be negative values. If the generation is higher then the consumption the current return delivery will kick in and the current power consumption is zero. The P1 telegram also contains the values of the total taken and returned peak/off-peak power. These are not negative as well as far as I can see.

I did subscribe to the Mosquitto broker and I do see negative values there but I dont seem to comprehend what is going on based on the values and data in the P1 telegram. So my questions are:

- What value is exactly currently negative and where does the mosquitto broker gets this data from?
- What value is the smart-main exactly showing on the dash, consumption or consumption - generation? I guess it's the latter because if it only was consumption it could never be negative. It would be great of both could be plotted on the dash.
- Once the dash will be fixed to show negative values, will this also effect the api for pvoutput.org.

What I'm trying to achieve with the FLM is that I can show a graph on pvoutput.org that plots the energy consumption on my pvoutput.org. Because of these negative values I'm not sure if the data seen now is what I'm looking for.

http://pvoutput.org/intraday.jsp?id=22252&sid=20144

icarus75's picture

The FLM subtracts the production reading from the consumption one. So a negative consumption means net injection into the grid. If you want to obtain gross production and consumption values, you could add a DIN rail meter in series with the inverter. You'll then have to do a little arithmetic to get gross consumption based on the aforementioned readings.