Problems after HA Upgrade to 2026.5.1

[Chuck-it]

Hi,

Node not connecting after upgrade to HomeAssistant 2026.5.1

Companion is connected via USB ttyACM0

[Chuck-it]

... after 3 raspi reboots running again smootly ;) i use HA with docker

[Chuck-it]

[frav-se]

Hi,

I have a similar issue with my two(2) Home Assistant installations, at different locations. I use rPI5 8GB on both locations. The MeshCore LoRa devices that are USB-connected to the HA rPI5 are Heltec ESP32 v3.2 on both locations and MeshCore official USB firmware v1.15 .

Since latest HA updates the LoRa module seems to be hard to connect to. I have them both on /dev/ttyUSB2. After an change in some way like an software update, reboot, disconnect/reconnect of the LoRa USB cable, the MeshCore integration have a hard time to reconnect to the LoRa device.

Some times it it works, some/most times it dosen´t...

The log says:

2026-05-14 15:58:43.877 INFO (MainThread) [meshcore] Serial Connection started
2026-05-14 15:58:58.878 ERROR (MainThread) [meshcore] No response from meshcore node, disconnecting
2026-05-14 15:58:58.878 ERROR (MainThread) [meshcore] Are you sure your node is a serial companion ?
2026-05-14 15:58:58.878 ERROR (MainThread) [custom_components.meshcore.meshcore_api] Failed to create MeshCore instance
2026-05-14 15:58:58.879 WARNING (MainThread) [custom_components.meshcore] Connection attempt 1 failed, retrying in 5 seconds...

Just to make sure it wasn´t any USB power issues from the rPI5, I have bought two externally powered USB hubs. Kensington UH7000C 4A/20W. But it is still the same issue.

When I try to "Reconfigure USB Connection" in the integration, it says "Failed to Connect"

I´m out of ideas how to proceed to get it working.
.
.
.

[Gopten]

I tried going back to 2026.5.0 but it didn't help. I noticed the other day when I went to 2026.5.1 it took 4 minutes longer for startup to wrap up.

[Chuck-it]

map is going crazy ^^

[Chuck-it]

[frav-se]

After some elaborating... I found out that even if I have MeshCore Companion >USB< firmware, the companion have "Bluetooth" in the device menu (Bug?). BT was in this menu enabled/activated, so I disabled BT in the menu and then HA MC Integration started.
I don´t know if this was pure one time luck or not? But it obviously did something positive, atleast this time... I have to try this "trick" on my other location when I´m there next time.

[Chuck-it]

[awolden]

FWIW I'm running 2026.5.2 in Container on the same Heltec hardware without any of these symptoms. That makes it hard to pin on the integration or the HA version itself.

To debug further, would need:

• companion firmware version
• exact board (V3, V3.2, etc) and revision if known
• USB cable + port (powered hub or direct?)
• full debug log from connection attempt (three dots on the integration > Enable debug logging > reproduce > Disable to download)

Without that it's hard to find the common factor across reporters.

[Gopten]

I deleated the integration and reloaded several versions but they made no difference.
This error originated from a custom integration.

Logger: custom_components.meshcore.meshcore_api
Source: custom_components/meshcore/meshcore_api.py:141
Integration: MeshCore (documentation)
First occurred: 10:49:21 (311 occurrences)
Last logged: 14:16:06

Failed to create MeshCore instance

This error originated from a custom integration.

Logger: meshcore
Source: custom_components/meshcore/meshcore_api.py:109
Integration: MeshCore (documentation)
First occurred: 10:49:21 (622 occurrences)
Last logged: 14:16:06

No response from meshcore node, disconnecting
Are you sure your node is a serial companion ?

This error originated from a custom integration.

Logger: custom_components.meshcore
Source: custom_components/meshcore/init.py:301
Integration: MeshCore (documentation)
First occurred: 10:49:21 (210 occurrences)
Last logged: 14:15:46

Connection attempt 1 failed, retrying in 5 seconds...
Connection attempt 2 failed, retrying in 5 seconds...

Logger: meshcore
Source: runner.py:289
First occurred: 13:43:54 (1 occurrence)
Last logged: 13:43:54

I reflashed my Heltec V3 directly connected by 30cm cable to HA with Heltec_v3_companion_radio_usb-v1.15.0-dee3e26-merged.bin and the problem hasn't recurred in past 24hrs.