Removing a Matter Device from Commissioning Service

I have a couple of questions as a non-matter user but interested in trying it out. I looked around here and on the web, but didn't see an answer to these. I'm thinking about dipping my toes into the matter ecosystem as I see some cost savings for a remote location.

  1. After adding a matter device to Alexa, Google, Apple Home, etc., and then adding it to Hubitat, can it be removed from the commissioning service/device? Meaning, I do currently use Alexa at home for some stuff, but thinking about a totally local setup at another location where I don't have Alexa devices or any other cloud service for that matter. Was thinking about temporarily setting one up for commissioning and then removing it. Also, I see some stuff where certain apps for the device/manufacturer might be able to commission? And I wouldn't need the could services?

  2. Does the initial commissioning and adding to a network (matter only so WiFi or Ethernet) get an IP address from the DCHP server? What if I don't have IPV6 enabled or am extremely weird about static addresses in my network? Does it just add it to the network without messing with DHCP? This I'm sure I could have probably found somewhere on the internet, but figured I'd ask those in the know here...

My OCD wants it to work like I add the device via whatever service, add it to Hubitat, its exists floating around on my network using IPV6 without my router or anything else seeing it and it doesn't suck up an IP address I will notice. :crazy_face:

Once a device is commissioned into Hubitat via Matter, it can be removed from the other commissioning service. If you use Alexa to get a device into Hubitat, you can remove it from Alexa once finished and it stays in Hubitat fine. As for using a manufacturer's app, it really depends on the device, but this is possible. My Third Reality Multifunction Night Light is only connected into the 3R-Matter app (by Third Reality) and Hubitat. I do this to get firmware updates, but I do not need that device in Apple Home or Google Home (which are used in my house).

As for the network, my Matter via WifI devices do take an IP address from my router (Google Nest Pro). I do not have IPv6 enabled and just run everything on fairly simple settings. I have not done a DHCP reservation for them because it is not needed. Matter devices talk via an internal IPv6 network that is created by themselves and the controller.

There are others in the forum that can probably give more in-depth advice on the networking piece depending on your setup.

3 Likes

That's awesome and exactly what I was hoping to hear... Thank you! Enough for me to play with and see... As mentioned before, I want to get some matter devices and install them at a remote location. Seems cheaper than investing in Z-Wave or Zigbee as that location is semi-temporary, although I love the other protocols and have a tone of those devices at home... :slight_smile:

I'm not super knowledgeable on the networking side, just know enough to be dangerous. I'm running OpnSense as my router/firewall with several WAPs (same at the remote site) but very particular about static IP assignments... I knew Matter uses IPV6, but I guess the device has to connect to the WiFi and will probably have to grab an IPV4 address to function and stay connected?... Although I believe devices will still connect to the WAP without the router running, so I was hoping it wouldn't require an IPV4 and somehow just pass traffic through the network...

If anyone else knows, thanks in advance!

I'd guess if it's a thread-connected device it will need to remain with the commissioning controller.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.