You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is relevant for any of the ZB-GW03 models, but for discussion and FYI; you might also be interested to check out tube0013's customized version of the uart component which enable hardware flow control for ESP32 boards:
PS: Note that while using hardware flow control it better in theory there as as far as I know no known issues with using software flow control isstead on the ESP32MG2x series, especially not when using a dedicated ESP32-based network-attached remote serial Zigbee Coordinator, But for reference read that not using hardware flow control is more likely to be an issue on when using a USB or serial-direct connected Zigbee Coordinaor to a low-powered Raspberry Pi that is also running other software applications like for example Home Assistant on the same device.
UPDATE: Ah, I might have been wrong about that. Appartently Nerivec has reported a bug as an issue to upstream where EmberZNet 7.4.0 still in all 8.0.x and 8.1.x you can see UART buffering issues and "appears to have changed in a way that makes the NCP very unstable under load (like an ongoing OTA on the network), it will throw a lot of max ACK timeout count errors. A "mostly-working" workaround appears to be increasing the default SL_IOSTREAM_USART_VCOM_RX_BUFFER_SIZE from 32 to 128 or above. This affects mostly software flow control (so, unclear on 8.1.0 because of first point), and appears pre-dominantly on CP210x-driven modules." ...though that might not affect ESP32-based network-attached remote serial Zigbee Coordinators as they do not use CP210x USB to UART Bridge VCP FYI, that and other bugs reported to Silicon Labs here:
Not sure if this is relevant for any of the ZB-GW03 models, but for discussion and FYI; you might also be interested to check out tube0013's customized version of the uart component which enable hardware flow control for ESP32 boards:
PS: Note that while using hardware flow control it better in theory there as as far as I know no known issues with using software flow control isstead on the ESP32MG2x series, especially not when using a dedicated ESP32-based network-attached remote serial Zigbee Coordinator, But for reference read that not using hardware flow control is more likely to be an issue on when using a USB or serial-direct connected Zigbee Coordinaor to a low-powered Raspberry Pi that is also running other software applications like for example Home Assistant on the same device.
UPDATE: Ah, I might have been wrong about that. Appartently Nerivec has reported a bug as an issue to upstream where EmberZNet 7.4.0 still in all 8.0.x and 8.1.x you can see UART buffering issues and "appears to have changed in a way that makes the NCP very unstable under load (like an ongoing OTA on the network), it will throw a lot of max ACK timeout count errors. A "mostly-working" workaround appears to be increasing the default SL_IOSTREAM_USART_VCOM_RX_BUFFER_SIZE from 32 to 128 or above. This affects mostly software flow control (so, unclear on 8.1.0 because of first point), and appears pre-dominantly on CP210x-driven modules." ...though that might not affect ESP32-based network-attached remote serial Zigbee Coordinators as they do not use CP210x USB to UART Bridge VCP FYI, that and other bugs reported to Silicon Labs here:
The text was updated successfully, but these errors were encountered: