Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Are present error italian translate...
If do you want I can contribute.
Thanks

Describe the bug
wireguard not working over wifi

Device information
Model UZG-01
Firmware 20240707
Hardware ESP32-D0WDQ6

Role Coordinator
Firmware 20240710

Describe the bug
After reboot the ESP32 with the latest image the Zigbee Firmware Version shows "0"
See #47

Device information
see Screenshots...

To Reproduce
Steps to reproduce the behavior:

1. Reboot ESP32
   

2. Check Zigbee Version
   

3. Zigbee Version is shown as expected
   

Expected behavior
After Reboot the ESP32 the Zigbee Firmware Version should be show the correct value

Describe the bug
There is a 502 error when attempting to navigate to 'General' settings tab when going through a reverse proxy. In this case- I am using Nginx Proxy Manager.

To Reproduce
Steps to reproduce the behavior:

1. Setup reverse proxy that points to XZG device
2. Navigate to {xzg-device}.{your-domain}.com settings
3. Go to 'General' tab

Expected behavior
Page should load like all the other tabs

Screenshots

Desktop (please complete the following information):

• OS: macOS
• Browser Chrome
• 125.0.6422.77

Additional context
All other tabs in the settings page loads just fine

Hi there! ✌️

I would like to c 12 hourly format for displaying time in the web.

This is not an absolutely urgent feature request, so we can move it somewhere to the end of to-do list. 😉

Thank u in advance!

Describe the bug
After upgrading FW revision 20240519 to 20240612 wireguard is no longer connecting. It shows status as Initialized and Disconnected.

On the affected firmware is not connecting.

Log:

[1210] | [ZB] Chip: CC2652P7
[1210] | [ZB] IEEE: xxxx
[1221] | [ZB] Flash size: 704 KB
[2347] | [Time] Thu Jun 13 19:50:08 2024
[2348] | [UPD_CHK] cron 9 30 19 * * *
[2453] | WG was initialized
[5689] | [DNS] Saved WiFi - 192.168.101.44
[14985] | [ZB] FW: Unknown! Check serial speed!

After downgrade:

Log:

[131] | Switched USB to ESP
[1210] | [ZB] Chip: CC2652P7
[1210] | [ZB] IEEE: xxxx
[1220] | [ZB] Flash size: 704 KB
[3053] | [ZB] fw: unknown!
[3997] | WG was initialized
[4009] | Local time: Thu Jun 13 19:39:16 2024

Device information

• Screenshot of Zigbee and Device tab from root page of device
• JSON object returned on http://xzg.local/api?action=1&param=all
  You should remove your credentials first

{
  "network-config": {
    "wifiEnbl": true,
    "wifiSsid": “xxxxxx”,
    "wifiPass": “xxxxxxx”,
    "wifiDhcp": true,
    "wifiIp": "::",
    "wifiMask": "255.255.255.0",
    "wifiGate": "::",
    "wifiDns1": "1.1.1.1",
    "wifiDns2": "8.8.8.8",
    "wifiPwr": 78,
    "wifiMode": 1,
    "ethEnbl": false,
    "ethDhcp": true,
    "ethIp": "::",
    "ethMask": "255.255.255.0",
    "ethGate": "::",
    "ethDns1": "1.1.1.1",
    "ethDns2": "8.8.8.8"
  },
  "vpn-config": {
    "wgEnable": true,
    "wgLocalIP": “xxxxx”,
    "wgLocalSubnet": "255.255.255.255",
    "wgLocalPort": 33333,
    "wgLocalGateway": "0.0.0.0",
    "wgLocalPrivKey": “xxxx+xxxxx=",
    "wgEndAddr": “xxxxx”,
    "wgEndPubKey": “xxxxx”,
    "wgEndPort": 13231,
    "wgAllowedIP": “xxxxxx”,
    "wgAllowedMask": "255.255.255.255",
    "wgMakeDefault": true,
    "wgPreSharedKey": "",
    "hnEnable": false,
    "hnJoinCode": "",
    "hnHostName": "XZG-CD6A",
    "hnDashUrl": "default"
  },
  "mqtt-config": {
    "enable": false,
    "server": "",
    "port": 1883,
    "user": "",
    "pass": "",
    "topic": "XZG-CD6A",
    "updateInt": 60,
    "discovery": true,
    "reconnectInt": 15
  },
  "system-config": {
    "disableWeb": true,
    "webAuth": true,
    "webUser": “xxxx”,
    "webPass": “xxxxx”,
    "fwEnabled": true,
    "fwIp": “xxxx”,
    "serialSpeed": 115200,
    "socketPort": 6638,
    "tempOffset": 15,
    "disableLedUSB": false,
    "disableLedPwr": false,
    "refreshLogs": 1,
    "hostname": "UZG01-xxxx”,
    "timeZone": "Europe/xxxx”,
    "ntpServ1": "pool.ntp.org",
    "ntpServ2": "time.google.com",
    "nightMode": false,
    "startHour": "23:00",
    "endHour": "07:00",
    "workMode": 0,
    "zbRole": 0,
    "zbFw": "?",
    "updHour": "19:30",
    "updDays": "*",
    "autoIns": true
  }
}

To Reproduce
Upgrade to 20240612

Expected behavior
Wireguard client should connect.

After moving all my devices to the UZG-01, all of them has low LQI.
Some of theme are slow to respond.
The highest connected one has 153 LQI, the lowest one has 29

With my old Conbee II stick, most units had excellent LQI

The Zigbee2MQTT configuration is set to:

Serial settings

serial:

Location of XZG

port: tcp://uzg-01.domain.tld:6638
baudrate: 115200

