Installation

Questions about installing and configuring a Fluksometer.

config ?

Finished the installation today of the Flukso V2.
Water sensor : installed without problems on a Elster V100
Gas sensor : installed with some 'problems' on a Elster BK-G6, had to file off the reedsensor housing top (by hand - don't use powertools) before there was a reliable magnetic contact between the internal magnet and the reedsensor.
Electric (3x220V) : first on the wrong foot by a early picture in the forum of a version 1 installation :-( but after some RTFM .... got it working.

Some things I'm not sure of :
- the calibration of the sensors
- in the syslog there is only one electric sensor reporting, could be normal if I read the manual wright, but to be sure is this correct ? (3 sensor - 3 phase setup)

Luc

Time of Flukso site incorrect

Is it possible to get the time displayed on the site for readings to be correct?
Its off by a good few hours.

The region in user settings is Johannesburg which is correct for the location (South Africa).

The times are off by a few hours though.
I don't have access to the Flukso remotely till i head back to South Africa though, so if I need to change it there will need to wait.

No more readings without any changes

Two nights ago my Flukso 02B suddenly stopped sending data to the Flukso dashboard (and therefor PVOutput.org). It has been running fine for more then a year and I havent touched it during this time. It stopped working in the middle of the night while I was asleep so it has to be some external cause. The Flukso is connected to the P1 port of my Smart Meter. I can access it through the webinterface and SSH fine. In the webinterface the status looks fine as well (wifi connected and ping to flukso succesfull). I rebooted the Flukso in the hope this would fix it but it hasnt. Below is the last part of the syslog, can someone help me indentify the cause and preferably come up with a solution.

  1. Jan  1 00:00:51 flukso-eb6e6c daemon.notice netifd: wan (676): Lease of 192.168.0.124 obtained, lease time 268435455
  2. Jan  1 00:00:52 flukso-eb6e6c daemon.notice netifd: Interface 'wan' is now up
  3. Jan  1 00:00:54 flukso-eb6e6c user.notice firewall: Reloading firewall due to ifup of wan (wlan0)
  4. Jan  1 00:00:55 flukso-eb6e6c authpriv.info dropbear[716]: Running in background
  5. Jan  1 00:01:01 flukso-eb6e6c cron.info crond[667]: crond: USER root pid 738 cmd /usr/bin/heartbeat 0
  6. Jan  1 00:01:06 flukso-eb6e6c user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
  7. Jan  1 00:01:06 flukso-eb6e6c user.notice dnsmasq: Allowing 127.0.0.0/8 responses
  8. Jan  1 00:01:07 flukso-eb6e6c user.info heartbeat[739]: POST <a href="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:" title="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:">https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:</a> 200
  9. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: started, version 2.66 cachesize 150
  10. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth
  11. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq-dhcp[769]: DHCP, IP range 192.168.255.100 -- 192.168.255.249, lease time 12h
  12. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: using local addresses only for domain lan
  13. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: reading /tmp/resolv.conf.auto
  14. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: using nameserver 8.8.4.4#53
  15. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: using nameserver 8.8.8.8#53
  16. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: using local addresses only for domain lan
  17. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq[769]: read /etc/hosts - 1 addresses
  18. Jan  1 00:01:10 flukso-eb6e6c daemon.info dnsmasq-dhcp[769]: read /etc/ethers - 0 addresses
  19. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Found user 'nobody' (UID 65534) and group 'nogroup' (GID 65534).
  20. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Successfully dropped root privileges.
  21. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: avahi-daemon 0.6.31 starting up.
  22. Jan  1 00:01:12 flukso-eb6e6c daemon.warn avahi-daemon[775]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
  23. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Loading service file /etc/avahi/services/flukso.service.
  24. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Loading service file /etc/avahi/services/http.service.
  25. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Loading service file /etc/avahi/services/mqtt.service.
  26. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Loading service file /etc/avahi/services/ssh.service.
  27. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.124.
  28. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: New relevant interface wlan0.IPv4 for mDNS.
  29. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Joining mDNS multicast group on interface br-lan.IPv4 with address 192.168.255.1.
  30. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: New relevant interface br-lan.IPv4 for mDNS.
  31. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Network interface enumeration completed.
  32. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Registering new address record for 192.168.0.124 on wlan0.IPv4.
  33. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Registering new address record for 192.168.255.1 on br-lan.IPv4.
  34. Jan  1 00:01:12 flukso-eb6e6c daemon.info avahi-daemon[775]: Registering HINFO record with values 'MIPS'/'LINUX'.
  35. Jan  1 00:01:14 flukso-eb6e6c daemon.info avahi-daemon[775]: Server startup complete. Host name is flukso-eb6e6c.local. Local service cookie is 3748380999.
  36. Jan  1 00:01:15 flukso-eb6e6c user.info sysinit: setting up led wlan
  37. Jan  1 00:01:16 flukso-eb6e6c daemon.info avahi-daemon[775]: Service "Secure Shell on flukso-eb6e6c" (/etc/avahi/services/ssh.service) successfully established.
  38. Jan  1 00:01:16 flukso-eb6e6c daemon.info avahi-daemon[775]: Service "MQTT Broker on flukso-eb6e6c" (/etc/avahi/services/mqtt.service) successfully established.
  39. Jan  1 00:01:17 flukso-eb6e6c daemon.info avahi-daemon[775]: Service "Web Server on flukso-eb6e6c" (/etc/avahi/services/http.service) successfully established.
  40. Jan  1 00:01:18 flukso-eb6e6c daemon.info avahi-daemon[775]: Service "Flukso RESTful API on flukso-eb6e6c" (/etc/avahi/services/flukso.service) successfully established.
  41. Jan  1 00:01:18 flukso-eb6e6c user.info sysinit: Daemon returned 0 as return value.
  42. Jan  1 00:01:18 flukso-eb6e6c daemon.info supd[793]: Sucessfully started with DEAMON=supd and DAEMON_PATH=/var/run/supd
  43. Jan  1 00:01:19 flukso-eb6e6c daemon.info spid[796]: Sucessfully started with DEAMON=spid and DAEMON_PATH=/var/run/spid
  44. Jan  1 00:01:19 flukso-eb6e6c user.info sysinit: Daemon returned 0 as return value.
  45. Jan  1 00:01:19 flukso-eb6e6c daemon.info fluksod[799]: Sucessfully started with DEAMON=fluksod and DAEMON_PATH=/var/run/fluksod
  46. Jan  1 00:01:19 flukso-eb6e6c user.info sysinit: Daemon returned 0 as return value.
  47. Jan  1 00:01:19 flukso-eb6e6c user.info sysinit: Daemon returned 0 as return value.
  48. Jan  1 00:01:19 flukso-eb6e6c daemon.info parsed[804]: Sucessfully started with DEAMON=parsed and DAEMON_PATH=/var/run/parsed
  49. Jan  1 00:01:24 flukso-eb6e6c user.info heartbeat[809]: POST <a href="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:" title="https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:">https://api.flukso.net/device/eb6e6cc5e66aa2f06f74d89448c50dfc:</a> 200
  50. Jan  1 00:01:25 flukso-eb6e6c daemon.info supd[793]: Received event START for ntp
  51. Dec 10 11:20:06 flukso-eb6e6c cron.err crond[667]: time disparity of 23636838 minutes detected
  52. Dec 10 11:30:01 flukso-eb6e6c cron.info crond[667]: crond: USER root pid 883 cmd /usr/bin/fcheck

Problems with meter readings

Hi guys,

Just bought the Fluksometer v2b with 50A current clamp, gas probe and water probe.

I installed everything but now I am just getting readings from the current clamp.

I connected the current clamp tot the first port as described in the manual.
Port 2 connects to my official solar panel meter (pulse output) but gets no readings. (Problem 1)
Port 3 and 4 were gas and water probe. In the manual there was something about port 4 and 5 that should be suited for water and gas probes, so I changed that, but without any result. (Problem 2)

However, if I understand the manual and webshop correctly, it shouldn't matter, choosing port 2 till 5 for such probes, as long as the number of phases and power clamps is set to 1 for Fluksometer v2b.

To be able to connect these two probes, I had to extend their cable for about 8 meters. Therefor I used a telephonecable with 4 conductors (+ & - for gasprobe and + & - for waterprobe) 0,6m².
Could it be the length of this cable that is causing these problems?
This cable runs alongside other powercables (pv).

Another problem is the differense in readings between the readings from the Flukso and readings from other metering systems. My Chacon and Smappee almost constantly measure about 100 to 200W more or less than the Flukso. (Problem 3).

Further I also have the repeatedly reported problems like no readings per minute, different reactions from Chrome, IE and Firefox to the Flukso website. Mostly Chrome reports "The call for sensor PowerR experienced a timeout. You are probably not in the same local network as the FLM." where as the other browsers don't report anyting.

Suggestions anyone...?

Thanks!

PS: my compass (real compass, not a smartphoneapp) reacts strongly to the watercounter and my GMT G4 gasmeter. So the pulses should be OK.

Din rail s0 meter problems

I have bought a din rail with s0 pulse output, because solar watthours measuring is not a good option with current clamps.
I have a problem. The manual says, the s0 pulse voltage should be between 12 and 27 volts.
But it is 3.23. I have measured, but everything works fine (in my opinion)
The voltage is 3.23 and when there is a pulse, it closes and the voltage is 0.
The count should be good.

BUT...

On my din rail and on my solar converter, the same watthours... (thats perfect)
But the din rail and the dash is not the same!
Dash is around 14% more kwh, than the din rail meter?!?!
So the pulses are given 1000 a kwh, so it should be set 1 in dash.
What could this be? Is the voltage too low?