DennisC

Suggest sending tech support a note and they will transfer the unit over to you. They will need the serial number.

I suspect that when you installed the zwave board it either didn't seat properly or it's in the incorrect slot. There are two slots and the instructions tell you which one to use. I suggest opening the ISY, removing the board, and reinstalling it.

As previously indicated, repair links is necessary after upgrading v5.2.0. In addition, I would ask how deep is your zwave mesh? You may need to add some devices or a zwave extended to insure a solid mesh network. Not being able to communicate is a strong symptom of needing to improve the zwave mesh.

But remember, you can not upgrade past 5.0.16C without the series 500 zwave board, if you have a zwave board installed. While you indicated you are not using zwave, that is not necessarily the same thing as not having the board installed.

Take update v5.2.0, which is the post we are currently in. Go to the first page and read the first post. All of the changes for v5.2.0 are listed right there on in the first post. If you are interested in a previous version you can search for that version and read the very first post. They are all listed here: https://forum.universal-devices.com/forum/15-current-release-betas-and-bug-reports/

All of the release notes are published on the same page as the upgrade files. All you need to do is look at the version number in question.

Have you confirmed you are using the series 500 Zwave board?

Try doing a synchronize all before reverting back.

If your admin console is sluggish you may need to increase your Java memory. Search the Wiki for instructions.

Are you saying none of the ISY front lights are on? If so, you are having a problem with your ISY. Check the power supply to start.

Here is a link to the troubleshooting section of the Wiki for Macs: https://wiki.universal-devices.com/index.php?title=Troubleshooting_Help

There in stock directly from UD store: https://www.universal-devices.com/store/

Information on correcting this issue can be found in the Wiki on troubleshooting. Scroll down a bit: https://wiki.universal-devices.com/index.php?title=Troubleshooting_Help

Try using start.jnlp following the instructions here: Chrome works fine. Make sure your firmware and UI versions match once you get in.

Just reply back to the ticket that you are having difficulties after following their directions. They will continue to help.

What does the log for the individual node Server say?

Have you entered data in the configuration fields in each Node Server from within Polyglot on either Polisy or your RPI?

I am monitoring 2 houses and definitely exceed 100 messages a month just from the monitoring.

I also use both, depending on message size and have not had a problem with either.

You may want to verify this before making a purchase with the company you are purchasing from. It was a while ago but I seem to recall someone getting a new ISY994i and it shipped with v5 firmware.

I would suggest making sure your firmware and UI versions match. If that's ok then right click one device and selector restore device.

You should use start.jnlp to launch the admin console which will automatically select the correct UI for your version. It is available on the release download page. There are at least two different versions depending on which version firmware you have.

I know you said you checked, but it sounds like it was not wired up correctly.

If you disconnect the smoke detector momentarily, does the speaker sound stop?

I would suggest doing most of the logic in the ISY. When the CT changes state, have the output turn on. Write an ISY program to monitor the output and handle the wait. I'm not near my system right now and don't remember if you can program spoken words in the ISY for the ELK, if not, have ISY set another output on after the wait period and have the ELK monitor the second output. When the 2nd output turns on, the ELK announces the cycle is complete. Over the years I have found the ISY handles the programming much better then the ELK. The ELK acts as input/output device very well.