Stoat

The barcode field is 32 bytes but any beyond what's actually on the barcode are simple 0x20 characters (ascii space) - Annoyingly many people have assumed 8 characters as a...

The ugly bits are mine. Robin Johnson wrote the original small script. Note that repeated use of sg_read_attr seems to eventually kill the MAM - which is a bit odd...

It's worth having this kicking around as the alert codes are the same on the MAM as here. Tape alert page (ssc-3) [0x2e] 1 Read warning 2 Write warning 3...

Suggestion: If you're going to write-test to deal with sector problems then it would make sense to call hdparm's --repair-sector option and make that a prerequisite for diskscan

Late followup..... Your pull (#17) doesn't help (Ubuntu 18.* 19.* and 20.*) As an aside - it looks like brice has pulled in the executive.c (fs hinting) stuff already but...

I wonder if this can be tasmotised?

> which test ports did you use Looking at the board photo: GPIO0 is the letter B by the led. Short this to the centre to put the device in...

> the blue mode is for pairing with bluetooth or pairing other then wifi... Actually it's for pairing with a "YPLINK hotspot" - SSID: aaa PASS: 12345678 (yeah, really secure)...

Back on trying to hack into this thing and tasmotize it @lucamot - what pins were you using? The standard GPIO1/GPIO3 pair don't work

I may have gone a little overboard on this, but I've tried to annotate the board image to help with debugging My unit has a v3.5 board but there seems...