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

[BUG] after update to 0.98 TC001 not accessible anymore #676

Open
UweW opened this issue Jan 13, 2025 · 2 comments
Open

[BUG] after update to 0.98 TC001 not accessible anymore #676

UweW opened this issue Jan 13, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@UweW
Copy link

UweW commented Jan 13, 2025

Bug report

Describe the bug

after update to 0.98 TC001 not accessible anymore.
Accesspoint still see TC001 connected with the last IP provided by dhcp server.
Multiple rebbots did not help

Additional information

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

To Reproduce

Steps to reproduce the behavior:

  • download firmware
  • update firmware via webinterface
  • after reboot, current IP is shown
  • not reachable under this IP
  • not connection to MQTT server

Expected behavior

accessable via network

Screenshots

If applicable, add screenshots to help explain your problem.

Logs

(optional) Add relevant logs which could help tackle the problem.

Additional context

nmap does not show any open ports or any ping response

@UweW UweW added the bug Something isn't working label Jan 13, 2025
@etienne72230
Copy link

Same issue. Clock seems to work very slow (clock dot update every 10sec) with a yellow pixel at bottom left corner. Before update clock work perfectly with wifi and mqtt.

@Blueforcer
Copy link
Owner

That's not the same issue. In your case Awtrix cannot connect to your MQTT broker.

For the topic issue im currently searching for an possible error, but since nothing has changed according to any kind of connection method and only one issue of that kind out of thousands users, it's currently hard to tell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants