Skip to content

Conversation

@puddly
Copy link
Contributor

@puddly puddly commented Jul 1, 2025

I'm going to be using 460800 baud for newer adapters.

57600 is used by I think one or two sticks, I wonder if it's time to drop it? Right now autoprobing is quite slow due to the sheer number of combinations.

@codecov
Copy link

codecov bot commented Jul 1, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.44%. Comparing base (81e25be) to head (0862031).
Report is 1 commits behind head on dev.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #677   +/-   ##
=======================================
  Coverage   99.44%   99.44%           
=======================================
  Files          52       52           
  Lines        3769     3769           
=======================================
  Hits         3748     3748           
  Misses         21       21           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@MattWestb
Copy link
Contributor

If i remember was old EM3X with original firmware using 57600 but the latest was compiled with 115200 but i think most of the EM3X dongles is now out then no current EZSP can being compiled for them plus need one tool-change that is very expensive and i think only Garry can do it in the community.
See old Wiki for hardware and EZSP version (all older then 6.7.8.0 is obselite) https://github.com/zigpy/zigpy/wiki/Coordinator-Firmware-Updates#recommended-firmware-versions-for-ezsp-coordinators

PS: most little older hardware with updated EZSP is using SW flow control at 115200 and only some hardware flow control so still importing have the 115200 probing.

@puddly
Copy link
Contributor Author

puddly commented Jul 1, 2025

The only stick that I have is the HUSBZB-1 with the original firmware (57600). All of the updated firmwares I think switch it to 115200?

@pipiche38
Copy link
Contributor

pipiche38 commented Jul 1, 2025

Would it make sense to start at 460800 then if no communication established switch to 115200 and finally to 57600?

@puddly
Copy link
Contributor Author

puddly commented Jul 1, 2025

This is precisely what ControllerApplication.probe does, these settings are specific to a radio library.

@MattWestb
Copy link
Contributor

The only stick that I have is the HUSBZB-1 with the original firmware (57600). All of the updated firmwares I think switch it to 115200?

Garry was cooking all community firmware for EM3X devices but i think it was both off some user was liking having the old slow HW and some like faster with SW but i think is nearly zero left of them now after Snoff and SC and so on.
If i have understanding right is only probing auto conf so if adding one coordinator manually its still possible setting the baud rate so shall working like before ding the probing = the EM3X time.

@puddly puddly merged commit 0a00d81 into zigpy:dev Jul 2, 2025
14 checks passed
@puddly
Copy link
Contributor Author

puddly commented Jul 2, 2025

We'll drop 57600 next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants