Dev corner

Calling all engineers, tinkerers, hackers and geeks.

502 Bad Gateway

Hi

When connecting to api.flukso.net on iOS, I tend to receive 502 Bad Gateway responses while e.g. querying

https://www.flukso.net/api/sensor/91f8991e2d96b408320f32beab385df6?versi...

with proper token and version set in HTTP headers. This is the response I'm getting:

  1. <html>
  2.         <head><title>502 Bad Gateway</title></head>
  3.         <body bgcolor="white">
  4.         <center><h1>502 Bad Gateway</h1></center>
  5.         <hr><center>nginx/1.0.10</center>
  6.         </body>
  7. </html>

Any clue?

Thanks
Tom

Query sensors (iPhone app)

Hi

I'm working on an iOS (iPhone & iPad) app, and was wondering whether it was possible to query the devices given a username/password combination on the Flukso-site.

Or is there another way to query the local device for sensors?

Thanks
Tom

Query with Flukso chart comparisons

Hi Bart,

we have a situation where a mate and I compare our household energy use via
the Flukso charting tool.

We have only just realized that when we are both logged into Fluko, the charts which should be identical are in fact quite different.
While the spikes in energy use look about right, the scale on the side of the chart and the averages, maximum readings etc, are all quite different.

I have taken a screen capture of both charts (when logged in concurrently from different machines) at almost precisely the same time and attached it as an example.

Callback on api.flukso.net

I'm developing a windows phone 7 api for flukso. As all http communication needs to be implemented async, i would need the callback to make a difference between the call's and responses.
This works perfectly on the local / reamtime requests, but not on the request to api.flukso.net.
Is this normal behavior or am I missing something out? The manual seems to make notice of the callback parameter for history requests to the api.

401 Unauthorized

The API has been working fine for a while now, but has recently been giving me a 401 unauthorized. I'm in the middle of developing a chrome plugin so I'm sure I call the API frequently. Is there a chance that I've been blocked? Or possibly a problem?