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

Hi Guys,

Are there other Brazilians out there using FLM?

I am comparing my FLM charts against Bart´s chart but I would like to compare against others people in my region (who shall have similar home appliances, cooling system and weather conditions).

Best regards,
Benito

hello,
I have a Dresser gas meter of type NPL12.

The data sheet of this meter can be found here

There is on this meter a connection for remote reading with LF pulse emitter.
Is there any chance of being able to use the gas probe with it? Any alternative solution?

Thanks for your help.

herve