My Smartwings shades are no longer responding to "set position" commands from Hubitat recently. When type in a number (e.g. 80 from open at 100), the "Command submitted!" popup is shown, and the "windowShade" changes to "closing". But the shade does not physically change, and the "position" is still at 100. The "open", "close" and "start position change" commands work fine. This only happens to commands issued from Hubitat. When I set the shade position from Home App, it physically goes to the desired position. It also updates the "position" in the Hubitat. This only seems to happen recently (suspect to coincide after I updated the Hubitat platform version to 2.4.1.167; don't remember what previous version was). I've been using these Smartwings Matter shades for a year, and my WebCore automation works fine for "set position" every evening until recently. Tested the issue on 6 out of 8 of them, all have this problem. I believe it has to do with the Smartwings Matter Shade built-in driver after the platform update. I did another update today to 2.4.2.119 and it is still happening. Rebooting hub doesn't help. I tried searcging this community, but only found posts about Z-wave position issue. Has anyone else experienced this issue with Matter shades? Any advice appreciated.
After days of scratching my head and troubleshooting, it seems you already determined the source of the problem I'm having myself.
I have five EveMotion matter shades (and I'm utilizing the SmartWings Matter Shade driver) that were all operating perfectly, including some rules I have that determine if a window was open, which then only partially closes the shade ("set position" to 40). For about 10 days now one of my shades hasn't been operating at all when the daily auto-close rule kicks off. I thought perhaps there was an issue with that one shade. I even went through the headache of removing that shade from Hubitat and re-connecting it, and then fixing all my rules. But now realize the issue is with the Set Position command.
In fact, if I issue the Set Position command, either by the rule running or manually by clicking the "Set Position" button on the device screen, it stops all control of the shade at that point - including Open or Close - until I click the "Initialize" button, which seems to restore the connection. It seems like the Set Position command is clogging up the works with the shade making it useless.
Like you, when I go back to the primary Matter control system - in my case Amazon Echo - I can control the shade just fine in the Alexa app, including setting any position I choose. And now it's clear to me that the timing of my issues coincides with my last HE platform update so, I have to assume that was the culprit.
Hubitat support - can you please take a look at this?
Have you tried 2.4.2.134 (released today)? One of the bug fixes is:
- Fixed commandController issues with some setLevel, thermostat setpoint commands and setPosition for blinds/shades.
I have not - I haven't seen the normal Red alert at the top of the screen that there's an update waiting, but I will check now.
I just got through implementing a temporary klugey work-around by disabling the "Set Position" commands in my rules and instead using two separate commands... first "Close Shade" and then "Stop Shade" with a delay of xx seconds. Essentially achieves the same result but is hardly ideal.
I will check for the update, install if available and re-test with Set Position.
Thank you.
Well, I got pretty excited when I saw your message @hydro311 , and promptly installed the latest update. Unfortunately, now ALL my matter shades are completely unresponsive. I checked each one, and I can't even issue Open or Close commands. I checked the Matter section in Settings, and I saw little red X's next to all my devices. So, I thought for good measure I turn the Matter function off and then back on. That returned with checkmarks next to all my Matter devices, which made me think the problem was solved. However, still no joy. And now, looking at the Matter settings page again, I see red X's next to all five devices again.
It seems - and I sure hope I'm wrong - that this update that was allegedly supposed to fix Set Position, now broke everything for Matter devices.
Not happy anymore... 
An addendum...
After a few minutes of inactivity, all the red X's on the matter settings page change back to checkmarks which would suggest the connections are all restored. However, as soon as I attempt to control a single Matter device, the indicators all turn back to red Xs. Something definitely got hosed up with this update. I think I'll need to revert so I can at least get some control of my shades back.
OK, perhaps I should have been a bit more patient in terms of letting the Matter/Hubitat connection re-stabilize after the reboot. I do now again have control over my shades.
Unfortunately, zero change to the Set Position problem. It still doesn't work, and when I do use that command, it causes the shade to become unresponsive until I issue an "Initialize" command to clean out the cobwebs, or whatever is happening.
So, net-net, update didn't break anything, but it didn't fix anything either, at least not for Matter shades using the SmartWings Matter Shade driver.
I'll need to stick with my klugey delay-stop work-around for now.
Back over to you, Hubitat Support, please.
Sigh...
Does setPosition work from the driver directly?
And does it work if commandRetry is disabled?
@mike.maxwell - if what you mean by "work from the driver directly" is just clicking the "Set Position" button on the device screen, yes, I have been trying that. I'm not just seeing this behaviour in running the rule. And commandRetry is currently disabled (I've never touched that switch - it seems to be disabled by default for all of my shades).
So it works from the driver correctly?, or not....
Sorry @mike.maxwell , should have been more clear...NO, clicking the Set Position button in the driver / on the device page does not work. In fact, as mentioned earlier, it somehow mucks up the shade so it stops taking any commands at all, including Open or Close. The only way I can restore the shade's operation is to click "Initialize."
OK, I have one of these shades in the lab, and I have it charging up, will have a look into it.
Brilliant, thank you @mike.maxwell
