Skip to content
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

v7.2.0: No Web Setup or serial communication #7282

Closed
8 of 15 tasks
jeroenrnl opened this issue Dec 21, 2019 · 4 comments
Closed
8 of 15 tasks

v7.2.0: No Web Setup or serial communication #7282

jeroenrnl opened this issue Dec 21, 2019 · 4 comments
Assignees
Labels
bug Type - Confirmated Bug fixed Result - The work on the issue has ended

Comments

@jeroenrnl
Copy link

PROBLEM DESCRIPTION

I've flashed a couple of new Shellys (Shelly1 v3 + Shelly2.5) with v7.2.0 but it didn't show an AP to connect to and on the serial terminal I see only this:
00:00:00 WIF: Connecting to AP1 in mode 11N as tasmota-7798... 00:00:16 WIF: Connect failed with AP timeout 00:00:16 WIF: Connecting to AP2 in mode 11N as tasmota-7798... 00:00:32 WIF: Connect failed with AP timeout 00:00:34 WIF: Connecting to AP2 in mode 11N as tasmota-7798...
Typing on the serial terminal doesn't do anything.

I've downgraded to 7.1.2 and that works flawless

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

  • Read the Contributing Guide and Policy and the Code of Conduct
  • Searched the problem in issues
  • Searched the problem in the docs
  • Searched the problem in the forum
  • Searched the problem in the chat
  • Device used (e.g., Sonoff Basic):Shelly1, Shelly2.5
  • Tasmota binary firmware version number used: 7.2.0
    • Pre-compiled
    • Self-compiled
      • IDE / Compiler used: _____
  • Flashing tools used: esptool.py
  • Provide the output of command: Backlog Template; Module; GPIO 255:
  <no output, no reaction on serial console>


  • If using rules, provide the output of this command: Backlog Rule1; Rule2; Rule3:
  Rules output here:
  <no output, no reaction on serial console>

  • Provide the output of this command: Status 0:
  STATUS 0 output here:
  <no output, no reaction on serial console>

  • Provide the output of the Console log output when you experience your issue; if applicable:
    (Please use weblog 4 for more debug information)
  Console output here:
  <no output, no reaction on serial console>

TO REPRODUCE

Steps to reproduce the behavior:
esptool.py --port /dev/ttyUSB0 erase_flash
esptool.py --port /dev/ttyUSB0 write_flash -fs 1MB -fm dout 0x0 tasmota.bin

### EXPECTED BEHAVIOUR _A clear and concise description of what you expected to happen._ configuration AP or possibility to set via console

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

@Danny02
Copy link

Danny02 commented Dec 21, 2019

Hi, first time user here. Just "bricked" two sonoff minis myself. seems to be same problem. The blue LED of the mini is just blinking maybe 500ms off 500ms on. Flashed with Sonoff DIY OTA.

Edit:
Sry for the confusion. My devices are probably still working and can be flashed over serial. It will just take some time for me to do, because as a beginner the OTA functionality is way more easy.

@jeroenrnl
Copy link
Author

Mine weren't bricked, simply reflashing them with other software fixed it, at least for one, reflashing the others now, but I'm quite convinced they will be fine too.

@arendst arendst self-assigned this Dec 21, 2019
@arendst arendst added the bug Type - Confirmated Bug label Dec 21, 2019
arendst added a commit that referenced this issue Dec 21, 2019
Fix no AP on initial install (#7282)
arendst added a commit that referenced this issue Dec 21, 2019
Fix no AP on initial install (#7282)
@arendst
Copy link
Owner

arendst commented Dec 21, 2019

Verified. Will release updated files.

@arendst arendst added the fixed Result - The work on the issue has ended label Dec 21, 2019
@arendst arendst closed this as completed Dec 21, 2019
@jeroenrnl
Copy link
Author

I reflashed one with the updated release and confirm: issue fixed. Thanks for the amazing service (40 minutes from bug report to fix!!!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Type - Confirmated Bug fixed Result - The work on the issue has ended
Projects
None yet
Development

No branches or pull requests

3 participants