Skip to content
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

[SUGGESTION] Team up with slaesh to also test his CC2652RB USB stick for development (for hardware independence) #8

Open
Hedda opened this issue Oct 14, 2020 · 1 comment

Comments

@Hedda
Copy link

Hedda commented Oct 14, 2020

@ciotlosm Can I suggest that you try to reach out to @slaesh (via [email protected] or Telegram) about teaming up to test and if possible also develop support his CC2652RB development sticks with firmware management tool?

https://slae.sh/projects/cc2652/

https://github.com/slaesh/cc2652-stick

https://t.me/slaesh

You could also post this suggestion to his issues tracker here:

slaesh/cc2652-stick#2

As I understand both slaesh CC2652 development stick and your addon are both only spare-time hobby projects but still I think that teaming up might give both projects some positive recognition in the Home Assistant and Zigbee2MQTT communities which might attract more developers and willing alpha/beta-testers from the community to come to help out with these projects which in the long run could benefit all users wanting Zigbee support with Texas Instruments hardware to become even more user-friendly and working with more hardware than today.

PS: Would also be nice to see some collaboration with the zigpy guys working on zigpy-znp as an optional alternative to zigpy-cc

https://github.com/zha-ng/zigpy-znp

https://github.com/zigpy/zigpy-cc

@Hedda
Copy link
Author

Hedda commented Oct 14, 2020

If so then maybe rename the project to Texas Instruments Z-Stack Zigbee Firmware Tool or something similar?

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

No branches or pull requests

1 participant