K-bert

I would use a static IP in the router. That is how I had set up the ISY. I havent set up anything for a static IP for the EISY yet. I would like to sort out the problem I currently have first. K

I had the ISY set to a static IP. I haven't done that yet foe the EISY. My router updated its firmware and rebooted at one in the morning. I can find the EISY in the IoX finder again. Email still doesn't work. I will try setting up a wireless connection tomorrow as I was instructed by UD support. If that doesn't work I'm fairly certain I will have another remote session on Monday. K

I had logged into my router and used the IP that it listed for the EISY after switching cables/ports.

Well, I gave swapping the port and cable a try when I got home. The original configuration was ISP-Router-Switch-EISY. It is now ISP-Router-EISY. I'm afraid things got worse. Now the IoX finder can't see the EISY. I still have access through portal and on my phone though. Giving up for the night. K EDIT: I should add, entering the address the router gave it comes back with "invalid url".

I am using the same cable that was connected to the ISY994, I just swapped it over. I have a pile of cables at home so I will swap them as well as use a different port. I will also try wifi. Should have more info after Monday. K

UD support has been remote logged into my computer playing with my EISY. Looks like we now know what the problem is, just not why. The EISY is timing out when trying to send an email. The EISY is connected to my network through an ethernet cable yet the upload speed seems to be too slow. Looks like it isn't the EISY, but the cause isn't yet know. Next steps is to try a different port on the router/switch. Since I was not at home for the remote session this hasn't yet been done. We tried to get it to talk over wifi, but it wouldn't switch from cabled to wifi remotely for some reason. After about an hour we had to give up for today. We will try again on Monday. I have to say that I really appreciate that they are willing to spend this time to try and troubleshoot remotely like this. K

I have submitted a ticket. After some back and forth there have been no changes in behaviour. K

I have several programs that send emails. None of them are working. It is actually how I found out that this wasn't working. K

I did follow those instructions and I am using a google generated password for an app. I tried filling out the "From" field. No change. K

Ok, things are a little weird. I ended up rebooting my EISY. When it powered up I received an email telling me that someone has turned on the thermostat in the house. There is a program I have running that does do this if the thermostat is set to off and then turned on to heat. This program always emailed me after every reboot of the ISY. Now I received it from the EISY. I tried it with the both "use default" and the setup from above. Both worked. However, running a test email after that fails. I received a slightly different error message this time. EDIT: If I leave it as default the email is send by alerts@universal-devices.com and if I have the gmail account in there it is send by the google account I put in. This is expected behaviour, but it refuses to send any emails beyond that. Even if I try to run the same program to send the same message again.

I gave it a try, I received the same error message. Attached is the screenshot. K

That was the program I was using in the ISY. It worked well for these switches. I received a reply to my ticket: "HAIL does work for some devices but does not for others, it depends on whether it is defined by the device as SUPPORTED vs CONTROLLED. We are waiting on a fix to the library we are using that will work for both modes." So hopefully this will be working again in a future update. K

I recently migrated from an ISY994i to an EISY. It is running IoX v.5.5.7 and the default mail server doesn't seem to be working. I have left SMTP Settings as "Use Default". When I try to test the email addresses that I have loaded into the system I get the error message "Mail server failure [[SMTP_ERRORS--1]]" Is there an issue with the mail server or is it something I have done wrong (more likely)? K

I would hope that it wouldn't be too much work to fix the hail. It worked fairly well with the ISY. I am using the two switches to run bathroom fans. Both have a timer so after a certain number of minutes they turn off. One of them is in a room with a shower and a z-wave humidity sensor which is used to automatically turn on the fan when the shower is used. The two dimmers are controlling the lights in the great room and the front entrance hallway. The dimmers are less critical than the switches. K

Thank you. I have submitted a ticket. I expect that there are a lot of tickets currently being dealt with considering how new these things are. K

I too am having trouble with my Fibaro. When I migrated it added more nodes than I know what to do with. More frustrating is the fact that status updates aren't working in the EISY. They have to be queried before any changes are seen. Also changing parametre settings doesn't seem to really do anything. K

