Open Hedda opened 3 years ago
By the way, PTVO Zigbee Configurable Firmware tool now works with CC2652R1, CC2652RB, CC2652P, and CC1352P2
https://ptvo.info/zigbee-configurable-firmware-features/
https://ptvo.info/cc2652r1-cc2652rb-cc2652p-cc1352p2-configurable-router-firmware-748/
+1
This would also make https://github.com/diyruz/flower/issues/20 (Feature Request: OTA Updates) possible.
@nurikk Have you given any more thought to @diyruz flower sensor redesign with a newer CC2652 radio module?
https://github.com/diyruz/flower/
Maybe also add support a few additional sensors for light (sunlight), temperature and humidity out-of-the-box?
For your information, there is much discussion about it and its derivative Zigbee flower/plant sensors here:
The "efekta" variants by smartboxchannel has especially become popular but it too uses the old CC2530:
https://github.com/smartboxchannel/Plant-Watering-Sensor-Zigbee
PS I believe the concept of CC2652 based Zigbee 3.0 flower/plant sensors would also have great commercial success.
What about EFR32MG2x? I'm lately working with Silabs chips and thinking about doing this with MG2x series...
What about EFR32MG2x? I'm lately working with Silabs chips and thinking about doing this with MG2x series...
It is always nice with more options and it would be great to see more EFR32MG21 (and EFR32MG24) radio modules on the market.
@bojanpotocnik Check out some related discussion here about platform choices when building DIY sensors -> https://github.com/zigpy/zigpy/discussions/867
But @diyruz use Texas Instruments chips in their projects and already have reusable components for Texas Instruments Z-Stack 3.x
https://github.com/diyruz/zstack-lib
I am sure this also has a historical reason because it has in the past been well known that the main benefit of using Texas Instruments Zigbee MCUs is that they have in the past not required that you purchase expensive development kits and register an account in order to get access to their Zigbee SDK and development tools for Zigbee, and that is why they have become popular for DIY hobbyists which in turn lead to tools PTVO Zigbee Configurable Firmware -> https://ptvo.info/
That is other than the fact that the older CC2530 radio modules have historically been less expensive than Silabs chips, especially if compare Silicon Labs EFR32 Series 1 / EFR32MG1x and EFR32 Series 2 / EFR32MG2x (which to be fair have more RAM and storage).
It should however be noted that Silicon Labs have however very recently changed their policies and opened the platform more in order to make it easier to get access their Zigbee SDK and development tools for Zigbee, as well as releasing less expensive development kits and EFR32MG21 Based Modules like MGM210 (MGM210P/MGM210L). See example that Gecko SDK is on GitHub:
https://github.com/SiliconLabs/gecko_sdk
Think most DIY:ers getting started would buy Silabs $19.99 Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT Kit (SLTB004A):
https://www.silabs.com/development-tools/thunderboard/thunderboard-sense-two-kit
More advanced is to also buy the $99 EFR32xG22 Wireless Gecko Starter Kit as well as buying their radio board separately:
https://www.silabs.com/development-tools/wireless/efr32xg22-wireless-starter-kit
SLWRB4180A for around $49 is the matching EFR32MG21 (EFR32 Mighty Gecko Series 2) radio board for that development kit:
SLWRB4180A is the same EFR32MG21 radio board that is included in the $479 EFR32xG21 Wireless Gecko Starter Kit, and EFR32MG21 is same type of chip used in Sonoff ZBBridge Zigbee Bridge.
Texas Instruments also recently added the required to register an account in order to download their Z-Stack SDK, and compared to the olderCC2530/CC2531 which has basic JTAG SWD for debugging the newer CC2652/CC1352 need to flash via the 2-pin cJTAG (a.k.a C-JTAG or c/JTAG) so require a more modern cJTAG debug probe adapter like example Texas Instruments XDS110 (or a clone):
https://electrolama.com/radio-docs/advanced/flash-jtag/
Unfortunately, Silicon Labs has suffered more than most chips companies from manufacturing issues and supply chain problems during the recent years worldwide chip shortage, so it is today simply much harder to find Silabs chips available to buy than it is to find available Texas Instruments CC2652 chips and radio modules.
Today you can go on Aliexpress and similar Chinese stores and find loads of available CC2652P modules but today you will find it hard to find EFR32MG21 (and EFR32MG24) radio modules. That might very well change in the future.
RF-star/RFStar and Ebyte/CDEbyte does make both Texas Instruments and Silicon Labs based Zigbee modules but no EFR32MG21?
Tuya also sells a radio board called "ZS3L" based on EFR32MG21 which might be an alternative if it can be purchased separately:
https://developer.tuya.com/en/docs/iot/zs3l?id=K97r37j19f496
https://developer.tuya.com/en/docs/iot/tuya-sandwich?id=K9lmlvkqwo6rn
CoolKit-Technologies (Shenzhen Cool House Technology) does sell SM-011 V1.0 but it has a questionable antenna design:
https://github.com/zigpy/zigpy/discussions/586
PS: New EFR32MG24 was just released by Silicon Labs which might change things up as has new features and much more releases:
https://github.com/zigpy/zigpy/discussions/893
PPS: No news on MGM240 (MGM240P and MGM240L) modules based on EFR32MG24 to replace FCC/CE precertified MGM210.
Have you considered replacing CC2530 in DIYRuZ Flower sensor design with a new TI CC26xx MCU like the CC2652 series or similar?
Should in theory make the battery last much longer and get better signal range, as well as make for more future-proof hardware with the potential of perhaps not only use Zigbee 3.0 but also even using Thread, Matter (Project CHIP), and/or Bluetooth via multi-protocol support as well.
Maybe use one of the newer CC2652R/CC2652R1/CC2652R2 or CC2652RB (or CC2652P) multi-protocol modules from RF-Star or Ebyte?
I understand CC2652P and CC1352P modules with integrated power amplifiers are most popular when making a Zigbee Coordinator or Zigbee Router, however, CC2652R or CC2652RB might be better for low-powered battery-operated devices?
It is of course also possible to configure a firmware for CC2652P and CC1352P modules to not utilize the power amplifier.
https://www.szrfstar.com/product/list-196-en.html
https://www.szrfstar.com/product/237-en.html
https://www.szrfstar.com/product/189-en.html
https://www.szrfstar.com/product/list-196-en.html
https://www.ebyte.com/en/product-view-news.html?id=1002
https://www.ebyte.com/en/product-view-news.html?id=1481
https://www.ebyte.com