Update README.md all CC253x are not recommended #94
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
List CC2538 as not recommended and add a note that Z-Stack 3.0.x firmware is not recommended for the CC2530 and CC2531 in a "production" environment (since they are not powerful enough). The argument is that while CC2538 based Zigbee coordinator adapters works they are no longer recommended by the Zigbee2MQTT community since they use outdated chips and older firmware. Availability of CC2538 USB adapters are scarce and I also understand that no zigpy devs are using it as Zigbee coordinator reference hardware so not being well tested, (even though CC2538 should work as CC2530 and CC2531 in theory). Thus might be a good idea for zigpy-znp to also just list CC2538 as "not recommended" in favour of newer CC26x2 and CC13x2 based adapters instead so hopefully less new users buy old hardware as their their first Zigbee coordinator. puddly also posted this comment in zigpy#48 about CC2538 around a year ago "*The last Z-Stack update for it was released more than two years ago and it will not support the newer route discovery features that improve network stability because the version of Z-Stack that it's stuck with supposedly has glitches.*" Other references: https://www.zigbee2mqtt.io/guide/adapters/#not-recommended https://github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/
|
@pully Acceptable to no longer "recommend" all CC253x including CC2538 and not just CC2530 and CC2531? Once no longer recommended in zigpy-znp will copy that recommendation to ZHA docs: https://www.home-assistant.io/integrations/zha#known-working-zigbee-radio-modules |
|
I don't personally use one (or have one to test since my module was defective) but the CC2538 I think is still fine, it's a more modern architecture than the CC2530/31 and has enough resources to properly run Z-Stack 3.0.1. That being said, support for it is best-effort with zigpy-znp until I get another one to try out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
List CC2538 as not recommended and add a note that Z-Stack 3.0.x firmware is not recommended for the CC2530 and CC2531 in a "production" environment (since they are not powerful enough).
The argument is that while CC2538 based Zigbee coordinator adapters works they are no longer recommended by the Zigbee2MQTT community since they use outdated chips and older firmware. Availability of CC2538 USB adapters are scarce and I also understand that no zigpy devs are using it as Zigbee coordinator reference hardware so not being well tested, (even though CC2538 should work as CC2530 and CC2531 in theory). Thus might be a good idea for zigpy-znp to also just list CC2538 as "not recommended" in favour of newer CC26x2 and CC13x2 based adapters instead so hopefully less new users buy old hardware as their their first Zigbee coordinator. puddly also posted this comment in #48 about CC2538 around a year ago "The last Z-Stack update for it was released more than two years ago and it will not support the newer route discovery features that improve network stability because the version of Z-Stack that it's stuck with supposedly has glitches."
Other references:
https://www.zigbee2mqtt.io/guide/adapters/#not-recommended
https://github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/
https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator#im-using-a-cc2530-or-cc2531-which-firmware-should-i-use