Disable Zigbee led?

disable_led: false

Set output power to max 20

advanced:
transmit_power: 20

Describe the bug
NEW SLZB-06, working fine on SMLIght Firmware, no network and Zigbee on XZG.
Board and zigbee are not detected properly (Unknown). I suspect a new rev with maybe a different pinout or something but can't fin info on SMLight website.

Device information
SMLIGHT:
XZG:
http://ZXG.local/api?action=1&param=all :
{
"network-config": {
"wifiEnbl": false,
"wifiSsid": "",
"wifiPass": "",
"wifiDhcp": true,
"wifiIp": "::",
"wifiMask": "255.255.255.0",
"wifiGate": "::",
"wifiDns1": "1.1.1.1",
"wifiDns2": "8.8.8.8",
"wifiPwr": 78,
"wifiMode": 1,
"ethEnbl": false,
"ethDhcp": true,
"ethIp": "::",
"ethMask": "255.255.255.0",
"ethGate": "::",
"ethDns1": "1.1.1.1",
"ethDns2": "8.8.8.8"
},
"vpn-config": {
"wgEnable": false,
"wgLocalIP": "::",
"wgLocalSubnet": "255.255.255.0",
"wgLocalPort": 33333,
"wgLocalGateway": "0.0.0.0",
"wgLocalPrivKey": "",
"wgEndAddr": "",
"wgEndPubKey": "",
"wgEndPort": 0,
"wgAllowedIP": "0.0.0.0",
"wgAllowedMask": "0.0.0.0",
"wgMakeDefault": true,
"wgPreSharedKey": "",
"hnEnable": false,
"hnJoinCode": "",
"hnHostName": "XZG-ACAE",
"hnDashUrl": "default"
},
"mqtt-config": {
"enable": false,
"server": "",
"port": 1883,
"user": "",
"pass": "",
"topic": "XZG-ACAE",
"updateInt": 60,
"discovery": true,
"reconnectInt": 15
},
"system-config": {
"disableWeb": false,
"webAuth": false,
"webUser": "",
"webPass": "",
"fwEnabled": false,
"fwIp": "0.0.0.0",
"serialSpeed": 115200,
"socketPort": 6638,
"tempOffset": 9,
"disableLedUSB": false,
"disableLedPwr": false,
"refreshLogs": 1,
"hostname": "XZG",
"timeZone": "Europe/Berlin",
"ntpServ1": "pool.ntp.org",
"ntpServ2": "time.google.com",
"nightMode": false,
"startHour": "23:00",
"endHour": "07:00",
"workMode": 0,
"zbRole": 0,
"zbFw": "?",
"updHour": "01:00",
"updDays": "*",
"autoIns": false
}
}

Logs :
[12072] | [ZB] FW: Unknown! Check serial speed!
[300488] | [Time] Thu Jan 1 01:05:00 1970
[300489] | [UPD_CHK] cron 40 0 1 * * *
[313227] | [Time] Thu Jan 1 01:05:13 1970
[313228] | [UPD_CHK] cron 6 0 1 * * *
[358552] | [ZB] No Zigbee chip!

To Reproduce
Install either 20240612 or 20240609.01 firmware

Expected behavior
Network and Zigbee working fine

Additional context
I try 20240612 and 20240609.01. Also I did an ESP32 and reset and NVRAM erase without success.

It would be useful to have packet counters for the zigbee interface to display them later in e.g. Grafana.
Thanks!

In the General section when selecting "USB mode" after saving in "Operating mode 2" and connecting from z2m via USB does not work. Experimentally found out that if you set value="1" instead of value="2" in the HTML code of the element selecting USB mode, then after sending the form and saving "Operating mode Zigbee-USB".

Splitting this off into a separate issue as it doesn't appear to match what @rombrock reported in theirs:

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:
FW version : 0.6.10
Hardware : TTGO T-Internet-POE
ESP32 model : ESP32-D0WDQ5

HW as shown in the XZG firmware:
Device model: Olimex-ESP32-POE
FW revision: 20240519
HW version: ESP32-D0WD

Originally posted by @Steltek in #11 (comment)

Describe the bug
After device reboot ZigBee FW revision on status page get "0" value.

To Reproduce

1. Restart whole device.
2. Check ZB FW revision

Expected behavior
ZigBee FW revision should be refreshed/checked.

Screenshots

I know, thats screenshot is from HA ;). And the unavailable status is my MQTT restart.

Additional info
When I press "Check Zigbee version" on Debug tools page, the firmware version is refreshed and get correct value.

Hello,
Is your feature request related to a problem? Please describe.
Support for HMG-01 POE Plus (Chinese clone)

Describe the solution you'd like
Is it possible to support the HMG-01 POE Plus device (Chinese clone)? I believe it is a "simple" modification?. In the firmware https://github.com/mercenaruss/uzg-firmware, I changed #define ETH_POWER_PIN_1 -1 to #define ETH_POWER_PIN_1 5 and it seems to be working correctly for the past couple of months. I see that this new firmware supports several devices: UZG-01, SLZB-06, Olizig PoE, LilyZig PoE, ZigStar LAN. Could HMG-01 POE Plus be included?

Describe alternatives you've considered
Change of the equivalent code in the XZG firmware regarding the use of ETH_POWER_PIN_1, following the modification from #define ETH_POWER_PIN_1 -1 to #define ETH_POWER_PIN_1 5 as done in the UZG firmware, and I do not know if further changes would be necessary.

Additional context
Thank you.

Is your feature request related to a problem? Please describe.
A feature, it would be good if we had connectivity with Home Assistant that showed the available updates for the ESP32 and Zigbee firmware like all other HA components