A further update: The Insteon water sensors were updated when they sent their heartbeats as expected. The thermostat also seems to be happy. So everything Insteon is working fine. Still have some z-wave issues. The hails sent from my Leviton switches and dimmers are not being seen in the event viewer. The ISY used to see the hails and then a program would query the devices to update the status. Without the hails being seen the device status is not updated in the EISY. I have tried removing one from the system and adding back in. No change. The Zooz 4 in 1 seems to be working, but it is hard to tell if it is keeping the parametres that I am trying to set it for. I am trying to change the humidity percentage difference to report to a smaller number than 10%. I am also trying to change the temperature report from F to C (I live in Canada). So far I have been unable to change it. The Fibaro Smart Implant seems more complicated than ever now. Because this one isn't battery powered I seem to be able to set the parametres fine and can query them and they seem to have taken. However, I cannot get it to behave as it used to. I have tried to set it up with the two inputs as binary normally closed for the front and back doors. First it isn't automatically updating in the EISY, I have to query it. Second the only thing that changes when a door is opened is the multilevel sensors go from 0V to 15V (supply power voltage). Again this has to be queried and isn't updated automatically. The Weiser door lock I removed from the network and then added back in. I am very glad I did. This device is now working much better than with the ISY. One thing that the ISY struggled with was recognizing which user code was used to unlock the door. The EISY is handling this with ease. I knew there were going to be some growing pains. And I am sure that after some time I will get everything back up and running how I like it. I am also sure I am going to need to ask advice from those with more knowledge than me. K

I migrated from my ISY994 with 500 z-wave board to an EISY with the Zmatter dongle yesterday. I had some issues with the z-wave stuff, but most of that was fixed when I removed and then re-added them to the system. I currently have a problem with the Leviton switches and dimmers. I have two of each. The Leviton devices do not update their status automatically. This was a known issue with the ISY. I found the solution on this forum which was to have the ISY react when the Levitons sent a hail. Every time the Leviton switches and dimmers were operated manually they sent out a hail. I have a program that when a hail was received from that device it would query the device. This worked fine and the ISY always knew what status the Levitons were. Now that I have migrated, the EISY is not updated when one of the Levitons is operated locally. I can still query and control the devices just fine from the admin console. I opened up the event viewer and set it to level 3 (device communication events) and the hails are simply not present when I operate the devices locally. I am confident that they are still being sent out, but the EISY is not registering them in any way. I tried removing one of the devices from my system and then added it again. This didn't change anything. Is there something I have missed in getting the hails? I really don't want to have to set up a query program that seeks information on a schedule. For example: every 30 seconds query all Leviton devices. Any help would be appreciated. K

I couldn't let it go. I removed and then added the Zooz 4 in 1 sensor. Operation successful. Big change is the increased security feature. I had to put the pin number that is listed inside the device into the EISY before it would be added. I now also receive more information in that it tells me if the device is awake or not. I have to re-add it to my programs now, but it should work just fine. I will update when I get to play with the other devices. K

