Repository navigation
0.7.0
The first release under the meshtastic org's maintenance, with firmware 2.8 support, a current web client and a long list of fixes.
Before you upgrade
- Home Assistant 2026.8 or newer is required.
- Firmware 2.8 renumbers nodes to a number derived from their public key. The integration follows the renumbering on its own, keeping your devices and entity ids.
- The web client needs an admin to open it. The radio API it proxies used to answer anyone who could reach Home Assistant. Now the Open button in the Meshtastic sidebar issues a token for that gateway, and only Home Assistant admins can press it. A token lapses after an hour unused, a day, or a Home Assistant restart; press Open again. Old
/meshtastic/web/gateway_*links lead to the sidebar. - Secrets are gone from state attributes. The gateway entity no longer publishes the node's Wi-Fi password, private key, MQTT password or Bluetooth PIN, and channel entities no longer publish their PSK. Values written before the upgrade remain in recorder history and backups: change those passwords, regenerate the node's key pair, and purge the old history with
recorder.purge_entities. - Gas resistance now reports kΩ instead of hPa, so its long-term statistics will flag the unit change.
New
- Firmware 2.8 support and protobufs from the
v2.8.2line, including thesensitivefield metadata. - Bundled Meshtastic web client v2.7.2, built reproducibly from the upstream tag, with routes that survive a reload and a long poll that no longer drops idle connections.
- Reconfigure an entry's connection, and diagnostics with secrets redacted.
- Events for mesh beacons and detection sensors, waypoint geofence fields, and
reply_id,is_reaction,from_id,hops_away, SNR and RSSI on text messages. Send replies and reactions from the services. - Sensors for noise floor, heap, host metrics, soil and water, lightning, ADC channels, and environment voltage and current; packet signature and current-LoRa node fields; PDOP/HDOP/VDOP on device trackers.
- MQTT downlink to the radio in client proxy mode.
- Entity names, icons and exception messages in translations, entity categories, and stale device removal.
Fixed
- Entities go unavailable while the gateway link is down, and the integration reconnects after the radio reboots, refreshing channels and node config.
- Coordinator updates no longer re-add every entity, which logged "does not generate unique IDs" errors.
- Gateway, channel and DM entities belong to their config entry, ahead of Home Assistant 2027.8.
- A failed setup releases the radio's single API connection instead of fighting the next attempt.
- The TCP proxy isolates its clients and bounds transport operations.
- Bluetooth connects through Bluetooth proxies and on devices without a PIN.
lastHeardno longer resets to 1970, reading the node database no longer hangs while the radio reconnects, and nodes without a hardware model get devices.- Serial uses the
serialxthat Home Assistant ships.
Contributors
@broglep, @kernel-oops, @Ixitxachitl, @zdenek-biberle, @richardpowellus, @randybb, @Gooman-rus, @Paxy, @dereckhall, @e11en, @ecapuano, @gwe8r7hw837rh87h, @ov1d1u, @skgsergio, @jamesarich