Describe the solution you'd like
As above, the Zigstar UZG-01 reports its firmware position in HA

Describe alternatives you've considered
N/A - manually checking periodically if it is latest firmware.

Additional context
N/A

Describe the bug
I have installed firmware 20240531 via Web Installer (fresh install no update) on my UZG-01. But I am unable to connect to my local WIFI with this firmware. I supspect there are some "new" restrictictions in place.

My local WIFI has a SSID in form of [email protected] and and a WPA2 password with a length of 63 charactes of all kind. I opened a WIFI hostpost from my Adnroid phone with a SSID "Phone_8123" and a WPA2 Password "12345678" and was able to connect. So I suspect something has changed in what is allowed for SSID or password.

Device information

To Reproduce
Steps to reproduce the behavior:

1. Create a WIFI with an SSID like XYZ.local.home and as password with a length of 63 charactes of all kind.
2. Try to connect to that WIFI

Expected behavior
Able to connect to WIFI like with UZG-01 firmware ;-)

I flashed 20240612 via USB using the web flasher which seemed successful, however when I connected the ethernet back it powered up but was unreachable via the network and ZHA refused to connect. Re-flashed it with ESPHome and it came back up.

Here is the esp-web-tools-logs.txt

this is the ESPHome .yaml https://github.com/tube0013/tube_gateways/blob/850b7ff29925f1eaef1ef23fef872351e00f53b2/models/current/tubeszb-efr32-MGM210-poe/firmware/esphome/tubeszb-efr32-mgm210-poe-2022.yaml

Is this firmware meant to work with ESP devices connected to Silabs zigbee modules like the efr32 or is it only for Ti based ones?

UZG-01 does not register itself with DNS after the latest version 20240529.1
It may be introduced in the release before, but it was with this update I discovered it

Hi folks,

I heard about this wonderful project and wanted to switch with my SLZB-06M to XZG.
Before flashing XZG I was on v2.2.8.dev from smlight.
I always use the device connected via wired ethernet and also powered over ethernet.

For flashing to XZG I used a USB cable of course.
After a few attempts the webflasher finally startet flashing and said successfull in the end.

First I thought it should obtain a IP-address via ethernet and DHCP but it didn't.
Then I found the XZG WiFi access point and connected to it.

Loved the UI but couldn't change to use the wired ethernet connection at all.
Every time I changed the config and triggered the reboot it came up with the access point again.
No connection via wired ethernet possible.
Neither by fixed ip (which is my default) or DHCP.

I the tried to put it in my own WiFi network first but also had no luck in changing to ethernet connection.
Even with the ethernet cable plugged in it always showed the wired ethernet connection "red" in upper right corner.

As I didn't had more time today to struggle with this, I flashed back to v2.2.8.dev from smlight to have my zigbee running again.

Thought, I write you guys here and maybe you an idea for me :)
Maybe I did something wrong or there really is an issue with wired ethernet connection and SLZB-06M.
Would love to give it another try if you guide me the right direction.

Thx
Julian

Describe the bug
I'm using HMG-01 POE Plus. It's cannot to add device via touchlink scan, because it returns an error.
Home Assistant OS 12.4, Zigbee2MQTT 1.38.0

Device information

• XZG:
  
  

• params
  { "network-config": { "wifiEnbl": false, "wifiSsid": "", "wifiPass": "", "wifiDhcp": true, "wifiIp": "::", "wifiMask": "255.255.255.0", "wifiGate": "::", "wifiDns1": "1.1.1.1", "wifiDns2": "8.8.8.8", "wifiPwr": 78, "wifiMode": 1, "ethEnbl": true, "ethDhcp": true, "ethIp": "192.168.1.47", "ethMask": "255.255.255.0", "ethGate": "::", "ethDns1": "1.1.1.1", "ethDns2": "8.8.8.8" }, "vpn-config": { "wgEnable": false, "wgLocalIP": "::", "wgLocalSubnet": "255.255.255.0", "wgLocalPort": 33333, "wgLocalGateway": "0.0.0.0", "wgLocalPrivKey": "", "wgEndAddr": "", "wgEndPubKey": "", "wgEndPort": 0, "wgAllowedIP": "0.0.0.0", "wgAllowedMask": "0.0.0.0", "wgMakeDefault": true, "wgPreSharedKey": "", "hnEnable": false, "hnJoinCode": "", "hnHostName": "XZG-8252", "hnDashUrl": "default" }, "mqtt-config": { "enable": true, "server": "192.168.1.87", "port": 1883, "user": "mqtt", "pass": "mqtt", "topic": "XZG-8252", "updateInt": 60, "discovery": true, "reconnectInt": 15 }, "system-config": { "disableWeb": false, "webAuth": false, "webUser": "", "webPass": "", "fwEnabled": false, "fwIp": "0.0.0.0", "serialSpeed": 115200, "socketPort": 6638, "tempOffset": -4, "disableLedUSB": false, "disableLedPwr": false, "refreshLogs": 1, "hostname": "HMG-01", "timeZone": "Europe/Moscow", "ntpServ1": "pool.ntp.org", "ntpServ2": "time.google.com", "nightMode": false, "startHour": "23:00", "endHour": "07:00", "workMode": 0, "zbRole": 1, "zbFw": "?", "updHour": "00:00", "updDays": "*", "autoIns": false } }

To Reproduce
Steps to reproduce the behavior:

1. Open HomeAssistant
2. Open Zigbee2MQTT UI
3. Select Touchlink
4. Scan

Expected behavior
It found devices

