I also started receiving this error after the upgrade and am unable to get it resolved. I've tried deleting the profile and reloading new ones by applying my settings manually, several times. Can one symptom be it's just an annoying error, or is the communication with the Rostock v2 messed up? On the surface everything seems to be communicating with mine OK.
I upgraded right as I was firing up my new E3D v6. I'm having a butt load of issues, that are likely not related, but I'm starting to wonder...I don't have an accelerometer, is there anything in the software running in it's absence that could be throwing that error? (forgive my ignorance please)