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
What are the corresponding /sensor/xyz/counter values? Are they transmitted? The gauge is just a local view; FLM normally deals with energy, thus Wh.
Using an FLM that is intended for household consumption for energy measurement in the plant category I regard rather naive...
counter is of type uint32_t counter; so this actually is a strange thing, icarus75 should take a look at...
Hi,
I don't have the corresponding counter values at hand, but they are correct as well.
Nevertheless nothing is transferred to the server. Whatever request I make, I only get 'NaN' values.
The strange thing is that when I switch off a unit and switch on again the next day, sometimes a chunk of data is displayed.
I'm wondering if this could be related to the fact that I have two FSM02A connected to the same account and in the beginning both had the same sensor names.
Is there a way to fully delete the server data for these units?
Kind Regards,
Frederik
What does the syslog say - here the corresponding POSTs should be recorded; are values delivered? Is the "pass on to server" on?
Hi,
This is an extract from the syslog:
...
Mar 5 09:58:02 flukso-68827b daemon.info fluksod[643]: POST https://api.flukso.net/sensor/61a847784eb15be02b9a b12bde8b1d6a: 200
Mar 5 09:58:03 flukso-68827b daemon.info fluksod[643]: POST https://api.flukso.net/sensor/44363c3bd479bf47f9d3 c70290dd3315: 200
Mar 5 09:58:03 flukso-68827b daemon.info fluksod[643]: processed pulse 44363c3bd479bf47f9d3c70290dd3315:139401 3483:114374825
Mar 5 09:58:07 flukso-68827b daemon.info fluksod[643]: processed pulse 61a847784eb15be02b9ab12bde8b1d6a:139401 3487:114467975
...
Mar 5 09:59:57 flukso-68827b daemon.info fluksod[643]: processed pulse 61a847784eb15be02b9ab12bde8b1d6a:139401 3597:114487225
Mar 5 09:59:58 flukso-68827b daemon.info fluksod[643]: processed pulse 44363c3bd479bf47f9d3c70290dd3315:139401 3598:114394950
Mar 5 10:00:01 flukso-68827b cron.info crond[550]: crond: USER root pid 1708 cmd /usr/bin/heartbeat 0
Mar 5 10:00:01 flukso-68827b cron.info crond[550]: crond: USER root pid 1709 cmd /usr/bin/fcheck
Mar 5 10:00:02 flukso-68827b daemon.info fluksod[643]: processed pulse 61a847784eb15be02b9ab12bde8b1d6a:139401 3602:114488100
Mar 5 10:00:03 flukso-68827b daemon.info fluksod[643]: processed pulse 44363c3bd479bf47f9d3c70290dd3315:139401 3603:114395825
...
What do you mean with "pass on to server" setting? We do have enabled the 'private' mode for the data.
Regards,
Frederik
"Mar 5 09:58:03 flukso-68827b daemon.info fluksod[643]: POST https://api.flukso.net/sensor/44363c3bd479bf47f9d3 c70290dd3315: 200" - the "send to flukso.net" feature seems enabled; as seen from some other threads there may be a hick-up in synching with the server; so, just as a try, save the sensor settings again to make the "sync with server" renewal... Just guessing...
Hello.
I seem to have a similar problem.
At 9 in the morning the curve suddenly drops on my solarpanelsreading!
This is the only pulsmeter i have, the others seem fine.
I can still get readings from the solapanels when i look at the minutegraph but if i switch to hours its no longer visible.
Same for the readings i get from the server, nothing for the solarpanels.
/Peter
Today the values dissapears at 9 and comes back at 13:00.
All the time i'm able to se the values in the minute view but not in the hour view!
/Peter
For me the problem seemed to be in the s0 equipment, upgraded the firmware and problem is no more!