I'm kind of like you in that I moved on to pursue this a different way. I did a factory reset on my Obi202, and reentered everything via the ObiTalk portal, which I plan to use until this gets revolved or goes away. And I want to see how the other half lives using the ObiTalk portal on a device under active configuration.
BTW, if you have any exports from the recent past, take a look and see if there's a mystery reboot code.
Another mystery on my Obi202, I see that it's now using "3.0.1 (Build: 3741)", whereas before it was on 3722
. Hum? For those not on using the ObiTalk portal, I see this in the FirmwareURL field: "IF ( $FWV < 126.96.36.19941 ) FWU http://www.obihai.com/firmware/OBi202-3-0-1-3741.fw
" -- noticed via the Web Server-Based Local Configuration (Device IP address), not seen via the ObiTalk portal.
Note to self: Evidently when using the ObiTalk portal you get new firmware updates like this, without having to do anything or click anything, and before they are made available via ***6. An educated guess is these updates are not new feature releases (or they'd be announced as such), they are bug fixes.