MeshCore-Evo 0.1.18 ist da.
https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.14.1-evo_0.1.18
Sie beinhaltet auf Wunsch jetzt auch
https://github.com/meshcore-dev/MeshCore/pull/1727 (Hardware channel activity detection).
Diese ist über set int.thresh 1 zu aktivieren.

Kleine Anleitung hinzugefügt https://meshcore-de.fyi/region_karte

MeshCore-evo 1.14.1_0.1.17 ist verfügbar.
Changelog unter https://github.com/mattzzw/MeshCore-Evo/releases

MelLinux lernt MehsCore "Anfänger Leitfaden Companion"
MelLinux lernt MeshCore "Anfänger Leitfaden Repeater"
MelLinux lernt MehsCore "Anfänger Leitfaden Room Server"

Vortrag auf den Chemnitzer Linux Tag

Bug in MeshCore v1.14.1: RX Boosted Gain Mode schaltet bei Upgrade unerwartet auf OFF
https://rhein-neckar-mesh.de/news.html#article-87

MeshCore App v1.42.0
- added ability to long press ping buttons to use multibyte ping
- added ability to open line of sight tool from coverage map tool menu
- added ability to import and export discovered contacts as json from discover screen menu
- added menu buttons to select all and deselect all contacts while in multi select mode
- added radio checkbox to select region screen to make it more apparent you must select the region to use
- added translations for dutch, french, hungarian, italian, polish and slovak
- antenna coverage tool now automatically fits map to imported json layers
- spaces are now allowed and automatically trimmed from path field in manual trace tool
- improved error message when unable to share contact to internet map due to missing advert blob
- channel messages must now be 10 bytes shorter if a region scope is applied
- fixed bug where contacts full notification would show even when preference was turned off
- fixed bug where adding contacts from discover wouldn't copy over the last advert timestamp
- fixed bug where it wasn't possible to swipe back to exit discover screen on ios

Firmware v1.14.1
https://github.com/meshcore-dev/MeshCore/releases

Also, checkout Scott's new post on the LilyGo T-Watch S3 Plus https://buymeacoffee.com/ripplebiz/lilygo-t-watch-s3-plus

Companion Firmware
- Added GPS support for SenseCAP Solar P1 in #1589
- Added nRF52 power management for RAK3401 in #1984
- Added token bucket based duty cycle enforcement in #1297
- Added support for new GAT562 30S Mesh Kit device in #2009
- Added support for new GAT562 Mesh Tracker Pro device in #1980
- Added LNA toggle CLI commands radio.rxgain on and radio.rxgain off in #1653
- Added MCU temperature to telemetry responses from room servers in #2052
- Migrated Heltec Tracker v2 to KCT8103L in #1936
- Fixed bug where some queued packets would not get transmit in #1877
- Fixed bug where BLE would stay on if turned off from companion screen when already connected in #1991

Repeater Firmware
- Added GPS support for SenseCAP Solar P1 in #1589
- Power off switch long press support for SenseCAP Solar P1 #1871
- Added nRF52 power management for RAK3401 in #1984
- Added token bucket based duty cycle enforcement in #1297
- Added support for new GAT562 30S Mesh Kit device in #2009
- Added support for new GAT562 Mesh Tracker Pro device in #1980
- Added LNA toggle CLI commands radio.rxgain on and radio.rxgain off in #1653
- Added MCU temperature to telemetry responses from room servers in #2052
- Migrated Heltec Tracker v2 to KCT8103L in #1936
- Nodes with GPS enabled will now auto sync time every 30 minutes in #1350
- Fixed bug where some queued packets would not get transmit in #1877
- Fixed bug where automatic adverts were not using the configured multibyte path setting in fcfdc5f

Room Server Firmware
- Added GPS support for SenseCAP Solar P1 in #1589
- Power off switch long press support for SenseCAP Solar P1 #1871
- Added nRF52 power management for RAK3401 in #1984
- Added token bucket based duty cycle enforcement in #1297
- Added support for new GAT562 30S Mesh Kit device in #2009
- Added support for new GAT562 Mesh Tracker Pro device in #1980
- Added LNA toggle CLI commands radio.rxgain on and radio.rxgain off in #1653
- Added MCU temperature to telemetry responses from room servers in #2052
- Migrated Heltec Tracker v2 to KCT8103L in #1936
- Nodes with GPS enabled will now auto sync time every 30 minutes in #1350
- Fixed bug where some queued packets would not get transmit in #1877
- Fixed bug where automatic adverts were not using the configured multibyte path setting in fcfdc5f

