Thread credentials synchronization not working

[LogimacGER]

Describe the issue you are experiencing

Im using Multiprotocol with SkyConnect. ZHA working fine.
Matter, Thread and Open-Thread-Border-Router is visible under "devices".
Last week i got a EVE energy matter device. When i want to add it with HA android app i get a message "border router needed".
I don't have any other border-router (Homepod or Nest hub) in my network.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Almond

What is the version of the add-on?

1.1.1

Steps to reproduce the issue

1. Adding a Matter Thread device.

System Health information

System Information

version	core-2023.4.1
installation_type	Home Assistant OS

dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.10.10
os_name | Linux
os_version | 5.15.84-v8
arch | aarch64
timezone | Europe/Berlin
config_dir | /config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	5000
Installed Version	1.31.0
Stage	running
Available Repositories	1251
Downloaded Repositories	5

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 9.5
update_channel	stable
supervisor_version	supervisor-2023.04.0
agent_version	1.4.1
docker_version	20.10.22
disk_total	219.4 GB
disk_used	9.6 GB
healthy	true
supported	true
board	rpi4-64
supervisor_api	ok
version_api	ok
installed_addons	File editor (5.5.0), Terminal & SSH (9.6.1), ArgonOne Active Cooling (29c), SSH & Web Terminal (13.1.0), Matter Server (4.2.0), Silicon Labs Multiprotocol (1.1.1)

Dashboards

dashboards	2
resources	1
views	5
mode	storage

Recorder

oldest_recorder_run	1. April 2023 um 14:42
current_recorder_run	7. April 2023 um 07:54
estimated_db_size	700.81 MiB
database_engine	sqlite
database_version	3.38.5

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

No response

Additional information

No response

[MattWestb]

Have you looking if the boarder router is have getting the data set OK so it can being used by the system ?
If you clicking on thei you shall getting the network settings and the dataset / TLVs if not you cant communicating with the OTBR.

[LogimacGER]

Dataset is available

[MattWestb]

I dont have any real Matter device that is working one thread so i have not paring them with the companion.
My EVE Energy is not upgraded and they is pared with BT to HA and then putting them on the thread network and its working great (as long the BT is working for paring).

I think the problem can being that the mobile can finding the thread boarder router so somthing strange with then WiFi network / the network the OTBR is on.

[agners]

If you have no Google Thread Border router, the companion app should synchronize your Thread credentials with Google, and use them.

Last week i got a EVE energy matter device.

I assume that is really the one with the Matter firmware on it (not HomeKit?)

@jpelgrom do you maybe have an idea why it fails/what goes wrong here?

[jpelgrom]

@jpelgrom do you maybe have an idea why it fails/what goes wrong here?

I'm not completely sure why it is giving this error. Like you said, if there are no Google Thread border routers the app will add the add-on's (which should then be used by Google's flow).

@LogimacGER Could you start Matter commissioning from the app, and get the app logs afterwards (Settings > Companion app > Show and share logs)? It should include log lines starting with "ThreadManagerImpl:" which will tell more about the status. This should (hopefully) be Thread import to device completed or Thread: device prefers core preferred dataset.

[LogimacGER]

Sorry for the late answer.
Do i have to force the sync with google?
When i start Matter commissioning the google service matter start and fails.
I can't find "ThreadManagerImpl:" in the logs but something with "WebviewActivity: Matter commissioning status non-ok/IN_PROGRESS"
homeassistant_companion_log_3-22-2023_12-56-43.txt

[jpelgrom]

Thanks for the full logs. It looks like the app is following the flow correctly, but it's skipping syncing the credentials.

I noticed a lot of HTTP 410 Gone errors for the URL http://192.168.178.20:8123/ in the logs, is native app functionality (eg sensors) working correctly? If the app can't read configuration data, it might skip syncing because it thinks your user/server doesn't meet the requirements.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[MattWestb]

For resetting the bot !!

Only large problem for my i cant using more HA with addon running OTBR then the DNS is braking all communication to my thred devices. If only having one running all is very stable but i have no matter devices (have not updating my EVE devices) but i like have redundancy in my system then moving it to the production system.
Larges test system Zigbee part is 31 most SEDs and is rock solide and have 3 more but the OTBR is no running on them for the moment.

And great work done and hope we can getting it in production quality soon !!

[agners]

@LogimacGER have you been able to resolve this issue? If not, what type of installation are you running?

[LogimacGER]

@agners this issue is still present. I'm running the latest version of Homeassistant OS on a raspberry pi 4 4GB (with M.2 SATA SSD) with sky connect (ZigBee devices working without problems). Also Matter and silicon laps multiprotocol is up to date. It seems my phone can't finde open thread boar router on my network. Homeassistant is connected via LAN and my phone with wifi of course. I tried another android phone but without success.

Once I did a clean install of Homeassistant but that did not work .

[agners]

@LogimacGER can you check the questions in comment #3582 (comment)?

It seems that the App has difficulties reaching Home Assistant for these particular requests. What type of HA installation do you use?

[LogimacGER]

@agners What are you meaning with "type of HA installation"? HA OS on a Raspberry pi.
I don't have problems using the app.

[jpelgrom]

For anyone still experiencing issues, could you download the latest update for the Android app (available now from the Play Store, version 2023.7.5), manually sync Thread credentials in Settings > Companion app > Troubleshooting and post the result here? That should make it easier to understand where it's failing.

[LogimacGER]

Homeassistant prefer a different network than my phone does. Maybe become HA rund over LAN and my phone over WiFi?

When I'm at home I set up Homeassistant over WiFi only.

[jpelgrom]

Homeassistant prefer a different network than my phone does. Maybe become HA rund over LAN and my phone over WiFi?

LAN/WiFi shouldn't matter, this is about Thread networks :) Not sure why your device prefers a different (non-existent as it says you don't have a border router?) Thread network named 'home-assistant'.

Unfortunately there is no way change the preferred Thread network on Android devices currently. The only 'solution' we know about is to clear all data for the Google Play Services app (system settings > Apps > All apps > Google Play Services > Storage & cache > Manage space), which stores the Thread networks. Keep in mind that clearing this will also clear other Google data that only exists on your device such as your Google Wallet cards (😥).

[LogimacGER]

The issue is solved after silicon laps multiprotocol update to version 2.3.0.

[jpelgrom]

Closing this as the original author has resolved the issue, and the app has received several updates to improve Thread credentials sync:

• Manually sync and view results in settings menu to help with troubleshooting (in stable release 2023.7.5-full)
• Improved updating/removing of credentials previously added by the app during sync (in beta release)

If anyone is still facing issues with Thread sync to Android, feel free to open a new issue with the output of the manual sync option while using the latest beta (or next stable) release of the app, and information about your setup.