Hi everyone, we hope those of you who have received a dash have had a chance to start playing with it and we appreciate the patience of those still waiting for theirs.
I wanted to let you know that we have released a firmware update utility that you can see on this page: https://content.konekt.io/docs/hardware/konekt-dash/updating-dash/
Most of the dashes that shipped last week have firmware 0.9 on them and we have 0.9.1 out now. I’d recommend updating before doing anything else.
Feel free to use this thread for any questions about the update process. We’re working on making the docs better and getting everything cleaned up so we’re eager to hear your suggestions.
Oh and scroll down to the User Program Code Examples section on this page for the latest version of the stock user program. If the USB serial feature isn’t working it may be because you have an old version here.
We’re going to add a changelog to the next update.
There are default topics set by our Cloud as data comes in. The ability to add additional topics is supported in the socket API, but os a feature that is going to be available in the next release.
We are almost finished with our advanced functionality library for Arduino, which will enable you to call functions that will set topic. It’s just finishing testing and some final features. Some interesting remote control functionality will be available in the release of the library as well.
Good news for Beta board users: We are putting the finishing touches on the updater app to update your bootloaders and bring you up-to-date with all the current features!
At that point, Beta boards and main Production boards will be in sync with one another for being able to run the latest firmware releases.
Did this functionality arrive? I’ve looked through the examples and documentation that I’ve found, and not finding anything relevant. Quite possibly I’m missing something obvious.
e.g. For an asset tracking device, I might want to send regular short messages, either to confirm location or just to phone home and kick the timeout on the heartbeat. These messages might be routed via email, or not at all. The same device might then want to send an urgent message, which I’d want to route via SMS. Setting the topic seems the way to handle this, but I’m not seeing a way to achieve it.