stevesreed

adding the following to /etc/rc.conf got me back up and running: vm_enable="YES" vm_dir="zfs:zudi/vms" vm_list="homeassistant" NOTE: my zfs setup is a bit odd, it's probably vm_dir="zfs:/storage/vms" for anyone who set it up with the script that was available later to set things up.

Everything is running now, except I've lost my Home Assist VM. Trying to recover that now.

I was also having issue with loging in to PG3x, so I assume UDX was not working for some reason. A full system reboot seems to have fixed both the PG3x login issue and the update not working.

I clicked the "upgrade packages" button in the admin console, but nothing seems to happen. The console never closed or became unresponsive. The version in the admin console "About" dialog box is still v5.8.4 and the unix version is still "FreeBSD eisy 13.2-RELEASE-p11" What the best way to see what happening?

I got that initially, but I tried again later and it worked fine. I'm not sure what changed. Maybe it was fixed with 2024.4.2, which came out yesterday, but maybe after my first attempt and before my second?

It could just be my imagination, but rebooting does feel faster. That's the only difference I've noticed so far.

I was trying to avoid changing the script file, but if you're editing it anyway. You can just add a single line to the end of the script: setup_nvme_boot which will call the function to start the process.

after running with bash -c "source ~admin/setup_nvme_boot.sh; setup_nvme_boot" everything works correctly. rebooted and everything is up and running on a big, fast SSD [admin@eisy ~]$ gpart show => 40 1953525088 nvd0 GPT (932G) 40 131072 1 efi (64M) 131112 1927282688 2 freebsd-zfs (919G) 1927413800 8388608 3 freebsd-swap (4.0G) 1935802408 17722720 - free - (8.5G)

To get the script to run I had to use: bash -c "source ~admin/setup_nvme_boot.sh; setup_nvme_boot" To get the function to be called in the shell script.

It looks like it might not work actually, due to the portal migration not allowing you to go back to an old ISY once migrated away from it. "Please note that a license transfer is permanent. It will not be possible to migrate the license back to the original ISY."

I'm moving to eisy this week, and was wondering if I should keep the polisy as a back up incase the eisy ever goes down. Has anyone restored an IoX backup that was made on an eisy to a polisy? I don't have any plugins, just a bunch of Insteon and zwave devices and a few simple programs (most complex automation is done in HA) Since the my Insteon PLM and Zmatter board are usb, moving them back and forth is easy and quick. If recovering from a failed eisy is as simple as updating the polisy to the latest and restoring a IoX backup, it seems like keeping it is worthwhile.

I had the same failure on Friday. 100% full SSD. Michael checked several things, and we decided corupted SSD/file system is the likely cause, so restoring SDD from an image was the best course of action. Here the process, though I'd wait until support contacts you, just incase they want to see if they can find the source of the missing disk space: https://forum.universal-devices.com/topic/42174-polisy-ssd-image-restore-process-for-a-corrupt-ssd/ My eisy arrives tomorrow, so I'm glad to hear the restore from polisy backup to eisy should be smooth and painless...

I removed and re-added my i3 Paddle after upgrading to 5.6.3, but it still says it's an i3 Switch in AC, and there is no % dim value shown, just on/off status. Are you seeing the dimmer values somewhere else?

That is a great idea! Thanks. I have a notification when I leave the door unlocked for more than 5 minutes, and they are getting annoying. This should "fix" the issue for now.

The thread you linked from @bumbershoot is talking about the i3 Dial working as expected. I have not seen any posts about the i3 Paddle working, nor has it been listed as working in any release notes.