I second (third, fourth, whatever) this. Have not yet asked to be rolled back, but thinking about it (trade-off is the annoying nag screen to update). From the Plex app code that was referenced elsewhere, it seems way too complex for an amateur but very doable for a full-time coder, in which I am surprised, like the rest of you, that Tablo hasn't just arranged on their own to update it. (Obviously they know their API so much better than anyone else.)
But then I remain awed and amazed that CycleJ has been their enormously thoughtful and skillful volunteer developer with Tablo Ripper. By now they really should have fully folded him/it into the family and made it the "official" way to archive. The only thought to the contrary I have had is that perhaps for copyright reasons they do not want to officially endorse archiving (others' example notwithstanding).
If Plex for Tablo had a similarly capable and dedicated person not only would Plex be shining for Tablo, but their remote-connect issues would be moot (at least for those with an always-on processing unit in addition to the Tablo), as largely would be drive-migration issues, and the overall offering platform would be much more robust and appealing.
I too find this Plex-Tablo Ripper-Plex eco-system superb and hugely reinforcing. I hope daily that Tablo will continue to have a big enough business to keep going (since we depend, among other things, on their server to be able to operate much of the device), on CycleJ's health and availability (to keep up with changes to their API, beyond his amazing continual and rapid improvements), and for Plex to remain viable for remote connection (since Tablo periodically loses connectivity for devices long enough away from "home").