Just thought I would provide an update on how things went. I followed all the instructions: make a z-wave backup in ISY994, make a backup of the ISY, power down the ISY, connect and power up the EISY, upgrade packages, enable z-wave and Insteon, restore from backup, restore PLM (using a USB unit instead of the serial). It didn't go perfect, but nothing caught fire either. I have problems with most of the z-wave devices and some Insteon devices: The only z-wave device that seems to have migrated successfully is my Weiser deadbolt lock. I can unlock and lock it and I also get the locked status updated when lock is operated manually. I don't have the battery level information yet, but I am going to leave it alone and see if it shows up later. All the others had the indicator that the device is being written to next to it, except for the two Leviton dimmers and two Leviton switches and the Zooz 4 in 1 sensor. The Zooz device had the expected "placeholder". I woke it up and did the sync "update with interview", and it sort of worked. However, all it tells me is the battery percentage. I don't get the humidity, light level, temperature, or motion. The two Leviton z-wave dimmers I have are controllable, but their hails are not seen in the event viewer. As such the EISY is not updating when the dimmers are operated manually. The two Leviton switches I have for bathroom fans are doing the same. Running a query does update the EISY, but because the hails aren't seen my program to query the devices upon hail is not run. Finally the Fibaro Smart Implant that is monitoring the outside door statuses through the security rough in as well as controlling the humidifier isn't communicating and has red "!" next to all its nodes and gives me "request failed" messages when I try to communicate with it. As for the Insteon, All the wired in switches and plugs seem to be operating just fine. The Open/Close sensors on the pantry and laundry closet didn't initially work when I did the restore PLM. I turned off "Automatically write changes" and then turned it back on. I was notified that I had devices that needed to be put in the programming mode. I did this and then clicked "Ok" and now they are in just fine. The two Insteon leak sensors haven't update the EISY with any information, but I assume that happens when the heartbeat is sent out, so I am not worried about it yet and will check again later. The thermostat has me a little concerned. I had a lot of trouble getting it to work with my old ISY when I first got it. It did not want to communicate. It took a lot of trouble shooting, including isolating the thermostat from the furnace control board wiring. Instead I have it on its own power supply controlling two relays, one for the fan and one for the heat. So far tonight trying to manually change the thermostat settings from the admin console only works some of the time. Also changing things on the thermostat doesn't update the EISY unless a query is run. However, so far my program to run the furnace fan for five minutes on the hour every hour has worked without fail. Granted, it has only been three times so far. I think my best bet may be to remove the z-wave devices and then reconnect them. It won't be tonight though. It is getting late where I live. K

Nice! That is good to know. Now I just need to find some time to get all this done, assuming there will be some trouble shooting. Hopefully this weekend, wife and kid permitting. K

Thank you. I think my plan will be to do the z-wave backup, then the ISY backup. If I have two files I will restore from the ISY backup first. If the z-wave comes over, great! If not I will us the z-wave backup. All in all I only have six z-wave devices, so I can start the z-wave from scratch again. I am also using a different PLM for the Insteon side of things (USB whereas the ISY has a serial unit). So I will already have a few extra steps. K

I am referring to the directions in the wiki (your first link). I will have created a z-wave backup of my ISY, but the only z-wave directions in the wiki are for if I am migrating from an Eisy or Polisy. Because it simply states "if migrating from ISY use that backup" I am wondering if that will bring in the z-wave automatically. I will browse the thread you linked. Thank you. Copied and pasted from from wiki instruction: If you are migrating your Z-Wave network If you aren't already using it, plug in your ZMatter Z-Wave dongle and unplug any other Z-Wave dongle you may have been using. (Polisy only) If you have a ZMatter Z-Wave board then power down Polisy, add it, then power on again. Reboot Eisy / Polisy Use (Admin Console | File | Restore ISY) to restore your "migration" backup If you are migrating from Eisy / Polisy use the migration backup (e.g. "ISY-BackupWithZWaveMigration.v5.5.4__Sat 2023.01.21 09.07.44 AM") If you are migrating from ISY-994 use your ISY-994 backup When IoX restarts, it automatically does the following: Writes you Z-Wave network into the ZMatter Z-Wave controller Interviews every Z-Wave device in the Z-Wave nework, creating/updating nodes, programs and scenes. This process can take anywhere from a few seconds to a few minutes for each device depending on the complexity of the device. The best way to monitor the progress is to open the Admin Console Event Viewer to level 3 For those who want lots of low-level details, you can also use this from the command line: tail -f /var/isy/FILES/LOG/ZWAY.LOG If you don't actually change your Z-Wave network by adding/removing Z-Wave devices after migration, you can back out the migration by connecting whatever Z-Wave dongle you were using before migration and restoring the backup you made prior to migration.

My EISY has arrived! I have been going over the migration instructions. I am migrating from an ISY-994 with the 500 series z-wave board. The instructions call for me to make a backup of the z-wave network and then a general backup of the ISY. Then power it down. In the migrating section under the "If you are migrating your z-wave network" it says that if you are migrating from ISY-994 to just use the general backup. Will this restore my z-wave? Do I need to restore the z-wave backup as well or is the backup just in case something goes wrong? K