#matter-archived

1 messages · Page 26 of 1

torpid sinew
#

arggh.... I thought i was using the 64bit arm version on my share-to HA instance, but am running the 32 bit HAOS version, its been awhile since i started this instance. I'll have to fix that. Thanks for the info!

sullen cove
#

Apparently it is 1.3

stiff rampartBOT
#

@broken ravine I converted your message into a file since it's above 15 lines :+1:

📎 message.txt
versed nymph
#

Hi @narrow dock, maybe its the right time to ask for it again. 😃

#matter-archived message

Another idea: Can you maybe translate the hex node id in the logs to a dec node id? 😃

narrow dock
versed nymph
cloud wraith
# stiff rampart <@401094214236110860> I converted your message into a file since it's above 15 l...

Matter is a communication protocol that works with different wireless transmission standards (WiFi or Thread).
Your lightbulbs are Matter devices running on WiFi. No additional hardware required.
I don't really think there's much difference in the featureset you get between the WiZ integration and the Matter implementation on WiZ lightbulbs. The Matter implementation does make it so that it is unnecessary to go through the WiZ mobile app to make them join your WiFi network
I have zero experience with Tuya products but the Home Assistant integration is cloud based and any Matter implementation would be entirely local.

broken ravine
cloud wraith
#

so here's the rub about Matter
there's still a lot of functionality that's not in the Matter spec and some vendors are nice and expose these features via a custom data cluster that HA can tap into
and some vendors are dicks and if there's any feature that's not included in the spec they tunnel you into their apps
so for example, Eve is pretty nice about this, energy monitoring on their smart plugs were available via a custom cluster before it was added to the spec in Matter 1.3
Tapo/Kasa has a bunch of shit that they want you to use their app for and in those circumstances I would look into their native HA integration

#

tl;dr
if there's a local-push, native Home Assistant integration, that's still probably the best choice to go with.

#

a lot of times you don't have that option or it's all cloud-push and in those instances Matter is a godsend

#

there are certain people in this server who say Matter is useless for Home Assistant users and to them I say this: because Apple is 100% onboard with Matter, and Apple drives decision making for millions of US consumers, there's a lot of vendors who would've otherwise never played ball that all of a sudden are now shipping robust local-control options for their home automation products

broken ravine
# cloud wraith so here's the rub about Matter there's still a lot of functionality that's not i...

That's been pretty much my experience. It is also changing rapidly. I have been in this ecosystem game for a while. I'm a hardware guy by trade though. I quickly saw solid reliability from the HA matter integration. Response times even seemed sharper. That is what really made me ask. For a light the HA Matter integration really has all the options today. I need a motion-or-presence sensor that will join via matter and stay off the cloud then I'm 100% local. So far they all want to go app to homekit to HA. That seems like a terrible idea.

cloud wraith
#

Apple's iron-willed refusal to budge on local control for HomeKit/Apple Home products is finally starting to change vendor behavior on this. you wait too long on this and it just looks weird to consumers that you're the only bulb on the shelf that doesn't have an Apple Home badge on it.
the roadblock is that home automation devices are kinda commodity hardware but also kinda not. a light bulb is just a light bulb... until you add in some novelty feature like audio reactive rgb strobing that is not part of "the platonic definition" of a light bulb.
I really hope the CSA has some plan to make custom clusters descriptive in some way so it's easier for Matter controllers to hook up to custom features. The way it's done now requires manual intervention from the controller to interpret values from the custom cluster a la ZHA "quirks" and ain't no one wanna do that work other than Home Assistant

broken ravine
cloud wraith
#

The CSA maintains a list of products that go through their Matter certification process https://csa-iot.org/csa-iot_products/
When I look at WiZ's support page about what devices do and don't support Matter...
I get why they haven't done anything with the remote and buttons.
They're both marketed as ways to use their products without a hub or phone. You'd think Matter Bindings would be perfect for these kinds of products but the reality is more than just about any other part of the spec, Binding is really immature. Not to mention, one of the big five controllers, Google Assistant DOESN'T SUPPORT MANAGING SMART BUTTONS AT ALL!!! No wonder the number of Matter smart buttons on the market can be counted on one hand. And until Google gets their shit together that's how it's gonna be.

#

as for the motion sensors...
well, this is my guess:

  • Matter over WiFi is not energy efficient and not suitable for battery powered devices
  • but Thread is an option!
  • ahhhhhhhhh there's a lot of consumers who have bought plenty of wifi devices but don't own a Thread-capable hub
  • have you noticed there's a dozen wifi matter bulbs and like two thread bulbs on the market?
  • motion sensors are not a plug and play product. you have to take the input from a sensor and write an automation around it
  • there's tons of consumers that don't use smart home platforms for anything more complicated than "i can turn off my light from my phone"
  • juice not worth the squeeze
