You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't a support inquiry, so much a solution for a problem I figured others might run into. Since this was mostly trial-and-error, I can't promise there aren't any side effects to this. And while I figure it goes without saying, running this command with your current SSID will kill your connection to the robot. Nonetheless, I hope it helps!
Long story short, the following command works to remove an old SSID from the Dreame D10s Pro's secure NVM if needed:
manager_ap.sh del_ap 'OldSSID'&& reboot
... where OldSSID should be replaced with the SSID. A reboot is required for the change to take effect.
The longer story: I tried changing my the SSID my robot connects to using the method in the vacuum's manual, but it kept connecting to the original SSID. When checking /data/config/wifi/wpa_supplicant.conf, I found network blocks for both SSIDs. Since the old SSID was listed first, I'm guessing wpa_supplicant would connect to it first. It might also have been a race condition: since both SSIDs are being broadcast by the same AP, the old SSID could easily just have gotten to the robot first.
Unfortunately, #1362 didn't help here, as /data/config/wifi/ap_config.json doesn't exist on my model. I wasn't able to find any other references to this sort of issue.
After some troubleshooting, I was able to figure out this model uses secure NVM (/dev/sst_storage?) to store the AP info. Thankfully, /usr/bin/manager_ap.sh uses /mnt/misc/dm as a flag to detect if secure NVM or the flash filesystem is used for AP config.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
This isn't a support inquiry, so much a solution for a problem I figured others might run into. Since this was mostly trial-and-error, I can't promise there aren't any side effects to this. And while I figure it goes without saying, running this command with your current SSID will kill your connection to the robot. Nonetheless, I hope it helps!
Long story short, the following command works to remove an old SSID from the Dreame D10s Pro's secure NVM if needed:
... where
OldSSIDshould be replaced with the SSID. A reboot is required for the change to take effect.The longer story: I tried changing my the SSID my robot connects to using the method in the vacuum's manual, but it kept connecting to the original SSID. When checking
/data/config/wifi/wpa_supplicant.conf, I found network blocks for both SSIDs. Since the old SSID was listed first, I'm guessing wpa_supplicant would connect to it first. It might also have been a race condition: since both SSIDs are being broadcast by the same AP, the old SSID could easily just have gotten to the robot first.Unfortunately, #1362 didn't help here, as
/data/config/wifi/ap_config.jsondoesn't exist on my model. I wasn't able to find any other references to this sort of issue.After some troubleshooting, I was able to figure out this model uses secure NVM (
/dev/sst_storage?) to store the AP info. Thankfully,/usr/bin/manager_ap.shuses/mnt/misc/dmas a flag to detect if secure NVM or the flash filesystem is used for AP config.Beta Was this translation helpful? Give feedback.
All reactions