MeshCore-evo 0.1.16 ist verfügbar. Dies ist eher ein Business-as-usual-Release, um die evo Firmware auf dem Stand vom Upstream dev Branch zu halten.

Changelog unter https://github.com/mattzzw/MeshCore-Evo/releases

evo v0.1.15 ist released. Neben ein paar wichtigen Bugfixes wurde zusätzlich die Boot Lockout Voltage auch für Xiao NRf und T114 repeater disabled. (Relevant, wenn andere Akku-Typen als Liion wie zB LiFePo, LTO etc verwendet werden)

https://github.com/mattzzw/MeshCore-Evo/releases/tag/v1.14.0-evo_0.1.15

MeshCore-evo v0.1.14 ist released, basierend auf dem heutigen MeshCore v1.14.0 Release.

Ist zwar identisch mit evo v0.1.13 aber um Verwirrung zu reduzieren, habe ich nochmal vom offiziellen main Branch gebaut.

https://github.com/mattzzw/MeshCore-Evo/releases

Absprachen, Fragen und Anregungen wurden in ein neues Wiki verlegt damit jeder (auch ohne Registrierung) dort schreiben kann.

Firmware v1.14.0

https://github.com/meshcore-dev/MeshCore/releases

https://buymeacoffee.com/ripplebiz/path-diagnostics-improvements

MeshCore-evo v0.1.12 ist released: https://github.com/mattzzw/MeshCore-Evo/releases

Es gab eine Menge Fixes, die in den letzten Tagen upstream gemerged wurden. ChangeLog: https://github.com/mattzzw/MeshCore-Evo/compare/v1.13.0-evo_0.1.10...v1.13.0-evo_0.1.12

MeshCore App v1.41.0
- NOTICE: is appears that some users are having issues with the new language translations. advised not to update yet
- https://files.liamcottle.net/MeshCore/v1.41.0/
- added support for parsing new multi-byte path hashes in rxlog
- added support for setting 1, 2 and 3-byte paths in the set contact path tool (requires firmware v1.14.0+)
- added dropdown to select preferred path hash size in experimental settings page (requires firmware v1.14.0+)
- added path hash to unknown repeater names
- added path hash size info to contact details screens
- added button to repeater neighbours menu to quickly discover nearby neighbours
- added button to repeater neighbours menu to remove all known neighbours
- added dropdown menu button to view owner info as guest when editing as admin
- added support for new max hop limit for auto adding contacts (requires firmware v1.14.0+)
- added initial chinese, german, japanese and korean language translations
- app now allows access to repeater neighbours ui when empty as we now have a discover neighbours button
- button to delete neighbours is no longer shown when logged in as guest

Neuer Beitrag: Gute Betriebstechnik

Das Netz wächst rasant. Das ist erfreulich. Nachrichten können Companions in hunderten Kilometern Umkreis erreichen. Allerdings ändert das nichts daran, dass dem Meshcore Netz nur eine einzige Frequenz zur Verfügung steht. Daher kommt es zunehmend zu Kollisionen und Engpässen. Um diese Situation nicht weiter zu verschärfen, sind derzeit einige Maßnahmen dringend empfohlen…

Aus Telegram:

Kurze Info an alle: Wurmberg hat Deny Flood aktiv und wir werden das in den kommenden Tagen mit ANSAGE vorher auch testweise auf Brocken 3 aktivieren. Parallel werden wir Messungen machen wie sich das ganze verhält. Mit den Admins der anderen Core Repeater wie Planet 9 und DB0SN sowie DB0WIZ werden wir uns abstimmen. Nach der Testphase (Brocken 3 ca 1 Tag) werden wir Wurmberg und Brocken auch wieder OFFEN fahren. Hierzu wird es dann aber auch weitere Tests geben. Final werden dann die Harz Repeater und vermutlich auch Planet 9 in ca 4-6 Wochen ALLE auf Flood Deny gehen. Allerdings machen wir das auch davon abhängig, ob das Problem der unterdrückten DM und ACKs bis dahin in der EVO Version lösbar ist.

Bitte das neuste immer ganz oben mit Zeitstempel anlegen, danke.