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.

dbwarner5, How do you test for a startup? Kevin

Admin console --> zwave --> Detect Button Presses --> off

Guess I should read the manual

I just notice that my programs that call network resources were not functioning. The fix was simple should anyone else run into the problem. Open “Network Resources” (Configuration --> Networking --> Network Resources) Click on the URL, Resource editor should open. Click on update. Click on save, Resource editor should close. Click on save. Select the Name of URL you did above. Click test, confirm it now works. I had to do for each one of my but afterwards they all worked. Note: All my network resources were migrated from an ISY backup. Then reinstalled from an eisy backup after doing a factory reset.

I can outline more for you in a few days. It will be for the eisy. I dont know if it will work on a Polisy. The minidlan build (make file) is centerened around the eisy tremont processor. You may need to customize or try the package. Do you have and nvne drive added to eisy? I don't want to touch the internal drive, too much. Ok with ssh and all command line? Ok with SSH and command line? I use disk labels when the creating the volume on the nvme. So any FSTAB notes will assume using labels Know how to create a jail in freebsd? good reference. https://clinta.github.io/freebsd-jails-the-hard-way/ OK if you brick your Polisy / eisy? update: Attached rough how to for installing mindlna on eisy. Other thoughts for fun things to add: zwave OTA update tool, homeassistant... minidlna how to outline.docx

The minidlna server is successfully running in a jail on EISY. Onkyo receiver sees and plays music from EISY with no issue. The DLNA server does not look to taxing on the system with 12K songs. It was also complied on the EISY. Anyone else have a fun unsupported application you can share?

The fast on (sceen button1) and fast off (scene buttton 2) onmy homeseer dimmers are now missing. They were present with the 994. I tried removing and adding back. Tried with and without S2 security. Double click programs are all now a no go. Any one else with similar problem? Also, the 5 digit S2 security code takes any number. Correct or incorrect DSK code both are accepted. At least with the home seer 200 series dimmers.

For brians: A jail is similar to a Linux container or a very light weight vm (not entirely accurate but close enough for a starting point). It is a good way to separate out services and application from the main system. On my primary freebsd server, nothing, zero, nada on on the main system. I have a samba share, Emby server, Nextcloud server all running in there own jails on the main system. Makes maintenance easy. Keeping a copy of a working service is easy, especially if single jail port upgrade goes bad. Only rule on jails I bend is use of a single shared ZFS raid for the emby and Samba share via nullfs. On the shared media directory I used a chflags to minimize mistakes. https://en.wikipedia.org/wiki/FreeBSD_jail Mr Bill: Thanks for the ssh login change. I was being lazy and just figured the main UI console would do it. I'll take your advice and let UD do the updates. System is working. I kept a copy of 13.1 base and port files. Those will work for the jail, as a jail must be the same or lower version of the host.

Just upgraded from and isy 994 to eisy. The overall upgrade went well, keeping I mind I tend to void warranties and open boxes that say no user serviceable parts inside 😊. Before doing the upgrade, I removed the zwave devices from the ISY. Then I did a backup. The backup sans Zwave devices is what I used on eisy. My reason is I only have a few zwave devices and I wanted to include them with S2 security (no current migration path from S0 to S2 without removing and reinstalling). The only issued I encountered was with one of two Schlage locks. Lock on house worked fine. The one on a detached garage did not. The one on the detached garage worked fine with the ISY at S0, i think. But it would not work with the EISY at S2 (yes. it is a new model that is S2 compliant). I could only make it work with all the garage door open (no metal blocking the signal). Adding a module in between did not help. Suggestion: 1) Allow the ability to choose (force) S0 security. S0 was grayed out. I could only do S2 or none. I tried with and without “Use secure inclusion” check box and with and without S2 on the inclusion pop-up box. The none option on all the variations I tried only showed an “entry” none and no controls (lock, unlock , etc) in the admin panel. 2) Can an easy way be made to store the eisy backup configuration on the internal nvme drive? And back up from it? No samba with mapings… Question: 1) Why does the SSH console always stay at admin / admin even when changing the login user and password? I’m guessing for UD to be able to troubleshoot, but it still sems odd. Just needs a master reset. 2) I see eisy is running ver 13.1-RELEASE-p7. Can I apply any patches or upgrade to 13.2 without problems? Looks like eisy maybe running a custom kernel. I don’t want to trash eisy if a generic kernel wont work (as tempting as it is, I won’t ask what is customized). Main reason for question 2, I installed a jail. Playing with minidlna for a simple music server. 1) Normally I run Emby with dlna on my full sized freebsd box but want to play. Side note the jail is on a nvme drive installed in the eisy unit.

Agree with opensprinkler. The opensprinkler API makes is easy to add missing features. One feature I added is an extra water when the temperature gets above 94 degrees. Openweathermap runs an "Enable program 3" on opensprinker via the network resource on an ISY. Program 3 is on the opensprinker, not the ISY. At 30 mins after sundown opensprinkler gives a little extra water to a few select zones. At 1:00 am the ISY runs a "disable program 3" ISY only enables and disables one of the many programs on opensprikler, based on a weather condition. Kevin BTW have 32 zones and the opensprikler Pi version. Never had an issue, I run serval programs and zones simultaneously. Same pi is also running polygot ver2 with openweathermap.