Hey guys,

Have had some issues with our internet connection over the last two days - its still currently offline and i'm tethering my mobile to get online to ask this question:

I know that the fluksometer will buffer its recordings during an internet outage and when the connection is resumed, it will bulk upload all of the recorded data in one hit to flukso.net dash.

My question is how does say pvoutput.org go when pulling data from flukso.net after said internet outage?

Earlier I managed to get the flukso to connect to my mobile phone's hotspot and it bulk uploaded the data. The flukso.net dash shows the recorded readings pretty much complete for the last two days its been offline - but pvoutput seems to have only imported records from approx 7pm onwards from flukso and didn't import any of the days consumption/generation, that shows on the flukso.net dash

Any ideas?

Cheers
Adam

Hey,

I'm having 2 phases that i would like to monitor. So i bought 2 clamps of 50. However I couldn't find any documentation how the settings should be for the sensor (Current clamp ports & Number of phases).

For the moment, i've got 'clamp ports: 3' en 'phases: 1'.
When i put someting else, i don't have any output of the sensors?
So i think that these settings are correct?

But i've got some doubts of the values that i see. :$
Is there any information who these settings should be?

When I power my modem/router off then back on again I loose connection to my Flukso ( no globe LED ) and the only way to get it to connect again it to power cycle the Flukso
Is this normal?
How do i fix this problem?
Cheers.

Dear FSM experts,

I encounter a strange problem: our FSM is connected to internet (ping to Flukso server is successful, from SSH session on FSM we can ping flukso.net) and measured values provided on the local API (MQTT) show correct measured values.
However these measurements do not get (correctly) to the server.

This is what the (locally connecting) MQTT client shows:
/sensor/44363c3bd479bf47f9d3c70290dd3315/gauge [1393862764,3055286,"W"]
/sensor/44363c3bd479bf47f9d3c70290dd3315/gauge [1393862765,3201220,"W"]
/sensor/44363c3bd479bf47f9d3c70290dd3315/gauge [1393862767,3052326,"W"]
/sensor/44363c3bd479bf47f9d3c70290dd3315/gauge [1393862768,3201220,"W"]

This is the same data on the server:
https://api.flukso.net/sensor/44363c3bd479bf47f9d3c70290dd3315?version=1...
[[1393862760,"nan"],[1393862820,"nan"],[1393862880,"nan"],[1393862940,"nan"],[1393863000,"nan"]

Further on there are no datapoints shown on the server.

This behavior is identical on both our FLM02A units (both upgraded to firmware 232).
Note that we have re-configured these systems quite a lot.
We also tried a full reset but no improvements.

Any idea on the cause?
Is there anything specific that can be checked on the FSM itself (e.g. with SSH session)?

Kind Regards,

Frederik

Hi,

In our final setup we need to make use of a quite big meterconstant (between 200 and 875).
I noticed in a test setup that with a meterconsant of 100 data was reported correctly, but when using 875 measured value is incorrect.
Could there be an overflow problem when using big meterconstants?

Kind Regards,

Frederik