Actual behavior
Errors:

Info 2024-06-26 16:26:15Start Touchlink scan
Info 2024-06-26 16:26:15Set InterPAN channel to '11'
Warning 2024-06-26 16:26:15Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:15Set InterPAN channel to '15'
Warning 2024-06-26 16:26:16Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:16Set InterPAN channel to '20'
Warning 2024-06-26 16:26:16Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:16Set InterPAN channel to '25'
Warning 2024-06-26 16:26:17Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:17Set InterPAN channel to '12'
Warning 2024-06-26 16:26:17Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:17Set InterPAN channel to '13'
Warning 2024-06-26 16:26:18Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:18Set InterPAN channel to '14'
Warning 2024-06-26 16:26:18Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:18Set InterPAN channel to '16'
Warning 2024-06-26 16:26:19Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:19Set InterPAN channel to '17'
Warning 2024-06-26 16:26:19Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:19Set InterPAN channel to '18'
Warning 2024-06-26 16:26:20Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:20Set InterPAN channel to '19'
Warning 2024-06-26 16:26:20Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:20Set InterPAN channel to '21'
Warning 2024-06-26 16:26:21Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:21Set InterPAN channel to '22'
Warning 2024-06-26 16:26:21Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:21Set InterPAN channel to '23'
Warning 2024-06-26 16:26:22Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:22Set InterPAN channel to '24'
Warning 2024-06-26 16:26:22Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:23Set InterPAN channel to '26'
Warning 2024-06-26 16:26:23Scan request failed or was not answered: 'Error: Timeout - null - 254 - null - 4096 - 1 after 500ms'
Info 2024-06-26 16:26:23Restore InterPAN channel
Info 2024-06-26 16:26:26Finished Touchlink scan
Info 2024-06-26 16:26:26MQTT publish: topic 'zigbee2mqtt/bridge/response/touchlink/scan', payload '{"data":{"found":[]},"status":"ok","transaction":"9yw1f-1"}'

Describe the bug
Unable to build XZG

I've setup a Debian machine, and per the README have installed npm (from Debian repos) and platformio (using their installer script).

However, when I try to run platformio run, I get the following error:

