StangManD

Well after many hours of screwing around with it and a support ticket later, it's still not working and the solution is to blow away the VM and start over with hoping the HA backup works after getting it back up. I've dug through the bhyve logs, enabled debugging and nothing is helping determine why it's just hanging upon boot. Nothing in the main log that would suggest why, nothing in the debug log either, just hangs and doesn't finish booting. I've decided now after 2 OS updates (when I updated to 6.0.0 initially and now with 6.0.3) and a 2/2 record or breaking this HA VM, I'm moving it off of the Eisy and will build it in a Proxmox environment and move on with my life... not worth the annoyance or headache it creates. For me there are no critical automations running, I just like the dashboards I've built and overall interface way better. Well my Eisy came back up updated, so this was not my issue... it was that the VM has somehow become unhappy, even with my NVMe drive in mirror mode which you would hope might help, but I guess not. Good luck with yours, I can only imagine.

Additional info, hoping someone can help here. sudo vm list output: NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE homeassistant default uefi 2 1G - Yes [1] Locked (eisy) /etc/rc.conf file still looks like it contains the correct parameters from the 6.0.0 install. vm_enable="YES" vm_dir="zfs:storage/vms" vm_list="homeassistant"

Not sure where to begin here, this has been working for a very long time and even on 6.0.0, but I just upgraded to 6.0.3 and it's not coming up. When I am SSHd into the Eisy, I can poweroff and when I start in interactive mode, it goes through what seems to be a BIOS boot type of screen/sequence then goes to a screen that says Booting Slot A (OK=1 TRY=1) and just has a flashing cursor and never moves. Not sure what to do or where to go from here.

Thanks for confirming. So I went ahead and upgraded and now Home Assistant didn't start evidently... after the upgrade/reboot HA has not come back online. Now I have to chase that down, if there's any help anyone can provide on that please and thank you.

Hi there, I'm currently on v6.0.0 and of course when I log into Admin Console, it tells me there's an update and to make sure to review the release notes, and to go to the Configuration Tab and click Upgrade Packages. So I'm thinking, this is fine, I'll look at the notes first before I do that... and this is where I get stuck because the direction is now conflicting. The release notes say: Please use UDMobile to upgrade the OSApplication Packagespkg eisyui must be upgraded to 0.6.2 To further confuse the situation, in UDMobile on my iPhone, when I click Settings > Firmware, it says "Firmware update available." Current Version 6.0.0 - PG3x-3.3.22 Available Version 6.0.0 There is a link to Upgrade Instructions in the mobile app that takes you to the old September '25 post for the original installation. There doesn't seem to be a way to actually perform an upgrade from the UDMobile app itself, so thinking that's my answer but want to make sure I'm not missing something as the instructions are branching off in a confusing way to me. Am I correct in coming to the conclusion that I should be going straight to the Admin Console after doing all applicable backups, then performing Upgrade Packages from there? Thanks in advance

I setup the HA VM a long time ago when the tutorial was posted with the instructions and it's been up and running solid on top of my Eisy since. As I realize it's completely redundant for the most part, there were things about it I liked and had integrated like Home Kit and some other things but now it seems after the 6.0.0 upgrade, it's just gone. I've opened a ticket, but I guess maybe I'm just late to the party here... is this to be expected on an upgrade? I know it was a "major OS version upgrade" but I didn't expect it to be wiped out. If it has been, I want to make sure any remnants of it that may be left are cleaned up before reinstalling. Seems like if I have to do that, I'd likely need to set back up from scratch, not sure one of my HA backups would even work. Have others run into this and is this to be expected?

This worked for me... I've been messing around with trying to get reconnected to the admin LAN console since updating and this was it for me :). Thank you a ton! Specifically this line: https://<local ip here> :8443/admin.jnlp

Okay, so the fix for me was as follows and please keep in mind I only have 1 Z-Wave device, so that may have something to do with the directions. 1) Remove/Exclude my one Z-Wave device. 2) Click the Migrate button under the Configuration tab. 3) Add the Z-Wave device back (it added correctly with ZY node names. 4) Correct my programs with the new device node names.

Still going through support, they rock. As of now, it was mentioned that I am seeing the original Z-Wave menu and I was asked if my Z-Wave nodes begin with "ZW" or "ZY". Mine begin with "ZW", which evidently "matches" the old original menu, so I'll let you know what that means as to what they are having me do to address/fix when I hear back.

Thank you... yeah my Z-Wave and Zigbee devices that run off of this device are simply water alarms and an alarm siren for now. Nothing crazy and only 5 total devices anyway. If I have to remove them all and re add them it wouldn't be the end of the world, just want to make sure I do whatever it takes right. I'll keep you posted. Thanks again

Thank you... and I agree, I usually do my "rounds" and go back up PG3, IoX, and HomeAssistant (I know that's not their deal but it's part of my backup process). Adding one more wouldn't be the end of the world but agree, would be nice to catch it all in one place somehow. I do realize this all lives on a VM environment ultimately anyway so some of that is inherent I suppose. I've created a support ticket and will report back what their suggestion and resolution is. Thanks again for your responses.

@xlurkr - Yes, I did have a Zooz 700 USB stick prior to the ZMatter dongle however I already went through that process back when I replaced it. So are you saying you clicked the migrate button in the Configuration tab, then those showed up? I'm afraid that I'm going to break what works just fine by doing that though... what was your experience by clicking the migrate button, did it take you through other setup steps or anything? @jkmcfadden - Yes, I do not have those options in my menu. This is what mine looks like:

I'm following the instructions line by line before updating my system to OS14.3 and IoX 6 for the new eisy-ui experience however in the instructions, it's telling me to go to the Z-Wave menu and select Backup when in the admin console. I do not have a "Backup" menu option. I'm currently up to date on OS 14.1 release P6 and IoX 5.9.1_18. I am running the Universal Devices ZMatter USB Dongle as well and control both Zigbee devices and Z-Wave devices from it. Can someone help me understand if this is something I need to worry about or not prior to clicking the "update packages" button? Last week I ran the update packages button successfully a couple times to make sure I was fully up to date before they did the final big release. I have also backed everything else up at this point (I do this regularly) but have never gone into Z-Wave to even look for a backup option... however there isn't one to be found. Please advise. Thank you in advance!

I get it and it’s no fun! It ultimately needed multiple rounds of updates over and over. Mike is wonderful for support. If you create a support ticket he will walk you through it all but basically mine was in a state of partially updated. Once it fully updated it worked fine and was good to go. After my full rebuild and restore and multiple rounds of updating, it finally came back to life as of my latest backup. I’ve now learned to back up every single time I make a change. I got lucky because even though I had old backups, they were probably about 90% there from what I was running the day of the crash. good luck with it and I highly recommend creating a support ticket.

Edit - nevermind... it was a firewall rule across VLANs. Thank you for taking the time to respond... I accidentally had my response (from Eisy to weather station) disabled. It's good to go now. Thank you!