Syncing thread credentials - Thread Channel Mask is missing from the dataset

Hi

I’m trying to setup more thread (and matter) devices at home.
So far I’ve successfully setup Eve water guard with homekit over thread.
But I’m currently trying to setup Eve energy but it fails, so I wanted to sync my thread credentials to my Android phone but I’m getting unknown error in the UI and the logs says the below text.
I’m using HA in docker and have installed openthread border router with skyconnect on the base Linux install.
If I run ot-ctl dataset active I can see it has an channel mask.

What should I do?

11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: java.lang.IllegalArgumentException: Thread Channel Mask is missing from the dataset
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at com.google.android.gms.threadnetwork.ThreadNetworkCredentials.zzb(com.google.android.gms:play-services-threadnetwork@@16.0.0:11)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at com.google.android.gms.threadnetwork.ThreadNetworkCredentials.(com.google.android.gms:play-services-threadnetwork@@16.0.0:9)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at com.google.android.gms.threadnetwork.ThreadNetworkCredentials.fromActiveOperationalDataset(com.google.android.gms:play-services-threadnetwork@@16.0.0:1)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at io.homeassistant.companion.android.thread.ThreadManagerImpl.isPreferredDatasetByDevice(ThreadManagerImpl.kt:241)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at io.homeassistant.companion.android.thread.ThreadManagerImpl.access$isPreferredDatasetByDevice(ThreadManagerImpl.kt:26)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at io.homeassistant.companion.android.thread.ThreadManagerImpl$isPreferredDatasetByDevice$1.invokeSuspend(Unknown Source:16)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:28)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:100)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:101)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at android.os.Handler.handleCallback(Handler.java:959)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at android.os.Handler.dispatchMessage(Handler.java:100)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at android.os.Looper.loopOnce(Looper.java:232)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at android.os.Looper.loop(Looper.java:317)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at android.app.ActivityThread.main(ActivityThread.java:8592)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at java.lang.reflect.Method.invoke(Native Method)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:580)
11-25 21:09:20.851 25426 25426 E ThreadManagerImpl: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:878)

Sometimes the Google Play Cache is bugged and needs to be cleared.

Thank you, after a couple of reboots on android (and HA) that part seems to be working.

Now I’ve to figure out why there seems to be something iffy with the thread network since I cannot add devices to it for some reason

Oh, well kinda spoke too soon.
I managed to pair a Matter/thread device now (eve energy)
BUT when trying to move another Eve Water Guard to thread Im back at

Unknow TLV type 74 for class aiohomekit…

Which I had a while ago as well…

SIGH

Thread is not always Matter.
Eve Water Guard might be just a Thread device and not a Matter device.

Correct, its homekit over thread or whatever its called.
But there seems to e fix for that hopefully coming in 2024.12 according to the github issue.

Thank you for your help.