-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
***** FinalStage Detected ****** Stuck #16
Comments
Sometimes is shut down fast , sometimes it keeps going for a long time : Setting up wifi scan |
Little bit more information, i need to unplug and plugin again to see the closed connection message : ***** Connected to FinalStage ****** |
Normally the FinalStage firmware will repeatedly try and fetch the firmware but it looks like yours is only trying once.
You should be able to ping 192.168.4.1 and the device should get the firmware from your webserver. |
Hi, First of all thanks for the help. For option 1 i see all the time :
Result on other script :
Option 2 : |
The tcpdump shows that the device is trying several times a second to get the firmware, Reboot the machine so as to make sure nothing is running that shouldn't be.
Try pinging 192.168.4.1 you should get a response.
The output should be this repeating:
Leave it running as it shows the device is actively trying to complete the upgrade.
and let me know what the output is. |
root@raspberrypi:/etc/apache2/sites-enabled# service apache2 stop When i plug it in , i see ony one run of trying to connect to 8080 but i see nothing in the apache log. |
No that is not correct what i am saying, when i plug in it i see this on tcpdump. 20:54:16.659971 IP 192.168.4.2.8080 > 192.168.4.1.26340: Flags [R.], seq 0, ack 8528, win 0, length 0 So it keeps polling port 8080, but when i start apache2 it stop 20:55:35.150871 IP 192.168.4.1.21079 > 192.168.4.2.8080: Flags [S], seq 31899, win 5840, options [mss 1460], length 0 and then nothing happen, i see nothing in the log of apache either. |
That tells me quite a bit.
When the device wants to talk to the host it sends a
What is supposed to happen next is that the device then sends the HTTP request but it doesn't, instead it send this packet:
This is known as a FIN packet ( Unfortunately, this is bad news. It means the FinalStage firmware isn't working the way it is supposed to and your device is unlikely to get the tasmota firmware. There isn't anything that can be done other than taking it apart and connecting to it via a serial connection.. About the only thing you can try at this stage is to leave it connected the way it is overnight and hope it somehow kicks into life and fetches the firmware. Alternatively you could try repeatedly powering off and on and using tcpdump to see if it has hung again. |
I also tried to flash it with sonota.exe (FinalStage) for windows but it has exactly the same effect, so now we know why. |
You might do better trying tuya-convert instead. I think their interim stage is better than mine and less prone to error. |
Device : SHP-6
Rasp PI3
Stuck on Flinalstage detected / Connecting to Finalstage
***** Receiving FinalStage Request ****
REQ: Client closed connection while receiving request:
etc etc etc ...
I can ping the client
64 bytes from 192.168.4.1: icmp_seq=201 ttl=128 time=3.99 ms
64 bytes from 192.168.4.1: icmp_seq=202 ttl=128 time=21.3 ms
64 bytes from 192.168.4.1: icmp_seq=203 ttl=128 time=86.2 ms
But after many many tries it will not send sonoff.bin
Anything else i can try ?
The text was updated successfully, but these errors were encountered: