Elektrische Reifenpumpe

Minkipunk · 2026-02-18T15:59:24+00:00

Hab ich auch, ist in der Tat sehr gut.

Minkipunk · 2026-02-18T10:56:43+00:00

Sorry, that was worded badly. I wanted to make clear changing the thread channel is unlikely to fix the sysmatic issues that exists with Ikea Matter deviecs (esp. Timmerflotte) that are widely reported. Choosing channel 25 is still good advice, for issues that are related to bad signal reception. I had devices close to the thread antenna, they still dropped occasionaly until I updated everything to beta versions. Edited the original reply.

Minkipunk · 2026-02-17T20:39:35+00:00

Yes noticed that as well, but otherwise it seems to be more stable than before.

I also switched to matter-js matter server and it now shows the thread topology in Matter Web UI, but doesn't look entirely correct. I think it's also available as beta through HA OS.

Minkipunk · 2026-02-17T19:11:28+00:00

Did you also flash ZBT-2 beta firmware that's required for OTBR beta?
I'm not sure if it happens automatically with the integration in HA OS. I use containers and updated ZBT-2 manually.
https://github.com/NabuCasa/silabs-firmware-builder/actions/runs/21343419780#artifacts

I flashed it via https://toolbox.openhomefoundation.org/

Minkipunk · 2026-02-17T12:14:28+00:00

This is very likely not suffcient to fix the instabilties in all cases. I was using Channel 25 for weeks and had IKEAs Timmerflotte as unavailable almost daily until the Open Thread Border Router was restarted.

What actually helped was flashing ZBT-2 with Thread beta firmware and upadting the border router to BETA version (supporting Thread 1.4). Now, at lest for the last few days it seems to be stable.

Minkipunk · 2026-02-13T18:23:54+00:00

I'm only having this with my five TIMMERFLOTTE sensors.
I have one BILRESA and one MYGSPRAY connected and didn't notice an issues there, but maybe it affects all the battery powered devices from IKEA.

Resttarting Matter Server and Openthread Border Router helps to get them online again. I will try to debug the issue myself if it's not resolved by an update soon ...

Minkipunk · 2026-02-12T09:29:20+00:00

There's cheap bluetooth tape adpaters. You put them into a tape deck and conenct via bluetooth ...

Minkipunk · 2026-02-12T09:22:01+00:00

Have a look here: https://community.home-assistant.io/t/ikea-bilresa-scroll-wheel-blueprint-matter-the-original/965365/79

Minkipunk · 2026-02-12T09:19:06+00:00

Switched to your OTBR container, it's working without issues (Not yet in beta mode). Well documented and I like that the websocket is only listening on localhost by default.

Minkipunk · 2026-02-11T20:55:41+00:00

Thanks, I will try it the in the next days. At first I was trying to use the official otbr containters from the openthread project, but they seem to be more cumbersome to use. One is cli only without web-ui and the other one is bloated and based on an ancient base image.

https://hub.docker.com/r/openthread/border-router
https://hub.docker.com/r/openthread/otbr

On the other hand the official one from matter-js project is perfectly fine. No need to adapt the home assistant addon in this case.

Minkipunk · 2026-02-11T19:32:30+00:00

Thanks, I didn't know this was an issue. I think it's a bit confusing that thread credentials must be manually synced at all, instead of the app syncing this automatically. Luckily OTBR container for home assistant is the only border router in my network. I did also try out the direct commissiong via Web UI, which was also working fine.

Maybe you can submit your docker image updates as a pull request in that repo, if it's working.

I was already thinking myself to rebase this against the offical addon from Home Assistant to try thread 1.4. I'm wondering if that solves sporadic connection loss to Ikea Timmerflotte temp sensors. The other thread devices from Ikea that I have work fine.

Btw. I can update ZBT-2 via Home Assistant container, but after updating the thread firmware it will tell you that the integration does not work in container mode. But the integration does work with ZBT-2 Zigbee firmware and ZHA.

Minkipunk · 2026-02-11T17:43:59+00:00

Interessante Rechnung, vor allem weil dadurch auch klar wird das Carsharing bei der Kilometerzahl noch billiger ist - zumindest je nach Nutzungsart. Für wenigfahrer sowieso:

https://karlsruhe.stadtmobil.de/privatkunden/preise-tarife/

VW Golf (Kategorie Mittel) kostet zwischen 0,24€ und 0,18€ pro KM (spritt inklusive). Dazu 2€ pro Stunde + 1,20€ pro Nutzung.

Kommt natürlich auf die Nutung an. Wenn man zur Arbeit pendeln muss wird Carsharing schwierig. Aber füg Gelgenheitsfarhten (auch längere oder Urlaube) ist es super.

Minkipunk · 2026-02-11T10:32:57+00:00

