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

My dashboard shows .0.27 Beta, how do I change that to production. There's not a option to update

Just go to the production store and install into the slot the beta is in.

The dashboard showed an update, after the update it's still showing as beta. If I go to the poduction store it won't let me install it in the same slot

In pg3x when you update beta it will replace with an updated beta, but you are supposed to be able to put the same production on beta or beta on production from the store. Not sure what is wrong here as I have been doing that for a month with these.

The other way to do it is delete the beta and install the production on that slot. You will want to copy the configuration to a scratch pad and then update the new one. Your programs will not be deleted, they will stay populated with the new programs nodes. If you have used any of the node in a scene though, they can get trashed. I have done this a lot lately because of the eisy-ui plugin changes. btw: this issue is exactly why in the new eisy-ui they went from 3-stores (local,beta,production) to one, where you do a beta by adding multiple sales options.

I deleted the beta from my dashboard, then went to the production store and clicked on Install but nothing happened.

sorry for the delay, painting day today.

@Techman , I saw your DM as well , what was the other server you tried?

and, of course, have you tried a reboot?

I just tested and am able to install from both stores, and am able to install on top of beta -> production -> beta looks like a local issue to you.

Edited 21 hours ago21 hr by sjenkins

I think something got screwed up in PG3. I've tried several other plugins to see if they would install, but the install button had no effect. It was working fine until I did a uninstall on the Tahoma plugin. I guess I need to only reinstall PG3 but not sure how, and don't want to mess up my installed plugins

You may want to open a ticket with UD

Thanks for getting back to me. Ticket is opened. I'll let you know the results