Today we are releasing firmware version 1.6.x13 for the Wyze Robot Vacuum to update the certificate.
Read our Release Notes:
Today we are releasing firmware version 1.6.x13 for the Wyze Robot Vacuum to update the certificate.
Read our Release Notes:
So how do I get this update?
I have a model WVCR200S/2100Pa. When I go to Settings->Device Info->Firmware Version, it says 1.6.202 and “Everything’s good, you’re up to date.”.
And what happens if I can’t get the update? The release notes only says it’s a certificate update. Does that mean if I don’t get the update, my vac will stop working at some point in the near future?
I am technically curious, as always, and have a question.
Why do you need a certificate to run a vacuum?
Is this a SSL certificate needed to run the vacuum securly over port 43? Or is it some sort of other certificate?
If by chance the certificate expires, does the vacuum become useless?
Thanks for any explanations.
I guess I will never know.
@ssummerlin Well, your question quoted me - and I was asking kind of a similar question. I’m not sure if you intended to ask me or not. If so, then I don’t know the answer, that’s why I asked what happens if I don’t get the update.
If I had to guess (and this is really just a guess), I’m assuming (hoping) either communication between my smartphone app and the robot over my local lan is encrypted and/or the communication between my robot and the wyze servers is encrypted (hopefully both are encrypted). In either case, I assume one or more certificates is required and certificates eventually expire, thus requiring the need to update them.
You might want to re-ask your question, this time quoting the OP (@WyzeJasonJ), I don’t know if that will prompt a response from him or not, but it might be worth a try.
Thanks. I guess I misdirected and wanted to say what you asked. Maybe @WyzeJasonJ can teach us a few things.
I think your explanation makes as much sense as any. I’ve seen updates in the past for Wyze Bulbs where the Release Notes say “Added support for G2 root certification”, so I just figured it was a patch that allows the devices to continue to communicate with and within their ecosystem while they make ongoing changes to the backend.