broken ravine
cloud wraith
#

well, that would be any Matter/WiFi device. from there it's just whether or not some out of spec features are available via a custom cluster or not. hit or miss on that, i suppose.
https://csa-iot.org/csa-iot_products/
as linked before, this is the CSA's official certification list. you go into the drop downs and select Program Type > Matter.
But the CSA's official list doesn't differentiate between WiFi and Thread devices
matter-smarthome's list is a good supplement
https://matter-smarthome.de/en/overview-products-compatible-with-matter/
obviously not as comprehensive but they're pretty quick on the draw and they tell you whether or not a device is ethernet/wifi/thread

broken ravine
# cloud wraith well, that would be any Matter/WiFi device. from there it's just whether or not ...

Those lists seem to be 100% I'm a Matter device but you still need my hub and my app and likely HomeKit running for this device to join HA via Matter. This seems to be crux of my issue.

I have been through both list and as of today my efforts show - EVE motion - Aqara Motion - Wiz Motion All need app and HomeKit to join HA as a matter device. (Only Matter compatible if you have other requirements beyond wifi)

Some other no name motion devices will join HA via Tuya/Smarthome without native app but not directly via Matter.

I have yet to find a wifi Motion/Presense device that can join HA via Matter (Beta).

Matter compatible and compliant does not remove the requirements to have other apps and interfaces active on your network. This seems to be a language issue when we talk about devices. Yes if I had an Apple/Hue/Aqara/Thread and a zigbee hub/radio/controller - just about every device would join my network. Likely my connection chain would hit the cloud twice for function via HA.

#

Spelled all that out not as an argument but to make sure I'm experincing this as it is today.

cloud wraith
#

Ok it's unavoidable for products that were retrofitted into matter compliance via firmware update to require you to open up a vendor app to retrieve a pairing code but brand new devices should not need the intervention of another proprietary app to be commissioned into a matter controller

broken ravine
#

I get that, even the Wiz lights needed the update but then... they were discoverable by Matter.

cloud wraith
#

Honestly your bigger knockback is a battery powered device like a motion sensor running over wifi is a battery killer therefore you're not likely to find such a product out on the market

broken ravine
#

there are plug in sensors

cloud wraith
#

I mean i guess, but I still reckon it's hard to find those in a wifi package, you'd have better luck finding some using zigbee

broken ravine
#

I appreciate you taking the time to opine. I hope others found some answers here too. I will let you know when I find a senso that Matter (Beta) lets in...directly!!

narrow dock
versed nymph
narrow dock
#

@versed nymph we are tracking the state not updating issue here:
https://github.com/home-assistant/core/issues/124503

Somebody reports that reverting to an older (6.3.x) version of the Matter Server, fixed the issue. Don't know if you still have a backup that you could restore to check that ?

versed nymph
narrow moth
#

My Nanoleaf A19 has reset itself. I needed to pair it again using the Nanoleaf app. It joined the Thread network again, but it is still unavailable in HA. It has been a couple of days. I tried resetting HA. Tried disabling and enabling again the Matter integration. The light is still unavailable.

I remember something similar happened before, and I did something to fix it, but I don't remember what. I'm sure I did it without removing the device from HA. What else should I try?

unreal silo
#

if the bulb was fully reset, then it will have lost all of the encrypted connection setup, so it has to be recommissioned via the add Matter device flow to be able to talk to HA again.

#

… I'm not sure what happens if you do that without first removing the device?

cobalt zenith
#

Oh nice. They're already rolling out firmware 3.5.0 for Eve Themo which conforms to Matter 1.3

versed nymph
cobalt zenith
versed nymph
#

Shouldn’t we get an update via Home Assistants DCL integration?

cobalt zenith
#

We do

versed nymph
#

Ahhh, ok, I forgot that I downgraded my Matter server to 6.3.1 to test the Motter over Thread state issue… Good timing… 😃

cursive iris
#

i gotta say its really a relief that other people have this matter over thread device state issue

versed nymph
#

By the way… today I also see the 3.5.0 updates for my EVE Thermos. @thorn axle Is it save to update the devices via HA, when you have Matter server 6.3.1 in use? Thanks

versed nymph
#

I mean, a lot of changes regarding OTA were made with Matter >=6.4.0. However, I think I will wait until my next Matter server update. 😉

versed nymph
thorn axle
thorn axle
versed nymph
frigid basin
narrow dock
versed nymph
narrow dock
#

we have other priorities first before we can implement bindings - just know that its on the list

