About the beta firmware:
Just checked - nothing changed.
currently it shows:
“Current Version: 1.4.2_0026
Firmware is up to date.”
UPDATE: ok - something weird just happened - but in the end I managed to update ( please note since I think it is a bug )
Since I didn’t managed to get the update, I change server from Germany → Singapore → check firmware update again but nothing changed, still _0026 version.
then I Killed the app → opened it to find that the bulb’s configuration were GONE/WIPED.
so left w/o any choice I added “new bulb”, but at after few scans, bulb was NOT found.
So I did the “reset” procedure you instruct in cases like this → the managed to scan & find the bulb.
When the bulb was finally added to the Yeelight app → ONLY THEN I got a “new firmware” alert, did it, and it was successfully updated to _0027 ver.
it is weird since killing the app shouldn’t make the bulb disappear - NOR CHANGING THE SERVER ( which is the only explanation left ).
don’t you do migration/sync of data automatically between server each hour/day ?
About the RED color fix ( in 0027 ver )
IMHO it’s slightly better “red” ocmparing to v0026
When at full brightness (=100), red (255,0,0) color is at its best, but with “orange” leftovers.
The lower the brightness, the less reddish the color is.
At lowest brightness (=1) the red (255,0,0) is still somewhat pinkish.
to sum it up - it’s better - but still need fixing.
Don’t you Xiomi got a “colorimeter” and “dark chamber” to test & calibrate it ?
About the ID issue -
I solved it - its not the bulb fault but linux’s commands & applications.
I explain it @this thread, and suggest a solution that I tested and works