KSaccullo01

https://forum.universal-devices.com/topic/43491-sprinkler-controller-irrigation-2024/ Open sprinkler and don't look back

Jazz --> Jazz===http://144.217.158.59:5152/ anyone have a good classical music station?

Country --> The_Ranch===http://185.132.41.147:8010/ Rock --> ROCK===http://cp6.digistream.info:42102/stream Catholic Radio --> EWTN===https://ewtnsgrewind.streamguys1.com/sgrewind/english/chunks.m3u8

Open sprinkler has been bullet proof. It as an open API that lets you add more functions. On my EISY I set flag if the temperature is over 95 degrees. if the flag is set EISY enables an extra water program on a few specific zones. At 2:00 am EISY disables the extra program. You can have multiple programs enabled at the same time.

You can activate the root account. I activated the root account. Created a new user account and deleted all traces of the default admin account. You can also eliminate the need for your new user account to ask for a password when using su. Just be careful how your system is exposed and who has access.

Try: sudo -s (enter password if prompted) crontab -e once saved new cron file should be in /var/cron/tabs/

Did you hand edit crontab? it look like you are in the system crontab. to edit correctly enter: sudo crontab -e it will bring up the vi editor so you may want to familiarize yourself with vi first. The file will be be stored in /var/cron/tabs As a side note. I completely deleted the admin account and all traces of it. I created a new account that uses the root folder. Eliminated the need to enter sudo for my new account and activated the root account. When I created the original cron file I did so directly as root. It should not matter. Try sudo -s then crontab -e.

Restart HA as a CRON job. Have CRON wait 3 minutes before starting HA.

When I reboot EISY HA does not see EISY. A "Failed to setup" error is thrown. Selecting reload fixes the problem, until the next reboot. The fix for me was to start VA from cron. /etc/rc.conf -- comment out vm_list="homeassistant" vm_enable="YES" vm_dir="zfs:HAIO" # vm_list="homeassistant" crontab. -- start the homeassistant vm 3 minutes after a reboot @reboot sleep 180 && vm start homeassistant I tried adding a delay vm delay in /etc/rc.conf. Did not work. vm_delay="300" hopes this helps someone else with the same problem

I used clonezilla for that exact purpose. Booted eisy into clonezilla and cloned the prinaly nvme on to a second one, exact same make / model / size as primary Tested it and no issues. I probably wont update the back up often, but at least i can get started f the primary drive dies.

Save the home assistant configuration then restore it. It worked for me after doing the SSD boot upgrade. in HA: Settings, --> System --> Backup. Save the backup file, tar file, on the computer the you remoted into HA. After a full reinstall and a new HA is running, restore the backup. At the main HA login screen don't setup a new account. select restore from backup. Select complete backup

What is the partition label name for the main partition (nvd0p2)? I had a few issues doing the NVMe upgrade. The original script did not want to run with the two functions in it: "setup_nvme_boot()" & "remove_emmc_mirror". So I broke the original script it into two separate scripts. That worked. However these seems to be a missing third function: "update_efi_boot_loader_label". I would assume it relabels paration 2. If someone could run "gpart list" on a factory system and provide the label name that would be great. My current partition labels: nvd0p1: efi nvd0p2: (null) nvd0p3: swap0 nvd0p4: HAIO ----------------------------------------------- Also I made minor changes to the script. added the alignment option and change the reserved size to 96 gb. MAIN_SIZE=`gpart show nvd0 | grep GPT | awk '{printf ("%.0f\n", ($3-42)/(2*1024*1024)-96)}'` gpart add -s ${MAIN_SIZE}G -t freebsd-zfs -a 512 nvd0 Added a 4th partition, by hand for home assistant. --> The eisy is a much more versatile box than i thought. Nice job team UD.

i see the file on my stock eisy. sudo find .... did not work. had to use sudo -i. glad you got it working

Maybe edit: /var/isy/FILES/CONF/NETWORK.CFG I don't know if it will work or break your eisy. Your on your own. you will need root privileges: sudo -i

Thank you dbwarner5 and hart2hart answer was hiding in plain sight.