(for some reason the first part of my post got dropped i.s.o. get used as summary)
Bart, I quite enjoyed your talk at Fosdem, and I look forward to getting my hands on the hardware (might even see where I can help out software-wise, being an embedded dev myself). Also looking forward to the V2 which could support an external sensor (yes, it was me who asked about that).
Now I need to check which hardware revision I have and if I can get my daughterboard upgraded :D
FOSDEM 2014, Track "Internet of things": The Fluksometer as an IoT hub
For FLM upgrade (v2) see https://www.flukso.net/content/fluksometer-v2a-b-upgrade
Thanks, I had by now found the upgrade package in the shop.
So I need to send in my flukso :(
- extended downtime
- new serial means discontinued graphs?
I had hoped it was a matter of installing another daughterboard.
Just installing another daughter board was the hope; but Bart told that it is necessary to upgrade the Dragino bootloader as well, so sending in is his option to not deal with "amateurishly bricked devices" afterwards...
Fair enough... and what about the effect on my graphs & configuration?
I suppose that this is no issue as the flukso.net account seems the base for the graphs, not the device... (to be verified); config is on the FLM itself, this is to be re-set, then (I suppose) on name-equivalence the graphs are consistent again (again, to be verified)
Right. Maybe I should just get a second Flukso to experiment with and the extra inputs would kinda be welcome too.
@petur Overall feedback on the FluksoKube at FOSDEM'12 was quite positive. I've uploaded the slides of the talk. There's now a kube feature branch on Github where the kube daemon for the FLM is being written. This kubed will take care of device management of the kubes (pairing, over-the-air firmware upgrades, etc) and data packet decoding/encoding. The hardware itself still requires further testing. The first radio packets have already been transmitted though. I'll be blogging about development progress on the Kube in the near future. Right now, it's back to the coding trenches.
PS: I've updated this forum post's title to get the name right.
Thanks, looking forward to the future of this.
Don't know if I need to know about any doctor visits of your family (second-to-last slide) ;)
I want one! [joke]Looks it can detect overdue doctor's receipts too. [/joke]
Bart, any update on the kube?
(looking at the FOSDEM schedule suddenly made me remember your talk)
@petur The kubed daemon on the Fluksometer now supports kube pairing, sensor auto-provisioning and over-the-air firmware upgrades (OTA). I've been making good progress on the FluksoKube as well. You can track development progress on the Kube's Github repo.
I will not be presenting at FOSDEM 2015. But I'll try to attend some talks on Saturday.
Yes, I did see the github activity, but without diving into the whole project it's difficult to see where it's at ;)
Will be at FOSDEM on both days, chances are low to meet without specific hour+place, but if I do see you I'll buy you a beer or coffee.
Just a quick update: temp, humidity, pressure, light, movement and vibration are now up-and-running with current draw in sleep mode under 20uA. A first test batch will be kicked-off in the coming weeks.
Is there a ETA for the kubes?
I am contemplating adding some wireless sensors to measure temperature, humidity, ... in the home.
If Fluksokubes are not too far out that would be my preferred solution, otherwise I'll try to hack something together myself.