``
$ platformio run
Processing prod-solo (platform: https://github.com/tasmota/platform-espressif32/releases/download/2023.07.00/platform-espressif32.zip; board: esp32-solo1; framework: arduino)

Verbose mode can be enabled via -v, --verbose option

██╗░░██╗███████╗░██████╗░
╚██╗██╔╝╚════██║██╔════╝░
░╚███╔╝░░░███╔═╝██║░░██╗░
░██╔██╗░██╔══╝░░██║░░╚██╗
██╔╝╚██╗███████╗╚██████╔╝
╚═╝░░╚═╝╚══════╝░╚═════╝░

Build: 20240730

Try to build WEB files

npm install --silent
sh: 1: npm: not found
*** Error 127
npx gulp xzg
sh: 1: npx: not found
*** Error 127

Finish building WEB files

██╗░░██╗███████╗░██████╗░
╚██╗██╔╝╚════██║██╔════╝░
░╚███╔╝░░░███╔═╝██║░░██╗░
░██╔██╗░██╔══╝░░██║░░╚██╗
██╔╝╚██╗███████╗╚██████╔╝
╚═╝░░╚═╝╚══════╝░╚═════╝░

CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32-solo1.html
PLATFORM: Espressif 32 (2023.7.0) > Espressif Generic ESP32-solo1 4M Flash
HARDWARE: ESP32 160MHz, 320KB RAM, 4MB Flash
DEBUG: Current (cmsis-dap) External (cmsis-dap, esp-bridge, esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:

• framework-arduino-solo1 @ 2.0.11
• framework-arduinoespressif32 @ 3.0.3+sha.f5be003
• tool-esptoolpy @ 1.40602.0 (4.6.2)
• tool-mklittlefs @ 1.203.210628 (2.3)
• tool-mkspiffs @ 2.230.0 (2.30)
• toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch5
  LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
  LDF Modes: Finder ~ chain, Compatibility ~ soft
  Found 41 compatible libraries
  Scanning dependencies...
  Dependency Graph
  |-- ArduinoJson @ 6.21.3
  |-- CircularBuffer @ 1.4.0
  |-- Ticker @ 4.4.0
  |-- CronAlarms @ 0.1.0
  |-- AsyncMqttClient @ 0.9.0
  |-- AsyncTCP @ 1.1.1
  |-- DallasTemperature @ 3.11.0
  |-- HTTPClient @ 2.0.0
  |-- FS @ 2.0.0
  |-- LittleFS @ 2.0.0
  |-- Preferences @ 2.0.0
  |-- WiFi @ 2.0.0
  |-- CCTools @ 0.0.6
  |-- Ethernet @ 2.0.0
  |-- OneWire @ 2.3.8
  |-- WireGuard-ESP32 @ 0.1.5
  |-- DNSServer @ 2.0.0
  |-- ESPmDNS @ 2.0.0
  |-- Update @ 2.0.0
  |-- WebServer @ 2.0.0
  |-- WiFiClientSecure @ 2.0.0
  Building in release mode
  Compiling .pio/build/prod-solo/src/config.cpp.o
  Compiling .pio/build/prod-solo/src/const/hw.cpp.o
  Compiling .pio/build/prod-solo/src/const/keys.cpp.o
  Compiling .pio/build/prod-solo/src/etc.cpp.o
  Compiling .pio/build/prod-solo/src/log.cpp.o
  Compiling .pio/build/prod-solo/src/main.cpp.o
  Compiling .pio/build/prod-solo/src/mqtt.cpp.o
  Compiling .pio/build/prod-solo/src/per.cpp.o
  Compiling .pio/build/prod-solo/src/web.cpp.o
  src/web.cpp:23:10: fatal error: webh/html/PAGE_VPN.html.gz.h: No such file or directory
  #include "webh/html/PAGE_VPN.html.gz.h"
  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  compilation terminated.
  *** [.pio/build/prod-solo/src/web.cpp.o] Error 1
  ============================================================================================================ [FAILED] Took 6.98 seconds ============================================================================================================

Environment Status Duration

prod-solo FAILED 00:00:06.975
======================================================================================================= 1 failed, 0 succeeded in 00:00:06.975 =======================================================================================================

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

• Screenshot of Zigbee and Device tab from root page of device
• JSON object returned on http://xzg.local/api?action=1&param=all
  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:

1. Get a UZG-01.
2. Flash [20240707](https://github.com/xyzroe/XZG/releases/tag/20240707) onto the device.
3. Configure it as a Zigbee coordinator, and point a Zigbee2MQTT instance at it.
4. Wait...profit.

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.

Not sure if this is related to the switch or the UZG-01
If I restart the UZG-01, it does not come back until I shutdown the switchport and turn it back on.
Until then, the UZG network port blinks for a second, then goes dark. Blinks for a second then goes dark, etc.

The switch is a Cisco Catalyst 9300 of model C9300L-48UXG-4X
The port settings looks like this:

interface GigabitEthernet1/0/31
 description UZG
 switchport access vlan 1098
 switchport mode access
 device-tracking
 speed 100

The show power inline command shows this:

show power inline Gi1/0/31 detail 
 Interface: Gi1/0/31
 Inline Power Mode: auto
 Operational status: on
 Device Detected: yes
 Device Type: Ieee PD
 IEEE Class: 0
 Discovery mechanism used/configured: Ieee and Cisco
 Police: off

 Power Allocated 
 Admin Value: 60.0
 Power drawn from the source: 15.4
 Power available to the device: 15.4
 
 Actual consumption
 Measured at the port: 0.8
 Maximum Power drawn by the device since powered on: 0.9
 
 Absent Counter: 0
 Over Current Counter: 0
 Short Current Counter: 0
 Invalid Signature Counter: 0
 Power Denied Counter: 0

 Power Negotiation Used: None
 LLDP Power Negotiation --Sent to PD--      --Rcvd from PD--
   Power Type:          -                    -
   Power Source:        -                    -
   Power Priority:      -                    -
   Requested Power(W):  -                    -
   Allocated Power(W):  -                    -

Four-Pair PoE Supported: Yes
Spare Pair Power Enabled: No
Four-Pair PD Architecture: N/A
Perpetual POE Enabled: FALSE
Fast POE Enabled: FALSE

The configHW.json debug file contains this:

{
  "board": "UZG-01",
  "addr": 0,
  "pwrPin": -1,
  "mdcPin": 23,
  "mdiPin": 18,
  "phyType": 0,
  "clkMode": 3,
  "pwrAltPin": 5,
  "btnPin": 35,
  "btnPlr": 1,
  "uartSelPin": 33,
  "uartSelPlr": 1,
  "ledModePin": 12,
  "ledModePlr": 1,
  "ledPwrPin": 14,
  "ledPwrPlr": 1,
  "zbTxPin": 4,
  "zbRxPin": 36,
  "zbRstPin": 16,
  "zbBslPin": 32
}

Is your feature request related to a problem? Please describe.
Missing support for WPA3-Personal
I've recently upgraded my wireless router and I was wanting to utilize wireless connection on my ZigStarGW.

Describe the solution you'd like
Update FW on ESP32 to support WPA3-Personal if possible
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/wifi-security.html#wpa3-personal

Describe alternatives you've considered

Additional context
https://imgur.com/gb6jt4i

Describe the bug
Getting warnings in HA when using Ethernet without WiFi:
Template variable warning: 'dict object' has no attribute 'wlanSsid' when rendering '{{ value_json.wlanSsid }}'

To Reproduce
Steps to reproduce the behavior:

1. Only connect over Ethernet
2. Check HA logs

Expected behavior
Shouldn't get these warnings while only connected over Ethernet.

Screenshots

Logger: homeassistant.helpers.template
Source: helpers/template.py:2613
First occurred: 20 mai 2024 la 20:18:52 (1427 occurrences)
Last logged: 19:56:18

Template variable warning: 'dict object' has no attribute 'wlanSsid' when rendering '{{ value_json.wlanSsid }}'

Additional context
Olimex-ESP32-POE
20240519

Is your feature request related to a problem? Please describe.
Can't run the device on IPv6-only networks.

Describe the solution you'd like
Add IPv6 support (SLAAC + Static as a minimum, DHCPv6 as a bonus).

Describe alternatives you've considered
N/A

Additional context
Services that should support IPv6: web service, DNS, NTP and Zigbee socket connection. Maybe also the firmware update parts (but that requires the external services to support IPv6 as well, so maybe that would have to be a future thing).

Describe the bug
The minimal input length of the broker hostname / ip is 4 characters. The hostname of my broker is "nuc", which can not be entered.

To Reproduce
Steps to reproduce the behavior:

1. Open the XZG web interface
2. Click on 'MQTT'
3. Try to enter a broker name with less than 4 characters
4. See error

Expected behavior
Enter and accept a hostname with less than 4 characters, but at least 1.

Screenshots

I don't know why the error message is in german, i explicitly changed the UI language to english. Maybe the message is generated by the browser (Firefox?) It says: "Please use at least 4 characters (currently 3)"

Workaround
Use the IP address and a static IP for the broker, which isn't always possible.

Is your feature request related to a problem? Please describe.
I'm trying to diagnose an issue with a Zigbee device and zigbee2mqtt (Koenkk/zigbee2mqtt#23204 - to be specific)

Describe the solution you'd like
There's some discussion here about some ways of sniffing Zigbee traffic:

https://www.zigbee2mqtt.io/advanced/zigbee/04_sniff_zigbee_traffic.html#_3-sniffing-traffic

However, I'm wondering if there's any way for the XZG firmware itself to capture/dump the Zigbee traffic, either for everything, or for a specific device (more helpful) - either to local storage, or perhaps to a network volume, or something else like that?

Describe alternatives you've considered
Using a second adapter that's close by to try to sniff the traffic (although worried it may miss some).

Additional context
Add any other context or screenshots about the feature request here.

So when I first upgrade the firmware and I am using Static IP, when I click to the IP setting page it is showing the default IP settings instead of what's being defined from previous firmware, I had mine switched from Static IP to DHCP and now IP info shows correctly.

Доброго времени суток. Постоянно получаю уведомление о доступности новой прошивки, но при попытки обновления постоянно висит в статусе "Скачивание последнего релиза GitHub...". Пробовал перезагружать роутер и координатор, ничего не помогает.

Describe the bug
In my case Zigbee coordinator (via USB) was connected and working, but socket saying "No connection".

Device information

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Additional context
I want to monitorize via MQTT the zigbee network status.

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.

This delete button looks like magic wand to me.
And on top of that, it is not confirming deletion

Request:

1. A better explanatory icon, and maybe a text
2. A popup to confirm deletion

Hi!

MQTT sensor of gateway zigbee firmware version displaying 0:

Describe the bug
Sometimes the device auto reboot.
log is here：
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:184
load:0x40078000,len:12736
load:0x40080400,len:2716
entry 0x40080594
�[35m1146 �[0m�[32m[printLogMsg] �[0m[ZB] Chip: CC2652P7
�[35m1147 �[0m�[32m[printLogMsg] �[0m[ZB] IEEE: 00:12:4B:00:2A:7B:4D:01
�[35m1147 �[0m�[32m[zbHwCheck] �[0mmodeCfg ffc1b9fd
�[35m1157 �[0m�[32m[zbHwCheck] �[0mbslCfg c50ffec5
�[35m1158 �[0m�[32m[printLogMsg] �[0m[ZB] Flash size: 704 KB
�[35m1724 �[0m�[32m[setup] �[0mConfig:
{
"network-config": {
"wifiEnbl": false,
"wifiSsid": "",
"wifiPass": "",
"wifiDhcp": true,
"wifiIp": "::",
"wifiMask": "255.255.255.0",
"wifiGate": "::",
"wifiDns1": "1.1.1.1",
"wifiDns2": "8.8.8.8",
"wifiPwr": 78,
"wifiMode": 1,
"ethEnbl": true,
"ethDhcp": true,
"ethIp": "::",
"ethMask": "255.255.255.0",
"ethGate": "::",
"ethDns1": "1.1.1.1",
"ethDns2": "8.8.8.8"
},
"vpn-config": {
"wgEnable": false,
"wgLocalIP": "::",
"wgLocalSubnet": "255.255.255.0",
"wgLocalPort": 33333,
"wgLocalGateway": "0.0.0.0",
"wgLocalPrivKey": "",
"wgEndAddr": "",
"wgEndPubKey": "",
"wgEndPort": 0,
"wgAllowedIP": "0.0.0.0",
"wgAllowedMask": "0.0.0.0",
"wgMakeDefault": true,
"wgPreSharedKey": "",
"hnEnable": false,
"hnJoinCode": "",
"hnHostName": "XZG-B196",
"hnDashUrl": "default"
},
"mqtt-config": {
"enable": false,
"server": "",
"port": 1883,
"user": "",
"pass": "",
"topic": "XZG-B196",
"updateInt": 60,
"discovery": true,
"reconnectInt": 15
},
"system-config": {
"disableWeb": false,
"webAuth": false,
"webUser": "",
"webPass": "",
"fwEnabled": false,
"fwIp": "0.0.0.0",
"serialSpeed": 115200,
"socketPort": 6638,
"tempOffset": 13,
"disableLedUSB": false,
"disableLedPwr": false,
"refreshLogs": 1,
"hostname": "XZG",
"timeZone": "Europe/Berlin",
"ntpServ1": "pool.ntp.org",
"ntpServ2": "time.google.com",
"nightMode": false,
"startHour": "23:00",
"endHour": "07:00",
"workMode": 0,
"zbRole": 0,
"zbFw": "?",
"updHour": "01:00",
"updDays": "*",
"autoIns": false
}
}
�[35m1880 �[0m�[32m[setup] �[0mVARS:
{
"system-vars": {
"hwBtnIs": true,
"hwLedUsbIs": true,
"hwLedPwrIs": true,
"hwZigbeeIs": true,
"connectedClients": 0,
"socketTime": 0,
"connectedEther": false,
"apStarted": false,
"wifiWebSetupInProgress": false,
"vpnWgInit": false,
"vpnWgConnect": false,
"vpnWgPeerIp": "::",
"vpnWgCheckTimeKey": 0,
"vpnHnInit": false,
"mqttConn": false,
"mqttReconnectTime": 0,
"mqttHeartbeatTime": 0,
"disableLeds": false,
"zbFlashing": false,
"deviceId": "XZG-B196",
"espUpdAvail": false,
"zbUpdAvail": false
}
}
�[35m1942 �[0m�[32m[setupCoordinatorMode] �[0mNetwork
�[35m3628 �[0m�[32m[mDNS_start] �[0mmDNS responder started on XZG.local
�[35m3642 �[0m�[32m[printNVSFreeSpace] �[0mTotal: 630, Used: 111, Free: 519
�[35m4473 �[0m�[32m[NetworkEvent] �[0mETH MAC: 10:06:1C:BB:82:17, IP: 192.168.0.46, Mask: 255.255.255.0, Gw: 192.168.0.1, DNS: 192.168.0.1, 100Mbps
�[35m4485 �[0m�[32m[printLogMsg] �[0m[DNS] Saved ETH - 192.168.0.1
�[35m5624 �[0m�[32m[printLogMsg] �[0m[Time] Wed Jul 10 15:24:44 2024
�[35m5624 �[0m�[32m[printLogMsg] �[0m[UPD_CHK] cron 43 0 1 * * *
�[35m15413 �[0m�[32m[printLogMsg] �[0m[ZB] FW: Unknown! Check serial speed!
�[35m15413 �[0m�[32m[setup] �[0m[ESP] FW: 20240710
�[35m15413 �[0m�[32m[setup] �[0mLoad cfg ZBC03P
�[35m16176 �[0m�[32m[setup] �[0mdone
**Guru Meditation Error: Core 0 panic'ed (Unhandled debug exception).
Debug exception reason: Stack canary watchpoint triggered (update Web Task)
Core 0 register dump:
PC : 0x40084cd5 PS : 0x00060736 A0 : 0x3ffda3a0 A1 : 0x3ffda2e0
A2 : 0x00000000 A3 : 0x00060723 A4 : 0x00060720 A5 : 0x3ffcc370
A6 : 0x3ffdae3c A7 : 0x00000002 A8 : 0x3ffc8514 A9 : 0x00000001
A10 : 0x00000000 A11 : 0x00060723 A12 : 0x00000001 A13 : 0x3ffda4af
A14 : 0x3ffb7fc8 A15 : 0x3ffbc9f0 SAR : 0x0000001c EXCCAUSE: 0x00000001
EXCVADDR: 0x00000000 LBEG : 0x4008a24d LEND : 0x4008a25d LCOUNT : 0xfffffffb

Backtrace: 0x40084cd2:0x3ffda2e0 0x3ffda39d:0x3ffda3b0 |<-CORRUPTED
ELF file SHA256: 0000000000000000

Rebooting...**
ets Jul 29 2019 12:21:46

Device information
{
"board": "ZBC03P",
"addr": 1,
"pwrPin": -1,
"mdcPin": 23,
"mdiPin": 18,
"phyType": 0,
"clkMode": 3,
"btnPin": 34,
"btnPlr": 1,
"uartSelPin": 13,
"uartSelPlr": 1,
"ledModePin": 4,
"ledModePlr": 1,
"ledPwrPin": 14,
"ledPwrPlr": 1,
"zbTxPin": 5,
"zbRxPin": 16,
"zbRstPin": 33,
"zbBslPin": 32
}

I realized I was running an older version of the zigbee firmware (20230507).
So I wanted to update it via the web gui.


But when I click install, it says:

and it hangs there for a while.
Then it simply states "failed"
Is there another way to flash it?

Thanks

WiFi / VPN page in specific. Attached an example

After update from 0.2.6 can't access web ui by fqdn; opening http://uzg-01/ redirects to 192.168.1.1 but my local address pool is in 10.0.0.0 range; Chrome, Firefox, Edge

          So I need to add socket connection and MQTT stoping mechanism. Ok.

Originally posted by @xyzroe in #63 (comment)

Is your feature request related to a problem? Please describe.
My WiFi network consists out of three AP's (one in each floor) with roaming enabled (same SSID). XZG does not reliably connect to the closest AP with the strongest signal. Sometimes power on/off serveral times in row helps. Currently I am stuck connected to the AP with lowest signal in my cellar - sigh :-(

Describe the solution you'd like
A very nice project I am also using is https://github.com/tbnobody/OpenDTU which seems to have solved the same issue by using this two lines of code:

            WiFi.setScanMethod(WIFI_ALL_CHANNEL_SCAN);
            WiFi.setSortMethod(WIFI_CONNECT_AP_BY_SIGNAL);

Describe alternatives you've considered
Power on/off device until connected to the desired AP or disable all AP's I don't want XZG to connect to. This is obviously not a alternative or solution ;-)

Additional context
none

Пробовал несколько раз разные прошивки - процесс идет до 75-95% и после этого устройство полностью отваливается (и по ping в том числе). Принудительно передергиваю по питанию (POE) - в окне статус "FW версия" либо пусто, либо 0
Пришлось прошивать через ZigStarGW-MT-x64

Describe the bug
Trying to access the webUI by the device's hostname set in General Settings, always redirects to 192.168.1.1.

Device information

{
  "network-config": {
    "wifiEnbl": false,
    "wifiSsid": "",
    "wifiPass": "",
    "wifiDhcp": true,
    "wifiIp": "::",
    "wifiMask": "255.255.255.0",
    "wifiGate": "::",
    "wifiDns1": "1.1.1.1",
    "wifiDns2": "8.8.8.8",
    "ethEnbl": true,
    "ethDhcp": true,
    "ethIp": "::",
    "ethMask": "255.255.255.0",
    "ethGate": "::",
    "ethDns1": "1.1.1.1",
    "ethDns2": "8.8.8.8"
  },
  "vpn-config": {
    "wgEnable": false,
    "wgLocalIP": "::",
    "wgLocalSubnet": "255.255.255.0",
    "wgLocalPort": 33333,
    "wgLocalGateway": "0.0.0.0",
    "wgLocalPrivKey": "",
    "wgEndAddr": "",
    "wgEndPubKey": "",
    "wgEndPort": 0,
    "wgAllowedIP": "0.0.0.0",
    "wgAllowedMask": "0.0.0.0",
    "wgMakeDefault": true,
    "wgPreSharedKey": "",
    "hnEnable": false,
    "hnJoinCode": "",
    "hnHostName": "XZG-FA75",
    "hnDashUrl": "default"
  },
  "mqtt-config": {
    "enable": false,
    "server": "",
    "port": 1883,
    "user": "",
    "pass": "",
    "topic": "ZigStarGW-C169",
    "updateInt": 60,
    "discovery": false,
    "reconnectInt": 0
  },
  "system-config": {
    "keepWeb": false,
    "disableWeb": false,
    "webAuth": false,
    "webUser": "",
    "webPass": "",
    "fwEnabled": false,
    "fwIp": "0.0.0.0",
    "serialSpeed": 115200,
    "socketPort": 6638,
    "tempOffset": 12,
    "disableLedUSB": false,
    "disableLedPwr": false,
    "refreshLogs": 1,
    "hostname": "ZigBee",
    "timeZone": "Europe/London",
    "ntpServ1": "pool.ntp.org",
    "ntpServ2": "",
    "nightMode": false,
    "startHour": "23:00",
    "endHour": "07:00",
    "workMode": 0
  }
}

To Reproduce

1. Remove DNS/static entries on router if necessary
2. Change the Hostname in General Settings to Bargle
3. Save and restart the coordinator
4. curl -v http://bargle
5. Recieve HTTP 302, Location http://192.168.1.1

Expected behavior
Get 200, and the page contents

Describe the bug
A clear and concise description of what the bug is.

Device information

• Screenshot of Zigbee and Device tab from root page of device
• JSON object returned on http://xzg.local/api?action=1&param=all
  You should remove your credentials first

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

In the previous firmware 0.26 and prior, MQTT configuration used to send the IP address of the coordinator

To Reproduce
Steps to reproduce the behavior:

1. Upgrade to XZG firmware
2. Enable MQTT Configuration

Expected behavior
IP Address as part of MQTT Payload

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Describe the bug
When trying to access the General page, the page get stuck on loading (blue circular rotating)
I get an HTTP 502 on the /api?action=0&page=1

This only happens on the General page when serving the web interface through a Reverse proxy, Nginx Proxy Manager.

All other pages works without any issue.

When accessing directly through http://xzg.local/general, it works fine.

Device information

• Screenshot of Zigbee and Device tab from root page of device:

• JSON object returned on http://xzg.local/api?action=1&param=all
  { "network-config": { "wifiEnbl": false, "wifiSsid": "", "wifiPass": "", "wifiDhcp": true, "wifiIp": "::", "wifiMask": "255.255.255.0", "wifiGate": "::", "wifiDns1": "1.1.1.1", "wifiDns2": "8.8.8.8", "wifiPwr": 78, "wifiMode": 1, "ethEnbl": true, "ethDhcp": true, "ethIp": "x.x.x.x", "ethMask": "255.255.255.0", "ethGate": "x.x.x.1", "ethDns1": "1.1.1.1", "ethDns2": "8.8.8.8" }, "vpn-config": { "wgEnable": false, "wgLocalIP": "::", "wgLocalSubnet": "255.255.255.0", "wgLocalPort": 33333, "wgLocalGateway": "0.0.0.0", "wgLocalPrivKey": "", "wgEndAddr": "", "wgEndPubKey": "", "wgEndPort": 0, "wgAllowedIP": "0.0.0.0", "wgAllowedMask": "0.0.0.0", "wgMakeDefault": true, "wgPreSharedKey": "", "hnEnable": false, "hnJoinCode": "", "hnHostName": "XZG-502F", "hnDashUrl": "default" }, "mqtt-config": { "enable": true, "server": "x.x.x.x", "port": 1883, "user": "********", "pass": "********", "topic": "uzg", "updateInt": 60, "discovery": true, "reconnectInt": 30 }, "system-config": { "disableWeb": false, "webAuth": false, "webUser": "admin", "webPass": "", "fwEnabled": false, "fwIp": "x.x.x.x", "serialSpeed": 115200, "socketPort": 6638, "tempOffset": 20, "disableLedUSB": false, "disableLedPwr": false, "refreshLogs": 10, "hostname": "UZG-01", "timeZone": "Europe/Oslo", "ntpServ1": "pool.ntp.org", "ntpServ2": "time.google.com", "nightMode": false, "startHour": "23:00", "endHour": "07:00", "workMode": 0, "zbRole": 1, "zbFw": "20240710", "updHour": "01:00", "updDays": "*", "autoIns": false } }

To Reproduce
Steps to reproduce the behavior:

1. Use Nginx Proxy Manager to serve the web interface through domain with SSL. e.g. https://zigbee.domain.com. --> Destination is http://xzg.local:80. Support for Websockets enabled.
2. Go to https://zigbee.domain.com/general
3. Loading icon appears.
4. Call to https://zigbee.domain.com/api?action=0&page=1 results in HTTP 502

Expected behavior
Expect the General page to show. Call to https://zigbee.domain.com/api?action=0&page=1 should result in HTTP 200.

I had my UZG01 just updated to the XZG firmware and found I am unable to connect to the Web UI using HAProxy.

Any idea please?