tazman

@RRalstonI'm not aware of any documentation did you look on the plugin's Github site? I have the vehicle charger and I'm able to start and stop the charger and set the rate it charges at. You can control all of that in programs or manually. I use it to have my own charge on solar programs so it starts charging when there is enough solar, adjust the rate of charge to only use solar to charge the vehicle and stops charging when the solar is to low.

Everything is working for me now! @rob7419if you do as @shbatmrecommended to me on his github page https://github.com/shbatm/hacs-isy994/issues/112 that will force the ISY integration to reload on it's own. I love this community the way everyone is so helpful and how UDI goes above and beyond on everything they get involved with. Thank you all!

I'm putting this here to mark as a fix for the original problem of HA not being online. My understanding is that this will be incorporated in a future update. sudo udxops.sh repo.util sudo pkg install -f udx I wanted to mark this post as the solution but it is not giving me that option so hopefully @Geddycould mark it for me.

It depends which problem you are having. We have it that HA starts and is online now. The problem I'm still having is the ISY integration needs to be reloaded after everything starts.

@KSaccullo01I tried this fix but I'm unable to get it to work. Does it have to go somewhere special in the file? # /etc/crontab - root's crontab for FreeBSD # # $FreeBSD$ # SHELL=/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin # #minute hour mday month wday who command # # Save some entropy so that /dev/random can re-seed on boot. */11 * * * * operator /usr/libexec/save-entropy # # Rotate log files every hour, if necessary. 0 * * * * root newsyslog # # Perform daily/weekly/monthly maintenance. 1 3 * * * root periodic daily 15 4 * * 6 root periodic weekly 30 5 1 * * root periodic monthly # # Adjust the time zone if the CMOS clock keeps local time, as opposed to # UTC time. See adjkerntz(8) for details. 1,31 0-5 * * * root adjkerntz -a @reboot sleep 180 && vm start homeassistant

I found this in the log file for Virtual but there is no place I see to allow access. Does the node server need to be updated? My virtual devices seem to be working properly so I don't know if this can be ignored. 2024-03-20 08:45:20,139 Thread-13 udi_interface.isy ERROR isy:_info: Access to ISY is not authorized. To allow node server to access ISY directly, go to the node server configuration and click Allow Unrestricted ISY Access by Node Server 2024-03-20 08:45:20,139 Thread-13 udi_interface.isy ERROR isy:_info: Access to ISY is not authorized. To allow node server to access ISY directly, go to the node server configuration and click Allow Unrestricted ISY Access by Node Server Sometimes when I press the on or off of a virtual switch from the AC I get the error pictured below with nothing in the Virtual error log and the switch changes state.

I opened a ticket and sent the log to Michel.

@Michel Kohanimthank you very much for your help in supporting items that are not UDI since we have tried what we can with ISY I can go through the proper channels with HA and the ISY integration to see if @shbatmcould make the integration look for ISY again after failure. Unless there is a reason you prefer this go through the UDI ticket system?

@Michel KohanimI tried what I think you outlined and it did not help for me. I will post the 2 files just to see that I did everything ok. #!/bin/sh # PROVIDE: pg3x # REQUIRE: NETWORK ldconfig # KEYWORD: shutdown # BEFORE: vm # Add the following lines to /etc/rc.conf.local or /etc/rc.conf # to enable this service: # # pg3_enable (bool): Set to "NO" by default. # Set it to "YES" to enable polyglot v3. . /etc/rc.subr name=pg3 desc="Polyglot3 IoX service" rcvar=pg3_enable load_rc_config $name : ${pg3_enable:=NO} : ${pg3_user=polyglot} : ${pg3_homedir=/var/polyglot} : ${pg3_workdir=/var/polyglot} #!/bin/sh # $FreeBSD$ # PROVIDE: isy # REQUIRE: NETWORK ldconfig udx polyglot # KEYWORD: shutdown # BEFORE: vm pg3x pg3 # # Add the following lines to /etc/rc.conf.local or /etc/rc.conf # to enable this service: # # isy_enable (bool): Set to "YES" by default. # Set it to "NO" to disable isy = ISY Service. . /etc/rc.subr name=isy desc="ISY Service" rcvar=isy_enable load_rc_config $name . /usr/local/etc/isy.d/static/common.sh : ${isy_enable:=YES}

@walkman9999sorry i'm not familiar with the product and new ZWAVE devices need to be remove before adding just to clear testing references. If the remote also works through ZWAVE you might have to check with the manufacturer or maybe someone here with the same model can help if you list what model you have.

@rob7419yes I do have the ZMatter dongle with some ZWave devices and the ISY integration did load fine without the ZMatter dongle plugged in. Maybe we can get @Michel Kohanimand @xKingto see if they could figure this one out also.

Try removing the blinds before you add them to eisy.

@rob7419is homeassistant starting before ISY for you? Now I have to go into HA and reload the ISY integration to get it to connect. @xKingdo you have any ideas how to deal with this?

@rob7419thanks for the update I sent Michel a message through my ticket because I was not able to figure out how to access the file he wanted.

To bad I had high hopes my eisy started out as WIFI but I did the 4 button press to reset when we found the problem with some node servers and WIFI. I will still give it a try tonight when I get home.

I am not using WIFI.

This is the end of the file without ISY and UDX WARNING: attempt to domain_add(bluetooth) after domainfinalize() WARNING: attempt to domain_add(netgraph) after domainfinalize() bridge0: Ethernet address: EDITED bridge0: changing name to 'vm-public' re0: promiscuous mode enabled vm-public: link state changed to UP Security policy loaded: MAC/ntpd (mac_ntpd) tap0: Ethernet address: EDITED tap0: promiscuous mode enabled re0: link state changed to DOWN vm-public: link state changed to DOWN tap0: link state changed to UP vm-public: link state changed to UP re0: link state changed to UP This is ISY and UDX enabled then reboot and HA not working WARNING: attempt to domain_add(bluetooth) after domainfinalize() WARNING: attempt to domain_add(netgraph) after domainfinalize() bridge0: Ethernet address: EDITED bridge0: changing name to 'vm-public' re0: promiscuous mode enabled vm-public: link state changed to UP Security policy loaded: MAC/ntpd (mac_ntpd) tap0: Ethernet address: EDITED tap0: promiscuous mode enabled re0: link state changed to DOWN vm-public: link state changed to DOWN tap0: link state changed to UP vm-public: link state changed to UP re0: link state changed to UP lo0: link state changed to DOWN lo0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP I have both full files saved if they are needed.

@xKingrebooted 3 times and HA came right 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" udx_enable="NO" isy_enable="NO" #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" vm_dir="zfs:storage/vms" #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" ~

@xKingI think it is safe to say net.link.tap.up_on_open: 1 and vm-public is UP at start are being set correctly but unlike @rob7419 I have experienced starting HA manually still results in a fail and vm-public and Tap0 are not showing as UP after starting HA but sudo ifconfig vm-public up; sudo ifconfig tap0 up sets them to UP and HA starts working.

Mine will not but I don't know if that is the normal since I have home assistant issues also.

Start 1 everything good and HA started Start 2 '1' and vm-public UP at reboot HA would not come up and vm-public and Tap0 not up after starting HA Start 3 '1' and vm-public UP at reboot HA started noticed pattern from before did 'sudo vm poweroff -f homeassistant' then rebooted Start 4 '1' and vm-public UP at reboot HA would not come up and vm-public and Tap0 not up after starting HA Start 5 '1' and vm-public UP at reboot HA started moved vm_dir="zfs:storage/vms" to before vm_enable="YES" in rc.conf file Start 6 '1' and vm-public UP at reboot then HA started Start 7 '1' and vm-public UP at reboot then HA started Start 8 '1' and vm-public UP HA did not work Start 9 '1' and vm-public UP at reboot HA started Start 10 '1' and vm-public UP at reboot HA started @xKingI feel moving the path of vm before starting vm helped but I can test more tomorrow afternoon if you want more restarts or to try something else.

[admin@eisy ~]$ sysctl -a | grep up_on_open net.link.tap.up_on_open: 1 [admin@eisy ~]$ sudo ifconfig -a Password: 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 9e:73:5c:44:25:33 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 6388 @xKingI will do a couple of reboots but this is the state it was in when HA did not come online after the last reboot. It seems odd to have the 1 but the devices not to be 'UP'

@xKingI rebooted eisy and 'vm start homeassistant' I don't know why but it seems inconsistent how it works.

@xKingI restarted again and after starting HA the vm-public and Tap0 were not 'UP'

@xKingfor this instance everything started fine Tap0 is UP and home assistant became available at homeassistant.local:8123 but I don't know that it would happen all the time unless it is just a matter of starting HA after everything else.