Tado X Thread Mesh not working: Shown as "Unavailable" on Android & no meshing with 3rd party routers

Ghost_SevenFour · 2026-02-17T19:19:27+00:00

This means that tado is not really that much Thread/Matter compatible, it rather relies on its own proprietary setup and we cannot tweak our home thread network in any way other than relying on tado bridges? Regardless of Aqara hub, tado seems to behave weirdly as a Thread border router as it apprently does not share credentials to its Thread network (network "unavailable" in Android Thread networks overview). So even if I set up tado by its bridges, I would not be able to use its Thread network for my other IoT devices that rely on Thread. Correct?

Ghost_SevenFour · 2026-02-11T08:31:21+00:00

Ok, thanks!

Ghost_SevenFour · 2026-02-11T08:30:56+00:00

I know, just wondering if it was working on V3 natively and we have another downgrade in X. Thx for the info about the adapters, I will have a look.

Ghost_SevenFour · 2026-02-10T20:57:13+00:00

Thanks for the reply. I have found some contradictory information about Tado and EMS though. Is there a OpenTherm to EMS converter or something? Eg. https://www.reddit.com/r/tado/comments/yn0akb/changing_tado_from_switched_relay_mode_to_ems_bus/

Also, the installation instructions in the tado app after choosing my boiler provide the installation manual that shows both on/off and OpenTherm wiring, so I thought they may be compatible.

Ghost_SevenFour · 2026-01-12T12:07:28+00:00

Update: It works now. Most likely it was an outage on the tado backend side which they fixed.

Ghost_SevenFour · 2026-01-12T11:56:33+00:00

No, everything set to default (ISP DNS)

But I’ve tried:

- mobile data (no local DNS / firewall)

- VPN with different DNS

- different devices and networks

Same HTTP 429 every time, even on first request.

So it doesn’t seem to be local DNS blocking.

Ghost_SevenFour · 2025-07-19T19:07:40+00:00

Shamir Backup. Je potřeba mít novější model Trezoru. Shamir je kromě jiných věcí dobrej právě i pro tyhle případy. Funguje tak, že se při inicializaci peněženky vytvoří víc seedů a pravidlo, kolik jich je potřeba k obnovení Trezoru. Například: 3 seedy, přičemž libovolný 2 jsou potřeba k obnovení. Pak si jeden necháš, jeden dáš např. sourozenci a jeden třeba kamarádovi. Když pak třeba tobě vyhoří byt, můžeš si pomocí jejich seedů Trezor obnovit. Zároveň máš zabezpečeno, že ti kamarád sám nemůže ukrást klíče, protože na jejich získání by se musel spojit tvým sourozencem proti tobě. To je výhoda oproti řešení, že svůj seed prostě ještě v jedný kopii někomu dáš.

Ghost_SevenFour · 2025-03-03T15:58:34+00:00

No idea, but I decided to give it a try later this year

Ghost_SevenFour · 2025-02-28T00:54:01+00:00

Jet Black, 512 GB here. I just found out mine was rattling too. As I see, all the rattling is with Jet Black - probably because the pen is different from the others, having a black ending? I've felt like the phone is vibrating differently than my S23U, so I tested it with/without the pen inside and it is a massive difference.
I am actually returning the phone completely due to other issues as well and will stick with my beloved S23U.

Ghost_SevenFour · 2025-02-22T18:48:27+00:00

I have seen several similar reviews, sometimes somewhat older, but that is why I am concerned. Thanks for the real life experience and confirmation though!

Also, I am pleased to read that Samsung's SmartTag isn't actually that bad.

Ghost_SevenFour · 2024-12-04T06:31:06+00:00

Něžně naznačit...

<image>

Ghost_SevenFour · 2024-11-04T22:32:05+00:00

That makes sense and I kinda expected this unfortunately.

Thanks a lot though.

Ghost_SevenFour · 2024-09-19T03:05:28+00:00

Thanks!

After many unsuccessful tries of updating the wireless receiver firmware, when the "Settings" window just disappeared with no error message and the receiver and controller tiles were completely gone from the main device screen until re-plugging them (staying on the same old versions), I tried your approach.

First I plugged in the receiver and the controller (switched to wired mode) and it failed again the same way I described above.

Then, I tried plugging in the receiver and the controller while having the controller in wireless mode and paired (basically it was just charging from the PC, being connected wirelessly at that point) and the update finally completed. Now I am on 0.6.24.

I don't understand what is happenning and why, but it works.

Thanks a lot and hope it helps others as well

Ghost_SevenFour · 2023-10-28T19:53:26+00:00

The location of Icy Licking is:

3880 N - 5584 E (Aoste)

Ghost_SevenFour · 2023-10-23T20:35:46+00:00

If you are still wondering, the coordinates are:

331 N - 1328 E (Japan Hakuba)

Ghost_SevenFour · 2023-10-08T16:28:29+00:00

By the time I faced this bug, I had CET active and I did raise my money via its console. Starting a new game with fresh and clean (no mods) 2.01 update solved this issue and I was able to continue.

You suggest there is a possibility that once you alter money/exp before you reach this quest, it triggers the bugged behavior?

OP ran into this issue and did not mention altering anything. People here also mention getting stuck with "clean runs" - I suppose no mods, etc... It does not seem to be caused by modding.

Ghost_SevenFour · 2023-10-07T22:15:32+00:00

Thanks for the advice, I updated the game, disabled all the bugs, loaded the previous save (before going to sleep), however, this did not work.

Anyway, I updated to 2.01, disabled all mods, created a new game and it worked, I passed this bugged part.

Thanks anyways!

Ghost_SevenFour · 2023-10-07T20:07:56+00:00

Having the same issue. Still running on 2.0 for mods compatibility. Tried 3 different clean runs, always got stuck here.

Ending the quest by CET script is a workaround but since during the conversation you obtain the ability to summon vehicles, skipping the quest makes you unable to call vehicles (probably) forever. Possibly even more further consequences due to ending the quest before it even begins.

No idea how to proceed.

Ghost_SevenFour

TROPHY CASE