This one is a feature request by @Guy Lavoie to be able to move by percent for RTS shades.

Make sure you do a full open / close and time how long it takes then put that in the span for each shade. Right now the default is 8s but my Phantom outdoor blinds are a full 27s.

I also know on my Hunter Blinds I have one blind which is a laggard to the others all the time.

After that you can move by percent in the up or down direction.

Remember the Pending / Completed is much slower as that is a handshake with the Tahoma, not measuring when the stop signal is given.

Anyway, have fun and give some feedback!

## 0.0.27

- RTS Move By Percent: new MOVEPCT command (percent 1–99, direction Up/Open or Down/Close) sends open or close, waits (percent × total span) / 100 seconds, then sends stop; SETSPAN sets per-shade Total Span Move Time (GV1, default 8 s, persisted); Last Command Executed adds Move By Percent; RTS-only — io/Zigbee shades keep SETPOS

PS - This plugin modifies the profile, so if you are using Eisy-ui it can be harder to get it to read the profile update (the button to load profile doesn't seem to be making it happen; on the old Admin you just restart it. I am still figuring out the best way besides deleting the browser cache and restarting the service. Any ideas @bmercier or @Javi ?

I have had at least once where it blasted right by the percent I had tried to move to. Wondering if the stop signal didn't get through. Let me know if anyone else sees this the odd time, I could send it twice.

I must say I am enjoying this feature (use it to bring down the second shade and block morning sun)

Edited yesterday at 12:14 PM1 day by sjenkins

11 hours ago, sjenkins said:

This one is a feature request by @Guy Lavoie to be able to move by percent for RTS shades.

Make sure you do a full open / close and time how long it takes then put that in the span for each shade. Right now the default is 8s but my Phantom outdoor blinds are a full 27s.

I also know on my Hunter Blinds I have one blind which is a laggard to the others all the time.

After that you can move by percent in the up or down direction.

Remember the Pending / Completed is much slower as that is a handshake with the Tahoma, not measuring when the stop signal is given.

Anyway, have fun and give some feedback!

## 0.0.27

- RTS Move By Percent: new MOVEPCT command (percent 1–99, direction Up/Open or Down/Close) sends open or close, waits (percent × total span) / 100 seconds, then sends stop; SETSPAN sets per-shade Total Span Move Time (GV1, default 8 s, persisted); Last Command Executed adds Move By Percent; RTS-only — io/Zigbee shades keep SETPOS

PS - This plugin modifies the profile, so if you are using Eisy-ui it can be harder to get it to read the profile update (the button to load profile doesn't seem to be making it happen; on the old Admin you just restart it. I am still figuring out the best way besides deleting the browser cache and restarting the service. Any ideas @bmercier or @Javi ?

You should update the plugin to use dynamic profiles.

Ref: https://developer.isy.io/docs/API/pg/DynamicProfiles

4 minutes ago, bmercier said:

You should update the plugin to use dynamic profiles.

Ref: https://developer.isy.io/docs/API/pg/DynamicProfiles

ug.

6 minutes ago, bmercier said:

You should update the plugin to use dynamic profiles.

Ref: https://developer.isy.io/docs/API/pg/DynamicProfiles

11 hours ago, sjenkins said:

This one is a feature request by @Guy Lavoie to be able to move by percent for RTS shades.

Make sure you do a full open / close and time how long it takes then put that in the span for each shade. Right now the default is 8s but my Phantom outdoor blinds are a full 27s.

I also know on my Hunter Blinds I have one blind which is a laggard to the others all the time.

After that you can move by percent in the up or down direction.

Remember the Pending / Completed is much slower as that is a handshake with the Tahoma, not measuring when the stop signal is given.

Anyway, have fun and give some feedback!

## 0.0.27

- RTS Move By Percent: new MOVEPCT command (percent 1–99, direction Up/Open or Down/Close) sends open or close, waits (percent × total span) / 100 seconds, then sends stop; SETSPAN sets per-shade Total Span Move Time (GV1, default 8 s, persisted); Last Command Executed adds Move By Percent; RTS-only — io/Zigbee shades keep SETPOS

PS - This plugin modifies the profile, so if you are using Eisy-ui it can be harder to get it to read the profile update (the button to load profile doesn't seem to be making it happen; on the old Admin you just restart it. I am still figuring out the best way besides deleting the browser cache and restarting the service. Any ideas @bmercier or @Javi ?

Cool, and thanks! I'll get it updated later today. Looking forward to trying this!

2 hours ago, sjenkins said:

I have had at least once where it blasted right by the percent I had tried to move to. Wondering if the stop signal didn't get through. Let me know if anyone else sees this the odd time, I could send it twice.

I must say I am enjoying this feature (use it to bring down the second shade and block morning sun)

But sending the stop command twice might cause the shade to go to the preset "my" position if it receives both commands, since the stop command is dual function, depending on whether the shade is moving or not. I suggest we just observe things for a little while.

What does the ID reference, Is it necessary or could it be eliminated for a cleaner look?

In UD Mobile, under custom configurtion the value can only be set using the ID number rather than open or closed

4 minutes ago, Techman said:

What does the ID reference, Is it necessary or could it be eliminated for a cleaner look?

In UD Mobile, under custom configurtion the value can only be set using the ID number rather than open or closed

Purely a unique identifier given by the Tahoma app. Can be used to make sure you have the right device if a node name is changed independently of the unit. Its carryover from my HunterDouglas plugin where it was the only true way to know you were talking to the right shade.

Clean look?!? Are you truly an Eisy user? ;)

In UD Mobile I would like to set the icon, and icon color, depending whether the shade is opened or closed, but the value only references the ID number rather than the last command sent, i.e. open or closed. Is this a UD Mobile issue?

@Techman ,

It can be done:

You just need to make sure the object you are doing this with {default, command, etc} is chosen as a shade (not a scene).

Well no...what's needed is an icon color that morphs darker or lighter in realtime as the shade closes or opens! 🤣

Hmm, how do I upgrade from 0.0.24? I'm trying from the dashboard, from the non-production store. It tells me it's already installed in slot 8, which is correct. But when I click on Install, nothing happens. Tried this by accessing plugins from both admin console and eisy-ui.

In the production store an update is now available to .0.27

production is at v0.0.26

non-production(beta) is at v0.0.27

@Guy Lavoie there should be a button beside that slot 8 indicator to reinstall there. I just checked the repos & all look good.

1 hour ago, sjenkins said:

production is at v0.0.26

non-production(beta) is at v0.0.27

@Guy Lavoie there should be a button beside that slot 8 indicator to reinstall there. I just checked the repos & all look good.

Not sure where you're referencing that button. From the dashboard I see the plugin (in slot 8) with status = connected and store = beta. If I click on Details, I see the main screen for the plugin. If I click on Update, I see that I'm running 0.0.24. See the screen shot below. If I click on Update, nothing happens.

Edited 18 minutes ago18 min by Guy Lavoie