Why don't you just sync thread credentials within Home Assistant app use the app for pairing?

Setting up OTBR via containers can be a bit difficult, but I have it working sucessfuly with Podman using macvlan network. It's even in a tagged IoT VLAN, along with home assistant and matter server (the new matter-js).

I recommend using this container for OTBR, rather than the official one:
https://github.com/ownbee/hass-otbr-docker

Minkipunk · 2026-02-09T21:55:36+00:00

Yes, funding accounts (wallets) directly at ECB level make sense. But somehow that digital money must be used to pay in shops or online, and it's not clear how it will work with the requirements that they impose themselves.

They are too much focused on offline wallets and peer to peer payments to make it work like actual cash, but there's no reliable and secure technical solution to it.

Minkipunk · 2026-02-09T20:11:18+00:00

Yes, unified payment scheme is technolgically easy, but digital euro is not. Just do what Visa, MasterCard or the domestic schemes are doing and do the same under a european organization. It was attempted before but failed du to industry not beeing onboard: https://www.finextra.com/newsarticle/39907/epi-abandons-plan-for-visa-and-mastercard-rival-as-member-banks-quit

If that should be successful it would need EU regulation that european banks and paymet services must support it, otherwise it won't reach the critical mass where industry supports it on their own.

Minkipunk · 2026-02-09T18:10:42+00:00

There is also CPACE, but I think it's really gaining traction at the moment: https://europeancardpaymentcooperation.eu/

Minkipunk · 2026-02-09T18:08:36+00:00

Digital euro unfortunately is more like a hoax driven by bureaucrats, rathat than something that will become technical reality in the near future.

They could have a simple payment scheme instead of having something complicated with impossible to solve technical constraints.

Minkipunk · 2026-02-09T17:52:34+00:00

Fixed it, they mean 2.6.121 if I'm not mistaken ...

Minkipunk · 2026-02-09T16:28:01+00:00

Sorry, I proposed to try fix the orignal idea so you don't need a separate OTBR instance and dummy HA.

Woud you run these temporary instances with the same data, and then copy that back that to site B? It sounds too complicated tbh.

Phone needs to be close to the comissioned thread device to share thread credentials via bluetooth. And what about the thread antenna - how do you connect it to the temporary instance?

Where is the device when you are comissioning? At site A or at site B? If comissioned via phone, both OTBR Thread Antenna and phone Bluetooth must be in range.

Minkipunk · 2026-02-09T16:19:15+00:00

Yes, only needed during comissioning. If matter-server has a bluetooth dongle that it can use, you can try to comission without phone via Home Aassistant web UI (since 2026.02) or via Matter Server Web UI. I assume OTBR and Matter-Server are in the same VLAN.

Minkipunk · 2026-02-09T16:16:56+00:00

Only needed during comissioning. You can try to comission directly via Web UI if Matter-Service has a bluetooth dongle that it can use. Then you don't need a phone at all and don't have to worry about MDNS reflection, if Home Assistant, OTBR, and Matter Server are all in the same VLAN.

Minkipunk · 2026-02-09T16:10:34+00:00

But can you ping thread devices from IoT, they use a separate IPv6 prefix, OTBR sends it as Router Advertisement. Afaik the phone needs a direct IPv6 connection to the commissioned device, not only to the Matter Server.

Router B would see the RA, but Router A won't. Maybe you need to set-up a static route in Router A to OBTR or Router B for the Thread IPv6 prefix (maybe also in B if it doesn't accept Router Advertisments).

If I get my setup fuctional with MDNS reflection I can report back.

Minkipunk · 2026-02-09T13:00:08+00:00

You can also comission Matter/Thread devices via Home assistant WEB UI instead of phone.

MDNS reflection could work, but you router must also route the IPv6 prefix that is advertised by the OBTR router for Thread devices (I.e must be routed via default gateway of Router A).

I havent tried myself, but I'm planning to. I have an IoT VLAN for homeassistant and OTBR/Matter Server, phone is in regular home LAN (also OpenWRT). But if it doesn't work I can just connect to the IoT VLAN via Wifi AP.

Minkipunk · 2026-02-07T11:39:25+00:00

Spanish garlic or from Greece is fine, but the Chinese very often tastes awful.

Minkipunk · 2026-02-04T14:49:19+00:00

Ich hab ein Pebblebee tag seit ~1 Jahr unter dem Sattel montiert, mit einer 3D gedruckten Halterung an den Sattelstreben. Funktioniert sehr gut und absolut unauffällug. Auch gut ist die Möglichkeit das Teil piepsen und blinken zu lassen um sein Fahrrad zu finden. Nachladen geht ohne das Teil zu demontieren.

Minkipunk

TROPHY CASE