Hi, thank you so much for maintaining this project!
People should be in control of their own property and this is only possible with local control.
When searching for reports about the 10R model, I quickly realized that the onboarding reports people are posting can become hard to keep track of.
Hence, maybe a overview linking to the reports might be of help of others.
PS: The issue reports are linking to the Discussion section of this repository for compatibility discussions, however, Discussions are disabled. Not sure if this is intended or not.
PSS: I know about the Tested Vacuums doc, but it would properly get a bit too messy there to reference all individual reports and details. So this issue could be a companion to the top-level documentation. Successful onboarding report issues could also be closed to help with issue management. But all of this is a suggestion, if you don't like this idea, feel free to close this issue 🙂.
❌ Saros 20 Sonic Complete / Saros 20 X
(Click to expand)
Failure
* #47 (FW V02.51.82 (Sonic Complete) + FW VV02.42.28 (20 X))
Saros 10R
(Click to expand)
Success
* #57 (FW V02.52.86)
* #61 (FW V02.52.86)
* #78 (FW V02.50.56)
S8 MaxV Ultra
(Click to expand)
Success
* #49 (FW V02.37.38)
S8
(Click to expand)
Success
* #46 (FW V02.17.42)
S7 Max V
(Click to expand)
Success
* #49 (FW V02.59.36)
S5 Max
(Click to expand)
Success
* #3 (FW V02.16.62)
Q8 Max
(Click to expand)
Success
* #70 (FW V02.06.86)
❌Q7 TF+
(Click to expand)
Failure
* #48 (FW unknown)
Q5 Pro
(Click to expand)
Success
* #56 (FW V02.04.06)
Qrevo Master
(Click to expand)
Success
* #57 (FW V02.28.26)
❌ Qrevo S Pro
(Click to expand)
Failure
* #67 (FW V02.36.38)
Qrevo S5V
(Click to expand)
Success
* #52 (FW V02.36.38)
Qrevo Curv
(Click to expand)
Success
* #60 (FW V02.28.60)
Qrevo CurvX
(Click to expand)
Success
* #64 (FW V02.35.88)
❌ QRevo Edge 2
(Click to expand)
Failure
* #59 (FW V02.11.66)
QRevo
(Click to expand)
Success
* #75 (FW V02.20.60)
Hi, thank you so much for maintaining this project!
People should be in control of their own property and this is only possible with local control.
When searching for reports about the 10R model, I quickly realized that the onboarding reports people are posting can become hard to keep track of.
Hence, maybe a overview linking to the reports might be of help of others.
PS: The issue reports are linking to the Discussion section of this repository for compatibility discussions, however, Discussions are disabled. Not sure if this is intended or not.
PSS: I know about the Tested Vacuums doc, but it would properly get a bit too messy there to reference all individual reports and details. So this issue could be a companion to the top-level documentation. Successful onboarding report issues could also be closed to help with issue management. But all of this is a suggestion, if you don't like this idea, feel free to close this issue 🙂.
❌ Saros 20 Sonic Complete / Saros 20 X
(Click to expand)Failure
* #47 (FW V02.51.82 (Sonic Complete) + FW VV02.42.28 (20 X))Saros 10R
(Click to expand)Success
* #57 (FW V02.52.86)* #61 (FW V02.52.86)
* #78 (FW V02.50.56)
S8 MaxV Ultra
(Click to expand)Success
* #49 (FW V02.37.38)S8
(Click to expand)Success
* #46 (FW V02.17.42)S7 Max V
(Click to expand)Success
* #49 (FW V02.59.36)S5 Max
(Click to expand)Success
* #3 (FW V02.16.62)Q8 Max
(Click to expand)Success
* #70 (FW V02.06.86)❌Q7 TF+
(Click to expand)Failure
* #48 (FW unknown)Q5 Pro
(Click to expand)Success
* #56 (FW V02.04.06)Qrevo Master
(Click to expand)Success
* #57 (FW V02.28.26)❌ Qrevo S Pro
(Click to expand)Failure
* #67 (FW V02.36.38)Qrevo S5V
(Click to expand)Success
* #52 (FW V02.36.38)Qrevo Curv
(Click to expand)Success
* #60 (FW V02.28.60)Qrevo CurvX
(Click to expand)Success
* #64 (FW V02.35.88)❌ QRevo Edge 2
(Click to expand)Failure
* #59 (FW V02.11.66)QRevo
(Click to expand)Success
* #75 (FW V02.20.60)