core: Meross Matter smart wifi plug fails to pair when added to home assistant directly, but works when credentials are shared from google home
The problem
Meross Matter wifi smart plug fails to pair when added to home assistant directly
What works instead:
- Use an android device
- adding to google home (the app)
- Google seems not to be able to manage the device (can’t turn it on/off, I don’t have a hub)
- sharing the credentials with home assistant
- The device works with home assistant
Note: I’m using a VLAN but both the plugs and HA are in the same VLAN, and I also have a mDNS reflector active. Pairing is done on the same vlan. Threads also works (I paired my other devices before the VLAN change in case it might be useful)
Devices works after this “strange” pairing, so I don’t believe my network configuration is wrong (otherwise they won’t work at all!)
Pairing with an iOS device fails completely (I don’t have any hub and I don’t know if that method of pairing is supported right now)
What version of Home Assistant Core has the issue?
core-2023.11.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Matter
Link to integration documentation on our website
https://www.home-assistant.io/integrations/matter/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
2023-11-22 15:45:57 core-matter-server PersistentStorage[126] INFO Committing...
2023-11-22 15:46:04 core-matter-server chip.DMG[126] ERROR Subscription Liveness timeout with SubscriptionID = 0x2957ef72, Peer = 01:0000000000000011
2023-11-22 15:46:04 core-matter-server matter_server.server.device_controller.[node 17][126] INFO Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2023-11-22 15:46:22 core-matter-server chip.EM[126] ERROR Failed to Send CHIP MessageCounter:135634974 on exchange 65047i sendCount: 4 max retries: 4
2023-11-22 15:46:25 core-matter-server chip.DMG[126] ERROR Time out! failed to receive report data from Exchange: 65047i
2023-11-22 15:46:25 core-matter-server matter_server.server.device_controller.[node 3][126] INFO Previous subscription failed with Error: 50, re-subscribing in 166748 ms...
2023-11-22 15:46:35 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-11-22 15:46:49 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[1:0000000000000011]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
2023-11-22 15:46:49 core-matter-server chip.DMG[126] ERROR Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout'
2023-11-22 15:46:49 core-matter-server matter_server.server.device_controller.[node 17][126] INFO Previous subscription failed with Error: 50, re-subscribing in 5192 ms...
2023-11-22 15:46:58 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from DCL.
2023-11-22 15:46:58 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 0 PAA root certificates from DCL.
2023-11-22 15:46:58 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from Git.
2023-11-22 15:46:58 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 0 PAA root certificates from Git.
2023-11-22 15:47:29 core-matter-server chip.CTL[126] ERROR Mdns discovery timed out
2023-11-22 15:47:29 core-matter-server matter_server.server.client_handler[126] ERROR [547590033936] Error handling message: CommandMessage(message_id='866fdcb7586b4c75afa82e94ad77af04', command='commission_on_network', args={'setup_pin_code': CENSOR})
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 188, in _run_handler
result = await result
^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py", line 221, in commission_on_network
raise NodeCommissionFailed(
matter_server.common.errors.NodeCommissionFailed: Commission on network failed for node 18
2023-11-22 15:47:29 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 7 months ago
- Comments: 18 (2 by maintainers)
I have taken the HACS integration route, and while I would rather keep it local this is working fine.
Thanks once more
If you have HACS you can use the cloud Meross via this https://github.com/albertogeniola/meross-homeassistant
It has also a link to the lan only version, which I’ve not tried yet
I’m starting to think these devices are just a bit flaky and Google works around it by just retrying and retrying and retrying numerous times until it succeeds. There’s not much we can do here. I’m not a fan of this keep-retrying just because we can approach. We already do a pretty large timeout and a couple of retries which is enough for all devices I’ve seen so far.
I’d suggest to just commission them to Google, share to HA and then remove from Google again (or not) if that works for you.
I actually should receive the Meross MS315 later this week. I’ll try to reproduce this scenario once I have it on my desk.
I run hassio on a mac as a virtual machine (bridged network).
I believe it is mostly a timeout issue, perhaps this specific model is slower than others to reply. I also noticed some messages similar to “device found but commissioning window is not open anymore” which seems to confirm a similar behavior.
My network is plain, without VLANs, mdns messages go through without problems (checked with wireshark), but Matter Server struggle to register these plugs. It’s not a consistent KO anyways: after a few resets eventually I managed to pair the devices (I also reinstalled the add-on, just in case).