Despite abysmal weather here in lockdown Northeast of England, it’s been a good weekend. One of my biggest daily challenges when running the blog is effortlessly, wirelessly transferring image from my Android phone to my PC for inclusion in the blog or elsewhere.
As many of you will know, the above is do-able with wires but for quick blog updating, I’ve gone to tremendous lengths to make image editing and transfer as painless as possible so I can concentrate on actual blog writing. To that extent I’ve settled in recent times on Snapseed on the phone to easily crop, straighten and brighten up images (no, reaaly, don’t underestimate this package – and Microsoft’s Your Phone to transfer them to my PC. Add Greenshot screen grabber into the mix and I can have an image ready in seconds to drop into WordPress for the blog.
That is, until “Your Phone” decides not to work, or restricts the number of files – or some other petty limitation – all of which can get annoying REAL fast. So imagine my delight when I discovered the Dell Mobile Connect App for PC and phone – only to have the wind blown out of my sails when I discovered it is only good for new (2018+) Dell machines. Well, never one to give up easily – I found a way around it.
Down in the comments you will see some great alterenative suggestions including a new one on me – ANDSMB (Google Play Store) – for now I’m happy with the Dell offering as above.
The modern ESP-01
And armed with THAT good start to my Sunday afternoon, I opened up the mail from Saturday – a couple of FOC bits and pieces from blog subscriber Ian Sexton…
I started with no idea what the software was on that particular ESP01 – I did know it was/is a 1 MB board, not the old-fashioned an utterly useless 512K version. I also know it arrived with a sketch on it that supports OTA with an ID of ESP01_OTA, as it appeared on my mobile phone as an access point – and there the mystery deepened – it was not ESP-GO or Tasmota or Espurna…
A quick visit to my mobile phone browser and a check on the web page that appeared at 192.168.4.1 produced a reference to the sketch ESP01_OTA_LED_PIEZO.ino – and given that there are only a couple of usable pins on the ESP01 I guessed that meant piezo sensor and a lamp… other than that I had no clue.
I already knew that if by putting Tasmota on it I could, in addition, make use of the serial pins (that’s a good thing). Between the ESP01 and Ian’s back-board which allows the board to use a standard USB connector for power, this looks like a useful improvement over the original ESP01.
At this point, Ian wrote back to me to confirm that the software that arrived with the board was nothing more than a blank canvas – problem solved. Ian also reminded me that this device with the right software will run i2c – and I have the very thing -Tasmota will do that. Out with the FTDI. Success.
And while we’re talking about Tasmota, I realised this morning (May 4 2020) that the easiest way to upgrade a single Tasmota (assuming the OTAURL is set correctly) is to simply go to the console and use
and that the simplest way to upgrade a bunch of them (assuming that the GROUPTOPIC is set correctly) is to send an MQTT message (in my case from Node-Red)
topic: (in my case tasmotas or kitchenlights)
As the development version of Tasmota at the time of writing (updated May 15, 2020) is now 220.127.116.11 (Fred) – I figured now is as good a time as any to upgrade my entire installation. Done.
As an aside, I also just realised that when sticking with Espressif SDK 2.2 for ESP-GO, I’m not alone – as Tasmota is using the same – and here’s me feeling guilty for never upgrading to the 3.0 Esp SDK version. Oh, well. Check the docs file for Tasmota.
And finally, Antonio (Mr Shark) has alerted me to Tasmota for ESP32 – maybe time to take a look?