Here are my personal rules for OBiHAI firmware updates. They have served me well for years. YMMV.

1. If there are no detailed release notes ("misc. bug fixes" is not detailed), I don't update.2. If there are detailed release notes and I don't have any of the problems that the new release fixes, I don't update.3. If there are detailed release notes and there are no new features that add real value for me, I don't update.

I can stare at a yellow triangle for months and months without any effect on my pulse or blood pressure.

Here are my personal rules for OBiHAI firmware updates. They have served me well for years. YMMV.

I believe the only really important rule (for all upgrades, whether they be iOS, Windows, or Obi) is:

0) If you do not have a spare "test mule" device (and many on this forum do, but many do not) and the device is "production" and working well, never, ever, be the first to upgrade. Let others take the plunge and report failures. Anecdotal reports of disaster should be discounted ("stuff" happens), but if there is a rash of complaints, wait for the issues to be understood, resolved, or workarounds provided.

Of course, if everyone waited until someone else tested first there would be no way forward, but there are always those who will serve as a vendors testers (whether they know they are guinea pigs or not).

The last I heard, 4738 was the latest firmware for the 200 and 202 ATAs. I am sticking with 4581 for now, based on several reports of some things not working correctly (for instance, SP4 configurations breaking) on the 4738 firmware. But this begs the question: What if I want to add a GV account to my device or change a GV password today? I need to be on 4738 to do so, right?

So, what's the resolution: Upgrade, change GV, downgrade? Unfortunately, the ins-and-outs of configuring these OBis have become anything but simple since OBiHAI started changing the rules of the game, and what's to prevent them from issuing a future firmware update which prevents downgrading? I really like the self-contained nature of GV under these OBis, but Ryan Tilton's OAUTH2.0 under Asterisk is looking more-and-more desirable as things progress.

Reports of 4738 "breaking" GV configuration functionality proved to be incorrect. The root cause was attempting to use the portal to configure an out-of-warranty device, when it had a down-level version of the firmware, and being told to purchase support to continue. You can simply upgrade the firmware manually/locally, and then return to the portal to continue the GV setup process. I've successfully tested this on two 200s and a 202 without issue.

... and what's to prevent them from issuing a future firmware update which ...

The honest answer is nothing prevents them from issuing a firmware update that does anything (well, achieving world peace is probably beyond their capabilities). Or if they choose (and this would seem to me to be more likely at some point), simply stop issuing firmware updates (and support) completely for their older devices.

But FUD will rarely serve you well.

One must remember that this forum is going to attract those with problems, and issues. For any update/change, there will be some which encounter problems. As we have seen to this point, sometimes there are workarounds, and sometimes "stuff happens" to a particular device (there is a small percentage of iPhone bricking too at every iOS upgrade).

Here are my personal rules for OBiHAI firmware updates. They have served me well for years. YMMV.I can stare at a yellow triangle for months and months without any effect on my pulse or blood pressure.

OK, so what FW version are you currently running?I want to download & save the older FW versions that work while it's still possible.

OK, so what FW version are you currently running?I want to download & save the older FW versions that work while it's still possible.

I am currently enjoying a bottle of OBiHAI 3.0.1 (Build: 4609). It's a full-bodied release with delightful notes of copper and polystyrene and just the slightest hint of ozone.

It pairs well with the bold flavors of DECT 6.0 cordless phones and even an occasional Samsung analog multifunction printer. The label doesn't suggest a serving temperature but I find it is best served between 22 and 26 degrees Celsius.

Transposed more than a few letters there. I have the latest firmware as 4738.

Interestingly, OBiHai has managed to squeeze more from less number of bytes in the firmware. Dating back to October 2012, the firmware has been approx. 13MB in size. I.e., all the way until 4581. The 4738 firmware is 10M.