Motionblinds CMD-01 extremely slow to respond

Configuration
1

I purchased a Motionblinds Wi-Fi Bridge CMD-01 and integrated it with HA.
All blinds are connected, used the native app to set top and bottom positions.

Everything looked fine… however, often the bridge is extremely slow to respond.

I do not have any conrete walls to worry about, wifi connectivity is excellent. I tried different positions, closer to the router, closer to the blinds, but often it takes 10-30 seconds before a command gets pushed through to the blinds.

And often nothing happens at all.

Motionblinds website provides no clue on how to solve it, I could not find any contact details and the motionblinds app does not provide any troubleshooting information either.

Anyone here experiencing these challenges?

2

If that’s cloud connected, your data passes out to another country and back. If this is Tuya based, all bets are off and you are lucky it works at all.

3

Is the bridge slow to respond when using the native app?

The MotionBlinds Integration is ‘Local Push’ and hence should respond quickly. It does use Multicast UDP when communicating with the Bridge and hence you should check you don’t have anything on your network interfering with that (ie. IGMP Snooping).

4

Yes it is slow in the native app as well.

I do have it in its own VLAN and I followed instructions to do the manual status query and set that to every 30 seconds. But delays are much longer than that at times. And sometimes, nothing happens at all.

The weirdest thing just happened this afternoon while testing.

action: motion_blinds.set_absolute_position
metadata: {}
data:
  absolute_position: 100
  width: 0
target:
  entity_id:
    - cover.topdownbottomup_0001_combined
    - cover.topdownbottomup_0002_combined
    - cover.topdownbottomup_0004_combined
    - cover.topdownbottomup_0005_combined

I fired off the event. Everything started moving.
Once they were all completely open, two blinds started moving the bottom bar down again… one went to about 30% and then moved up again. Did that twice…

The other one went down to like 80% and never went up again.

It is this kind of behavior that makes me scratch my head…

5

Hmm… there is also other stuff going on…
I have many of these messages, it seems that automation to trigger a refresh is no longer working. It used to work… but somehow does not seem to be able to find that entity any more… weird!

2025-10-23 17:17:00.478 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity cover.motion_shade not found.
2025-10-23 17:17:30.477 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity cover.motion_shade not found.
2025-10-23 17:18:00.478 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity cover.motion_shade not found.
2025-10-23 17:18:25.001 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity cover.motion_shade not found.
6

Ok that is user error… that was the entity from the example in the docs. While I added an actual entity through the UI in the automation, this one was still in the YAML and not visible in the UI…

Learning curve…