C8 pro 2.5.1.152
I have my shades working but they only respond to open and close. Is there a way to make them stop at a given point? If I could just get them to stop at say 90% closed I would be happy with that. Any work arounds that people have done? I do want to stay with the built in driver.
I have done this, and as best I can remember, I did it as per below (there may be an old thread around here in which I explained it in more detail ...). I'm using the Bond Community integration for this but I don't think it matters.
In the Bond App, make a separate "device" that you want to pair with Hubitat for not fully open but not fully closed and give it a different name, such as appending the word "partial" on the end. This is just adding the rail you already added a 2nd time with a different name.
Bring that device into Hubitat via your Bond integration.
In rule machine, for your action,
For some reason it would not work unless I made it a totally separate "device" but it has been working fine for over 4 years now.
Before I switched my shades to Matter I had created a raise and lower option in the bond shade community driver. These commands would send the shade to the next setpoint on the shade. The old motors on my shades could use setpoints. So I created one setpoint on all my shades. If I used the raise or lower it would go to the next setpoint. I used virtual shades that when changed would activate the bond driver. It was a convoluted way to do it but it worked well once I go it all setup. I needed a RM rule that would look at the state of the virtual shade and send the appropriate command based on where it was currently and what position I had changed it to. If it sounds like something your interested in trying I can see if I still have the driver and a copy of the rule. But I think I deleted it all when I upgraded to matter.
In hubitat there is a 'stop position change' and a 'set position'. I don't get any change from either one of those settings. I'm not really sure what they are trying to do but they don't seem to do anything.
Is there a way to stop the motor in the standard app. I only see a closed and open. I don't see any way to stop it.
You use the set position, and in the next field, set the position using whole numbers. Start with 10, and increase by increments of 10 until you get what you want.
Are you trying to write an automation or are you trying to use dashboards to move the shades?
I'm using rules to test with. I run a rule with 50 in the set position and it doesn't seem to do anything.
It does nothing as in it does not move the shade at all, or it raises and lowers it completely??
If it does nothing, it is possible the signal is not reaching the Bond. I had this issue, so I now have it on repeat 6x. It works 99% of the time now. This is not a Hubitat issue and also not really a Bond issue; rather it is an issue of your shade's frequency being able to connect with the Bond Hub. Here is my rule:
If what you mean is that it completely raises and lowers instead of stopping partially, play around with the numbers. Try 10 and 90, 20 and 80, etc.
If you can get the stop position change to work, you could use a virtual shade device with the virtual shade driver to control it. That driver lets to set a transition time in preference. You time how long it takes to open/close, and use that number.
Make rules so that when the virtual shade windowShade attribute changes to "opening" it sends open to the actual shade. When the windowShade attribute changes to "partially open", have it stop the actual shade. Same with "closing" sends close, and it will stop when it gets "partially open".
When you press 70% in the virtual driver, it will change to "opening" which will trigger the shade to open. The virtual driver will change to partially open based on a % of the transition time to get there.
I'm not sure if you all understand that I'm using the built in driver. The errors show up in the log file showing that an invalid command was sent. I'm not wanting to use the community driver but I may have to.