frigid basin
#

Wasn't meant to put you in a hurry, just wanted to pass the information from the eve employee forward to you - but I would assume you are already in contact with them 🙂

narrow dock
versed nymph
# thorn axle Yeah update is already present in that version, so you should be good to go.

I have updated my 9 EVE Thermos via Home Assistant. Fantastic! Well done @thorn axle and @narrow dock! 😃

Two of my EVE Thermos didn’t want to update. I noticed that the battery level was low at 20%. So I replaced the batteries with new ones and the updates went through.

Is there any check of the battery status before the update is triggered?

By the way… It was interesting to get a message from Apple Home after updating an EVE Thermo via Home Assistant:

https://imgur.com/a/FxPb04z

#

@thorn axle and @narrow dock

Another thing I've noticed recently. In my opinion, you've reached the point where Home Assistant's Matter implementation is better than Apple Home's. When my Thread network needs to re-mesh, it used to be that Home Assistant found all of my 60 Matter via Thread devices before Apple Home found the 37 devices that are also paired with Apple Home. WTF? 😂

edgy lily
edgy lily
versed nymph
edgy lily
versed nymph
#

Not possible to upload files here. I can try to share it with you via dm. I am at the phone at the moment.

edgy lily
#

I notice Eve Systems implemented the ThermostatUserInterfaceConfiguration
ClusterId 516 (0x00204) for this Eve Thermo device

versed nymph
versed nymph
rough niche
#

Now if their fp2 sensors would work.. 😭

broken ravine
#

Hoping someone can explain enough so I know I understand. lol

  1. Works With Home Assistant "Matter"!! Does that really mean HA can handle the onboard/binding part?

  2. For us Docker people will the matter-server always be external or will it crawl inside the HA docker soon??

Thanks.

crystal quartz
#
  1. It HAS to be external, since it's other software
unique path
#

Hi all, I am having some challenges with my matter devices. They are all Aqua devices (motion and light) plus also a door/window sensor. I've noticed over the last week or so - certain devices have fallen off the network, i've swapped with new batteries, just in case, but no difference. Log below, these devices worked perfectly for weeks, hence the confusion as to why they no longer are!

2024-09-04 19:08:27.502 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-09-04 19:08:27.503 (MainThread) DEBUG [matter_server.server.sdk] Node:16 Establishing CASE session took 45.4 seconds
2024-09-04 19:08:27.503 (MainThread) WARNING [matter_server.server.device_controller] Node:16 Setup for node failed: Unable to establish CASE session with Node 16
2024-09-04 19:08:27.509 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-09-04 19:08:27.509 (MainThread) DEBUG [matter_server.server.sdk] Node:37 Establishing CASE session took 45.4 seconds
2024-09-04 19:08:27.509 (MainThread) WARNING [matter_server.server.device_controller] Node:37 Setup for node failed: Unable to establish CASE session with Node 37
2024-09-04 19:08:27.537 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1

rich abyss
#

What's the difference between Works via Matter with HomeAssistant and normal Matter integration?

#

Is there some special feature?

thin nymph
#

It's the same. It just means that you can be sure that "Works via Matter with Home Assistant" devices actually work with Home Assistant and don't do any weird stuff.

broken sparrow
#

Yeah there are certain Matter devices that don't actually work. I know there is a Matter air purifier that you can't actually control even though you can add it.

#

Same goes for the 2 buttons on the Switchbot Hub 2. You can add it via Matter. But you can't do anything with them inside HA.

random lodge
#

What server hardware does the Sky Connect dongle work with? I plugged it into a RPI and it was found no problem. Tried it with x86 based HAOS and it doesn’t find it. Is there a trick to get it working on x86 hardware or is it not compatible?

blissful coral
#

The Aqara P2 contact sensor burned through batteries last time I checked, does the comparability certification fix that? 🤞

stray ice
#

No issue with sky connect on a haos VM here

#

Make sure you pass through appropriately

#

Has anyone tried sharing matter devices from ha to Google?

#

Right now I have everything passed through the old custom addon but some stuff is a little janky so I wouldn't mind doing it via matter

pale flax
#

Does it additionally cost to get the Work with HA certificate?

rugged tartan
#

Slightly tangental Matter question... is there a way to remove & re-add a device in HA without having to remove and re-provision in the Matter server?
I've an Eve smart plug which I want to take from where it is and use somewhere else, but I want to clear down the history and stats (so energy usage, etc gets reset) as it's going to be connected to something else.
I suspect I've going to have to remove and re-provision, but thought I'd just check first 🙂

winged oasis
#

