Releases: nRF24/RF24Mesh
v2.0.2
2.0.2 - 2024-10-06
🚀 Added
- Enhance checkConnection() function by @TMRh20 in #240
- Expose releaseAddress() for master node by @2bndy5 in #244
- Address build warnings about ncurses example by @2bndy5 in #243
- Mesh.checkConnection via parent not master by @TMRh20 in #250
- Add pyproject.toml by @2bndy5 in #252
🛠️ Fixed
- Fix spelling of MESH_NOMASTER in py wrapper by @2bndy5 in
2fb4d25
- Fix spelling of MESH_NOMASTER in RF24Mesh.cpp by @2bndy5 in
a8c63bc
📝 Documentation
🗨️ Changed
- Change MESH_DEBUG into RF24MESH_DEBUG by @2bndy5 in #239
- Update doxygen CSS and use v1.11.0 by @2bndy5 in #245
Full commit diff: v2.0.1...v2.0.2
v1.1.12
1.1.12 - 2024-10-06
🚀 Added
🗑️ Removed
📝 Documentation
- Mesh.checkConnection via parent not master in
7ca48f0
🗨️ Changed
- Change MESH_DEBUG into RF24MESH_DEBUG in
4fbd113
- Expose releaseAddress() for master nodes in
ada11ac
Full commit diff: v1.1.11...v1.1.12
v2.0.1
v1.1.11
v2.0.0
Introducing RF24Network & RF24Mesh v2.0 with some significant API changes, adding the use of C++ Templates in order to support a
range of ESB enabled radios, most recently NRF52x radios.
Important Notes:
- Any network layer that uses v2 needs to have RF24Network/RF24Mesh dependencies of v2 or newer. RF24 v1.x is an exception here.
- General usage should remain backward compatible, see the included examples of the related libraries for more info
- Any third party libs that extend the network/mesh layer may also need to be updated to incorporate the new templated class prototypes:
template<class radio_t>
class ESBNetwork;
template<class network_t, class radio_t>
class ESBMesh;
- Third party libs should also be able to use the backward-compatible typedef in their template:
- ESBGateway.h:
and inform the compiler what types they intend to support:template<typename network_t, typename mesh_t> class ESBGateway
- ESBGateway.cpp:
template class ESBGateway<RF24Network, RF24Mesh>;
- The auto installers do not perform a version check like package managers, so having the correct versions of the software is important.
- We will be maintaining the v1.x versions with bugfixes etc for those who cannot or do not wish to migrate to the newer template approach.
Full Changelog: v1.1.9...v2.0.0
v1.1.10
This release simply caps the dependent RF24Network version to v1.x
.
Full Changelog: v1.1.9...v1.1.10
v1.1.9
Bug Fix for v1.1.7
PIGPIO support
What's Changed
- PIGPIO support for IRQ feature (now that wiringPi is no longer shipped with RPi OS)
- improve examples' use of mesh.begin() and renewAddress() by @2bndy5 in #205
- Add topology to ncurses example by @TMRh20 in #207
- various improvments to docs by @2bndy5 in #209
- update python examples per testing by @2bndy5 in #212
- Clang format by @2bndy5 in #213
Full Changelog: v1.1.6...v1.1.7
v1.1.6
- CMake support
- RPi Pico SDK support
- Updates to callback functionality
- Update examples
- Update python wrapper
- Doc updates
- new Sphinx generated docs (hosted at https://rf24mesh.rtfd.io)
- Many changes, see commit history
Warning for installing from the packaged release assets (.deb or .rpm files below)
If you have previously installed the library from source code using the traditional make; sudo make install
, then you will need to uninstall it manually to avoid runtime conflicts.
sudo rm /usr/local/lib/librf24mesh.*
sudo rm -r /usr/local/include/RF24Mesh
This is because the Linux package manager puts the newly installed library into a /usr/lib and /usr/include folders. Installing from source will put the library in /usr/local/lib and /usr/local/include folders.