Guy Lavoie

Good. I thought so, that you would be doing something like that. Logical too, get the functionality first, and get the pretty stuff done later. As it is, it's darker than the inside of a cow! lol So the concept of tiles is to create a home screen with the nodes that you want to see right away when logging in, a sort of favorites? In my mind the term "tile" evokes more of a smaller icon, that you could then click on to see the details, a bit like the favorites screen in UD Mobile. I just want to make sure I get the idea.

This is what I have: https://www.amazon.com/Adapter-ELUTENG-Converter-Portable-External/dp/B07VP2WH73?th=1

You should get the USB adapter to allow you to restore the SSD from a file.

I haven't opened up my eisy yet but from reading other information on the eisy, it doesn't have a removeable SSD. There is room for one, but UDI uses the one built in on the motherboard. It would certainly be nice to be able to make the same kind of image backup to a file. Maybe there's an alternate way to do that, or at least a full drive unix cpio backup to a file that can then be copied over the network.

Just a note that I got this resolved. I took the SSD out of the properly working Polisy, made a disk image file with Rufus, and then wrote that image on the SSD of the Polisy with the weird filesystem sizes. Now I have a perfectly working clone, which is ok for test purposes. It's also a great way to make an ultimate backup, when you're about to make a big change like this kind of version upgrade.

Logging in via ssh is the same as before: ssh admin@eisy.local In some cases you can/need to use the ip address instead, ex: ssh admin@192.168.0.199

When I updated my Polisy, it did say that a reboot was now required, which I did from the Admin Console Configuration screen. I imagine that the eisy will be similar.

Works for me. See the 6.0.0 support thread.

IoX finder still works for me (also a Polisy), but looks a bit different now when logging in.

Now that this is officially released, I thought I'd at least give it a try on my lab rats. I have two Polisys (or is that Polisies?) that I use for testing. On the first one I tried, the upgrade seemed to go through, but the version was still 5.9.1 and the OS was still 14.1. So I logged in by ssh and watched the upgrade process (tail -f /tmp/udx.upgrade.log) and relaunched the upgrade in admin console. It was failing due to the filesystem being full. Interesting. using the unix "df" command showed that the zudi/ROOT/default filesystem had 6424805 blocks, and the heading indicated 512 byte blocks, and was full. Ok, so I sshed into my other Polisy to compare. That one has 25621361 blocks, and the heading is for 1K blocks. Makes a lot more sense for a 32 GB SSD. So I logged into Admin Console on that one, launched the update...and it worked. 6.0.0 in all it's glory! And on a Polisy! I finally got to take a look at easyui. It will take some getting used to... but I can get a feel for it and learn, and keep up with the new releases before making the actual plunge with my eisy. It certainly is "dark" mode. Hopefully we'll be able to customize the look at some point. Back to the Polisies (or is that Polisys?) I'm mostly posting this for others who might try it. The one that shows a much smaller filesystem size is one that I restored using rufus and an image file that UID sent me. Rufus seems to detect and leave existing filesystems in place, only restoring the contents. Both Polis...whatever have 32 GB SSDs, so I wonder if the filesystem setup or configuration was ever changed. The one that failed is an older unit, and it's Unit ID (MAC address) is lower. Anyways that would be the subject of a separate discussion, or if anyone has a thread or other hints on how to set it up. Just a hint for anyone else with a Polisy that's trying to install eisyui and runs into a similar problem.

Well, IoX 6.0.0 just got released now, and Polisy is included:

The "Pro" thing is a node limit in the ISY994i, which is different from the link limit in the PLM. It might still be worth checking out though.

What I said was "bring" it, not "bridge". Basically, install it temporarily near other working devices, and try linking. If it's a wall switch, connect the white and black wires to a power cord and plug it in. The idea is to determine if it's the switch itself that's the problem, or it's location. Plugging a lamp module into a long extension cord to bring it close is also a viable thing to try.

If you have spare dual band lamp modules handy, try putting one on each panel. They will act as phase couplers. If your nearest working device is 100' away from your new ones, then that would probably explain your problems with linking. Try temporarily bringing one of the new switches near your working ones and try again.

There is a limit of the number of links that the PLM can have. It's something around 1000 (or 1024). You really need a large amount of devices (a couple of hundred) to hit that. You see how many you have by going in Tools -> Diagnostics -> Show PLM Links Table. Click on Start and wait for the links to be retrieved. Then click on Count.

Look here. But if you're having trouble adding device types that are the same as some you already have, then something else might be wrong, like your PLM going bad.

Else statements that actually perform actions should be very rare. Usually they'll just do something like reset a variable.

Well the REST api is when you want to go the other way: from an external device, computer, etc TO the polisy. Your initial post is about having the polisy send commands to the devices in the new building, over wifi. Assuming you want to control simpler things like lights or appliances, using devices that support Matter would probably be the most straightforward way to do that. If you use wifi based Matter devices (ie: not Thread) then your polisy should be able to do that already, if it is running IoX 5.9.1. Matter is still in beta development, so some testing would be required. Otherwise, you could use other IP based devices with an open protocol, and control them via a plugin if there is one, or using Network module commands.

If you are using Insteon dual band devices (like almost all of them currently are) then they should work, since it's rf based. It depends on how far apart the two systems are, for proper communications.

I have an Elk ESM1 signal meter from my X10 days, and it has been handy for seeing Insteon powerline transmissions, and noise. Not perfect, but if the noise is bad enough, it can give you a quick hint.

You might need to hook up a hdmi monitor and keyboard, and see how it comes up. Have you tried reconnecting it back where it was to see what happens?

I'm always leery about versions ending in 0.0. I have no real need to update yet so I'll wait until the initial issues are worked out.

Another thing with scenes is that when you launch one that has several Insteon responders, Insteon communications will be busy for a noticeable period of time, up to a couple of seconds. This is because of the "cleanup" messages that are sent back and forth between the devices. If you have programs that launch scenes, avoid any programming that sends more Insteon commands immediately after launching a scene. Wait a couple of seconds. Commands sent too soon might not be reliable, and might even cause a dreaded "all on" event.

We love happy endings! But...make a backup or three, right now! And clean the contacts on your SD card. Then you'll be all set for a while yet.

I doubt that someone will rewrite the Hue plugin to use the V2 API. I'd try Matter, which is still in beta on the eisy. Matter was specifically created to allow interoperability between systems, and this is a good example of that. You'll probably get the basic functionality, minus some of the fancier features.