-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
UZG-01 running 20240707 crashes (stalls) after 1-2 days #99
Comments
I'm also using UZG with 20240707 and don't have such problems. |
Got it - is there some way of retrieving any debug data from the running unit (e.g. via the USB-C port)? I haven't power-cycled the unit yet, as it's currently in the crashed (wedged) state - I was waiting to check if there might be useful diagnostic information to pull? |
@xyzroe Am I OK to power-cycle the USG-01? Or is there something I can collect from the box in its crashed state? And after I power-cycle it - is there something I can setup to collect more verbose logs, or capture diagnostic information on why the unit might be stalling? |
You're ok. |
Got it - is there a place I can download the debug build already for 20240707? Or do you happen to know if this will build easily on macOS? (Otherwise I can see about setting up a Linux VM to do this all on. Sorry if this is a silly question - but should I assume it will cross-compile to ARM fine, from a x64 box?) Also - how do I enable the debug build? And where will the additional debug information get dumped to afterwards? Or how do you view these logs? |
I'm using mac os. Just install all dependencies |
Just select "debug-solo" build variant |
I have the same issue after flash firmware > 20240610
I back to firmware 20240610 and all OK |
Any update on this? |
I am having this issue also, resulting in an unavailable controller several times a day. |
for me the same my Device: Zig-Star model: UZG-01 connected via USB/Wifi/LAN always results into device stalling after a few, max 12h, hours |
I am having the same issue. Device: Zig-Star UZG-01 Setup as coordinator. |
Try to disable cron based update availability check |
I updated to 20240914, set frequency to disable. Still automatically reboots itself usually within 15 minutes. After multiple self reboots the device usually hangs and requires a power cycle. |
Any update on this? |
Describe the bug
I have flashed XYZ onto a UZG-01 (ZigStar UZG) device. It is running as a Zigbee Coordinator in my network, and is connected to Zigbee2MQTT.
It is being powered by PoE.
However, after approximately 1-2 days, the device appears to disappear off the local network - it is no longer responding to ICMP ping, and the web interface is not accessible either, and Zigbee2MQTT is not able to connect to it.
However, the LAN Ethernet activity lights are still flashing, and the left-most blue activity light is flashing. (I can attach a video if needed - or if the frequency etc is somehow relevant).
Device information
You should remove your credentials first
Unfortunately I can't get the above, as the device's web interface isn't responding.
Is there some way to get debug logs from the device, before I power-cycle or reboot it? Or what else can I retrieve before I try to reflash it again?
To Reproduce
Steps to reproduce the behavior:
[20240707](https://github.com/xyzroe/XZG/releases/tag/20240707)
onto the device.Expected behavior
The UZG-01 running XZG firmware should not crash or become unavailable.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: