[BUG]

[CharlyMai]

Bug report

Awtrix with Ulanzi permanent reboot

Describe the bug

After install the 0.73 Version every thing looks fine.
If i add the MQTT-Field (correctly) without the Home-Assistant Checkbox, the Ulanzi shows:

 1) "Awtrix" in rainbow color 
 2) "Awtrix 10.10.30.150" in rainbow color with the correct IP
 3) "MQTT..." in rainbow color
 4) Time for a few 1/100 second
 5) "Check" in white color
 6) "no up :(" in white color
 7) "0.73" in rainbow color

And than it starts by No 1.......

Additional information

• Devices involved:
  • Model: Ulanzi Awtrix Smart Pixel Clock 2882 (TC001)

To Reproduce

Steps to reproduce the behavior:
a) Firmware update
b) connect to ioBroker (so far so good)
c) enter MQTT IP and all other fields (permanent reboot)
d) remove IP address from MQTT and wait for the next showing of AWTRIX 10.10.30.150 for press -Save configuration-
everything is fine and no reboot

BR
CharlyMai

[Blueforcer]

Doesn't sound like youre using Homeassistant..?
If youre using IOBroker please read the pinned issue:
#165

[TB-SE]

If youre using IOBroker

I have the same issue and I don't use IOBroker. I'm using the Mosquitto broker addon with Home Assistant OS.

I went from V0.71 to V0.73

[Blueforcer]

Then check with MQTT explorer wich messages arrive to awtrix.
If there is a message to /reboot you sent it to awtrix.

[TB-SE]

Fantastic! I can't even flash it manually with the old firmware because of the boot loop.

[Blueforcer]

Read my comment and stop sending the reboot command. Easy.

If you're sure you don't send anything.
Post the serial log output. Otherwise no one can help you.

You can still flash it via USB like any other ESP.

[TB-SE]

You can still flash it via USB like any other ESP.

Well that's the thing, it keeps rebooting. I can neither see anything with MQTT explorer, nor does it stay connected to my PC. Every two seconds in reconnects to the PC via USB.

Is there any way to get it into boot mode, like with any standard ESP32?

[Blueforcer]

Wait, if it's reconnect to the PC, then it has nothing to do with the Firmware or ESP. the USB interface is separated and is always active even without a running ESP.

Are you sure your ulanzis battery is full of charge? It will not run with a empty battery even if it's connected via USB.

[TB-SE]

Are you sure your ulanzis battery is full of charge? It will not run with a empty battery even if it's connected via USB.

Well, it was plugged in to an usb charger for 24h before I updated the firmware and I have only moved it to the PC for manual flashing. So as far as I know, the battery should be between 95-100%. The clock is not visible in windows or through the ESP Web Tool when it is turned off and connected through USB.

When I have it connected via USB and hold down both arrow buttons to make it start/boot, it basically connects and disconnects infinitely every 2 seconds - so flashing it manually seems out of the question.

[TB-SE]

I'm tired, bloody and a bit perplexed... but it's finally working again. I had to disassemble it completely. After unplugging the battery and matrix (and holding down the reset button), I could finally re-flash it. But while assembling it, the issue came back. Only after disassembling and assembling everything again roughly 5 times it "just" works.

I'm now literally scared s***less to flash or OTA any future updates. It's seems to be either poor soldering or imminent component failure, but I lack proper soldering gear (and know-how) to do anything about it. Ulanzi seriously needs to ramp up the quality control on this fairly simple ESP32 device. I've already pre-emptively ordered a new one, I hope the old ones holds until it arrives. 🤞

[Blueforcer]

Since no more feedback comes from the issue creator, I close here. If there are still problems, please open again