Dev corner

Calling all engineers, tinkerers, hackers and geeks.

flm02 firmware

Hi Fluksonians,

This weekend I cloned the flm02 from github and compiled my own flukso firmware with success. For my convenience I did the installation on the flukso (with a dragino v0.6 board) with the fonflash.exe program from wiki.dragino.com, also with success.

But then, the flukso boots, but is very slow. I manage to get an ip address (192.168.255.x), after several minutes, and could retrieve the webpage. Then I observe the following problems:

- Login fails (502 gateway timeout)
- SSH-ing to flukso gives me the impression that it is very busy (avrdude, mosquitto)

Any suggestions how to fix this?

Pieter

Individual graphs in dashboard

Hi Guys,

Little question, is there an option to select individual graphs (so 1 graph from 1 sensor) instead of all graphs together on 1 page?
I really need this cause my idea was to bill tenants in my building based on their KWH usage
and I want to show them their graph.
Now all sensors are together on 1 page, which is really handy for an overview, but it would be very nice if there was a dropdown at the top of the page where I can select just 1 sensor.

Kind regards,

Steven

MQTT standardisation effort

The OASIS standards group is currently working on standardising MQTT, and is looking for public comments from MQTT users, developers, and interested people. I've copied the announcement below for anyone who's interested in providing feedback.

-- Snip --

The OASIS Message Queuing Telemetry Transport (MQTT) TC [1] members have
recently approved a Committee Specification Draft (CSD) and submitted this
specification for 30-day public review:

MQTT Version 3.1.1
Committee Specification Draft 01 / Public Review Draft 01
12 December 2013

Specification Overview:

MQTT is a Client Server publish/subscribe messaging transport protocol. It is
light weight, open, simple, and designed so as to be easy to implement. These
characteristics make it ideal for use in many situations, including
constrained environments such as for communication in Machine to Machine (M2M)
and Internet Of Things (IoT) contexts where a small code footprint is required
and/or network bandwidth is at a premium.

The protocol runs over TCP/IP, or over other network protocols that provide
ordered, lossless, bi-directional connections. Its features include:

- Use of the publish/subscribe message pattern which provides one-to-many
message distribution and decoupling of applications.
- A messaging transport that is agnostic to the content of the payload.
- Three qualities of service for message delivery:
· "At most once", where messages are delivered according to the best
efforts of the operating environment. Message loss can occur. This level
could be used, for example, with ambient sensor data where it does not
matter if an individual reading is lost as the next one will be published
soon after.
· "At least once", where messages are assured to arrive but duplicates
may occur.
· "Exactly once", where message are assured to arrive exactly once. This
level could be used, for example, with billing systems where duplicate or
lost messages could lead to incorrect charges being applied.
- A small transport overhead and protocol exchanges minimized to reduce
network traffic.
- A mechanism to notify interested parties when an abnormal disconnection
occurs.

TC Description:

The OASIS Message Queuing Telemetry Transport (MQTT) TC is developing a
lightweight publish/subscribe reliable messaging transport protocol suitable
for communication in M2M/IoT contexts where a small code footprint is required
and/or network bandwidth is at a premium.

Public Review Period:

The public review starts 13 January 2014 at 00:00 GMT and ends 11 February
2014 at 23:59 GMT.

This is an open invitation to comment. OASIS solicits feedback from potential
users, developers and others, whether OASIS members or not, for the sake of
improving the interoperability and quality of its technical work.

URIs:

The prose specification document and related files are available here:

Editable Source (Authoritative):
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/csprd01/mqtt-v3.1.1-csprd01.doc

HTML:
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/csprd01/mqtt-v3.1.1-csprd01....

PDF:
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/csprd01/mqtt-v3.1.1-csprd01.pdf

ZIP distribution file (complete):

For your convenience, OASIS provides a complete package of the prose
specification and related files in a ZIP distribution file. You can download
the ZIP file here:

http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/csprd01/mqtt-v3.1.1-csprd01.zip

Additional information about the specification and the Message Queuing
Telemetry Transport (MQTT) TC can be found at the TC's public home page:

https://www.oasis-open.org/committees/mqtt/

Comments may be submitted to the TC by any person through the use of the OASIS
TC Comment Facility which can be used by following the instructions on the
TC's "Send A Comment" page, or directly at:

https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=mqtt

Comments submitted by TC non-members for this work and for other work of this
TC are publicly archived and can be viewed at:

https://lists.oasis-open.org/archives/mqtt-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License,
which ensures that the feedback you provide carries the same obligations at
least as the obligations of the TC members. In connection with this public
review of "MQTT Version 3.1.1", we call your attention to the OASIS IPR Policy
[2] applicable especially [3] to the work of this technical committee. All
members of the TC should be familiar with this document, which may create
obligations regarding the disclosure and availability of a member's patent,
copyright, trademark and license rights that read on an approved OASIS
specification.

OASIS invites any persons who know of any such claims to disclose these if
they may be essential to the implementation of the above specification, so
that notice of them may be posted to the notice page for this TC's work.

========== Additional references:

[1] Message Queuing Telemetry Transport (MQTT) TC
https://www.oasis-open.org/committees/mqtt/

[2] http://www.oasis-open.org/who/intellectualproperty.php

[3] http://www.oasis-open.org/committees/mqtt/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#s10.3.1 Non-Assertion Mode

datasheet for current clamps

Hello,
I would like some kind of information about the current clamp bandwidth.
I have a solar charger that switches current to batteries.
I would like to get the RMS value of that current and I am wondering if the current clamps can do that.
So if a datasheet exists, it would be nice to get it!
Thank you,
Manu