I’m confident it will perform much better than the BeUno.. but tell you what.. if you remove your BeUno and send it to me so we can do a head-to-head comparison (and publish here), we’ll send you a Thermo free 
Interested? If so, DM me or @tac0s and we’ll make the arrangements.
8 Likes
4 Likes
Make sure you boys let me watch when you.. Compare antennas 
4 Likes
Thats an offer that is hard to say no to, but unfortunately, the math isnt mathing well enough.
Shipping + installation of the new Thermo, assuming that i do the removal myself, come to about 200€, for which i could purchase a Thermo myself.
So, while i would love to contribute to your research, that is a bit to expensive for me.
4 Likes
I would like to clarify something:
This will do temp (obviously), but also work with the vivokey vault and spark actions apps?
1 Like
Vault, yes, Spark Actions, no (at least for now).
2 Likes
just to add further clarity, the Thermo units are keyed and work with the Verify API which VivoKey Vault uses. Other apps and services which use the Verify API could, in theory, be used with the Thermo.
The only reason Actions is not supported is that we had to decide on the eventual target market for such a product, and sadly for the community, VivoKey aims to bring products like Thermo to the broader market - a market that expects a smooth primary experience.. and you don’t get much smoother than this;
The app opens itself from an NFC background scan and gets the temperature immediately. This is done on Android by using the AAR NDEF record type.
An Android Application Record (AAR) in an NDEF message forces an Android device to open a specific app, bypassing the general tag dispatch system. The NDEF record contains the package name (e.g.,
com.vivokey.thermo), which the system uses to launch the app or open the Google Play Store if not installed.
Because of this, the default Actions URL would never even be allowed to open for anyone with an Android phone who scanned your Thermo.
2 Likes
I am excited to see if I can get some iOS code working with this!
3 Likes
It has been a long week, apologies.
So it is locked into that app, correct, no way to change it?
Would it be reasonably possible for one of the following to occur:
1- I get one, install it, unlock it (this is where my doubt kicks in), and change what the NDEF blocks have on them
2- You (DT) ship an “unlocked thermo” using VK’s hardware either as custom work or its own product where I could put good ol dngr.us/rick in the ndef
I don’t like being tied to a particular entity (company), but I want to clarify before I start debating another install. The temp reading would certainly be useful, but I wouldn’t mind opening an app in advance to do so.
2 Likes
Agreed. Interesting product but I won’t buy one unless I am able to change the ndef record. Keep it the way it is by default but allow users to change it if they want to, otherwise we are needlessly limiting functionality.
Currently yes.. however they are keyed in such a way that it should technically be possible to re-write the NDEF using a special VivoKey app (which doesn’t exist at this point). The app would perform a mutual auth with the Verify API which would allow for NDEF memory space updates during that session, but the memory space would remain locked.. it would just be writable after auth for the NFC session. In short, we would need to release a “VivoKey Writer” kind of app for Thermo. This is not out of the question though.
This I understand.. however the lack of NDEF writability is definitely not being “locked in” as it has nothing to do with the primary function - reading temperature. In fact you could write your own app to get the temperature data from the sensor, it is not locked out or secured with keys (like BeUno). It’s just a feature of the NFC transponder you can’t change.. so I would consider it to be more of a missing feature than being locked into something. This is partly why we don’t even talk about data sharing or NDEF at all on the product page.. it’s not considered a feature of the product.
That said, I will mull over the “VivoKey Writer” app and what will be necessary to change in our Verify API to accomplish this.
4 Likes
Coming from the perspective of a biohacker customer, this makes sense as a take / perspective. Coming from the perspective of a company that has an entire strategy behind every aspect of the way the product was developed over the last two years and the plan to bring that product to market, there is a very strong purpose behind the decision… “needlessly” is completely subjective. You don’t see a need for this, but we do.. and there was much consideration put into making this decision.. it wasn’t made lightly.
3 Likes
I think this is the reason.
In my opinion, Vivokey is more targeted towards consumer experience (Plug n’ Play) products rather than biohacking products.
Maybe DT will release an Unlockable xThermo with a Password DNGR to unlock the NDEF
5 Likes
5 Likes
I put a Thermo in my arm to explore just how inaccurate it would be. At a little over a hundred samples it’s still a small dataset. As you can see, there are lots of outliers. When the sample count is substantially higher it will be interesting to see if the tight night grouping holds out.
7 Likes
Where exactly?
1 Like
