New v3 Kit – Is the stupid get-after-set issue fixed? – General Troubleshooting – Community Forum

New v3 Kit - Is the...
 
Notifications
Clear all

[Solved] New v3 Kit - Is the stupid get-after-set issue fixed?  

  RSS
i
(@skwerl)
New Member

  I'm still struggling with getting my iBlinds to work well with OpenZWave.  The problem appears to be the thing where the controller immediately asks for the device's status after it has sent a set command.  The resulting behavior, which is ridiculous, is that when you ask the motor to open or close, it just keeps on going the direction it was asked to turn until it is 100% closed.

Will the new kits still require these config file hacks?

 

Thank you,

Josh

Posted : 06/09/2020 11:19 pm
Admin
(@eric)
Member Admin
Posted by: @skwerl

  I'm still struggling with getting my iBlinds to work well with OpenZWave.  The problem appears to be the thing where the controller immediately asks for the device's status after it has sent a set command.  The resulting behavior, which is ridiculous, is that when you ask the motor to open or close, it just keeps on going the direction it was asked to turn until it is 100% closed.

Will the new kits still require these config file hacks?

 

Thank you,

Josh

Hey Josh, 

I agree with the disabling the immediate GET after SET command can be cumbersome to figure out. 

So far our initial test results and our beta user test results are turning out good.  An immediate GET does not cause the iblinds v3 motor to have the "ridiculous" behavior.  The blind will continue to move to the requested level.   However, there is still the issue of when the GET is issued. The iblinds motor will always return its current position.  So, for example, if the blinds are moving from 50% to 0% and the GET command is received when the blind has only had time to tilt to 45%, iblinds will return 45%. 
 

What hub are you using?   

Also, if you are having trouble updating your config file for use with your iblinds v2 please contact us at support@myiblinds.com we might be able to assist.   

Posted : 07/09/2020 1:01 am
RMo
 RMo
(@rmo)
New Member

Thanks for this information! I'm not the original poster but noticed this same oddity on my Z-Wave controller and created a solution that works most of the time for me. What would be nice is if the unit simply reported back the current level/position on its own when it was done moving instead of needing a Get from the controller--that way we could eliminate the guessing with how much time the blinds are likely to take to move to a new position (which is my current method of handling this--I don't want to optimistically "pre-update" the current level in case the blinds are not responding; I want to know what it really is). Battery reports would be nice, too, but I see they can at least be configured to send a "low battery" report (which I don't think my hub has a good way of handling). Perhaps some of these are already addressed. I'm excited to see what the 700-series device can do regardless!

Posted : 16/09/2020 3:59 am
c
(@chance)
Member Admin

Answer: Yes!

Our Beta Testers have had success with the solution

We have been able to solve the issue of Get After Set, please see: http://communityarchive.myiblinds.com/community/postid/179/

 

Locking this thread so that discussion will be moved to previous post.

Posted : 14/10/2020 7:55 pm
Share: