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.
Download the Hubitat app
