I live in NL, have 3-phase service, and will install a PV plant soon and want to monitor it. And if I want to monitor the PV plant production I should also monitor the house electric consumption. But it seems a challenge to separate the two; my father is an EE and is visiting soon so he can help me if the breakerbox and clamps and/or addition of DIN rail meters with S0 ports could be arranged in a satisfactory manner.

But, there may be a better solution because I will also receive a smart meter which will allow reading from the P1 port both consumption and delivery to the grid, as well as gas consumption. When searching for P1 port monitoring solutions with Flukso not much came up other than https://www.flukso.net/files/presentations/flukso.20121026.sensorboard.pdf

So question is, can Flukso v2 available now interrogate the P1 port? Or is this something that could be enabled with a sw update? Or, if this will not be possible with the v2 HW, any suggestions for the simplest topology?

Thanks!
Chris

Is this a healthy looking logfile?

Does this means it reboots every 15 minutes? That can not be a good thing?

please advise

hugo

syslog:

Dec 17 17:00:01 flukso-00757e cron.info crond[933]: crond: USER root pid 2983 cmd /usr/bin/fntp
Dec 17 17:05:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3000 cmd /usr/bin/heartbeat 0
Dec 17 17:05:03 flukso-00757e user.info heartbeat[3001]: POST https://api.flukso.net/device/00757e836fb97579b15600ce488e0fda: 200
Dec 17 17:15:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3011 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 17:15:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3012 cmd /usr/bin/fntp
Dec 17 17:30:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3031 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 17:30:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3033 cmd /usr/bin/fntp
Dec 17 17:45:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3051 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 17:45:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3054 cmd /usr/bin/fntp
Dec 17 18:00:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3071 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 18:00:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3074 cmd /usr/bin/fntp
Dec 17 18:05:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3091 cmd /usr/bin/heartbeat 0
Dec 17 18:05:03 flukso-00757e user.info heartbeat[3092]: POST https://api.flukso.net/device/00757e836fb97579b15600ce488e0fda: 200
Dec 17 18:15:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3102 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 18:15:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3103 cmd /usr/bin/fntp
Dec 17 18:30:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3122 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 18:30:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3125 cmd /usr/bin/fntp
Dec 17 18:45:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3142 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 18:45:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3144 cmd /usr/bin/fntp
Dec 17 19:00:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3162 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 19:00:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3165 cmd /usr/bin/fntp
Dec 17 19:05:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3182 cmd /usr/bin/heartbeat 0
Dec 17 19:05:02 flukso-00757e user.info heartbeat[3183]: POST https://api.flukso.net/device/00757e836fb97579b15600ce488e0fda: 200
Dec 17 19:15:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3193 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 19:15:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3195 cmd /usr/bin/fntp
Dec 17 19:30:01 flukso-00757e cron.info crond[933]: crond: USER flukso pid 3219 cmd [ $(/usr/bin/fcheck; echo $?) -ne 0 ] && reboot
Dec 17 19:30:01 flukso-00757e cron.info crond[933]: crond: USER root pid 3222 cmd /usr/bin/fntp

Hi there,

I have issues seeing data on the dash. I have logged in and I do see my two sensors registered.

Only no data not even a graph background, just empty(see attached screenshot).

What could be wrong?

hugo

Hallo,

Ik probeer de flukso via de wired verbinding direct uit te lezen omdat ik via de site geen waarden in de grafiek zie.

Als ik de handleiding volg en mijn sensor id invul krijg ik onderstaande meldingiemand enig idee?

Dank

hugo

hugo@vaio ~ $ curl -v "http://192.168.255.1:8080/sensor/
0371cbb8ce1802f29b156ca5760bd544?version=1.0&interval=minute&
unit=watt&callback=realtime"
* About to connect() to 192.168.255.1 port 8080 (#0)
* Trying 192.168.255.1... connected
> GET /sensor/ HTTP/1.1
> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: 192.168.255.1:8080
> Accept: */*
>
< HTTP/1.1 403 Forbidden
< Connection: close
< Content-Type: text/plain
< Transfer-Encoding: chunked
<
Access to this resource is forbidden
* Closing connection #0

Hi,
I'm trying to get access my data directly on the flukso server through the RESTful api.
I use the manual and replace the X-token and sensor-token by my own tokens. I get the following message (tokens modified).

roel@Enif:~$ curl -k -v -X GET -H "Accept: application/json" -H "X-Version: 1.0" -H "X-Token: dd9aa4835a7a4e0965f51c227bb1****" "https://api.flukso.net/sensor/399e12b79d5f9bf90491af155ca8****interval=month&unit=watt"

* About to connect() to api.flukso.net port 443 (#0)
* Trying 178.79.177.6...
* connected
* Connected to api.flukso.net (178.79.177.6) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using RC4-SHA
* Server certificate:
* subject: C=BE; O=Flukso; CN=api.flukso.net; emailAddress=admin@flukso.net
* start date: 2012-05
* expire date: 2014-05
* common name: api.flukso.net (matched)
* issuer: C=BE; O
* SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
> GET /sensor/399e12b79d5f9bf90491af155ca8****interval=month&unit=watt HTTP/1.1
> User-Agent: curl/7.27.0
> Host: api.flukso.net
> Accept: application/json
> X-Version: 1.0
> X-Token: dd9aa4835a7a4e0965f51c227bb1****
>
* additional stuff not fine transfer.c:1037: 0 0
* HTTP 1.1 or later with persistent connection, pipelining supported
< HTTP/1.1 400 Bad Request
< Server: nginx/1.0.10
< Date: Sat, 15 Dec 2012 21:30:34 GMT
< Connection: keep-alive
< Content-Length: 0
<
* Connection #0 to host api.flukso.net left intact
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):

Any idea what's going wrong?
Thanks,
roel