<div dir="ltr"><div>Warning: Speculation based on rumors ahead -></div><div><br></div><div>I've read a ton while waiting for tools to compile. The crib notes:</div><div><br></div><div>All _dash_ buttons will be migrated to V2 hardware. Those still shipping V1 were just slow movers or produced right before hardware changeover.</div><div><br></div><div>The IoT V1 is identical hardware to the dash V1 but the firmware is different as it allows for three states... Short Press, Long Press, and Double Click to be communicated to the server. Dash Buttons _supposedly_ only do short press.</div><div><br></div><div>The IoT V2 is supposed to be unique hardware from the V2 dash, however re-reading, that is speculation based on the rumor the battery will be replaceable. As we know now, the Dash V2 hardware has a replaceable battery if you break the seal. Maybe it will have a different case to allow access to the battery, or maybe someone at Amazon or the mfr. let loose when they saw the battery holder and there are no plans to give end users access. Regardless, if they keep the tri-state button, it would make sense to have different firmware.</div><div><br></div><div>It feels better to have that on the outside. (lol)</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 26, 2016 at 2:06 PM, Shane Trent via TriEmbed <span dir="ltr"><<a href="mailto:triembed@triembed.org" target="_blank">triembed@triembed.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Pete,<div><br></div><div>My Amazon AWS IoT button arrived yesterday (ordered back in May). It appear to be sealed like the other Dash Buttons. Below is a photo of the back showing the model number, which I believe matches the rev 1 Dash Button. Again, I wonder why they used rev 1 hardware for the AWS IoT button. Will the other Dash Buttons all migrate to rev 2 and keep rev 1 with the lithium battery for the IoT Buttons?</div><div><br></div><div>Shane</div><div><br></div><div><img src="cid:1562861724b396fa0553" alt="button front small.jpg" style="max-width:100%"><br></div><div><br></div><img src="cid:156286083765f3430412" alt="button model number.jpg" style="max-width:100%"><br><div class="gmail_quote"><div dir="ltr">On Tue, Jul 26, 2016 at 1:52 PM Pete Soper via TriEmbed <<a href="mailto:triembed@triembed.org" target="_blank">triembed@triembed.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>(excuse the repetition, but this will avoid complete bewilderment
if somebody starts reading about the subject at this point)<br>
</p>
<p>The rev 2 Dash button labeled "JK29LP" on the back has a
replaceable battery if the bottom piece of plastic is cut off.
It's in a dead-plain battery holder (AAA alkaline). It has Atmel
MCU and radio, and is currently opaque with respect to redoing
it's firmware. The rev 1 one labeled "JK76PL" has a lithium
battery that is welded to PCB connections, with ST MCU and
Broadcom radio that is as easy to program as an EMW3162 ('cause
the hardware is identical!). Instructions for the firmware
programming of a rev 1 are on <a href="https://learn.adafruit.com/dash-hacking-bare-metal-stm32-programming/overview" target="_blank">Adafruit</a>.
IMO it would be close to trivial to replace the welded on lithium
battery with a connector for an alternative battery. As Shane
pointed out, the rev 2 is more power efficient to compensate for
the wimpier battery.<br>
</p>
<p>Unless I'm mistaken the IoT button won't be shipped until August
23rd. I'd bet a box of donuts it's based on, if not the same rev 2
Dash guts, something very very close. The <a href="https://aws.amazon.com/iot/button/" target="_blank">AWS web page</a>
describing it says this and the picture makes it seem identical on
the outside, but looking closely at the picture I see where the
removable bottom piece allows getting to the battery holder. This
convenience is not worth $15. :-) It makes perfect sense for the
Dash buttons, which would ordinarily be used at most a couple
dozen times a YEAR, to have the bottom sealed. But with an app
that calls for multiple button pushes a day there may be an issue.
If the guys doing the Dash teardowns can figure out how to swap
the IoT button firmware into a rev 2 Dash button, they'll no doubt
publish that. In the meantime, my wagon is hitched to the rev 2
Dash buttons with the intention of replacing the top layer of
firmware while also playing with the ARP-detection angle for
simple functionality.</p>
<p>One specific goal is to get arpalert installed on the Splatspace
server and donate a button or two for experimentation there. I
can think of multiple immediate uses for these buttons at
Splatspace, but also think blocking their access to Amazon will be
desirable.</p>
<p>-Pete<br>
</p>
<div>On 07/26/2016 12:39 PM, Michael
Monaghan wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Shane,
<div><br>
</div>
<div>If I understand correctly the Amazon IoT button has
different hardware than the Dash button, including a "user
replaceable" battery. The firmware is a bit different as
well. Of course at $20 a pop, one has a little different
expectations.</div>
<div><br>
</div>
<div>Mike</div>
<br>
</div>
</blockquote>
<br>
</div>
_______________________________________________<br>
Triangle, NC Embedded Computing mailing list<br>
<a href="mailto:TriEmbed@triembed.org" target="_blank">TriEmbed@triembed.org</a><br>
<a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" rel="noreferrer" target="_blank">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a><br>
TriEmbed web site: <a href="http://TriEmbed.org" rel="noreferrer" target="_blank">http://TriEmbed.org</a><br>
</blockquote></div></div>
<br>_______________________________________________<br>
Triangle, NC Embedded Computing mailing list<br>
<a href="mailto:TriEmbed@triembed.org">TriEmbed@triembed.org</a><br>
<a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" rel="noreferrer" target="_blank">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a><br>
TriEmbed web site: <a href="http://TriEmbed.org" rel="noreferrer" target="_blank">http://TriEmbed.org</a><br>
<br></blockquote></div><br></div>