I tried live logging during the event but nothing registered in the log.
So you would have to get in touch with ST to see if they can see anything on their end. Also can you try controlling it manually through the app/voice. We know it’s not an issue with the motor so we are trying to find out what ST is doing differently now. Also which DH are you using?
No response from app either. What is DH?
DH = Device handler.
Also I mean rather than using routines for a few days can you try just controlling from your app to see if it gets stuck as well?
DH is a generic dimmer switch.
I can try using the app.
On a side note, I have 2 busted motors on 2 blinds that are being replaced
by spring. Out of 6.
What happened to the motors? Also roller shades?
One died. The second one gets stuck every other time and blind doesn’t
move. I had a lot of pairing issues also (couple of them lost pairing and
couldn’t get them back until I moved them 2 feet from the hub).
These are the graber layered zebra shades.
Hello,
I’m having the same issue with my smartthings sometimes failing to move my blinds more than a few inches and then the red light turning on, I have two blinds that both have the issue (one more than the other)
would additional logs help diagnose the issue?
The motor just dieing on you is very rare.
For pairing issues once paired always run a z-wave repair to make sure it’s connected through the strongest repeater. It shouldn’t drop once paired.
Any and all logs will help. Once again since this is an issue that’s only on SmartThings if we can figure out what’s going on we might be able to make tweaks to the DH so it works better.
As mentioned earlier, it’s something that’s started after a few of the recent firmware updates.
here’s some logs, i just tried to move both my blinds one at a time, blind 2 successfully moved, blind 1 did not
Blockquote
e2468f3c-7435-496d-92da-d5675e43f3e0 4:42:48 PM: debug getChildDevices(false), children=1
e2468f3c-7435-496d-92da-d5675e43f3e0 4:42:48 PM: info Shady – v1.0.2 – Blind 2 is at 71%.
e2468f3c-7435-496d-92da-d5675e43f3e0 4:42:48 PM: info Shady – v1.0.2 – Blind 1 is at 90%.
e2468f3c-7435-496d-92da-d5675e43f3e0 4:42:48 PM: info Shady – v1.0.2 – Running Asynchronous Refresh.
e2468f3c-7435-496d-92da-d5675e43f3e0 4:42:48 PM: info Shady – v1.0.2 – Blind 2 is at 71%.
e2468f3c-7435-496d-92da-d5675e43f3e0 4:42:48 PM: info Shady – v1.0.2 – Blind 1 is at 90%.
e2468f3c-7435-496d-92da-d5675e43f3e0 4:42:17 PM: info Shady – v1.0.2 – Shades are moving.
ebf85f30-ce2d-4829-9560-8dcd401f246f 4:42:17 PM: info Z-Wave Shade – v1.0.2 – Shade has stopped.
e2468f3c-7435-496d-92da-d5675e43f3e0 4:42:13 PM: info Shady – v1.0.2 – Shades are moving.
ebf85f30-ce2d-4829-9560-8dcd401f246f 4:42:13 PM: info Z-Wave Shade – v1.0.2 – Shade is moving.
e2468f3c-7435-496d-92da-d5675e43f3e0 4:42:08 PM: info Shady – v1.0.2 – Shades are moving.
a6148734-8e6a-4d86-8497-89729045abc0 4:42:08 PM: debug Outgoing: [requestId:4417773631854408511, payload:[commands:[[ids:[ebf85f30-ce2d-4829-9560-8dcd401f246f], status:PENDING]]]]
a6148734-8e6a-4d86-8497-89729045abc0 4:42:08 PM: debug Set Blind 2 to 70
a6148734-8e6a-4d86-8497-89729045abc0 4:42:08 PM: debug handleExecute()
ba03cf3b-d053-4c5d-850d-018c7becfd5c 4:41:58 PM: info Z-Wave Shade – v1.0.2 – Shade has stopped.
ba03cf3b-d053-4c5d-850d-018c7becfd5c 4:41:58 PM: info Z-Wave Shade – v1.0.2 – Shade has stopped.
ba03cf3b-d053-4c5d-850d-018c7becfd5c 4:41:57 PM: info Z-Wave Shade – v1.0.2 – Shade is moving.
e2468f3c-7435-496d-92da-d5675e43f3e0 4:41:57 PM: info Shady – v1.0.2 – Shades are moving.
e2468f3c-7435-496d-92da-d5675e43f3e0 4:41:57 PM: info Shady – v1.0.2 – Shades are moving.
ba03cf3b-d053-4c5d-850d-018c7becfd5c 4:41:57 PM: info Z-Wave Shade – v1.0.2 – Shade is moving.
e2468f3c-7435-496d-92da-d5675e43f3e0 4:41:52 PM: info Shady – v1.0.2 – Shades are moving.
a6148734-8e6a-4d86-8497-89729045abc0 4:41:52 PM: debug Outgoing: [requestId:15621690612735591389, payload:[commands:[[ids:[ba03cf3b-d053-4c5d-850d-018c7becfd5c], status:PENDING]]]]
a6148734-8e6a-4d86-8497-89729045abc0 4:41:52 PM: debug Set Blind 1 to 70
a6148734-8e6a-4d86-8497-89729045abc0 4:41:52 PM: debug handleExecute()
Blockquote
1 Like
Would you be able to pm me the logs as text files? Also can you capture them a few times over the next few days and send them over?
Also if you can send me the logs of the devices themselves as well. This seems to be from the shady app. Also if you are using the DH on the first post, put log level to trace.
Tried the repair with no luck. Had to unmount, take it physically near the
hub to repair which was a real pain.
I have some additional info to add (note @ZebraBlinds, I’d put in a call to Graber tech support but got tired of waiting 
so am still having blinds sync issues)… All of my blinds are using the Z-Wave Generic Switch DTH. I was having waay too many problems with the Generic Dimmer Switch DTH.
-
One of my five blinds isn’t responding at all to open/close commands directly from the ST app/associated remote. Logs from that:
6:38:02 AM: debug Shade master unhandled CentralSceneNotification(keyAttributes: 1, reserved11: 0, sceneNumber: 2, sequenceNumber: 93)
6:37:52 AM: debug Shade master unhandled CentralSceneNotification(keyAttributes: 2, reserved11: 0, sceneNumber: 2, sequenceNumber: 92)
6:37:52 AM: debug Shade master unhandled CentralSceneNotification(keyAttributes: 2, reserved11: 0, sceneNumber: 2, sequenceNumber: 92) -
A third blind that was open eventually responded to a “close” command did show on in the logs, but via a “Shade Master” Device (it’s not one of mine; maybe a Graber/Somfy thing?) Here’s that one line of log:
6:06:27 AM: debug Shade master unhandled CentralSceneNotification(keyAttributes: 0, reserved11: 0, sceneNumber: 2, sequenceNumber: 91)
We will be getting 8 Bali roller shades with centralized power. There is a power distribution solution that is offered by Bali. What power supply are they using? A MeanWell DRP-120-12 or maybe more likely a MeanWell SDR-120-12 as it allows +50% peak?
Not sure on the exact model but I do know that if the unit isn’t purchased through SWF and tied to the order they can void warranty on your motors.
Hmm, I seem to be affected by the bug people have been reporting. When trying to control one of my shades with ST, rather than changing to the level that the hub calls for, the shade moves about 10% and then stops. Here’s a log from just now. The shade should have adjusted to 90% but it stopped short of that.
6cf3b44d-9cc2-449e-b5fd-14c1546abe3e 7:47:07 AM: debug Parse returned [Living Room Shade 1 switch is on, Living Room Shade 1 level is 70%]
6cf3b44d-9cc2-449e-b5fd-14c1546abe3e 7:47:07 AM: debug parse() >> zwave.parse(zw device: 40, command: 2603, payload: 46 46 00 )
6cf3b44d-9cc2-449e-b5fd-14c1546abe3e 7:47:04 AM: debug Parse returned [Living Room Shade 1 switch is on, Living Room Shade 1 level is 66%]
6cf3b44d-9cc2-449e-b5fd-14c1546abe3e 7:47:04 AM: debug parse() >> zwave.parse(zw device: 40, command: 2603, payload: 42 FE FE )
6cf3b44d-9cc2-449e-b5fd-14c1546abe3e 7:46:59 AM: debug setLevel >> value: 90.0
2 Likes
don’t think I’m able to send PM’s
here’s a spread sheet with my logs for the last few days
hope this helps
1 Like
Ignore me, it was a set of batteries that needed changing 
.
1 Like
I received 5 sets of Zebra blinds around 2 weeks ago. They are having the weird issue where they move maybe 10% and stop. They are almost unusable. Had better luck with the generic switch DH, but still lots of failures to open or close all the way. I got so frustrated with it that today I moved them over to Hubitat, and using their generic zwave dimmer I can verify the same behavior exists. Looks like this isn’t purely a SmartThings issue. Mine have the duel battery trays, and am using new Energizer advanced lithium batteries that I purchased 3 weeks ago.