Installation

Questions about installing and configuring a Fluksometer.

new installation, something wrong with fases?

by swords on

I've just installed a Flukso and checked the flukso totals with the meters:

The gas and water meter are within 1 liter difference in 11 hours, just perfect.
The power (3 fases on 50 amp) have a difference of 6kW (15 vs 9). It's a standard house from 2008. Any one got a clue on what I'm doing wrong?

Report energy data to own server

by dvrslype on

Hello,

i assume it is possible to report the real time energy data to an own entity instead of reporting to flukso.net. Is the procedure and data format for this described anywhere?

thanks

dvrslype

FLM does not hook online after power outage

by gebhardm on

Today (again) we had a power outage from 14:57 until 15:50; while the SolarLogger went up (so I could detect the interval of power not available), the FLMs (two) did not get into the internet again:

  1. Jan  1 00:02:07 flukso-c13f30 user.err heartbeat[832]: POST "https://api.flukso.net/device/c13f3032d717d096065d8cf524116524": -2
  2. Jan  1 00:02:07 flukso-c13f30 user.err heartbeat[832]: Name or service not known
  3. Jan  1 00:02:07 flukso-c13f30 user.err heartbeat[834]: POST "https://api.flukso.net/device/c13f3032d717d096065d8cf524116524": -2
  4. Jan  1 00:02:07 flukso-c13f30 user.err heartbeat[834]: Name or service not known
  5. ...
  6. Jan  1 01:01:02 flukso-c13f30 user.info heartbeat[963]: POST "https://api.flukso.net/device/c13f3032d717d096065d8cf524116524": 200
  7. Jan  1 01:15:01 flukso-c13f30 cron.info crond[770]: crond: USER root pid 1051 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
  8. Jan  1 01:30:01 flukso-c13f30 cron.info crond[770]: crond: USER root pid 1060 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
  9. Jan  1 01:45:01 flukso-c13f30 cron.info crond[770]: crond: USER root pid 1138 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
  10. Jan  1 02:00:01 flukso-c13f30 cron.info crond[770]: crond: USER root pid 1147 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
  11. Jan  1 02:01:01 flukso-c13f30 cron.info crond[770]: crond: USER root pid 1156 cmd /usr/bin/heartbeat 0
  12. Jan  1 02:01:02 flukso-c13f30 daemon.info dnsmasq[809]: reading /tmp/resolv.conf.auto
  13. Jan  1 02:01:02 flukso-c13f30 daemon.info dnsmasq[809]: using nameserver 82.212.62.62#53
  14. Jan  1 02:01:02 flukso-c13f30 daemon.info dnsmasq[809]: using nameserver 78.42.43.62#53
  15. Jan  1 02:01:02 flukso-c13f30 daemon.info dnsmasq[809]: using local addresses only for domain lan
  16. Jan  1 02:01:02 flukso-c13f30 user.info heartbeat[1157]: POST "https://api.flukso.net/device/c13f3032d717d096065d8cf524116524": 200
  17. Jan  1 02:15:01 flukso-c13f30 cron.info crond[770]: crond: USER root pid 1239 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
  18. Jan  1 02:15:45 flukso-c13f30 user.err fsync[1258]: POST "https://api.flukso.net/sensor/f628158301152d75538cef50736f338a": -150
  19. Jan  1 02:15:45 flukso-c13f30 user.err fsync[1258]: POST "https://api.flukso.net/sensor/d6b662b10579091cbb5f39170c678f5e": -150
  20. Jan  1 02:15:45 flukso-c13f30 user.err fsync[1258]: POST "https://api.flukso.net/sensor/b6ae3286419bf81e3a6fc1d192666286": -150
  21. Jan  1 02:15:45 flukso-c13f30 user.err fsync[1258]: POST "https://api.flukso.net/sensor/0ebaec40f9e80ff39534d745d8e0fd4d": -150
  22. Jan  1 02:15:45 flukso-c13f30 user.err fsync[1258]: POST "https://api.flukso.net/sensor/97eb5fb3198888e1c21ddf7086361269": -150
  23. Jan  1 02:15:45 flukso-c13f30 user.err fsync[1258]: POST "https://api.flukso.net/sensor/413509b4c041f9a4dc3b50f52f0fc62f": -150
  24. Jan  1 02:15:45 flukso-c13f30 user.err fsync[1258]: fsync exit status: 7, synchronisation with Flukso server failed

I did not do a hard reset before re-saving the config from the web-interface to force a sync; but this also showed a "synchronisation with Flukso server failed"...
@Bart: May you have a look before I do a hard reset on both? (this account's FLM is re-powered; gebhardm2 is in the condition after the outage)
The same behavior applies to both my FLMs in the same manner - so they seem to not really like "forced power down" situations; maybe they don't like when the internet modem is not up fast enough...
Strange...
Best regards, Markus