Dev corner

Calling all engineers, tinkerers, hackers and geeks.

Totalisers

Hello Everybody,

It`s difficult to maken a totaliser for electricial/water/gas ?

I think everybody like it to see what the use every month/year/day on engergy.

Thanks,
Sven

Different data values returned for same timestamp

Hi, I've been playing around with the Flukso API and I came across this strange behavior. There appears to be 2 different values returned for the same time value (in minute resolution) if the start and end date difference are large enough. For example, using:

curl -k -v -X GET -H "Accept: application/json" -H "X-Version: 1.0" -H "X-Token: 93cf47a00945ab989e3626a55275e145" "https://api.flukso.net/sensor/804b2ff9d7f048a23c853d46b19b25a0?start=1341895106&end=1341905106&resolution=minute&unit=watt"

The resulting last few data points are:

[1341904740,393],[1341904800,393],[1341904860,393],[1341904920,387],[1341904980,400],[1341905040,387],[1341905100,393],[1341905160,"nan"]

However using:

curl -k -v -X GET -H "Accept: application/json" -H "X-Version: 1.0" -H "X-Token: 93cf47a00945ab989e3626a55275e145" "https://api.flukso.net/sensor/804b2ff9d7f048a23c853d46b19b25a0?start=1341805106&end=1341905106&resolution=minute&unit=watt"

The results are:

[1341904740,229],[1341904800,355],[1341904860,302],[1341904920,378],[1341904980,310],[1341905040,291],[1341905100,295],[1341905160,"nan"]

I'm just curious as to why different data values are returned as the only difference in the 2 calls are the start and end time values.

Thanks for your help.

Handig functie voor op het dash

Gaan er nog meerdere functies komen, zoals bv een totaliser per dag per maand per jaar zou supper handig zijn voor controle energie factuur!

Gr sven

sensors gas and water

Mijn gasmeter werkt met een spiegeltje in de laatste "0", weet iemand welke sensor ik daar moet gebruiken?
Bij mijn water heb ik een ronddraaiendende metalen halve maan.....deze valt te detecteren met een proxiswitch.
Hallsensoren(magneetsensoren, zoals de A1314) werken bij mij dus niet...
Bijkomend probleem: op de flukso moeten deze gevoed worden via 3.3V en deze zijn moeilijk te vinden, heb ook liever geen zin om te beginnen knoeien met weerstanden enz...
Weet iemand of een NO contact zodat je de +- kortsluit op de flukso mag, anders zou ik een bestaande proxi op 24V een microrelais kunnen laten opkomen die de pulsen doorstuurd?

MQTT: MQ Telemetry Transport

I recently learned about MQTT (http://mqtt.org) a light weight sensor connectivity protocol. Played a bit with it and it looks really cool. The guy who invented the protocol uses it to monitor his house (like way before anyone else) and has a nice presentation (but a bit outdated) about it on Slideshare (http://www.slideshare.net/andysc/the-house-that-twitters).

It's basically a message broker with some publishers and subscribers. Mosquitto (http://mosquitto.org) is an open source implementation of the protocol.

It looks like MQTT is built for things like Flukso sensors so I thought it would be nice to bring up the topic here. I am planning to look at it and see what cool things one can do combining Flukso and Mosquitto but maybe this post can help someone developer who wants to hack something together.

Bart, did you ever consider MQTT for Flukso?