Guy Lavoie

We're all noobs when it comes to eisy-ui, and some changes in terminology are going to add more time in learning it. If you have two screens on your computer, I find it useful to have admin console on one screen and eisy-ui on the other, and then compare the look of something (node, program, etc) side by side to see how your familiar features now appear. I'm presently doing this on one of my test Polisys, to teach my old brain new tricks. It's the little things you notice and learn to appreciate. For example the node list in admin console only shows you node names. In eisy-ui you also get it's address and basic status, which is handy. Then you notice that pending changes appear as a red dot, etc. The idea is to breed familiarity, a bit at a time.

My initial gut feeling is that the PLM has gone bad. Thankfully you have a spare on hand. If it's a used PLM, do a factory reset on it first (plug it in while holding the link button pressed until it beeps). The proper procedure for replacing it is to start with making a backup. Then: Power off your eisy Replace the PLM with the new one Power up your eisy Log into admin console and under File -> Restore PLM This will take time, since it will be writing out the new PLM's address to every device. Then if you have any battery powered devices, these will need to be restored individually (Restore Device) by waking them up by pressing their link button and initiating the restore.

It's a little bit slower than a eisy, but hardly feels "sluggish", more like a one second pause when loading some things. One thing that hasn't been mentioned about eisy-ui is that loading programs into the editor is almost instantaneous. You can literally log into eisy-ui and edit a program in seconds. It loads the program in real time, whereas with the admin console you log in, with a long delay before you can see the node list, then click on the Programs tab and another long delay before the program list appears. It can get annoying.

I just loaded this up on a test Polisy. Once again, it's about learning where things now are. 🙂

Well, you get the latest updates and fixes, and will likely make any eventual move to a eisy smoother. You get eisy-ui, which will become fully functional by year's end. Support for the new zwave and zigbee dongles. Keeping it current costs nothing, and can only help.

Maybe a workaround could be used (I haven't tried this): Create a program looking for the status change of your triggering Zwave device, which then issues a scene command.

See my edit above, about using the ip address

5.8.4 is getting a bit old. Have you verified if your operating system meets the minimum version for upgrades? Look at the current release requirements, indicated in the second post above. If the version is ok, then you'll need to upgrade using a ssh session and the commands indicated earlier. For IoX finder, add a new entry with the ip address in it, such as https://192.168.0.123:8443/desc and try that.

You're good to go. The best way is still probably by doing it through admin console. Just do your backups and upgrade.

I do appreciate that we're given ample transition time. But it's very different and getting used to the new format will take time.

Making fun of features!

I haven't tried any of these new ones. My first zwave dongle was the Zooz 700 series, then I got a ZMatter dongle, which I still use. Someone else on the forum did get one of the newly supported dongles above. They are automatically detected, so there is no need for setup.

They're listed here: AeoTec Z-Stick 10 Pro – Dual protocol Zigbee/Z-Wave [ link ] Sonoff Z-Wave 800 Dongle Plus [ link ] Zooz 800 Z-Wave USB Stick [ link ] Zigbee Requires an external dongle (not included): AeoTec Z-Stick 10 Pro – Dual protocol Zigbee/Z-Wave [ link ] Sonoff Zigbee 3.0 USB Dongle Plus [ link ]

You only really need the admin password.

Yes. So go ahead and do the update, from the comnand line as explained earlier.

Yes, hardcode the ip address of your controller instead. For example: https://192.168.0.123:8443/WEB/sysconfig.txt

Hah, though that will often turn out to be the same!

Click on the three little dots to the right of the "Node" heading (your mouse pointer needs to be over the heading to see them). Choose "sort by ASC" (ascii order).

Will do. Thanks!

It's model 43095, I had posted a picture of it on page 4 of this thread, plus a link to some other information. I also displayed the DH cluster line that shows energy consumption. This model seems to be discontinued. I also have a GE branded one that seems to be the same internally. I have 9 of these, including one that's brand new in it's box. I'd be willing to give you that one (I'd send it to you) in order to have it supported in a future IoX release. Would that work? Thanks.

Hah, I'm far from "knowledgable" on this stuff, but google has given me many answers!

Yes, the Beecon supports RTS and Zigbee, while the Switch does both of those plus a newer protocol called IO

Existing shade controllers shouldn't be affected. My URTSII or existing remotes weren't affected. The general idea with RTS is that you push a button on an existing controller or remote, so that the gateway listens to the signal to learn the RTS address of that shade. Somfy remotes learn the same way. Setting up a new shade (ie: with no paired remote yet) is a bit more work because as you say, you need to access a tiny button on the shade itself. I suppose you could delete the app once you're done, but why? Just keep it on your phone for testing, adding new shades, etc.

Yes, the Switch (or Beecon) needs the TaHoma app to add the shades to the gateway device. You also need the app to generate the unique key that will give local access to the gateway, and that you need to eneter as a parameter when configuring the Somfy plugin. For your second question, Somfy says "up to 65 feet in optimal conditions", so I'd position the gateway as high and centrally (to your shades) as possible. Mine is on top of a disk cabinet that's near the center of the house. There are also RTS repeaters available.

I get a sense that it might get incorporated into UDI's support, possibly as a self-help screening process if you want to open a ticket. Not that I'm against the idea. Just something that seems to be in the queue. It could be useful for some of the usual questions that can be hard to search on the forum, such as "What updates are still supported on the Polisy?" or "What is the proper procedure to replace a Insteon PLM?".