tazman

@xKingattached is my homeassistant.conf file is there any other VM configuration you know of? loader="uefi" cpu="2" memory="2G" network0_type="virtio-net" network0_switch="public" disk0_name="disk0" disk0_dev="sparse-zvol" disk0_type="virtio-blk" uuid="EDIT" network0_mac="EDIT" #graphics="yes" #graphics_wait="yes"

@xKingthe lines are a little different which one should go? ifconfig_re0_ipv6="accept_rtadv" ifconfig_re0_ipv6="inet6 accept_rtadv" With the 'vm_list' out and '/etc/sysctl.conf' line out [admin@eisy ~]$ sysctl -a | grep up_on_open net.link.tap.up_on_open: 1

@xKing with that rc.conf and the line out of cron homeasstant starts but vm-public and Tap0 are not "UP"

###MAINTAINED BY UDX#### ###DO NOT MODIFY### hostname="eisy" # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev="NO" zfs_enable="YES" dbus_enable="YES" sshd_enable="YES" moused_nondefault_enable="NO" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" clear_tmp_enable="YES" #NTP ntpd_enable="YES" ntpd_sync_on_start="YES" #HDMI is disabled by default #kld_list="i915kms" #Make sure dhclient is run in the background background_dhclient="YES" #make sure we support double stack ipv6_ipv4mapping="YES" defaultroute_delay="0" #Network Interfaces (default) rtsold_enable="YES" #for now, do not let iwlwifi/iwm get loaded devmatch_enable="YES" devmatch_blocklist="if_iwm if_iwlwifi" UDX_UPGRADE_STATUS="active" ifconfig_re0_ipv6="accept_rtadv" ifconfig_re0="DHCP" ifconfig_re0_ipv6="inet6 accept_rtadv" vm_enable="YES" vm_dir="zfs:storage/vms" vm_list="homeassistant" mdnsresponderposix_flags="-f /usr/local/etc/udx.d/static/mdns.services" ~ ~ ~ ~

@KSaccullo01I tried putting the below line at the bottom of the /etc/crontrab and homeassistant does not start for me. @reboot sleep 180 && vm start homeassistant

@xKingthis was a suggestion that might help now?

Added Output [admin@eisy ~]$ sysctl -a | grep net.link.tap.up_on_open net.link.tap.up_on_open: 1 But if I try to enable vm_list="homeassistant" in rc.conf the virtual switches are not UP any more.

Yes

@xKingthat brought it up! Now will that carry over on reboot or is there something we need to add somewhere?

@xKingif it just works for you I think that makes you a guru I appreciate the help and I hope you can follow my previous post ok!

The dhclient was just a way I found to make the vm come online. ifconfig_re0="DHCP" ifconfig_re0_ipv6="inet6 accept_rtadv" Was already in mine and I placed # in front of the home assistant so it would not start automatically. After restart [admin@eisy ~]$ sudo ifconfig -a Password: re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE> ether 00:21:b9:02:61:da inet6 fe80::221:b9ff:fe02:61da%re0 prefixlen 64 scopeid 0x1 inet6 2601:500:8801:38a0:221:b9ff:fe02:61da prefixlen 64 autoconf inet 10.0.0.66 netmask 0xffffff00 broadcast 10.0.0.255 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 groups: lo nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> vm-public: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether 96:f8:51:04:43:ae id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> ifmaxaddr 0 port 1 priority 128 path cost 20000 groups: bridge vm-switch viid-4c918@ nd6 options=9<PERFORMNUD,IFDISABLED> After starting home assistant and showing running under vm list but is not available at homeassistant.local:8123 where I find it when it is running. [admin@eisy ~]$ sudo ifconfig -a re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=82099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE> ether 00:21:b9:02:61:da inet6 fe80::221:b9ff:fe02:61da%re0 prefixlen 64 scopeid 0x1 inet6 2601:500:8801:38a0:221:b9ff:fe02:61da prefixlen 64 autoconf inet 10.0.0.66 netmask 0xffffff00 broadcast 10.0.0.255 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 groups: lo nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> vm-public: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether 96:f8:51:04:43:ae id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> ifmaxaddr 0 port 4 priority 128 path cost 2000000 member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> ifmaxaddr 0 port 1 priority 128 path cost 20000 groups: bridge vm-switch viid-4c918@ nd6 options=9<PERFORMNUD,IFDISABLED> tap0: flags=8942<BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: vmnet/homeassistant/0/public options=80000<LINKSTATE> ether 58:9c:fc:10:90:31 groups: tap vm-port media: Ethernet autoselect status: active nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> Opened by PID 8050 Since home assistant is not running there is no traffic. [admin@eisy ~]$ sudo tcpdump -i tap0 -s0 -vvv tcpdump: listening on tap0, link-type EN10MB (Ethernet), capture size 262144 bytes

I managed to get eisy up and running with something I found online. After eisy is up I was able to get HA running again with the sudo dhclient tap0 sudo dhclient vm-public Now I just need to be patient and wait to see what @Michel Kohanim's thoughts on how I got it to work.

@rob7419Well I hosed my eisy I put cloned_interface="bridge0 tap0" and ifconfig_bridge0="addm re0 addm tap0" in my rc.conf file and it will only boot to a read only file system. I ordered a USB reader that I should be able to restore my backup rc.conf file I made from Amazon that I should get tonight. When it boots it says "Enter full pathname of shell or RETURN for /bin/sh:" does anyone know of a path that would allow be to be able to load something where I would be able to edit a file?

I found that if I enter sudo dhclient tap0 sudo dhclient vm-public both of them get an IP address and then I have to start HA through VNC then it becomes available at homeassistant.local:8123 so I think the problem is with the setup of the virtual network devices but I don't know how to fix it. I don't know that this will help @rob7419 because I did not have an IP address listed when I started HA through VNC.

No problem I appreciate your help and expertise trying to figure this out! I think the question is whether it would be beneficial to look at @rob7419's system or if we can get mine working then you can help them with a fix.

@Michel Kohanim I already submitted the ticke we have been working on it.

@rob7419 the post you linked is HA has trouble loading the ISY plugin which I experienced but is not related. I'm at a lost for where to go from here I can not even run sudo fl.ops revert.to.emmc.boot to return to the old drive and try to star over I get executing from /usr/local/etc/udx.d/static cannot resolve path '/dev/mmcsd0p3' Sat Mar 2 10:36:46 MST 2024|/usr/local/etc/udx.d/static/fl.ops: failed replacing the zpool ... I guess I'm just lucky ISY is still working.

I could really use some help with this! When I perform a fresh install of everything including sudo pkg remove edk2-bhyve sudo pkg remove vm-bhyve then run my script everything is working fine but once I reboot eisy HA drops off the network and will not come back. The info for the switch and HA look the same after reboot so I think something is messed up with the connection to the operating system but I can not figure out what is wrong. Any help is greatly appreciated! [admin@eisy /]$ sudo vm switch info public local: _netgraph,: bad variable name ------------------------ Virtual Switch: public ------------------------ type: standard ident: vm-public vlan: - physical-ports: re0 bytes-in: 796128377 (759.247M) bytes-out: 802290155 (765.123M) virtual-port device: tap0 vm: homeassistant [admin@eisy /]$ sudo vm info homeassistant ------------------------ Virtual Machine: homeassistant ------------------------ state: running (33005) datastore: default loader: uefi uuid: 642bcf48-d786-11ee-82f2-0021b90261da cpu: 2 memory: 2G memory-resident: 2151665664 (2.003G) console-ports com1: /dev/nmdm-homeassistant.1B network-interface number: 0 emulation: virtio-net virtual-switch: public fixed-mac-address: 58:9c:fc:09:77:b9 fixed-device: - active-device: - desc: - mtu: bridge: vm-public virtual-disk number: 0 device-type: sparse-zvol emulation: virtio-blk options: - system-path: /dev/zvol/storage/vms/homeassistant/disk0 bytes-size: 137438953472 (128.000G) bytes-used: 8130683904 (7.572G)

Yes after some reading about Bhyve I found the switch is responsible for the network interface so I performed a "sudo vm switch destroy public" then instead of trying to figure out how to add it back I stopped HA "sudo vm poweroff -f homeassistant" then removed it "sudo vm destroy -f homeassistant" then ran the script to install it. I think all those commands are correct I did a lot of experimenting and figured out the commands from https://www.gsp.com/cgi-bin/man.cgi?section=8&topic=VM-BHYVE

@carteriii if you look in your Alexa app does the device trigger when the variable changes?

Here is the vm info if someone could look at theirs to see if anything stands out [admin@eisy /]$ sudo vm info homeassistant ------------------------ Virtual Machine: homeassistant ------------------------ state: running (1802) datastore: default loader: uefi uuid: e5fb8b86-d29b-11ee-a9aa-0021b90261da cpu: 2 memory: 2G memory-resident: 724877312 (691.296M) console-ports com1: /dev/nmdm-homeassistant.1B network-interface number: 0 emulation: virtio-net virtual-switch: public fixed-mac-address: 58:9c:fc:0f:be:89 fixed-device: - active-device: - desc: - mtu: bridge: vm-public virtual-disk number: 0 device-type: sparse-zvol emulation: virtio-blk options: - system-path: /dev/zvol/storage/vms/homeassistant/disk0 bytes-size: 137438953472 (128.000G) bytes-used: 8503794688 (7.919G)

First thing I would try is a new power supply!

I had Michel help me reconfigure my NVME so it is the boot drive and I had to redo my HA install but I can not get HA to show up at all. I briefly got a new device on my router but when I look at it there is no IP shown for it and it is no longer online. The HA directory is present and I can perform a sudo vm restart homeassistant and it all seems to be working. When I look in /etc.rc.conf i see ifconfig_re0="DHCP" vm_enable="YES" vm_dir="zfs:storage/vms" vm_list="homeassistant" mdnsresponderposix_flags="-f /usr/local/etc/udx.d/static/mdns.services" which looks good to me. Does anybody have any advice for me?

I hope @Michel Kohanimwill let us know!

I opened a ticket with UDI and Michel told me the scripts will be updated next week with more instructions.