-
-
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
XZG Zigbee Firmware 20240510 #11
Comments
Hello everyone, I reinstalled the old firmware and the connection is now stable again. No failure for over an hour, with the new version (FW revision 20240510) there were interruptions about every 45 minutes. |
Chiming in: I wasn't able to get FW 20240508/20240509 to work on my ZigStar LAN PoE gateway because the LAN connection would not work. It worked once immediately after flash with DHCP, and then never again. No combination of LAN DHCP or static IP address settings would make the LAN connection come up, and I tried re-flashing the firmware multiple times. (I also wasn't able to connect it to my Wi-Fi, though that may be normal as I've never used Wi-Fi before on it.) I rolled back to the old firmware and the device started working normally again. Hardware and previous firmware: |
|
I need a little bit more information.
|
Right after upgrading, no LAN connected yet, only USB: Device model: Olimex-ESP32-POE Unplugged USB (power down) and plugged in Ethernet PoE. Device booted and took an IP from the DHCPd. Model info etc stayed the same. Changing the network configuration to static (DHCP off, IP 192.168.1.x, gateway 192.168.1.y, DNS servers 1.1.1.1 and 8.8.8.8) and rebooting: No more LAN connection. (Orange LED on for 2-3 seconds, then green LED comes on and the orange LED is blinking for a second, back to orange LED on, .... loop. The interface on the switch side never shows a link.) The XZG... AP appears but I either can't connect to it, or get disconnected immediately after connecting. (Feels like the device is in a boot/crash loop.) Update: Same symptoms on a non-PoE interface. Serial/USB console output:
Update 2: After this, re-flashing the firmware does not make LAN work again. Problem with the link remains the same. Blinking sequence is the same. It is possible to get in via Wi-Fi by unplugging the LAN interface, and I can confirm the LAN settings are back to default (Ethernet Enabled, DHCP enabled), but link will no longer establish. It looks like the only way to make the LAN connection work again with DHCP is to go back to the old ZigStar GW firmware, and then to XZG. |
The main problem is from board detecting mechanism. Just because of unplugged LAN cable during first boot. You could try to factory reset using tools page, with plugged in LAN cable. |
I flashed version 20240519 via USB with the network (without PoE) attached. Disconnect USB and Ethernet, then plugged in Ethernet with PoE. (*) The device remains stuck like before, the yellow Ethernet light is on for a few seconds, then the green one turns on and the yellow one blinks for a second, then the green one turns off and the yellow one stays on normally again (keeps looping like that). Hardware in the WebUI still shows the same: Device model: Olimex-ESP32-POE |
|
It can be caused by two reasons: hang up Zigbee module or reboot ESP32. That's why we need to know about uptime. |
Okay, then I'll update the second Zigbee adapter to the new version and see what happens. I'll report back. |
I hope this helps a little. After 47 minutes, the Zigbee adapter lost its connection to the iobroker. The adapter (ESP32) then restarted and the connection times started again at zero. The connection to the iobroker is not established automatically. I cannot provide the raw data from the debug console as this is deleted when the adapter is restarted. Another note: Since the Zigbee adapter did not work at the beginning after the web update, I installed the firmware via USB. Then the Zigbee adapter finally established the connection to the iobroker (green digit). |
I left the adapter running last night and could see that the ESP32 restarted after about 45 minutes. This morning I started the adapter again and after about 45 minutes the same thing happened again, the ESP32 restarted but the connection to the iobroker was not established automatically. A restart must be performed in iobroker. Here is the current information from the debug console. |
But you uptime doesn't drops to zero, it is only goes up. |
But your operating time doesn't go down to zero, it just goes up. It looks like the Zigbee chip is stuck. What Zigbee chip are you using? What firmware version? I have no problems with firmware version 06.10. |
But in logs that you provide time only goes up. So I thought that way.
OK.
Have you tried to use latest version of XZG ? |
I installed version 20240524 on the ESP and 20221226 on the Zigbee module. I use the same Zigbee firmware on my active adapter with FW06.10. Here is the data after the restart. |
Do you keep your tab with web UI open continuously? |
Yes, the tab is permanently open. When the failure occurs, 5 devices are shown as connected. But since it is a test environment, it can actually only be one device. Then in iobroker we noticed that the RAM usage was no longer 130 MB but had gone up to over 600 MB. |
It looks like some problems with iobroker. |
I have no other ideas at the moment. |
That's not a problem at the moment. My active Zigbee LAN adapter is currently still running on the old version. |
- Add support **USB mode for ALL boards** - Move device mode selection to Zigbee page - Increase Zigbee firmware flashing speed (115200 vs 460800) - Improve Zigbee FW detection mechanism, fix #47 - Remove configSys.keepWeb - network is always active - Remove vars.hwUartSelIs - no need to check - Add DNS check logs to web console, could help with #11, #24, #42, #43 - Add cod.m CZC-v1.0 config to boards list (but cause it's the same as UZG-01 ones, it has no sense right now) - Some code cleanup, and of course a lot of new garbage :)
Today I updated via LAN my ZigStar Lan Gateway.
Device model WT32-ETH01
FW revision 20240510
HW version ESP32-D0WD
The device is recognized by iobroker, but the connection is offline every 30 to 60 minutes. After a few minutes it is online again, but the adapter (zigbee.iobroker) in the iobroker remains yellow. Only after restarting the adapter will it turn green again.
The text was updated successfully, but these errors were encountered: