Guy Lavoie

So you tried the recovery in the announcement: sudo rm /var/udx/.udx_install_cleanup sudo rm /var/udx/.upgrade_status sudo pkg install -f isy sudo service udx restart The recovery instructions are written for a eisy, so it's normal that the interface re0 would not exist. For the polisy, that would be igb0 instead, so: sudo dhclient igb0 sudo service udx restart But first, what did you see when you did: sudo pkg install -f isy ?

That looks good, so it's not a messed up filesystem. Normally when the upgrade finishes, it prompts you to reboot. See that at all?

Log in with ssh and do the "df" command to show the disk apace, and post a picture of the screen.

Thanks. I hadn't thought about the multiple pages, which can certainly make organizing things much more intuitive.

Cool! Nice to have the tools to expand existing filesystems.

Let me send you a message in a few minutes

The easiest way is to copy and paste the link given in the release announcement. Otherwise you log in by ssh, go into the directory path shown in the link, and then use "vi" or "more" or view the sysconfig.txt file.

In my case, he had sent me a link to download it from. It would be a rather large file to send as an email attachment. Could you post an image of your screen following a "df" comnand from the unix shell?

Interesting. If you saw my first post about the two test Polisys that I attempted the upgrade on, the first one I did showed me a similar strange setup with only about 3 GB or so being used, and a filesystem using 512 byte blocks. I had recovered that particular Polisy using the disk image that UDI had me download, like you. I ended up recovering it another way (cloning the SSD of another Polisy) but what I *think* might have happened could be a mistake when I ran Rufus. When you select the image file to restore, you really need to choose the file correctly, as per UDI's instructions: From Boot selection, choose Disk or ISO image (Please select) and then click on the Select button which allows you to pick polisy.13.img that you downloaded previously The mistake I probably made was to pick the "polisy.13.image" directly in the Boot selection list (it does appear there), instead of selecting "Disk or ISO image (please select)", then select "all files" (by default the list shows iso files) and then pick the "polisy.13.image" file. I can't say for sure because I had restored that Polisy several months ago. But I can see how easy it would be to make that mistake. The funny thing is that the Polisy still worked, but with the much smaller disk size.

That's the thing with disk image files. It simply takes an exact picture of what's on your disk, sector by sector. It doesn't know or care if it's unix, windows, etc. To have a bigger filesystem than the 32 GB that the UDI image was created with, you'd have to go through an actual installation of unix, setting up filesystems, etc. Because all Polisys are the same when shipped, it was much easier for UDI to make one detailed installation they way they wanted it, and then clone the disk image to make the product.

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.