We recently purchased eight new honeycomb blinds with a motor, Eve Motionblinds CM-08-E, which all connect to HASS using Matter/Thread, without needing their bridge.
There are however two problems we’re experiencing:
Problem 1: Some of the devices occasionally become unavailable to HASS.
Yesterday, two of the eight blinds were unavailable. Now, they’re all there. Tomorrow, it might be two others that are unavailable. Practically. this means that when I run the script to open/close all the blinds at once, it’s a bit of Russian roulette to see which ones respond and don’t.
It’s unclear to me what causes the issue: HASS, the blind motors themselves, or perhaps the Thread network they’re connect through (Nest Wifi Pro). Rebooting HASS doesn’t make a difference. Even while a device is unavailable, pulling the manual cord on it will still make the blind go up or down as expected, so the motor isn’t ‘dead’. Given the proximity of all the devices to the nearest NWP, range isn’t an issue.
How would I start debugging this problem?
Problem 2: blinds never open/close all at once
When I run the script to close/open them all at once, there’s a huge variability in response time.
Sometimes, three blinds start closing at the same time, another one starts a second later, and the final few go even later (this is presuming they’re all online obviously). Another time, the combination is different, but they never respond at the same time.
In the script, I tried both putting all the commands after each other, and grouping them in a Parallel execution block, but both exhibit the same behavior.
Like in problem 1, I don’t know where to start finding the issue. Is there perhaps a known issue that HASS can’t send so many commands over Thread at once? Is there an issue with the Thread network itself? Or could it be an issue with the firmware in the motors?