@narrow dock My Thread/Matter network seem much more stable. now. Here's what I did (thanks to your suggestions):

  1. Removed multi-admin (Apple Home) from all devices and only have them admin'd by HA.
  2. Disabled WiFi channel 11, as that overlapped with Thread channel 25 on my ATVs.
  3. Upgraded to tvOS 18 beta 8 on both ATVs
  4. Running latest HAOS/Matter server
spiral pollen
#

But it's not just the 'cost', it's also that you make sure as a company that products will keep working

pale flax
#

Any idea how much this would be?

crystal quartz
sullen cove
short aspen
#

newb question here.

i just set up home assistant and i'm looking at the aqara P2 door sensor which says it supports matter. can i add that sensor to home assistant without any additional hubs/coordinators?

sullen cove
#

you will need a thread border router of some sort

lapis saddle
narrow dock
narrow dock
iron scroll
#

so....ipv6....I finally got my eve M-o-T plugs into HA, by putting HA and the apple router on the same VLAN and enabling ipv6

it always failed to commission when they were on different VLANs

I guess I'm sharing a finding, but I'm also curious if anyone has MoT working when HA and the Apple TBR are on different vlans?

cloud wraith
#

vlans and matter go together like ketchup and grape jelly

iron scroll
iron scroll
cloud wraith
#

ipv6 mdns repeaters are just shit

#

so general advice is if you're going to use vlans make sure all your matter stuff is in the same vlan

narrow dock
iron scroll
#

thank you both

broken ravine
# short aspen newb question here. i just set up home assistant and i'm looking at the aqara P...

Same struggle. You do need a Thread border router and the devices need to be in range for the aqara devices. I have a distance problem so I have no zgbee or other radios. Pure wifi no hubs/controllers.

Alternative is wifi only motion sensors that will join via Tuya integration. You set them up in smartlife or tuya app. Then load the Tuya integration into HA via Tuya security code. Current issue is the Tuya part relies on the cloud. Many tuya sensors $10-$30 that are reliable.

one of them- TREATLIFE WiFi Motion Sensor, 2.4GHz PIR Motion Sensor $30 (expensive because it is battery or cable)

Hoping to move to a cloud free solution, fingers crossed aqara or others eventually make a Matter sensor that will onboard/bind directly to HA Matter.

broken ravine
ember moon
#

Hello! I'm sorry if this has been asked before, but I'm confused with how Matter works or benefits us. I have some Matter lightbulbs. I can add them via Alexa but the bulb doesn't show up in Home Assistant as a device. If I add the bulb to Home Assistant instead of Alexa, she can't control the light bulb. So I am confused. Can someone explain to me why Matter is a good thing and how I should be utilizing it please?

broken ravine
unreal silo
#

one interesting thing about matter is that matter devices are required to support being controlled by multiple platforms - you can add the bulb to both home assistant and alexa. (you add it to one, then share it to the other)

broken ravine
unreal silo
#

well, in this case, those "something else on the network" would be home assistant and some amazon device, like an echo or similar.

ember moon
# broken ravine Just to keep it relevant to your situation- What bulb?? How did you add it HA? ...

The bulbs I bought were off Amazon. "Energetic Lighting" on the box, but the sticker on the back says Yankon Lighting Inc. "Matter Smart Bulb A19".

As for the integration, I didn't understand which one to install, so I installed 3. I installed the two add-ons; Matterbridge, and Matter Server. I also installed Matter (Beta) in hacs.

After adding the bulb to Alexa, I figured out that I can share the bulb, got the share code, and then went into Matter Server and clicked on Commission Node. And then entered the share code when it prompted me for it.

broken ravine
ember moon
#

I dont see anywhere in Beta to add a new device.

broken ravine
broken ravine
ember moon
#

I have 1 bulb already connected through Beta, but Alexa can't control it, so with my second bulb, I added it to Alexa instead and found that HA can't control it automatically, but then saw you could share the bulbwith HA. So this whole thing is confusing to me. I'm sorry if I'm doing it wrong

unreal silo
#

from home assistant, you can also share the bulb to alexa

ember moon
unreal silo
#

if this is HAOS, no configuration is needed, the matter integration will automatically use the matter server addon

broken ravine
#

replace "localhost" with your matter server ip if your getting an error your HA is not seeing the matter server

I'm in Docker so this is a little different.

ember moon
#

I did change the localhost to my IP. ws://10.0.0.105:5580/ws and then it says: "Failed to connect"

ember moon
#

I also just realized, I didn't read your message in detail enough. To add a device, I have to go to the device tab and then click "add matter device"

broken ravine
unreal silo
#

