Thanks for the kind words ... thankfully I have a glass half full disposition most of the time and when something doesn't work that is a new opportunity for me to learn something. So when my I2C solution didn't work, it was an opportunity for me to practice debugging techniques. I had recently bought an 8 channel logic analyzer but hadn't had a great purpose to use it ... so this proved a great reason. Of course, when I failed to see a CLK signal through my new logic analyzer, I wasn't yet sure if I was using THAT new tool correctly ... so there were a lot of permutations to try.
As for this being the biggest problem of the week ... not even close ... but that's ok ... there are countless mysteries associated with our ESP8266 hobby/study ... some unveil themselves quickly, some are as opaque as ever. For example, today I was trying to use the Arduino Eclipse project to build Arduino ESP apps and found that the Arduino Eclipse project doesn't know what to do with ".S" files which I believe are assembler source ... so now I have a new major puzzle on how to get the Arduino Eclipse environment building the Arduino ESP.
We are going to need to think up some new language soon ... as now we have IDEs:
o Command line
o Eclipse
o Arduino
and libraries:
o Espressif SDK
o Arduino ESP
and mappings from some to some of the IDEs to the libraries ...
o Command line Espressif SDK
o Eclipse Espressif SDK
o Arduino IDE with Arduino libraries
o Command line with Arduino libraries
o Eclipse with Ardunio libraries
And I fear this is just the beginning