xlurkr

Makes sense. But what is the smallest drive ever shipped with a Polisy? Both of mine are 32G, so why not have that be the default partition size? -Tom

I think - not sure - that the image I flashed was already 6.0. It was definitely FreeBSD 14.3 based on the name (though it was misspelled "poilsy" as @larryllix correctly documented.) That's why I said it didn't seem like the upgrade packages that I did after the reimage actually did anything. Also, I think I had a 6GB partition from the start. Perhaps Michel is creating these on the fly as each request comes in, and basing each new one on lessons learned from the last one. I know that the link to my image was time-limited, because it timed out and I had to ask for another. Meant to prevent sharing of images, potentially "bad" early ones? Or maybe it's tied to my UUID somehow, for the purpose of tracking portal subscriptions? -Tom

Thanks. I found your older post and just did this on my Polisy. In addition to the zudi substitution, I had to "sudo" the autoexpand command. It looks like it worked. Two additional comments: I'm not sure the update packages that I ran after reimaging did much, if anything. And it probably all fit in the 6G original partition because this is an empty Polisy. Now, I'd love to hear from anyone who has run upgrade packages on a Polisy and had it work correctly. I still have not upgraded my working Polisy, and I don't want to without more confidence that it will work correctly. -Tom

I saw this, but I can't find it. can you repost? Thanks. @Michel Kohanim your image did get me going again, but I'm concerned about the disk image size. Should I be? Is there a reason that the total disk space is so much smaller than before, and the used amount (capacity) is so much higher? -Tom

Looks like I got a small partition. This is a 32GB SSD. Everything is working, but not a lot of free space. I'm going to check out the video. -Tom

Fortunately, this is a spare unit, and it had no devices, programs, etc. So I guess I'll reimage, check the size of the image, and try to upgrade again. I might as well reenable the portal subscription, too: it doesn't cost much, goes to a company with great support, and would allow me to do more kinds of tinkering if I leave this unit in service. -Tom

The one I was upgrading had a lapsed portal subscription, but I hope that didn't have anything to do with the failure. btw, Michel got back to me and told me to flash it. I have the USB device from back when they all had to be flashed if they had the old FreeBSD version, but I'd rather try anything else first. Anyone have any suggestions? -Tom

OK. While the Launcher has at times failed to find one or more of my Polisy automatically, it has never failed when I used the add button and put the address in manually. Until now. And never have I had to use portal credentials to log in. -Tom

@larryllix: I saw you mention this in another thread. In what place and at what time are you referring to this login? As I said above, I plugged in my Polisy, the Launcher found it, and I clicked on its entry and attempted to launch the AC. Without any login request appearing, it told me that I needed to upgrade to 6.0. As I wrote, the first time I clicked no, and it terminated. The second time I clicked yes, and it threw up a dialog warning not to interrupt it. I dismissed it and my Polisy beeped a few times. Since then, I can't get Launcher to find it, which I assume is because the isy service isn't starting. Where can I log in with my email address? -Tom

btw, I should document for future posterity that your modified command for getting a new (different) dhcp lease did work for me, but since I was connected via ssh on a Polisy and not keyboard/monitor on an Eisy, as MIchel's instructions assume, I lost the connection, had to get my router to tell me the new address, establish a new connection to be able to restart udx again, only to still find that the isy service didn't start. Kinda illustrating my point about how we Polisy owners are a bit of an afterthought. -Tom

No offense, but I think I'm going to wait for a response to my ticket at this point. I promise I'll come back and post whatever I learn from UDI about what the problem was and how they fixed it. Looking at my old posts, and some of yours and larryllix's I get the sense that they have a tendency to leave out a step or two in their automated upgrade procedures for Policys. Understandable, if all they have and use these days are Eisys. -Tom

I just tried it again. The "pkg install" command doesn't have any error messages and installed one package - the rest were already there. It's the udx restart that has the error messages - something about needing to use the -H flag when running pip via sudo, and a pkg named "serial" not found. isy service still not running. According to Michel's recovery instructions, it must start for the Launcher to find my Polisy, and let me launch the AC, and finish the upgrade by clicking on upgrade packages? -Tom

Posts crossed. Yes, I did all those steps, and thanks for explaining the re0 thing. I'm assuming that just clears up IP addressing problems, but my Polisy has maintained the same address the whole time, and I have always been able to reach it via ssh. Many messages scroll by when doing the pkg install and udx restart, and some of them look like error messages. -Tom

I have a ticket in, and it wouldn't surprise me if UDI intervention will be required. The system is responsive via ssh, it's still on FreeBSD 14.1, I don't think there's any upgrading going on, and for some reason their documented recovery steps don't get the isy service to start, or the Launcher to let me launch the AC. So for the moment, it's a fully functional FreeBSD computer and a fully useless Insteon and home automation controller. But I have faith. At least it's more than a brick! -Tom

Nothing is happening, and since I can't launch the AC, I don't know how it would tell me to reboot. -Tom