Russell Morris

Yep, exactly. And as I recall it's erroring out (i.e. returning a fail error code) - but I could be wrong on this one (sorry, remote right now, can't check...

Thanks! Definitely no biggie.

Not quite. If I take the original file size, subtract out the commercial time (from EDL) - the output file is not quite the same number as this (example below)....

Agreed, awesome tool - thanks! I can second this one, thought I was going crazy ... 😆. But made sure to use the debug version, and checked the (debug) log...

Will give that a try, thanks! Just to make sure (first 😆) ... nothing lost / no downside of the reset, right? Thanks again.

Rolled the dice, reset NVRAM 🤣. It worked, thanks! BTW, to check, from a terminal (or ssh), ``` nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version ``` I'm thinking this is what Hackintool uses also. Before,...

> I've never reset nvram before what is the easiest way? From OpenCore, just select the option to Reset NVRAM.

Seeing the same thing here - it's not always detecting the bootloader correctly. Any logs that would help? Thanks!

> Can you give me the `tuya-cli`command you are using? I assume something like.. Yep, exactly like that 😄, ``` ./node_modules/@tuyapi/cli/cli.js get --id ******** --key ******** --ip 192.168.2.147 -a ```...

> It seems to be a non-standard Tuya plug device. But it matches (closely) to this (and what I find at the Tuya site), https://tasmota.github.io/docs/TuyaMCU/#power-monitoring-plug ... so really non-standard? BTW,...