I have a ZBT-2 for thread, and i bought some of the ikea matter hardware . But unable to pair it.
My internet searching says there might be issues around ikea item. So i wonder, is there a cheap Thread item i can buy to test my thread setup?
My car won’t start. Can somebody tell me where to buy a cheap car to see if it starts?
See any flaw in your logic?
Why not tell us which Ikea model you are having problems with, what you have attempted, and what any error logs are telling you? Maybe you can fix your first device without having to buy another.
4 Likes
Klippbok, and lightbulbs.
Pairing Failed . ( From iphone)
Im asking for a known good device, so i can make sure my network is working.
Logs:
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9829
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9830
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9830
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9830
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9830
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9830
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9830
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9830
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9830
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9831
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9831
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9831
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9831
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9831
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9832
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9832
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9832
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9832
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9832
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9832
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9832
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9832
00:06:10.132 [W] P-RadioSpinel-: Error processing result: NoAddress
00:06:10.132 [W] P-RadioSpinel-: Error waiting response: NoAddress
00:06:10.157 [N] MeshForwarder-: Dropping IPv6 None msg, len:40, chksum:0000, ecn:no, sec:yes, error:NoRoute, prio:normal, radio:all
00:06:10.157 [N] MeshForwarder-: src:[fd3e:b3da:c169:4be0:804a:6075:c1a2:61a4]
00:06:10.157 [N] MeshForwarder-: dst:[fd3e:b3da:c169:4be0:0:ff:fe00:9c00]
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9833
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9833
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9833
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9833
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9833
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9833
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9833
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9833
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9833
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9833
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9834
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9834
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9834
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9834
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9834
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9834
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9834
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9835
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9835
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9835
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9835
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/9835
Sounds like you have a networking problem. Do you have IPv6 enabled? Do you have any VM, VLANs configured?
Its multi vlan , opnsense firewall.
I did give homeassistant both a nic in both lan and wifi.
I know that thread uses ipv6, i tought it communicated on a seperate network not wifi.
Yes, regardless if it uses Thread or WiFi as the transport layer, the data still needs to make connection.
You need to check your network configuration to see how those UDP packets are going to reach their destination via IPv6, which is what the error log seems to indicate is the issue.
I would probably look at your VLAN configuration first. Are you expecting data to travel between subnets without routing? Are you letting your UDP data packets through the firewall?
I’ve installed 2 alpstuga’s in the last few days… ZBT-2 plugged into HA Green. I just upgraded OTBR, HAOS and Core… Not sure if this was there before or not, but if you go into Apps (add ons) there is an OTBR entry. If you open that, there is a setting for:
“NAT64
Enable IPv6 to IPv4 network address translation. This allows Thread devices to communicate with devices on the Internet.”
Seems the problem is network/internet related, not sure it will help but don’t think it will hurt anything. No idea if a restart is required. It can be put back if it changes nothing
I checked my logs after the upgraded OTBR upgraded I got 5 of those same error messages, but then they cleared and loaded:
"Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to …:
I guess I’m saying upgrading OTBR also can’t hurt as you’re not working anyway, and if you back it up first, you can put it back.
The upgrade was specifically to fix “Incremental Thread border router updates; recent versions (2.16.x) have open bug reports for timeout errors with some hardware (ZBT-2 issues reported 5 days ago)”
I agree it sounds like a network/firewall issue, not a problem with the device.
Please come back here when you have it working and tell us what you discovered. A lot of us here are considering Thread but waiting to see how well things turn out for early adopters. Especially around the issue of internet/cloud dependencies. Zigbee and Z-Wave devices do not require any external connectivity to activate, or to use. So for those of us who use those protocols, that can be an area of concern.
Having a water leak sensor have access to the internet is not going to happen. Il see if i can find out whats wrong with the IPV6 enviroment and report back
1 Like
You need to make sure your network firewall is not blocking mDNS, this is your issue, it is a requirement for matter over wifi and matter over thread devices to work.
I have mDNS Repeater in opnsense, i seems like its cache some old mdns settings atm. So i have to wait a bit to see when that expires
1 Like
You may want to read up on this forum about Matter and internet access dependencies. I’m just an observer, trying to learn all I can before making the jump. But if what I’ve been reading is true, there is at a minimum a requirement to connect to pair the device, and possibly an ongoing need for external access to maintain some functionality. Again, I’d be interested in anything you learn about this issue.
The only details that matter is that for thread you need a properly setup border router that supports the protocol, matter over wifi only requires the matter server integration running in home assistant and that you have an SSID able to connect them to the network your instance is setup on to have those devices added as there is no need for a dedicated antenna device for it.
In both cases you need IPv6 and mNDS supported and not blocked on the network to allow devices to connect and communicate with them.
Matter devices are local devices, you don’t need a connection to the internet to add them, just scan the QR code or input the matter code printed on it to add it via the companion app on your phone.
The only time you would need a 3rd party app is for admin level setup and management like in the case of my U300 lock which is connected via thread through my GLS200 where I don’t need to be in the app have its states populate in HA but to admin users I need the aqara app. (the boarder router also does BT over MQTT but I have yet to work out exactly how to connect devices to it to pass into HA other than seeing it being active in MQTT explorer)
My matter over wifi power-boards have all entities available out of the box and just pair as stated previous with the matter code offline.
The only other thread based devices I have at this time are the aqara P2 door sensors I have one of 4 setup on my security door and that was able to be setup offline as well no issue once put into paring mode like with the previous two examples.
Here is where I did my general setup details as I learned what I can and should setup with that border router I use: https://community.home-assistant.io/t/gl-s200-and-matter-over-thread
Yea that is what i expected, most matter devices should work offline. Esp those that use thread for transport.
That being said, i suspect my current issue is a ghost network card, making thread attemt t send messages via a none existing interface.
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/356
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/356
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::13b2:6c80:4840:5595/end0.104/356
I even tried to reset the network settings. I suspect the next step is insert ssh key into HA, so i can access the root OS.
Out of curiosity are you using it in multiprotocol mode? if so then this has been abandoned as a supported feature of it due to the stability issues and there have not been further firmware updates since to try resolve it as such its recommended to run it either in zigbee or thread and avoid multiprotocol entirely.
I have the zbt-1 myself and have it dedicated to zigbee hence the GLS200 for thread (I bought a spare zbt-1 thinking my one was failing at the time but the other issue I had was that the usb hub kept making it disconnect).
If the fix is something else network wise then we can rule out multiprotcol mode still being an issue with the zbt-2 like it was with the zbt-1.
Also make sure you are on the same wifi network when commissioning and your matter credentials are up to date on the phone.
I have 3 dedicated radios, zbt-2 zigbee, zbt-2 thread and a zwave.
ok so its only the one dedicated to thread that is the issue here so we can rule out a multiprotocol issue via single co-ordinator setup.
Since you have 2x zbt-2’s I wonder if its a conflict with them being on the same host instance due to hardware ID’s etc just like with VM instances and having the need to try assign different ports to them manually.
If you are able to test removing the zigbee one just to see if the thread one starts working.
Hey, just leaving this here if it helps anyone… I also have not been able to connect new Ikea matter devices until I got to this post. Since I am not using an apple phone like in the linked post I went to android companion app SETTINGS > Companion App > Troubleshooting > And clicked on Sync Thread credentials… And I could connect all devices without problems…