note that if the device is fresh out of the box, or reset (not yet on wifi), then you will have to add it using the home assistant mobile app, which will connect to the bulb via bluetooth and configure it to join the wifi before adding it to home assistant.

#

when sharing a device from alexa to home assistant, you can use the web ui

broken ravine
ember moon
#

Okay! Got the one from Alexa connected to HA!

#

I think I got it now!

broken ravine
ember moon
#

For the server, I had to check the box that said something about auto using the built in server instead of unchecking that box and typing in my IP for the matter server. So Supervised must be the same as HAOS when setting up the server.

unreal silo
#

yeah, supervised lets you use addons similarly to HAOS, iirc.

#

(tho note that you won't get a lot of support for using supervised; people normally recommend either managing docker yourself or going all the way to haos)

ember moon
unreal silo
#

keep in mind that with this setup, there's no communication between alexa and home assistant. instead, both platforms are directly talking to the bulb.

#

so they can operate independently, but they will also stay in sync because if one platform changes something, the bulb notifies all platforms that it changed.

ember moon
# unreal silo yeah, supervised lets you use addons similarly to HAOS, iirc.

Yeah, I was told that last week. Here's the thing ... I had Home Assistant setup on Debian, installed it via docker, but somehow also installed the Supervisor image as well, and everything was working fine! Has been for a couple years now. But last week my machine fan was turning on and getting really loud for long periods of time, so I was inquiring on how I could find out what process or integration was causing it. That's when the person helping me, pointed out that my setup was wrong. I tried installing Hass again using docker-compose but realized I wouldn't have access to addons. I need access to addons for a few of them I use. So my only option was to do Supervised. (I don't want to do HAOS. My friend is using that and he runs into problems all the time - whereas I don't, so I'm confortable using Hass the way I currently do)

ember moon
unreal silo
#

yeah, i personally use HAOS in a VM (with usb passthrough for my zigbee and bluetooth adapters), and it's been completely hassle-free for me.

#

if you end up getting into Thread devices, you will find that getting the required network configuration working will be easier with HAOS :/

ember moon
#

With HAOS, I feel blind on how to run commands in the command prompt. At least with Debian, there's TONs of forums with people posting how to fix things. At least that's how I feel about using both. I feel like my hands are tied with HAOS

unreal silo
#

yeah, if you ever have to actually run a cli command on haos then something must have gone seriously wrong. it's an appliance os, not something you use as a general purpose linux that also runs other stuff.

#

