I will spare you all the gruesome details and cut to the chase.
I ended up having a fight with the retailer after them feeding me lies for the past 3 months about trying to source me a replacement. I ended up getting my money back and emailing LG several times asking them where I could source 0.64 firmware glasses.
They kept telling me to contact a local retailer and having them order some in (which wasn't going to happen). In the end I contacted Australia Wide Spare Parts and they also couldn't tell me which version they stocked and to Call LG Support back and ask them for a part number.
After 3 calls back, LG rep finally told me that "Australia would not be receiving any 0.64 firmware glasses, as they had not received any complaints" (in fact she told me they only had 4 cases). She suggested purchasing 0.63 version again and trying them out.
I went to another local retailer tonight to pick up 1 pair of 0.63 just to try them out again. When I picked up the box, I noticed the 0.63 however, I picked up another box next to it and to my surprise 0.64 version! I snapped up all 5 pairs.
Currently have 2 charging and will be trying them out tonight. Just to be clear I have the 60PZ570 model TV.
For those of you asking to see what the sticker looks like on the box, I have included it below. I've removed the serial numbers from the pic, but you can clearly see what you have to look for. Obviously the "AU" at the top applies to the Australian model only.
I'll let you all know how I go tomorrow.. fingers crossed.. I'm hoping like others that got the 0.64 replacements that they wont shut off.
All in all LG customer support (Australia anyways) has been disappointing to say the very least!! I've never had to chase down a product like this and have the manufacturer not even know where I could get them. Mind you the price I was quoted from Australia Wide Spares (LG's spare part division) was $130. I picked them up for $79 at the retailer which is what all of them are selling at, at the moment.
Fingers crossed!! 3+ months stuffing around, so I'm hoping this resolves the issue... Attachment 233250