rand256 / valetudo

Valetudo RE - experimental vacuum software, cloud free
Apache License 2.0
670 stars 74 forks source link

No Wifi on provided pre-built firmware image #26

Closed WouterJN closed 5 years ago

WouterJN commented 5 years ago

Describe the bug:

After flashing the Valetudo firmware successfully the vacuum does not create a Wifi accesspoint. I tried to hold the reset button for >30 seconds but still no accespoint has been created.

The robot can still clean by pressing the power button

Other Info: Vacuum Model: S5 Valetudo Version: V1898

Terminal during flashing:

INFO:miio.updater:Using local /Users/wouter/Downloads/v1898.fullos.pkg (md5: 355c8df23cf7fd4a564dd1cad51701dd) Hosting file at http://192.168.8.88:61273/v1898.fullos.pkg Update started! 0%| | 0/100 [00:00<?, ?it/s]192.168.8.1 - - [03/Nov/2019 19:30:50] "GET /v1898.fullos.pkg HTTP/1.1" 200 - Downloading: 95%|███████████████████████████████████████████████▌ | 95/100 [03:38<00:10, 2.18s/it]INFO:miio.updater:Got a request, should be downloading now. Downloading: 100%|█████████████████████████████████████████████████| 100/100 [03:43<00:00, 2.09s/it]Installation started, please wait until the vacuum reboots Downloading: 100%|█████████████████████████████████████████████████| 100/100 [03:44<00:00, 2.25s/it] (venv) wouter@Wouters-MacBook-Pro flasher %

commensal commented 5 years ago

Same here. Builtin AP is non existent. Had to do factory reset.

s3er commented 5 years ago

Also no WiFi for me on 1st Gen after flashing 0.4.0-RE5.1 preview. Robot was not connected to WiFi before flashing.

rand256 commented 5 years ago

Well, published firmware images for RE5.1 were made with forked dustcloud's imagebuilder script which had very few changes compared to the original one (that is known to work well). And, as I could see, none of those changes could possibly break AP mode. So, if it's broken, then probably something is broken in origin imagebuilder and/or stock images themselves.

I myself am using images built for S5 exactly the same way as these (apart of a couple additional features enabled and nothing disabled), and they're working fine for me. But it should be noted: I installed them over the provisioned old firmware, so they just connected to my wireless network using an old settings, without ever entering an AP mode. Also I can say just nothing about Gen1 version since I own only Gen2.

To conclude, releasing prepared firmware images were announced as an experiment. And I wished it'd go well, but seems it didn't. I had no positive reports about these images so far, but three negative reports are right here. Right now I'm unable to debug Wi-Fi issues on the provided images, nor it falls into the scope of Valetudo application at all - as they're in the scope of the firmware.

I definitely don't want to release broken images, so for now I denote this experiment as failed and will from now on make releases of Valetudo app only, as before.

rand256 commented 5 years ago

If anyone has any ideas on this, or had succeeded in running those pre-built images, please post.

diabl0w commented 5 years ago

I am not sure about the other reporters here, but for my case, the issue is that the vacuum first says "failed updating, reverting to previous firmware" and then after that there is no access point. i tried flashing twice in case there was a corruption that occurred during the transfer. the resolution is to factory reset by holding the plug button while quick pressing the wifi reset button

giejay commented 5 years ago

I installed the latest prebuilt firmware and it's working fine for me on the v1. I should say, i did not had to enter AP mode because I already have a token.

hawkeye223 commented 5 years ago

You can try the repository - https://github.com/zvldz/vacuum. Using it, working firmware versions are created. See the link: (http://w3bsit3-dns.com/forum/index.php?showtopic=881982&st=3600#entry82130220 https://vacuumz.info/download/).

rand256 commented 5 years ago

It is ideologically the same as used here.

hawkeye223 commented 5 years ago

It is ideologically the same as used here.

Yes, but it is finalized and really works!

diabl0w commented 5 years ago

@rand256 I believe in some other forum that you stated firmware versions above 1820 did nit have many cleaning upgrades and most changes to firmware were debugging changes for logging. do you still have these same thoughts? do you think 1820 may be the best version to use then?

rand256 commented 5 years ago

@diabl0w, I said that there were quiet a lot of debug versions above 1820 released at that time. They were never delivered to users via official channels. But afterwards there were released a few official upgrades via mi Home - for example 1864, 1886 and 1898. I don't think there's a reason to stay on 1820 right now.

diabl0w commented 5 years ago

@diabl0w, I said that there were quiet a lot of debug versions above 1820 released at that time. They were never delivered to users via official channels. But afterwards there were released a few official upgrades via mi Home - for example 1864, 1886 and 1898. I don't think there's a reason to stay on 1820 right now.

@rand256 thank you for the clarification and update

rand256 commented 5 years ago

This issue should be fixed with RE7.1 release.