(which is why addons exist in the first place; there's nothing stopping you from running anything available in an addon in a normal docker container without using haos/supervised)

ember moon
#

Except if you don't do it right, you get that message saying your system is unhealthy

unreal silo
#

a minor note is that apparently quite a few of the cheaper wifi matter bulbs like this have buggy transitions - if you find the bulbs fade on/off really slowly when controlled from home assistant, then it would be good if you can provide some diagnostic information so the default transition can be blocked on them.

ember moon
#

Okay, I can do that! Right now I am having a problem adding the second bulb via sharing from Alexa. Hass keeps failing. After a few attempts, I cancelled in the Alexa App and when I went to try once again, it said the bulb was connected to Hass even though it failed in Hass. So I removed it and am trying again.

#

Like right now, it says it's connected to Hass, but yet Hass is saying "Search for the sharing mode in the app of your controller, and active it. You will get a sharing code, enter that below. <Setup code> ... ADD DEVICE

#

I exit out of that prompt in Hass, and go back to the Integrations tab, and see Matter (Beta) - 2 Devices. I open that up and sure enough, it IS connected.

unreal silo
#

huh. that's kind of weird. sounds like the matter integration/web ui might have gotten out of sync with the matter server somehow

ember moon
#

Ya, like Alexa App got the ack back that it connected, but Hass setup couldn't see it connected afterall.

ember moon
hollow barn
#

I’m having an issue with my Nanoleaf Essentials Light Bulbs (Matter). The brightness slider is acting weird—it keeps jumping back and forth whenever I try to adjust the light level.

spiral jackal
#

Hi! Could anybody help me out with a python-matter-server setup?
In general the server is up and running and connected to HA. I can easly add an Aqara M3 Hub but can't add a Matter over Thread device. I'm getting a "Network is unreachable" in the matter server logs so I assume it maybe could have to do something with my ipv6 setup? But I'm unsure and have no idea, how I can find the problem. Pls help!

narrow dock
spiral jackal
sullen cove
spiral jackal
broken ravine
spiral jackal
broken ravine
rugged tartan
# spiral jackal Yes. It maches my Setup. And at this moment I bought another Matter device and ...

IIRC as Thread is IPv6 native, the TBRs announce the Thread IPv6 range via IPv6 RAs, which are picked up by whichever device needs to talk to the Thread device and used as the next hop route for the Thread network.
I would guess (?) the Matter Server isn't getting those route advertisments to know how to route to the Thread IPv6 network, or your containers are on Docker provided IPs and so don't have routed IPv6 connectivity at the container level. 🤷‍♂️
You may need to check that your containers are on native IPv6 and are getting those TBR RAs and applying them. This is one of the reasone HAOS is stated as preferred as it's got all these tweaks and fixes added and enabled from day 1 🙂

spiral jackal
# rugged tartan IIRC as Thread is IPv6 native, the TBRs announce the Thread IPv6 range via IPv6 ...

Thank you, this are good hints and sounds plausible! I only have a very basic knowledge about IPv6 so I currently have no idea how to check it or how to configure it. So I just have to get more into it.
But if you have any hint, how I can check it, it would be very appreciated!
And yes, HAOS would be a way more easy solution - if there would be a powerful and reliable device which is supported by HAOS, I would buy it immediately. That was the reason why I moved from RasPi to another System with Docker.

rugged tartan
# spiral jackal Thank you, this are good hints and sounds plausible! I only have a very basic kn...

Re IPv6, you basically need IPv6 capability on every component which needs to talk to the Thread device, that doesn't mean you need to allocate an IPv6 subnet or anything like that, but everything must be able to talk IPv6 to everything else (and receive those RAs from the TBRs).
Re HAOS, you can install HAOS on any modern x86-64 PC - https://www.home-assistant.io/installation/generic-x86-64 - so the sky is pretty much the limit in terms of what you use, whether it's a 3nd use PC, or pick up something like an N100 mini PC 🙂

narrow dock
#

Yeah, I run HAOS on a small NUC (installed directly on the SSD) with 16GB memory and it works amazing - there a few good addon repositories so you really can find an addon for everything you may need. Plug and play, more time for me to write code 😉

spiral jackal
humble kettle
#

Hi, I just added a iqore smart plug (powered by Tuya) with energy monitor to HA. Iit is added as a Matter device, and it's showing voltage, current and power, but no energy. In the tuya app it does show energy. Is this a matter-integration-issue?

sullen cove
remote sail
#

Hello, I hope you're well! I'm soliciting you because I received a matter light bulb but when I want to connect it via the HA application it blocks me at network connectivity check, strange knowing that 1 week ago I've already connected other matter devices.

sullen cove
#

Are both bulbs matter over wifi? Or matter over thread?

remote sail
#

@sullen cove

#

So after restarting HA I now get to the Home Assistant device connection stage, then I get the message Unable to locate device.

broken ravine
remote sail
#

I plug in the bulb and put it in pairing mode by turning it on and off, then once it's flashing I go to HA and go to settings, integrations then add an integration, then Add a Matter device and there I scan the QR code or type in the code shown on the bulb and then the pairing between the bulb and HA starts and I lock on Home Assistant device connection stage. @broken ravine

broken ravine
remote sail
broken ravine
remote sail
#

Ah, it's true that I've never tried to connect a device via its application and then add it to HA, so what you're suggesting is that I install the "Nous" application, configure it in the app and then add it with matter?

remote sail
broken ravine
remote sail
#

I've restarted HA at least 4 or 5 times but it's still stuck on adding to HA. If you want, I can send you a video.

#

Whaaaaatttt making the video to send it to you worked

#

In the end, it took 6 reboots to make it work.

broken ravine
remote sail
copper maple
#

Is there any official person from Jiecang Motor here? Please DM me (I will give you feedback on many bugs of your Matter over Thread motor)

#

HooRii Technology, a Chinese （Matter over Thread）solution provider, why is your Matter over Thread motor solution so bad? Considering that HooRii often appears in the Thread Group & CSA Alliance joint commissioning, why do you keep making garbage solutions again and again without considering finding a way to fix it? It's really puzzling (angry)

kind wing
#

So fairly new to home assistant and brand new to matter devices. I have a yoolax blind that I connected over matter with zero issues, it lost connection one day and without knowing what to do I just reset everything. I held the button on the shade to do a factory reset, reprogrammed the remote and the blind works just fine via remote. I also reset the border router which unknown to me at the time changed the network, not a big deal since at the time the blind was my only matter device. The problem comes in when I try to repair the shade to home assistant through the app, I get an error that says it can not connect to thread network and names the old network not the new one. I have reset the motor multiple times with no success. I have since then added multiple diffrent light bulbs via matter with no issues but for some reason the blind just will not join the new network...... Ive tried searching and searching and keep coming up with things that don't work.... any help would be fantastic.

edgy lily
humble kettle
sullen cove
humble kettle
#

It's a standard entity, maybe I will report it as a bug.

warm egret
#

I have been trying to set up a Nuki with Matter and Thread for weeks without any luck. Now I am trying to do it with Matter and Tasmota via WiFi, but I can't do it either. Can anyone help? Thanks.

#

2024-09-08 17:23:34.872 (Dummy-2) CHIP_PROGRESS [chip.native.EM] Retransmitting MessageCounter:246611102 on exchange 25174i with Node: <0000000000000000, 0> Send Cnt 4 2024-09-08 17:23:36.448 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:246611102 on exchange 25174i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4 2024-09-08 17:23:38.973 (Dummy-2) CHIP_ERROR [chip.native.SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33 2024-09-08 17:23:38.973 (Dummy-2) CHIP_DETAIL [chip.native.IN] SecureSession[0x7fa28c001ff0]: Released - Type:1 LSID:61643 2024-09-08 17:23:38.973 (Dummy-2) CHIP_ERROR [chip.native.ZCL] Secure Pairing Failed 2024-09-08 17:23:38.973 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to establish secure session to device: src/controller/python/ChipDeviceController-ScriptDevicePairingDelegate.cpp:89: CHIP Error 0x00000003: Incorrect state 2024-09-08 17:23:38.974 (MainThread) ERROR [matter_server.server.client_handler] [140336453499024] Error while handling: commission_on_network: Commissioning failed for node 4.

cursive night
#

I hope some one can help me 1 have 10 smartplugs from Iqore conected via matter only have problems using them thare are 4 sensors ? showing

Energie 0,0000kwh
Spanning 230V
Stroom 1.956mA
Vermogen 400,90W

the problem is Vermogen 400,90W is show my kwh usage and Energie 0,0000kwh stays on 0
the energy dasbord show them when i try to add them and the energy dasbord uses Energie 0,0000kwh so how can i correct this ?

cursive night
#

Apparaat info
Smart Plug
door Realwe Innovation
Firmware: 1.2.6
Hardware: 1.0

humble portal
#

i dont know why but i test aqara m2 hub and no power info in HA

dull zealot
sullen cove
broken sparrow
#

Well their devices support Matter now so I think they just want to promote the fact that it works with HA now.

dull zealot
#

I was more wondering about the plain Logo, instead of the "works with HA" one.

thorn axle
#

I have a Aqara Motion and Light sensor P2 which reports a phantom movement exactly every 1h 58min 🙈 I bought multiple, it is only one device. Anyone else seen that? 😅

#

Factory reset and onboarding to a different Thread network didn't help. I guess I need to RMA it 🤷‍♂️

#

Same firmware too (1.0.2.0).

worthy nexus
worthy nexus
#

Do I need to remove Eve Weather and re-commission it with HA to use added cluster? altitude and pressure @thorn axle

narrow dock
dusk saffron
#

Anyone tried to convert their Wiz Lights to matter? i tried doing this last week, but it was kinda of strange. I was able to add to matter, but it was still working in the normal Wiz integration. Another strange thing about it, when using the Wiz App to enable matter, its not like a software/firmware update was applied to the bulb, it was simply here's the sharing code. So, I just left them as Wifi.

cursive night
near lodge
#

I have HA running, ipv6 available, aqara D200 lock that connected to aqara application and M3 Hub in aqara application that the D200 lock is a child device.

I really want the lock inside HA, but when I add the M3 hub to HA using matter pairing code, I dont see any entity or device of the child devices of the hub, although the hub is full connected, any ideas?

versed nymph
cloud wraith
dusk saffron
broken ravine
#

My older bulbs were listed under more options via new device in the add device scan screen.

cloud wraith
dusk saffron
dusk saffron
cloud wraith
#

honestly if a device does deliberately disable its proprietary communication when matter is enabled, i figure it's because their SOC cannot handle both at the same time. otherwise, no reason for the vendor to turn it off

dusk saffron
#

makes sense

broken ravine
broken ravine
near lodge
dusk saffron
#

i only had colour choices

humble portal
broken ravine
#

I’m running HA in Docker with Matter-Server in Docker as well. Both just found an update today.

wicked nebula
#

Anybody know what might cause failures when adding matter device immediately after successful previous adds?

Was doing matter over thread bulbs (Nanoleaf essentials) today and the first 2 of them connected fine, 3rd one is giving me recurring fails with logs that look like it's just not resolving the address and timing out but nothing's changed in my config, and they're all updated to the firmware that makes them play happy with thread (3.6.196).

# 
2024-09-11 19:21:56.014 (Dummy-2) CHIP_ERROR [chip.native.CTL] Found unconnected device, removing
2024-09-11 19:21:56.783 (Dummy-2) INFO [chip.ChipDeviceCtrl] Established secure session with Device
2024-09-11 19:22:28.911 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2024-09-11 19:22:42.888 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:000000000000000F]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
2024-09-11 19:22:42.893 (Dummy-2) CHIP_ERROR [chip.native.CTL] Session establishment failed for <000000000000000F, 1>, error: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout.  Next retry expected to get a response to Sigma1 or fail within 60 seconds
...
2024-09-11 19:24:12.914 (Dummy-2) CHIP_ERROR [chip.native.CTL] Error on commissioning step 'kFindOperationalForStayActive': 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout'
2024-09-11 19:24:12.914 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to commission: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
2024-09-11 19:24:12.915 (MainThread) ERROR [matter_server.server.client_handler] [140121096050960] Error while handling: commission_with_code: Commission with code failed for node 15.```
wicked nebula
#

Well, whatever caused it, I was able to resolve it by doing a factory reset on the bulb 🤷

narrow dock
broken ravine
# narrow dock You are not going to find and any time soon. WiFi is not suitable for battery po...

I get what you’re saying.
I already own several wifi sensors that are battery only. A few are either cable or battery. We are 9 months into it and even my main hallway hasn’t needed a battery. The problem isn’t just matter it’s that all of the wifi sensors I found are tuya and are cloud based. Redoing my whole home in thread routers would be expensive and a waste really. I already have a very reliable system. I just want a sensor that gets off the cloud.

narrow dock
broken ravine
narrow dock
#

Yeah, like I said, you will have to wait but there are no signs of any Matter WiFi sensors. Maybe Tuya is going to produce them but all other companies are betting on Thread or stay with Zigbee.

sullen cove
#

I mean, you might be able to find some stuff off of AliExpress/Alibaba, but no guarantee how well they will go, or if you are going to get any support for them

worthy nexus
worthy nexus
unreal silo
sand mango
#

Does anyone know if the Onvis matter plugs support power consumption reporting like the Eve plugs do?

broken ravine
rugged tartan
sand mango
#

Yes, the S4 ones

#

Thanks!

thorn axle
#

There is a new Matter Server version 6.5.1. Mostly cleanup and some update improvements/fix. We've hold back the add-on update, but if you have the beta flag you'll get it already now on restart. 🎉

edgy lily
#

Soon it will be possible to see/change more attributes for Eve devices.

broken sparrow
#

You have a sensor for times opened? That's pretty cool.

broken ravine
worthy nexus
broken ravine
worthy nexus
#

The occupation state is barely accurate and so are temperature readings

#

It’s a nightmare using it to automate lights

broken sparrow
worthy nexus
broken ravine
cloud wraith
#

yeah. all matter devices require hubs

#

but it's wifi, not thread. note the compatibility chart lists a Nest Mini which does not have a Thread Border Router

broken sparrow
#

So it could be a Nest mini like yahooney just mentioned or HAOS.

broken ravine
#

Confused as hub/controller/commissioning requirements are 3 different things.
But all we need to know is if it will commission directly into HA matter integration.

edgy lily
broken sparrow
#

Yeah I think it adds to the confusion just because they want to avoid calling it a hub.

#

So many wifi devices use "no hub required" as a selling point.

#

So some say the same thing about Matter devices although that's misleading since it requires something

broken ravine
edgy lily
fast rune
#

Is there a way server-side to see which matter protocol version a given device is using?

Asking because I have a couple TPLink KP125M Matter smart plugs.
They've gotten firmware update recently but I'm not sure if it included matter 1.3.
It did advertise power consumption statistics are available in the Kasa app now, which leads me to believe so.

Would HASS automatically detect a new sensor for power consumption if I already have the device added via matter?

sullen cove
unreal silo
#

if the matter integration adds support for a custom cluster, or the device gets a firmware upgrade that adds a new standard cluster, it should update and show new entities in home assistant automatically.

edgy lily
winged oasis
narrow dock
# winged oasis Here are some tips on how to optimize your Matter over Thread network (thanks <@...

Nice article again and good to hear that its working stable now for you. Now lets hope there comes a time where it just always works and no reboot or whatosever is needed.
A few comments;

  • OTA in HA using apple BR's is currently not possible.
  • The multi-admin traffic painpoint is high on the list within CSA and there are multiple solutions being discussed, including the offloading the traffic onto a central role in the network that can act as a proxy/bridge for multiple matter fabics towards the (thread devices)
winged oasis
narrow dock
winged oasis
narrow dock
winged oasis