I’ve soldered the headers, with chip on top – looked natural. But the GPIO silkscreen markings got hidden at the bottom of the module – i think it’s better for development to have them on top, shorted out text is OK.

There are two rows left on both sides of the the breadboard.

So, let’s see what the extra flash is good for.

SSL – Is SSL the right solution for #IoT?

FOTA – What about the FOTA upgrades security?

Going down the rabbit hole it seems that the MOST important and hard part of a IoT implementation is to get the security right. So the extra flash will present an opportunity to test to some ideas on how to do it. And we need it for the service we are building – it’s just vital to have and to have it right.

A simple i2c driver for the Microchip’s TCN75A thermometer – supports up to 8 thermometers. Driver works in one shot mode which is suitable for battery powered operations. The chip is with quite good specs for its price.

After a lots of lots of wasted hours debugging an I2C driver it came out that the noise from the connected cheep USB2TTL converter is way too much. Would have lost months without the help of the new DS1054z scope i’ve got.

While working on a current project i’ve faced an issue with code reuse. Espressif sdk allows only one interrupt handler for all GPIOs. That’s fine for monolithic code but since we like modular code a dispatcher comes handy.

The little inconvenience i’ve had was like this. I wanted to use the drivers/key.c code but it does use the data argument , so i’ve had to modify it to use a global variable. So i can call it from my own interrupt handler. And that is ugly.

Spend last weekend trying to make apache with proxy_wstunnel to work.
The solution recommended is to add this in the apache config:
ProxyRequests off
ProxyPass /mqtt ws://127.0.0.1:8082
ProxyPassReverse /mqtt ws://127.0.0.1:8082

ESP8266 is a highly integrated chip designed for the needs of a new connected world. It offers a complete and self-contained Wi-Fi networking solution, allowing it to either host the application or to offload all Wi-Fi networking functions from another application processor.

The chip have both certifications FCC and CE. You can sell your products to the mass market.

The FCC identifier : 2AC7Z-ESP8266EX

The CE opinion number : TCF-1933CC14

Internet of things survey from an year ago at Wi-Fi.org shows very big numbers for smart enabled devices.

Why WiFi for the Internet of Things A.K.A Smart Devices?

Two words – security and availability.

While WiFi is know to be at the edge of the secure protocols it offers much more protection than regular 315/433Mhz devices. 2.4GHz keyboards were hacked recently too.

There are two main types of data that the IoT devices process:

Sensor Data – It may be sensitive or not but can only be used for analysis. Can cause trouble but only indirectly.

Actuators Control – If hijacked can make a real mess – what if you use a wireless door lock?

WiFi and the esp8266 chip provide enough security with the TKIP and AES engines built in /is there ever completely secure system? / to control your appliances.