Guy Lavoie

If you're referring to Somfy shades using the RTS protocol, the way to do it is by timing, in a program. That's also how the Somfy plugin for the URTSII does it. You configure a parameter telling it how many seconds a full open requires, and it will then convert any percentage command (such as with Alexa) to a time value between the open and stop commands. Because RTS is one-way, you have no way to know if it's starting out as closed or not, so use this to the best of your knowledge on how the shades are used by the owner.

Looks like things aren't getting eisyer... Sounds like a trade war related issue. But an answer from the source would certainly be good.

In IoX launcher, click on "Admin Console (cloud)"

Ah yes, garage doors and KPL. This is one area where we really want to use the KPL LED as a position status indicator. I messed around a lot with it to get that functionality, no matter how the garage door opener is activated (including it's own RF remotes). I think I restarted the programming project 3 times. I did get it working as I wanted it, with one KPL button/LED for open and another one for closed. The end result is 14 separate programs. This includes proper status indication in UD Mobile too. The door activation hardware is one IOLinc (for input and output). The trick was getting to sense position change when not done by automation, and still update status, without triggering any events. To do that, I needed to use a disabled program that only gets run once. Fun stuff.

Use the search function to look for variable usage in your programs. Right click on "My Programs" at the top and then on "Find/Replace". In the pop up window, select the type of search from the select list, and then the value that you want to look for, and then "Find".

Dual band sounds nice, but if your setup isn't working anywhere except in that room, then it sounds like something is really wrong, which dual band modules might only make things work marginally. Have you tried the opposite: put your PLM and modules in any another location except that office? What else do you have in the office that might be creating noise?

The first thing I would suspect is electrical noise issues. Have you tried the devices in more than those two locations? Are the devices dual band?

Do you remember when you last updated it? Within the past couple of months, or much longer before that?

You could try a factory reset on the switch, then try the linking again. Factory reset is done by pulling out the link button for 10 seconds, then pushing and holding it in (as when you link it) until it beeps.

Just a note of thanks to whoever created and/or maintains this plugin, it's appreciated. I used the option to connect to a TCP port (no serial ports on a eisy) and for that, I used one of my trusty Lantronix EPS1 print servers. The serial port can be configured as a raw serial port. I bought a bunch of these many years ago and they have proven to be very handy.

I bought it off the shelf, but I searched and found it: https://www.hammfg.com/part/1599BSGY

I couldn't get the ZMatter enclosure in Canada, so I ended up making my own. Because my enclosure was bigger, I could put the whole board in it.

I periodically run the update on my test Polisy and I just did so now. Still showing 5.9.1_18 and has been the same since March 20.

Have you updated your eisy (or Polisy) very recently, like in the past two weeks or less? The earlier 5.9.1 updates would give you that error. If you haven't, do the update and try again.

It's specified elsewhere, but you need to snap off the top half of the card before installing it in the enclosure.

If it's that device that's going bad, then this will be a good solution. But if it's a noise issue, then it might just be a band aid on a bigger problem. Just be aware.

The 2486D isn't dual band, so will be more prone to signal issues, esp if there is noise on the powerline.

Yes, there is a migration you can do. See here: https://www.universal-devices.com/4x-migration/

That's another purpose of my Polisy as a test controller: to learn plugin programming. I've done a couple of simple plugins to get the hang of it. It's a steep learning curve

Thanks for the replies, and that is pretty well what I expected: there there would be no real difference, at least as far as making an "upgrade" from Polisy to eisy worthwhile is concerned. I'm happy about that. I first got the eisy, and then came across a used Polisy with the ZMatter board that cost me little more than the ZMatter board itself. I have the Polisy as my "lab" system and as a standby spare if the eisy should die an untimely death.

The initial question hasn't been answered: how much faster is the eisy compared to the Polisy? It would be interesting to know.

No, not as a Wait statement, within a single program. But you can do it if you break it up into more than one program. I have my bathroom fan timer set up like that. For example, you want to perform Action B a number of minutes after Action A, where the number of minutes is in variable "i_wait". In this example s_timer is a status variable. If original trigger condition Then Action A Then s_timer = 1 If s_timer > i_wait Then Action B Then s_timer = 0 If s_timer > 0 Then s_timer +=1 Then Wait 1 minute The third program is the "timer", incrementing by 1 every minute, as long as the s_timer is set to any value above 0.

Which version of the UD Mobile app do you have, Android or IOS? I'm not sure it's been successful yet with IOS. A few of us have succeeded with Android, though it only configures devices as on/off devices for now. This is still beta. Have a look at our discussions here:

Did you do the migration using a backup and restore? Here is the procedure I found elsewhere on the forum: 1) Make sure 5.5.3 is installed (we're already past that now) 2) Leave your Zooz dongle connected and ZMatter Z-Wave dongle not connected 3) Create a backup of your Polisy/eisy (File | Backup ISY) 4) Create a backup of the Polisy/eisy you are migrating to (if different than in step 3) 5) Go to configuration tab in Admin Console and select "Migrate to ZMatter ZWave" 6) Choose the option that allows you to create a "migration" backup (first option) 7) Once you have your "migration" backup you are ready to migrate To migrate, you remove the Zooz dongle and plug in the ZMatter Z-Wave dongle. If you have a ZMatter Z-Wave board then you would power down Polisy, add it, then power on again. Next, use (File | Restore ISY) to restore the "migration" backup you just created (in step 6). When your Polisy/eisy restarts it automatically migrates and creates the new nodes, does the device interviews etc.

Ok, so you want to be able to issue a scene command from UD mobile and have your controller "filter" it through a time of day condition, to allow it to be executed or not. Since you mention that you have a eisy on the way, I can tell you that there is a very nice way to do that on the eisy, using a free plugin (called "Virtual"). The idea is that you create a virtual switch that you add to your existing scene. You then create a program that watches for changes in the status of that virtual switch, and ANDs that with your time of day criteria and anything else to then execute your command(s). Since this virtual switch can only get turned on by your scene, this is how you can get a scene to execute a program. You would actually need to create this as two scenes: one that turns on the virtual switch (and triggers the program) from UD Mobile, and then the actual scene that you want to execute, which is run by the program.