- Did such a glaring problem escape them? If it did, then they failed to test their product properly, which they might not have if they hadn't been working on other products already. If it didn't, then they chose to send out the product anyway, not mentioning the bug, hoping it would be overlooked. Either way, I'm not impressed.
- Their programmer couldn't work on the GO firmware; he was too busy working on the prototype Geek Pulse and prototype Geek Wave ... unless LH chose to crowdfund those products without any idea of what the firmware would be, in which case they really jumped the gun.
With Larry's comments about the ESS9018K2M I wouldn't be surprised if they uncovered a bug in the silicon. If that is the case then solving the problem can become quite complicated, the manufacturer needs to identify the issue, file an errata sheet and workaround. Not uncommon with firmware design and breaking new ground and can be challenging to solve and uncover the root cause... Usually if the issue is in the low level drivers it can be fixed quite quickly.
Keenly following the issue as I'm interested in the GO1000.