Time to move this one up to production; the RTS move by percent feature seems to be working well on my system and some others.

Let me know if you see anything.

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.

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.

Significant profile changes which can take some dancing to get eisy-ui to recognise, the admin just restart.

To bmerciers advice, I will take another look at dynamic profiles, but it is a whole new paradigm.

## 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

So I pushed the update to GitHub and the easy-ui plugin store, which should replicate to the PG3x store, but it may take a day. I am resisting the temptation to update in both stores (was told not to). So if you reinstall from the pg3x production store you will get the new version; the store just may not say it, but the plugin will.

I'm still running the non-production 0.0.27 and finally got around to trying out the shiny new percent feature. Seems to work great! I set the travel time values in a standalone program called "startup" that gets run on startup. I'm old enough to be trained on the good ole AUTOEXEC.BAT and CONFIG.SYS file days...

One thing that does happen when sending shade commands in UD Mobile is that I sometimes get the message below, but the command still works. Not sure what might cause that