Installation

Questions about installing and configuring a Fluksometer.

Different readings for same consumption

I have installed 2 Flukso devices (a V2 and V2B), running the same firmware (232). Now, this weekend I have bought 3 additional clamps in order to measure a separate circuit. To make sure everything works though, I have put the new clamps in exactly the same position as the existing 3 clamps. Situation: I now have 2 Flukso devices, measuring , exactly the same consumption - well at least they should be.
What I now see, is that there is a difference between both measurements of a bit less than 100 Watts... (the V2B measuring a bit more than the V2). How can that be? Can that be due to inaccuracies in the clamp measurements? Or differences between the A and B devices? Or influences from wires outside the clamps?
PS I have 3 phases at home, 240 Volts (not 400 - so my settings are at 133 Volts in the sensors).

Minimum wattage of the power clamps

Hello everybody.

I'm new here. I have installed 2 current clamps.
1 on the main cable, for my total consumption of energy.
1 on the solarpanels cable.

When the solarpanels starts up my inverter begins with 1 watt and goes on to almost 2000 watt. But when i see THE grafics on flukso, iT start with almost 200 watt?!

When my house consumption is around 400 watt, and my solarpanels give around 400 watt back, THE clamp of the Total consumption must be around 0 watt!!!
But both of THE clamps have no grafics between 0 and 200 watt!?!
So whats happening?

Flukso dies periodically with increasing frequency

Hi,

A few days ago, one of our Fluksos went off-line suddenly and was not reachable over WiFi. I switched it off and on and it came back quickly. The next time this happened it didn't get back online after a few minutes so I just tried to swap the power supply and it eventually came up with the new one. I thought the power supply was getting a bit "tired" and was glad to have things repaired that way. Now today there was another hang and I had to switch it off and on again which worked.
On next hang, I will be getting the thing off the wall and check if all internal connections are seated well or if visually a problem can be seen. But I am prepared to replace the device and I wanted to ask what this does to the data already in flukso.net from this device:
Can I just delete the device from my account, add a new one with the same sensors attached and continue with my data stream or is there some intervention from Flukso needed to make sure my measurements up until now are not lost ?

Thanks - Christoph

No meter readings from Landis + Gyr ZMF110 smart meter over P1

Since this is about a different meter I created a new entry but it looks like I have a similar/same problem as posted about the Kaifa smart meter. All connections seem to be OK but no meter readings.

My installation:

  • brand new Landys+Gyr ZMF110 smart meter with P1 connector
  • brand new flmv2b
  • flm connected via LAN
  • P1 connected on sensor 6 with cable provided (I didn't see any options to configure P1 under "Sensor" so nothing enabled)
  • I see gas and electricity sensors on flukso.net
  • I see my device ID (version 244) on flukso.net
  • status page 3x OK (System, network, sensor config sync -- latest yesterday evening 22:56)
  • All my device are in the 192.168.178.* local network segment as is the fluksometer

Despite all the good signs I don't see any electricity or gas readings in my dash. After a few seconds I see Error - The call for sensor smart-main experienced a timeout. You are probably not in the same local network as the FLM.

What to do next?

gebhardm/flmdisplay

Hi Gebhardm,

I installed the flmdisplay/combined/raspi_setup.mdon Rpi and I got this error at running, but the page is open and not data.

The difference between raspi_setup.mdon and my Rpi is that I installed RASPBIAN 2014-09-09 instead of the 2014-06-20 that is not available.

~/node_modules/thing-client$ node test.js
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see

Many thanks for your help.