View Single Post
Posts: 207 | Thanked: 482 times | Joined on Mar 2016
#225
Originally Posted by abranson View Post
Afaik the appmessage protocol is identical in v2 and v3. The code is pretty much identical between rockwork/rockpool and pebbled.
Ok, then we need logs from watches to understand why it's nacking appmsg. The message is fairly simple - simple scalar value, nothing what could potentially be wrongly serialized.



Does anyone have annotated firmware disassembly accidentally? To look for possible reasons to nack.

Last edited by ruff; 2016-04-08 at 06:49.
 

The Following User Says Thank You to ruff For This Useful Post: