Looks like a premature observation.
The Arduino/timer seems to reset when the Pi powers up and links but it was a one off. 5 hours stable now
View attachment 643900
[short version]
Does the controllers access point now require a password and if so what its it!]
[Long version]
With just over 4 years of pretty much 24/7 use my original build (above) is starting to get a little unreliable.
This was an undockered installation of Fermentrack running with multiple WiFi ESP8266s
Having seen this a (much overdue) opportunity to upgrade I thought I'd get that sorted today as I'm an old hand at this now (right?)
It would seem I was overambitious!
New PiOS loaded
New dockerised (is that a word?) version of Fermentrack loaded and set up
Used Fermentrack to flash ESP8266 with latest (version 15c) WiFi version of the controller firmware
Setup the controller, wait, what? Why is the access point asking me for a Password?
Read the Fermentrack documentation - no nothing about the access point having a password there
Did some Google searching - came up dry
Check the log of the log of the flash (seems good, as below)
Tried another ESP8266 board with a fresh flash - same thing - the access point seems to be asking for a password
Tried the obvious (Password, password, BrewPi, Brewpi, brewpi...)
Any help appreciated
Flash Command: esptool.py --port /dev/ttyUSB0 write_flash 0x00000 /app/firmware_flash/firmware/ESP8266 - BrewPi-ESP8266 - vv15cr -- WiFi - firmware.bin 0x300000 /app/firmware_flash/firmware/ESP8266 - BrewPi-ESP8266 - vv15cr -- WiFi - spiffs.bin
esptool.py v2.8
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP8266
Chip is ESP8266EX
Features: WiFi
Crystal is 26MHz
MAC: a4:cf:12:dd:6c:57
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Compressed 490480 bytes to 340364...
Writing at 0x00000000... (4 %)
Writing at 0x00004000... (9 %)
Writing at 0x00008000... (14 %)
Writing at 0x0000c000... (19 %)
Writing at 0x00010000... (23 %)
Writing at 0x00014000... (28 %)
Writing at 0x00018000... (33 %)
Writing at 0x0001c000... (38 %)
Writing at 0x00020000... (42 %)
Writing at 0x00024000... (47 %)
Writing at 0x00028000... (52 %)
Writing at 0x0002c000... (57 %)
Writing at 0x00030000... (61 %)
Writing at 0x00034000... (66 %)
Writing at 0x00038000... (71 %)
Writing at 0x0003c000... (76 %)
Writing at 0x00040000... (80 %)
Writing at 0x00044000... (85 %)
Writing at 0x00048000... (90 %)
Writing at 0x0004c000... (95 %)
Writing at 0x00050000... (100 %)
Wrote 490480 bytes (340364 compressed) at 0x00000000 in 30.4 seconds (effective 129.2 kbit/s)...
Hash of data verified.
Compressed 1024000 bytes to 130681...
Writing at 0x00300000... (12 %)
Writing at 0x00304000... (25 %)
Writing at 0x00308000... (37 %)
Writing at 0x0030c000... (50 %)
Writing at 0x00310000... (62 %)
Writing at 0x00314000... (75 %)
Writing at 0x00318000... (87 %)
Writing at 0x0031c000... (100 %)
Wrote 1024000 bytes (130681 compressed) at 0x00300000 in 12.1 seconds (effective 674.9 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...