TheA2Z

Thanks @DennisC For the mailbox voice alert, that is what I do just speak the words as you show. For the water alarm, I want for it to actually activate the siren alarm in the house as well. I programed a key on Elk keypad to set off water alarm that worked great with ISY. I can do the speak words option for it as well. Looks like it is in the enhancement list. So I will use the words option for both alerts.

Which is best for eisy network? Anyone seeing any differences that would pick one over the other? I can do either.

Thanks all., Will give it a go this weekend.

Ok, thanks @MrBilland @Geddy. Will look to use one of the options you two called out this weekend.

Just migrated to eisy. Trying to send alerts to cell using the @tmomail.net email address in the group settings. I dont get the alert from eisy. I do get the alert from eisy, if I send to my email address. I also get the alerts on my cell, if I send from my email. Just dont get them when sent from eisy. For my SMTP setting I checked use defauilt. Anyone else had this problem and have a fix or work around?

Just bought the Elk node today and I am setting up. So far so good. One thing I cant figure out is how do I have an eisy program push an Elk Keypad F# button? In ISY I had a program that if leak detector had a leak, it would programmatically push the F5 button on the ELK keypad to cause the Elk to voice announce a water alarm. I also use it to voice announce a mailbox open alarm by pushing another Keypad F key. Please let me know how I can do this. Thanks!

I was scouring the other posts and found this one. Dennis C post in other topic. Sure enough, I pushed the power button one time and it started updating and I monitored it happening in the logs. Im hopeful when it is done, I will reboot. I will download the new Start file, clear the java cache and see if it works.

Followed all the steps above. Still cant get Eisy to show in the IoX launcher. I am able to ssh into the eisy though. After reboot I checked the log again using the tail method above. It sis still showing the same statements that the different packages needing to be updated. It is saying the packages need to be updated. Do I need to update them or should eisy do it by itself? The ethernet port is showing flashing green activity, but nothing is updating in the log. Does the screenshot below reflect what a successful update of eisy should look like or does it look like something is wrong?

Thanks @DennisC I will give it a shot. Thanks for helping me out on this.

When I ssh'd in and typed sudo tail -f /var/udx/logs/log That is all that showed on the screen? The dates stamp for those activities were an hour ago.

No luck on being able to access the eisy after hitting Upgrade Packages in admin. Been an hour. The Logs show this from almost an hour ago then stop. I rebooted and still cant get to admin screen. Do I need to do a factory reset and try again?

It will be the first upgrade since I got the eisy in Jan. Ill keep monitoring. Where are the SSH instructions to monitor progress? Couldnt find, can you send link?

Just getting around to starting my ISY migration. First step, hooked eisy to ethernet cable and logged in with IoX admin. Clicked Upgrade Packages button. Been about 15m since I hit the button. How long does it take before the eisy shows back up in the IoX finder screen hitting refresh?

Older post, but started having same problem of notifications not being sent. Worked for the test email in ISY but didnt work for others. I had a custom email setting for SMTP. I tried multiple email smtps. Program would not send notification, but worked with ISY test email. To fix, I just use the default checkbox setting for email settings. Works fine from programs now.

@Chris JahnWhen is the next build forecasted to be released?

Thanks @lilyoyo1. I have been in IT and avionics repair for almost 30 years. I get your point as things never go as smoothly as planned. However, there is a difference between bleeding edge new tech that has to have HW and OS kinks worked out compared to a stable system where you have a flukey zwave device install or program debugging that is kicking your butt that you have to try things, back out, and try again. Good to hear you got your polisys working as that is a good to hear that. I was interested in hearing responses from folks that may have a similar ISY install as me and that they were able to get their eisy setup this past week. I know eisy is new and kinks will need to be ironed out. Just would like to hear some success stories with similar setup.

I got my Eisy, PLM kit, and zMatter comes today. As on most forums it is mostly folks posting with problems they are having. I was wondering if anyone with all my items in the title got their Eisy fully setup and functioning? Before I blow a weekend setting up, I want to make sure kinks are worked out. My plan is to backup and restore my ISY config and programs and restore to eisy. Dont currently have Polisy, but I know I will need to setup node server for my ELK alarm. I plan to do clean install of all zwave devices (alot of them). ISY has gotten slow over years as I added zwave devices. Also have some rogue devices that I cant clear/ forget. Best to start clean for me. Interested from you success stories are there any tips or tricks you encountered on your road to success. How long do you think it took you to setup completely? If there are no complete success stories, Ill probably hold off a few weeks to install. As much as I love to tinker on stuff like this, just dont have time right now.

Thanks @dbwarner5

Thanks @Bumbershoot

Thanks @lilyoyo1 Not a hardcore developer and havent used Node Servers so far. Any easy way of getting my isy elk config into the Node Server and integrating with eisy? Anyone have a step by step process?

Eisy is on the way. zMatter shipping 12/27. Currently on isy, elk screens/integration is part of the admin console. When I back up ISY and install in eisy will this ELK setup port over? If not, how do I get Elk setup with eisy?

I just took the plunge and ordered the "whole left side of the menu" for Eisy: Eisy, matter USB, and PLM adapter. Funny I was thinking the exact same thing as original poster when I came across this post. So what is the consensus on migrating over to Eisy from ISY? I was thinking: Backup from ISY and restore config to Easy. Not the zwave restore. Ensure all config looks correct in Eisy and can connect to ELK, variables are in there, programs etcs. Disable all programs in Eisy until I get the zwave devices updated in them to prevent errors in Eisy. I was thinking of keeping both boxes up and migrating device by device starting closest to box to easy and updating programs in Eisy to use the new device. But, seeing last post Im rethinking. So for step two, factory reset all zwave devices up front. I would not think I would need to do an exclude now from Eisy as it should not be in the Eisy zWave controller. So I would just include each factory reset devices one at a time starting from closest device. Then add that device in Eisy to each program that used it in ISY. Rinse wash repeat until all zwaves are in Eisy. What about my Insteon leak detectors. Is it the same process? Thoughts on the approach above or anyone got a better idea?

Not a major update for me. Went from 16 to 16C. No issues.

Michel, Thanks! I upgraded to Pro and Im back in business. I got over 250 nodes and folders. it would be nice if it was more descriptive on the error.

Getting a strange error that I haven't had before. When I try to add a new subfolder to the main screen, I get a pop up that says: "Request Failed." Click ok and it goes away. Nothing shows in the event viewer. I rebooted ISY. Tried again and got error below. Then tried again and got "Request Failed" I have added many folders on the main screen before with no issues. I can add a new folder on the Program tab. Version info below. Anyone have a clue how to fix?